RE: [FR-devel] Plugin dependencies proposal

[Rich Kilmer]

Appreciate the thoughts...the startup time is exactly why I am
refactoring.  Right now all plugins registered to do so load and run at
startup (but they don't necessarily display/perform processing).  The
way I originally implemented it was WAY to slow (too many messages) and
I am working on optimizing it.  Be done soon.

BTW:  I will send the Ripper stuff to you.

-rich

> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden On Behalf Of Ian MacLean
> Sent: Wednesday, November 06, 2002 1:44 PM
> To: address@hidden
> Subject: Re: [FR-devel] Plugin dependencies proposal
> 
> 
> Curt Hibbs wrote:
> 
> >Rich Kilmer wrote:
> >  
> >
> >>Team,
> >>
> >>Our current dependency management is being revamped.  The 
> problem that 
> >>Laurent and I observed last weekend was caused because of 
> the way that 
> >>the dependencies were being managed...specifically there was a race 
> >>condition that was intermittent...which sucks.  The other thing I 
> >>noticed upon analysis is that we send over 2000 
> notifications between 
> >>plugins when they are coming up.  This is WAY to many.  We have 29 
> >>plugins...imagine what will happen when we have one or two 
> hundred...
> >>
> >>    
> >>
> Somthing else worth considering is cumulative startup time of 
> plugins. 
> As it stands are all plugins loaded at startup ? will startup 
> time grow 
> linearly with the number of plugins added ? By way of 
> comparism - in the 
> VS.Net plugin architecture absolutely everything is delay 
> loaded so that 
> the class browser plugin is loaded only when you ask to see it.  Of 
> course with cascading dependencies you may end up loading everything 
> anyway - just somthing to consider.
> 
> Ian
> 
> 
> 
> _______________________________________________
> Freeride-devel mailing list
> address@hidden 
> http://mail.nongnu.org/mailman/listinfo/freeri> de-devel
>