Migrating applications from Echo 1 to Echo2

This page lists changes and how to port / migrate Echo1 based applications to Echo2.

Echo2 Core

• Package names have changed in Echo2.

   nextapp.echo.*  ->  nextapp.echo2.app.*

• Filler/Strut components are no longer present in Echo2. Columns and Rows should be used instead. EchoPointNG does provide a Strut component.

• The Column/Row components should be used in lieu of Echo1's Panel (which no longer exists in Echo2).

• SelectFields now use the same model/selection model API as ListBoxes in Echo2. The DefaultSelectFieldModel class no longer exists. A DefaultListModel and DefaultListSelectionModel should be used instead.

• ButtonGroup changes;

   nextapp.echo.ButtonGroup  ->  nextapp.echo2.app.button.ButtonGroup
   ButtonGroup.add()  ->  ButtonGroup.addButton()

• In Echo1 RadioButtons are added to ButtonGroups using the following method:

   
   // Echo1
   buttonGroupA.add(radioButton1);
   buttonGroupA.add(radioButton2);
   buttonGroupA.add(radioButton3);

In this way, Echo1 makes one RadioButton selectable among radioButtons that are added to buttonGroupA.

For Echo2 it is reversed, now you should set group of RadioButton for each button as follow:

   // Echo2
   radioButton1.setGroup(buttonGroupA);
   radioButton2.setGroup(buttonGroupA);
   radioButton3.setGroup(buttonGroupA);

And buttonGroupA.addButton(radioButton1) does not work!

EchoPoint 1.0 -> EchoPointNG 2.0

• BallonHelp.add(...) -> BallonHelp.setPopup(..) (To show a component inside baloon help, add function still exist but does nothing)

• ConfirmButton (echopoint) -> ??

• NumberFormatField (echopoint) -> ??