Single Sourcing: Extend your RCP Application to the Web with RAP

Ralf Sternberg (Innoopract GmbH), Rüdiger Herrmann

Eclipse Platform - Runtime · Long - one hour
Wednesday, 10:10, 50 minutes | Room 206

Ralf Sternberg

Rüdiger Herrmann

Can I really make my RCP application work in a browser? The Rich Ajax Platform (RAP) was designed to bridge the gap between desktop- and web-development. To achieve this RAP reuses the RCP development model integrating the largest possible subset of the RCP-APIs.

In this talk we'll explore the differences between RAP and RCP that are especially relevant to the goal of single sourcing as much code as possible. We'll cover a range of techniques and basic patterns to close the gap between RCP and RAP, for both existing RCP applications and new RCP/RAP projects. We'll take a look at the roadmap for RAP as well as discussing possible steps for integrating the platform into e4.

Ralf is a member of the RAP development team at EclipseSource in Karlsruhe, Germany. Ralf's special focus is on the styling capabilities of RAP - he developed RAP's CSS theming subsystem and also contributes to CSS support in e4. His technical interests include agile development practices and programming languages, while his right brain loves typefaces, colors, and user interface design.

RÃ¼diger is a developer at EclipseSource and co-lead of the Rich Ajax Platform (RAP) Project.
As one of the initial committers on the RAP project, Ruediger was responsible for the development of RWT, the RAP side of SWT (Standard Widget Toolkit). His interests include promoting test driven development and using pair programming to optimize RAP development. Away from work you may find Ruediger jogging in Hamburg or touring in Latin America.