Re: [SM-DEVEL] Plugins - Looking forward to SM 2

[Erin S. <ebu...@sq...>]

pdo...@an... said:

>> On Tue, Feb 18, 2003 at 09:06:57PM -0800, pdo...@an...
>> wrote:
>>> we should have a way to address this kind of thing, even if it
>>> requires a separate perl script in each plugin directory that takes
>>> over the registration of hooks.
>>
>> Which would make perl a pre-requisite for SquirrelMail, instead of
>> simply a useful extra.  I think this should be avoided.  It would
>> certainly exclude some of the current user base, who install SM on
>> webhosting sites where they have no access to Perl.
>
> I think the number of persons who do not actually use conf.pl isn't large,
> and I have no idea, but it seems if they have enough shell access, they'd
> have access to Perl.... but your point is taken nonetheless.
> Unfortunately, besides an 'exclude list' which is being discussed now, I'm
> not sure what else we'd do... except maybe create a php-based
> configuration script...  also, the current proposal for new plugin design
> would pretty much necessitate Perl access, since conf.pl starts to do
> things that a sysadmin won't easily be able to duplicate manually.  This
> might be something we want to talk about (separate from the issue you were
> responding to)
>
>> OTOH, it would be nice if plugins could also add their own
>> sections/options to the conf.pl script in a fashion similar to the SM
>> options pages.
>
> nice idea.  would be interesting to move conf.pl to "conf.php"...

Paul -
Look at config_revisions.php in sm2_planning. That is all about how to
encode config information so it can be parsed by whichever language we
want (which opens the door for a php script or a perl script or a webmin
plugin, should someone want to go that far.. ;).

the only reason we'd do this is precisely what was mentioned. Some people
don't have shell access. I personally find making config tools like this
webaccessible to be asking for trouble, but I suppose some would rather
use a web front end...

In any case, we're trying to get around the maintenance nightmare that
currently exists between conf.pl and the admin plugin (which always seems
to be out of date, and which doesn't perform a lot of the input
verification, etc.)

On the other hand, I'm beginning to think some of those config ideas are a
smidge over the top... but anyway - take a look.



Erin
(ebullient)

--
'Waste of a good apple.' - Samwise Gamgee
ICQ: 38670353