diff --git a/eclipse/index.html b/eclipse/index.html index f1dde3234..d6bde4335 100644 --- a/eclipse/index.html +++ b/eclipse/index.html @@ -1,7 +1,7 @@

The GF Eclipse Plugin

John J. Camilleri
-Updated: 23 Jan 2012

+Updated: 31 Jan 2012

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.

@@ -70,6 +70,12 @@ Updated: 23 Jan 2012

Major release history

+
31/01/12
+
(1.2.5.x) Hugely improved scoping performance. New “Clone to new language” wizard. Improved code formatting. More efficient builder.
+ +
23/01/12
+
(1.2.4.x) Logging is now done to the Eclipse Platform Log (use “Error Log” view). Tested with Eclipse 3.6.2. Bug fixes.
+
11/01/12
(1.2.3.x) Updated to use Xtext 2.1.0. Links to external files now moved into new “GF Library View”.
@@ -84,15 +90,6 @@ Updated: 23 Jan 2012

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, ResourceDescription implementations.
- -
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.
@@ -127,7 +124,7 @@ Updated: 23 Jan 2012

  1. Inside Eclipse, go to Help → Install New Software.
    2. -
  2. Add new software site using the URL: http://www.grammaticalframework.org/eclipse/release/
    3. +
  3. Add new software site using the URL: http://www.grammaticalframework.org/eclipse/release/
  4. Select the GF Eclipse Plugin, and make sure the Contact all update sites during install to find required software option is checked.
  5. Click Next, accept the license agreement and install.
  6. Accept the prompt warning that the software is unsigned.
    7. @@ -158,6 +155,32 @@ system and how you installed GF.
  7. If your project has a folder named (External) you can safely delete this via the Eclipse Project Explorer. It is no longer used in GFEP >= 1.2.3
    8. +

    Project settings

    + +

    Although the plugin should take care of your project settings for you, in case anything gets messed up you can always correct them manually as follows:

    + +

    Project nature

    + +

    Your .project file should include the GF Project Nature as follows:

    + +
    <natures>
+  <nature>org.grammaticalframework.eclipse.ui.natures.projectNatureID</nature>
+</natures>
+
    + +

    Builder

    + +

    Your .project file should include the GF Builder as follows:

    + +
    <buildSpec>
+  <buildCommand>
+      <name>org.grammaticalframework.eclipse.ui.build.GFBuilderID</name>
+      <arguments>
+      </arguments>
+  </buildCommand>
+</buildSpec>
+
    +

    Getting started

    @@ -233,7 +256,7 @@ files and manually add them to your Eclipse workspace to experiment with some of

    Logs

    -

    You can set the log verbosity from Window → Preferences → Grammatical Framework. This setting also affects the verbosity of the log file gfep.log.

    +

    You can set the log verbosity from Window → Preferences → Grammatical Framework.

    Validation

    @@ -268,4 +291,9 @@ files and manually add them to your Eclipse workspace to experiment with some of

    Logs

    -

    The GFEP writes a log file in your Eclipse workspace folder, self-evidently named gfep.log. When things go wrong it may be useful to consult this file, or even send it as part of any feedback you provide.

    +

    The GFEP writes to the Eclipse platform log. This can be accessed in two ways:

    + +
      +
    1. By opening the Error Log view in Eclipse
      2. +
    2. Accessing the file directly at workspace/.metadata/.log
      3. +