Org. Eclipse. UI. startup

By default, the Eclipse plug-in is lazy start, that is, only when the plug-in functions are actually called (such as opening the view in the plug-in or clicking the global menu of the plug-in ), the plug-in will be started (execute the start method of the lifecycle ).

The Org. Eclipse. UI. startup extension may be one of the APIs that have been controversial in version 2.0.
It indicates the plug-in to be started when eclipse is loaded. That is, when a plug-in has a class to implement the org. Eclipse. UI. startup extension point,
The startup plug-in is activated when eclipse is started (when the workbench window is opened), without the restriction of the delayed loading policy.

 

Execution sequence:

Execute the start method of the plug-in class --- execute the earlystartup method of the class that implements the istartup Interface

Extended point attributes:
Point-standard identifier of the target extension point (Org. Eclipse. UI. startup)
ID-an optional identifier of the extended instance.
Name-optional name of the extenextended instance.
Class-standard name of the class implementing org. Eclipse. UI. istartup. If this item is not specified, the plug-in class is used.
Do not specify a plug-in class as an explicit value; otherwise, it will be instantiated twice (one by the conventional plug-in activation operation, one by this mechanism ). This is a note.

 

Examples in plugin. xml
<Extension
Id = "hellorcp. Start. startup"
Name = "hellorcp. Start. startup"
Point = "org. Eclipse. UI. startup">
<Startup class = "hellorcp. Start. startup"> </startup>
</Extension>