The "One Laptop Per Child" project has a great device ready to ship, but there's no Java on there. Let's think about working together to put Java on OLPC!
Re: Getting started with Eclipse plug-ins: understanding extension points
Alex,
On the off chance you're still paying attention to this thread, I have a question for you.
I understand your example and it seems to make sense. I've created a basic plugin like your example and when I place it in my Eclipse plugins directory and restart, I get the new menubar item. My question has to do with the sentence "The Eclipse toolbar listens out for such extension installation,". If I place this same plugin in a "hello world" app, the menu doesn't show up. Is this because the app isn't "listening for extension installations"?
Any idea on what I would need to do to make an independent app (not the Eclipse workbench), understand a new plugin is available and it needs to display a menu bar item? I've read your next article and that seems to address extension points for your own plugins. Maybe its the same thing but I was thinking the workbench automatically listens for basic things -- like your USB hub example.
Re: Getting started with Eclipse plug-ins: understanding extension points
I suspect this is coded into the Workbench UI plug-in. So your choices would be to use the workbench UI, or (if that's not desirable) create your own mechanism for listening out for changes to the action sets property by registering an extension point registry listener.
Re: Getting started with Eclipse plug-ins: understanding extension points
Alex,On the off chance you're still paying attention to this thread, I have a question for you.
I understand your example and it seems to make sense. I've created a basic plugin like your example and when I place it in my Eclipse plugins directory and restart, I get the new menubar item. My question has to do with the sentence "The Eclipse toolbar listens out for such extension installation,". If I place this same plugin in a "hello world" app, the menu doesn't show up. Is this because the app isn't "listening for extension installations"?
Any idea on what I would need to do to make an independent app (not the Eclipse workbench), understand a new plugin is available and it needs to display a menu bar item? I've read your next article and that seems to address extension points for your own plugins. Maybe its the same thing but I was thinking the workbench automatically listens for basic things -- like your USB hub example.
Re: Getting started with Eclipse plug-ins: understanding extension points
How could one then get the action programmatically in order to its properties?Re: Getting started with Eclipse plug-ins: understanding extension points
I suspect this is coded into the Workbench UI plug-in. So your choices would be to use the workbench UI, or (if that's not desirable) create your own mechanism for listening out for changes to the action sets property by registering an extension point registry listener.Alex
Re: Getting started with Eclipse plug-ins: understanding extension points
In order to its properties? I think you're missing a verb ...You can query the actions by iterating through the actionSets extension points
Alex