Hi Rienners,
great news indeed!
We'd also like to keep up the good cooperation between RAP and Riena and
created this bug to track progress:
Bug 324443 - Support Riena RAP migration
https://bugs.eclipse.org/bugs/show_bug.cgi?id=324443I've seen that you listed a couple of issues on this wiki page:
http://wiki.eclipse.org/Riena_on_RAPPlease don't hesitate to open bugs for those issues that you need help
for and set those bugs as dependencies to the one above.
Best regards, Ralf
Christian Campo wrote:
Hi Rienaers, (Riena committers, contributors, users, interested parties)
"dont surprise your community" is one of the key points when dealing
with others in an open source environment. So I have explain a little
for a change in our plans and I hope I dont surprise anyone here.
When we create Riena 2.0 for the Helios release we published that our
next release would be 2.1. in december this year. That pretty much
followed what we did the year before where we have a minor release after
6 month.
Now several month in the time "after Helios", when we looked for ways to
go we had some interesting discussions among us committers (mostly face
2 face or telco's).
We'd like to make a major step in making Riena work really way better
under RAP. A second goal is to investigate and prototyp making Riena run
on e4, not only on the compatibility layer but also using the new
workbench model and all the other new stuff that is part of it.
However we cannot do all at the same time.
In any event, having a midterm release in december seems to stop us from
making a big step forward. So we decided that our next release is Riena
3.0 which will come with Indigo in June 2011. We will publish milestones
along the line with Indigo (Eclipse 3.7).
A new major version is not only necessary because it is a big step
forward but it also need some flexibilty (nice wording :-) ) for
breaking API. We will do that we the same kind of documentation and
caution that we used for Riena 2.0. But certain things will need to change.
Our main focus will be to improve the RAP support. And that will also
mean that we have to make a number of changes in our code. Elias was
kind enough to start a wiki page http://wiki.eclipse.org/Riena_on_RAP
with some issues that we need to address.
The second task (with less prio) is to investigate what it means to also
run on the native new API of e4 and build prototypes for that. We have
already started and will keep on going there and start to create bundles
for that.
Any feedback, comments, contribution, help or anything is welcomed at
this point in time.
If you have an opinion about the direction we are taking let us know......
christian
-------------------------------------------------------------
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
-------------------------------------------------------------
_______________________________________________
rap-dev mailing list
rap-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rap-dev
--
Ralf Sternberg
RAP Development Team
EclipseSource
www.eclipsesource.comTel: +49 721 664 7330
Fax: +49 721 664 73329
Innoopract Informationssysteme GmbH
Stephanienstrasse 20, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
_______________________________________________
rap-dev mailing list
rap-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rap-dev
