Re: [PyKDE] SIP Roadmap
http://www.riverbankcomputing.co.uk/sip/roadmap.php Sounds very interesting... great changes to come up. However, as always I'm concerned about the Qt/Embedded and more specifically the QtPE bindings - what is your direction for these? iPAQ and Zaurus developers will have to stick at least another year or so with Qt/E 2.3.x. Cheers, Mickey. -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] SIP Roadmap
On Friday 03 January 2003 10:35 am, Michael Lauer wrote: http://www.riverbankcomputing.co.uk/sip/roadmap.php Sounds very interesting... great changes to come up. However, as always I'm concerned about the Qt/Embedded and more specifically the QtPE bindings - what is your direction for these? iPAQ and Zaurus developers will have to stick at least another year or so with Qt/E 2.3.x. Same applies to Qt-NC users which is why I'll continue to keep SIP v3 working. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] SIP Roadmap
For those interested I've added a SIP Roadmap to the website at http://www.riverbankcomputing.co.uk/sip/roadmap.php which describes the main objectives and features for SIP v4. Comments welcome. As author of PyQwt, an extension package that I support also on Qt-230-NC, I have the following comments: (1) wrt the obeying to the Python API export rules. This also facilitates the link step on other platforms than MacOS/X: under current scheme this is a minor problem on Posix systems, but on Windows, it means rebuilding PyQt-NC and sip-NC to rebuild the necessary *.exp and *.lib. Great! (2) wrt to the limitation to Qt = 3.0.0. This will make it more difficult for me to keep PyQwt compatible with Windows (I have no commercial version for Qt, neither for PyQt). Let me point out that I know of at least 2 companies with a commercial license for PyQt that are also using PyQwt. From a more general point of view: (3) Using the new-style Python-2.2 classes allows to map a C++ inheritance tree to Python (I have played with this, writing a wrapper for Fltk by hand). This is a great step forward for sip, also as a wrapper tool for other libraries than Qt. In this respect, it would be nice if there is support for two Python sip extensions modules, sipQt and sip, with and without Qt support. In summary, sounds great, but I'd like to keep support for Qt = 2.3.0. Gerard - This message was sent using HTTPS service from CNRS Grenoble. --- https://grenoble.cnrs.fr --- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] SIP Roadmap
Hi Phil friends, On Thursday 02 January 2003 20:10, Phil Thompson wrote: For those interested I've added a SIP Roadmap to the website at http://www.riverbankcomputing.co.uk/sip/roadmap.php which describes the main objectives and features for SIP v4. Comments welcome. This roadmap sounds very nice and reasonable. But what are your plans concerning point 18, 22, 23 and 24 from sip TODO? Phil Hans-Peter ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] SIP Roadmap
On Friday 03 January 2003 11:46 am, [EMAIL PROTECTED] wrote: For those interested I've added a SIP Roadmap to the website at http://www.riverbankcomputing.co.uk/sip/roadmap.php which describes the main objectives and features for SIP v4. Comments welcome. As author of PyQwt, an extension package that I support also on Qt-230-NC, I have the following comments: (1) wrt the obeying to the Python API export rules. This also facilitates the link step on other platforms than MacOS/X: under current scheme this is a minor problem on Posix systems, but on Windows, it means rebuilding PyQt-NC and sip-NC to rebuild the necessary *.exp and *.lib. Great! I hadn't appreciated that. I'll try and remember to include a sub-package, excluded from the Typical installation, that includes the .exp and .lib files. Remind me when I forget. (2) wrt to the limitation to Qt = 3.0.0. This will make it more difficult for me to keep PyQwt compatible with Windows (I have no commercial version for Qt, neither for PyQt). Let me point out that I know of at least 2 companies with a commercial license for PyQt that are also using PyQwt. Actually the real problem is that (1) requires qmake rather than tmake. I don't think there will be an issue with Qt itself. From a more general point of view: (3) Using the new-style Python-2.2 classes allows to map a C++ inheritance tree to Python (I have played with this, writing a wrapper for Fltk by hand). This is a great step forward for sip, also as a wrapper tool for other libraries than Qt. In this respect, it would be nice if there is support for two Python sip extensions modules, sipQt and sip, with and without Qt support. How would that help? If you use a non-Qt wrapper with a Qt-sip module, it will work fine. If you try a Qt wrapper with a non-Qt-sip module you will get an exception. In summary, sounds great, but I'd like to keep support for Qt = 2.3.0. As I said, it comes down to tmake/qmake. tmake doesn't support plugins which is what a pure Python module is - but maybe that won't be an issue for Windows and UNIX. It will be worth playing with once snapshots of SIP v4 appear. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] SIP Roadmap
On Friday 03 January 2003 12:05 pm, Hans-Peter Jansen wrote: Hi Phil friends, On Thursday 02 January 2003 20:10, Phil Thompson wrote: For those interested I've added a SIP Roadmap to the website at http://www.riverbankcomputing.co.uk/sip/roadmap.php which describes the main objectives and features for SIP v4. Comments welcome. This roadmap sounds very nice and reasonable. But what are your plans concerning point 18, 22, 23 and 24 from sip TODO? The Roadmap isn't intended to cover everything - but I don't perceive these to be as important. Of course one purpose of the Roadmap is to enable people to change my perception. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] SIP Roadmap
On Friday 03 January 2003 13:21, Phil Thompson wrote: On Friday 03 January 2003 12:05 pm, Hans-Peter Jansen wrote: This roadmap sounds very nice and reasonable. But what are your plans concerning point 18, 22, 23 and 24 from sip TODO? The Roadmap isn't intended to cover everything - but I don't perceive these to be as important. Of course one purpose of the Roadmap is to enable people to change my perception. Well, while 18, 22, and 23 would allow the user to follow more pythonic approaches (and help also reducing hand written sip code), I do remember some difficulties in advanced QSQL handling without Qt property support, which is on of the big sell arguments for Qt3, IMHO. I can dig into the details again, if you want. Phil Pete ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] SIP Roadmap
On Friday 03 January 2003 1:12 pm, [EMAIL PROTECTED] wrote: On Friday 03 January 2003 11:46 am, [EMAIL PROTECTED] wrote: For those interested I've added a SIP Roadmap to the website at http://www.riverbankcomputing.co.uk/sip/roadmap.php which describes the main objectives and features for SIP v4. Comments welcome. As author of PyQwt, an extension package that I support also on Qt-230-NC, I have the following comments: (1) wrt the obeying to the Python API export rules. This also facilitates the link step on other platforms than MacOS/X: under current scheme this is a minor problem on Posix systems, but on Windows, it means rebuilding PyQt-NC and sip-NC to rebuild the necessary *.exp and *.lib. Great! I hadn't appreciated that. I'll try and remember to include a sub-package, excluded from the Typical installation, that includes the .exp and .lib files. Remind me when I forget. (2) wrt to the limitation to Qt = 3.0.0. This will make it more difficult for me to keep PyQwt compatible with Windows (I have no commercial version for Qt, neither for PyQt). Let me point out that I know of at least 2 companies with a commercial license for PyQt that are also using PyQwt. Actually the real problem is that (1) requires qmake rather than tmake. I don't think there will be an issue with Qt itself. I think that you are wrong, here. See below. From a more general point of view: (3) Using the new-style Python-2.2 classes allows to map a C++ inheritance tree to Python (I have played with this, writing a wrapper for Fltk by hand). This is a great step forward for sip, also as a wrapper tool for other libraries than Qt. In this respect, it would be nice if there is support for two Python sip extensions modules, sipQt and sip, with and without Qt support. How would that help? If you use a non-Qt wrapper with a Qt-sip module, it will work fine. If you try a Qt wrapper with a non-Qt-sip module you will get an exception. I suppose you are right. I just had the idea that it would be more clear if you use sip to wrap classes for systems without Qt. In summary, sounds great, but I'd like to keep support for Qt = 2.3.0. As I said, it comes down to tmake/qmake. tmake doesn't support plugins which is what a pure Python module is - but maybe that won't be an issue for Windows and UNIX. It will be worth playing with once snapshots of SIP v4 appear. IMHO, the point that you are missing is that Qt style plugins and Python extension module plugins are two different type of plugins. If you are using the Python import API, the extension module is a shared library from the point of view of Qt (or the linker). The import_QtOtherExtension() statement in the initQtExtension() function takes care of dynamic loading. The point is that on some platforms plugins are different from shared libraries - MacOS/X being the most relevant example. tmake doesn't know about those differences (ie. the different flags that need to be passed to the link/loader) - qmake does. Python does not care about Qt style type of plugins. So, I am pretty confident that you can keep support for Qt 3.0.0. If it turns out that the only platform with this issue is MacOS/X (but I would also have concerns about AIX) then the problem goes away because it needs Qt3 anyway. What I might do is allow tmake to be used with SIP v4, but say it is unsupported until it is proved to be Ok. Phil ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
RE: [PyKDE] SIP Roadmap
On 02-Jan-03 Phil Thompson wrote: For those interested I've added a SIP Roadmap to the website at http://www.riverbankcomputing.co.uk/sip/roadmap.php which describes the main objectives and features for SIP v4. Comments welcome. I think it looks great - I especially like the Python 2.2 features as I switched completely to 2.2 quite a while ago. I'm not opposed to the Qt3.0 cutoff either - that will make it necessary to cutoff PyKDE at 3.0 also. Jim ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
