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 Saturday 09 September 2006 12:44 am, David Boddie wrote:
On Friday 08 September 2006 05:07:49 +0100 (BST), jim j wrote:
I have a problem while compiling the following code.
the code is given below:
%Module pyMyTimer
typedef void (*TIMERFP)(long);
struct _time
{
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
12 matches
Mail list logo
