Comments on: NetBeans Module Automatic Unload http://pronetbeans.com/archives/43 The source for learning NetBeans. Wed, 20 Aug 2008 11:24:45 +0000 http://wordpress.org/?v=2.3.3 By: Adam Myatt http://pronetbeans.com/archives/43#comment-719 Adam Myatt Mon, 12 May 2008 01:51:11 +0000 http://pronetbeans.com/archives/43#comment-719 I was really just talking out loud and hoping. The Feature on Demand seems decent as it has already been developed (even though Geertjan made clear it is a tentative feature, and certainly not locked in stone - definitely an experiment). The automatic module unload capability is just wishful thinking (if it makes sense). We'll see what happens. I was really just talking out loud and hoping. The Feature on Demand seems decent as it has already been developed (even though Geertjan made clear it is a tentative feature, and certainly not locked in stone - definitely an experiment). The automatic module unload capability is just wishful thinking (if it makes sense). We’ll see what happens.

]]> By: wadechandler http://pronetbeans.com/archives/43#comment-718 wadechandler Sat, 10 May 2008 12:24:37 +0000 http://pronetbeans.com/archives/43#comment-718 Well, I guess my last comment is mute as there are proxy modules being installed which technically any object should be able to be loaded from, I suppose they are detailing top level menus as any standard way of creating an action from the layer should be able to work. I think I'll just wait for more documentation on what is being worked on :-D Well, I guess my last comment is mute as there are proxy modules being installed which technically any object should be able to be loaded from, I suppose they are detailing top level menus as any standard way of creating an action from the layer should be able to work. I think I’ll just wait for more documentation on what is being worked on :-D

]]> By: wadechandler http://pronetbeans.com/archives/43#comment-717 wadechandler Sat, 10 May 2008 12:11:02 +0000 http://pronetbeans.com/archives/43#comment-717 I noticed in Geertjan's blog there are new layer entries for support etc. This goes further than the Wiki document. That looks more like what I was talking about, so it seems it is to the point that modules may subscribe to feature on demand. The only thing I wonder is if the design will/does support any type of action. Some NB actions provide popup menus etc. I note the Wiki document details only for top level menu items, but as you noted it is still under design and in the process of being worked out. Maybe they have some new ideas which haven't made it into the Wiki page such as allowing a module to provide a JavaFX script chunk for the menu or something along those lines. That would allow more complex proxy menus before the real classes get loaded. Anyways, I'm looking forward to studying it deeper. I wasn't aware it had progressed further than what is on the Wiki page. I noticed in Geertjan’s blog there are new layer entries for support etc. This goes further than the Wiki document. That looks more like what I was talking about, so it seems it is to the point that modules may subscribe to feature on demand. The only thing I wonder is if the design will/does support any type of action. Some NB actions provide popup menus etc. I note the Wiki document details only for top level menu items, but as you noted it is still under design and in the process of being worked out. Maybe they have some new ideas which haven’t made it into the Wiki page such as allowing a module to provide a JavaFX script chunk for the menu or something along those lines. That would allow more complex proxy menus before the real classes get loaded. Anyways, I’m looking forward to studying it deeper. I wasn’t aware it had progressed further than what is on the Wiki page.

]]> By: wadechandler http://pronetbeans.com/archives/43#comment-716 wadechandler Sat, 10 May 2008 11:54:20 +0000 http://pronetbeans.com/archives/43#comment-716 The only problem I see is that modules really need to be subscribers to on-demand. There needs to be a new set of manifest entries/keys which tell the module system a module either subscribes or it does not, but yes this would be a good idea. The reason one needs to subscribe is all of the actions will need to be available some how, and those actions classpaths will need to be available. It seems along with subscribing a new model is needed to support modules overall in the on demand features so that specifics of the classpath may be left loaded in memory while others are left out until needed or that in the layer.xml a module may define actions and other UI information which may be provided for the user so they may enter into specific actions without the full module really being loaded. For instance, if a modules only user interface entry point is an action, then if it is deactivated it won't show up for a user, and they'll never be able to use it without first manually activating it. So, definitely would be good, but will take more thought and resources than is in the current design of the on demand features, and it would need to be a system wide design outside of just the UI gestures module. The only problem I see is that modules really need to be subscribers to on-demand. There needs to be a new set of manifest entries/keys which tell the module system a module either subscribes or it does not, but yes this would be a good idea.

The reason one needs to subscribe is all of the actions will need to be available some how, and those actions classpaths will need to be available. It seems along with subscribing a new model is needed to support modules overall in the on demand features so that specifics of the classpath may be left loaded in memory while others are left out until needed or that in the layer.xml a module may define actions and other UI information which may be provided for the user so they may enter into specific actions without the full module really being loaded.

For instance, if a modules only user interface entry point is an action, then if it is deactivated it won’t show up for a user, and they’ll never be able to use it without first manually activating it.

So, definitely would be good, but will take more thought and resources than is in the current design of the on demand features, and it would need to be a system wide design outside of just the UI gestures module.

]]>