[Plib-users] Hi all!

[Cameron B. <ko...@da...>]

Hi,

intro
-----
Im just recovering from the Ludum Dare 48hour game contest and, while
I liked pygame/sdl as a platform, I had some pain with it, so I
thought Id try something else :).

I looked around at a lot of libraries and finally narrowed it down to
ogre or plib (mostly by looking at the docs/tutorials and seeing if I
could follow them while still clueless :). Ogre was fussy with its
compilations, and plib just worked (on my gentoo ppc mac too! :).
Yaay!

Id just like to say that I really appreciate the structure of the 
librarys. While I dont have a great understanding of opengl and other
stuff, I can follow the logical sequence of how this stuff is built
and what each part does (much easier than an all in one library) and
Im looking forward to tinkering.

But, as with all new mailing list users, I feel I have to ask a couple
of stupid questions just to make myself look like an idiot, so...



pylib or plibpy ? :)
--------------------
I poked around on the net and found a maillist archive that said:
  "Well, there has been work on building a set of Python language
  bindings." (back in 2002)

but then I found:
   http://www.py3d.org/links/plib
   "Open-source plib/ssg, game library with OpenGL (only) scenegraph
   engine, Python bindings."

I couldnt see any evidence of plib python bindings in the source...
um... so have i missed them or are they not 'rolled in' (and available
somewhere else) or are they nowhere to be seen? :) 

My c++ has _really_ rusted since I started using python ;) (I work as
a sysadmin/c programmer so that spells doom for the part of my brain
that stores info about virtual constructors :) but Im looking forward
to playing with plib (and the fact it works under cygwin too makes it just
perfect! :) and I think Ill need to for some obvious speed issues with
python ;).


fake puFileSelector ?
---------------------
Another question.. :) sometimes (it seems to me) you might want to
edit options out of the directory contents that are offered from
puFileSelector.

Given the modular way the rest of the library is structured, I
was a little puzzled not to find that  puFileSelector  didnt just
use a base class like  puEditableChunkOfLineSelector  or something. ;)

(It just seems to me that it's rolling two functions (dir walking
_and_ user interface) into one class when just the UI itself might be
useful.)

I guess noone has ever needed it that way (and Im not sure i do either
;) but it seems like a restricted puFileSelector would be great for
selecting PSL programs, while not allowing you walk 'up' the tree or
while filtering out all files that dont match the extension).

Its always possible that Ive missed something obvious here (like you
use dir* to construct the puFileSelector and then you can access the
puListBox::newList to add or subtract things.





cheers,
cam

--
 / `Rev Dr'   cam  at darkqueen.org            Roleplaying, virtual goth \
<   http://darkqueen.org        Poly, *nix, Python, C/C++, genetics, ATM  >
 \  [+61 3] 9809 1523[h]         skeptic, Evil GM(tm). Sysadmin for hire /
                      ---------- Random Quote ----------
What use is magic if it can't save a unicorn?
		-- Peter S. Beagle, "The Last Unicorn"