I am interested in possibly reviving the integrated Python scripting in Mahogany. I'm a complete newcomer to this project and before diving in, wish to ask what issues I might face.
Could someone tell me what are the problems associated with such an effort. I would be interested in using Python 2.2.1 (the latest). I have embedded the Python interpreter before, but have no knowledge of Mahogany source code (yet). As I understand the Python scripting capability, there was/is Python code interfacing to the internal C++ object model of Mahogany. While I'm on the subject, I'll just toss in a possibly helpful link to my favorite C++/Python interfacing tool, the Boost Python Library. http://www.boost.org/libs/python/doc/index.html (It is changing because of the type/class unifications in Python 2.2.) Another semi-related question -- What about a wxPython port of Mahogany? Does anyone think that would be worthwhile? I'm interested in all opinions here. The question is related because a wxPython port would yield, as a side effect, an integrated Python interpreter. In the end it might be less work to actually do a wxPython port than a combination wxWindows/embedded Python package. (Because wxPython mirrors almost 1-to-1 the classes in wxWindows.) Looking forward to your answers and opinions, Kind regards, Mark Evans ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
