[news.eclipse.platform] Re: Load my plugin at startup in particular orde

[Paul Webster <pwebster@xxxxxxxxxx>]

You need to do some auth ... and interact with the user (as in request a 
 password) or simply do calculations?  Are you an RCP app or a plugin?

For an RCP app that needs to do something (like check a license) you can 
set the startlevel for that plugin to start before most of the workbench 
(but after OSGi) and do your calculations.  Split out the auth part from 
the UI part, so the UI part happens later.

If you need to open some kind of login dialog (user/password) consider 
doing it in the Splash screen ... there are already examples of this.

There's also the option of using http://eclipse-jaas.sourceforge.net/ 
which I believe performs some authentication and then can prevent 
plugins from loading (or control them).

If you are simply an eclipse plugin that expects to run in the SDK (IDE) 
then you are limited in what you can do.

For non-ui license checking, you might still be able to specify your 
start level.  You won't have access to the splash screen, and you would 
have to check eclipse-jaas to see what it supports in an IDE environment 
(where you don't control the application or product yourself).

org.eclipse.ui.startup will start your plugin in a non-UI thread after 
the workbench has been initialized, so it's common to use an 
asyncExec(*) or UIJob(preferred) to post your actions to the UI thread. 
 The startup will be in no particular order, and almost always after 
many of the standard components (CDT, JDT) have started.

Later,
PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/workbench.htm