What, no eclipses? (was RE: [Plib-devel] Re: [Fwd: Plib 2.0])

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

Gentlemen,

	In the interests of learning SSG, I have compiled and am currently
running the "Sky" SSG example program.  Quite frankly, I am amazed.  Phases
of the moon, stars, sunlight, clouds, wow!

	If somebody could help me by implementing a PUI widget in SSG, I
could try my hand at importing some others.  I would suggest that the
"puAux" widgets be moved over into a separate "ssgWidgets" library and not
be put into the core "ssg" library.

	Incidentally, ...
		- the "Sky" example is not part of the "Examples" workspace.
		- there are 33 compiler warnings under MSVC -- mostly
double-to-float conversions
		- I got a run-time warning about "null star data passed to
ssgaStars::build()".

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



-----Original Message-----
From: pli...@li...
[mailto:pli...@li...]On Behalf Of Steve Baker
Sent: Tuesday, July 13, 2004 8:34 AM
To: Erik Hofman; pli...@li...
Subject: [Plib-devel] Re: [Fwd: Plib 2.0]

<snip>

Hence, in addition to SSG shader support, there are other drastic changes
that PLIB needs:

<snip>

2) PUI is converging on SSG.

    Both API's are tree structured data with branches and leaves. Leaf nodes
    cause rendering to happen and branch nodes control behavior with state
    nodes doing stuff like colour and texture.  Collision detection and
    figuring out which button was clicked are also very similar activities.

    PUI is in dire need of state management to allow it to use texture
    and such like more cleanly.   Merging those two systems into a single
    API brings in very interesting possibilities for both 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 like building
    your GUI pages in a 3D modeller).

<snip>