RAP does a good job of taking the UI written for the desktop and “remote’ing” it to the web. Perhaps though in this case the photo app’s desktop “shape” is wrong for the web.

I’ve been speaking to Erich and others recently about the notion that the workbench model should just describe the parts and their relationships, with then all visual decisions being made elsewhere. Presently there’s an odd mix of some decisions such as containment within sashes, sash positions, etc., being made in the model, and others such as fonts and colors made in CSS. Then there’s the problem that once you get below the part level, it’s up the handler code to make the additional child widgets. If instead that widget creation was declarative, then for the RAP case we could create an equivalent web control rather than ‘web-ifying’ the Gallery widget.

So I’m not sure if the right solution for RAP is:
1) Make a remote’able Gallery widget (like you’ve done for SWT)
2) Override the e4 modelled workbench renderers to produce web’y things instead of producing SWT things that can be remote’d (cut out the middle man)
3) Copy the e4 photo xmi, replacing the thumbnails part with something specific for the web
4) Go the full-on declarative route where the parts describe the widget tree declaratively and, like the workbench model renderers, produce the right widgets for desktop or web.