|
Re: Single Sourcing RAP & SWT [message #1240032 is a reply to message #1239947] |
Wed, 05 February 2014 15:16 |
Eclipse User |
|
|
|
Hi João
I can fully understand your needs.
At the time we started developing an RWT implementation of Scout we started with one single code base for RWT and SWT. Pretty soon we had several hard coded switches to fix some issues for the one or the other rendering engine. So in RWT it is rather a bad idea to use GC drawings or the file chooser does behave fully different in Web applications also table, tree, smartfield, timechooser, datechooser and more. Furthermore several layout issues can easily be solved with CSS vs a hard finger work in rich clients.
So we decided to fully split the SWT and RWT rendering engines and keep the flexibility of the two worlds.
To answer your questions:
1) No, Scout does not provide a solution for single sourcing RWT and SWT renderers.
2) See explanation above.
3) To keep the flexibility also in future I would advice to split the RWT and SWT rendering engine strictly.
Hope it helped
-andreas
|
|
|
|
Powered by
FUDForum. Page generated in 0.09245 seconds