Included libs in Python-Ogre

I figured it was better to start a new thread for this purpose, rather than having the discussion in the other thread which is not really related. I'll start by asking what the intent of the current Python-Ogre developers are (i.e. Andy and Roman (?) ), regarding binding and including other libs.


So, right now, when you get Python-Ogre, you not only get bindings for OGRE, but also for a bunch of other libs that are related to game development. The complete list is currently...

1. OGRE ( rendering )[/*:m]
   
2. OIS ( input )[/*:m]
   
3. CEGUI ( gui )[/*:m]
   
4. OgreNewt ( physics, newton )[/*:m]
   
5. OgreRefApp ( physics, ode ? not sure about what this is )[/*:m][/list:u]
   Now, I'm not sure how this works, but I guess that each of these libs have a number of more or less independent dlls? That is, if you do not want any of these (physics for example is only relevant for a few cases), you can simply remove the dlls? Or how much work is involved in removing unwanted dependencies?
   
   If it is difficult to do that (from a Python-Ogre user (such as myself) perspective), it would be nice if that would either change (so that it becomes easy to remove unwanted libs from your game), or that you provide them separately, or that there are perhaps two different distributions: One minimal with just OGRE (and perhaps CEGUI) and one with every single game related lib available.
   
   
   And, to ask the question Andy asked in the previous thread: What other libs would be interesting to wrap?
   For sound, FMOD is really nice, but there is PySonic, which has a pretty nice license I believe... Yup:
   
   pySonic is an open source Python package covered by the MIT license. No catch there. On the other hand, the FMOD library itself is a closed source product with various licensing schemes. But not all hope is lost. If you plan to use FMOD in a product that is not intended to make money and does not make you any money, then you may use FMOD free of charge. See the FMOD website for details.
   
   So it might be nice to have a binding for OpenAL as well (I think there are one or two, but we switched from OpenAL to pySonic for VW for some reason, guess it was easier to use or somemthing). Are there any other nice sound libs out there?
   
   PyGame has support for sound, music, input and for getting you a surface to draw to.. but including PyGame in Python-Ogre seems a bit wrong?
   
   A nice lib (but also very specialized) is libnoise that provides a really nice interface for creating perlin noise. Could be worth looking at if someone is interested.
   
   wxPython is a nice GUI lib, but I haven't been able to get the wxPython + P-O demos working yet. Anything I need to do? Should demos focus on wxPython only or should we attempt to create demos for different gui libs such as tk, gtk, qt and so on?
   
   Of course, these things are not requests of any kind, but more of a way to plan and discuss the future of Python-Ogre and Python-related game development (using Python-bound C++ libs).
   Any thoughts?

This doesn't belong on the PyOgre forum, you should of posted it on the Python-Ogre mailing list.

As for the topic at hand the its really quite simple. The other libraries are wrapped not because they are general game libraries but because they are Ogre related libraries that Python-Ogre users would like to use because they are generally used with Ogre C++ development. OIS and CEGUI should be able to operate independent of Ogre while OgreNewt and OgreRefApp obviously need Ogre.

Ah, mailing lists. I really don't like mailing lists. I just asked here because Andy asked in this thread:
http://www.ogre3d.org/phpBB2addons/view ... 8&start=15


What pygame functionality do you use/want??

I ask in the context of our Python-Ogre development and am interested in what 'other' libraries we should look to wrap (and potentially include as part of the Python-Ogre package)..

(...)

wxPython is a nice GUI lib, but I haven't been able to get the wxPython + P-O demos working yet.
Getting Python-Ogre embedded into a wxPython app would be the ideal demo since that is an obvious path to creating tools. That would be great.

This doesn't belong on the PyOgre forum, you should of posted it on the Python-Ogre mailing list.
It sure seems like PyOgre is dead. So why not use this forum for Python-Ogre? I don't like mailing lists, either.

Have you guys even used google groups, because you aren't talking like you have. Its just like forum only you need to have an a google account. Why don't you check it out. In general I agree that mailing list aren't very user friendly, but if you ever need to use them I would check out gmane.

I would wait until Python-Ogre reaches final (1.0) release before we decided if PyOgre is really dead. Currently Python-Ogre uses a bleading edge version of Boost which makes it harder to use than the simple swig dependency of PyOgre. That should change in time though.

Please don't wait for Python-Ogre 1.0

Use the versions we've either released, going to release (in the next week), or build from the SVN (which requires a little work at the moment to get all the necessary libraries etc, and we will make this easier)... AND give us feedback, either through bug or enhancement tickets on the http://python-ogre.python-hosting.com site, via the mailing list, or on this BBS...

We are committed to completing and supporting the Python-Ogre project (personally I need a really good game development environment with which to teach my kids ) and we are putting a lot of effort in to ensure it is maintainable over the long term -- basically with Py++ and the current wrappers, building a new set of bindings each time Ogre changes becomes trival...

To answer a previous question, each of the 'bundled' libraries in Python-Ogre is either 'very' standalone (in that you simply can remove the appropiate sub directory under packages - at least this will be the case in the next release as I'm moving the dll's back into the packages tree) or is dependant upon the base 'Ogre' package.

Making and release a Python-Ogre 'lite' package is simple, although probably doesn't save you much in the way of disk space as currently 'Ogre' is the bulk of the release..

Perhaps once we get a 1.0 release out (which will match the release of Ogre 1.4) we can have a broader discussion on Python-Ogre vs Pyogre (as we need to change links from the Ogre site etc)

Cheers
Andy

wxPython is a nice GUI lib, but I haven't been able to get the wxPython + P-O demos working yet. Anything I need to do? Should demos focus on wxPython only or should we attempt to create demos for different gui libs such as tk, gtk, qt and so on?

regarding the bolded text above, change the following code in OgreWindowWx.py

line 209:
#viewport.backgroundColour = (0, 0, 0)
viewport.backgroundColour = ogre.ColourValue(0, 0, 0)

OgreWindowTest.py should work fine

*edit*
sorry, i accidentally double posted.

or...
viewport.setBackgroundColour ( 0,0,0 )