|
| Re: To migrate or not to migrate (Indigo to Luna) [message #1396458 is a reply to message #1391824] |
Tue, 08 July 2014 10:21   |
 Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
RAP does not support the compat mode! I worked for Luna on an incubator
project to supporting RAP on e4! The biggest problem for you is that all
views you are probably used from RCP/e3 are not available on plain e4
(ConsoleView, ErrorView, ...).
Tom
On 01.07.14 15:16, John GALLET wrote:
> Hi all,
>
> Here is my situation: we have been running on E3 Indigo for quite some
> time but since the latest IE 11 and Firefox (on windows 7), our RAP
> application does not work anymore (not even at the splash screen level).
> Very soon our clients will run into this problem as they migrate to the
> latest versions. We have quite a technical debt and we need to act.
> We have these choices :
> - immediately go for a full E4 "new" application model, which I would
> prefer.
> - "only" migrate our E3 components through the compatibility layer and
> stay on an E3 model for another year or so. It seems a safest way but
> also seems to involve doing the work twice, at least all the regression
> tests if not the development.
> - if I understand well, an hybrid "we keep what's working in E3 and
> migrate the new components" will just not work (by design).
>
> A list of the officially APIed components would greatly help. For
> example, I noticed that ProgressView is sort of ready but not really yet
> (bugzilla 429505).
>
> Is there such a list somewhere ? I waited for Luna to have the latest
> stabilized version but I am not confident about this choice.
> Also any advice would be greatly appreciated.
> I bought and read Lars Vogel's book (second Edition), but it was written
> long enough that it could not yet really cover this topic.
>
> TIA John
>
> Context:
> BIRT based RCP application also using RAP for the browser version.
>
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.02843 seconds
] 
Search
Help
Register
Login
Home
