Oops. I thought I remembered using the rilative URL rather than the
>} I would propose taking the fields of the
>} code:
>} would have been without the transform. This would allow fractal
I like that word (or perhaps replicative? :-). You're right; I was
You're also right that the performance could be improved. I saw that
Leemon Baird
on> I did use. I've fixed that now, and I've also moved the files to rbr>
an FTP site so the MIME type problem on the server won't affect it:
ftp://ftp.usafa.af.mil/com-sci/baird/ftree.wrl
I won't b> able
>} MATERIAL node, and adding them
>} Transform {
>} emissiveColor .5 1 2
>} }
>} would make all future nodes half as red and
>} colors, even fractal-compri> ed photographs, to b> applied to
objects.
>I assume you are not recommending removing the Material node (or
even the
>emissiveColor field
coloring
>scheme in addition
suggesting that the Material fields b> added
we could do fractals either by recursive DEF/USE statements or by
recursive WWWInline statements two months ago when I first read the
draft 1.0 spec. When I finally got access to a browser this week, I
was dissapointed that I had
than an elegant solution (DEF/USE) to get it
[email protected]
[email protected]
http://kirk.usafa.af.mil/~baird