Duration: 25:16

1,732 views

0

When Riena was created 5 years ago on top of Eclipse Technology (RCP, OSGi) it was targeted as a more enduser friendly application platform for client / server applications.So we tweaked RCP here and there and we made OSGi and extensions easier to use by allowing annotations for DI (dependency injection). We also created our own application model that allowed the partition and segment an application in a very flexibel way.

Then over the time we had to adapt to changes in the foundation on which Riena was built on top of. We made Riena fit to run with RAP and adopted web technology, switching from single user mode to multi user mode on demand. Later Riena had to run on top of e4 which has its own application model and a new way of doing DI.

The next move that is currently in process is not only supporting SWT as UI Toolkit but also JavaFX.

This talk includes details about

challenges and problems (multi user, multiple UI toolkits)
the way we solved problems
design decisions (2 application models vs 1 application model)
running Riena and Riena applications on 4 different platforms and keeping the codebase nearly identical
what would we have done differently if we had started Riena with e4