Re: [Plib-devel] Getting rid of GLUT
Brought to you by:
sjbaker
From: Steve B. <sjb...@ai...> - 2004-02-03 22:47:06
|
Fay John F Contr AAC/WMG wrote: > (1) The "puSetWindow" or any window-setting is used only in two places > in PUI. Neither of these places is necessary to the library as a > whole. OK. > (2) The "puGetWindow" function is absolutely necessary to PUI. Every > widget must check whether the mouse click is in its window when it is > running "checkHit"; if it does not, we find the spectacle of clicking > the mouse in one window and activating a widget in a different window. Yeah - this is something I wasn't happy about. What I wanted to happen was to have a different widget tree for each window. Then you would call puMouse/puKeyboard/puDisplay for whichever window the event was intended for - and not waste time for all the other widgets that belong to some completely different window. If that had been the case, each PUI widget tree would only get events needed by it's widgets and no window ID testing would be needed. > (3) PUI does not use the "puSetWindowSize" function in any significant > way. I described the vertical menu window sizing earlier; that is the > only place where it is used in PUI and it is going away. Yes. I agree. > (4) PUI uses "puGetWindowWidth" and especially "puGetWindowHeight" when > it is positioning the "puMenuBar" at the top of the window. It also > uses the latter in converting from GLUT window coordinates to PUI window > coordinates. This is hard to work-around. > The question of how important it is to get rid of GLUT is, of course, a > matter of opinion. We have at least two people on this list who use > PLIB but not GLUT/freeglut (Marten Stromberg and Andy Ross -- correct me > if I misrepresented you, please) and I daresay if we shook the bushes > there would be more. Steve wouldn't cry if GLUT dependence were removed > either (ditto). I really think we should get rid of GLUT dependence. There is an up-coming generation of devices like Cell phones and PDA's that are getting OpenGL implementations - but NOT any recognisable windowing system...and CERTAINLY not a GLUT port. > Perhaps we should ask on the PLIB users' list how many people need the > multiple-window capability. I need it critically; my application--which > is a significant fraction of my bread and butter--cannot live without > multiple windows. Well, whilst I don't think multi-window capability is anything I'd every have implemented, now that it's been done, it would be a shame to lose it again. As I pointed out in my long posting from last night, I don't think there is a problem in doing this properly without losing a single PUI feature or changing one single line of existing programs or Makefile's to do it. ---------------------------- Steve Baker ------------------------- HomeEmail: <sjb...@ai...> WorkEmail: <sj...@li...> HomePage : http://www.sjbaker.org Projects : http://plib.sf.net http://tuxaqfh.sf.net http://tuxkart.sf.net http://prettypoly.sf.net -----BEGIN GEEK CODE BLOCK----- GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M- V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++ -----END GEEK CODE BLOCK----- |