At 08:04 PM 1/19/98 -0600, Jason L Tibbitts III wrote:
>
>BH> 2) a subsystem view of the config file, to limit the admin screen to
>BH> just show "resend" variables, "majordomo" variables, etc.
>
>That sounds interesting. I'd eventually like to see a tree-like approach,
>or something like it. I'm sure you can already handle the fact that a
>variable can exist in more than one group.
>From a Majordomo 1.94 + MajorCool perspective, no, since the keywords are
an index into a single hash and the indices have to be uniquely named in
$config_opts{} and %known_keys. But from an abstract MajorCool + Majordomo
2.0 standpoint, sure, I just call a get_keyword function which returns the
appropriate keys and run with it.
But really, what code exists now has little bearing on what will be.
MajorCool for 2.0 will probably be a complete Perl5 rewrite, much like
Majordomo is. The interface ideas and lessons learned will still be
applicable even if all the code isn't. (But first I guess I gotta learn
this Perl5 object stuff.)
--bill
Follow-Ups:
References:
|
|
