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 http://www.toedter.com/blog/?p=80
An contacts demo startup animation with animated splash screen you find at http://www.toedter.com/download/e4/e4-animation.htm > In e4, we would need equivalent code in > org.eclipse.e4.ui.workbench.swt.internal.PartRenderingEngine.run(MAppli > cationElement, IEclipseContext) so that the model could be > created/initialized and > the GUI created all while displaying the splash and spinning the event > loop. 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... > AFAIK we will continue to use the splash handler (with enough > modifications to make it e4 friendly). But no one has looked at this > yet. As soon as there is something I could try, please let me know :) Best regards, Kai > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Paul Webster > Sent: Montag, 4. Januar 2010 14:15 > To: E4 Project developer mailing list > Subject: Re: [e4-dev] e4 + splah handlers + app life cycle > > On Mon, Dec 21, 2009 at 5:17 AM, Toedter, Kai <[email protected]> > wrote: > > Is there any hack that I could use right now to animate the splash > screen? As far I have debugged the code, the current splash screen is > displayed before the OSGi runtime starts and then not touched > anymore... > > In the 3.x world, we have code in a runUI() method that creates the > splash handler, an "init" thread that's allowed to post asyncExecs > that will run (more or less), and spins the event loop while > initializing the workbench in the init thread. > > In e4, we would need equivalent code in > org.eclipse.e4.ui.workbench.swt.internal.PartRenderingEngine.run(MAppli > cationElement, > IEclipseContext) so that the model could be created/initialized and > the GUI created all while displaying the splash and spinning the event > loop. > > AFAIK we will continue to use the splash handler (with enough > modifications to make it e4 friendly). But no one has looked at this > yet. > > 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
