RE: [Plib-devel] PUI questions

[Dave M. <Dav...@dy...>]

John wrote:
> I am working on a CFD grid generation program that makes very 
> heavy use of
> PUI.  I've had to add several new widgets, multiple-window 
> capability, and
> active-widget callbacks, so I call it "PUI-incremented" 
> privately.  The
> program has some 45 windows, averaging one or two dozen 
> widgets each.  I
> have just started upgrading it to PUI 1.3.0 (note my previous 
> posting on
> this list about adding multiple-window capabilities).
>
As for using multiple glut windows, I have mixed feelings.  I'm developing
for an embedded system that doesn't have support for multiple glut windows.
By "multiple interfaces linked together" i mean when you click on a button
it takes you to a *new* interface by deleting the *old* interface and
creating a new one in the same window.

> I haven't used rendering callbacks.  My "puLargeInput" is 
> basically a slider
> with a list box (and I use it for file listing and selection), but it
> doesn't work quite right and should probably be implemented 
> differently from
> the way I have done it.  I'm not sure what you mean by 
> "multiple interfaces
> linked together" but if you mean multiple windows I can 
> certainly help you.
> And I don't know what a python is, aside from a particularly 
> large snake.
>
information about python can be found here -- www.python.org.  using
scripting to drive your interface system is becoming pretty common.

i know that PUI is considered fairly static and stable but would anyone mind
some refinement of PUI to occur.  basically, my goal would be to enhance PUI
to the point where i can build a nice looking SSG viewer.  For that, I need
a listbox and other controls (which could be in the viewer) to allow
something that looks as good as GLUI example #5.  Any reason not to go
forward in this direction?

--Dave