Project

General

Profile

TaxonomicEditorImplementation » History » Version 6

Pepe Ciardelli, 03/26/2008 11:38 AM

1 1 Pepe Ciardelli
{{>toc}}
2
3
4
5
6
----
7
8
9 2 Pepe Ciardelli
# Taxonomic Editor Implementation
10 1 Pepe Ciardelli
11 2 Pepe Ciardelli
This page is a technological overview of the implementation of the [[TaxonomicEditor]].
12 1 Pepe Ciardelli
13
14 2 Pepe Ciardelli
A list of resources - tutorials, code snippets, etc. - can be found under [[EclipseRCPResources]].
15 1 Pepe Ciardelli
16
17
18
## Technology
19
20
 **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](http://www.eclipse.org/eclipse/platform-ui/) website.
21
22
23
Important libraries of the RCP include:
24
25
* **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 
26
27
* **org.eclipse.swt** - the Eclipse Standard Widget Toolkit, which provides GUI elements and basic layouts
28
29
* **org.eclipse.jface** - helper classes for UI development, such as viewers; contains components for implementing an MVC framework
30
31
* **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.
32
33
34
 **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](http://www.swt-designer.com/.)
35
36
37
 **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.
38 3 Pepe Ciardelli
39
40
41
## Java Web Start
42
43
http://java.sun.com/products/javawebstart/
44
45
46
[Deploying eclipse based application with Java Web Start](http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/java_web_start.htm)
47 4 Pepe Ciardelli
48
49
[RCP and Java Web Start](http://www.i-proving.ca/space/RCP+and+Java+Web+Start)
50 5 Pepe Ciardelli
51
52 6 Pepe Ciardelli
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](http://www.holmbech.com/eclipse/keytool/,) to create a Java keystore (JKS). 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. To run Eclipse under the Java SDK, go to Window ~~> Preferences -> Java -> Installed JREs. If no JDK is listed, click "Add ..." and enter the JDK home directory ~~ i.e. "C:\Programme\Java\jdk1.6.0_02" - under "JRE home directory". Then be sure the JDK entry has a check mark next to it before hitting "OK".