Slashdot Mirror
KDE 3.0 is Out
Emilio Hansen noted that KDE 3.0 is
on their site. There
is no official announcement yet, but this looks like the real deal. No debian
packages yet, but you can snag RPMs from various distros or src for the
do it yourself. Updated by HeUnique:Here is the announcement, enjoy.
Slashdot their main FTP before the mirrors are ready. That's a really bright idea!
True warriors use the Klingon Google
KDE 3 is already apt-get_able for Conectiva Linux for a few days
/etc/apt/sources.list the lines:
Just make sure you have the snapshot in your
rpm ftp://ftp.nl.linux.org/pub conectiva/snapshot/conectiva main extra orphan gnome experimental games kde
rpm-src ftp://ftp.nl.linux.org/pub conectiva/snapshot/conectiva main extra orphan gnome experimental games kde
then:
apt-get update
apt-get install task-kde
apt-get clean
and go for it.
of course if you are not using the snapshot version yet, you might want to:
apt-get dist-upgrade
"I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
Well, I'm writing this with Konqueror/KDE 3.0.0 which I downloaded about six hours before this story got posted here. Ya know, there are some people who just can't wait ;-)
And there won't be a mess, things *might* just slow down a bit. After all, the KDE FTP server is not a homebrewn dial-up server or shit.
I show some freaking respect towards the developers. I like their stuff that much that I couldn't wait a minute to get my hands on their newest creations.
The only thing I dislike about this story getting posted is that there is no link to the mirrors page, which was were I looked first of course. Or a link to download.kde.org which shows there already ARE some FTP mirror sites having the 3.0 release.
You should've pointed towards theses URLs instead of flaming around, IMHO...
Oh please!
If you don't want it to be downloaded, don't make it available. If you want to conserve bandwidth to, let's say, push it out to the mirrors, then MODIFY YOUR ANONYMOUS USER ACCESS LIMITS.
You have complete control of how your stuff gets posted on your public ftp servers. Don't complain too loudly if you screw up and get slashdotted.
Gnome's panel *does* display a description rather than a name, and has for quite some time. When you click 'properties...' on a launcher, there's a field called "Comment". That's what shoes up when you mouse over the description.
-d
=== "Some people see the glass as half-empty. Others see it as half-full. I see the glass as too big." -G. Carlin.
It's generally a better practice to remove all your previous KDE packages. I've never gotten a -Uvh to work. Crashes, freezes, all sorts of wackiness usually result.
I have been using the KDE3-pre that's included in RH's Skipjack and I do have to say that it appears to be well worth the upgrade. It seems slower to start initially, but once it's running, it seems just fine.
And the xrender menu transparencies finally work (semi)correctly (i.e. less/no annoying menu flicker as it grabs the image behind itself).
I wish I had a kryptonite cross, because then you could keep Dracula and Superman away.
Check some screen shots out here. Keep in mind, these are only some of the possibilities. KDE is super-themable.
Lex orandi, lex credendi.
This link is pretty good.
It's not even been announced yet, so please don't take down kde.org by slashdotting it. Use a mirror, list here. I got it from the Norwegian mirror which was very fast for me (I'm in Norway, YMMV, look out your window and check). It's a cool 100 megs though.
"Oppression and harassment is a small price to pay to live in the land of the free." -- Montgomery Burns.
I must say that Konqueror 3.0 looks really good with antialiased fonts and great themes!
Kde 3.0 is an awesome release, that surely will help Linux to gain some users from you know who :)
Although I am still working on getting connected the to ftp server and have not yet installed it, I have seen some Screenshots of the 3.0 theme and think it's overall smoother and more professional looking than 2.2.
Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
About screenshots:
KDE 3 is very tunable, but most of the user interface hasn't changed significantly from KDE 2.2.2 (most of the work has been in polishing the internals, to correspond to the move to Qt 3) - apart from a couple of things, like the new file selection dialogue. Your best bet to see what KDE 3 can do is to go to the KDE theme website, KDE-Look.org.
About the feature list:
Here is the internal KDE 3 feature plan. There's also a link there to the features planned to be in KDE 3.1.
-- Help Digitise the Public Domain at DP.
Try this (from google's chache
;)
It all may be moot with 3.0 anyway but if you don't feel like upgrading right now
"Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
There's a solution for that different nonprofit projects' FTP main sites that don't want to be hammered before mirrors catch up.
Junkies posting stories to Slashdot use ftp.
Mirrors use rsync.
So just make it so that rsync and ftp processes access the release directory as different users on the server.
Don't allow access to the FTP user on the new release directory for some time until all mirrors update through rsync. Only then chmod the latest release directory to let anonymous ftp users in.
Chmod only takes a fraction of second to execute.
So in addition, there will be no poor soul that in a hurry would download a partially copied, uncomplete file...
You've always had to pair allocate/free constructs in C and C++
I haven't done that for years. I just use constructs like the following:
Or, in some rare cases where the lifetime of the object is less obvious:
Add the careful use of auto-destroying and smart pointers to careful implementation of constructors and destructors and memory leaks are a complete non-issue for my C++ code. Using auto and smart pointers inside classes wastes a small amount of memory per instance, but, in many cases, makes default copy ctors and destructors do the Right Thing, reducing programmer error. Same thing works for other resources as well, like file handles, drawing contexts, etc.
Thus requiring consistent use of copy constructors, if only to print a message saying "you didn't really mean to copy me, did you?".
There's a better way. Make a class "Uncopyable", like so:
And provide *no* implementation for the copy ctor and assignment operator. Then, when you have a class that shouldn't be copied, just mix in Uncopyable like so:
There you are! Most accidental copies will be flagged by the compiler, because the copy methods of Uncopyable are private. Copies made within, for example, MyClass won't be caught by the compiler, but since there are no implementations of the Uncopyable methods, the linker will barf. This method has zero overhead; the only Uncopyable method that will ever be "called" is the default ctor, and it's empty and inlined. Uncopyable has no virtual functions, so no vtable. Any code that happens to generate calls to the copy ctor or the assignment operator is a bug that will be diagnosed by the linker.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
I'm pulling down the Redhat rpms at 154K and I'm not telling any of you where I got it from. yayaya prepositions at the end of sentences blah blah blah
Correction: KDE lets the user run whichever netwm-compliant window manager he wants, but uses its own kwin window manager by default.
There are some freeBSD packages at freebsd.kde.org, but they are not yet right. There is at least one known problem. They will be re-generating the packages soon, but they would like experts (those who can work around the current known problems) to find any other problems that need to be fixed before a general release is done.
A general release will probably be on freebsd.kde.org long before anyplace else. I'd expect ports to be updated in a couple days though, so cvsup once in a while.
FluxBox is no replacement for KDE, only for kwin, and it has KDE support.
Um, Mr. flipflapflup, there is evidently something you do not know. For a high-visibility package such as KDE, in order for everyone to get it, it has to get to the mirror sites. That's why when a release is made and put on a site, no announcement goes out: this is to allow at least a day for it to get to all the mirrors. If some dork posts an alert to Slashdot prematurely, the primary site gets hammered and the mirror sites can't get in. Everyone suffers from horrendously slow downloads from the primary site.
What's scary is that CmdrTaco evidently still does not realize this, and continues his irresponsible policy of announcing releases prematurely.
They used ports to generate the packages; they're waiting on the official release to put them on CVS.
And as of now there is the new page with the official KDE 3.0 screenshots as well. :-)
Both of the concepts you mentioned are implemented in boost's library (http://www.boost.org). Actually, std::auto_ptr is implemented in the C++ standard library, but boost has many different pointer types, including reference-counted pointers, weak-referenced pointers, and plain-jane scoped pointers. The library is robust and easy to use, and I highly recommend it.
Yes, it does. Although, you could have had this feature in KDE 2 just by using a window manager other than kwin.
-- Help Digitise the Public Domain at DP.
I had some problems getting the right support RPMS with my RH 7.1 system, but that's nothing I'm not used to.
As noted here by someone else, it's a little slow to start up. I wonder if that is an artifact of it starting up for the very first time. The look and feel are very similar KDE 2.2.2 for me.
The big difference so far is performance. Menus snap into place quickly, window operations are faster, pages render more quickly, the file manager is fast, and so on. My computer has a 300Mhz Celeron.
Also, a lot of web pages now work correctly, where they didn't in the 2.x series.
Overall stability is unknown at this point.
Your design to a real part online: Big Blue Saw
KDE 3.0.0 final tarballs were released to a group of packagers 9 days ago. That's how everyone has final packages, and that's why I have some packages that end in _3.0.0-1_i386.deb.
We have had experimental debs for some time, but have not wanted to release them to the public as they weren't ready for general consumption. The only release that was vaguely public was the whole RC4 fiasco, and its being made public was not my doing.
* cough*
KDE3 won't enter sid for a while yet; not until woody is released. Don't hold your breath. The reason we do this is because KDE2.2.2 currently takes up about 2.5gig of archive space, and forking with KDE3 would not only cause havoc with the woody release, but it would also make it impossible for us to issue any 2.2.2 fixes, and bloat the archive massively. I'm not going to be a party to this.
*cough*youwillhaveanaptsourcefrommeinabout12hours
Silly me, responding to this nonsense.
/. article Koffice is being developed by a group of around *six* people and the progress they've made so far is remarkable given their slender resources.
Please note that I use both KDE and Gnome, although mostly KDE, but I am formally involved in neither project.
Executive summary: the original writer is an ignorant bigot obsessed with licences and the fact that he can't program closed-source programs in QT without paying anything. He believes corporate support from Sun and HP is a fine thing for Gnome (didn't do much for CDE, though, did it?) but corporate support for KDE from the vastly smaller Trolltech is somehow sinister. The rest of his points are either (a) purely subjective, eg integration and look of the interfaces (b) flogging dead horses (eg the *alleged* GPL violation of KDE 1.x) (c) actionable libel, notably his accusations of a *funded* astroturf campain on behalf of the KDE team (d) childish and baseless character assassination of the KDE project and anyone or anything involved in it (e) vapourware or FUD.
Anyway, here's my point-by-point response:
"The KDE project is famous for its funded and organised trolling of weblogs and message board associated with Linux and Free software/open source. Outrageous newbie impressing claims are made for the software and huge quanities of FUD are spread to destroy competitors. If this sounds familiar, then you are correct, most of these tactics were lifted straight from Microsoft's arsenal of dirty tricks."
This is an outrageous slur! Some proof please? Remembers, extraordinary claims require extraordinary evidence... In particular, who pray tell is funding this campaign?
I'm not aware of Gnome lacking in advocates!
Myth #1 - KDE is more integrated than GNOME
Yes it is; the application and dialog behaviour is far more consistent and the structure is modular with applications able to use a wide variety of services. I'd expect the gap to narrow as GTK develops further.
Myth #2 - KDE is easier to use
Yes it is, because of greater interface consistency and (for most users) its much criticised default Windoze look&feel (see above).
Red Carpet seems to run fine on Red Hat but it's a nightmare on SuSE which I use; I've found it worse than useless.
I note that you have had to include Ximian tools to propose superiority over KDE; this is like me saying that, say, a SuSE-enhanced KDE with the same tools would be a match.
Myth #3 - KDE is more popular
"In what sense? Arguably more people use KDE, but it is a close run thing. "
You've just said it - you believe KDE is more popular.
Commercial use? Name me one HP and Sun which *right now* ships with Gnome as its default interface. And stop trying to sell futures (just how late is Gnome 2 running???)
Myth #4 - Konqueror is the best Linux browser
It's the one I most use because it is (a) faster than Mozilla (b) has extremely flexible cookie handling (c) has that nice Duplicate Window feature (d) renders nearly everything fine (e) works really well as a file browser as well.
Yes, it has problems with Javascript (apparently fixed in KDE 3). For those pages that give problems I use Mozilla. But I don't use Mozilla as my default browser. For me Konqueror is *the best all-rounder*. Your mileage may vary; browsers are subjective things.
Since when is Nautilus the default Gnome browser rather than work in progress???
"Myth #5 - KDE applications are better/more advanced than GNOME ones due to the ease of developing in C++ using the Qt toolkit "
KDE's applications have been written from scratch. Gnome in many cases (eg GIMP and OpenOffice) has taken on board as "Gnome" applications that were already well advanced before Gnome was out. I have no problem running either of these applications under KDE; does that make them part of the KDE project?
Please note that as per a recent
Please don't bullshit about how wonderful Gnome 2.x will be; I thought it was the KDE people who spouted vapourware... Please compare KDE with what Gnome has out *now*!
"Myth #6 - KDE is faster and takes less memory than GNOME "
I'm not a developer so I can't comment on your accusations about programming style, except to say that I would have thought that the much-touted Gnome advantage of being able to use any language rather than just C++ would make script kiddies far more at home than in KDE.
The gcc problem I understand is a very real one with c++ and the KDE crowd are as aware of that as anyone, and that pre-link etc are interim hacks.
I haven't done detailed tests but AFAICS Gnome and KDE run at pretty similar speeds on my machines; certainly there isn't enough difference for it to be a deciding factor.
"Myth #7 - GNOME development is slower. KDE releases faster. "
My greatest criticism of the Gnome project is the AFAIC amateurish way it is managed. KDE has maintained a far more disciplined development environment (easier partly because they have consistent releases of QT to build on) and keep hitting release target after release target. It seems to me that in Gnome too many things are going on at once (incrementally developing the toolkit as well as the applications and environment all at once) which makes development a less straight-forward and more iterative process.
"KDE is destined for noisy advocates porn and MP3 boxes." Please explain? I've worked in IT for twenty years, am in my mid-forties and use KDE as my standard work and home desktop. Oh, sorry, this is just another totally baseless slur.
"Myth #8 - The Qt toolkit is cross-platform and yet takes advantage of each individual platform "
And GTK compares how?
"Myth #9 - TrollTech is a friend of Free software
To Be Written. Ideas: Qt started out as non-Free. KDE developers knew this violated the GPL, didn't care, stole others' GPL code by porting it to link (in violation of the license) with Qt and are therefore untrustworthy. KDE core developers work for TrollTech. Expensive per developer licensing for writing closed-source with Qt, and hence KDE. Trolltech only moved towards the GPL because of the success of GNOME. Labyrinthine licensing nightmare (3 licenses to deal with). Gradual migration of features belonging in KDE into Qt (and so into TrollTech's IP portfolio), allowing easy porting of apps to the revenue generating Windows world (see TheKompany for a perfect example), thereby making KDE an irrelevant launcher of Qt applications. Claims made that Qt is GPL, while true, hide the real truth. There cannot be a real fork of Qt for the KDE project: Core developers work for Trolltech; any fork would need to be full GPL and hence ban any closed-source apps from KDE altogether (all KDE apps must link with Qt); Any commerical licensees of Qt (non-GPL) would and could only follow TrollTech. KDE is stitched up good and proper. "
Right, this is where I get really angry.
a. the GPL violation was *on RMS's definition of the GPL*. Fair enough, he wrote it. Note however that KDE was started by Germans who may have well understood it quite differently in translation and Europeans are less litigation-obsessed than Americans anyway. I believe that there was an honest misunderstanding and belief that they were fulfilling the spirit and letter of the GPL
b. "stole others GPL code". Not this chestnut again! The only GPL code that was wrongly linked I understand was a small part of the KDE 1.x printing code. This was corrected in KDE 2. No *developer* has ever come through and taken on the KDE team for this; it was a storm in a teacup initiated by the RMS cheer-squad to provide further justification for Gnome (which frankly I believe started off as an NIH exercise, with the licence issue a rationalisation).
The KDE developers were and are not "untrustworthy"; they merely formed an interpretation of the GPL which did not correspond to that of RMS. As they had a different first language and were in a different nation in a different continent with a quite different attitude to litigation this is understandable.
Or should only English-speaking Americans be allowed to develop GPL software? Oh that's right; Sun and HP are both American companies.
"KDE core developers work for TrollTech."
Let me get this straight: Sun and HP funding Gnome is OK but TrollTech, a tiny Norwegian concern, funding KDE isn't???? Are you for or against commercial sponsorship of open source software development?
"Expensive per developer licensing for writing closed-source with Qt, and hence KDE."
!GASP! You mean if you want to make money from closed-source apps Qt should be entitled to some? The bastards....
"Trolltech only moved towards the GPL because of the success of GNOME."
KDE is full-GPL now, so that is irrelevant. I should say, however, that effort via the early days of Gnome *for the sole purpose of sabotaging a competing project for the sole reason that its developers disagreed with a license interpretation* was the ugliest and most self-defeating (Micro$oft must have been laughing their arses off...) activity I've ever seen in the free software world.
"any fork would need to be full GPL and hence ban any closed-source apps from KDE altogether"
And your problem is?
"Any commerical licensees of Qt (non-GPL) would and could only follow TrollTech. KDE is stitched up good and proper. "
And it doesn't matter for GPL apps, which is what I thought we were most interested in. Is Gnome stitched up by the support of Sun and HP?
"Myth #10 - KDE is more than attractive, but GNOME/GTK is ugly
To be Written. Ideas: Mosfet liquid theme is an ugly and unstable hack. GNOME GTk icons are better thought-out and of a far higher quality than the poorly drawn and cartoonish and confusing KDE ones. Qt is basically a Windows-look on a Unix platform. "
Frankly, despite my use of KDE, I've always thought Gnome looked prettier on its default install. Remember however that the Windows-look interface to KDE is only a default and there are plenty of other icon kits you can use. Mosfet's theme, by the way, runs great for me and does not seem to make the system more unstable (and it has been extremely stable).
And back to the beginning:
"It is my hope that this, in some small way, will redress the balance and re-introduce two things almost eradicated by the KDE project: Honesty and facts. "
Nope, lies and more lies.
You might try going into KDE Control Center and turning off the animations. I have it on a 800mhz Duron box (256mb, GF2) and it performs beautifully.
KDE defaults to a "middle of the road" setting for window effects, etc. Turning them off speeds it up considerably. I've noticed much the same difference in speed ratios in Windows XP, and I suspect they are more hardware or hardware related driver issues then anything else.
One thing I also noticed was a small improvement in 2D desktop speed with the latest Nvidia driver rpms released a short time ago.
No matter what OS one uses, we still have to tweak for performance...
Cheers
Shadowbearer
Sig Mod: Only if the Dock DIES!
It's old. The more humans I meet, the more I like my cats. At least they are honest.