On Jun 22, 2006, at 3:30 PM, Andreas Grau wrote:

I am looking Dada 2 10 8 PRO Mystery Girl, and others, are in the
extensions directory, yet Config pm points them to plugins What is
the recommended way to handle this ?

It is a little confusing, but Mystery Girl started as an extension,
and I tacked on the ability to use it as what's basically known as a
plugin, but because of how the versioning control works, I haven't
moved it over to where the plugins reside

The other extension don't have to be moved anywhere special

Speaking of outside configuration, can't we have $PLUGIN_URL
settable in the outside configuration as well ? As of now, it wants
plugins/ and extensions/ in the same directory, read URL, as
mail cgi - wouldn't it be sufficient to have line 1279 of Config pm
be changed

from my $PLUGIN_URL = $S_PROGRAM_URL; to $PLUGIN_URL ||= $S_PROGRAM_URL;

Then, $PLUGIN_URL could be set in the outside config as well

Right now, there's this:

[code]

my $PLUGIN_URL = $S_PROGRAM_URL; $PLUGIN_URL =~ s/mail cgi$//; $PLUGIN_URL = 'plugins'; my $EXT_URL = $PLUGIN_URL; $EXT_URL =~ s/plugins/extensions/;

[/code]

This is saying, if you're Dada Mail is at:

http://example
com/cgi-bin/dada/mail
cgi

Plugins live here:

http://example
com/cgi-bin/dada/plugins

Extensions live here:

http://example
com/cgi-bin/dada/extensions

Feel free to change this as needed :)

Usually, when I set the $ADMIN_MENU variable in an outside config
file, it looks sort of like this:

[code]

$S_PROGRAM_URL = $PROGRAM_URL; my $PLUGIN_URL = $S_PROGRAM_URL; $PLUGIN_URL =~ s/mail cgi$//; $PLUGIN_URL = 'plugins'; my $EXT_URL = $PLUGIN_URL; $EXT_URL =~ s/plugins/extensions/;

$ADMIN_MENU = [ # a whole bunch of stuff ];

[/code]

Cheers,