At one point I tried to SWIG (and boost.python) mythtv 0.14. I just ran out of steam after hunting down lots of peripheral problems. I don't know if it was SWIG, or mythtv, or an architectural impedance mismatch between the two (most likely). I did have much better luck in terms of code coverage with SWIG. I am not an expert, by any stretch, using SWIG or boost - so YMMV. I agree that it would be great if python extensions were available to open up plugin writer accessibility further. Certainly C++ isn't always the "right tool for the job".
Brian On Fri, 10 Dec 2004 00:05:53 +0000, James Casbon <[EMAIL PROTECTED]> wrote: > On Thursday 09 December 2004 18:03, Matthew Conway wrote: > > > > On Thu, 9 Dec 2004 17:52:54 -0000 (GMT), Phil Thompson > > > > <[EMAIL PROTECTED]> wrote: > > > PyQt is build using SIP > > > (http://www.river-bank.demon.co.uk/docs/sip/sipref.html) which makes it > > > easy to define new Python modules that extend existing ones (like PyQt). > > > PyQt doesn't use SWIG because (historically) the C++ support has been > > > less than ideal. > > > > Any thoughts on Boost.Python (http://www.boost.org/libs/python/doc/)? > > I guess I'll end up playing with all three a bit to see which one fits > > mythtv the best. > > So much for: > "There should be one-- and preferably only one --obvious way to do it." > > This doesn't seem to apply here. > > > _______________________________________________ > mythtv-dev mailing list > [EMAIL PROTECTED] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev >
_______________________________________________ mythtv-dev mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
