Texture URL's (was Re: WWWInline; include non-VRML data?)

Linas Vepstas (linas@innerdoor.austin.ibm.com)
Tue, 18 Oct 1994 11:39:54 -0500

>To: linas@innerdoor.austin.ibm.com (Linas Vepstas)
>Subject: Re: WWWInline; include non-VRML data?
>Date: Mon, 17 Oct 94 22:04:44 EDT
>From: Brygg Ullmer <ullmer@bigcheese.math.scarolina.edu>
>Hi, Linas! Did you want to cc this to the list? (And if you did, maybe you
>can append my response to the list as well... or otherwise, I'll post my
>response if you post yours! ;-)


>> Regarding the texture mapping of html onto 3D polygons, may I suggest
>> extending The Inventor VRML proposal:
>> Texture2 {
>> filename ""
>> image 0 0 0
>> wrapS REPEAT
>> wrapT REPEAT
>> }
>> so that filename is an http request.
>I gather you mean filename is (or can be) a URL?


>> The we can argue about how to
>> support this. (everybody supports gif's, but maybe it's implemenentation
>> dependent if .jpg is supported ... and, maybe it would be interesting to
>> take a flat ascii html file, and turn it into a texture ... but maybe
>> this can be left as implementation dependent thing to do.)
>Perhaps... I suppose a mailcap-like extension can be used here, though

Mailcap is great for spawning external viewers, but I don't see how
to use it in any sensible way with integrated viewers.

>from an implementational point of view, I wonder if it's not easier to
>explicitly delineate WWW-savvy nodes. But any way you cut it,
>it seems Texture2 will have to be passed a net-linked texture argument;
>maybe we should consider renaming it WWWTexture2 to reflect this fact.