Hi Jody, > Second, I want to start the new year with a nice improvement proposal for > uDig. > You saw the RFC JIra pass already. > > Let me find the link: UDIG-1964
Yep, as reported in the RFC. [...] > We should keep in mind that the Console may already be in use by RCP apps > embedding uDig components. Not sure what you mean by that. > I am not familiar with how JConsole works, can > you add some links or design pictures for me to look at before I vote on > this? I did not bother too much on creating design pictures and stuff like that, because I built on the source, i.e. the eclipse RCP html texteditor example: http://www.eclipse.org/eclipse/platform-text/development/rcp/examples/ I assumed the design was ok, following that one. I will add that to the proposal. In fact, back when I started the JConsole, the tutorial was done on the JavaEditor, not the HtmlEditor, which came really handy, since I needed that one :) > I do like the idea of targeting GeoScript (as a nice common ground that > Justin has already worked out for us). What I have seen of the GeoServer / > GeoScript examples there may be some work to allow GeoScript access to the > uDig catalog? As I already told Frank, I will not target that. I will simply add support for aided Gescripting and then plug the execution through the spatial toolbox plugin. Changes: - a couple of additional libs for geoscript to work - a couple of plugins to support Texteditors - 1 plugin for the jconsole > I could also use a reminder of how java scripting works (I seem to recall > you set up an environment of objects the script has access to, and then run > the script within that environment). Guess the best way is to get started from the examples page of geoscript: http://geoscript.org/tutorials/index.html And yes, a new java process is spawn placing the proper libs in the classpath. > In this respect I am keen to know what > objects from uDig we are making visible to a script ... Again. I am not making uDig objects visible to the scripting environment. I hope someone will do that in a second step, but we do not have the resources to (not that I would know how to do it right now). Right now it is possible to drag resources from the catalog and layerview into the edior window, so they resolve to the file paths if they are files. That way scripting get's easier for the available resources in the workspace. I think it is important to make this first step to get geoscript working seamlessly inside uDig. Better interaction with uDig objects would be a nice followup, mybe a summer of code? Cheers, Andrea > > Jody > > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel > _______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
