http://www.grammaticalframework.org/eclipse/release/The GF Eclipse Plugin
+ +The research leading to these results has received funding from the European Union’s Seventh Framework Programme (FP7/2007-2013) under grant agreement n° FP7-ICT-247914.
+ +Introduction
+ +The aim behind developing a desktop IDE for GF is to provide more powerful tools than may be possible and/or practical in a web-based environment (the GF Web IDE). In particular, the ability to resolve identifier cross-references and browse external libraries quickly during development time is one of the primary motivations for the project.
+ +The choice was made to develop this desktop IDE as a plugin for the Eclipse Platform as it emerged as the most popular choice among the GF developer community. Support for the platform is vast and many tools for adapting Eclipse to domain-specific languages already exist. Unlike the zero-click Web IDE approach, using the GF Eclipse plugin (GFEP) will require some manual installation and configuration on the development machine. Thus the GFEP is aimed more at seasoned developers rather than the curious GF newbie.
+ +The starting point for the GFEP is using the Xtext DSL Framework for Eclipse. By converting the GF grammar into the appropriate Extended-BNF form required by the LL(*) ANTLR parser, the framework provides a good starting point for future plugin development, already including a variery of syntax checking tools and some cross-reference resolution support. The specific requirements of the GF language, particularly in the way of its special module hierarchy, mean that significant customisations to this generated base plugin are needed.
+ +Who
+ +The GFEP is being developed as part of Work Package 2 of the MOLTO Project.
+ +Primary developer is John J. Camilleri, who should be contacted for all queries and feedback related to the plugin on john.j.camilleri at domain chalmers.se.
Links
+ +-
+
- This document shall contain the most up-to-date information about the plugin. The most up-to-date version of this file can always be found in the source-code repository at https://github.com/GrammaticalFramework/gf-eclipse-plugin/blob/master/README.markdown +
- This documentation is also available at the MOLTO Project Wiki. +
- Source code repository is at https://github.com/GrammaticalFramework/gf-eclipse-plugin (do not try to run the plugin from source; please only use the packaged releases). +
- Here are some example GF projects for testing out the plugin features. +
- Software update site URL for installing through Eclipse:
+
http://www.grammaticalframework.org/eclipse/release/
Update history
+ +-
+
- 16/11/11 +
- Third BETA released, using new tag-based scoping for better performance. + +
- 11/10/11 +
- Second BETA released, with improved support for qualified names, local variable bindings, selective inheritance, module outlining, and launch configurations. Also new GF Project type. + +
- 01/10/11 +
- Initial BETA released. + +
- 20/09/11 +
- Refactoring of grammar to provide neater syntax trees, and handle cross-referencing contraints. Major work on name resolution across modules, implementing custom
Scoping,Naming,ResourceDescriptionimplementations.
+
+ - 08/09/11 +
- Successfully converted GF language grammar into ANTLR-compaticble format. Refactoring to avoid left-recursion took up the majority of this time so far. + +
- Late August 2011 +
- Started investigation the use of Xtext as a basis for building the Eclipse plugin. Xtext requires a EBNF-style language grammar in order to generate development tools as a plugin for the Eclipse IDE. +
+ +
Features
+ +Implemented (or partially implemented)
+ +-
+
- Syntax highlighting and error detection +
- Code folding, quick block-commenting, automatic code formatting +
- Definition outlining, jump to declaration, find usage +
- Warnings for problems in module dependancy hierarchy +
- Launch configurations, i.e. compilation directly from IDE +
- Auto-completion for declared identifiers +
Near-term
+ +-
+
- Inline documentation for function calls, overloads +
- Quick-fix suggestions for syntax and naming errors +
- Code generation for concrete/instance modules +
- Code generation for new languages in application grammars +
- Grouping of concrete syntaxes by language, fast switching and linked navigation +
- Built-in library browser (in particular for GF resource grammar library) +
Long-term goals
+ +-
+
- Test-suite functionality +
- Treebank management and testing +
- Provide a single platform for developing and using embedded grammars +
- Integration with ontology engineering tools +
Known issues
+ +-
+
- The in-editor validation often needs to be triggered by a keystroke. +
Other remarks
+ +-
+
- Interface decisions such as icons were made reltively hastily and may not be entirely suitable or intuitive. +This will get better as the plugin gets used by more users (and provide feedback). +
- A wiki or bug tracker may be set up if there is enough usage feedback to justify it. +
+ +
Installation & updating
+ +System requirements
+ +-
+
- The plugin was developed using Eclipse 3.7, and has not been tested with older versions of Eclipse. +
- GFEP makes use of the newest GF features, and requires that the latest developer version of GF is already installed on your system. Paths to GF must be set within the Eclipse plugin (meaning you don’t necessarily need to have GF in your
PATHenvironment variable).
+
Installing the plugin for the first time
+ +-
+
- Inside Eclipse, go to Help → Install New Software. +
- Add new software site using the URL:
http://www.grammaticalframework.org/eclipse/release/
+ - Select the GF Eclipse Plugin, click Next, accept the license agreement and install. +
- Accept the prompt warning that the software is unsigned. +
- Restart Eclipse when prompted. +
Settings
+ +-
+
- Add the GF perspective by clicking Open Perspective → Other and choosing GF. +
- Set your paths to the GF executable and libraries by going to Window → Preferences → Grammatical Framework.
+The runtime path is assumed to be~/.cabal/bin/gf, which may be wrong depending on your +system and how you installed GF.
+The library path should get automatically set from your environment’sGF_LIB_PATHvariable.
+
Updating the plugin
+ +-
+
- In Eclipse, go to Help → Check for updates. +
- Any available updates will appear in the dialog. Select them and follow the usual steps. +
+ +
Getting started
+ +Some steps you can follow to get a feel of of the plugin’s features.
+ +-
+
- Create a new GF Project. +
+
-
+
- Create some new modules using the GF Module wizard from File > New > Other > GF Module: +
If asked whether you want to add the Xtext nature to your project, you can safely say No (this prompt has been removed in newer versions).
+ +-
+
You can find some small examples at http://www.grammaticalframework.org/eclipse/examples/. Download the +files and manually add them to your Eclipse workspace. To experiment with some of the plugin features.
+Use Eclipes’ own features to drag and drop your editor tabs to suit your needs. Notice the Outline view in the bottom-right offers a quite overview of your module structure. Clicking any of the terms will make your cursor jump to that point in the file.
+
-
+
- Note how changing a
catdefinition for example will produce warnings and/or errors in other the modules.
+
-
+
- Use the built-in code formatter to tidy your code automatically. Right-click in the editor and choose Format or use the keyboard shortcut Ctrl+Shift+F. +
-
+
- Set up a launch configuration from Run → Run Configurations… → Grammatical Framework. You will see the dialog below with some fields automatically filled in for you. +
-
+
- Run the launch config and you will see the output from the GF compiler in the console view within Eclipse. +
+ +
Feedback
+ +As part of the evaluation of the GF Eclipse Plugin, feedback (both negative and positive) on the following would be appreciated:
+ +-
+
- Issues encountered with installation +
- Incorrect support of GF syntactic constructs, module hierarchy system +
- Performance issues (speed, resources footprint) +
- General intuitiveness of the UI +
- Feature wish-list +
- Compatibilities / conflicts with other Eclipse plugins +