>> One thing we're thinking of adding for 1.5.0 is an enhanced config
>> that will make the config process easier in general.
>> One of the things currently on the board is making it possible to
>> plugin configuration with the main SM config (so you don't have to
>> remember to visit each plugin directory, etc.
>> *If* you're going to institute more changes to plugin structure for
>> new system, it would be good if it were compatible, etc, with what's
>> worked on for 1.5, so that migration to 1.5 will be easier on plugin
>> developers than the migration to 1.4 was...
> I agree that any changes we make in the near term should include early
> adoption of such a paradigm... This means we need to have a discussion
> of what it looks like to bring plugins into the fold of the SM config
> world, since they are currently all over the map. That's just something
> that I haven't heard tossed around yet - I don't have the energy at this
> moment to start it, but if no one else does in the next few days, I'll
> start thinking it over.
I haven't had a chance to look at the SM2 planning in abit, so forgive me
if this is already in there.
But I have one question about this... is this going to require plugin
developers to write their config scripts in perl so they can just be
included via the perl config? Or are will the config parse a file and
derive the config from that?
I personally think the first option is the best, but that requires the
plugin writer to know perl also. The second will take more coding, and
not be as flexable as the first.
One another simular subject, What I have been thinking about lately is a
cross between the administrator plugin and the configtest.php script
(which I like BTW) that will allow users to config SM for the first time
(can we say install script) without needing SSH access (which some ppl
don't have). It can easily autodetect alot of the necessary options, and
fill them in, allowing the user to change what he likes, save, and test.
It could also be setup to create the mysql tables, ect... for the user if
he wants database instead of file, ect... When it is installed to his
liking, he can click a button at the top of the config page to disable the
script from being ran, or to username/password it, ect...
Its an idea I have been kicking around for awhile now since a new host I
got doesn't allow ssh access (I just modified the administrator plugin to
allow me to config with being logged in) and have thought that SM needs a
I'll play with both ideas some and see what I can do,