= Gnowsis in Eclipse =
Sooner or later (probably September 2006) we will move the gnowsis gui to '''Eclipse RCP'''. The big advantage of that is that we have a nice gui and a community that knows how to make frameworks.

 * [http://www.eclipse.org/articles/Article-RCP-1/tutorial1.html Eclipse RCP tutorial]

== Setting up the application ==
The application can be set up similar to what dbin.org did or the Hayloft/Haystack people do.

What we would need is an "Nepomuk application" object with roughly these properties:

 * getPimoService();
 * getPimoStore();
 * ... get all other services

For the applicationWindow:
 * getCurrentResourceDS(); - the currently selected resource
 * getCurrentModelDS() - the currently selected model. The model could be expanded with operations for committing changes or rollback

Then each editor and view can access them.

== Selection and Data model in the background ==
The eclipse selection model could be combined with the known GnoGno components from GnognoComp.

== Actions ==
Eclipse actions are a big opportunity for us.
If we manage to transfer as much as possible from [http://download.eclipse.org/eclipse/downloads/documentation/2.0/html/plugins/org.eclipse.platform.doc.isv/reference/api/org/eclipse/jface/action/Action.html Action] or [http://download.eclipse.org/eclipse/downloads/documentation/2.0/html/plugins/org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/IWorkbenchWindowActionDelegate.html IWorkbenchWindowActionDelegate] we can save much time.

Also, this would allow us to have plugins that have new actions for resources (what we always wanted).

== Views and Editors ==
yes, views. oh boy, views. Heiko Maus always wanted to have views.