Eclipse Community Forums: Remote Application Platform (RAP) » Plans for the rendering engine on 2.0

Help

Home

Home » Eclipse Projects » Remote Application Platform (RAP) » Plans for the rendering engine on 2.0

Show: Today's Messages :: Show Polls :: Message Navigator

Plans for the rendering engine on 2.0 [message #952388]

Sun, 21 October 2012 12:13

Thomas Kratz

Messages: 165
Registered: July 2009

Senior Member

Hi RAP folks,

I just followed that there are plans to run 2.0 on e4 with a rwt renderer. As I had a hell of a time with the branding api (I found it impossible, at least in a day to make the TabbedStackPresentation work with my own factory, but I don't know the reasons why you choose this un-mixable implementation). So if you could confirm the e4 plans, I wouldn't invest in the branding api and go for the renderer instead. If there are otherwise plans to move the branding api on top of the renderer, it would be great to make it a little more flexible (for e.g. not bind the config action to ConfigurableStack as it may not be needed, implement workbenchpresentationfactory on top of the branding api).

Regards
Thomas

Report message to a moderator

Re: Plans for the rendering engine on 2.0 [message #954825 is a reply to message #952388]

Tue, 23 October 2012 09:24

Ralf Sternberg

Messages: 1313
Registered: July 2009

Senior Member

Hi Thomas,

There are currently no plans at EclipseSource to develop an E4 renderer
for RAP. But we are happy to support everyone who starts this work.

However, during our evaluations of E4 on RAP, we found that the E4
workbench is not yet fully decoupled from SWT. That means that at the
moment, there's more to it than just writing a renderer for RAP. Parts
of the workbench would also have to be ported. But there are efforts in
the E4 project towards a better decoupling [1].

There are also still a couple of issues in E4 that make it unusable in a
multi-user environment in its current state [2]. Once these issues are
resolved, providing a RAP renderer will be rather easy.

You're not the only one who struggles with the presentation API. I also
wouldn't like to invest in it anymore, as the 3.x workbench is
definitely dead end - there is no further development taking place.

I don't know if this is an alternative for you, but many users decided
to get rid of the workbench and write their application in plain SWT and
JFace, which also results in more lightweight applications.

Best regards,
Ralf

[1] e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=384843
[2] such as bug 309868, bug 385394, bug 283255

--
Ralf Sternberg

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/

Report message to a moderator

Previous Topic:	Custom Widget Ids for Widgets supplied by Extensions (Menu, Toolbar)
Next Topic:	RWT/RAP API documentation not accessible from RAP website

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Jan 26 09:51:02 GMT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter