} [ James P. Goltz writes: ]
} > I'm aware of the "new_keyword" function in config_parse.pl to add
} > keywords to the per-list config files. What I'm not sure of is:
} > *where*, exactly, should this function be invoked?
You may place your own new_keyword() invocations in config_parse.pl
directly. However, one tactic I took was to simply locate all
keyword additions in a 'mj_local.pl' file and then 'require' it
within config_parse.pl. This way, when we upgrade, all the changes
are localized to one file and they won't be lost if config_parse.pl
gets overwritten by a new distribution.
On Feb 18, 8:43am, Dave Wolfe wrote:
} new_keyword() doesn't exist in 1.94.1 since
} nothing used it. The good news is that 2.x is designed with modularity
} and extensions in mind.
[This is a developer issue, so I have copied the -workers list.]
What!!!!??! Is this true?!? I'm sorry, but what is the point of
providing an 'API' (that's really what it is) if there is
absolutely no intent to carry it forward? All the documentation
said to use new_keyword() for enhancements, since it provides a
layer of abstraction. The assumption was that layer would be
carried through to other releases.
Dropping it because "nothing in 1.94 used it" is not a good idea.
I don't think the point was ever to have Majordomo itself use it.
The point was to have it available so that external routines could
use it without worrying about the internal structure of Majordomo.
I use it heavily to add local keyword enhancements to my
installation. If new_keyword() is gone, then all my efforts to
follow instructions and provide an easy-to-migrate setup are
} For now, however, if you know enough to figure
} out new_keyword, changing config_parse.pl to add new keywords should be
Not true: MajorCool (the admin Web interface) requires the
addition of one keyword. My installation instructions directed
people to use 'new_keyword()' in order to implement it. While the
above statement is true for me as a *developer*, the same cannot
be said for your typical site administrator. My experience has
been that most people can barely handle adding the one-statement
new_keyword() addition -- having to change config_parse.pl in 2
or 3 different locations is just asking for trouble.
Enough of my rantings. Let's get to some resolution....
Is new_keyword() gone? If so, what are the chances of replacing
that functionality, say in 1.94.2?
Is there any kind of 'API' in 1.94? If so, can we get a commitment
to please carry it forward to 2.0? There may be people out there
using it without our knowledge. Let's not break things unnecessarily.
Geez...changing the API from release to release. Who do we think we
are, Microsoft? :)