Become a fan of Slashdot on Facebook

 


Forgot your password?
Close
typodupeerror
×
KDE GUI

KDE 3.0 beta 1 is out 292

Posted by HeUnique from the let-the-tests-begin dept.
From the development team who tries to break every development speed record (last month they released KDE 2.2.2) comes KDE 3.0 beta 1, with lots of new features, new QT (3.0.1). It is beta 1 so expect crashes. You can find release notes and download locations over . A full feature list of whats planned to be on KDE 3.0 is also available (hmm, quite a big list) and some screenshots are available here. Please read the README files for your favorite distribution before installing the files as those packages are not replacing the KDE 2.2.X binaries (if you have it installed).
This discussion has been archived. No new comments can be posted.

KDE 3.0 beta 1 is out More

KDE 3.0 beta 1 is out

Comments Filter:

  • Feature List URL (Score:3, Informative)

    by ankit ( 70020 ) on Thursday December 20, 2001 @05:16AM (#2731107) Homepage Journal
    The feature list URL is incorrect. The right one is this [kde.org]

  • Finally, USB sync...sorta (Score:4, Informative)

    by ShmuelP ( 5675 ) on Thursday December 20, 2001 @05:17AM (#2731111)
    I believe that this is the first KDE "release" where KPilotDaemon supports USB-based palm devices (such as Visors). Anyone know if there are meaningful conduits using the archeitecture, though?

    • Re:Finally, USB sync...sorta (Score:1, Informative)

      by Anonymous Coward
      The "old" conduits are still being ported to the new architecture, so the kpilot from the beta can be used to backup or restore your pilot, but that's all. I suppose we'll get lots of bug reports from people saying "i upgraded to 3.0beta1 and kpilot don't work no more." Well duh. Oh, don't count on devfs to work either.

  • ScreenShot MIRROR. (Score:4, Troll)

    by minus23 ( 250338 ) on Thursday December 20, 2001 @05:19AM (#2731118)
    I've mirror'd the screenshot page here. Included are also the full size pictures of the screenshots. Enjoy. Mirror Link [opnotic.com]
    • No need to worry. (seriously) Sigh.. why is it *everytime* I mirror something an AC comes by and says it's the goatse link? -- At least think of something original.. seriously.. it's been going on for years.
      • Cause that's what trolls do - and don't worry, the moderators are only rarely fooled, and if they are the error is soon corrected.

        I notice that the trolls have already defeated the Slashdot [link.url] thingies though, take a look at the AC replying to your post with the google.com kde.gif link. It fools both Slashdot and IE, if you mouseover it says it's a link to google. Amazing. To discover the trick, you have to use the "Copy Shortcut" command and paste it into your URL bar. Think what creative energies like that could do, if they were turned to the light! Think of the programs that could be written with talents like that! And yet whatever sad person thought that up sits here at Slashdot finding ways of fooling a few people into seeing the wrong website, until the post is modded into oblivion 2 minutes later. It truly is sad...

  • Slashdot caches URLs? (Score:3, Informative)

    by athmanb ( 100367 ) on Thursday December 20, 2001 @05:20AM (#2731120)
    That's what I first hoped. That Slashdot had finally started to mirror URLs they link to, to protect other sites from the rampant bandwidth rape which comes with a mention on /.

    Alas, it was only a typo...

  • From the feature list... (Score:3, Redundant)

    by tunah ( 530328 ) <sam&krayup,com> on Thursday December 20, 2001 @05:24AM (#2731133) Homepage
    ...
    KWin
    magnetic borders for window resizing, gallium
    ...

    At last! I'm so sick of gluing my windows in place, and the glue makes the screen blurry.

    Hold on, don't magnets make the screen dark and erase the hard drive?

  • I have been very excited about KDE since the latest version (2x) series came out. Can anyone explain what the 3.0 series is going to offer? Some of the technical details of the lists will go over my head.
    • KDE 3.0 will have a number of additional features regaarding access to databases, multimedia, support for more mime types, stability enhancements and the like.

      As with any open source project, KDE will go in the direction that interests those who contribute to the system. Feel free to get KDE 3.0 and submit bug reports though - each helps KDE 3.0 be better all the time.
    • In addition to the features being added, they are moving it to use a new version of the Qt toolkit (Qt 3) - once that is done, they'll be able to add loads more stuff.

  • Bear in mind... (Score:5, Informative)

    by [vmlinuz] ( 158785 ) on Thursday December 20, 2001 @05:52AM (#2731188) Homepage
    A few people have been complaining here that KDE 3.0 looks the same as KDE 2.x. I just wanted to clear a few things up:

    - First of all, KDE 3.0 is largely an architectural upgrade - we have moved to the new Qt 3.x series, and this needs to be reflected in KDE 3.x. The Qt 3.x series has a lot of bug fixes and additional features such as database connectivity, better handling of data structures and the like - this increased stability is passed on natively to KDE 3.0.

    - In terms of interface updates, KDE 3.0 will see some updates but bear in mind that this update was aimed at primarily porting the codebase to Qt 3.x. Any additional interface updates will be added as the need arises - we always like your suggestions and bug reports are always welcome.

    - KDE 3.0 is largely about increased functionality - examples include better JavaScript, a more integrated Konqueror, new modules such as the KDE Educational Module, the font installer, kernel compiler etc. These things are really likely to appear in 3.1 and further releases.

    - For those of you who are gonna bitch and moan about KDE, GNOME, XFree86, Kernel, Mesa etc...why not just help to correct the things you don't like. You don't need to be a coder to help ny project - *everyone* can help an open source project.

    Please be patient folks and keep those bug reports coming in - we value your help.

    Jono Bacon

    • Re:Bear in mind... (Score:3, Insightful)

      by dunstan ( 97493 )
      I first used KDE in the pre version 1 betas, and the look and feel hasn't changed much since then. This is A Good Thing, because it means they got it right in the first place. When I first tried out KDE the current state of the art in unix desktops was CDE. When I first saw KDE my view (and that of my then colleagues) was "OK, that's the X desktop sorted, now let's move on". Since then most of the change has been under the bonnet (hood), enabling applications running under KDE to play nicely together, together with new applications which use this functionality (Konqueror, Koffice).

      It is a true tribute to KDE that a major version change doesn't look or feel much different.

      Dunstan

      • Re:Bear in mind... (Score:2, Insightful)

        by rseuhs ( 322520 )
        It is a true tribute to KDE that a major version change doesn't look or feel much different.

        I second that. And because the codebase does not change, it should be a lot more stable than KDE2.0.

        I know a lot of people who have tried KDE2.0 and left it because it was quite buggy.

        KDE3.0 will (hopefully) be stable from version.0 on, so the large audience trying the .0 version won't be scared away from it.

        I think KDE3 will make inroads in the desktop-market.

  • This is not a flame! (Score:4, Interesting)

    by powerlinekid ( 442532 ) on Thursday December 20, 2001 @05:54AM (#2731191)
    I'll come straight and say it... it looks like KDE is pulling some considerable distance between GNOME and itself. Look I have a lot of respect for the GNOME people... anyone who donates their time to such a massive complex system such as a user enviroment deserves a round of golf claps. The fact is though is that I used to be a GNOME user. And then one day I accidently* logged into KDE 2.2.X (whatever is with RedHat 7.2) and was blown away by the speed and grace. If linux ends up on the desktop in it's present form (X sucks but thats a different story), then most likely it'll be KDE that everyone thinks is linux. They seem to have the perfect model right now... release quickly and update often. Quite impressive really, considering how much shit goes into a project of that magnitude.

    * - About the accident... usually I install both enviroments on my machine so I can use apps from both (I always liked KDE's media player and Kmail).
    Basically I just always ignored KDE and then one day was checking out what windows managers was available and forgot that I had highlighted KDE and logged in. The rest is history... haven't gone back since.
    • I suppose it's a matter of taste. I've tried to use KDE lots of times, but I find it ugly and unintuitive. Gnome can be slow, but I think Gnome is a lot better than KDE on a high-end machine. Nautilus is great if your box is fast enough to handle it. KDE always feels like a Windows wannabe to me (not a flame, just an opinion.) And maybe I'm just a complete imbecile when it comes to updating things, but I keep breaking apps in KDE.

      Besides, I've fallen in love with Galeon. Much better than Explorer or Konqueror (does konqueror have tabbed browsing yet? haven't checked it out in a little while.) I'm currently running 0.11.3, and it's still more stable than Explorer. And on the two occasions it has crashed, it's restored my browsing state. Poetry.
    • I also like KDE, but when I first installed it the memory usage was horrendous. I have 512Megs of memory and when KDE would load I would be left with about 50 Megs! (This is with almost everything else shut down, just X/KDE running) Gnome leaves me with alot more Memory, which is good because I hate having to leave X to compile something I just downloaded. Under KDE it will take about 3x as long to compile as under Gnome!
      • That's funny, I only have 256 MB of RAM, so why doesn't my HD swap when I use KDE?


        [jharris@servo jharris]$ free

        total used free

        Mem: 255516 199036 56480

        Swap: 265032 0 265032

      • Re:Memory usage (Score:3, Informative)

        by Seli ( 51600 )
        I also like KDE, but when I first installed it the memory usage was horrendous. I have 512Megs of memory and when KDE would load I would be left with about 50 Megs! (This is with almost everything else shut down, just X/KDE running) Gnome leaves me with alot more Memory, ...

        So you're claiming your KDE needs 450MiB memory? Wow, I wonder how I managed to run it on a machine with just 96MiB RAM and 128MiB swap (and a lot of free memory was still available).

        Seriously, understanding 'top' or 'ps' output is not that simple as it seems. The formula for computing used memory from numbers given by 'top' is : Used_memory = mem used + swap used - cached - buff . Now go again to measure your memory usage, and if your number is still higher than 100MiB for plain KDE, there's something wrong with your install. For me, the number for a booted computer with plain KDE started is less than 50MiB (I'm not sure how much exactly and I'm not going to close all apps and logout just to find out).

        Also, important portion of KDE's memory usage comes from gcc/glibc/binutils inefficient handling of C++ libraries ( see http://dforce.sh.cvut.cz/~seli/en/linking2 [sh.cvut.cz] ). This is being worked on.

        It would be nice if this got moderated up. I'm getting tired of repeating it.

  • Add GUI for configuring "animated gifs", Waldo Bastian

    I've been waiting for that for a LONG time...

    Unfortunately it's still in the "TODO" group, but I think this feature is worth waiting for.

  • Super fast UK mirror (Score:2, Informative)

    by adders ( 191568 )
    If your in the UK and need a fast download of KDE, or just about any other download, try http://www.mirror.ac.uk/ or ftp://ftp.mirror.ac.uk/ http://www.mirror.ac.uk/sites/ftp.kde.org/pub/kde/ unstable/kde-3.0-beta1/ [mirror.ac.uk] ftp://ftp.mirror.ac.uk/sites/ftp.kde.org/pub/kde/u nstable/kde-3.0-beta1/ [mirror.ac.uk]

  • KHTML vs. Gecko (Score:4, Interesting)

    by moZer ( 83729 ) on Thursday December 20, 2001 @06:41AM (#2731254) Homepage
    One thing that I really would like to see is a better integration of Gecko in Konqueror. I know it's already possible to switch rendering engine, but it's highly unstable in my experience.

    Now here's an example of an area in which many of the largest open source projects (Mozilla, GNOME, KDE) could collaborate, benefit from each other's work and find a common standard - the HTML rendering engine. Imagine the Konqueror, Galeon, Mozilla and Nautilus teams putting their efforts behind Gecko development...it would be one important step towards a more unified Linux desktop. Unified as in common standards and shared components, not unified as in lack of choice.

  • Screenshots (Score:1, Insightful)

    by tacocat ( 527354 )

    OK, I checked out the screen shots. Looks just like my current KDE 2.2.1.

    KDE is a good product, don't get me wrong. But why does it have to look just like MSFT's products?

    I actually would like to work more on finding desktops/WM's that do not look like MSFT. It's interesting to see what other ideas are out there and to see who's got a fresh new paradigm on this desktop. After all, it's not really a desktop anymore.

    • Re:Screenshots (Score:5, Insightful)

      by Seli ( 51600 ) on Thursday December 20, 2001 @07:05AM (#2731274)
      > KDE is a good product, don't get me wrong. But why does it have to look just like MSFT's products?

      The point is, it doesn't have to, it just can.
      • The point is, it doesn't have to, it just can.

        Somebody please mod that up, that answers about half of all the anti-KDE/Linux FUD out there:

        "KDE looks like Windows"
        "Linux is recompiled on a daily basis"
        "Linux is used from the CLI"

    • If you don't like the style, change your style engine. If you don't like the theme, change the theme. KDE is totally customizable.

    • But why does it have to look just like MSFT's products?

      Because, like it or not, the MSFT products it looks like (i.e. not XP, which out of the box is horrible IMHO) do a really good job at making day to day tasks simple. There's more than 20 years of research behind that (Xerox PARC ripped off by Apple ripped of by MSFT), so why should the KDE-team spend unnecessary time redoing that research?

      This is of course not to say that they shouldn't if they feel they can come up with a better solution, but the one they have now works well enough, so ...
    • blackbox
      afterstep
      windowmaker

      just about everything other than gnome and kde look completely different and act completely different.

      My favorite is afterstep, small, super fast, and written in C instead of that damned C++ (because I know C and personally Hate C++, actually blackbox is awesome example of how C++ can fly!)

      If your window manager is larger than 4 megabytes, it is no longer a window manager, it's an application integration environment.
      • because I know C and personally Hate C++, actually blackbox is awesome example of how C++ can fly!

        That's because Blackbox did C++ right. C++ done right is awesome. C++ done mediocre is really mediocre. And C++ done bad is abysmal.

        Unfortunately, the foundations of Qt were made while the C++ standard had not yet been finalized. And it is still portable to non-standard C++ compilers. Because of this there are a few hacks, quirks and workarounds that aren't good C++ and will never be good C++. Qt is a great library, and there are valid reasons for its kludges, but they still remain kludges.

  • What about speed? (Score:3, Interesting)

    by PastaAnta ( 513349 ) on Thursday December 20, 2001 @07:02AM (#2731272)
    The biggest problem with KDE (IMHO) is the unresponsive feeling - especially when starting up programs. Are there any changes to this in KDE 3.0?

    I know it is mainly something about a compiler/linker issue, but what is the progress in that area?
    • I agree. The speed is very important. If the gui is slow, it doesn't matter how many features it has. That's why I usually run windows NT, because moving windows, resizeing windows and browsing the disc is so much faster there.

      • Re:What about speed? (Score:1, Offtopic)

        by Psiren ( 6145 )
        Well that's fine and dandy if all you do all day is move and resize windows and browse your disk. For the rest of us who actually use our computer to do something productive, the choice of OS has a lot to do with the programs that are required. Having said that, there are a lot of NT programs that I could use during my day-to-day admin duties, but Linux and it's associated programs offers me all I need.

    • Wait for glibc 2.3... (Score:5, Informative)

      by marm ( 144733 ) on Thursday December 20, 2001 @12:26PM (#2732648)

      ...or (horror of horrors) compile glibc yourself with Jakub Jelinek's prelinker patches, if you can find them (they seem to have disappeared off the net).

      The dynamic linking of libraries is by far the biggest cause of KDE program startup slowness. A big desktop environment has a lot of shared libraries to link to an application at runtime, it's expensive computationally (particularly for C++ libraries), and the way the glibc dynamic linker works right now, it's done every time an application is started or a library is dlopen()'ed (such as when embedding a KPart). It can also cause swap thrashing on machines with limited memory (the entire library must be read into memory to perform the address relocation, only after relocation can the VM drop pages of the library) and obviously, disk contention between this swapping and the application loading can slow things down even further.

      What the prelinking patches do (don't get them confused with the objprelink hack which, while useful, is not a long-term or efficient solution) is move the linking time from application startup time to system startup time. A tool runs at system startup, immediately after ldconfig runs, which loads and relocates libraries in its search path, then notes down the relocation addresses. Then, later, when the dynamic linker is asked by an application to load a library, it simply uses the values that were cached earlier. Any libraries that have not been 'prelinked' are simply relocated as normal. The linker also makes sure that non-prelinked libraries are not relocated into the same address space as any prelinked libraries that are not currently loaded.

      The next major version of glibc will hopefully include library prelinking by default, but I haven't been following glibc development closely enough to know for sure. Let's keep our fingers crossed. Note that it's not just KDE that will benefit from this, Mozilla will gain a great deal (it, like KDE, is mostly C++ code split into many shared libraries) and even GNOME will benefit a little - doing the dynamic linking on C libraries still costs processor time, although it's much less than with C++ libraries.

      The next biggest cause of KDE startup slowness is icon loading - currently every app has to search through the entire set of available icons on startup in order to load the icons that it needs. Not very efficient. Given that KDE has several hundred icons available already and that is likely to increase over time, it needs a solution. Waldo Bastian is apparently working on an icon server for KDE 3.0, which will do that search once, cache the data, and then respond with appropriate icons when an app asks, rather than forcing the apps to do it themselves every time. I'm hoping it also makes it easier and faster to do image compositing (overlays and so forth) with icons.

      To sum up: glibc 2.3 together with KDE 3.0 should make a huge improvement to app startup (and KPart embedding) time, and, assuming the KDE guys are tight with their code, may even make KDE 3.0 usable on machines that couldn't effectively run KDE 2.x.

      • This seems to be one area where MS have got their OS technically superior. Windows DLLs are by default 'pre-linked' in the fashion you talk about, as they have compiled into them a standard base address. As long as you don't use two DLLs that have conflicting base addresses (and with a centrally organized desktop environment, you can get that right every time) you're fine!

        • Back in the old days of Linux, circa 1994, it was precisely that model that was used for libraries. Back then Linux used the COFF (or a.out) executable format that required libraries be pinned to fixed base addresses, there was also a registry that assigned base addresses to libraries. It was a complete pain in the ass. When Linux moved to the ELF executable format, we got relocatable shared libraries and I don't think anyone seriously wants to go back. The prelinker sounds like a pretty good compromise to me.

          • I don't think its that bad of a problem. a.out had other issues that made people hate it (specifically, shared libraries were a bitch to build and the semantics of shared and dynamic libraries were different). The only problem with prelinking is that on x86 machines, you soon run out of that paltry 4GB address space. On my machine, /usr/lib, /lib, and /usr/local/lib add up to about 460MB. These images become bigger in RAM since the BSS (zero-initialized data) isn't present. On a larger system, you could easily blow the address space with all the libraries (think Microsoft apps!) With 64bit archs, this is a non-issue, however. The good thing about the scheme, however, is that you potentially don't need position independant code, since you could relocate the library once at install time and not have to touch it afterward.
          • Windows DLL's *can* specify a base address, it doesn't *have* to use it. It's a suggestion, but if the address is in use, it will relocate it. Wouldn't be too hard for linux's ld.so to do something similar ... would be nice for the development of ld.so to get a divorce from the pile of smegma that is glibc first...

  • "From the development team who tries to break every development speed record (last month they released KDE 2.2.2) comes KDE 3.0 beta 1, with lots of new features, new QT (3.0.1). It is beta 1 so expect crashes.

    One argument tending away from Linux and to *BSD is the advantage of maturity. Another important trait is the slow implementation of new features (eliminating many bugs). Introduce two features simultaneously and something breaks, which was to blame?

    • Well, if you want maturity and stability, just ignore the new stuff. Distros like debian stable make this really easy for you.

      I think it's a clear advantage to have both new, possibly bleeding-edge stuff and old, probably rock-solid stuff available.

  • Speed (Score:3, Interesting)

    by kikensei ( 518689 ) <<joshua> <at> <ingaugemedia.com>> on Thursday December 20, 2001 @08:15AM (#2731444) Homepage
    Well, I just installed the beta on my SuSE 7.3 workstation, without issue. KDE3 is much snappier, it feels much mpore crisp when opening apps, windows, etc. It has apparently better font rendering. Kpilot, while unfinished, I can tell is much improved in terms of feature and interface, next up is to actually test it with my USB Visor. Konquerer file manager has much more solid support for multimedia previewing/viewing within the file manager window. As a browser, Konquerer still crashed and burned on my Chase banking web site, so Mozill 0.96 is still the way for me. It seems faster as well in KDE3, albeit initial startup is still a bit slow. I've been using Evolution 1.0 for mail, and it still works fine in KDE3. I still cannot cut and paste an URL from an Evolution email into my Mozila browser. KMail looks a bit more fine tuned and launches quicker than before, I have yet to test its use though. KDE3 it seems is primarily an architecture shift to QT3, but the results are impressive in the feel and response. Visually, while a bit cleaner, its the same KDE that you already either like or not.

  • Woohoo... (Score:3, Interesting)

    by Junta ( 36770 ) on Thursday December 20, 2001 @09:06AM (#2731661)
    I noticed on the list of features that they are going to extend the keyboard shortcut mechanism to support more extended keyboard shortcuts and enable them to make DCOP calls from shortcuts. Why is this so important to me? I have a Gateway multimedia keyboard, which, for the "special" buttons sends 3-4 keycodes per button, the windows key combined with at least two letter keycodes and other modifier keys depending on the button. Until now I haven't seen a clean way of getting these keys to work (the few apps concerned with this are limited to single keycodes...). Now I can bind this to applications. Now, is there a DCOP enabled mixer that supports XOSD, or am I going to have to write one? The KDE mixer should suffice. Can't wait to get off of work and try this sucker out, for this stupid little feature alone.
    • Ok, so it is still in the TODO stage, but it still ought to be pretty cool when it is finished...
    • Now, is there a DCOP enabled mixer that supports XOSD

      I've just started (about 2 hours into it) creating KOSD, which is can display like XOSD, but have information scroll up, fix an information bar on the display, or display information in Kinkatta style OSD. Much of that is "TODO", not in code. It can be attached to by all apps via DCOP, and then you can centrally control (via a paneltray icon)color per app, turn display on per app, how the app will display, and scroll back through old messages.

      It's *very* much an idea rather than code at this second, but I'd like to scramble and get it functional asap so the dcop connection works at least. (Hey, OSD status for one off bash scripts running in the background or with long run times would be nice).

      If you're interested, email me at slashdot@timewarp.org. Quite frankly, I'm swamped with contract work through to the first of next year, and I'm dubious as to when I can get some serious time on the project, but someone else working on it would be great incentive. :) --
      Evan

  • When are the GCC people and everyone else who is needed to fix it, fix the damn C++ loading problem that slows down every c++ app? All of kde would get a nice speedboost, what was it 30-40%?

    Also, it's interesting but maybe the kde folks have been holding themselves to a very high standard *because* of that bug. Maybe it just forced them to write code as slim as possible and when that bug is removed it will really pay off :)

    • Using GCC 3.1 to build your applications will help.

      Right now, you can install Red Hat's rawhide distribution to get KDE 3 built with a snapshot of GCC 3.1.
  • The screen updates are modest, but look much cleaner - I particularly like the anti-aliased fonts (yes, I know they're in 2.2.x). However, there are a couple thing I and others I've worked with have ALL remarked that KDE and associated apps need:
    • Kmail needs LDAP support. At least 2.2.2 on Debian Unstable doesn't include it, and I didn't see it in the list of features (though everything else we needs like SSL/TLS support seems to be making its way into it).
    • Anti-aliased fonts are great, but there are times when aliased fonts are actually preferable. In particular, I used anti-aliased fonts, but in terminals, I *really* want a regular-old courier font. At 1024x768 in my terminals, anti-aliasing makes it difficult to tell the difference between and m and n or a , and .
    • Could someone PLEASE make Konqueror stable? It's getting better, but it still crashes on me (or locks up) frequently, more often when I open multiple windows. It seems that if I open 5 or 6, it's bound to lock up, while it can go for days on 1 or 2.
    • A "smarter" cookie feature. Netscape used to "allow cookies only from originating server". I liked that option. It allowed me to use sites like ebay, slashdot, etc, without having to add them to my list of allowed domains. Right now, I get either "Allow, Deny, or Ask". "Ask" *seemed* like a great idea, but some sites want to add 10 cookies - and it's terribly annoying. I'd be *really* impressed if someone came up with a way to detect useful cookies (like logins or shopping carts) and useless ones (like ones that simply track your visits).
    • Tabbed konqueror windows. Seriously. I like to open lots of windows so I don't have to keep using the Back button, but if I have several windows open, it's tough to manage them. A sidebar or nav bar tab with an option to open in a new window or as a tab (like the newer mozilla releases) would be really helpful.


    That's all. Hope I didn't ask too much :-) I'm not much of a C++ coder, nor do I have the spare cycles to help out (unfortunately), but these are things (particularly Kmail) which I've seen a tremendous need for. Thanks for all your hard work, K-team!

    • Re:Features needed!!! (Score:4, Informative)

      by LMCBoy ( 185365 ) on Thursday December 20, 2001 @10:19AM (#2732019) Homepage Journal
      Have you submitted bug reports/feature requests for any of these (especially konq crashes)? KDE needs your input to fix these things. Complaining on /. doesn't count :)

      "Anti-aliased fonts are great, but there are times when aliased fonts are actually preferable. In particular, I used anti-aliased fonts, but in terminals, I *really* want a regular-old courier font. At 1024x768 in my terminals, anti-aliasing makes it difficult to tell the difference between and m and n or a , and ."

      konsole -noxft

      It's a life saver, since most AA fonts don't render well in konsole anyway :)
  • You've got to love the fact that KDE offers Objective C and Java bindings.

    People tend to forget but you don't have have java bindings under Windows!!! (Well, unless you want to lock yourself up with MS broken Java implementation.)

    Of course, this is rarely used, but the mere fact that it is available is amazing. I don't know about Objective C and windows though... How does that work?
  • At my desk in a client's office, I have a win2k machine. The magic of VNC [att.com] allows me to work on an X desktop. But I also sometimes work on my laptop from home. So, I have different VNC sessions going simultaneously at different screen resolutions.

    I currently use fvwm2 because kde 2.x doesn't support more than one kde session per user per machine.

    Has this changed in kde 3?

    • I currently use fvwm2 because kde 2.x doesn't support more than one kde session per user per machine.

      Huh? that is plain false. You can run as many kde
      sesssions per machine as you want

  • I have yet to be able to render java pages correctly with konqueror. The cnn.com/QUICKNEWS pages never renders the headlines correctly. I would very much appreciate if this was fixed or if someone could tell me what my dumbass maneuver has been. I am using FreeBSD with KDE, and have built the jdk. It still will not use it correctly even though the java option is set correctly in the konqueror options.
  • Apple sent a truly gung-ho demonstrator to the NY PC Users Group meeting after Internet World to put OS X through its paces, and I ended up with my first Mac soon after.

    I like it so far, but the idea of dropping half a grand on Redmondware sort of defeats my purpose in buying a non-Wintel machine. Trolltech's site says that Qt3 comes in a Mac OS X version, but I'm fuzzy on how much of KDE is Qt "skeleton" vs C "muscle." Could someone make a SWAG at how much effort would be involved in creating a working KOffice for the Mac?

Slashdot Top Deals

Be sociable. Speak to the person next to you in the unemployment line tomorrow.

Close