forked from GitHub/gf-core
GFEP: update readme for 1.5.2 release
This commit is contained in:
@@ -10,13 +10,13 @@
|
||||
<body>
|
||||
|
||||
<h1 id="the-gf-eclipse-plugin">The GF Eclipse Plugin</h1>
|
||||
<p>John J. Camilleri<br />Updated: 10 January 2013</p>
|
||||
<p>John J. Camilleri<br />Updated: 11 January 2013</p>
|
||||
<p><em>The research leading to these results has received funding from the European Union'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>
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<p>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 <a href="http://www.grammaticalframework.org/demos/gfse/">GF Web IDE</a>). 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.</p>
|
||||
<p>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 requires some manual installation and configuration on the development machine.</p>
|
||||
<h3 id="license">License</h3>
|
||||
<p>The GF Eclipse Plugin is open-source under the <strong><a href="http://www.gnu.org/licenses/gpl-3.0.txt">GNU General Public License (GPL)</a></strong>.<br /><em>The licenses that cover the rest of GF are listed <a href="http://www.grammaticalframework.org/LICENSE">here</a>.</em><br /><em>Note that Xtext and Eclipse are released under the <a href="http://www.eclipse.org/legal/epl-v10.html">Eclipse Public License (EPL)</a>.</em></p>
|
||||
<p>The GF Eclipse Plugin is open-source under the <strong><a href="http://www.gnu.org/licenses/gpl-3.0.txt">GNU General Public License (GPL)</a></strong>.<br /><em>The licenses that cover the rest of GF are listed <a href="http://www.grammaticalframework.org/LICENSE">here</a>.</em> <em>Xtext and Eclipse are released under the <a href="http://www.eclipse.org/legal/epl-v10.html">Eclipse Public License (EPL)</a>.</em></p>
|
||||
<h3 id="links">Links</h3>
|
||||
<ul>
|
||||
<li>This document shall contain all collected information about the plugin. The most up-to-date version of this file can always be found <a href="https://github.com/GrammaticalFramework/gf-eclipse-plugin/blob/master/README.md">here</a></li>
|
||||
@@ -49,7 +49,7 @@
|
||||
<li>External library browser</li>
|
||||
</ul>
|
||||
<h2 id="release-history">Release history</h2>
|
||||
<p><strong>10/01/13</strong> : (1.5.2.x) New option for specifying build files.</p>
|
||||
<p><strong>11/01/13</strong> : (1.5.2.x) New option for specifying build files.</p>
|
||||
<p><strong>12/06/12</strong> : (1.5.1.x) Support for scoping when library sources not available. Performance and implementational improvements to External Library View.</p>
|
||||
<p><strong>19/04/12</strong> : (1.5.0.x) Removed need for <code>.gfexternal</code> folder. Much improved "External Libraries" 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.</p>
|
||||
<p><strong>04/04/12</strong> : (1.4.3.x) Improvements to the Test Manager. Added support for arbitrary commands in launch. Made the license information clearer.</p>
|
||||
@@ -106,7 +106,7 @@
|
||||
<li>You can also adjust the verbosity level of the GFEP console log in the preferences window.</li>
|
||||
</ol>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-preferences.png" alt="Plugin preferences window" /><p class="caption">Plugin preferences window</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-preferences.png" alt="Plugin preferences window" /><p class="caption">Plugin preferences window</p>
|
||||
</div>
|
||||
<h3 id="updating-the-plugin">Updating the plugin</h3>
|
||||
<ol style="list-style-type: decimal">
|
||||
@@ -139,8 +139,9 @@
|
||||
<h4 id="specifying-build-files-guided-build">Specifying build files (guided build)</h4>
|
||||
<p>As of GFEP ≥ 1.5.2, you are now able to explicitly which modules in your GF project should be built by the builder. This would normally contain your "top-level" modules. This can be done right-clicking on your project in the Project Explorer and choosing <strong>Properties → GF Build Settings</strong>. From here you simply tick which modules in your project the GF builder should compile:</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-project-build-settings.png" alt="Project-specific build settings" /><p class="caption">Project-specific build settings</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-project-build-settings.png" alt="Project-specific build settings" /><p class="caption">Project-specific build settings</p>
|
||||
</div>
|
||||
<p>When doing this, GFEP will never attempt to compile any other files in the project. Whenever you add a new top-level module or change your module hierarchy, be sure to check these build settings again.</p>
|
||||
<!----------------------------------------------------------------------------->
|
||||
|
||||
<h2 id="getting-started">Getting started</h2>
|
||||
@@ -175,33 +176,33 @@
|
||||
<p>These can be removed manually at any time, as they will always be regenerated as necessary. You will probably want to ignore these directories in your version control system.</p>
|
||||
<h3 id="create-a-new-gf-project">Create a new GF Project</h3>
|
||||
<p>If you have a folder in your workspace which you want to convert into a GF Project, then you can select it from the drop-down. This folder will then appear as an Eclipse project in your workspace.</p>
|
||||
<p><img src="http://www.grammaticalframework.org/eclipse/images/eclipse-projectwizard-1.png" alt="New project wizard" /> <img src="http://www.grammaticalframework.org/eclipse/images/eclipse-projectwizard-2.png" alt="New project wizard" /></p>
|
||||
<p><img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-projectwizard-1.png" alt="New project wizard" /> <img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-projectwizard-2.png" alt="New project wizard" /></p>
|
||||
<h3 id="new-module-wizard">New module wizard</h3>
|
||||
<p>Use the <strong>GF Module</strong> wizard from <strong>File → New → Other → GF Module</strong>:</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-modulewizard-1.png" alt="New module wizard" /><p class="caption">New module wizard</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-modulewizard-1.png" alt="New module wizard" /><p class="caption">New module wizard</p>
|
||||
</div>
|
||||
<p>You can find some small examples <a href="https://github.com/GrammaticalFramework/gf-eclipse-plugin/tree/master/workspace-demo/GF%20Project">here</a>. Download the files and manually add them to your Eclipse workspace to experiment with some of the plugin features.</p>
|
||||
<h3 id="clone-module-wizard">Clone module wizard</h3>
|
||||
<p>If you want to clone an existing module into a new language, you can now do so via the <strong>Clone GF Module</strong> wizard. This is also available as a context menu option in the <strong>Project Explorer</strong>, via <strong><Right click> → Grammatical Framework → Compile for new language</strong>:</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-clonewizard.png" alt="Clone GF module to new language wizard" /><p class="caption">Clone GF module to new language wizard</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-clonewizard.png" alt="Clone GF module to new language wizard" /><p class="caption">Clone GF module to new language wizard</p>
|
||||
</div>
|
||||
<p>This will create and open a new module with the relevant replacements made. Note how in this case string constants are replaced by the empty string <code>""</code>. This wizard currently only works on <code>concrete</code> and <code>instance</code> modules.</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-clonewizard-newfile.png" alt="Newly cloned file" /><p class="caption">Newly cloned file</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-clonewizard-newfile.png" alt="Newly cloned file" /><p class="caption">Newly cloned file</p>
|
||||
</div>
|
||||
<h3 id="workbench-editor-layout">Workbench editor layout</h3>
|
||||
<p>Use Eclipse' own features to drag and drop your editor tabs to suit your needs.</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-editor-general.png" alt="The editor and outline view" /><p class="caption">The editor and outline view</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-editor-general.png" alt="The editor and outline view" /><p class="caption">The editor and outline view</p>
|
||||
</div>
|
||||
<h3 id="outline-view">Outline view</h3>
|
||||
<p>The <strong>Outline</strong> view in the bottom-left offers a quite overview of your module structure. Clicking any of the terms will make your cursor jump to that point in the file.</p>
|
||||
<h3 id="cross-referencing-errors-and-warnings">Cross-referencing errors and warnings</h3>
|
||||
<p>Notice how changing a <code>cat</code> definition for example will produce warnings and/or errors in other the modules.</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-editor-cat.png" alt="Warnings and errors in the editor" /><p class="caption">Warnings and errors in the editor</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-editor-cat.png" alt="Warnings and errors in the editor" /><p class="caption">Warnings and errors in the editor</p>
|
||||
</div>
|
||||
<h3 id="validation">Validation</h3>
|
||||
<p>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.</p>
|
||||
@@ -210,20 +211,20 @@
|
||||
<p>For validation to work correctly, the project's <strong>Build Automatically</strong> option should be turned on. Each time you save a file (or some other change occurs in your project), the builder should get triggered which re-compiles any GF files which have changed. If the builder does not seem to get triggered, try to run a <em>clean</em> via <strong>Project → Clean...</strong></p>
|
||||
<h3 id="code-formatting">Code formatting</h3>
|
||||
<p>Use the built-in code formatter to tidy your code automatically. Right-click in the editor and choose <strong>Format</strong> or use the keyboard shortcut <strong>Ctrl+Shift+F</strong>.</p>
|
||||
<p><img src="http://www.grammaticalframework.org/eclipse/images/eclipse-before-format.png" alt="Before auto-formatting" /> <img src="http://www.grammaticalframework.org/eclipse/images/eclipse-after-format.png" alt="After auto-formatting" /></p>
|
||||
<p><img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-before-format.png" alt="Before auto-formatting" /> <img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-after-format.png" alt="After auto-formatting" /></p>
|
||||
<h3 id="syntax-highlighting">Syntax highlighting</h3>
|
||||
<p>You can change your syntax colouring styles as you wish from <strong>Preferences → Grammatical Framework → Syntax Coloring</strong></p>
|
||||
<p>You can change your syntax colouring styles as you wish from <strong>Preferences → Grammatical Framework → Syntax Colouring</strong></p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-syntaxcoloring.png" alt="Syntax highlighting styles" /><p class="caption">Syntax highlighting styles</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-syntaxcoloring.png" alt="Syntax highlighting styles" /><p class="caption">Syntax highlighting styles</p>
|
||||
</div>
|
||||
<h3 id="launch-configurations">Launch configurations</h3>
|
||||
<p>Set up a launch configuration from <strong>Run → Run Configurations... → Grammatical Framework</strong>. You will see the dialog below with some fields automatically filled in for you.</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-launchconfig.png" alt="Launch configuration dialog" /><p class="caption">Launch configuration dialog</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-launchconfig.png" alt="Launch configuration dialog" /><p class="caption">Launch configuration dialog</p>
|
||||
</div>
|
||||
<p>Run the launch config and you will see the output from the GF compiler in the console view within Eclipse.</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-compileroutput.png" alt="Output from the GF compiler" /><p class="caption">Output from the GF compiler</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-compileroutput.png" alt="Output from the GF compiler" /><p class="caption">Output from the GF compiler</p>
|
||||
</div>
|
||||
<h4 id="run-as...-launch-shortcut">Run As... launch shortcut</h4>
|
||||
<p>Using the <strong>Run → Run As → Compile with GF</strong> shortcut will take the current selection or active editor and do one of two things:</p>
|
||||
@@ -236,18 +237,18 @@
|
||||
<p>Additionally, every time a grammar is <strong>Run</strong> a <em>new</em> console is opened to display the output. This console may also serve as the interactive GF Shell, depending on the <strong>Interactive Mode</strong> checkbox in your <strong>Run Configuration</strong>.</p>
|
||||
<p>Eclipse does not make it obvious when multiple console windows open; click on the <strong>Display Selected Console</strong> button to switch between open consoles:</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-console-icon.png" alt="Display Selected Console icon" /><p class="caption">Display Selected Console icon</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-console-icon.png" alt="Display Selected Console icon" /><p class="caption">Display Selected Console icon</p>
|
||||
</div>
|
||||
<p>If the process associated with a console window has terminated, it will be indicated in the upper-left corner as below. Such console windows can then be closed using the grey cross button:</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-console-terminated.png" alt="Close terminated console icon" /><p class="caption">Close terminated console icon</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-console-terminated.png" alt="Close terminated console icon" /><p class="caption">Close terminated console icon</p>
|
||||
</div>
|
||||
<p><em>The Eclipse console implementation does not support command history (up arrow) or auto-completion (tab).</em></p>
|
||||
<h3 id="external-libraries-view"><em>External Libraries</em> view</h3>
|
||||
<p>This view is automatically populated with a list of all the external modules referenced by the current file. Double-clicking on any item provides a quick way of opening GF files which are imported into your grammar from outside your Eclipse project, for example the GF Resource Grammar Library.</p>
|
||||
<p>This view also provides a text box for searching within the current module's scope, as shown in the image below. Clicking the small arrow on the right-hand side of the view provides options for case sensitive and/or regular-expression based search.</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-external-libraries.png" alt="External libraries view" /><p class="caption">External libraries view</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-external-libraries.png" alt="External libraries view" /><p class="caption">External libraries view</p>
|
||||
</div>
|
||||
<h3 id="test-manager-view"><em>Test Manager</em> view</h3>
|
||||
<p>This feature works together with the launch configurations to make the process of running regression tests on your grammars quick and easy. As described in the <a href="http://www.grammaticalframework.org/gf-book/">GF Book</a> (Section 10.5), the general development-test cycle (independent of GFEP) is as follows:</p>
|
||||
@@ -259,12 +260,31 @@
|
||||
</ol>
|
||||
<p>The <strong>Test Manager</strong> view follows this same pattern but provides a convenient graphical interface for running your test cases and also for looking at the output, just using a few clicks:</p>
|
||||
<div class="figure">
|
||||
<img src="http://www.grammaticalframework.org/eclipse/images/eclipse-test-manager.png" alt="Test Manager view" /><p class="caption">Test Manager view</p>
|
||||
<img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/eclipse-test-manager.png" alt="Test Manager view" /><p class="caption">Test Manager view</p>
|
||||
</div>
|
||||
<p>Note that GFEP assumes the following convention:</p>
|
||||
<p><code>*.trees</code> or <code>*.sentences</code> : Test input files: trees file (for testing linearisation) and sentences file (for testing parsing)</p>
|
||||
<p><code>*.trees.out</code> or <code>*.sentences.out</code> : Corresponding output files (generated each time a test is run)</p>
|
||||
<p><code>*.trees.gold</code> or <code>*.sentences.gold</code> : Corresponding gold standard files (manually corrected from an output file)</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Extension</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><code>*.trees</code> or <code>*.sentences</code></td>
|
||||
<td align="left">Test input files: trees file (for testing linearisation) and sentences file (for testing parsing)</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><code>*.trees.out</code> or <code>*.sentences.out</code></td>
|
||||
<td align="left">Corresponding output files (generated each time a test is run)</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><code>*.trees.gold</code> or <code>*.sentences.gold</code></td>
|
||||
<td align="left">Corresponding gold standard files (manually corrected from an output file)</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="logs">Logs</h3>
|
||||
<p>The GFEP writes to the Eclipse platform log. This can be accessed in two ways:</p>
|
||||
<ol style="list-style-type: decimal">
|
||||
@@ -301,13 +321,40 @@
|
||||
<p>In both cases make sure you get the correct version of Xtext (see below). Once you have Xtext set up, you can clone the repository locally with the following command:</p>
|
||||
<pre><code>git clone git://github.com/GrammaticalFramework/gf-eclipse-plugin.git</code></pre>
|
||||
<p>You can then add the projects under the <code>workspace</code> directory to your Eclipse workspace, by using the <strong>File → Import...</strong> wizard. The individual projects are:</p>
|
||||
<p><strong><code>org.grammaticalframework.eclipse</code></strong> : Main plugin which covers all parsing and linking behaviour.</p>
|
||||
<p><strong><code>org.grammaticalframework.eclipse.ui</code></strong> : Covers all UI aspects of the plugin. Depends on <code>org.grammaticalframework.eclipse</code> (but the opposite is not true).</p>
|
||||
<p><strong><code>org.grammaticalframework.eclipse.tests</code></strong> : Contains unit tests for the plugin. Not required for running the plugin.</p>
|
||||
<p><strong><code>org.grammaticalframework.eclipse.ontology-grammar</code></strong> : GF Ontology Grammar Plugin for Eclipse, developed separately by Ontotext AD.</p>
|
||||
<p><strong><code>org.grammaticalframework.feature</code></strong> : Feature project for the GF Eclipse Plugin. Exports <code>org.grammaticalframework.eclipse</code> and <code>org.grammaticalframework.eclipse.ui</code>.</p>
|
||||
<p><strong><code>org.grammaticalframework.feature.ontology-grammar</code></strong> : Feature project for the GF Ontology Grammar Plugin. Exports <code>org.grammaticalframework.eclipse.ontology-grammar</code>.</p>
|
||||
<p><strong><code>org.grammaticalframework.updatesite</code></strong> : Update site project which exports both feature projects under the same category.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Namespace</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><code>org.grammaticalframework.eclipse.ui</code></td>
|
||||
<td align="left">Covers all UI aspects of the plugin. Depends on <code>org.grammaticalframework.eclipse</code> (but the opposite is not true).</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><code>org.grammaticalframework.eclipse.tests</code></td>
|
||||
<td align="left">Contains unit tests for the plugin. Not required for running the plugin.</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><code>org.grammaticalframework.eclipse.ontology-grammar</code></td>
|
||||
<td align="left">GF Ontology Grammar Plugin for Eclipse, developed separately by Ontotext AD.</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><code>org.grammaticalframework.feature</code></td>
|
||||
<td align="left">Feature project for the GF Eclipse Plugin. Exports <code>org.grammaticalframework.eclipse</code> and <code>org.grammaticalframework.eclipse.ui</code>.</td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><code>org.grammaticalframework.feature.ontology-grammar</code></td>
|
||||
<td align="left">Feature project for the GF Ontology Grammar Plugin. Exports <code>org.grammaticalframework.eclipse.ontology-grammar</code>.</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><code>org.grammaticalframework.updatesite</code></td>
|
||||
<td align="left">Update site project which exports both feature projects under the same category.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h4 id="extra-dependencies-for-unit-testing-project">Extra dependencies for unit testing project</h4>
|
||||
<p>The unit testing project (<code>org.grammaticalframework.eclipse.tests</code>) has an extra requirement for the library <code>org.eclipselabs.xtext.utils.unittesting</code>, which you will probably get complaints about when importing your projects into Eclipse. You only need to worry about this if you want to run the unit tests; otherwise you can ignore these errors. You can get more information about this library <a href="http://code.google.com/a/eclipselabs.org/p/xtext-utils/wiki/Unit_Testing">here</a>, or just install it in Eclipse directly using the following update site URL: <a href="http://xtext-utils.eclipselabs.org.codespot.com/git.distribution/releases/unittesting-0.9.x/">http://xtext-utils.eclipselabs.org.codespot.com/git.distribution/releases/unittesting-0.9.x/</a></p>
|
||||
<h4 id="xtext-version">Xtext version</h4>
|
||||
@@ -355,37 +402,37 @@ sudo apt-get install gtk2-engines-pixbuf</code></pre>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><img src="http://www.grammaticalframework.org/eclipse/images/module-abstract.png" /></td>
|
||||
<td align="left"><img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/module-abstract.png" /></td>
|
||||
<td align="left">Abstract module</td>
|
||||
<td align="left"><code>abstract Foods = {...}</code></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="http://www.grammaticalframework.org/eclipse/images/module-concrete.png" /></td>
|
||||
<td align="left"><img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/module-concrete.png" /></td>
|
||||
<td align="left">Concrete module</td>
|
||||
<td align="left"><code>concrete FoodsEng of Foods = {...}</code></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><img src="http://www.grammaticalframework.org/eclipse/images/module-resource.png" /></td>
|
||||
<td align="left"><img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/module-resource.png" /></td>
|
||||
<td align="left">Resource module</td>
|
||||
<td align="left"><code>resource ResFoods = {...}</code></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="http://www.grammaticalframework.org/eclipse/images/module-interface.png" /></td>
|
||||
<td align="left"><img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/module-interface.png" /></td>
|
||||
<td align="left">Interface</td>
|
||||
<td align="left"><code>interface LexFoods = {...}</code></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><img src="http://www.grammaticalframework.org/eclipse/images/module-instance.png" /></td>
|
||||
<td align="left"><img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/module-instance.png" /></td>
|
||||
<td align="left">Instance</td>
|
||||
<td align="left"><code>instance LexFoodsEng of LexFoods = {...}</code></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="http://www.grammaticalframework.org/eclipse/images/module-functor.png" /></td>
|
||||
<td align="left"><img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/module-functor.png" /></td>
|
||||
<td align="left">Functor</td>
|
||||
<td align="left"><code>incomplete concrete FoodsI of Foods = {...}</code></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><img src="http://www.grammaticalframework.org/eclipse/images/module-functor-instantiation.png" /></td>
|
||||
<td align="left"><img src="https://raw.github.com/GrammaticalFramework/gf-eclipse-plugin/master/doc/images/module-functor-instantiation.png" /></td>
|
||||
<td align="left">Functor instantiation</td>
|
||||
<td align="left"><code>concrete FoodsEng of Foods = FoodsI with (...) {...}</code></td>
|
||||
</tr>
|
||||
|
||||
Reference in New Issue
Block a user