On Mon, 1 Jul 2002 20:11:11 -0500 Mark Evans <[EMAIL PROTECTED]> wrote:
ME> I am interested in possibly reviving the integrated Python ME> scripting in Mahogany. Great! ME> I'm a complete newcomer to this project and ME> before diving in, wish to ask what issues I might face. Of course... ME> Could someone tell me what are the problems associated ME> with such an effort. I would be interested in using Python 2.2.1 (the ME> latest). I have embedded the Python interpreter before, but have no ME> knowledge of Mahogany source code (yet). As I understand the Python ME> scripting capability, there was/is Python code interfacing to the ME> internal C++ object model of Mahogany. That's my understanding. And this is done with SWIG. By my knowledge about Python ends here... ME> While I'm on the subject, I'll just toss in a possibly helpful link to ME> my favorite C++/Python interfacing tool, the Boost Python Library. ME> http://www.boost.org/libs/python/doc/index.html I have no idea about the respective merits/drawbacks of Boost and SWIG. If you would prefer to use one instead of the other, I guess this should not really be a problem, as currently none is really used. ME> Another semi-related question -- What about a wxPython port of Mahogany? ME> Does anyone think that would be worthwhile? I'm interested in all ME> opinions here. The question is related because a wxPython ME> port would yield, as a side effect, an integrated Python ME> interpreter. Mahogany's code is approx 150.000 lines. I'm not so sure it could be worthwhile to rewrite all of them, just to get an integrated Python interpreter... You would also have to rewrite/integrate c-client, the C library (75.000 lines) that M depends on for all the mail related functions. ME> In the end it might be less work to actually do a ME> wxPython port than a combination wxWindows/embedded Python package. ME> (Because wxPython mirrors almost 1-to-1 the classes in wxWindows.) My understanding of the current state of the Python affair is that SWIG is here to allow an *automated* creation of a Python package (I might be wrong on the terminology here, please correct me) that gives you access to the internals of Mahogany. This package allows one to open a folder, read messages, move them, compute filter conditions, etc., all what can be done from M itself. Even if the SWIG 'configuration files' have not been updated for a while, I'm sure the amount of work needed to get them up-to-date is not much, and in any case is nothing compared to rewriting M. Hope this helps. -- Xavier Nodet PGP fingerprint: EFE0 0E75 C4DC 2654 5C36 4E2D 107C 19DE 0646 1FE2 ------------------------------------------------------- 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
