GitHub/gf-core
1
0
Fork 1
mirror of https://github.com/GrammaticalFramework/gf-core.git synced 2026-04-09 04:59:31 -06:00
Code Issues Packages Projects Releases Wiki Activity

GFEP: updated readme

Browse Source
This commit is contained in:
john.j.camilleri
2012-06-12 11:04:59 +00:00
parent 8f53e010d1
commit b7347b1fef
2 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
eclipse/images/eclipse-preferences.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 74 KiB

14
eclipse/index.html
View File

@@ -11,7 +11,7 @@
<h1>The GF Eclipse Plugin</h1>
<p>John J. Camilleri<br />
Updated: 11 June 2012</p>
Updated: 12 June 2012</p>
<p><em>The research leading to these results has received funding from the European Union&#8217;s Seventh Framework Programme (FP7/2007-2013) under grant agreement no. FP7-ICT-247914 (the <a href="http://www.molto-project.eu/">MOLTO Project</a>).</em></p>
@@ -67,6 +67,9 @@ Updated: 11 June 2012</p>
<h2>Release history</h2>
<dl>
<dt><strong>12/06/12</strong></dt>
<dd>(1.5.1.x) Support for scoping when library sources not available. Performance and implementational improvements to External Library View.</dd>
<dt><strong>19/04/12</strong></dt>
<dd>(1.5.0.x) Removed need for <code>.gfexternal</code> folder. Much improved &#8220;External Libraries&#8221; view allows you to search in current scope. Memory usage improvements in scoping implementation. Validation now occurs on file open. Re-added GF Library Path field in preferences.</dd>
@@ -155,12 +158,15 @@ Updated: 11 June 2012</p>
<ol>
<li>Add the GF perspective by clicking <strong>Window &rarr; Open Perspective &rarr; Other</strong> and choosing <strong>GF</strong>.</li>
<li>The plugin will try to determine the path to your GF executable automatically. You can check/overwrite it by going to <strong>Preferences &rarr; Grammatical Framework</strong>.
This path should include the name of the GF binary itself, e.g. <code>/home/john/.cabal/bin/gf</code> or <code>C:\Users\John\GF\gf.exe</code>.</li>
<li>By default, the <em>Library path</em> setting is set to <code>.:alltenses:prelude</code>. This is passed to GF using the <code>--path</code> flag.</li>
<li>Open the plugin settings by going to <strong>Preferences &rarr; Grammatical Framework</strong> (image below).</li>
<li>The plugin will try to determine the path to your GF executable automatically, but this may need to be corrected. The path should include the name of the GF binary itself, e.g. <code>/home/john/.cabal/bin/gf</code> or <code>C:\Users\John\GF\gf.exe</code>.</li>
<li>The <em>Additional path directive</em> setting can be used if you want to avoid writing <code>--# -path=...</code> directives in your source files. By default it is set to <code>.:alltenses:prelude</code>, but can also be left blank. This is passed to GF using the <code>--path</code> flag.</li>
<li>If you are using pre-compiled version of the Resource Grammar Library (i.e. you didn&#8217;t build them yourself from source) <em>but</em> you still have the sources available on your system, then you can enter to that path here. This is optional and is only used for jumping to source definitions. You should enter the absolute system path up to and including the <code>src</code> folder, e.g. <code>/home/john/GF/lib/src/</code>.</li>
<li>You can also adjust the verbosity level of the GFEP console log in the preferences window.</li>
</ol>
<p><img src="http://www.grammaticalframework.org/eclipse/images/eclipse-preferences.png" alt="Plugin preferences window" /></p>
<h3>Updating the plugin</h3>
<ol>