No subject

Sat Apr 19 01:31:08 UTC 2014

not the case.
=20
For example, consider something like
=20
<Object position=3D"128.0 128.0 23.0">
<Rectangle extrusion=3D"straight" scale=3D"1.0 2.0 5.0" offset=3D"root"/>
<Circle extrusion=3D"sphere" scale=3D"1 1 1" offset=3D"0 0 1"/>
</Object>
=20
that doesn't look like a bad idea at all to me.
/Stefan=

--_1d749aed-2031-4a4b-85b7-d636bdf6f011_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class=3D'hmmessage'>> It would be good to see a proposal on how to=
 change those objects into<BR>> something better. None of us are in love=
 with them, but better<BR>> approaches haven't popped up yet.<BR><BR>
Probably because nobody has made any attempt at discussing and proposing ch=
anges; this mail was an attempt to get that ball rolling.<BR>
 <BR>
There was some energy poured into analyzing how attachments were communicat=
ed; that would be a good start, if we could get a wiki page up just detaili=
ng what we know about scene entities.<BR>
 <BR>> > * Related, we need to revise the xml serialization sche=
me and the db<BR>> > * schemes. The xml scheme should be user-friendl=
y to the point where<BR>> > * you should be confident to create and e=
dit objects in notepad,<BR>> > * basically. This is not the case at t=
he moment. Massive duplication,<BR>> > * weird bit values and non-int=
uitive value ranges are king at the<BR>> > * moment.<BR>> <BR>>=
 Given the amount of data in a prim, editing in notepad always is going<BR>=
> to be a bad idea. :) I think we've got something like 40 fields that<B=
R>> have to be sensible for the prim to work.<BR><BR>