From: Jenkins, B. \(NE\) <Bar...@gd...> - 2006-06-20 21:05:19
|
Chris, re: item e) I would add the ability to choose between a polling method or an event drive method. Event driven is more efficient IMHO. Bart Jenkins -----Original Message----- From: ope...@li... [mailto:ope...@li...] On Behalf Of Chris Nicholas Sent: Tuesday, June 20, 2006 2:12 PM To: Frank Warmerdam Cc: Mario Beauchamp; ope...@li... Subject: Re: [Openev-discuss] OpenEV2 plans (revised) OK - as expected, after some more discussion at this end with potential end-users, several more concrete items. I'm trying to tell them this is supposed to be an imagery-intensive viewer, not a full GIS....and pin things down to do-able, well-defined deliverables. I'ill toss out these items...you can tell me how hard or easy they are: a) some guide to writing Python extensions (add your own button, etc) b) support for some kind of ascii or XML-based "project file", that can preserve state, i.e. which images & overlays are visible, etc. If layer visibility could be scale-dependency, even better. Perhaps just support a subset of ESRI axl-like things, Mapserver mapfiles, or Web context documents ? c) some tool to crop, reproject, and export rectangular regions, even the area falls across tile boundaries. d) basic style editing for overlays (color, font, line width), and tolerable WYSIWYG printing e) Some polling mechanism to automatically refresh layers; the example given was WFS points being updated asynchonously with GPS positions. "wish list" items: f) fetch-ahead of slightly larger areas for that 'Ajax-style" smooth scrolling once people knew this was written in Python: g) Some scripting mechanism to empower people to "tell a story". Chris Frank Warmerdam wrote: >Mario Beauchamp wrote: > =20 > >>Frank, Chris, >> >>On Sunday 18 June 2006 13:09, Frank Warmerdam wrote: >> =20 >> >>> >Chris says: >>> > >>> =20 >>> >>>>>How hard would it be to do something similarly crude-but-effective, >>>>>with basic WFS-T support vector access and edits? >>>>> =20 >>>>> >>>I have thought about integrating WFS-T support in OpenEV in the past. >>>It would be possible, but a bit challenging. There are a few levels=20 >>>at which the updates could be written back. >>> =20 >>> >>Ok, since Frank obviously knows more on the subject than me, I guess=20 >>he would be the one to implement it, if it comes to that. Of course,=20 >>it means he would get the funding :) >> =20 >> > >Mario / Chris, > >Well, to be honest, I don't know that I have the time and patience to=20 >try and pursue this matter aggressively. It sounds like the project=20 >might not require "fine grained" WFS-T, in which case my "save via=20 >wfs-t" might be sufficient. > >Best regards, > =20 > _______________________________________________ Openev-discuss mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openev-discuss |