> 1+ added my vote. Thanks Frank.
> Thanks for the link, A picture is worth a thousand > words ;) Maybe you could change the proposal pictures to those you > used at your blog Right, didn't think of it. Way better. Cheers, Andrea > > Cheers > Frank > > 2013/1/7 andrea antonello <[email protected]>: >> Hi Frank, Jody, >> >>> Maybe we can separate the expectations I and Jody had/have into an >>> other (long term) RFC. I had in mind to have access to the whole >>> catalog model that makes it possible to add resources to the catalog >>> and work with these. >> >> yes, I think that should be a future RFC. >> >>> Having this in mind it would be great to use the existing console and >>> extent this for, e.g GeoScript and in the second step bringing groovy >>> console into the arena with access to the udig catalog model. >>> >>> A third potential highlight could be an editor for script files like >>> geoscript/groovy with syntax highlighting and content assist like >>> (almost) every editor in eclipse has. I guess its worth to have a look >>> at the Groovy-Plugin for example : >>> http://groovy.codehaus.org/Eclipse+Plugin which provides Eclipse >>> integration already. >>> >>> I agree, a google summer of code project is a good point to start for >>> the second and even 3rd step ;) >> >> I think I didn't make myself clear about what I want to have in my proposal. >> I wrote a bit of a summary here: http://tinyurl.com/aopxu5l >> >> I hope that helps voting up :) >> >> Cheers, >> Andrea >> >> >> >>> >>> Cheers >>> Frank >>> >>> 2013/1/7 andrea antonello <[email protected]>: >>>> 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 >>> _______________________________________________ >>> 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 > _______________________________________________ > 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
