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:0.7.0 Planning:Iteration 10"

Line 1: Line 1:
 
Iteration 10 runs from July 11 - July 22
 
Iteration 10 runs from July 11 - July 22
  
'''Target line items - ''' [https://bugs.eclipse.org/bugs/buglist.cgi?bug_severity=enhancement;classification=Tools;query_based_on=I9%20Enhancements;query_format=advanced;product=EDT;target_milestone=0.7.0%20M2%20I10 Bugzilla Search]
+
'''Target line items - ''' [https://bugs.eclipse.org/bugs/buglist.cgi?bug_severity=enhancement;classification=Tools;query_based_on=I10%20Enhancements;query_format=advanced;product=EDT;target_milestone=0.7.0%20M2%20I10 Bugzilla Search]
  
  
 
*Core
 
*Core
 +
**Compiler - front end needs to be designed - refactoring, validation framework, etc. and then tasked. ({{bug|347006}}) 
 +
*IDE
 +
**Generator builder <br>
 +
**Editor
 +
***Content assist ({{bug|348207}})
 +
***working copy compiler ({{bug|348960}})
 +
***search ({{bug|346312}})
 +
***Ruler actions ({{bug|350647}})
 +
****Folding (Enable folding, Expand all, Collapse all)
 +
****Add task, Add bookmark
 +
***port EGLAR support code from RBD 8012 to EDT ({{bug|347065}})
 +
****Export an EGLar
 +
***Improve RBD refactoring ({{bug|349847}})
 +
 +
 +
*Services
 +
**Implement REST service invocation for Javascript gen ({{bug|346144}})
 +
**Implement a proxy for Javascript service invocation ({{bug|346145}})
 +
**Implement XML support for Javascript generation ({{bug|346138}})
 +
**Deployment design, simple copy implementation
 +
 +
*Javascript
 +
**Code contribution - start the CQ process for the JavaScript runtime. We'll start with the entire RBD JS runtime, and then strip out anything that won't be needed in EDT. ({{bug|348120}})
 +
**generating a RUI library, JavaScript generation in general. Open extensible architecture. Also looking at hooking into debug - this needs to be explored. Need to look at 'purifying' the RUI gen, removing the RBD-specific aspects.
 +
***Runtime architecture
 +
***Support for records ({{bug|346925}})<br>
 +
***Templates
 +
***Universal UI model
 +
***Mobile strategy (later iteration?)
 +
*Javagen
 +
**refactoring core EGL language vs. RBD-specific ({{bug|346334}}) (itemize what is left, likely deferred to later iteration)
 +
**JPA design ({{bug|346425}})
 +
*Determine scope of EGL Language
 +
*Test framework
 +
**Develop conformance tests for a type and a statement ({{bug|347153}})
 +
**create tooling to parse the test framework results ({{bug|347221}})

Revision as of 07:10, 6 July 2011

Iteration 10 runs from July 11 - July 22

Target line items - Bugzilla Search


  • Core
    • Compiler - front end needs to be designed - refactoring, validation framework, etc. and then tasked. (bug 347006
  • IDE
    • Generator builder
    • Editor


  • Services
    • Implement REST service invocation for Javascript gen (bug 346144)
    • Implement a proxy for Javascript service invocation (bug 346145)
    • Implement XML support for Javascript generation (bug 346138)
    • Deployment design, simple copy implementation
  • Javascript
    • Code contribution - start the CQ process for the JavaScript runtime. We'll start with the entire RBD JS runtime, and then strip out anything that won't be needed in EDT. (bug 348120)
    • generating a RUI library, JavaScript generation in general. Open extensible architecture. Also looking at hooking into debug - this needs to be explored. Need to look at 'purifying' the RUI gen, removing the RBD-specific aspects.
      • Runtime architecture
      • Support for records (bug 346925)
      • Templates
      • Universal UI model
      • Mobile strategy (later iteration?)
  • Javagen
    • refactoring core EGL language vs. RBD-specific (bug 346334) (itemize what is left, likely deferred to later iteration)
    • JPA design (bug 346425)
  • Determine scope of EGL Language
  • Test framework
    • Develop conformance tests for a type and a statement (bug 347153)
    • create tooling to parse the test framework results (bug 347221)

Back to the top