Changes between Version 3 and Version 4 of Developer
- Timestamp:
- 07/02/14 12:52:20 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Developer
v3 v4 1 __'''Developer Guide BNF Tools'''__ 1 = Developer Guide BNF Tools = 2 2 3 3 BNF Tools is a BNF-Editor based on xText DSLs, which gives away alot of features. 4 4 5 '''The used Features are:''' 5 == The used Features are: == 6 6 7 7 * Grammardefinition … … 23 23 * Deployment as RCP (Rich Client Platform) 24 24 25 '''Grammardefinition:''' 25 ==Grammardefinition:== 26 26 27 27 The corefeature of xText. … … 69 69 After this the whole project can be executed as an Eclipse Application for testing: 70 70 71 '''Validation allows to check for conditions in the BNF-Document:''' 71 ==Validation allows to check for conditions in the BNF-Document:== 72 72 73 73 In the File de.ugoe.cs.swe.bnftools.ebnf/de.ugoe.cs.swe.ebnf.validation/!EbnfValidator.xtend … … 106 106 Which find the Rule references inside a BNF-File or outside a BNF-File. 107 107 108 [[BR]] '''Quickfixing can be applied to warnings given by Validations:'''108 [[BR]]==uickfixing can be applied to warnings given by Validations:== 109 109 110 110 In the File de.ugoe.cs.swe.bnftools.ebnf.ui/de.ugoe.cs.swe.bnftools.ui.quickfix/!EbnfQuickfixProvider.xtend … … 150 150 1. Change the underlying ecoremodel. 151 151 152 [[BR]] '''Generation allows to generate other files from a BNF-Document:'''152 [[BR]]==Generation allows to generate other files from a BNF-Document:== 153 153 154 154 In our case we create a .fo document, that can be transformed into a PDF-Document … … 217 217 To include apache fop you need to add all the jars in a folder e.g. Libs in your project, add this folder to your buildpath, cofigure buildpath and add the jars to it and add them in the plugin.xml on the page runtime at classpath. 218 218 219 [[BR]] '''Formatting or Prittey Printing is to format the BNF-Document:'''219 [[BR]]==Formatting or Prittey Printing is to format the BNF-Document:== 220 220 221 221 In the File de.ugoe.cs.swe.bnftools.ebnf/de.ugoe.cs.swe.ebnf.formatting/!EbnfFormatter.xtend … … 249 249 The Entities are recieved via an Inector that gives access to The Grammar. 250 250 251 [[BR]] '''Outlining and Labeling are Features, that show the document Structure of the BNF-Document:'''251 [[BR]]==Outlining and Labeling are Features, that show the document Structure of the BNF-Document:== 252 252 253 253 Outlinining can be customized in the File … … 277 277 } 278 278 279 [[BR]] '''File import allows to reference Rules from one BNF-Document in another:'''279 [[BR]]==File import allows to reference Rules from one BNF-Document in another:== 280 280 281 281 There are 2 ways for imports, via URI and VIA Namespaces: … … 303 303 'import'importURI=STRING 304 304 305 '''Also it is possible to add features to the UI via Xtext:''' 305 ==Also it is possible to add features to the UI via Xtext:== 306 306 307 307 In the File de.ugoe.cs.swe.bnftools.ebnf.ui/plugin.xml new extensions to the UI can be created in the plugin.xml tab. e.g.: … … 429 429 Here is a Problem since the!EclipseResourceFileSystemAccess2does not contain all the needed inforamtion. Maybe it can be looked up in the normal call of the generator. 430 430 431 '''Deployment as Plugin:''' 431 ==Deployment as Plugin:== 432 432 433 433 If you want to deploy your the BNF Tools you can use the deployment as plugin: … … 435 435 Rightclick your xTextProject, choose__export__, choose__Plug-in development --> Deployable plug-ins and fragments__, choose all parts of the project, *.ebnf *.ebnf.tests *.ebnf.ui and a directory. After you finish this will generate a jar for every one of the choosen projects. Add these to the pluigin-folder of a eclipse and it should be installed 436 436 437 '''Deployment as RCP: ''' 437 == Deployment as RCP: == 438 438 439 439 If you want to create a Rich client platform for a standalone minimal worbench setup with only your plugin an requiered plugins in it RCP is a good choice (This is for an eclipse 3.x RCP).