Re: [ jEdit-users ] Plugin Load on demand

[Slava P. <sl...@je...>]

Hi,

jEdit 4.2 does this once a plugin is updated for the jEdit 4.2 plugin
API. For many plugins -- eg FTP and XML (latest versions in CVS); the
JAR file is not even opened until the first time you access a feature of
that plugin (opening an FTP site, or an XML file). This is done using a
cache system. Reading the cache for all plugins on plugin central only
takes half a second or so on my system; so once the majority of plugins
are updated for the new API, we will see major startup speed increases.

On Fri, May 30, 2003 at 11:27:30AM +0200, Max wrote:
> Hello,
> 
> To my understanding every plugin which is installed is loaded when jedit 
> is being started. And this extends the startup time.
> 
> Would it be possible to have all installed plugins listed as usual in 
> the menus but only load if they are flagged to be loaded at init ?
> 
> Other plugins which are not loaded at init shall still be in the plugin 
> menu but may be loaded only when the user explicitly demands the load. 
> For example each plugin may have a menu item like "load this plugin". 
> One problematic issue could be that some plugins may need to do some 
> work during init. However plugins can identify themselves as plugins 
> "which can loaded at init only" or "anytime".
> 
> Currently my problem is that there are some plugins which are rarely 
> used but when I need to use them I need to install the plugin and 
> restart jedit. And after using I need to remove them again.
> 
> Just some ideas.
-- 
Slava Pestov