Re: Common Objects
Mitra ([email protected])
Mon, 29 May 1995 19:20:20 -0700
At 4:04 PM 5/29/95, Gavin Bell wrote:
>Second, the "display something simple while waiting for something complex"
>functionality you want is already in WebSpace, using VRML 1.0 objects. You'd
>just specify:
>
>DEF Teapot LOD {
> range [ 10, 100, 1000 ]
> WWWInline { name "http://obscure.com/realcoolteapot.wrl"
> WWWInline { name "http://vrml.org/generic/fancyteapot.wrl"
> WWWInline { name "http://vrml.org/generic/teapot.wrl"
>}
>
>Think of LOD as a way of specifying a series of representations, ordered from
>most desireable to least desireable, with the ranges being a weird way of
>specifying how desireable each is.
>
>If WebSpace already has the lower LOD's fetched, it will display them while
>fetching the higher LOD. Once Webspace does caching, that should get you the
>behavior you're looking for; if the generic teapot is in the cache, it will
>be displayed while the obscure teapot is fetched. Webspace also allows the
>user to control how much detail they want to see when moving around; if the
>user chooses low detail then maybe the realcoolteapot will never be fetched.
Gavin,
I've checked the spec, and this isn't mentioned. What it says is "The size
of the objects when projected into the viewport is used to determine which
version to use" if this is the expected behaviour then maybe it should be.
However I think its a little bizarre especially since
a) the "teapot.wrl" will be displayed at a distance, and will change to the
"fancyteapot" at some arbritray distance
b) its quite likely that all three of these teapots will have their own LOD
node to specify, for example, a simple version of the realcoolteapot
Just to be clear, I think Webspace's behaviour conforms to the spec, but
isn't required by the spec.
- Mitra
=======================================================================
Mitra [email protected]
Worlds Inc (415)281-1308
<http://earth.path.net/mitra> fax (415)284-9483