| 3 | | *Core Features: |
| 4 | | -BNF front-end (Parser, Lexer, Linker, etc.) - translates a textual representation into an Ecore model |
| 5 | | -the editor |
| 6 | | - Editor - provides IDE features, e.g. auto-completion, syntax highlighting, etc. |
| 7 | | |
| 8 | | *Validation Rules: these rules will give warnings in the editor if they find find consistencies in the code |
| | 4 | 1. BNF front-end (Parser, Lexer, Linker, etc.) |
| | 5 | 1. translates a textual representation into an Ecore model |
| | 6 | 1. Editor - provides IDE features, e.g. auto-completion, syntax highlighting, etc. |
| 10 | | -checkUpdateGrammarConsistency: checks, if the grammar is an updated grammar, for consistencies between the originals and the new grammar |
| 11 | | e.g.: |
| 12 | | status: not migrated |
| 13 | | |
| 14 | | -CheckReferencedOnlyOnce: this should warn if there is a rule that is only referenced once, this is an inlining hint |
| 15 | | e.g.: |
| 16 | | status: migrated |
| 17 | | |
| 18 | | -checkPassthroughRule: |
| 19 | | e.g.:this tests if a rule gets just passed through |
| 20 | | a ::= b |
| 21 | | b ::= "literal" |
| 22 | | <=> a ::= "literal" , which is better for EBNF |
| 23 | | |
| 24 | | -checkEqualAlternative: this tests if a rule got equal alternatives |
| 25 | | e.g.: |
| 26 | | a::= d | d |
| 27 | | status: still some problems |
| 28 | | |
| 29 | | -checkDuplicateRules: checks if there is another rule in the EtsiBnf, that got the same behaviour |
| 30 | | e.g.: |
| 31 | | a ::= "literal" | b |
| 32 | | c ::= "literal" | b |
| 33 | | status: migrated |
| 34 | | |
| 35 | | -checkSubruleDuplicates: |
| 36 | | |
| 37 | | status: not migrated |
| 38 | | |
| 39 | | -check unused rule: it checks if a rule is used (exept for the rule with the number 1) |
| 40 | | |
| 41 | | status: migrated |
| 42 | | |
| 43 | | -checkNameIsUnique: checks if the nam of a rule is already in use |
| 44 | | e.g.: |
| 45 | | a ::= "end" |
| 46 | | a ::= "fin" |
| 47 | | |
| 48 | | status: migrated |
| 49 | | |
| 50 | | *Generation: |
| 51 | | -basic generation has been achieved but the output-format is unclear. Works with a Xtend-generator, momentary "xmi-like" output for a bnf grammar |
| 52 | | -old version had: mwe2 Generator and Xpand2 support |
| 53 | | - it could generate mergeGrammars from CoreGrammars and CompositeGrammars from Merge grammars |
| 54 | | -seemingly it could produce a xsl-fo-file with the corresponding nodemodel |
| 55 | | |
| 56 | | -new version: xsl-fo file for all bnf grammars (not for merge or deltagrammars) this can be Rendered to Pdf using apache-fop |
| 57 | | |
| 58 | | *Formatting: |
| 59 | | -old: had some but they are got commented out in the main project |
| 60 | | |
| 61 | | -new: Line-break after every rule, white-spaces after all literals, linebreak and double tab after all >|< bars |
| 62 | | -still got some Problems with rulereferences at the end of a definitionlist |
| | 8 | * '''Validation Rules:''' these rules will give warnings in the editor if they find find consistencies in the code |
| 64 | | *Refactoring & Quickfixing: |
| 65 | | old had: |
| 66 | | -auto Numbering of rules |
| 67 | | -not migrated |
| 68 | | -remove unused rules |
| 69 | | -not migrated |
| 70 | | |
| 71 | | -replacement of passthroughRules |
| 72 | | -not migrated |
| 73 | | -refactor uppercasetokenRules |
| 74 | | -not migrated |
| 75 | | |
| 76 | | -find references, this one is standard in xtext2.* |
| 77 | | -renaming, this is standard in xtext2.* |
| 78 | | |
| 79 | | *Grammar composition: |
| 80 | | -3 grammartypes: |
| 81 | | grammar: normal grammar |
| 82 | | deltagrammar: different notation for a extension grammar, |
| 83 | | adds new rules to a grammar (regular rules)and |
| 84 | | adds changes to rules of the extended grammar(extension rules) |
| 85 | | -can be automaticly created |
| 86 | | mergegrammar: for merging extensions |
| 87 | | -old version had an automatic composition Process, for merge grammars, with a small pop-up-menu. |
| | 10 | 1. checkUpdateGrammarConsistency: checks, if the grammar is an updated grammar, for consistencies between the originals and the new grammar e.g.: status: not migrated |
| 92 | | *Deploying: |
| 93 | | -export project: Plug-in Development/deployable plug-ins and fragments |
| 94 | | -rcp project with a minimal eclipse editor |
| | 14 | 3. checkPassthroughRule: e.g.:this tests if a rule gets just passed through a ::= b b ::= "literal" <=> a ::= "literal" , which is better for EBNF |
| | 15 | |
| | 16 | 4. checkEqualAlternative: this tests if a rule got equal alternatives e.g.: a::= d | d status: still some problems |
| | 17 | |
| | 18 | 5. checkDuplicateRules: checks if there is another rule in the EtsiBnf , that got the same behaviour e.g.: a ::= "literal" | b c ::= "literal" | b status: migrated |
| | 19 | |
| | 20 | 6. checkSubruleDuplicates: |
| | 21 | |
| | 22 | status: not migrated |
| | 23 | |
| | 24 | 7. check unused rule: it checks if a rule is used (exept for the rule with the number 1) |
| | 25 | |
| | 26 | status: migrated |
| | 27 | |
| | 28 | 8. checkNameIsUnique: checks if the nam of a rule is already in use e.g.: a ::= "end" a ::= "fin" |
| | 29 | |
| | 30 | status: migrated |
| | 31 | |
| | 32 | * '''Generation:''' |
| | 33 | |
| | 34 | -basic generation has been achieved but the output-format is unclear. Works with a Xtend-generator, momentary "xmi-like" output for a bnf grammar -old version had: mwe2 Generator and Xpand2 support |
| | 35 | |
| | 36 | - it could generate mergeGrammars from CoreGrammars and CompositeGrammars from Merge grammars -seemingly it could produce a xsl-fo-file with the corresponding nodemodel |
| | 37 | |
| | 38 | -new version: xsl-fo file for all bnf grammars (not for merge or deltagrammars) this can be Rendered to Pdf using apache-fop |
| | 39 | |
| | 40 | * '''Formatting:''' |
| | 41 | |
| | 42 | old: had some but they are got commented out in the main project |
| | 43 | |
| | 44 | new: Line-break after every rule, white-spaces after all literals, possible update linebreak and double tab after all >|< bars |
| | 45 | |
| | 46 | * '''Refactoring & Quickfixing:''' |
| | 47 | |
| | 48 | 1. auto Numbering of rules -not migrated |
| | 49 | 1. remove unused rules -not migrated |
| | 50 | |
| | 51 | 3. replacement of passthroughRules -not migrated |
| | 52 | 3. refactor uppercasetokenRules -not migrated |
| | 53 | |
| | 54 | 5.find references, this one is standard in xtext2.* -renaming, this is standard in xtext2.* |
| | 55 | |
| | 56 | *Grammar composition: |
| | 57 | |
| | 58 | -3 grammartypes: |
| | 59 | grammar: normal grammar deltagrammar: different notation for a extension grammar, |
| | 60 | adds new rules to a grammar (regular rules)and adds changes to rules of the extended grammar(extension rules) -can be automaticly created |
| | 61 | mergegrammar: for merging extensions |
| | 62 | -old version had an automatic composition Process, for merge grammars, with a small pop-up-menu. |
| | 63 | |
| | 64 | * at the moment no support in the new version |
| | 65 | |
| | 66 | * '''Deploying:''' |
| | 67 | |
| | 68 | -export project: Plug-in Development/deployable plug-ins and fragments -rcp project with a minimal eclipse editor |
