ApCoCoA-1:Eclipse GUI: Difference between revisions
From ApCoCoAWiki
S schuster (talk | contribs) |
S schuster (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
==The Eclipse GUI Project | ==The Eclipse GUI Project: Goal of the Project== | ||
The overall goal of the project can be described as follows: | The overall goal of the project can be described as follows: | ||
To create a state of the art, platform independent Graphical User Interface for faster CoCoAL program and prototype development. | To create a state of the art, platform independent Graphical User Interface for faster CoCoAL program and prototype development. | ||
==Project Plan== | |||
==Scratchpad== | |||
Quick and dirty notes for myself, thought as a basis for extending to a proper developer documentation .... | |||
===General Links=== | |||
* http://help.eclipse.org/ganymede/index.jsp | |||
* http://www.eclipse.org/articles/Article-UI-Guidelines/Index.html and http://wiki.eclipse.org/User_Interface_Guidelines | |||
* http://blog.eclipse-tips.com/ | |||
===Commands=== | |||
Examples in our GUI: Starting external ApCoCoA process, sending CoCoAL code to esternal ApCoCoA process, history forward/back, starting Server. | |||
To add a command, extend these extension points in the plugin.xml: | |||
* org.eclipse.ui.commands: here just an ID together with other attributes (name, category,...) for a certain command is defined. | |||
* org.eclipse.ui.handlers: this is the link between the command ID and an actual handler, ie. a class that does something when the command is called. It is possible to implement more than one handler to a certain command and to determine certain conditions when to use which handler (elements <code>activeWhen</code> and <code>enabledWhen</code> | |||
* org.eclipse.ui.menues: here the actual visible menu and toolbar contributions are defined along with declarations, when they are visible, eg. they are visible when, say, an editor "is in a certain context". | |||
* org.eclipse.ui.contexts: this defines a context which is referenced by the visibility check of the menus, toolbars,... The context is set by the following code snippet in the class <code>ApCoCoAEditor</code>. | |||
IContextService contextService = (IContextService) getSite().getService(IContextService.class); | |||
contextService.activateContext("org.apcocoa.eclipse.contexts.ApCoCoA"); | |||
====Links==== | |||
* Good starting point: http://richclientplatform.blogspot.com/2007/07/new-menu-contribution-extension.html | |||
Just for redundancy, the previous link mentions among others the following links: | |||
* http://wiki.eclipse.org/Command_Core_Expressions | |||
* http://wiki.eclipse.org/Menu_Contributions | |||
* http://wiki.eclipse.org/Platform_Command_Framework | |||
* | |||
Revision as of 13:05, 12 February 2009
The Eclipse GUI Project: Goal of the Project
The overall goal of the project can be described as follows:
To create a state of the art, platform independent Graphical User Interface for faster CoCoAL program and prototype development.
Project Plan
Scratchpad
Quick and dirty notes for myself, thought as a basis for extending to a proper developer documentation ....
General Links
- http://help.eclipse.org/ganymede/index.jsp
- http://www.eclipse.org/articles/Article-UI-Guidelines/Index.html and http://wiki.eclipse.org/User_Interface_Guidelines
- http://blog.eclipse-tips.com/
Commands
Examples in our GUI: Starting external ApCoCoA process, sending CoCoAL code to esternal ApCoCoA process, history forward/back, starting Server.
To add a command, extend these extension points in the plugin.xml:
- org.eclipse.ui.commands: here just an ID together with other attributes (name, category,...) for a certain command is defined.
- org.eclipse.ui.handlers: this is the link between the command ID and an actual handler, ie. a class that does something when the command is called. It is possible to implement more than one handler to a certain command and to determine certain conditions when to use which handler (elements
activeWhenandenabledWhen - org.eclipse.ui.menues: here the actual visible menu and toolbar contributions are defined along with declarations, when they are visible, eg. they are visible when, say, an editor "is in a certain context".
- org.eclipse.ui.contexts: this defines a context which is referenced by the visibility check of the menus, toolbars,... The context is set by the following code snippet in the class
ApCoCoAEditor.
IContextService contextService = (IContextService) getSite().getService(IContextService.class);
contextService.activateContext("org.apcocoa.eclipse.contexts.ApCoCoA");
Links
- Good starting point: http://richclientplatform.blogspot.com/2007/07/new-menu-contribution-extension.html
Just for redundancy, the previous link mentions among others the following links:
