We'd have to ensure that we continue to support the 'headless' operations. Right now we leave it up to the rendering engine to perform platform specific operations (like spinning the SWT event loop). We could add an 'isHeadless method to E4Application fairly easily I think.
There will have to be some sort of start up life cycle in any case; we need some formalized location for folks to hook into in order to have a cut at manipulating the model; see https://bugs.eclipse.org/bugs/show_bug.cgi?id=296478 comments 21 & 23. Eric From: Paul Webster <[email protected]> To: E4 Project developer mailing list <[email protected]> Date: 01/04/2010 09:36 AM Subject: Re: [e4-dev] e4 + splah handlers + app life cycle Sent by: [email protected] On Mon, Jan 4, 2010 at 9:18 AM, Toedter, Kai <[email protected]> wrote: > Paul, > > I just started experimenting with Trident and animated splash screens. Just for a proof of concept, I modified the startup of the E4Application a bit. More details you find a blog entry Thanx for having a look at this. > Since the splash handler should be invoked as early as possible, probably E4Application would be a better place. It would also be possible to make the API render engine independent. Another way would be to create the render engine at the very beginning of the lifecycle rather than after loading the model... It might have to be the second option ... the rendering engine determines what windowing toolkit is used, and so it must handle (in our case) all of the SWT operations. If we determine the hooks for starting and stopping the splash screen, E4Application could call out to the renderer right at the beginning of its initialization (I think). PW -- Paul Webster Hi floor. Make me a sammich! - GIR _______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
