1) Number 9 of the proposed changes concerns cameras. Similar to HTML NAME
anchors, VRML will be able to specify a camera position by appending a
#<camera name> to the WWWAnchor URL (or, I suppose, in an HTML HREF...
anyone considered this aspect? Does it change anything?). Anyway, I
proposed, some time ago, that even if the target VRML file did not have a
camera set up where the author of the VRML file pointing to it wanted to
send the viewer, the author could define a camera *within the WWWAnchor
node* (in the world coordinates of the target VRML file) at the desired
position and looking in the desired direction. There is certainly some
appropriate encoding of this camera after a # so that it can be defined in
an HTML HREF as well (this would have to be devised). Are there objections
to this? Reasons not to include it? This allows convenient access even to
files where the author did not bother to define any cameras. I would like
to see it in the spec.
2) The Texture2 imagemapping I was talking about before. This hit the
mailing list, was supported briefly, and vanished like a drop in the
bucket. I thought I had made a good case for it. Again, are there any
objections or reasons why it is not feasible? Please seriously consider
it.
I would like to hear some response from the VAG on this and, ideally, see
these changes included in Bernie's official Proposed Changes list.
Thanks,
--Greg