Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EDT:RUI (Rich UIs)"

 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
This is a draft document and is a work-in-progress.
 +
 
= Overview  =
 
= 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).    
 
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.&nbsp; <br>
  
 
<br>  
 
<br>  
  
 
= Requirements  =
 
= Requirements  =
 +
 +
This section is to document stories &amp; scenarios that are essentially in-plan.
  
 
== Story:&nbsp; Hello, World  ==
 
== Story:&nbsp; 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, ". <br><br>([http://www.youtube.com/watch?v=FxKTNgoT0cU This video] for EGL Community Edition 1.0 provides a good illustration of this scenario, although there will be some changes and some improvements.)<br>
+
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, ". <br><br>([http://www.youtube.com/watch?v=FxKTNgoT0cU This video] for EGL Community Edition 1.0 provides a good illustration of this scenario, although there will be some changes and some improvements.)<br>
 +
 
 +
[[Scenario: Hello, world]] <br> [[Scenario: Hello, world with a Database]] <br>  
  
 
<br>  
 
<br>  
  
==== Scenario:&nbsp; Hello, world <br> ====
+
== Story:&nbsp; Import Widget projects as an EGLAR  ==
 +
 
 +
[If this is really a story (instead of a feature), need details]
 +
 
 +
<br>
 +
 
 +
== Story:&nbsp; RUI Technical Sample  ==
 +
 
 +
[need details]
 +
 
 +
<br>  
 +
 
 +
== Story:&nbsp; Dojo Technical Sample  ==
 +
 
 +
[need details]
 +
 
 +
<br>
 +
 
 +
<br>
 +
 
 +
= Future Epics  =
 +
 
 +
User stories which are not in-plan at this time.
 +
 
 +
<br>
  
<br>
+
= Additional Features<br> =
  
<br>
+
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).

Latest revision as of 21:21, 20 July 2011

This is a draft document and is a work-in-progress.

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
Scenario: Hello, world with a Database


Story:  Import Widget projects as an EGLAR

[If this is really a story (instead of a feature), need details]


Story:  RUI Technical Sample

[need details]


Story:  Dojo Technical Sample

[need details]



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).

Back to the top