Update history
-
-
- 17/11/11 -
- Third BETA released, overhauled to take advantage of new compiler features. Tag-based scoping for better performance. +
- 18/11/11 +
- Third BETA (1.1.0.x) released, overhauled to take advantage of new compiler features. Tag-based scoping with caching for better performance. Interactive console (GF Shell) for luanch configs.
- 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. +
- Second BETA (1.0.0.x) 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. @@ -96,8 +100,8 @@
- The plugin makes use of the newest GF features, and requires the latest developer version of GF to be installed on your system. -
- Paths to GF must be set within the plugin, meaning: +
- The plugin makes use of the newest GF features, and requires the latest developer version of GF to be installed on your system (instructions here). +
- Paths to GF must be set within the plugin (see below). This means:
- you don’t necessarily need to have GF in your
PATHenvironment variable
@@ -187,7 +191,7 @@ files and manually add them to your Eclipse workspace. To experiment with some o
- The in-editor validation often needs to be triggered/updated by a keystroke. So if you can still see errors which you believe should be correct, try adding a space character to ensure the validation has been re-triggered. -
- Validation expects to have the project’s Build Automatically option checked (turned on). -
- Sometimes you may get an entire file marked with errors, even though in fact there is only a single error which is causing the internal builder to fail. In such cases referring to the Problems view should help you locate the cause. This issue is particularly relevant when changes made to one module may induce errors in its descendants (e.g. renaming a parameter in a resource module). This behaviour will hopefully be improved in future versions. -
-
Usage hints
+Usage hints & issues
Consoles
@@ -205,6 +209,14 @@ files and manually add them to your Eclipse workspace. To experiment with some oYou can set the log verbosity from Window → Preferences → Grammatical Framework. This setting also affects the verbosity of the log file
+gfep.log.Validation
+ +For validation to work correctly, the project’s Build Automatically option should be turned on.
+ +The in-editor validation sometimes needs to be triggered/updated by a keystroke. If you can still see errors which you believe should be correct, try adding a space character to ensure the validation is re-triggered.
+ +Sometimes you may get an entire file marked with errors, even though in fact there is only a single error which is causing the internal builder to fail. In such cases referring to the Problems view should help you locate the cause. This issue is particularly relevant when changes made to one module may induce errors in its descendants (e.g. renaming a parameter in a resource module). This behaviour will hopefully be improved in future versions.
+
Evaluation & feedback
@@ -212,14 +224,6 @@ files and manually add them to your Eclipse workspace. To experiment with some oPlease try to use the plugin for developing your own GF projects and report any issues you come up against. Do not hesitate to contact me on
-john.j.camilleriat domainchalmers.seand let me know how you think the plugin can be improved.Notes
- --
-
Criteria
As part of the evaluation of the GF Eclipse Plugin, feedback (both negative and positive) on the following would be appreciated:
- you don’t necessarily need to have GF in your
System requirements
-
-