-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 29 October 2003 21:38, David Boddie wrote: > > I don't see how moc should help here. I don't think it should be put in > > moc_pyqwidgetplugin.cpp because it is automatically generated from > > pyqwidgetplugin.h and is for class PyQWidgetPlugin. Others moc_* file > > don't exist and you can't create other moc files from *.py files. Or are > > you thinking about creating a pymoc command? > > I've thought some more about this and I'm coming round to the idea that we > could derive a class from QWidget, in much the same way that Jim derived > PyKPanelApplet from KPanelApplet, and get it to set up a customised meta > object for each Python class by examining the relevant class definitions in > Python scripts. In fact, looking at moc_pykpanelapplet.cpp in the > PyKDE-3.8rc2 sources, it seems that we have a good template to start from. What is the advantage of creating a subclass than making the change directly to QWidget?
> The disadvantages of this approach are: > > 1. Lack of a general method for defining signals and slots. Why? We can read out variabes in the Python class defining the signals, slots. regards Roland -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/oCgcV/hlvQgMogsRAnNtAKDg/V2BM87DYlGxQKUn1C/WlX5gNgCdHpu3 I+96fJfgtW/fsTBnz632vl8= =ZpJ9 -----END PGP SIGNATURE----- _______________________________________________ PyKDE mailing list [EMAIL PROTECTED] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
