On 14.04.2012 17:47, Landon Blake wrote: > OK. > > If I remember correctly the plug-in interface has a initialize and an > execute method.
exactly >The problem may not be in the design of JUMP, but in > the design of the offending plug-ins. that's one way to look at it. another would be to say that most plugins essentially do their initialization in initialize(), which can be quit extensive especially if they themselves have to find their extensions e.g. sextante. execute() obviously is not the place to do it as this is called by the gui when the menu entry is selected. users expect prompt answer here. >Really, plug-ins should do as > little as possible in initialize and as much as possible in execute. well they should, which essentially means they don't necessarily do so. because the development of extensions is decentralized modifying all extensions is essentially impossible. showing workbench and keep on initializing would be a workaround. > Not sure if that is the problem, but it is a thought. In that sense, > OJ is already design for lazy loading. as laid out above, no it isn't ;) ..ede ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
