An RCP application should declare a subclass of WorkbenchAdvisor and override methods to configure the workbench to suit the needs of the particular application.
The following advisor methods are called at strategic points in the workbench's lifecycle (all occur within the dynamic scope of the call to PlatformUI.createAndRunWorkbench):
initialize - called first; before any windows; use to register things
preStartup - called second; after initialize but before first window is opened; use to temporarily disable things during startup or restore
postStartup - called third; after first window is opened; use to reenable things temporarily disabled in previous step
postRestore - called after the workbench and its windows has been recreated from a previously saved state; use to adjust the restored workbench
preWindowOpen - called as each window is being opened; use to configure aspects of the window other than actions bars
fillActionBars - called after preWindowOpen to configure a window's action bars
postWindowRestore - called after a window has been recreated from a previously saved state; use to adjust the restored window
postWindowCreate - called after a window has been created, either from an initial state or from a restored state; used to adjust the window
openIntro - called immediately before a window is opened in order to create the introduction component, if any.
postWindowOpen - called after a window has been opened; use to hook window listeners, etc.
preWindowShellClose - called when a window's shell is closed by the user; use to pre-screen window closings
eventLoopException - called to handle the case where the event loop has crashed; use to inform the user that things are not well
eventLoopIdle - called when there are currently no more events to be processed; use to perform other work or to yield until new events enter the queue
preShutdown - called immediately prior to workbench shutdown before any windows have been closed; allows the advisor to veto the shutdown
postShutdown - called last; after event loop has terminated and all windows have been closed; use to deregister things registered during initialize
The following advisor methods are called at strategic points in the workbench's lifecycle (all occur within the dynamic scope of the call to PlatformUI.createAndRunWorkbench):
initialize - called first; before any windows; use to register things
preStartup - called second; after initialize but before first window is opened; use to temporarily disable things during startup or restore
postStartup - called third; after first window is opened; use to reenable things temporarily disabled in previous step
postRestore - called after the workbench and its windows has been recreated from a previously saved state; use to adjust the restored workbench
preWindowOpen - called as each window is being opened; use to configure aspects of the window other than actions bars
fillActionBars - called after preWindowOpen to configure a window's action bars
postWindowRestore - called after a window has been recreated from a previously saved state; use to adjust the restored window
postWindowCreate - called after a window has been created, either from an initial state or from a restored state; used to adjust the window
openIntro - called immediately before a window is opened in order to create the introduction component, if any.
postWindowOpen - called after a window has been opened; use to hook window listeners, etc.
preWindowShellClose - called when a window's shell is closed by the user; use to pre-screen window closings
eventLoopException - called to handle the case where the event loop has crashed; use to inform the user that things are not well
eventLoopIdle - called when there are currently no more events to be processed; use to perform other work or to yield until new events enter the queue
preShutdown - called immediately prior to workbench shutdown before any windows have been closed; allows the advisor to veto the shutdown
postShutdown - called last; after event loop has terminated and all windows have been closed; use to deregister things registered during initialize
扫一扫
407
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
