Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 255513

Summary: Provide for exchangeable client implementation
Product: [RT] RAP Reporter: Ralf Sternberg <rsternberg>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: elias, jboehme, mknauer, mpost
Version: 1.4Keywords: plan
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: plan-version=1.4 plan-theme=other-clients plan-status=committed
Bug Depends on: 252159, 255514, 390435    
Bug Blocks:    

Description Ralf Sternberg CLA 2008-11-17 09:34:23 EST 
RAP should provide support for alternative client-side technologies.

In order to exchange the qx version, RAP already introduced an rwt.q07 fragment that contains LCAs and the Javascript files. However, this is not sufficient for a clean separation that would allow to use a completely different client-side technology.

This work will requires different sub-tasks, e.g. splitting several sub-systems and then moving them to the fragment. Those sub-tasks will be covered by separate bugs.

Our current approach is to use a single class as interface between host and fragment for all subsystems. This class is preliminary and is meant to be refactored after the general split has been accomplished.
Comment 1 Ralf Sternberg CLA 2011-12-23 05:36:09 EST 
Even though the context of this request has changed with the progress on bug 311355, there are still a couple of issues with regard to support of alternative clients such as
- exchangeable layout calculation (theme adapters, coputeSize, etc),
- some kind of pluggable bootstrapping,
- identifying and handling different clients

I'll keep this bug open as an umbrella.
Comment 2 Ivan Furnadjiev CLA 2018-01-30 05:29:09 EST 
Most of the topics are already implemented together with Tabris for RAP.