TaxonomicEditorImplementation » History » Revision 5
« Previous |
Revision 5/20
(diff)
| Next »
Pepe Ciardelli, 03/26/2008 10:47 AM
- Table of contents
- Taxonomic Editor Implementation
Taxonomic Editor Implementation¶
This page is a technological overview of the implementation of the TaxonomicEditor.
A list of resources - tutorials, code snippets, etc. - can be found under EclipseRCPResources.
Technology¶
Eclipse Rich Client Platform (RCP) - the Java framework upon which the Taxonomic Editor will be built. It exposes to the developer the libraries for all graphic and interactive elements used within the Eclipse IDE. For more information, see the Eclipse website.
Important libraries of the RCP include:
org.eclipse.ui - the basic building blocks of an Eclipse UI - windows, views, menus, and toolbars - which are extended by the developer within the context of an Eclipse Plug-In Project
org.eclipse.swt - the Eclipse Standard Widget Toolkit, which provides GUI elements and basic layouts
org.eclipse.jface - helper classes for UI development, such as viewers; contains components for implementing an MVC framework
org.eclipse.ui.forms - offers a "Web-like", more modern look for SWT widgets, and puts font, headings, and colors in a managed form object that makes things like re-drawing all the elements on a page simpler. Also includes a nice master-detail framework used for the freetext-form implementation.
SWT Designer - a plug-in for the Eclipse IDE that provides a graphic, drag-and-drop interface for GUI development and rapid UI prototyping, as well as some support for data binding. We have purchased 10 academic licenses; if you are interested in using SWT Designer in the course of the project, please contact me at p.ciardelli@bgbm.org. For more information, visit the SWT Designer website
Technical requirements - Eclipse version 3.3.0 ("Equinox"), with Compiler Compliance (Windows -> Preferences -> Java -> Compiler) set to 5.0 and on-board Java Runtime Environment (Windows -> Preferences -> Java -> Installed JREs) set to 1.5. The settings ensure compliance with the CDM Java libraries.
Java Web Start¶
http://java.sun.com/products/javawebstart/
Deploying eclipse based application with Java Web Start
Note that all plug-ins must be signed since the application needs full permission from the client. We use the keytool application that comes with the JDK, via a keytool plugin In addition, the Eclipse used for development must run on a Java SDK instead of a JRE. If this constraint is not satisfied, the jar signing will fail.
Updated by Pepe Ciardelli about 16 years ago · 5 revisions