Re: metadatabase

On Tue, 2003-10-14 at 14:32, Andreas Rottmann wrote:
> >
> I'd even go as far as not loading the metadatabase _plugin_, if the UI
> (or other code) doesn't use it. I guess however, that we would
> eventually need a real plugin manager for that.

I think we've had this conversation before.. but
how about a rehash:

1. Current plugin system loads everything all the time (blech)
    and should be redone.

2. A new plugin system should load only the needed plugins possible on  
   demand.  (jeesh...almost like a shared library)

3. New Plugins need to support C++ , have versions checking, etc
   
4. Several plugins now have internal code that only tests if the plugin
   is applicable to the call (true for metadata plugins).   Does the    
   plugin manager need some sort or rule or test case to determine
   which plugins should be loaded or should this be left to the
   plugin user?  If the second option is correct, then how does
   the plugin user know which plugins to load (back to case 1).

I would like to see a c++ plugin manager
that operates using autoload functionality maybe using 
delegation.    Something like a really smart pointer 
that when used in call automatically loads the plugin
(if not already loaded) and forwards the call.

Similarly,  it would nice to have some plugin code outside
the plugin for rule testing..

Something like 
InfraredPlugin.ui : if (infrared library available) 
                      autoload (InfraredPlugin.in)

In order to keep down the errors we see when loading plugins.
   


-- 
email:[email protected] office:(805)893-4276 http://www.cs.ucsb.edu/~kris



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php