I suppose it _could_ be possible to render the border and displayed data into a texture and then assign that to poly representing the area. But wouldn't that be quite expensive - after all that it should be achieved by using a 3D engine in the first place.. :)
Another thing I forgot to mention in the first post - propably because it's completely different topic - is continous picking. The user interface should employ some method of mouse tracking, with highlighting and additional information show when cursor hovers over certain object in the scene; this propably needs to be done by firing picking rays at certain intervals to see if something is available.
I'm a bit concerned by performance issues - in Java3D this took too long, at least with unoptimized code and large scenes, and degraded performance too much on not-so-high-end machines..
Another thing I forgot to mention in the first post - propably because it's completely different topic - is continous picking. The user interface should employ some method of mouse tracking, with highlighting and additional information show when cursor hovers over certain object in the scene; this propably needs to be done by firing picking rays at certain intervals to see if something is available.
I'm a bit concerned by performance issues - in Java3D this took too long, at least with unoptimized code and large scenes, and degraded performance too much on not-so-high-end machines..