Opened 14 years ago

Closed 14 years ago

#115 closed New Feature (invalid)

Use PluginsPath for each plugin

Reported by: Alfonso Martínez de Lizarrondo Owned by: Alfonso Martínez de Lizarrondo
Priority: Normal Milestone:
Component: General Version:
Keywords: Cc:


Now the PluginsPath configuration setting is used only once at the end of the parsing, so if you want to load plugins from different sources you have to be sure that each one has specifed the path at load time:

FCKConfig.PluginsPath = FCKConfig.BasePath + 'plugins/' ;

FCKConfig.Plugins.Add( 'autogrow' ) ;

// Non standard plugins
FCKConfig.Plugins.Add( 'rtSpellCheck', '', '/customPlugins/' ) ;

but it would seem more logical to be able to change the PluginsPath and so the next plugins will load from that path:

FCKConfig.PluginsPath = FCKConfig.BasePath + 'plugins/' ;

FCKConfig.Plugins.Add( 'autogrow' ) ;

// Non standard plugins
FCKConfig.PluginsPath = '/customPlugins/' ;

FCKConfig.Plugins.Add( 'rtSpellCheck' ) ;

I've checked the code in [149] so it can be discussed and reviewed before it gets added to the trunk.

Change History (2)

comment:1 Changed 14 years ago by Frederico Caldeira Knabben

I'm not sure the proposal is still a clear solution. The fact is that PluginsPath is a configuration option. It is quite strange to change it many times in the configuration file, expecting it to change the behavior of subsequent calls to the Add method.

Actually, it is not possible to know how Add works behind the scene, so one can't be sure that PluginsPath will be used at the right moment of the Add call, or after the entire configuration file is processed.

In any case, you are right to say that the current plugin loading system has room for improvements. I think we could come with something for the 3.0. Maybe simply indicating the full path for the plugin folder would be enough, instead of using base paths and plugin names. It would be a simpler and clearer solution.

I would vote to close this ticket and write some documentation at wiki:Components/Plugins? regarding it, so we can work on the definitions first.

comment:2 Changed 14 years ago by Alfonso Martínez de Lizarrondo

Resolution: invalid
Status: newclosed

I don't really know how to write the spec for the Plugins page, but now I see that this patch wasn't really needed (as each plugin can specify its path and that's probably a better long term solution), so I'm closing this bug and reverting the changes in my branch.

Note: See TracTickets for help on using tickets.
© 2003 – 2020 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy