Community
Participate
Working Groups
I am opening this bug to host a discussion with the Platform team where we can talk about the problems that Riena currently has running on top of E4 and we can openly discussion what can be done. There is already a wiki page http://wiki.eclipse.org/Riena/E4 where I am describing how you setup a Riena workspace against 3.8 and 4.2 (both M5) and check for yourself how Riena behaves on the two platforms. And to be clear on this, the problem is that Riena is tightly coupled to the workbench of RCP 3.x and has many tweaks including using the Presentation API to make a Riena App NOT look like an RCP app. The Presentation API is no longer supported in 4.x and we in Riena need to figure out what to do to support both platforms 3.x and 4.x.
Christian, is there any way you could attach screen caps of the 3.x versions of the presentations that are causing problems ? This would give me a starting point to see if I can come up with some approaches to try...
Sure I was planning to do this. I just didnt come around to find the time. I am sure there is time tomorrow
Assigning to self to reduce traffic on the riena-dev-ui maibox. Everyone interested in the Riena team on the progress needs to add himself to the CC list of this bug.
I have update the wiki with a description who you can setup a workspace with 3.8 and 4.2 target platform and start a Riena sample app for both of them. The 3.8 based version comes up with a screen (a link to a screenshot is in the wiki), the 4.2. falls over with a NPE in the ModelServiceImpl. Riena obviously uses one method that wasnt API and doesnt exist in 4.x (there is a description on how to remove that one line of code) Bug 361133 was submitted by one of our committers earlier about a callback that is no longer called in 4.x. @Eric please let me know how you like to continue. I want to minimize the time that you spend. We started to build to work on a hack where Riena somehow comes up in E4, but is not yet anywhere in the codebase. Also that was more a prove of concept in what direction the final implementation should be going and even that is unfinished.
e4 support the old way with the theming API is not going anywhere so I am closing this as WONTFIX.