On Apr 12, 2012, at 4:21 AM, Stefan Dlugolinsky wrote:
> 1. Point3D's a problematic name because there's already a javax.vecmath.Point3d. Same goes for Geometry3D etc. Naming is forever, so it's worthwhile to think upon this up front.
> What about name it Geometry3D => GeometryTG, Point3D => PointTG etc. where TG stands for TransformGroup, and all these classes extends it.
Geometry and Point are challenging words because they mean something in Java3D. How about something like GISGeometry or GISPoint? I dunno, not easy.
> 2. I had previously given some thought to an alternative but less elegant approach: take any FieldPortrayal2D or collection of FieldPortrayal2Ds and dump it [them] to a BufferedImage, then draw the BufferedImage as a texture in a large rect in a Display3D. You could handle hit-testing and selection by taking the intersection point and translating it into a location in the virtual FieldPortrayal2D world and pushing through that way.
> There's also a problem with the 'layering' in my solution, because I set z-coordinate to 0 for all the GIS shapes, so it looks not good if there is for example a line crossing some filled polygon drawn.