Given that Ogre uses bitbucket it is the only sensible option.
As on suggestions how best to oranize/move forward( none of the
following are meant as a criticism of the current source/build
* Replace the dependency modules zziplib/ois/Cg/FreeImage/freetype/
zlib with the ogre dependencies from:
* Remove module_dependency on Ogre for modules such as OIS, this will
allow individual modules to be packaged to distros such as Debian and
may increase user base from non Ogre users. If python-ogre isn't
packaged on Ubuntu/Debian etc it will simply die. No one wants to
spend a week trying to build a library.
* Remove older redundant modules, perhaps it would be a good idea to
have an ogre addons repository which is primarily maintained through
users contributions(??). Also I always thought it would be nice to
include an extras/helper lib with classes that could be created from
python but are slow/or require extensive ctypes code.
* Document/make the generate_code more easier to use (??). The
existing code base is quite daunting/difficult specifically to new
* Remove python-ogre media from the repository, they can be downloaded
from sourceforge and/or extracted from the base libraries source
* Provide scripts to generate documentation specifically doxygen apis,
the python-ogre api matches Ogre doesn't really wash.
* Stick with versions of boost/Py++ etc. during development of
branches/ or update on minor releases, head/master will be the latest
* Lastly back to previous post you made, maybe development of a c
wrapper which would benefit other projects as well as python-ogre.
The problem with the above is finding time/people willing to help.
Given the relatively small python-ogre user base is it worth the
effort? Maybe it's time to include other render engines such as
On Nov 30, 11:31 am, andy miller <a...@kiwisoft.com> wrote: