On Tue, Jun 22, 2004 at 08:38:19AM +0200, Simon Edwards wrote:
> I commited a copy of SIP, PyQt and PyKDE to KDE CVS on the weekend . . .
Major milestone! Kudos!
___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinf
rsions against
> Mdk and RH.
Well, if I wasn't convinced this was in good hands before I certianly
am now. I'll wait patiently for SuSE rpms that will be ready, well,
when they're ready.
Thanks for the work, Jim.
Steve Simmons
--
Transported to a surreal landscape, a youn
> How do people here feel about the current state of PyQt/PyKDE in relation to
> KDE (the project)? Is it a real problem for people that PyQt/PyKDE isn't
> distributed as part of KDE? or would it be enough if the distros also came
> with PyQt/PyKDE as 'standard'?
I'd prefer that PyQt/PyKDE came
On Wed, Aug 13, 2003 at 10:12:33AM -0500, Frederick Polgardy Jr wrote:
> I definitely have to second this. (Would that be: this->second()? I
> guess for a std::pair it would be just this->second. Ugh, feel free to
> just shoot me at any time. :))
No problem. :-)
I've watched C++ grow since
On Wed, Aug 13, 2003 at 08:53:45PM +0200, Simon Edwards wrote:
> When it comes to programmers and OO languages that's the real problem. Few
> programmers truly grok the zen of OO (love that phrase).
It would be even better if talking about object-oriented modelling.
--
"I don't like being quote
provide a good venue for such cross-language
discussions. It seems to me that the PyKDE folks might have an
interest in this, tho right now I can't predict where or how. But
if you're interested, you can follow the discussion and tentative
proposal ideas at <http://mini.net/tcl/9589>
On Wed, Jul 09, 2003 at 02:14:33PM -0700, Jonathan Gardner wrote:
> On Wednesday 09 July 2003 13:32, Steve Simmons wrote:
> > On Wed, Jul 09, 2003 at 03:49:46PM -0400, Rob Knapp wrote:
> > I would normally do 'python build.py' and 'make' as an ordinary
&g
On Wed, Jul 09, 2003 at 03:49:46PM -0400, Rob Knapp wrote:
> These issues have been resolved. I'm just noting them here in case anyone
> else has the same problem. Not sure how they would since it was my
> own idiocy...but I can't be the only one this unobservant, can I?
Nope, I did it too.
I