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
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.