I've talked with Gavin about this a bit. I believe something like the SoText3
node would work fine but we should leave out the "parts" field or we'll have to
implement SoProfile and I think extruded text is too much for now. I'm not
sure how the VRML spec deals with this sort of thing. Perhaps the parser
should accept this field and ignore it.
We need a font node of some sort. Rather than using the SoFont node as is I
think something that more closely matches the HTML way of specifying fonts
would be more portable among the various machines. I'll work up a proposal and
post it.
I don't think we need a SoText2 node.
--
chris marrin ,,.
Silicon Graphics, Inc. ,`` 1$`
(415) 390-5367 ,|` ,$`
cmarrin@sgi.com b` ,P` ,,.
mP b" , 1$'
,.` ,b` ,` :$$'
,|` mP ,` ,mm
,b" b" ,` ,mm m$$ ,m ,,`P$$
m$` ,b` .` ,mm ,.`'|$P ,|"1$` ,b$P ,,` :$1
b$` ,$: :,`` |$$ ,:` $$` ,|` ,$$,,`"$$ .` :$|
b$| _m$`,:` :$1 ,:` ,$Pm|` ` :$$,..;"' |$:
P$b, _;b$$b$1" |$$ ,,`` ,$$" ``' $$
```"```'" b$P `""` ""` ,P`
`"` '$$b,,...-'
"As a general rule, don't solve puzzles that open portals to Hell."
- excerpt from "A Horror Movie Character's Survival Guide"