Eclipse Scout: Migration Guide

This document describes all relevant changes from Eclipse Scout 7.0 to Eclipse Scout 7.1. If existing code has to be migrated, instructions are provided here.

Since the new Html UI was introduced with Scout 5.2 this property had no effect on the UI anymore. Instead the UI uses sensible defaults for each field type. For instance: a LabelField is never focusable, a normal StringField is always focusable, as long as it is enabled. Since the property was rarely used, we removed all methods from the interface/class FormField. Removed methods/properties:

Since there is no replacement for the focusable property, remove all code that uses one of the methods/properties listed above.

In Scout 7.0 the new SmartField implementation used the package and name smartfield2.SmartField2. With Scout 7.1 the new SmartField replaced the old SmartField completely, and thus was moved to and renamed to smartfield.SmartField. If you have already used the new SmartField in Scout 7.0 you must move / rename all references to these classes.

The base class and interfaces of the old SmartField implementation was IContentAssistField. With the new SmartField implementation this interfaces and all classes containing the word "ContentAssist" in their name, have been either removed or renamed to "SmartField". If your code references one of these classes you should simply try to rename all references. Since the API of the new SmartField is almost the same as the old, this should work and should cause no or few changes in your code. The following classes have been removed without replacement:

Since the new SmartImplementation does not have a proposal chooser model anymore these classes have also been removed. If you must have a special implementation of a proposal chooser, you must implement a proposal chooser in JavaScript (see: ProposalChooser.js), which renders the data / lookup-rows it receives from the server-side SmartField:

N/A

N/A