|Re: Workbench Eventing [message #994958 is a reply to message #994954]
||Fri, 28 December 2012 13:24
| Thomas Schindl
Registered: July 2009
Events are not the correct solution because you can not cancel them! We
already have some events in the bootstrap process called lifecycle
hooks, all we need to make them accept a return value.
There's another more bug in the system assigned to me where we add more
lifecycle to other areas like MApplication, MWindow, MPerspective, ... .
The problem is that we have to invent so many annotations for those
lifecycle callbacks that I suggested in a discussion at e4-dev to have a
way to add a value to a constant (you can look up them up in the archive).
Am 28.12.12 19:12, schrieb Joseph Carroll:
> I would like to display a login screen before the workbench is rendered.
> The login screen should be able to stop the workbench from launching if
> login fails. I would also like to initialize an activity monitor that
> logs the user out if they have been inactive for x amount of time by
> installing filters on the display.
> After reviewing several forum discussions, I have not been able to find
> a suitable way to accomplish this. So I wanted to get feedback on
> creating workbench events, specifically tied to the workbench life
> cycle. I created an enhancement request
> (http://bugs.eclipse.org/bugs/show_bug.cgi?id=397223) with a proposed
> The solution allows an opportunity to utilize the complete workbench
> context (including the display) and shutdown the workbench before the
> rendering engine is started. Currently, I can display the login screen
> using the traditional life-cycle hooks, however there isn't a way to
> stop the workbench from rendering.
> By publishing events from the workbench, I can initialize resources
> before the workbench is rendered (like login and monitoring) and tear
> down those resources when the workbench is stopped.
> I am certainly open to feedback and alternative ways of accomplishing this.
Powered by FUDForum
. Page generated in 0.01427 seconds