|Re: Scout and web-based GUIs [message #877290 is a reply to message #877126]
||Sat, 26 May 2012 10:46
| Ivan Motsch
Registered: March 2010
A scout application consists of models for form, field, desktop, view, etc, including gui/business logic and glue code.|
This model does not contain any swt, swing, ajax etc. code.
By adding the scout gui plugins (swt/rcp, swing, ajax,rap) this application becomes a RCP, AJAX, RAP application.
In short. The scout way of creating applications is by not creating a hard-wired swt,swing or ajax application in the first place.
Therefore for example a migration from an existing scout "Swing" application to a scout "Ajax" application is a zero step. Just changing the involved gui plugins.
This all describes the front-end part.
The back-end part is similar. It uses the equinox server side as the core for services (osgi), integration, jax-ws and j2ee (bridge servlet).
Powered by FUDForum
. Page generated in 0.04112 seconds