In this week's KDE CVS-Digest: Ruby bindings now have DCOP support.
Reaktivate, a Konqueror module for embedding ActiveX controls, is improved.
RealRekord, an application to record RealPlayer streams, is imported.
KConfEdit adds a property editor.
Dot Categories:
Comments
>wish #35130 (includes original URL in .war archives)
Was waiting for this one a long time now.
Extrêmely useful when doing some research on a specific topic. No need to switch between bookmarks and the war files. A great improvement for my "producticity" :)
Thanks
I notice that the Swedish translation team is always ahead of everybody else. This is the nth time that the Swedish team has 100% translation and the Danish and other slouches have abysmal figures like 99.27%. :-)
Go Swedish translation team, Go!
"What do you think about June 2004 KDE 3.3 beta and through July
release candidates and beginning of August 3.3?"
A late August release would be awesome. People have to keep in mind that these are 0.x releases and hence should not go through such a long cycle and include so many new features. Frequent releases are much better. It's a little like washing yourself ;) What would you prefer, a shower everyday or a big long bath every week?
Agreed.. it's worked for KDE before as well, for example, the KDE 2.0->2.1 cycle, which was 5 months, and the KDE 2.1->KDE 2.2 cycle, which was 5 and a half months long.
KDE 3.x release tend almost to be revoluationary instead of evolutionary, which is cool, but I still liked the 2.x cycles better :)
Hi,
back then, KDE was struggling to become "good enough". Now that it is, the pressure to release that frequent has dropped.
Anyway, I agree that KDE could consolidate its leadership very well with a polished 3.3 release. The KDE Quality Team needs a relative close release date to get its workings tested.
Yours, Kay
> back then, KDE was struggling to become "good enough". Now that it is, the pressure to release that frequent has dropped.
KDE 1.x had also been "good enough"..
Good enough for its time. It's not good enough for now.
KDE 2.0 was not really good enough back then, IMHO. 2.1 was, though.
Actually 2.0 was very promising, 2.1 was good and 2.2 what I call "good enough"...
Since then, I am just amazed at what can be added.
Yours, Kay
1.1, 2.2, 3.3 ... all part of a grander scheme of things? ;-)
Oh my god, Aaron, when will 4.4 be release?
Yours, Kay
> Good enough for its time. It's not good enough for now.
Yeah, but I don't think KDE 3.2 would be good enough for 5 years down the road either.
Almost no program is. Although I have used Winword 6 a few months ago, and it´s a damn good word processor (and much more than I need :-)
It's impossible to build kdelibs from CVS without CUPS (--disable-cups) since a few days. This is a very annoying problem, more people here experiencing this?
OK, this works again (at least in HEAD). Link: http://lists.kde.org/?t=107844903100004&r=1&w=2
KDE 3.2 has finally landed on debian unstable :-)
To be precise, it's even 3.2.1!
And yes, it feels really faster. Applications & KDE startup, and
especially konqueror. Very nice, hats off kde hackers!!!!!
I am a little surprised (positively of course) that I can use kmail 1.5.4
(from KDE 3.1) in 3.2. I guess that's the thing with binary compatibility.
A happy user
Hi,
a few things are still missing, like kdesdk, quanta in newer versions, but I guess, that's hot on the heels.
Yours, Kay
A few? According to http://packages.debian.org/unstable/kde/ even kdenetwork and kdepim are missing.
Check again.
Its probably just not updated the website yet. They where all in when I asked for them.
- Can I use this with Sarge, too? How?
I tried to find some docs but I'm not sure what exactly to search for...
- Is there a howto that explains the sources.list stuff a little more in-depth than the Debian installation docs?
Use "apt-pinning"
The Web is full of advice how to do it.
However you'll no longer have "pure Sarge" after that.
In the future you may get dependency problems.
I am thinking the same but wait/hope for migration into Sarge after
the minimum of 10 days in Unstable
(and probably longer - as all dependencies with
all packages in Sarge have to be solved before migration).
Good luck!
O.L.
Thanks for the hints.