RE: [Plib-devel] Re: [Fwd: Plib 2.0]

[Fay J. F C. AAC/W. <joh...@eg...>]

Paolo,

	I am certainly open to ideas--and I daresay Steve is, too--but this
is no guarantee that they will be accepted.  But do please bring them =
on.

	I guess Steve's desire to fold PUI into SSG means that I am going to
have to learn SSG.  One thing I do NOT want for PUI, though, is the =
baggage
of all the file readers and writers.

John F. Fay
joh...@eg...



-----Original Message-----
From: pli...@li...
[mailto:pli...@li...]On Behalf Of Paolo
Leoncini
Sent: Tuesday, July 13, 2004 10:27 AM
To: pli...@li...
Subject: R: [Plib-devel] Re: [Fwd: Plib 2.0]



Is this a call-for-thoughts around Plib 2.0? Can anyone contribute with
ideas?


> -----Messaggio originale-----
> Da: pli...@li...=20
> [mailto:pli...@li...] Per conto di=20
> Steve Baker
> Inviato: marted=EC 13 luglio 2004 14.34
> A: Erik Hofman; pli...@li...
> Oggetto: [Plib-devel] Re: [Fwd: Plib 2.0]
>=20
>=20
<snip>
> 2) PUI is converging on SSG.
>=20
>     Both API's are tree structured data with branches and=20
> leaves. Leaf nodes
>     cause rendering to happen and branch nodes control=20
> behavior with state
>     nodes doing stuff like colour and texture.  Collision=20
> detection and
>     figuring out which button was clicked are also very=20
> similar activities.
>=20
>     PUI is in dire need of state management to allow it to use =
texture
>     and such like more cleanly.   Merging those two systems=20
> into a single
>     API brings in very interesting possibilities for both=20
> API's and saves
>     us a bunch of maintenance (because both could share the same =
state
>     management and cull routines - you could even do things=20
> like building
>     your GUI pages in a 3D modeller).
>=20
<snip>