Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EDT:How to move RBD app to EDT"
| Line 1: | Line 1: | ||
| − | An EDT project has different layout with an RBD project, the best way to make RBD code working 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. | + | An EDT project has different layout with an RBD project, the best way to make RBD code working 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 == |
| + | #Create a new EDT project. | ||
| + | ##If the application contains RUI Handlers, choose either '''Web2.0 client application''' or '''Web 2.0 client application with service''' depending on if the application also contains services. | ||
| + | ##If the application contains only Programs and common code, choose '''Basic'''. | ||
| + | #Copy EGL files and packages from the RBD project to the EDT project | ||
| + | #Configure EGL Compiler and generators. Compiler setting is a new feature in EDT which allows setting of different generators for each package and file. | ||
| + | ##Select JavaScript Generator for Rich UI Handlers, Widgets and any common parts(Record, Library) which are referenced by Rich UI Handlers or Widgets | ||
| + | ##Select Java Generator for Services, Programs and any common parts referenced by Services or Programs | ||
| + | ##Common parts require both JavaScript Generator and Java Generator are suggest to be put into a separate package which is configured with both Generators | ||
| + | ##Compiler setting of a parent resource is inherited by the children. Setting the package is usually good enough. | ||
| + | ##Refactor package and code is sometime necessary | ||
== Create new EDT project == | == Create new EDT project == | ||
| − | |||
== Create new EDT project == | == Create new EDT project == | ||
| − | |||
[[Category:EDT]] | [[Category:EDT]] | ||
Revision as of 05:40, 23 November 2011
An EDT project has different layout with an RBD project, the best way to make RBD code working 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
- Create a new EDT project.
- If the application contains RUI Handlers, choose either Web2.0 client application or Web 2.0 client application with service depending on if the application also contains services.
- If the application contains only Programs and common code, choose Basic.
- Copy EGL files and packages from the RBD project to the EDT project
- Configure EGL Compiler and generators. Compiler setting is a new feature in EDT which allows setting of different generators for each package and file.
- Select JavaScript Generator for Rich UI Handlers, Widgets and any common parts(Record, Library) which are referenced by Rich UI Handlers or Widgets
- Select Java Generator for Services, Programs and any common parts referenced by Services or Programs
- Common parts require both JavaScript Generator and Java Generator are suggest to be put into a separate package which is configured with both Generators
- Compiler setting of a parent resource is inherited by the children. Setting the package is usually good enough.
- Refactor package and code is sometime necessary