Re: [PyQt] A couple of question about PyKDE4
Jim Bublitz wrote: Before I start out with PyKDE4, I have a couple of questions: - what is the preferred build system? cmake or configure.py? Will any of these build system vanish in the future? I haven't looked lately, but I think Simon is using cmake with the KDE SVN version. I'll be continuing to use configure.py. I'm pretty sure Simon will want to go with/stay with cmake, and that I'll stay with the configure.py setup. cmake support is needed to make it possible for people to build the whole kde-bindings module in one (big) go. I've also pulled out parts of that cmake code and made it possible to install PyKDE programs with it. Using cmake for a Python program means you also get access to the existing cmake support for building other KDE related things like translation (.po) files, docs, and C++ modules if you want to do mixed development. - are you going to make separate releases of PyKDE4, or will everything be coordinated with the KDE releases? I'll probably do separate releases - I'm behind again and won't be releasing for a month or two. If you are adding bug fixes to the KDE 4.0, then you could probably just skip the extra releases and just release via KDE SVN. KDE bug fix releases come out once a month these days, and we don't even have to lift a finger for that to happen. ;-) There's also a better set of documentation and a documentation viewer (pykdedocs) that integrates tutorials, example programs, docs and will let you browse other docs (Python, PyQt, Qt, KDE, etc) locally or online. The Ply-based tools will make it a lot easier to develop docs from the KDE doc set and is a much easier to maintain bunch of code. Once the docs are updated, and if the viewer is stable/complete enough, then we can put it in KDE 4.1. The only thing missing in PyKDE4 is Phonon support, which is a little messy (or was last time I looked). IIRC, Phonon will be moving into Qt itself, possibly in Qt 4.4. In which case it'll become Phil's problem. ;-) cheers, -- Simon Edwards | KDE-NL, Guidance tools, Guarddog Firewall [EMAIL PROTECTED] | http://www.simonzone.com/software/ Nijmegen, The Netherlands | ZooTV? You made the right choice. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] A couple of question about PyKDE4
On Tue, Feb 05, 2008 at 12:13:28PM -0800, Jim Bublitz wrote: I'll probably do separate releases - I'm behind again and won't be releasing for a month or two. What Simon has put in KDE SVN should be current and reasonably complete, and will likely stay that way. hi Jim. next week we'll have a PyCamp in my region and I think I can gather 3 or 4 guys to hack on pykde. how can we start helping? also, I'm confused... why do you and Simon work separately? -- (Not so) Random fortune: 13:13 sensei_sacuyista los de la salita 1, Marge Simpson, son todos putos 13:15 @perrito666 sensei_sacuyista: se dice con capacidades sexuales diferentes ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] A couple of question about PyKDE4
On 07.02.08 21:11:21, Simon Edwards wrote: The only thing missing in PyKDE4 is Phonon support, which is a little messy (or was last time I looked). IIRC, Phonon will be moving into Qt itself, possibly in Qt 4.4. In which case it'll become Phil's problem. ;-) Not exactly. As far as I've heard from people involved with phonon, its going to be in both Qt4.4 and also stay in kdelibs as well. The plugins for Win32/MacOS and gstreamer already where in kdebase sometime last year (but weren't ready for release and thus moved to extragear for now). The devs said they'll try that both versions stay in sync, but obviously there'll be small differences as KDE and Qt release cycles are not aligned. Of course if Phil provides bindings for phonon in the PyQt4.4 release, its probably easy for you or Jim to adapt the small changes that might happen in kdelibs :) Andreas -- You're at the end of the road again. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] A couple of question about PyKDE4
Hi all, Debian's KDE team has started to package KDE 4.0 quite some time ago, and they have asked me if I had plans to package PyKDE 4.0. Before I start out with PyKDE4, I have a couple of questions: - what is the preferred build system? cmake or configure.py? Will any of these build system vanish in the future? - are there going to be separate releases of PyKDE4, or will everything be coordinated with the KDE releases? - is there any high-level documentation about krosspython? Forgive my ignorance, but I've never come across it. (I'd *guess* that it's for embedding PyKDE4 scripts as components in KDE programs) thanks for your help, Torsten -- Torsten Marek [EMAIL PROTECTED] ID: A244C858 -- FP: 1902 0002 5DFC 856B F146 894C 7CC5 451E A244 C858 Keyserver: subkeys.pgp.net signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] A couple of question about PyKDE4
On Tuesday 05 February 2008 11:49, Torsten Marek wrote: Hi all, Debian's KDE team has started to package KDE 4.0 quite some time ago, and they have asked me if I had plans to package PyKDE 4.0. Before I start out with PyKDE4, I have a couple of questions: - what is the preferred build system? cmake or configure.py? Will any of these build system vanish in the future? - are there going to be separate releases of PyKDE4, or will everything be coordinated with the KDE releases? - is there any high-level documentation about krosspython? Forgive my ignorance, but I've never come across it. (I'd *guess* that it's for embedding PyKDE4 scripts as components in KDE programs) Hi Torsten - On Tuesday 15 January 2008 08:40, you wrote: Hi Jim, Debian's KDE team has started to package KDE 4.0 quite some time ago, and they have asked me if I had plans to package PyKDE 4.0. It's been quite some time since I've done serious work with PyQt and PyKDE, my packages are in maintenance mode mostly. I'd actually like PyKDE4 to be an opportunity to get a good look at KDE 4.0 and probably do some GUI programming again. Before I start out with PyKDE4, I have a couple of questions: - what is the preferred build system? cmake or configure.py? Will any of these build system vanish in the future? I haven't looked lately, but I think Simon is using cmake with the KDE SVN version. I'll be continuing to use configure.py. I'm pretty sure Simon will want to go with/stay with cmake, and that I'll stay with the configure.py setup. The latter depends on sip support, so if Phil changes that, I'll have to change my setup/install stuff, but it's likely I'll stay with some kind of Python scripting. Of course nothing lasts forever, but I don't see anything that would change my mind in the near future. - are you going to make separate releases of PyKDE4, or will everything be coordinated with the KDE releases? I'll probably do separate releases - I'm behind again and won't be releasing for a month or two. What Simon has put in KDE SVN should be current and reasonably complete, and will likely stay that way. We're a little out of sync at the moment because he's still using the original PyKDE tools (presip + scripts) to develop PyKDE. My holdup is largely finishing a new toolset for PyKDE based on Ply (Python Lex-Yacc) rather than a handwritten parser. There's also a better set of documentation and a documentation viewer (pykdedocs) that integrates tutorials, example programs, docs and will let you browse other docs (Python, PyQt, Qt, KDE, etc) locally or online. I don't know if Simon has included that yet. The viewer software is all PyKDE4 based, so I have had a chance to test out a lot of the GUI and KParts/KHTML related stuff, and it was working very nicely. The Ply-based tools will make it a lot easier to develop docs from the KDE doc set and is a much easier to maintain bunch of code. The only thing missing in PyKDE4 is Phonon support, which is a little messy (or was last time I looked). - is there any high-level documentation about krosspython? Forgive my ignorance, but I've never come across it. (I'd *guess* that it's for embedding PyKDE4 scripts as components in KDE programs) Kross is for embedding Python scripts in KDE apps - that could use PyKDE (I think), but isn't dependent on it or sip. I think Sebastian Kugler ([EMAIL PROTECTED]) is the lead developer - we've exchanged a few messages (email or at dotKDE - don't recall which), but there isn't any connection between Kross and PyKDE. I haven't seen any Kross docs, but haven't looked in a while (that's about the third or fourth time I've said something like that - I am a little behind on most of this). Jim ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] A couple of question about PyKDE4
On 05.02.08 12:13:28, Jim Bublitz wrote: On Tuesday 05 February 2008 11:49, Torsten Marek wrote: - is there any high-level documentation about krosspython? Forgive my ignorance, but I've never come across it. (I'd *guess* that it's for embedding PyKDE4 scripts as components in KDE programs) Kross is for embedding Python scripts in KDE apps - that could use PyKDE (I think), but isn't dependent on it or sip. I think Sebastian Kugler ([EMAIL PROTECTED]) is the lead developer - we've exchanged a few messages (email or at dotKDE - don't recall which), but there isn't any connection between Kross and PyKDE. Its actually Sebastian Sauer and there are some Kross tutorials on http://techbase.kde.org/index.php?title=Development/Tutorials#Kross. Also the kate devs have a looked a bit into Kross lately and written some sample code: http://lists.kde.org/?t=12002331483r=1w=2 Andreas -- You're definitely on their list. The question to ask next is what list it is. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
