[eboxy-users] plugin suggestion
Status: Alpha
Brought to you by:
bluelightning
From: <re...@ch...> - 2003-12-30 07:53:46
|
Hi, While working with eboxy, and at the same time hacking it, I found the plugin system was great but still quite hard to configure. Indeed, the way it currently works, one must install every plugin in the /usr/local/lib/eboxy/, which roughly means "system-wide" and "one plugin name per computer". Why not just allow the eboxy.xml to provide the location to it? Something like: <plugin module="filebrowser" location="./lib/libfilebrowser.so"> <pluginobject name="filebrowser"> </pluginobject> </plugin> It would be really convenient, for the user who can reference a particular version of the plugin, but also for the developer (who can reference the plugin they want to test without installing it on the system). Making such "ref" attribute optional wouldn't break compatibility. It may also be useful to do the same for the interface plugin: let the eboxy.xml provide (optionnally) the location of the interface library (so that you may remove the hardcoded path in [devel-0-4-0]interfacemanager.cpp ;-)) Rodrigo |