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:RUI (Rich UIs)"
Line 2: | Line 2: | ||
EGL RUI (Rich UIs) allows you to build modern Rich Internet Applications that are written entirely in EGL (rather than having to learn and keep up with HTML, CSS, and JavaScript). | EGL RUI (Rich UIs) allows you to build modern Rich Internet Applications that are written entirely in EGL (rather than having to learn and keep up with HTML, CSS, and JavaScript). | ||
+ | |||
+ | <br> | ||
+ | |||
+ | The Visual Editor (VE) provides a what-you-see-is-what-you-get experience in composing and laying out RUIs. <br> | ||
<br> | <br> | ||
Line 20: | Line 24: | ||
{| cellspacing="1" cellpadding="1" border="1" width="100%" | {| cellspacing="1" cellpadding="1" border="1" width="100%" | ||
− | |+ Scenario: Hello, world | + | |+ Scenario: Hello, world |
|- | |- | ||
− | | Step<br> | + | | Step<br> |
− | | Description<br> | + | | Description<br> |
| Features<br> | | Features<br> | ||
|- | |- | ||
− | | Create a project<br> | + | | Create a project<br> |
| <br> | | <br> | ||
| | | | ||
− | + | *Create EGL Project wizard<br> | |
− | *Create EGL Project | + | **import widget libraries<br> |
− | *import widget libraries<br> | + | **specify a base package and generate the default packages<br> |
− | *specify a base package and generate the default packages<br> | + | |
|- | |- | ||
− | | <br> | + | | Create a new view<br> |
− | | <br> | + | | <br> |
− | | <br> | + | | |
+ | *Create RUIHandler wizard<br> | ||
+ | |||
|- | |- | ||
− | | <br> | + | | Create the UI consisting of a <br>textfield and a button<br> |
− | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
− | | <br> | + | | Create a simple service<br> |
− | | <br> | + | | <br> |
− | | <br> | + | | |
+ | *Create Service wizard<br> | ||
+ | |||
|- | |- | ||
− | | <br> | + | | Add logic to invoke the service when the button is clicked.<br> |
− | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
− | | <br> | + | | Preview the application to ensure that it works.<br> |
− | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
− | | <br> | + | | Debug the application by setting breakpoints in both <br>the UI and the service<br> |
− | | <br> | + | | <br> |
| <br> | | <br> | ||
|- | |- | ||
− | | <br> | + | | Deploy the application.<br> |
− | | <br> | + | | <br> |
− | | <br> | + | | Deploy<br> |
|- | |- | ||
− | | <br> | + | | Run the deployed app.<br> |
− | | <br> | + | | <br> |
| <br> | | <br> | ||
|} | |} | ||
− | <br> | + | <br> |
= Future Epics = | = Future Epics = |
Revision as of 14:03, 20 July 2011
Contents
Overview
EGL RUI (Rich UIs) allows you to build modern Rich Internet Applications that are written entirely in EGL (rather than having to learn and keep up with HTML, CSS, and JavaScript).
The Visual Editor (VE) provides a what-you-see-is-what-you-get experience in composing and laying out RUIs.
Requirements
This section is to document stories & scenarios that are essentially in-plan.
Story: Hello, World
As an EGL developer, I can build a "Hello, World" web application in which a user inputs their name, and I can implement a service that responds with the user's input prepended with "Hello, ".
(This video for EGL Community Edition 1.0 provides a good illustration of this scenario, although there will be some changes and some improvements.)
Scenario: Hello, world
Step |
Description |
Features |
Create a project |
|
|
Create a new view |
|
|
Create the UI consisting of a textfield and a button |
|
|
Create a simple service |
|
|
Add logic to invoke the service when the button is clicked. |
|
|
Preview the application to ensure that it works. |
|
|
Debug the application by setting breakpoints in both the UI and the service |
|
|
Deploy the application. |
|
Deploy |
Run the deployed app. |
|
|
Future Epics
User stories which are not in-plan at this time.
Additional Features
Below is a hierarchy of miscellaneous features that are not Future Epics and which are not identified in any of the user stories in Requirements (above).