Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
KDE GUI

KDE 3.0 is Out 564

Posted by CmdrTaco from the congrats-to-the-hackers dept.
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.
This discussion has been archived. No new comments can be posted.

KDE 3.0 is Out More

KDE 3.0 is Out

Comments Filter:
  • It's a trap! Some guy on the KDE team has his desktop calendar all screwed up... he think's that TODAY is April 1!

    • Re:Watch out... (Score:2, Offtopic)

      by knulleke ( 557202 )
      It's a trap! Some guy on the KDE team has his desktop calendar all screwed up... he think's that TODAY is April 1!

      I wish I had a beowulf cluster of april 1st jokes.

  • KDE 3.0 Scoop (Score:5, Funny)

    by fruey ( 563914 ) on Wednesday April 03, 2002 @11: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 @11: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.
    • It's not really slashdotted, just all the anon slots on their ftp server are full, so they really won't be using any more bandwidth than they wanted to.
      • 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.

    • 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 @02: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.

  • Long awaited by KDE'ers! (Score:3, Insightful)

    by NewbieSpaz ( 172080 ) <nofx_punkguy@lin ... UTrg minus punct> on Wednesday April 03, 2002 @11:22AM (#3276842) Homepage
    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 @11: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 @11: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 @11:25AM (#3276880)
    Slashdot their main FTP before the mirrors are ready. That's a really bright idea!

    • Re:Great idea! (Score:2, Informative)

      by kableh ( 155146 )
      Yea, really.

      Eds, you really shouldnt be posting a link to their FTP site. It encourages too many people to follow that link. Didnt we learn this lesson with kernel.org? Post a link to their mirror [kde.org] page.
    • 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...

  • How Incredibly Discourteous (Score:5, Insightful)

    by gnugeekus ( 463988 ) on Wednesday April 03, 2002 @11: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 @11: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 @11: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...
        • The fact is, they are a professional website, they get paid for running it, and they should act like professionals.


          If you don't like the lack of professionalism at Slashdot, don't go here. Don't trust it when it says "abc 1.2.3 released", ignore those stories and ignore those links. Ignore Slashdot alltogether and start/join a more professional site. Only take release announcements seriously from Freshmeat or something like that.


          This should indeed be fixed on the developers side. A simple solution would be a private FTP server from where all servers including ftp.kde.org sync. Shouldn't be too hard to set up, so I'll propose that on the mailinglists tonight. As KDE developer I might not be pleased with Slashdotted servers, but the closer to the source this can be fixed, the better.


          If Rob hadn't posted it, some other asshole would've placed a link on his site. ;-)

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

    • How Incredibly Discourteous (NOT) (Score:2, Informative)

      by Anonymous Coward
      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.
    • oh please! kde could have gotten the mirrors to sync yesterday morning before it was available for the general public. the release has been ready for a few days now.

      i've been trying to get 3.0 for a few days, (wanted to try rc3, but it wasn't available anymore), and saw it on kde's servers last night, but only the rpms, no source. i saw source this morning, but had to be persistant to get the downloads (350 of 350 anonymous users). i checked the mirrors this morning and they were a day behind. i would like to see someone from kde come out and explain why there isn't some corrdination with the main mirrors (download.us.kde.org, etc) to get them the files before the public can get them.

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

      by InodoroPereyra ( 514794 ) on Wednesday April 03, 2002 @12:02PM (#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 ...

    • With due respect to your position, the KDE group should know by now that if news like this is leaked and there's a credible place to verify it (e.g. an FTP site), it will be reported on by sites such as Slashdot.

      The onus is on anyone who wants to keep a secret, and steps should be taken to keep it that way until they're ready for its announcement, and IMHO this includes the KDE development team.

      A possible solution? Put the distribution on a mirrors-only site, let it propogate to the mirrors, put it up on your FTP site last.

      In my opinion, what the KDE group faces is the ante for participating in the information freedom, everyone collaborates, communicates and participates age.

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

    by johnjones ( 14274 ) on Wednesday April 03, 2002 @11: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 @12:12PM (#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.
        • try writing some real world application with more than 5 lines of code in it [without] memory leaks.

          It's quite doable if you use a decent language to start with. I'd recommend Smalltalk, Lisp, ML, etc. All of these (especially ML and Lisp) can reach "good enough" speeds to compete with C/C++ in the case of most GUI app and, where they don't, a few simple C stubs (which are much easier to check for memory leaks) are usually sufficient to remedy the issue.

          In short, don't excuse the difficulty of writing software on the basis of YOUR choice of poor technology.

      • Wow! Not that I don't believe you but my impression of C++ was that memory issues were worse because the compiler makes it easy to get a bitwise copy of an object and the first destructor that runs could leave dangling pointers in every other copy. Thus requiring consistent use of copy constructors, if only to print a message saying "you didn't really mean to copy me, did you?".

        You've always had to pair allocate/free constructs in C and C++. The syntax being different shouldn't make them less likely to occur. Whether I allocate a bit map using new char[10000] or malloc(10000), doesn't make much difference.

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

          by swillden ( 191260 ) <shawn-ds@willden.org> on Wednesday April 03, 2002 @01:18PM (#3277716) 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.

          • Both of the concepts you mentioned are implemented in boost's library (http://www.boost.org [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.
          • There's a better way. Make a class "Uncopyable", like so:

            Unfortunately MicroSoft has f**ked us there, if you are interested in making portable shared libraries. It will fail to build a shared library if the implementation of the function is not there. The best this does then is that non-member functions cannot do a copy, but unfortunately member or friend functions still can. Of course you can make the function abort but that is enourmously less useful than detecting things at compile time.

            I ifdef these things out on Unix but this useful thing is lost on Windows users.

        • Not that I don't believe you but my impression of C++ was that memory issues were worse because the compiler makes it easy to get a bitwise copy of an object and the first destructor that runs could leave dangling pointers in every other copy.

          C++ doesn't make bitwise copies of objects. The default copy constructors in C++ does a per-member assignment; that's important. And in order to avoid bad pointers, you disable the default copy constructors. That's easy to do and hard to overlook (in fact, you can grep for its occurrence).

          You've always had to pair allocate/free constructs in C and C++. The syntax being different shouldn't make them less likely to occur.

          It's not a question of syntax. With almost no exceptions, the only places new/delete should occur in well-written C++ code are in constructors and destructors. That, and a few other rules, ensure that you can't get memory leaks while still being able to express whatever you could in C. If KDE code calls new or delete anywhere else, it's unnecessarily inviting memory leaks.

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

    by MSG ( 12810 ) on Wednesday April 03, 2002 @11: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.
    • 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
      • 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.
  • Emilio Hansen noted that KDE 3.0 is on their FTP site. There is no official announcement yet,


    Thanks, ./ and Emilio. Maybe they wanted it to go out to mirrors, etc first before their sites were steamrolled.

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

    by Nighttime ( 231023 ) on Wednesday April 03, 2002 @11: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 @11: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 @11: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 :).

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

        Even so, those who disseminate information have a responsibility for the information they disseminate. The editors have a choice about whether or not to publish a story, and they should be fully aware of the repercussions of those choices, and should act in an ethical matter. Based on the facts that they know that this release has not been announced, and that web sites posted on slashdot generally get a large amount of traffic (heck, this is so prevalent that they named the phenomenon the Slashdot Effect), they should have chosen to be respectful.

        Whether or not the editors are professional journalists (which I believe it could be argued), is rather irrelevant. I don't believe that professionals are the only people that should be expected to be ethical.

        • Oh, I agree with you 100%. They should put more effort into growing as journalists/editors. I just don't expect them to make that effort. I do agree that they have a certain social responsibility to maintain a level of professionalism, I just don't think they can or are willing to make that commitment. Which is why I will never subscribe and I block ads on this site. I don't have the energy to try to push for change and I don't think they're interested.

          I could go on at length about this but I don't want to get into it that much. To summarize -- I don't think the editorial policy will ever change; not through public pressure either by complaints or exodus. So, I don't worry about it. I take what I can get from the site and move on.

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

        Slashdot is journalism (journalism lies in how it is read, now how it is written), and it is professional (after all, it is for-profit)-- it's just also a tabloid for the geeks. An in the greatest tradition of tabloid, Slashdot cares not about the subjects it covers, only about getting the "scoop" for its readership and then sensationalizing it.

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

      by stienman ( 51024 ) <adavis@@@ubasics...com> on Wednesday April 03, 2002 @11: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 @11:34AM (#3276959)
    When it reaches that version then we will have reached nirvana.

  • Its' great (Score:2, Interesting)

    by mike_mcc13 ( 138358 )
    I'm using the skipjack beta and the cvs version was so good i killed gnome

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

    by rsd ( 194962 ) on Wednesday April 03, 2002 @11: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

  • Maybe it's not Discourtious.. (Score:3, Informative)

    by Havokmon ( 89874 ) <rick@h[ ]kmon.com ['avo' in gap]> on Wednesday April 03, 2002 @11:43AM (#3277018) Homepage Journal
    Let the techies get to the stuff before it's announced, so the general public isn't locked out of the servers...

    • It's only the techies who would be downloading 3.0 instead of simply finding it on the CD of the distribution that they just purchased from CompUSA.

      Maybe this is in some way /. trying to get a First Post.

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

    by antdude ( 79039 ) on Wednesday April 03, 2002 @11: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 @11:56AM (#3277096)
      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).

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

    by nobodyman ( 90587 ) on Wednesday April 03, 2002 @12:01PM (#3277132) Homepage
    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 @12:03PM (#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.
  • I found a fast mirror... Stay away!
  • Kde 3.0 is looking goood! Have a look at my screenshots here [stud.ntnu.no] and here [stud.ntnu.no]!
    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 :)

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

    by JPriest ( 547211 ) on Wednesday April 03, 2002 @12:19PM (#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.
  • Has anyone else had problems compiling QT with -xft on Mandrake 8.1 ? Despite having XFT working in 2.2, when I specifiy -xft in configure, it still compiles without it. Anyone?

  • One thing that's starting to annoy me about debian (Score:3, Interesting)

    by gid ( 5195 ) on Wednesday April 03, 2002 @01:00PM (#3277590) Homepage
    Let me start out with saying that I think the Debian people are doing a good job with the resources they have. I love the distribution and the ease of upgrades. It takes a lot of time to package something correctly ahearing to all the Debian rules, but it's starting to annoy me how if I was just running Redhat, I could be running KDE 3 already, whilst it'll probably take another 4 months or so for KDE 3 to make it into sid. Maybe this is one of the downfalls of Debian, because of the strict packaging guidlines, authors aren't willing to release .debs because of the ammount of time it takes to package them.

    I suppose I could just grab and compile it myself.
    • 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.

      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* cough*

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

    by Dr. Spork ( 142693 ) on Wednesday April 03, 2002 @01: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.

  • Edge Flipping? (Score:3)

    by poopsie ( 320177 ) on Wednesday April 03, 2002 @03:49PM (#3278841)
    Does KDE by any chance now support edge flipping (IE. Move your pointer to the edge of the screen and jump to the next screen)?

    This is the single reason that I can't use KDE for more than about five minutes before becoming totally exasperated. I use this feature CONSTANTLY in Gnome. What's the point of having four desktops if I can't move to 'em quickly? (I know I could probably do this with keyboard shortcuts, but it's not the way I work).

    KDE 1.X had this feature, and when 2.X came out I switched to Gnome. Seriously, the coolness of this feature is what got me hooked on Linux desktops in the first place - it is, to me, the most useful feature of any desktop environment/window manager.

    Anyone wanna code this into KDE for me?

  • Release Party! (Score:3, Interesting)

    by ThatComputerGuy ( 123712 ) <amrit AT transamrit DOT net> on Wednesday April 03, 2002 @04:59PM (#3279378) Homepage
    Head over to #kde on irc.openprojects.net for the release party :)

Slashdot Top Deals

He has not acquired a fortune; the fortune has acquired him. -- Bion

Close