Jody,
I've finally got a few minutes to get back to you with some comments.
The editing tools I'm working on for OpenJUMP will be quite different
fromt those currently in the program, and even different from what you
are thinking.
My editing and tools will not make use of "handles" to manipulate
feature geometries. This is rather "imprecise" from a surveyor's
perspective. :] Besides, OpenJUMP already has some pretty good tools
for this type of manipulation.
My tools will user precise information entered by the user into a
dialog to perform its editing. For example, instead of dragging a
feature from on spot to another spot on the map, the user would do the
following:
[1] Specify the feature to be moved.
[2] Specify the base point for the move.
[3] Specify a "Move North/South" amount and a "Move East/West" amount
or
Specify a "Distance" and "Direction"
or
Specify a destination point.
Notice I say "specify", and not "click" or "type". That is becuase I
want these tools to accept input in a number of forms. In the above
example, the user might specify a distance and direction by typing in
a couple of text boxes, or they might instead select an existing
segment of a linear feature from the map display.
The problem with this scenario is that OpenJUMP doesn't really have a
way to allow for "precision" selection of coordinates on the map
display. I hope to solve that problem with my Coordinate Selectors.
I think as we move into the future it will be more difficult for
OpenJUMP and UDig to share source code. You guys are using SWT for
your GUI, and we are using Swing. I thought we could share the
"models" of our tools, even if we couldn't share the GUIs, but you
guys seem to be pretty tightly coupled with GeoTools. I think your
development pace is also moving quicker than ours. It will be tough
for our project to keep up, although you would think collaboration
would help that, not hinder it.
I suppose one solution to this would be for me to become more acitve
in GeoTools, so that OpenJUMPers would have a voice in the development
of those APIs. This would make it easier for us to adopt them along
with UDig. However, I took a look at the GeoTools website, and it just
seems like my goals are very different. I think implementing open
technology standards is a great idea, but you already know how I feel
about the OGC. :] I'm much more interested in development of practical
applications without all that red tape and politicing. :]
Its a shame though, as I think I will be working on some really useful
"utility" code at the SurveyOS project that would benefit any type of
geospatial application.
I think the best I can do in this situation is make an effort to keep
the lines of communication open with the UDig development team, so at
least we can be aware of what each team is working on. (Not that you
could really call our scattered OpenJUMP developers a "team".) :]
I'll let you know how the edit tools work out.
The Sunburned Surveyor
On 10/2/06, Jody Garnett <[EMAIL PROTECTED]> wrote:
Sunburned Surveyor wrote:
> Jody,
>
> Thanks for taking the time to look into this.
>
> I want to get back to you with some comments, but I'd like to have a
> little more time to read over what you and Adrian posted.
>
> I'll try and respond by the end of the week.
>
> The Sunburned Surveyor
No worries, sorry to come in so light on the strong formal design, at
least we both have experience.
Jody
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
