Hi all,
I've received the first version of Doug Bell's TreeLine in the PyQt 4 version.
So the first application that we have on openSUSE is on it's way to PyQt 4.
I've also found a volunteer to create initial packages for openSUSE in the
build system.
Now, after following the previous thread,
Hi all,
I've received the first version of Doug Bell's TreeLine in the PyQt 4
version.
So the first application that we have on openSUSE is on it's way to PyQt
4.
I've also found a volunteer to create initial packages for openSUSE in the
build system.
Now, after following the previous
Hello,
On Thursday 14 September 2006 17:39, Joachim Werner wrote:
The starting point is that we currently only have the kdebindings3 version
of
sip, PyQt, and PyKDE in openSUSE.
We don't really want to change this for the openSUSE 10.2 release, but at
the
same time I'd like to have
On Wednesday 13 September 2006 7:52 pm, Simon Edwards wrote:
On Wednesday 13 September 2006 14:28, Phil Thompson wrote:
On Tuesday 12 September 2006 13:02, Phil Thompson wrote:
One thing you need to check is that you can install kdebindings3 (ie.
PyQt3 using SIP3) and kdebindings4 (ie.
On Saturday 09 September 2006 00:08, David Boddie wrote:
If you have access to the pages on developer.kde.org, or can get an account
for that, it would be good to at least have links to other resources on
there.
FWIW, a 'normal' KDE SVN account allows you to edit d.k.o.
--
sebas
On Tuesday 12 September 2006 13:02, Phil Thompson wrote:
One thing you need to check is that you can install kdebindings3 (ie.
PyQt3 using SIP3) and kdebindings4 (ie. PyQt4 using SIP4) in the same
Python installation. I assume this is a requirement - so that people can
continue to use PyKDE3
On Tuesday 12 September 2006 12:08, Simon Edwards wrote:
Now the problem is the old PyFoo package. It depends on python2.5-kde
version 4.0 or better and hence sip 4, because sip 4 is what shipped in KDE
4.0. This is the version of sip that PyFoo runs on. If the new
python2.5-kde package for
On Tuesday 12 September 2006 13:02, Phil Thompson wrote:
One thing you need to check is that you can install kdebindings3 (ie.
PyQt3 using SIP3) and kdebindings4 (ie. PyQt4 using SIP4) in the same
Python installation. I assume this is a requirement - so that people can
continue to use PyKDE3
On Wednesday 13 September 2006 05:28, Phil Thompson wrote:
On Tuesday 12 September 2006 13:02, Phil Thompson wrote:
One thing you need to check is that you can install kdebindings3 (ie.
PyQt3 using SIP3) and kdebindings4 (ie. PyQt4 using SIP4) in the same
Python installation. I assume this
On Wednesday 13 September 2006 14:28, Phil Thompson wrote:
On Tuesday 12 September 2006 13:02, Phil Thompson wrote:
One thing you need to check is that you can install kdebindings3 (ie.
PyQt3 using SIP3) and kdebindings4 (ie. PyQt4 using SIP4) in the same
Python installation. I assume
On Tuesday 12 September 2006 01:59, Jim Bublitz wrote:
On Monday 11 September 2006 11:47, Simon Edwards wrote:
Then if I have a KDE program PyFoo that includes a Python C module (or sip
wrapper) and was developed for KDE 4.0, it will called something PyFoo2.5
and require KDE 4.0 or later.
On Saturday 09 September 2006 16:36, Phil Thompson wrote:
On Friday 08 September 2006 8:46 pm, Simon Edwards wrote:
What we want to be able to tell users and 3rd party developers is that a
KDE 4.0 application written in Python will work fine on any 4.0+ version
of
KDE, just like how it
On 11.09.06 20:47:31, Simon Edwards wrote:
On Saturday 09 September 2006 16:36, Phil Thompson wrote:
On Friday 08 September 2006 8:46 pm, Simon Edwards wrote:
What we want to be able to tell users and 3rd party developers is that a
KDE 4.0 application written in Python will work fine on
On Monday 11 September 2006 21:29, Andreas Pakulat wrote:
That's not quite true anymore, at least for Etch and onwards you'll only
have
python-qt3
which provides pyqt3 for python2.4 and 2.3 (atm, but possibly also 2.5).
I don't know how this new python policy works, but that is what
On Monday 11 September 2006 11:47, Simon Edwards wrote:
Then if I have a KDE program PyFoo that includes a Python C module (or sip
wrapper) and was developed for KDE 4.0, it will called something PyFoo2.5
and require KDE 4.0 or later. When KDE 4.1 comes out maybe Python 2.6 is
also out, but
On Friday 08 September 2006 23:42, David Boddie wrote:
On Friday 08 September 2006 21:11:25 +0200, Simon Edwards wrote:
On Friday 08 September 2006 01:51, David Boddie wrote:
Reading through the SIP files for PyKDE, you find lots of information
about the way the KDE APIs have evolved over
On Friday 08 September 2006 22:34, Jim Bublitz wrote:
On Friday 08 September 2006 12:11, Simon Edwards wrote:
[development testing time]
Right - mostly because the compiles take so long, and there are at least 5
releases (3.0.x - 3.5.x) to test against. But see below (I used to go down
to
On Friday 08 September 2006 21:44, Jim Bublitz wrote:
The other problem is having an environment to compile and test the code -
that turns out to be a big time consumer for me, especially if I'd have to
compile KDE. Which is why I wait for rpms before upgrading PyKDE. On the
other hand, PyKDE4
On Thursday 07 September 2006 11:17 pm, Hans-Peter Jansen wrote:
What I would like to see is Phil's new sip generation tool (if he's
willing to release it into the open world) applied to KDE, with the
(possibly) missing pieces added from Jim's presip. That way, the
maintainance work could be
On Friday 08 September 2006 9:34 pm, Jim Bublitz wrote:
I expect Phil's stuff is quite good, but I don't know how releasable it is
or whether Phil wants to keep it proprietary (which I would understand
completely). The other problem is likely that Qt uses less of C++ than
KDE does, so Phil may
On Friday 08 September 2006 8:46 pm, Simon Edwards wrote:
On Friday 08 September 2006 02:48, Jim Bublitz wrote:
I'm completely in favor of synching KDE and PyKDE
:-)
:
Seriously - 2 or 3 maintainers splitting up module responsibilities would
probably do it with decent communication and
On Saturday 09 September 2006 05:50, Sebastian Kügler wrote:
On Friday 08 September 2006 21:44, Jim Bublitz wrote:
The other problem is having an environment to compile and test the code -
that turns out to be a big time consumer for me, especially if I'd have
to compile KDE. Which is why I
On Saturday 09 September 2006 20:22, Jim Bublitz wrote:
Aren't you glad you asked?
Tremendously ;-)
I'll need some time to digest, though. And I'm travelling the next days.
Thanks for the detailing the matter!
--
sebas
http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
- - -
On Saturday 09 September 2006 05:04, Simon Edwards wrote:
On Friday 08 September 2006 22:34, Jim Bublitz wrote:
On Friday 08 September 2006 12:11, Simon Edwards wrote:
[development testing time]
Right - mostly because the compiles take so long, and there are at least
5 releases (3.0.x
On Saturday 09 September 2006 04:42, Simon Edwards wrote:
On Friday 08 September 2006 23:42, David Boddie wrote:
On Friday 08 September 2006 21:11:25 +0200, Simon Edwards wrote:
On Friday 08 September 2006 01:51, David Boddie wrote:
Reading through the SIP files for PyKDE, you find lots
On Saturday 09 September 2006 07:11, Phil Thompson wrote:
On Thursday 07 September 2006 11:17 pm, Hans-Peter Jansen wrote:
What I would like to see is Phil's new sip generation tool (if he's
willing to release it into the open world) applied to KDE, with the
(possibly) missing pieces added
On Friday 08 September 2006 01:51, David Boddie wrote:
Although KDE 4 looks like it's starting to take shape, I can't believe that
there's not going to be a lot of flux in the APIs before they stabilize
into a form that provides the features that have been promoted in various
places. I don't
On Friday 08 September 2006 00:26, Sebastian Kügler wrote:
It would be nice, however, to have something to play with in the meantime,
especially for those, that would like to ship their PyKDE when KDE4 is
released, or shortly thereafter. But then I'm not the one who has to run
after an
On Friday 08 September 2006 01:51, David Boddie wrote:
On Thursday 07 September 2006 23:03:14 +0200, Simon Edwards wrote:
While it would be nice to have ready made bindings for each new KDE release,
it's going to take some willingness on the part of the core KDE developers
to plan for this in
On Friday 08 September 2006 02:48, Jim Bublitz wrote:
I'm completely in favor of synching KDE and PyKDE
:-)
Seriously - 2 or 3 maintainers splitting up module responsibilities would
probably do it with decent communication and source control. I'm perfectly
willing to provide help. I don't
On Friday 08 September 2006 01:26, Sebastian Kügler wrote:
On Friday 08 September 2006 01:51, David Boddie wrote:
Although KDE 4 looks like it's starting to take shape, I can't believe
that there's not going to be a lot of flux in the APIs before they
stabilize into a form that provides the
On Friday 08 September 2006 18:53, Joshua J. Kugler wrote:
Let's get PyKDE in KDE SVN and get movin'. :)
There is already a spot in SVN for PyKDE and friends.
After Akademy I want to start playing with KDE4 and porting over some of my
stuff, and working on PyKDE at the same time to make that
On Friday 08 September 2006 12:11, Simon Edwards wrote:
On Friday 08 September 2006 01:51, David Boddie wrote:
On Thursday 07 September 2006 23:03:14 +0200, Simon Edwards wrote:
While it would be nice to have ready made bindings for each new KDE
release, it's going to take some willingness
On Friday 08 September 2006 12:46, Simon Edwards wrote:
On Friday 08 September 2006 02:48, Jim Bublitz wrote:
I'm completely in favor of synching KDE and PyKDE
:-)
:
Seriously - 2 or 3 maintainers splitting up module responsibilities would
probably do it with decent communication and
On Friday 08 September 2006 21:11:25 +0200, Simon Edwards wrote:
On Friday 08 September 2006 01:51, David Boddie wrote:
Reading through the SIP files for PyKDE, you find lots of information
about the way the KDE APIs have evolved over time. If the bindings were
too closely tied to some
On Friday 08 September 2006 08:53:52 -0800, Joshua J. Kugler wrote:
Right now, it seems the Ruby bindings have quite a bit of momentum, as
evidenced by the extensive page above. Whereas the python bindings page
has just a few links: http://developer.kde.org/language-bindings/python/
Most of
On Wednesday 06 September 2006 13:46, Hans-Peter Jansen wrote:
Am Dienstag, 5. September 2006 19:29 schrieb Joachim Werner:
SUSE has been shipping with PyQt/PyKDE installed in the default
system for quite a while. For PyQT/PyKDE 3 this was a no-brainer: The
HP printer tools are installed by
Am Donnerstag, 7. September 2006 23:03 schrieb Simon Edwards:
On Wednesday 06 September 2006 13:46, Hans-Peter Jansen wrote:
Am Dienstag, 5. September 2006 19:29 schrieb Joachim Werner:
SUSE has been shipping with PyQt/PyKDE installed in the default
system for quite a while. For
On Thursday 07 September 2006 23:03:14 +0200, Simon Edwards wrote:
On Wednesday 06 September 2006 13:46, Hans-Peter Jansen wrote:
which reminds me that the official kdebindings3-python package of KDE
3.5.4 is _way_ behind the current state of affairs.
True. One of the main problems here
On Thursday 07 September 2006 16:51, David Boddie wrote:
On Thursday 07 September 2006 23:03:14 +0200, Simon Edwards wrote:
On Wednesday 06 September 2006 13:46, Hans-Peter Jansen wrote:
which reminds me that the official kdebindings3-python package of KDE
3.5.4 is _way_ behind the
Am Dienstag, 5. September 2006 19:29 schrieb Joachim Werner:
Hi all,
SUSE has been shipping with PyQt/PyKDE installed in the default
system for quite a while. For PyQT/PyKDE 3 this was a no-brainer: The
HP printer tools are installed by default and need them, so we have
to install PyQt/PyKDE
On Tuesday 05 September 2006 23:20, Jim Bublitz wrote:
There's going to be a delay for PyKDE4, since KDE4 is still some time off
in the future (end of the year, as I recall). I don't really know what the
KDE4 will probably not be released this year. kdelibs and kdebase will
probably stabilise
Hi all,
SUSE has been shipping with PyQt/PyKDE installed in the default system for
quite a while. For PyQT/PyKDE 3 this was a no-brainer: The HP printer tools
are installed by default and need them, so we have to install PyQt/PyKDE (or
actually kdebindings3-python that contains them) by
On 05.09.06 19:29:14, Joachim Werner wrote:
Now I have requested the addition of PyQt v4 to the upcoming openSUSE 10.2
release. But I have met some resistance because there is not a single
application that needs it right now.
www.apaku.de/linux/xpathevaluator
Though I need to re-design the
Hi,
a first application that requires PyQt4 will appear soon. Eric4 the Python IDE
is in its final stage. I hope to release a first snapshot by the end of the
month. That could eventually find it's way into openSUSE.
Detlev
On Tuesday 05 September 2006 19:29, Joachim Werner wrote:
Hi all,
On Tuesday 05 September 2006 10:02, Andreas Pakulat wrote:
The cool thing about the openSUSE build service is that does not only
build RPMs for various flavours of SUSE Linux, but also packages for
Debian/Ubuntu,
Debian and possibly the next ubuntu release already contain PyQt4.
Yes, the
On Tuesday 05 September 2006 10:29, Joachim Werner wrote:
Hi all,
SUSE has been shipping with PyQt/PyKDE installed in the default system for
quite a while. For PyQT/PyKDE 3 this was a no-brainer: The HP printer tools
are installed by default and need them, so we have to install PyQt/PyKDE
On Tuesday 05 September 2006 19:29:14 +0200, Joachim Werner wrote:
It would also help to tell me about applications that are already using
PyQt 4 and should be added to openSUSE, or at least be available for
optional download on the build service.
Apart from the one mentioned by Andreas,
48 matches
Mail list logo
