Multiple plugin directories

[yermol]

Loading plugins from multiple separate plugins directories would be very useful; possibly using an optional directory parameter on the loadPlugin method. (does javascript support that kind of thing?)

[mokhet]

i cant see why it would be usefull. There is a plugin structure, it can be discussed, but what can be the benefits to load a plugin from another directoy ?

[gogo]

Moving to yermo's version.

[guest]

Hi there, I would love to see a feature like "configurable plugin directories". Hence it could be possible to write custom plugins AND keep them separate from the official plugins.

E.g. in my project I need a special plugin to insert links (e.g, to select links from a sitemap, also my links have special URL parameter etc.). I simply could create a MyLink?-plugin in the Xinha plugins folder. Still, this would mix project specific code with general code. Therefore, updating the Xinha installation be difficult.

I would prefere to have a Xinha installation in folder A and my project stuff in folder B with the plugin folder: B/myplugin. Then use HTMLArea-Config Object to say something like:

var cfg = new HTMLArea.Config();
cfg.addPluginDir( "coolProject", "B/myplugin" );

var plugins = [
  "HtmlTidy", // official plugin
  "coolProject/MyPlugin", // plugin located in "B/plugin"
  "coolProject/Another" 
];

// add plugins and initialize editor

AFAIK this would effect the following functions/methods:

HTMLArea.getPluginDir
HTMLArea.prototype.imgURL
HTMLArea.prototype.popupURL
HTMLArea.prototype._loadlang

regards, gERD

gerd (at) php-tools (dot) net

[ray]

#1195