[pLog-general] Your thoughts on 1.1

[Oscar Renalias]

all these features look interesting, but I am afraid that we are going
to cross the border that separates a CMS from a blogging tool if we
implement them. Moreover, most of them would require complete
reengineering of the whole plugin subsystem once again.

These ideas should be broken down into smaller milestones and be
implemented in different releases (because my goal is still to shorten
the development cycle and make incremental releases every so often
instead of big ones)

Oscar

On 4/15/05, Benjamin Krause <ork at orkland.de> wrote:
> 
> well.. i'd better read my email once again before sending :)
> 
> > - create a new page called 'plugin management' in the administration. on
> >   this page the admin can add new plugins (maybe even upload them as a
> >   zip file) and control wheter a plugin is:
> >   - active (must have for all blogs)
> >   - active (optional for each blog)
> >   - disabled
> >   i guess this might be done with a table view and a drop down on each
> >   plugin row. the admin should see what plugin is installed and what
> >   state each plugin is in right away.
> 
> the admin cannot change any plugin setting there.. the plugin still adds
> new menu entries whereever it wants to.
> 
> > - change the plugin centre in control centre so the blog owner gets a
> >   list of all active (must have and optional) plugins. we should have a
> >   table of all plugins and a checkbox in each row to enable/disable each
> >   optional plugin. all mandatory plugins are displayed but not
> >   checkable.
> >
> > - store a array containing all plugins in the blogSettings. so
> >   each blog has an array containing the wanted plugins.
> 
> of course the array contains just the active (mandatory or optional)
> plugins.
> 
> > - blogview, change the plugin manager to load only those plugins really
> >   needed by the current blog. this will save time if you have a lot of
> >   plugins installed. the plugin manager must still load all plugins if
> >   in the admin panel.
> 
> not correct.. the 'plugin administration' must load all plugins. the
> admin panel itself will only load all active plugins for the current
> blog (the one choosen at the dashboard). however we need an array
> containing all plugins (name, desc) somewhere (cacheable) so the blow
> owner can see information about disabled plugins, but the plugin itself
> must not be loaded (and therefore does not add menu entries if not
> neccessary).
> 
> > now we get these new cool features:
> > - admin might install plugins that are mandatory for each blog and no
> >   blogowner can disable them. (e.g. the authimage plugin)
> > - each blog owner can decide what plugin to use and can manage this
> >   setting quite easily in a table.
> > - the general loading time might be drastically decreased if you have a
> >   lot of plugins installed.
> >
> > Ben
> >
> >
> >
> > _______________________________________________
> > pLog-general mailing list
> > pLog-general at devel.plogworld.net
> > http://devel.plogworld.net/mailman/listinfo/plog-general
> 
> _______________________________________________
> pLog-general mailing list
> pLog-general at devel.plogworld.net
> http://devel.plogworld.net/mailman/listinfo/plog-general
>