AW: [udig-devel] Map3D in UDIG

["Wellmann, Harald" <harald.wellmann@xxxxxxxxxx>]

Regarding the pan and zoom tools, they work fine for me even with Java3D, but for the moment I'm only doing 2D rendering, so that is no surprise.

In the long run, when we want to render real 3D data, separate tools is not enough, we really need a viewport model that takes care of 3D aspects (so it would be a viewing frustum) really, and we need tools to support at least the 6 dimensions of rigid motions. Plus scaling, perspective projections etc.

Or maybe we no longer need a viewport model at all, if this is just a private contract between the ViewportPane and the Tools? Don't know what side effects that would have.

By the way, I've started writing up some background on my protoype in http://udig.refractions.net/confluence/display/HACK/Java3D+Renderer

This is incomplete, but it's a start...

Regards,
Harald 

> -----Ursprüngliche Nachricht-----
> Von: udig-devel-bounces@xxxxxxxxxxxxxxxxxxxxx 
> [mailto:udig-devel-bounces@xxxxxxxxxxxxxxxxxxxxx] Im Auftrag 
> von Jody Garnett
> Gesendet: Mittwoch, 25. März 2009 14:01
> An: User-friendly Desktop Internet GIS
> Betreff: Re: [udig-devel] Map3D in UDIG
> 
> Okay I am glad our discussion brought you out to talk to us.
> 
> Please note that as a university student I can send you the 
> commercial training materials for uDig (if you get your 
> professor to email me).
> 
> It is always annoying when license issues get in the way of 
> collaboration. Even if you cannot contribute your work due to 
> license conflicts; you can still contribute your feedback 
> (and nice patches).
> Indeed you can share your source code in the community 
> section; and look into making your work an optional download 
> in the help menu. We are limiting the core of uDig to LGPL 
> simply because so many of our supporters depend on the 
> ability to package up custom applications for their organizations.
> 
> You talk about your library managing layers internally; and 
> it should be doing that. The idea is to generate that 
> internal structure based on the uDig Map/Layer data model. 
> You will actually find the uDig rendering code generates a 
> model for rendering (called RenderExecutor or something) - so 
> the split you are talking about is actually by design.
> 
> My question about tools is more about checking your needs for 
> working with the viewport model; can you drive your 3D 
> display from it? Can we enhance the viewport model to meet 
> the needs of a 3D display?
> 
> Allowing the display widget to cough up its own pan/zoom 
> tools represents the other approach; basically saying the 
> viewport model will never meet the needs of everyone; and 
> that the viewport model should be "sucked into" the display 
> widget; and the display widget should advertise to the rest 
> of the udig application the "tools"
> needed to effect a visual pan or zoom.
> 
> Cheers,
> Jody 
 
*******************************************
innovative systems GmbH Navigation-Multimedia
Geschaeftsfuehrung: Edwin Summers - Kevin Brown
Sitz der Gesellschaft: Hamburg - Registergericht: Hamburg HRB 59980 
 
*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.
*******************************************