self-intro: Craig Sebenik

Max Kanat-Alexander mkanat at bugzilla.org
Sat Jul 19 00:36:50 UTC 2008


On Fri, 18 Jul 2008 17:18:03 -0700 Craig <craig5 at pobox.com> wrote:
> I was thinking that if combined with more CLI controls, then moving
> away from static files becomes easier. After all, if you can still
> edit (and view) the commands via the CLI, isn't that the same thing.

	Well, I'm not sure we want more CLI controls, that's would add
a fair bit of code complexity to help only a small portion of our
users, who are the type of people who are probably already smart enough
to just use our XML-RPC interface to create their own CLI controls.

	But yes, a lot of those params should probably be in the DB. I
just need a concrete example that really proves *why* that's the case.
After all, right now, "it ain't broken."


> >>    - move the help pages/data into the DB
> > 
> > 	We generally don't want strings in the DB, it prevents
> > localization.
> 
> Couldn't that *help* localization?
> [snip]

	Not without a fair bit of additional code and query complexity
that I'd like to avoid as much as possible.

	The best way to do localization would be gettext (or really,
Locale::Maketext) and that's what I'd like to focus our efforts on, if
we're going to go in some other direction for localization.

> That would be a far amount of effort with questionable benefits. I
> think it makes sense and provides more functionality, but the cost
> could very well out-weight the benefits.

	Yeah, we have a bug where we discuss it, somewhere.

> That brings up a question... In the past, most of my web apps have
> had really simple CGIs and almost all of the logic in the perl
> modules. [snip]

	We're moving more in that direction. If you think of our CGIs
as "controllers" and our modules as the "model" in the MVC sense, then
I'd like to get more of the logic inside the model and out of the
controllers. But I wouldn't want to remove it *all* and just have it
call a single function. I want a flexible model and then the
controllers can use it as they please.

	-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.



More information about the developers mailing list