In this week's KDE-CVS Digest: Python bindings for Qt and KDE are now in kdebindings.
amaroK now has JavaScript scripting.
kutils adds incremental find. kwin adds window specific settings GUI.
Dot Categories:
In this week's KDE-CVS Digest: Python bindings for Qt and KDE are now in kdebindings.
amaroK now has JavaScript scripting.
kutils adds incremental find. kwin adds window specific settings GUI.
Comments
As everybody, I have to thank you for this nice digest, I'm not on kde maillist, but enjoy the digest, and compile KDE from CVS almos every week.
Thanks !!
Mail from their main yahoo-messenger-for-unix-hacker:
http://groups.yahoo.com/group/ymessenger/message/2230
oh, and thanks to Derek for his work!
I always wanted the Python bindings to be in the official KDE and this is great news as currently the ones I downloaded are not working. =( Anyway, python and Python Qt are simply amazing and I hoep their use in KDE and eslewhere will rise dramtically.
I'm also glad that YahoO! is diching their hideous and dysfunctional GTK 1.2 client and rewritting it for KDE =) I'm sure they will be pleased with Qt as well as KDE's ease of development.
A whole bunch of packages for PyQt/PyKDE have been release lately. Try download again (or just wait for 3.3 to appear, that's if you _can_ wait. :-) )
http://sourceforge.net/project/showfiles.php?group_id=61057
cheers,
--
Simon
Finally! I've been waiting for this day for at least two years. I look forward to a flood of KDE-ized Python apps.
Are great! A bit of documentation would be good though ;)
You are more than welcome to help with it :).
Yeah, but before I have to understand how it works :)
This has now been tagged as stated in the CVS Digest.
I updated to this with CVS and several packages wouldn't build. I'll have to try again to see which ones were hard errors and which ones were just being difficult.
I also notice that KDE-3.2.3 is rather buggy to the point that KDE-3.2.4 is needed.
So, I wonder, are we in a hurry to kick KDE-3.3.0 out the door? Is this a good thing? If it fixes all of the new bugs (regressions) in KDE-3.2.3 then I suppose it is. But, we need to be careful because my impression is that KDE's quality control has been slipping in the last few releases.
--
JRT
> I also notice that KDE-3.2.3 is rather buggy
Examples?
> So, I wonder, are we in a hurry to kick KDE-3.3.0 out the door? Is this a good thing?
The competition doesn't sleep. And all the new kdepim 3.3 features have to be released soon.
> Examples?
I have filed some bug reports and added my CC to ones that already existed.
I have been advised that the 3.2 branch will be closed so I was waiting to test the 3.3.0 BETA before filing more.
There are some problems with KWin focus behavior and I have had problems changing file permissions with a KFM window opened as SU -- theses are the two that come to mind.
> The competition doesn't sleep.
Yes, but I regard Windows as the competition. For many users the main complaint with Windows is that it is buggy. Therefore, I consider a bug free KDE more important than a lot of new features. The issue is how to release new features without the product becoming more buggy.
Especially important is to avoid new releases with regression bugs -- new features that don't work quite correctly are much less of a problem as long as you can turn them off.
We have had very noticeable (and therefore serious) regressions in the 3.2 branch and this should be avoided in the 3.3 branch.
--
JRT