Slashdot is powered by your submissions, so send in your scoop


Forgot your password?

KDE 3.0 Beta 2 is out 341

Subject says all - the next beta of KDE 3.0 is out, after a short delay. You can find the downloads at this announcement. Click below to read more details about this version.
One of the most important things that the Konqueror teams wants from people are test cases of your regulary visited pages, where Konqueror either fails to render or render things incorrectly, and submit it using KDE's Bug Tracking system. URL's will not be helpful as it takes lots of time to strip a page from all the HTML code in order to find the actual problematic part of the web page.

Just to save the search for some people: Mandrake, SuSE, Slackware and Tru-64 binary packages are available now. Others will be available soon. Source code is of course available also.

This discussion has been archived. No new comments can be posted.

KDE 3.0 Beta 2 is out

Comments Filter:
  • KDE - Beta is stable (Score:5, Interesting)

    by lemonhed ( 412041 ) on Wednesday February 13, 2002 @03:47PM (#3002129) Journal
    Ive tried the KDE Beta 2. And I must say... Its a very very very stable pre-release. Hats off to the KDE developres.

    The only problem is that some of the older KDE apps wont run correctly with the new KDE and they must be upgraded to work with the new QT packages.

    Everyone should D/L it and check it out.

    • Just make sure you keep KDE2 libraries around and your old KDE2 apps will still work. They just won't directly interoperate with KDE3 apps. For instance, you can't embed old modules/plugins into new applications.

      • Good point.

        But that actually raises another concern. Why didnt they make KDE3 backward compatible with KDE2? KDE2 is compatible with KDE.

        I have alot of KDE2 applications running and I know it will be difficult to maintain both sets and remember which works with which set of libraries. Its sort of like the whoel GLIB problem (e.g., 2.2)

        • KDE1 was not even close to binary compatible with KDE2. Anyways, KDE3 broken binary compatibility because Qt broke it with Qt3 so it was a good opportunity. The transition shouldn't take too long before you have all KDE 3.0 applications though. Don't worry, it won't be that painful.

          Part of the job of the beta is to get people porting their apps to KDE3 too.
        • Why didnt they make KDE3 backward compatible with KDE2?

          As I recall from earlier stories (PLEASE correct me if I'm wrong here, it's been a while) the KDE folks were looking at binary incompatibility no matter what due to a new gcc that was due out. I don't pretend to understand the mechanics, but apparently everything was going to require a recompile anyway.

          Probably mentioned in some mailing list archive someplace. They figgered that if ever there was a good time to break compatibility, now was that time. The long term game plan is to have the underlying architecture of KDE 3.0 support new versions for the next 3 years or so.

          I've seen it mentioned a number of times exactly how aware the KDE crew is to this breakage. Heck, there's still KDE 1.2 apps that haven't been bumped up yet! Hopefully, this will be the last of these kinds of upgrades for a while... assuming the game plan works out that is. 3 years is a darn long time for KDE.
  • by Anonymous Coward on Wednesday February 13, 2002 @03:47PM (#3002130)
    I want proof that Konqueror cannot be removed from KDE without causing severe damage to the OS!
    • by reflexreaction ( 526215 ) on Wednesday February 13, 2002 @04:00PM (#3002236) Homepage
      And I want to be charged $20 less for KDE when and if Konquerer can be removed.
    • by IceFox ( 18179 ) on Wednesday February 13, 2002 @04:01PM (#3002246) Homepage
      Actually what I would like is clear simply instructions on how to have the kde call openBrowser(url) open in something other then Konq. This is one of the major reasons why Kinkatta ( isn't in KDE. Kinkatta gives the user the option to select what browser to use because I can't answer the e-mails on how to have openBrowser(url) use Galian or Mozzila, Opera, etc. I have many non-kde users that use Kinkatta, but giving users options is "not the kde way" acording to *someone* in kde.
      • by 7-Vodka ( 195504 ) on Wednesday February 13, 2002 @04:53PM (#3002688) Journal

        Actually what I would like is clear simply instructions on how to have the kde call openBrowser(url) open in something other then Konq.

        Ok, your wish is granted.

        1. Click on the kcontrol icon.
        2. Click on file browsing tab.
        3. Click on the file asociations tab.
        4. Enter .html in the text box.
        5. Change the order of the browsers.

        Each user to his own browser. Just how I like it. Very easy to change.
        Simple enough? I think so.
        What peope don't seem to realize is that kde is more customizable than any other DE/WM. It's also scriptable. Type dcop in a term.

      • This is one of the major reasons why Kinkatta ( isn't in KDE. Kinkatta gives the user the option to select what browser to use because I can't answer the e-mails on how to have openBrowser(url) use Galian or Mozzila, Opera, etc.

        No... or at least it hasn't come across the list. There *was* some talk about redesigning it to use the setting from the control center by default. What precisely are you talking about?


      • Noone said that you shouldn't give users a choice. It was argued that the KDE-way to open an browser is openBrowser() and that applications shipped as part of KDE should use the KDE API.

        If you feel that functionality is missing from openBrowser(), you should still use it and fix openBrowser(). By not using it you give out a sign of unwillingness to adopt to KDE standards. You'd rather ignore the standards than fix them.

        If you want your application to ship as part of KDE you're no longer a third party developer, you'd be a KDE developer and you'll have to think of a picture bigger than just your application.

        Even more important however: I do not think KDE should replace shipped applications (there is a functional AIM client already) every time an alternative comes along, even if the alternative is better. That'd be inconsistent.

  • by Anonymous Coward on Wednesday February 13, 2002 @03:50PM (#3002141)
    It turns out that a large silent number of
    people are running KDE (and GNOME) desktops
    under not *linux, but under FreeBSD. It would
    be nice if more FreeBSD binary packages were
    • Screw the binaries. All I want is a /usr/ports entry.

      I get a nice, warm, fuzzy feeling knowing that everything on my computer was built from source by my computer.

      You have to do something with all those spare cycles and I could really care less about finding alien signals from noise, cracking the latest DES, or factoring the largest mersine (sic) primes.

      Viva la source!!!!

    • The KDE FreeBSD [] project is a fairly small, but interesting, site. I still build from ports, though.
  • Slackware support! (Score:3, Interesting)

    by OpCode42 ( 253084 ) on Wednesday February 13, 2002 @03:54PM (#3002185) Homepage
    Hurrah, they've provided slakpacks!

    Ive been using it today, its very nice. I wasnt a fan of KDE2, and at first glance this is just kde2 with bells and whistles. However, there are subtle changes and integrations that make it much nicer to work with on a daily basis.

    Konquerer is a little buggy though (crashes every time i press the Back button)

    Cant wait for the final release!
  • by Anonymous Coward on Wednesday February 13, 2002 @03:55PM (#3002193)
    "You get what you pay for after all."

    -Rob Malda []

    How useful can KDE be?
  • by 4of12 ( 97621 ) on Wednesday February 13, 2002 @03:56PM (#3002205) Homepage Journal

    I was pretty happy with KDE 1 and remain happy with KDE 2.0

    I'm sure to get Troll -1'd into oblivion for this, but

    Why is KDE 3.0 so good that it's worth getting excited about from the standpoint of the end user?
    • Oh wait, that's the Olympics. Still true about KDE 3, though.
    • Nothing really that earth shattering, but it does link against QT3 rather than QT2, hence the major version number bump.

    • by PeterClark ( 324270 ) on Wednesday February 13, 2002 @04:12PM (#3002327) Journal
      Well, you've already been moderated as flamebait, but I don't think that's the case, so I'll respond.

      First of all, the major reason for KDE3 is QT3. QT3 has several advantages over QT2 for developers, and the KDE project want to use these to their advantage. As an end user, you probably won't be aware immediately of the changes, but developers will, which means that better programs will be coming your way.

      Also, look at 3.0-features.html [] to get an idea of what's being added in KDE3. Then you can decide for yourself whether KDE3 is worth it. :)


    • by stilborne ( 85590 ) on Wednesday February 13, 2002 @05:14PM (#3002832) Homepage
      besides Qt3 (which others have pointed out) there are a number of new features and general improvements. for example the javascript and html engines are both much better/faster than what was in kde2. directory listing is much faster, the file dialog has been spiffed up a bit more, there is support for file information plugins that appear on mouse over (not to mention animated icons), improved imap and gpg support in kmail, dcop has been improved tremendously from the viewpoint of scripting, aRts is much improved with the new GSL engine (cooperation with GNOME!), some new eye-candy like animated window decorations and new thumbnail types, tons of bug fixes and speed ups etc.. etc.. etc...

      this is very much an evolutionary release as opposed to a revolutionary one (as KDE2.0 was), but the changes are quite noticeable. they make the general kde experience smoother and more useful IMO. one nice thing about it being evolutionary is that it is immediately stable and familiar ...

    • I see theres no programmers here

      Better programs is why you should use 3.0
  • by PeterClark ( 324270 ) on Wednesday February 13, 2002 @03:59PM (#3002230) Journal
    I have been a KDE fan ever since last summer, when I finally got the hardware to support it. :) It's been my primary desktop environment ever since, although (probably due to something getting borked upstream) I'm having to use Fluxbox until the memory and performance issues in the current Debian Sid KDE go away.

    Anywho, the feature that I've been most looking forward to is tabbed browsing in Konqueror, due to appear in KDE 3.1. Galeon is the one constantly used app that isn't a part of KDE, and I use it because a.) it has tabbed support and b.) a smart bookmarks toolbar. Plus, it's a web browser. Nothing more, nothing less. Konqueror has various view settings (such as "file manager", "web browser", and whatnot, but in my experience, the different view settings don't always play nice. But since tabs are at the top of my wishlist, I will definitely reconsider Konqueror in the near future.

    So, what are all you other KDE fans looking forward to?


    • So, what are all you other KDE fans looking forward to?

      Waiting to see how short of a time span it is for my current download to timeout because of being posted on the /. front page. :-)
    • by brunes69 ( 86786 ) <> on Wednesday February 13, 2002 @04:36PM (#3002548) Homepage

      I agree with the tabbed browsing, I can't wait for t to appear in 3.1. But the smart bookmarks toolbar; I find that vastly inferior to Konqueror's web shortcuts feature, mainly because it is so much simpler to use. Why do I need a bulky toolbar cluttering up my screen when I can just type "php:fopen" to search the php manual, or "rf:gaim" to search freshmeat? It's very cool. if you've never tried this feature, go into your konqueror settings under "Enhanced Browsing". It's very easy to add your own sites.

      • or "rf:gaim" to search freshmeat?

        I just thought I'd make a correction for people who are not familiar with this (totally freakin' awesome) feature.

        rf:gaim - The "rf" is for searching []
        fm:gaim - The "fm" is for searching FreshMeat []

        You can see many more things available to you by going to:

        Control Center --> Web Browsing --> Enhanced Browsing

        Very cool stuff...
    • So, what are all you other KDE fans looking forward to?

      The improved javascript support. It's the one place where I still occasionally run into problems using Konqueror, but so far the KDE3 CVS snapshots have been looking much improved over KDE2 in this department...

  • UI Design (Score:5, Interesting)

    by XBL ( 305578 ) on Wednesday February 13, 2002 @04:04PM (#3002269)
    This post is a complaint, but I want to see what others think.

    My opinion of the KDE overall user experience is that it's rather "blah". Now, I will admit that going from KDE 1 to KDE 2 was a huge step up, I just think that it needs to become cleaner, lighter, and less cluttered.

    For example, the default setting for the Kicker is 2 buttons high. This is just too tall. The new Konquerer is really too cluttered, with the big sidebar, etc.

    Going to the extreme, I wish KDE would become more like BlackBox with its basic design. BlackBox actually makes 1024x768 seem like a higher resolution than that. KDE makes 1024x768 seem like 800x600 or maybe even less.

    So anyway, those are my thoughts.
    • Re:UI Design (Score:5, Informative)

      by PeterClark ( 324270 ) on Wednesday February 13, 2002 @04:21PM (#3002403) Journal
      A vague bell is going off in the back of my head, warning, "Troll! Troll!" but I'll ignore it and give you the benefit of the doubt.

      If you think KDE is rather "blah", check out [] and look over the icons and themes. Ignore the wallpapers, though, must of them are not worth your time. KDE-look has taken the place of [], so if you want to add spice, go there.

      Secondly, if you're able to use Blackbox, you are able to spend the two minutes it takes to customize KDE to your liking. If you don't like the default height of Kicker, right click on it and you can change it immediately. Plus, if you really want that Blackbox look and feel, you have the choice of using Blackbox themes in KDE (I'm not sure if this is included by default with KDE; if not, go to, or use BlackBox as the window manager instead of kwin. Google is your friend if you don't know how to do this.


      • by neema ( 170845 )
        "A vague bell is going off in the back of my head, warning, "Troll! Troll!" but I'll ignore it and give you the benefit of the doubt."

        The Spider-Sense for geeks.
      • Re:UI Design (Score:3, Informative)

        by JabberWokky ( 19442 )
        Secondly, if you're able to use Blackbox, you are able to spend the two minutes it takes to customize KDE to your liking.

        Or you can use the kbox window decoration, which even loads BlackBox themes.

        Or, you can do like I used to and use use BlackBox or FluxBox instead of kwin. KDE runs just fine under both, with FluxBox even handling docked apps perfectly (there's a patch for BlackBox to do that as well).


    • Absolutely. Compared to windows or Mac, KDE and even GNOME to a lesser extent are way cluttered. It turns off power users, and confuses new users.

      Course, take my opinon with a grain of salt, since my desktop isn't exactly normal: []

      I still think the default mode of both of these environments should be more lean. Power users can always add on what they want. All Windows has is a 10px high "start bar", consisting only of 1 button, and a clock. And most users love it. Keep in mind it's been through a lot of usability testing... feed off that, since we can't afford our own.
    • Re:UI Design (Score:4, Insightful)

      by brunes69 ( 86786 ) <> on Wednesday February 13, 2002 @04:30PM (#3002502) Homepage

      So turn the sidebar off, and make the kicker 1 button high. Big whoop, takes all of 10 seconds in kcontrol.

      These things are set this way for a reason. The sidebar makes browsing a folder tree MUCH easier for people used to windows explorer, and I , a non-windows user, also find it a very powerful tool, where I can access my bookmarks and FTP sites in a cinch. As for the kicker, I prefer it two buttons high, not for the sake of the buttons so much as the clock and the launcher icons. I think having them large gives it a more polished look. Not to mention the Run Command kApplet won't fit in a kicker under two buttons. If you feel like the desktop is cramped, why not make your kicker transparent using TeaX [], I think this is very slick.

      Anyway, my point is just because you like it one way doesn't mean everyone else does. That's why kde and gnome are so customizeable. So customize them already!

    • Re:UI Design (Score:2, Insightful)

      by Anonymous Coward
      There are two issues with KDE related to UI shortcomings.

      Highly-configurable UIs like Gnome and KDE tend to show off by turning all the stupid options ON by default. The fact that they are highly configurable allows users to fix this on their own, but the first impressions are still "flashy, cluttered, slow" instead of something more utilitarian and, well, usable. This hurts in reviews, gaining non-techie converts, etc.

      The other issue is that Gnome and KDE both borrow BAD UI ideas from Windows because people are used to sucky UIs, rather than aiming a bit higher. Again, you can configure your way into a good UI, but, by default, you're looking at some bad UI design. Both KDE and Gnome have menus that cascade down from a menubar, EXCEPT for the desktop itself, where the menus launch out of the bottom of the screen! What planet does this make sense on? If you want menus coming out of the bottom of the screen, at least make them do that for your applications too for consistency! And then there's the "close window" button up in the upper-right corner, with all the other buttons that control window behavior. Why not put the potentially destructive button in one of the other corners AWAY from the benign ones? That's the way everybody handled it until Win95 came out and made it so much easier to close windows accidentally.

      Yes, these are silly rants. All of these errors can be fixed. The question is: why do WE have to fix them?

  • by immanis ( 557955 ) <> on Wednesday February 13, 2002 @04:05PM (#3002273) Homepage Journal

    enlist volunteers to help find elusive and platform-specific bugs, and to provide constructive feedback through the KDE bugs database prior to the developer meeting later this month

    At first glance, I missed why this even needed inclusion in the announcement. Most users are more than willing to provide feedback when Konqueror or KDE doesn't work right. Then I re-read the word "constructive."

    So, for further edification, constructive feedback doesn't typically contain the words "suckers" "bastards" "morons" or "jerks." That kills 99% of the feedback they would be getting.

  • by rseuhs ( 322520 ) on Wednesday February 13, 2002 @04:08PM (#3002299)
    Is that it's quite the same as KDE2 and NOT a major rewrite.

    I know a lot of people who were scared away from KDE2.0's unstability and bugs.

    It's a marketing-thing. People tend to only try out .0 releases, so a 3.0 release that is in reality a 2.3 is the best thing that can happen to KDE :-)

    The second-best feature of KDE 3.0 is the configuration of animated pics, BTW ;-)

    • It's a marketing-thing.

      No, it's a "we may change the API and ABI in major releases" thing.

      One of the main points of KDE 3.0 is the switch to Qt 3.0, which brings many advantages, but also breaks the existing ABI (and to a small extent, API).
  • Redhat? (Score:2, Interesting)

    by L-Wave ( 515413 )
    Sad sad, they never had redhat packages, even beta 1 *still* doesn't have them... oh well, (the reason i am not installing the tarballs is because its beta, i dont want to clutter my FS if it doesnt work right. anyways, thats my 2 cents =)
  • by 2Bits ( 167227 ) on Wednesday February 13, 2002 @04:11PM (#3002317)
    This applies to KDE as well as Gnome.

    These two environments tend to come with huge packages (e.g. gnome-applets, kdenetwork, kdemultimedia, kdegraphics, koffice, ...).

    Sometimes, you just need one or two in the packages, and you are forced to install the whole jumbo packages. Why? Why can't we pick and choose?

    E.g. I use Kword sometimes for simple word processing, but I never use the spreadsheet and the presentation app. Same for kdenetwork. I use KMail and KNode, but I don't need korn,ktalkd,ksirc,.... And kdemultimedia, I don't do MIDI stuff, and I don't want to waste 10MB for timidity++ and other junks.

    Oh yeah, same for Gnome. Why do I need to install the whole gnome-applet package if I only need one applet? Same for other jumbo packages.

    I'm on RPM-based distro. How about apt-get-based?
    I don't know the internal details of the code, but isn't there a way to separate them out?

    • Blame it on the packagers! :-)

      I don't know if any other distribution does this, but Conectiva ( has per-application rpms in most cases. So, if you want just the CD player in kdemultimedia, you has to install only kdemultimedia-kscd.

      It's really nice, and I hope more dists would do this. SuSE has something similiar, but not for the base packages (e.g., kdemultimedia comes in a big package, but "3rd-party" applications not included in the distribution have their own package and can be installed individually.)
    • To my knowledge, Debian KDE packages are separated. To install KWord, the dependency koffice-libs (to my recollection) is installed with it. I could be wrong (I'm not at my comp right now to check how apt-get handles everything), but when you do apt-get install koffice it installs all of the individual components quite nicely. Check out this page [] to see the list of KDE application packages. I also checked the library page and confirmed koffice-libs.

      Granted, you get a small amount of bloat if you just want KWord (compared to a more standalone wordprocessor), but it beats the RPM distributions easily. The quality and ease with which KDE is handled in Debian was one of the major deciding factors in me switching to Debian from Red Hat.

    • These two environments tend to come with huge packages (e.g. gnome-applets, kdenetwork, kdemultimedia, kdegraphics, koffice, ...).

      Not necessarily.

      Take a look at Raw Hide [] to see what the KDE packages are likely to look like in the next Red Hat Linux release.

      I've decided to split up most of them.
    • I'm on RPM-based distro. How about apt-get-based?

      Apt-get isn't a packaging system. I presume you probably mean Debian. My office has been using apt-get to maintain our Red Hat boxes for a few months now, and it works quite well. Regardless, the release of KDE 3 marks a good time for the KDE webmasters to save users a bit of time when fetching the latest release my making the packages for Red Hat, SuSE, etc into an APT repository. Its quite easy (we're already doing the same with KDE 2.2.2 at work) and I might volunteer myself if I have the time.

  • Tips for SuSE users (Score:5, Informative)

    by Geek Boy ( 15178 ) on Wednesday February 13, 2002 @04:17PM (#3002365)
    The suse packages have a few minor installation conflicts. Make sure you have the prereqs installed and just --force and it will work. They use a separate .kde dir (.kde3-testing) so that you don't lose your old kde2 environment. However they don't migrate up your old settings. You can do this by copying the .kde2/share/config and .kde2/share/apps directories into .kde3-testing/share before your launch kde after you update. kconf_update will migrate your settings forward.

    I was unable to get the lisa package or kdevelop to install due to dependency problems, and I didn't try. Make sure you install the mesaglut-devel package. It's needed.

    The packages install into /opt/kde3 and you have to log in with the kde3 session entry in kdm if you use that.

    Known bugs so far:

    - Browser identification doesn't always work correctly.

    - Greek keyboard setting is giving me Russian characters instead for some reason. (this may or may not be a bug)

    • by psocccer ( 105399 ) on Wednesday February 13, 2002 @04:53PM (#3002681) Homepage
      Make sure you install the mesaglut-devel package. It's needed.
      Good to see they've finally included one of the most-needed functions ever for a geek, the megaslut package. I know I've been asking for it for a long time, I can't wait to see what kind of development stuff is in the devel- package...

      looks again

      Crap... Oh, mesaglut... well, I guess it's back to autopr0n []...
  • by WebWiz ( 244386 )
    Just curious how much human factors goes into the development of open source desktop packages? Are there members of the KDE or QT or Gnome teams whose sole job/interest is to further the usability of the interfaces? Or are the developers just happening to "place this here" or "place this there? Are the beta testers assuming the role of Usability testing?

    • Well, for Gnome, there was a Sun sponsored usability study, IIRC.

      However, such a study doesn't improve usability on it's own, it just states that it has to be improved. You can tell a crappy UI coder that he is just that over and over, he won't get better just because of this.

      KDE also has Usability page [], but there seem to be more active KDE subprojects...

      (Note that I don't want to imply that Gnome has more crappy UI coders than KDE. Both have their share, and both have great ones.)

    • I can't speak for KDE (though I believe they have a Usability team), but look here [] for the GNOME Usability Project (aka GUP). I know that Sun has done user testing on GNOME.
  • KDE 3 (Score:4, Interesting)

    by Satai ( 111172 ) on Wednesday February 13, 2002 @04:32PM (#3002520)
    I'm really looking forward to KDE 3.

    No, not because of the move to QT3.

    No, not because of the improvements in Konq, KFM, or any of those - not even the multi-key shortcuts.

    I just want to be able to use KMail for my Maildir mailboxes. I know there are hacks, workarounds, all that - but I don't want those. I just want to be able to plug in and go. Right now I use Mutt, but sometime in the future I'd like to be able to do some of the things it doesn't - like inline HTML viewing. KMail won't be for regular use, I guarantee it, but it will certainly be a nice complement to mutt.

    A very close second is the switching of desktops when dragging a window - that's on the "KDE 3 List" [] and it's definitely something I miss from E. I don't know if it's going to be in 3, but I also really miss the ability to "walk off the edges" of the desktop and switch to a different virtual desktop. I've got the keyboard shortcuts set up, but it just isn't the same.
  • KDE 3.0 (Score:3, Interesting)

    by saintlupus ( 227599 ) on Wednesday February 13, 2002 @04:50PM (#3002662) Homepage
    I haven't had any luck getting the 2.x family of KDE to build on an OpenBSD box, whether the hardware was x86 or PPC. Which sucks, because I really want to use Konq, and Mozilla won't build at all under Open.


    Anyhow, has anyone managed to build one of the 3.0 betas under OpenBSD?

  • No tabbed browsing? (Score:2, Interesting)

    by crivens ( 112213 )
    Shame there's no tabbed browsing in Konqueror. Also I was quite surprised at the number of changes listed for console! That made me chuckle; it's like saying this is the program that most people use so it's the most important. :P

    As a side note, how much obsolete and legacy code is in KDE right now? I mean, Windows contains lots of legacy code for DOS support. Any thoughts?
  • Screenshot (Score:5, Informative)

    by Isle ( 95215 ) on Wednesday February 13, 2002 @05:39PM (#3003036) Homepage
    Since noone else has.
    Here is the secret link to the new []
    KDE 3.0 Beta2 screenshots
    • by Rob Kaper ( 5960 )
      I originally wanted to update them a bit before linking and announcing them. The link is no longer secret, it is now linked from the main screenshots page.

      Damn, it's harder to keep a secret in KDE CVS / Dot / Slashdot than in a high school full of giggling Olsen twins.

  • I'm downloading and compiling the beta as I type this...

    I've been playing with CVS snapshots off and on recently, and I must say they're looking promising. The appearance is similar to 2.2, but with a bit more 'beautification' and eye-candy effects available, and certainly, Javascript support is MUCH improved (though I still haven't been able to view things on Atomfilms for some time in Konqueror...). The ONE complaint I have that keeps driving me back to 2.2 is the apparently broken focus handling in KDE3...

    I haven't been able to tab between fields in a form, for example, though this isn't a BIG problem. The BIG problem is that while entering text in textareas (such as this form right here on slashdot), hitting 'enter' to drop to a new line will something. Not actually submit the form, but the page seems to re(?)load. The back button brings the form back up, sans all the text that was entered in these cases. I haven't been able to figure out EXACTLY what it's doing yet.

    This is the only problem I've run into, but I spend enough time on web forums that it kills me...anybody already tried the beta out know whether or not this has been fixed yet? I DO recall reading that the focus problem, in general, was due to be fixed before the final release...

  • Huh? Well, there is a list of planned features [] already. Mostly stuff that didn't make KDE 3.0 or wasn't done yet because 3.0 is the only opportunity to make binary incompatible changes for a long while again. So the development focus for 3.0 has very much been the underlying framework, while 3.1 will add some more features and eye-candy, probably.

    Please note that some of the planned items still might not make it and that it is very likely that several items are not yet planned but will pop up in time for the 3.1 freeze which is several months away.

The trouble with the rat-race is that even if you win, you're still a rat. -- Lily Tomlin