View • Attachments (0) • Info
mainengine
the main operations engine
issues by JGrass
The logical chain I would love to have is: operations - chaining - openmi - console - R.
How it was in JGrass: we defined a beanshell environment that executed all the operations in the console environment so a command from gui went also through this and everything was one and one for all. We need an environment that lets us chain models together and they should be executed from the console engine as well as from toolbar.
Note: UDig doesn't have anything there as of yet.
proposed solutions by UDig
- you could create a nice visual way to compose operation chains using GEF, it provides much of the connection layout etc... framework.
- you would probably define "Extenstion points" so other plugins can contribute additional operations
- ui.console
- ui.gef
- the console would be a view. A view takes up screen space. But can be a "fast" view so it doesn't take up space until you open it in which case it acts similar as a dialog only it maintains its previous state where a dialog is re-created each time
Comments ( Hide )
|
Adrian Custer says:Feb 03, 2007 11:18 ( Permalink ) |
|
Andrea Antonello says:We used to use Rserve in JGrass and it worked fairly well. But sometimes we lost the socket connection and were not able to get it back without restarting JGrass. This happens in those situations in which the user has more freedom. Usually in that case the user does something dummy and Rserve probably doesn't know how to handle it. |
The connection to R and especially to R spatial objects is being worked on. The DIVA folk have a connection to Rserve although I don't know how that works. I will be working on a connection to R through JRI and hopefully builiding up ways to pass in vectors and images.
--adrian