Eclipse Rich Ajax Platform

Eclipse RAPJUG Cologne, 5th October 2009 Fabian Lange

2 © 2009 codecentric GmbH Eclipse RAP

Agenda


Eclipse RAP

•Rich Ajax Platform•Created under the name W4T (WWWWindowingToolkit)

•Eclipse project since Ganymede release•Donated by Innoopract

•Maintained by EclipseSource•Strategic asset for Eclipse 4 (e4) currently in incubation


So what is it?

•SWT for the web


How does RAP do that?

•Interfaces!•The reason for using interfaces is that you can switch implementations

Operating System

OSGi

SWT

RCP

Application

RWT

•OSGi•RAP cheats and just claims to be the SWT layer

*architecture stack simplified


100%

•RAP is not 100% compatible with RCP•And most likely will not be

•RCP has design flaws preventing multiuser support•Workarounds exist, e4 will solve many issues

•Fail early concept•If it is not supported, it doesn’t compile

•Good news: 100% is often not required


History of RAP

•October 2007•1.0 release. First release to adhere to RCP/SWT APIs

•June 2008•1.1 release, part of Ganymede. Brings many APIs to par

•June 2009•1.2 release, part of Galileo. Improved stability and response times

•Today•Large quantities of RCP application code work on RAP


Agenda


Demo


Agenda


Light Side

•Migrate existing RCP applications•Depending on app, almost for free

•Develop Web Apps RCP Style•Reuse developer know-how

•Easily develop complex applications•Compared to traditional way of adding JavaScript widgets

•Some means of web styling•Web “compatible” themes


Dark Side

•Don’t build web sites•It is a pain in many aspects

•Heavy JavaScript•Slow, but browsers get better

•Differences between desktop and web•Loading and saving files, printing and similar

•RAP does not support all RCP features•Some key&mouse stuff, GraphicalContext

Eclipse Rich Ajax Platform

Technology

Transcript of Eclipse Rich Ajax Platform