Difference between revisions of "EDT:How to move RBD app to EDT"

Revision as of 23:38, 30 November 2011

An EDT project has a different layout than an RBD project. The best way to make RBD code work in EDT is to create a new EDT project and copy the code to it. There have also been some changes to the EGL language that may require you to change your RBD-developed code to be modified prior to running on EDT. 

Move code to an EDT project

1. Create a new EDT project.
   1. If the application contains RUI Handlers, choose either Web2.0 client application or Web 2.0 client application with service depending on whether the application contains services.
   2. If the application contains only Programs and common code, choose Basic.
2. Copy EGL files and packages from the RBD project to the EDT project.
3. Configure the EGL Compiler and generators. The Compiler setting is a new feature in EDT which allows specifying generators for each package or file.
   1. Select JavaScript Generator for Rich UI Handlers, Widgets and any common parts (Record, Library) which are referenced by Rich UI Handlers or Widgets.
   2. Select Java Generator for Services, Programs and any common parts referenced by Services or Programs.
   3. Common parts that require both JavaScript Generator and Java Generator should be put into a separate package configured with both Generators.
   4. The compiler setting of a parent resource is inherited by the children, so setting at the package level is usually good enough.
   5. Refactoring packages and code is sometimes necessary.

Modify EGL code

1. Use Organize Imports (Ctrl+Shift+O) to let EDT import the correct widgets and system parts. This is needed for almost all EGL files because of the package name changes.
2. Below is a handy list of things to modify. It is recorded when we moved RBD samples and test apps to EDT. See the EGL Language conversion page for more information about updates to EGL. The Code snippets page is also a good place to find code.

myInt INT?;

myInt Int[]?;

employeeList Employee[0];

employeeList Employee[];

myService1 MyService {@DedicatedService};

myService1 MyService?{@DedicatedService};

myService1 MyService {@bindService{bindingKey = "abc"}};

myService1 MyService?{@Resource {bindingKey = "abc"}};
 
or 
 
myService1 MyService?;
myService1 = SysLib.getResource("abc");

writeStderr("hello world!");

Syslib.writeStderr("hello world!");

program MyProgram type BasicProgram {}
library MyLibrary type BasicLibrary {}
record recordName type BasicRecord

program MyProgram
record recordName
library MyLibrary

Record Attendee {
XMLStructure = XMLStructureKind.simpleContent}
 
ExternalType BrowserUtils ... {
javaScriptName = "BrowserUtils" ...}	
 
target String{@JavaScriptProperty {}};

Record Attendee {@XMLValue {
kind = XMLStructureKind.simpleContent}}
 
ExternalType BrowserUtils ... {
externalName= "BrowserUtils" ...}
 
target String{@Property {}};

egl.defineWidget('utils', 'QueryUtils', 
'egl.ui.rui', 'Widget',

egl.defineWidget('utils', 'QueryUtils', 
'eglx.ui.rui', 'Widget',

t time;

t timestamp("yyyyMMddHHmm");

Language elements not supported in EDT

Called program, DataItem, Datatable, Structured Record, Form, FormGroup, currentTime, DataTimeLib.currentTime, DateTimeLib.timeOf, DataTimeLib.timeValue, Move, maxSize, validValues, interval, RuntimeException