Stories
Slash Boxes
Comments
Search

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

KDE 3.0 is Out

Posted by CmdrTaco on Wed Apr 03, 2002 10:17 AM
from the congrats-to-the-hackers dept.
GUI KDE
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.
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

KDE 3.0 is Out 50 Comments More /

 Full
 Abbreviated
 Hidden
More
Loading... please wait.

  • KDE 3.0 Scoop (Score:5, Funny)

    by fruey (563914) on Wednesday April 03 2002, @10:20AM (#3276828) Homepage Journal
    What I want to know is who is spending time lurking on ftp sites to get scoops like this?

  • Give them a chance... (Score:4, Insightful)

    by rleyton (14248) on Wednesday April 03 2002, @10:21AM (#3276833) Homepage
    Good grief.

    Give the poor sods a chance to get the distribution ready, please. Perhaps they didn't WANT people downloading it just yet... Hence no announcement, just yet??

    Bandwidth and hosting costs money, as poor old distributed.net [distributed.net] is finding out. A few mirrors being updated, and then linking to the appropriate announcement would be a bit more considerate than putting up the first submission on the 3.0 release.

    • Surely if they didn't want people to get it yet, it wouldn't be visible on the ftp site yet! There are simple ways to allow the mirrors to get hold of copies before joe public, if they wanted to.

      How about giving the developers a bit of credit - I'm sute they know exactly what they are doing. I wouldn't be surprised if they leaked this "scoop" themeselves ;o)

      • flipflapflopflup is not insightful (Score:4, Informative)

        by JoeBuck (7947) on Wednesday April 03 2002, @01:39PM (#3278335) Homepage

        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.

      • Yeah, but accepting a TCP/IP connect, and sending a "we're full" message back, for thousands of Slashdotters, some of whom will have their software set to retry every second, will bring the box down.
  • As a user of KDE (and GNOME and WMaker), I am very happy to see this release. The RC's looked great so this must be even better. Now it's GNOME's turn... Keep the competition going, it makes everything better! Congrats to the KDE Team.

  • The mirrors... (Score:5, Informative)

    by adamwright (536224) on Wednesday April 03 2002, @10:24AM (#3276867) Homepage
    Please note, these don't seem to have propogated yet, but when they do...

    Germany ftp://ftp.kde.org/pub/kde/stable/3.0/
    USA ftp://download.us.kde.org/pub/kde/stable/3.0/
    United Kingdom ftp://download.uk.kde.org/pub/kde/stable/3.0/
    Australia ftp://download.au.kde.org/pub/kde/stable/3.0/
    Austria ftp://download.at.kde.org/pub/kde/stable/3.0/

    Lots more at http://www.kde.org/ftpmirrors.html

  • ftp.kde.org mirrors (Score:5, Informative)

    by carm$y$ (532675) on Wednesday April 03 2002, @10:25AM (#3276871) Homepage
    ftp://download.us.kde.org/pub/kde
    ftp://download. uk.kde.org/pub/kde
    ftp://download.au.kde.org/pub/ kde

    and so on, the full list here [kde.org].

  • Great idea! (Score:4, Informative)

    by codexus (538087) on Wednesday April 03 2002, @10:25AM (#3276880)
    Slashdot their main FTP before the mirrors are ready. That's a really bright idea!

  • How Incredibly Discourteous (Score:5, Insightful)

    by gnugeekus (463988) on Wednesday April 03 2002, @10:27AM (#3276896)
    The KDE developers have not announced the release of KDE 3.0 yet because the mirrors have not gotten KDE 3.0 yet. Since they have not announced the release, do you think there might be a *reason* they have not announced it?

    The editors at slashdot *know* the effect it has on a web site or ftp site when a story runs about that site. They *know* that the kde ftp site will get hammered because of this story. The *know* that the KDE developers obviously aren't ready yet BECAUSE THEY HAVE NOT ANNOUNCED THE RELEASE.

    Yet, you announce the story anyway, before the actual release. Now, the ftp site will be slammed *before* the mirrors get a copy, which insures that things will be a huge mess for quiet some time.

    This is the most incredibly discourteous and unprofessional behavior I've seen on a web site. Show some freaking respect towards the open source developers who create code (and give you something to write about on this site) and DO NOT ANNOUNCE A RELEASE BEFORE THE RELEASE.

    Your lack of caring about the impact of your actions on this site really disgusts me.

    • Re:How Incredibly Discourteous (Score:4, Interesting)

      by Accipiter (8228) on Wednesday April 03 2002, @10:41AM (#3277011)
      They've done this before [slashdot.org], and had the nerve to try to pass the blame on to the developers.

      Looks like this stupidity affects more than one of the editors.

      • Re:How Incredibly Discourteous (Score:4, Insightful)

        by FortKnox (169099) on Wednesday April 03 2002, @10:47AM (#3277043) Homepage Journal
        Isn't it funny. All the editors think this is just a personal site of theirs, and they don't need to have a perfessional manner.

        The fact is, they are a professional website, they get paid for running it, and they should act like professionals.

        Don't even get me started on how rude Michael really is, either...
    • 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 [kde.org], which was were I looked first of course. Or a link to download.kde.org [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...

    • I almost posted about this (Re: How Incredibly...) (Score:4, Insightful)

      by InodoroPereyra (514794) on Wednesday April 03 2002, @11:02AM (#3277136)
      This is the most incredibly discourteous and unprofessional behavior I've seen on a web site. Show some freaking respect towards the open source developers who create code (and give you something to write about on this site) and DO NOT ANNOUNCE A RELEASE BEFORE THE RELEASE.

      I totally agree. Even LinuxToday, beaten up to death some time ago by /. , was respectfull of the schedule and at least up to now did not announce anything (which by the way is natural since there was no announcement yet).

      Yesterday night I saw 3.0 in ftp.kde.org, and I almost posted a story (not supposed to be published) asking the /. editors to please NOT announce anything until the release was official . Then I thought, no, they will not do that again. Oh well ...

      • Re:How Incredibly Discourteous (Score:5, Insightful)

        by gnugeekus (463988) on Wednesday April 03 2002, @10:37AM (#3276977)
        What good would that do? Someone would find the files on a mirror, and instantly we'd get a slashdot story about the kde3 release with a link to the ftp site, and it would get slammed again.

        I think it is much easier and simpler for slashdot to not run false stories. In fact, the kde developers have NOT announced the release of KDE 3.0, and therefore, KDE 3.0 *has* *not* *been* *released*.
      • Just consider. Presume that 97.5% of Slashdot readers will be courteous. No, make that 99%. That means that only .01 will react inappropriately. Say that there are 10,000 slashdot readers who are both discourteous enough and interested enough to do the download (with a 5 second interval between tries).

        Then that gives 100 people trying every 5 seconds. This averages one try every .05 seconds. How long does a response cycle take?

        Now try to make a better guess at the real numbers.

        There are things that are wrong to do because of the effects that you can predict with fair certainty that they will have. In fact, those are the only things that are wrong to do (they are also the only things that are right to do, but that's a separate discussion).

        It is fairly certain that the posting of this story will cause the distributing servers to become clogged at nearly the worst time. Causing this to happen sounds to me like an ungood thing. If you do something, and the effects of doing it are predictable, then those effects are caused by what you did. Therefore this posting is the Slashdot editors causing the KDE servers to be overloaded.

        I'm not saying that the individual downloaders aren't also culpable. But that sure doesn't exonerate the Slashdot editor.

  • Valgrind and memory leaks (Score:3, Interesting)

    by johnjones (14274) on Wednesday April 03 2002, @10:27AM (#3276900) Homepage Journal
    I am still finding memory leaks via valgrind

    oh well it is a .0000000

    hopefully GNOME people will profile their code like KDE did for memory leaks

    because it really stablized when it was percived that memory was something to worry about

    regards

    john jones

    • I haven't had memory leaks in C++ in years--they are straightforward to avoid with consistent use of constructors/destructors. Where do those leaks occur in KDE code? Don't the KDE style guidelines make memory leaks impossible? If not, why not?

      • Re:Valgrind and memory leaks (Score:5, Insightful)

        by Anonymous Coward on Wednesday April 03 2002, @11:12AM (#3277201)
        Umm; try writing some real world application with more than 5 lines of code in it, and then come back here telling about impossible memory leaks.

        • Re:Valgrind and memory leaks (Score:5, Informative)

          by swillden (191260) <shawn-ds@willden.org> on Wednesday April 03 2002, @12:18PM (#3277716) Homepage Journal

          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:

          {
          auto_ptr<Foo> f = new Foo();
          // ....
          }

          Or, in some rare cases where the lifetime of the object is less obvious:

          {
          smart_ptr<Foo> f = new Foo();
          // ...
          }

          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:

          class Uncopyable
          {
          public:
          Uncopyable() {}
          private:
          Uncopyable(const Uncopyable&);
          void operator=(const Uncopyable&);
          };

          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:

          #include "uncopyable.h"
          class MyClass : Uncopyable
          {
          //...
          };

          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.

  • KDE3 -pre is in Red Hat's Skipjack (Score:5, Interesting)

    by MSG (12810) on Wednesday April 03 2002, @10:29AM (#3276919)
    I tried the CVS release of KDE 3 included in Red Hat's Skipjack beta. Like a man admiring his neighbor's well groomed lawn, I've got to say that it looks *beautiful*. There's some good stuff in there.

    One of my favorite features is that the panel can optionally display the "description" of each item, rather than the "name" of the application. That's far more useful for the novice user. I suggested that the GNOME panel do that about.... 2 years ago (??) on one of the gnome mailing lists, but never got around to submitting a patch myself.
      • I know about the tooltips, but that doesn't help novices much. Can you imagine a novice user looking at the menu for the first (or second, or ...) time and mouse-over'ing every item? (Ooo, what's this? Ooo, what's this? etc.)

        KDE's panel can now display the comment *as the menu label* which is what I suggested to the GNOME devel group way-back-when.

  • New KDE version? (Score:5, Funny)

    by Nighttime (231023) on Wednesday April 03 2002, @10:31AM (#3276934) Homepage Journal
    Then it must be time for the following posts:
    - how KDE kicks GNOME's butt
    - GNOME is now a dead-end for the Linux desktop
    - why GNOME 2.0 will be better
    - KDE looks too much like Windows
    - KDE loading times
    - KDE/GNOME are bloated, use iceWM/XFCE/Blackbox/whatever
    - who needs a GUI? the command line is where it's at
    - people making lists of expected posts :)

    Any more?

  • Ethics in Journalism? (Score:5, Insightful)

    by Trilaka (172371) on Wednesday April 03 2002, @10:33AM (#3276948)
    Is it just me, or does anyone else find this unethical behavior? Granted, the release of KDE 3.0 is News for Nerds, and Stuff that Matters, but is it so important to get the scoop on something like this that you are unwilling to allow time for propogation? For a popular software release like this, I believe the editors should consider it their ethical duty to wait for the official announcement, and post a list (or at least a link to a list) of mirror sites.

    The way it stands now, the mirrors may be having difficulty getting a copy of the distribution, as a hoard of eager slashdotters floods the primary ftp site.

    Just to recap, I have no problems with someone submitting this story as soon as they see they possibly can, but I believe the editors have a responsibility to be respectful in their decision when to post the story.

    • Slashdot != Professional Journalism (Score:5, Insightful)

      by Seanasy (21730) on Wednesday April 03 2002, @10:56AM (#3277094)

      Don't confuse Slashdot with journalism. The site is still run like a college kid's pet project. Sure they're making money and have thousands of readers but that doesn't make the staff qualified journalists/editors. They're geeks with a popular geek web-site -- nothing more.

      I come here almost everyday to see what they've collected because it's usually a nice mix. It has a the right amounts of tech, science and politics to keep me coming back. But, I never read their 'editorials' or Jon Katz because it's amateurish bunk. And, usually skip or skim the comments for the same reason :).

    • Re:Ethics in Journalism? (Score:5, Interesting)

      by stienman (51024) <adavis AT ubasics DOT com> on Wednesday April 03 2002, @10:57AM (#3277103) Homepage Journal
      Slashdot is a journal, and as such wants 'the scoop'. When they get 'the scoop' they post it. While it may not be nice, there are dozens of things the ftp manager can do to limit their problems. First (and most important) is to NOT RELEASE IT if it's not released. They can do this by disabling anonymous access to that directory, while enabling mirrors to log in and get access (either using IP, or ssh ftp with usernames and passwords, etc). This is something they will have to implement for following releases. It's plain common sense to give official mirrors front row seating and advance notice. Independantly run mirrors can wait like everyone else.

      No one would be complaining if some other tidbit of software was available but not announced at some other FTP site.

      The sooner people start treating slashdot like the Enquirer, the fewer people will complian. This site is not much more than mental candy for nerds, and provides very little real value to its users. But it is fun, interesting, and often entertaining.

      -Adam

  • KDE 3.11 (Score:5, Funny)

    by 9633 (570325) on Wednesday April 03 2002, @10:34AM (#3276959)
    When it reaches that version then we will have reached nirvana.

  • apt-get[able] for Conectiva Linux (Score:5, Informative)

    by rsd (194962) on Wednesday April 03 2002, @10:41AM (#3277008) Homepage
    KDE 3 is already apt-get_able for Conectiva Linux for a few days

    Just make sure you have the snapshot in your /etc/apt/sources.list the lines:

    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

  • Let the techies get to the stuff before it's announced, so the general public isn't locked out of the servers...

  • What's the correct way to upgrade my KDE? (Score:5, Interesting)

    by antdude (79039) on Wednesday April 03 2002, @10:45AM (#3277032) Homepage Journal
    I have Red Hat Linux 7.1 and 7.2 boxes. What's the correct way to upgrade from KDE v2.2.1 and v2.2.2? Should I uninstall KDE packages and then install or use rpm -Uvh?

    Thank you in advance. :)

    • Re:What's the correct way to upgrade my KDE? (Score:5, Informative)

      by ZaMoose (24734) on Wednesday April 03 2002, @10:56AM (#3277096) Homepage
      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).

        • Re:What's the correct way to upgrade my KDE? (Score:4, Interesting)

          by nitehorse (58425) <clee@kde.org> on Wednesday April 03 2002, @03:55PM (#3279355)
          Care to back that up?

          (And no, mosfet's web page doesn't count. How about you look at the code and decide for yourself?)

          Here, I'll back up the fact that it IS XRender. (code is from a CVS copy of kdelibs/kdefx/kstyle.cpp.)
          // Here we go, use XRender in all its glory.
          // NOTE: This is actually a bit slower than the above routines
          // on non-accelerated displays. -- Karol.
          void TransparencyHandler::XRenderBlendToPixmap(const QPopupMenu* p)
          {
          KPixmap renderPix;
          renderPix.resize( pix.width(), pix.height() );

          // Allow styles to define the blend pixmap - allows for some interesting effects.
          kstyle->renderMenuBlendPixmap( renderPix, p->colorGroup(), p );

          Display* dpy = qt_xdisplay();
          Pixmap alphaPixmap;
          Picture alphaPicture;
          XRenderPictFormat Rpf;
          XRenderPictureAttributes Rpa;
          XRenderColor clr;
          clr.alpha = ((unsigned short)(255*opacity) << 8);

          Rpf.type = PictTypeDirect;
          Rpf.depth = 8;
          Rpf.direct.alphaMask = 0xff;
          Rpa.repeat = True; // Tile

          XRenderPictFormat* xformat = XRenderFindFormat(dpy,
          PictFormatType | PictFormatDepth | PictFormatAlphaMask, &Rpf, 0);

          alphaPixmap = XCreatePixmap(dpy, p->handle(), 1, 1, 8);
          alphaPicture = XRenderCreatePicture(dpy, alphaPixmap, xformat, CPRepeat, &Rpa);

          XRenderFillRectangle(dpy, PictOpSrc, alphaPicture, &clr, 0, 0, 1, 1);

          XRenderComposite(dpy, PictOpOver,
          renderPix.x11RenderHandle(), alphaPicture, pix.x11RenderHandle(), // src, mask, dst
          0, 0, // srcx, srcy
          0, 0, // maskx, masky
          0, 0, // dstx, dsty
          pix.width(), pix.height());

          XRenderFreePicture(dpy, alphaPicture);
          XFreePixmap(dpy, alphaPixmap);
          }
          Now, like I was saying, where's your backup? Hell, I'll even quote mosfet's web page about this one.

          (from mosfet's liquid web page [mosfet.org])

          Where Liquid and KDE3's implementation differed was that KDE3 can optionally use XRender to shade the background pixmap, while Liquid will always use the blending methods I included in KPixmapEffect.


          Now, mosfet has a funny position here. He says "It's not really XRender" and then he admits that we use XRender to shade the background pixmap. This is exactly what we claim. The method of transparency is chosen by the user in the KDE Control Center. There are options for Software Tint, Software Blend, and XRender Blend. Nobody claimed that these were 100% Real Translucent Menus (Just like in MacOS X!). We're still waiting for keithp and his magical X Translucency Extension before we can promise that.

          But really. Don't you have anything better to do than troll about how "it's fake"?

  • New to Linux world (please be gentle) (Score:3, Interesting)

    by nobodyman (90587) on Wednesday April 03 2002, @11:01AM (#3277132)
    So, I'm really really ignorant of all of these window managers and what the distinctions are between X11, KDE, Gnome, Windowmaker, etc. I've been to gnome.org and kde.org, but I was hoping to find one big uberpage that laid it all out from square one.

    I feel somewhat like Homer Simpson when he tried to drum up business for the bowling alley (first reading advanced economics, then introductory economics, then finally websters dictionary).

    Anyone got a link or two?

  • At least use a mirror! (Score:5, Informative)

    by RPoet (20693) on Wednesday April 03 2002, @11:03AM (#3277145) Journal
    It's not even been announced yet, so please don't take down kde.org by slashdotting it. Use a mirror, list here [kde.org]. I got it from the Norwegian mirror [sunsite.uio.no] which was very fast for me (I'm in Norway, YMMV, look out your window and check). It's a cool 100 megs though.

  • Better looking.... (Score:5, Informative)

    by JPriest (547211) on Wednesday April 03 2002, @11:19AM (#3277294) Homepage
    Although I am still working on getting connected the to ftp server and have not yet installed it, I have seen some Screenshots [kde-look.org] of the 3.0 theme and think it's overall smoother and more professional looking than 2.2.

  • Why not post it to Usenet? (Score:4, Interesting)

    by Dr. Spork (142693) on Wednesday April 03 2002, @12:39PM (#3277875)
    Look, obviously, a ton of people will be downloading this, and the people hosting it are just volunteers who support KDE out of goodwill. I think major releases like this should just be posted to usenet. I mean, 100 Megs (or even 700 megs for all the different binary distributions) is barely a drop in the usenet bucket, everyone would get excellent transfer rates, the ftp would be for people without usenet access, and everyone would be happy!

    Also, it would be an important example of how usenet binaries serve and important and legal purpose.

    I would really support a Slashdot code of ethics that says: you can't announce major software before the developers do unless you have already posted it to Usenet.

    • My sister (15 year old mall rat) now REFUSES to use windows, since I showed her linux. She used to complain that the box I had set up for her kept crashing, so I set up a dual-boot for her, to see if she could learn. Obviously, I wouldn't want her to become frustrated with something just because she couldn't understand it, so I set up something closest to what she understood.

      She understands how KDE works, because, for the most part, it's fairly intuitive. She did use linux. Not only is this a (small) proof of viability for linux in a consumer market, but it does show where even a "bloated" window manager can have it's place.

      Tell me, would you rather have a bloated window manager and the linux kernel, or windows for someone you loved?

    • Re:My wife uses KDE and likes it.. (Score:5, Insightful)

      by WildBeast (189336) on Wednesday April 03 2002, @11:54AM (#3277538) Journal
      well her needs are probably more than extremely basic. I tried that experience with my cousin, a casual user who doesn't know much about computers, so I rebooted in Linux and told him to try it out. His first impression is that it was ugly. He used KWord and plenty of other apps and most of the time he was unable to understand what was going on because of the lack of messages. Why not put messages like "Please wait while loading", "Cannot open file", etc.? Some apps have it but many don't.

      For some reason, he didn't like Mozilla. What bothered him is that he couldn't use the microphone to talk with his MSN Messenger Buddies, he could only type the messages. He didn't like the games much, im some games he had to use the mouse in other games he had to use the keyboard. What bothered him most in this is that he couldn't exit some games by clicking on the X, I told him that he had to press ESC.

      In short, there's way too many usability problems. If KDE or GNOME had at least 1 usability expert helping them, they would get rid of most of those problems.

    • Re:FreeBSD packages ready? (Score:4, Informative)

      by bluGill (862) on Wednesday April 03 2002, @01:01PM (#3278052)

      There are some freeBSD packages at freebsd.kde.org [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.

All trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the Poster. The Rest © 1997-2009 Geeknet, Inc.