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 "Xtext Project Plan"

(Milestone 4 (due 2008-0x-xx))
(Milestone 5 (due 2008-0x-xx))
Line 33: Line 33:
 
* remove singleton services registration
 
* remove singleton services registration
  
=== Milestone 5 (due 2008-0x-xx) ===
+
=== Milestone 5 (due 2008-07-04) ===
 
+
* partial parsing
 +
* tests and UI use resource API
 +
* GrammarAccess contains accessors to parser and lexer rules
 +
* first draft of content assist
  
 +
=== Milestone 6 (due 2008-07-18) ===
 
----
 
----
  

Revision as of 02:46, 2 July 2008

Milestone 1 (due 2008-05-09)

  • Bootstrapping

Milestone 2 (due 2008-05-23)

  • build process
  • error handling in parser and lexer
  • support for mixing of imported and generated meta models
  • Basic Editor
  • parse tree
  • parse tree / contains whitespace
  • parse tree / reconstruction / bi-directionality
  • EMF Resource API adaption

Milestone 3 (due 2008-06-06)

  • build process
  • error handling in parser and lexer
  • language inheritance
  • service registry framework
  • value converter (i.e. arbitrary Datatypes for lexer rules)
  • generator model
  • (UI) syntax coloring
  • (UI) Preferences
  • (UI) Outline
  • (UI) Content assist (define interface, integrate Michael)

Milestone 4 (due 2008-06-20)

  • use commons logging
  • more Junit tests
  • build process
  • refactor genmodel (remove GenClass and GenPlugin)
  • remove singleton services registration

Milestone 5 (due 2008-07-04)

* partial parsing
* tests and UI use resource API
* GrammarAccess contains accessors to parser and lexer rules
* first draft of content assist

Milestone 6 (due 2008-07-18)



Features to be implemented

Runtime

  • syntactic predicates
  • semantic predicates
  • description of lexer rules
  • cross-references
  • validation API
  • referencing files
  • Enum rules
  • generated checks based on the grammar
  • grammar inheritance (having built-in rules defined in a common super grammar)
  • fragments

Tooling

see Xtext Project Plan/Features/Tooling

Back to the top