Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Scout/NewAndNoteworthy/6.0"
(→Frontend development in Java) |
(→Frontend development in Java) |
||
Line 22: | Line 22: | ||
=== Frontend development in Java === | === Frontend development in Java === | ||
− | The goals of the Scout framework remain | + | The goals of the Scout framework remain unchanged: |
* Boost developer productivity | * Boost developer productivity | ||
* Long term strategy (enterprise apps often live > 10 years) | * Long term strategy (enterprise apps often live > 10 years) | ||
+ | As in previous releases the Scout developer implements against the Scout model classes. | ||
Developing frontends and UI logic in Java remains independent of the new HTML5 renderer technology. | Developing frontends and UI logic in Java remains independent of the new HTML5 renderer technology. | ||
Revision as of 15:01, 18 May 2016
The Scout documentation has been moved to https://eclipsescout.github.io/.
Contents
Eclipse Scout becomes a Java Web Framework
With Release 6.0 the frontend part of the Scout framework becomes a powerful Java web framework.
A new HTML5 Rendering Component
Scout comes with a completley new HTML5 rendering component.
The new HTML5 renderer fully support todays web standards HTML5/CSS3/JavaScript.
- Full styling/theming with CSS3/Less
- Add project specific custom widgets
The HTML5 renderer is highly optimized for Scout
- Minimize download size for initial download
- Avoid unnecessary server rountrips
Frontend development in Java
The goals of the Scout framework remain unchanged:
- Boost developer productivity
- Long term strategy (enterprise apps often live > 10 years)
As in previous releases the Scout developer implements against the Scout model classes.
Developing frontends and UI logic in Java remains independent of the new HTML5 renderer technology.
Plain Maven Projects
simplified build setups for projects
simpler integration of java libraries and frameworks
Upgrade of existing Projects
great care to reduce api breakage to minimum moderate efforts required to upgrade