[news.eclipse.rt.riena] Re: RAP Support

[Aleksander Bandelj <aleksander.bandelj@xxxxxxxxxx>]

I am currently working on Riena/RAP and my current approach is to fork 
*.ui.swt bundles into *.ui.rap bundles (still connected to CVS, but will 
be tiresome to update). Bare basics seem to work after few hours hacking 
off PaintListeners, GCs and similar incompatibilites. It would be nice 
if all this painting and lnf stuff would be in separate bundle ;)

Longer term, I would structure bundles into *.ui.swt which would only 
use SWT API covered by RAP and interfaces for stuff which has different 
API, *.ui.rcp for full RCP implementation and *.ui.rap for RAP 
implementation.

-a

Hasan Ceylan wrote:
> Hello,
>
> I have just started to browse the riena project and I think I see a 
> lot of future use of the functionalities. Good work, congrats.
>
> This must be somewhere that might have been asked or written but I'll 
> ask anyway...
>
> It has been said that the "RAP and Riena are to become top projects 
> and interoperability between the projects will be a must".
>
> What is the status of this statement. We are developing an RCP 
> Application with the following technologies
> * RCP
> * RAP
> * Databinding
> * EMF
> * EMF Databinding
> * CDO
> * Teneo
> * Hibernate
>
> The main objective is to provide a SOA datacentric application for 
> both web and desktop users.
>
> Should I spend sometime learing riena or do I need for the next 
> project to add Riena in list of technologies above?
>
> Regards,
> Hasan Ceylan