On Tue, 19 Mar 2002, john.fay@... (Fay John F Contr AAC/WMG)
> Date: Tue, 19 Mar 2002 08:17:52 -0600
> To: plib-devel@...
> From: john.fay@... (Fay John F Contr AAC/WMG)
> Subject: RE: [Plib-devel] PLIB on GLFW
> I'm not sure I follow the reasoning here. First I need to make clear
> that my knowledge in this subject is very shallow: I use PUI with GLUT
> and nothing else. (That explains why I really don't care about the
> dependency; I don't know about any other windowing systems.)
> But how does PUI require the user to manage his windows with GLUT? I
> thought the only dependence was some fonts that I was able to hack out.
It currently really *does* require the user to manage his windows with GLUT
unless he uses that PU_NOT_USING_GLUT hack.
The problem are not only OpenGL fonts but also how to retrieve window
dimensions, which PUI needs to set up the OpenGL viewport, to keep
puMenuBar widgets at the top of a window and for many other things.
Furthermore, I consider the current modification only as a hack and not as
a solution. Think about it - it requires that some textured fonts are
always present, that means that a programmer will always have to distribute
them along with his application. It does not work with multiple windows
> Frankly, I do think that removing GLUT from PUI would be a worthwhile
> thing just on general principles
That one is not only about "general principles", but about the usability of
PUI. We all know that you are a probably the heaviest PUI user around. If
somebody would come up to you and say "Uhm ... John, I need a set of basic
UI widgets for OpenGL to integrate into my application ...", you'd surely
mentition PUI and ask the person "You do use GLUT to create your windows,
don't you ?" - and what if the person would tell you that he uses something
else but would like to use PUI in multiple windows nevertheless ?
That limitation is brain-dead, but difficult to remove ...
> If we could do it without breaking existing applications, I would even
> put some work into it.
Tell me how to do it without breaking existing applications and I'll be
working on it immediately !
However, I can't think of a way to do it without breaking existing
applications. Getting some built-in fonts isn't a problem. But the
retrieval of the window size is. Either we must have the user to supply us
with window dimensions, or we would have to look at as many window systems
as possible and find out how to retrieve window sizes, but either way, we
would require applications to supply is with some information (either
window sizes or window structures of the appropiate system) that they do
not hand over to us currently. Hence, we would break them.
Quick question for the list: GLUI depends on GLUT too, doesn't it ?