Re: [e4-dev] (My) Working areas for 4.3

[Mike Wilson <Mike_Wilson@xxxxxxxxxx>]

> The other solution is to write an SWT port which use JavaFX as the
> rendering technology which is also a big task.
>
I asked Steve Northover (who is working JavaFX now) about this at one point. He seemed to think it was doable.

I'd guess one person for six months would get you an initial port, and then another year or so of tuning/tweaking to make it real.

McQ.

Tom Schindl ---08/06/2012 09:03:24 AM---That's exactly what e(fx)clipse does. It uses JavaFX all over while this is a good approach for RCP-

From: Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>
To: e4-dev@xxxxxxxxxxx,
Date: 08/06/2012 09:03 AM
Subject: Re: [e4-dev] (My) Working areas for 4.3
Sent by: e4-dev-bounces@xxxxxxxxxxx

---

That's exactly what e(fx)clipse does. It uses JavaFX all over while this
is a good approach for RCP-Applications it is not practical for the
Eclipse IDE because you'd have to rewrite all and everything which is a
very very huge task.

The other solution is to write an SWT port which use JavaFX as the
rendering technology which is also a big task.

Tom

Am 06.08.12 04:33, schrieb Ivan Ooi:
> Nice! May I share some ideas ?
> 
> Since SWT do not have any plans on multi touch, gesture, animation and
> all that. Why not utilize JavaFX ? 
> Since JavaFX support SWT quite well ( I guess )
> 
> Best Regards,
> Ivan
> 
> On Thu, Jul 12, 2012 at 6:25 PM, Tom Schindl
> <tom.schindl@xxxxxxxxxxxxxxx <mailto:tom.schindl@xxxxxxxxxxxxxxx>> wrote:
> 
>     Hi,
> 
>     Now that we got 4.2 out I'd like to share what I plan to work on in the
>     4.3 timeframe.
> 
>     Prio 1:
>     -------
>     * Native Editor Support in EAP
>     * JavaFX2 rendering engine (not part of e4 project but my own
>       e(fx)clipse project)
> 
> 
>     Prior 2:
>     --------
>     * Dynamic language switching for EAP
>       => no static translation resolving via NLS (also important for
>          multi-user envs like RAP)
>     * Allowing to nest an MSashContainer in an MPartStack (378298)
>       => Not sure though if an MSashContainer is a good idea because then
>          one can there once more nest a stack, do we want that?
>       => this will most likely fix 8009
>     * XPath for contributing and querying
> 
> 
>     Things I'd consider important too but I don't plan to work on:
>     * Improving the e4 bridge
>     * enable e4 programming model for IDE dev (maybe needs e4 bridge)
>     * refactor code to natively run on e4
>       * common navigator?
>       * preferences?
>       * ui.dialogs?
>     * e4xmi-Tooling
> 
>     Do we have a call today?
> 
>     Tom
> 
>     --
>     B e s t S o l u t i o n . a t                        EDV Systemhaus GmbH
>     ------------------------------------------------------------------------
>     tom schindl                 geschäftsführer/CEO
>     ------------------------------------------------------------------------
>     eduard-bodem-gasse 5-7/1   A-6020 innsbruck     fax      ++43 512
>     935833 <tel:%2B%2B43%20512%20935833>
>     http://www.BestSolution.at                      phone    ++43 512
>     935834 <tel:%2B%2B43%20512%20935834>
> 
>     _______________________________________________
>     e4-dev mailing list
>     e4-dev@xxxxxxxxxxx <mailto:e4-dev@xxxxxxxxxxx>
>     https://dev.eclipse.org/mailman/listinfo/e4-dev
> 
> 
> 
> 
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev
> 


-- 
B e s t S o l u t i o n . a t                        EDV Systemhaus GmbH
------------------------------------------------------------------------
tom schindl                 geschäftsführer/CEO
------------------------------------------------------------------------
eduard-bodem-gasse 5-7/1   A-6020 innsbruck     fax      ++43 512 935833
http://www.BestSolution.at                      phone    ++43 512 935834
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev