AW: [riena-dev] Committed - Navigation on RAP (1st step)

["Liebig, Stefan" <Stefan.Liebig@xxxxxxxxxxxx>]

Hi Elias,

This is really great! The RAPified Riena app is really impressive.

As far as I understand there are several facades which handle the RAP/RCP specific implementations. Those facades use the FacadeFactory to create the specifc facades.
Currently, the FacadeFactory is in the bundle org.eclipse.riena.ui.swt because it has a dependency to SWT (it uses SWT.getPlatform() to discriminate). This is the only "thing" that stops it from being moved e.g. to riena.core.
I assume that we could use the FacadeFactory also for non-UI stuff like the navigation model. So, another home for it would be nice.
Within riena.core we have a ContainerModel that can tell whether the code is running on the server or the client side. I wonder whether we could just use this (or some other mechanism) to discriminate between RAP/RCP?

What do you think?

Tschüß,
Stefan

> -----Ursprüngliche Nachricht-----
> Von: riena-dev-bounces@xxxxxxxxxxx [mailto:riena-dev-
> bounces@xxxxxxxxxxx] Im Auftrag von Elias Volanakis
> Gesendet: Montag, 9. August 2010 08:39
> An: Riena Developers list
> Betreff: [riena-dev] Committed - Navigation on RAP (1st step)
>
> Riena navigation now runs on RAP - see screenshots. I've changed about
> 30 files, so it's a good time to sync.
>
> There is still plenty of things that don't work or need polish. But
> even a long journey starts with a first step.
>
> Notes:
>
> - to reproduce the screenshot you will need to patch RAP at the moment!
> (Bug 322041)
>
> - my focus on the next sprint should be making Riena on RAP more
> consumable for other developers. Right know in both targets (Riena /
> RAP) you have a few (or about 300 on RAP) compile errors. I think in
> order to have more people consuming / hacking this we need automated
> build, which also means 0 compile errors. My vision of getting there
> involves two targets (Riena || RAP), two .psf files, two builds --
> these things we almost have except: 0 compiler errors and a RAP build.
> To get to 0 compile errors we need a bit of API-breaking refactoring
> -- mostly of custom SWT widgets like the CompletionCombo, InfoFlyout,
> DialogGrabCornerListenerWithTracker etc). I'll discuss details and next
> steps with Christian.
>
> Looking forward to an interesting week,
> Elias.
>
> --
> Elias Volanakis | Technical Lead | http://eclipsesource.com
> elias@xxxxxxxxxxxxxxxxx | +1 503 929 5537 | @evolanakis

-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: http://www.compeople.de/

Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
Ust-Ident.-Nr: DE207665352
-------------------------------------------------------------