Slashdot Mirror


KDE 2.0 Technology Overview

Recently, there was an article about a KDE 2.0 Technology overview here on Slashdot. Unfortunately, the article it linked to was missing some details and didn't give some necessary information, which caused a huge number of complaints and misunderstanding in issues like CORBA, DCOP etc. Now mofset has posted an updated Technology Overview with all the explanations about what's going on with KDE 2.0, CORBA, DCOM, KSycoca and other terms. What do you think?

167 comments

  1. Re:Comments on CORBA by sopwith · · Score: 1

    It all depends on which CORBA implementation you use. I have a simple CORBA demonstration server here, on which 'size' reports 4119 bytes on the server and 3938 bytes on the client.

  2. Re:XML by Chalst · · Score: 1

    Ah yes, XML-RPC. It makes sense now.

  3. Re:KDE == Good by cybrthng · · Score: 1
    been able to theme kde for quite a while now.. can even plugin enlightenment.

    I can look like a mac, beos, or whatever i want.. even changing icons, title bars, everything really.. under 1.0 it didn't work well, but 1.1 added a great theme manager, and 1.1.1 built apon that even more.

  4. KDE 2 = Nice, but how bad will RedHat f' it up? by notbob · · Score: 2

    Are they going to do another brilliant move and move the files out of /opt/kde again?
    It's the most annoying thing in the world to get redhat rpm's and watch them put it in a f'd up location, true switchdesk is nice and all but leave it where it was intended by the programmers!

    I know RedHat likes to make everything customized, but jesus leave it alone. I like RedHat overall and their new installer is damned nice (esp. compared to the old 4.2 which is so archaic it's almost funny), but the damn thing formats / without asking unless you select custom install. Thats crazy, and annoying as hell, done that twice to me, oh well thank god for 4 harddrives.

    1. Re:KDE 2 = Nice, but how bad will RedHat f' it up? by cremat · · Score: 1
      Are they going to do another brilliant move and move the files out of /opt/kde again?
      It's the most annoying thing in the world to get redhat rpm's and watch them put it in a f'd up location, true
      switchdesk is nice and all but leave it where it was intended by the programmers!


      I completely agree with you. Having KDE and GNOME in /usr makes me sick. Then, if you want to compile KDE and GNOME apps from tarballs they install to /usr by default. For me, /usr is sacred. I believe anything not being core components of the OS should go to either /usr/local or /opt.


      I have been using KDE since Beta2, compiling eveything from tarballs. I decided to try GNOME a few weeks ago. Since I did not want to mess /usr with packages that do not belong there, I had to edit the gnome rpm specs amd recompile all SRPM packages to install them in a different location. I could have compiled from tarballs in the first time, but I wanted to prove my point.


      For those of you who like to place certain applications in /opt, here's a script I have declared in /etc/bashrc to automate your $PATH to reflect new directories in /opt. It was made by cpg, not me.



      repath () { # pick new stuff off /opt
      for i in /opt/*/bin ; do
      if [ -x $i ] && (echo $PATH | grep -v --silent $i); then
      PATH="$PATH:$i"
      fi
      done
      }

    2. Re:KDE 2 = Nice, but how bad will RedHat f' it up? by Dionysus · · Score: 1

      The people who are responsible for the file path standard (FSSTF? some acronym, who can remember) says that anything that comes with the distribution CD should go in /usr. Everything that goes the local system only (not network), should go in /usr/local. /opt is packages that was not included in the distribution.

      RedHat follows the standard. If you get a package from RedHat, it installs into /usr. If you get a KDE package from KDE, it installs in /opt.

      I do agree with you, though, that putting desktop environment (spreading GNOME and KDE all over the place) is a very BAD IDEA. Someone should change the standard.

      --
      Je ne parle pas francais.
  5. Re:Comments on CORBA by kgeorge · · Score: 1

    I whole heartedly agree. In addition to which the corba semantics and definitions have all been defined by committee which means that every one tried to be nice to one another trying to achieve consensus and it shows. Ease of programming definitely seemed to have been at the bottom of their wish list.

  6. Re:Who wants your shitty little 10 dollar app? by arielb · · Score: 1

    so you're basically saying that linux is only for the rich-either large companies like IBM and Oracle or people who have enough time on their hands to give away their work for free. Screw the small developers huh?

    --
    ---
  7. Re:Who wants your shitty little 10 dollar app? by Arandir · · Score: 2

    $1000 is not that much, even for the small developer. If you plan to sell a shareware app for 10$ a pop, and expect to sell 1000 copies, then you've just grossed $9000! If you don't plan to sell that many copies, perhaps it's time you rethought your whole vocation.

    Head on down to your local Mom-And-Pop store on the corner. It doesn't matter what they're retailing. Now take a look at their fixtures. How much to you think it cost them? Real life example: Mom-And-Pop carpet store down the street: Armstrong Vinyl rack = $1000~; each individual carpet waterfall = $50-75$ and there are 25 of them, and this isn't covering the samples; specialized accounting software = $1500 per cpu; carpet roller in the back = $5000; etc., etc., etc. And these are the small guys!!!

    $1000 is peanuts for a quality tool like Qt, and it even comes with support and updates. It's nothing compared to what you'll have to spend on quality marketing.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  8. Re:KDE == Good by Guy+Harris · · Score: 2
    Fortunately for the world, I never did get that far

    Damn. Any interest in trying again, this time with a Qt 2.0 or GTK+ 1.2 theme?

    that's only a short step from talking paperclips...

    Anybody know if Microsoft has an SDK for the Office "Assistants"? Having Tux or Beastie suggest you use StarOffice or KOffice or... instead, or having Mr. Hanky the Christmas Poo or Bart Simpson or some other alternative, could be amusing....

  9. Re:What do you call the compiler costs? by plague3106 · · Score: 1

    Support? Ever call MS? At my old job, we had a problem with this query on sql server 6.5...called tech support, they insisted it was us. Then they tried it...they crashed it too. Called us back a few days later...'don't do that' was their solution. You call that support?

  10. Re:Other KDE2 "technology" by Anonymous Coward · · Score: 0

    I'm running it now you blithering git. Ever heard of CVS? Did that look like a release announcement to you?

  11. Re:This looks seriously neat! by Anonymous Coward · · Score: 0

    It'd be nice to have 256 different clipboard units, like AmigaOS had in 1986(and microsoft are passing off multiple clipboards as a great new feature in office 2000)

  12. Re:Qt for free for free software. by C.Lee · · Score: 0

    >Bite my ass. That kind of shareware would help bring Linux to the >forefront of the computing world.

    Says who? Windows users? Spare us please.....

  13. So I would need *two* orbs? by Anonymous Coward · · Score: 0

    That doesn't sound like a good idea...

    1. Re:So I would need *two* orbs? by JamesHenstridge · · Score: 1

      An ORB is not a huge 10MB daemon running on your system (at least it doesn't have to be). It is a library that marshals requests to possibly remote or out of process objects. If you use two different ORBs at the same time, you would just have two libraries in memory -- many of the CORBA services such as name service and interface repository could be shared (and you probably would want to).

      CORBA does not have to be huge. For instance there is a partial implementation of the marshalling (not services) code written in a bit over 1000 lines of emacs lisp.

  14. Re:XML by Rozzin · · Score: 2

    Yes, XML is a language.
    XML is a subset of SGML.
    XML is a metalanguage.
    XML is for doing markup.
    XML is not a programming language.

    --
    -rozzin.
  15. What about memory usage? by Anonymous Coward · · Score: 0

    What's the memory usage of the ORB?

  16. Re:Is Gnome using Corba extensively? by Anonymous Coward · · Score: 0

    GNOME is using Corba fairly extensively. The activation code uses it, the control-center/panel uses it. Bonobo uses it. Gnumeric uses it (you can manipulate your spreadsheet through CORBA calls), and even the CD player uses it. The file manager uses it to manage the desktop (want to add an icon, just make a CORBA call.) A lot of the simple stuff, though has a GtkObject wrapper or something similar so app developers don't need to know they're using CORBA.

  17. What *I'd* like... by pwhysall · · Score: 1

    ...is for KDE to be able to use GTK+/E themes.

    That would be very, very nice. I have precisely no clue as to how hard it would be, though.

    On a different note, I'd like to know how much effort is going into the installer for KDE 2.0; the 1.0 one wasn't much to speak of (although it's better than GNOME's - i.e. it does at least exist).

    Peter.
    --

    --
    Peter
  18. Re:I'm still nervous. by evilpenguin · · Score: 5

    DDE doesn't do applications embedding. That's OLE. DDE is a horse-dung IPC mechanism that sends messages in the message queue to EVERY RUNNING APPLICATION on a Windows boxen.

    The expense of ORB calls can be very similar to the cost of initially calling a shared lib, but from then on shared library calls will tend to be much faster than ORB calls. This difference gets exaggerated when a lot of data is passed in the call and/or in the result, because all of it has to go through the transport representation conversion and data transmission.

    Now, while I've done a fair amount of IDL/ORB/IIOP stuff in my time, I haven't looked into the KDE code at all. If they did it right, they should have a lightweight IPC API that can use a variety of transports and that will autmatically use the much faster local *nix capabilities on the local machine, and the moderately slower Xlib capabilties between X-displays, and use CORBA for anything more divergent. Point being the app writer should not have to particularly know or care.

    CORBA is VERY time expensive, esp. when you're talking about things that have a dramatic influence on the perception of speed, like redrawing windows.

    Often the user's feeling of performance is based more on finding the right place to stick the delay than in having the fastest end-to-end time for a process.

    Case in point: I once eliminated hundreds of user's complaints about a slow system by slowing it down about 40%. We had a PowerBuilder (ugh!) front end to a client-server application. One of the forms had a pick list that was HUGE, populated by a stored procedure call. That call would often take 3-4 minutes to complete. Users went bananas because they got the good olde Win 3.1 hourglass while the pick list was populated.

    I changed the code to pick up one record at a time from the result set and insert it in the pick list rather than make the single "all at once" call. It actually took 2-3 minutes longer to fully populate the pick list, but the users never got the hourglass and could start working the form right away. Zero complaints.

    I guess what I'm saying is, KDE is a UI. As such, it has to focus on user issues, not technological issues. I am 100% a technology guy. I'd rather satisfy myself that things are done right than satisfy users. Even so, the KDE folks want people to use their software. That means they have to address user issues first and put architecture second. It seems to me they are doing a danged fine job of balancing these concerns.

  19. Re:This looks seriously neat! by Hard_Code · · Score: 2

    Well there are ways to trim down CORBA alot to bypass network requirements, etc...but yes, even the trimmest CORBA orb will have some additional overhead over straight calls...it just needs to be used when appropriate.

    --

    It's 10 PM. Do you know if you're un-American?
  20. NOT FUNNY by Anonymous Coward · · Score: 0

    this shows that moderators are anal, and have no sense of humor

  21. Are the moderators asleep? by Anonymous Coward · · Score: 0

    Just checking... BTW: KDE looks more like CDE than anything else.

  22. Re:But will KDE get swallowed apps? by Anonymous Coward · · Score: 0

    Can you run the gnome panel and kill the kde panel? Hmmm?

    Yep... except that no kpanel stuff will integrate into the gnome panel, and vice versa (yet...)

    There's _no problem_ (except waste of space) runing both GNOME and KDE apps on the same desktop. They just don't talk to eachother much (yet) - KDE invented their own Drag and Drop protocol, while GNOME inherited motif's

  23. Re:This looks seriously neat! by Anonymous Coward · · Score: 0

    > I can't find any mention of improved clipboard > services in the KDE 2.0 doc. When I looked at > the KDE 1.1.2 code recently there were only > three types of clipboard data - text, bitmap and > URL's. KDE 2 will have a much better clipboard support - any data can be copied and pasted, it will be recognized by mimetype.

  24. Re:KDE it *UGLY* *SLOW* and *NOT GPL* by Anonymous Coward · · Score: 0

    Americans tend are slower to use KDE - the "not invented here" syndrome. Pretty much all europeans use KDE before GNOME (they'll run GNOME apps on their KDE desktop, though). KDE looks better, is more stable, and is more mature. Note: do not judge the stability of KDE by the RedHat 6.0 / 6.1 installation. I have no idea why, but it's really flaky on my system - Mandrake KDE is rock solid...

    GNOME is alright so long as you're a C programmer.

  25. Re:Comments on CORBA by Q*bert · · Score: 1
    Yes, the KDE developers have consistently chosen the most practical route when faced with tough design decisions. This goes for GUI design especially, at least in my opinion. KDE apps work, and they're easy to use.

    Anyway, I'm wondering what GNOME's extensive use of CORBA and KDE's general eschewing of CORBA will mean for full integration of the environments. In particular, I wonder when, if ever, kpanel will communicate with E. I love E, but not being able to use the taskbar in kpanel is too much of a loss to let me switch over (from kwm, natch). For those of you who are wondering about kpanel and E playing together, the launchers and swallowed apps work fine if you invoke kpanel --no-KDE-compliant-window-manager, but the dern taskbar (the only good thing Microsoft ever invented, except maybe Joliet) doesn't work. D'oh!


    Beer recipe: free! #Source
    Cold pints: $2 #Product

  26. Re:Is Gnome using Corba extensively? by Anonymous Coward · · Score: 0

    Sorry "itp", but nobody uses Bonobo.

    Wrong--perhaps the best GNOME app, gnumeric, uses it.

  27. This looks seriously neat! by jd · · Score: 3
    KDE 2.0 looks very nice, and I'm glad the developers are using technologies which are practical, rather than using just the "glamour" stuff. (eg: Using CORBA =when appropriate=, rather than for everything under and over the sun.)

    I've tended to shy away from KDE, after KDE 1.x proved very slow on my box. However, I'm definitely going to give this a try, and see how it performs now.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:This looks seriously neat! by sleepingduke · · Score: 1

      > KDE 2 will have a much better clipboard support - any data can be copied and pasted, it will be recognized by mimetype. That sounds really nice. Will it have more than one clipboard though, or still just use XA_PRIMARY? I can't find XA_SECONDARY used for anything - what about nominating that as a clipboard for search text? Copy and paste on a typical KDE app doesn't behave the way a Mac/Wiindows/NeXT user would expect. For instance, if you open a text file with kwrite. Select some text, then choose the copy command from the menu. Then scroll down the file a bit and select some more text. Then choose paste from the Edit menu. Ask a Mac user whether they thought the text in the file will have been changed and they will say "yes", but a KDE user will say "no". Any text you select is automatically copied to the clipboard overwriting what was there (whether you wanted that to happen or not).

    2. Re:This looks seriously neat! by Anonymous Coward · · Score: 0

      This is an artifact of the old X / UNIX copy-paste convention - basically, at one stage in the distant past there was no _buffer_ for copied text - what was highlighted was what was pasted when you clicked the middle mouse button. That's why you have xclipboard - it is a program that is just a blank sheet (i.e. a visible buffer) to copy the text to, temporarily. (and it's also why UNIX people scream when you take their middle mouse buttons away...)

      It's just a different way to do it - if you learnt the UNIX way first, the buffered system seems very slow and clunky. Of course, once you start talking about cut-copy-pasting by mimetype, you really need the buffered system. What /I/ want to see is multiple selectable buffers

      The AmigaOS had 256 cut buffers in 1986, conventionally stored in CLIPS: - it identified clip types by IFF filetype, which was an amiga system-specific thing, somewhat akin to mimetypes. AmigaOS style-guide compliant programs allowed select which clipboard unit (0-255) you wanted to use, although most people stayed at unit zero.

      Multiple clipboards were made even more useful by a commodity (AmigOSish for daemon) called ClipHistory, which shoved the previously buffered sleection to the next unit i.e. 0->1 1->2 etc, each time you cut - thus implementing a clipboard history. _Very Useful_

    3. Re:This looks seriously neat! by itp · · Score: 2

      KDE 2.0 looks very nice, and I'm glad the developers are using technologies which are practical, rather than using just the "glamour" stuff. (eg: Using CORBA =when appropriate=, rather than for everything under and over the sun.)

      I'm not sure what you're trying to say here. On a modern UNIX, you've already payed the price by using it once. If it's going to be in memory as a shared library (and ORB), why not use it multiple times?

      --
      Ian Peters

    4. Re:This looks seriously neat! by jd · · Score: 2

      In memory, yes, but the ORB'll be shunted out into swap if it's left sleeping, which frees up some RAM. The biggest factor, though, is network times. CORBA requires a stupendous number of network connections to do anything. (DNS lookup for name registry; ORB connection to obtain list of services; ORB connection to connect to service; 2 hops, even when using the same machine, to transmit from client to server). This is -not- efficient.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    5. Re:This looks seriously neat! by sleepingduke · · Score: 1

      I can't find any mention of improved clipboard services in the KDE 2.0 doc. When I looked at the KDE 1.1.2 code recently there were only three types of clipboard data - text, bitmap and URL's. Clipboards aren't as glamorous as components and run time linking and so on, but they are probably going to be used the most often. It would be nice to have a clipboard type for search text, set up a search for a word in one app, change to another app and hit search - it might look for the same word. Or richer data types like PDF, RTF or similar so you can paste text with attributes in a standard manner.

    6. Re:This looks seriously neat! by Anonymous Coward · · Score: 0
      No, DNS is not involved in using the name service, nor are there millions of round trips involved.

      Neither do you even have a "connection" to an ORB - the ORB is just a library that implements the CORBA API.

      Efficiency is a matter of implementation - CORBA can be as efficient as the ORB a CORBA application uses.

  28. I'm still nervous. by Amphigory · · Score: 2
    I guess I don't get it. It seems like they are creating something similar to "DDE" in the Windows environment to support their application embedding operations.


    However, as I understand it, the overhead of a local execution in a good ORB (say ORBit or OmniORB) is equivalent to that of a shared library call. Why not use a good ORB and have the added benefit of network communications?


    Can someone who is brighter than I explain this? For the record, I actually use KDE and am not a GNOMEr in any real sense of the word.

    --
    -- Slashdot sucks.
    1. Re:I'm still nervous. by arivanov · · Score: 0
      I guess I don't get it. It seems like they are creating something similar to "DDE" in the Windows environment to support their application embedding operations.
      • At first DDE is not windows but OS2 technology predating windows by far
      • At second DDE was and is network aware (thanks god that scripting kiddiez do not know how to use it under M$)
      • At third there is only one step from DDE to OpenDoc which is not bad as technology
      Why not use a good ORB and have the added benefit of network communications?

      Because it stinks by design as a general purpose exchange mechanism

      • It will never be 100% compatible across platforms (there will always be thy black sheep , call it M$, call it something else)
      • It will always be slower then a properly written platform specific exchange mechanism
      • It will always lag behind in utilizing all the capabilities of a particular OS or desktop environment
      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    2. Re:I'm still nervous. by itp · · Score: 2

      However, as I understand it, the overhead of a local execution in a good ORB (say ORBit or OmniORB) is equivalent to that of a shared library call. Why not use a good ORB and have the added benefit of network communications?

      This is my understanding as well. Also, the memory usage should be quite tame, since this is a share library, not something that should bloat each app. However, I understand the KDE people have been having serious problems with binary bloat while using MICO.

      --
      Ian Peters

    3. Re:I'm still nervous. by LizardKing · · Score: 2

      As the article states, CORBA itself doesn't provide a machanism for embedding in X applications, it simple allows the process to be initiated. The actual embedding is still relies on X and KDE library calls, so CORBA was just adding complexity to this.

      As far as I understand it (and I'm an user of KDE, not one of the programmers), the new embedding technology is as simple an API as possible. Presumably a wrapper around CORBA is out of the question, because a wrapper around what is essentially a wrapper already is daft. Perhaps if the OMG's CORBA specification hadn't been designed by a band of muppets things would be different.


      Chris Wareham

  29. Re:When IS CORBA appropriate? by patrik · · Score: 1

    Umm CORBA is used in distributed computing, along with Java. In fact today I was just talking to a guy who has been doing just that, at NASA. As far as being open sourced it's not but it is quite a substantial example, that it isn't as useless as you say. I personally haven't worked with it though so I don't know how difficult it is to learn.

    --
    ----------
    Just your ordinary BOFH ;)
    http://killertux.org
  30. Re:Other KDE2 "technology" by Anonymous Coward · · Score: 0

    Also, what PIM needs a PII/233+ and 64MB of RAM to run ?

    Lotus Notes 5 Client

  31. This looks like the way to go ... by LizardKing · · Score: 4

    Having recently compiled a snapshot of KDE 2.0, I can say with some conviction that it's a Windows killer. The usability is much better, and the optimised build much smoother. Having had to do some testing of Unix apps running under the Windows Reflections X server, I'm suprised at just how poorly NT performs when more than one application is open. (I mean Windows apps like Outlook and Explorer, not the Unix apps).

    The loss of Mico as a dependency for KDE 2.0 is also a good thing. Mico is just too large for it to form the basis of a component model, the only place it really shines is truly network transparent CORBA apps.


    Chris Wareham

    1. Re:This looks like the way to go ... by Davorama · · Score: 1

      Having a completely finished desktop environment won't be the windows killer. It's a great first step to having the completely integrated office suite which is what will bring in the masses and the business users.

      --

      Davo -- Free speech, free software, AND free beer.

    2. Re:This looks like the way to go ... by Emil+Brink · · Score: 1

      ...it's a Windows killer. The usability is much better, and the optimised build much smoother.
      Um, exactly how often to you tend to (re)build Windows, then? Perhaps you meant "... smoother than on previous versions" on that last part, and I'm just being picky? ;^)

      --
      main(O){10<putchar(4^--O?77-(15&5128 >>4*O):10)&&main(2+O);}
    3. Re:This looks like the way to go ... by TummyX · · Score: 1

      Um, I find NT to handle very well with multiple apps. I regulary have 20 or so apps open, about 10 IE windows, ICQ, SQL, SET, REAL etc etc etc....and it's fast as.

      Ever tried to open more than one netscape? Or maybe staroffice?
      ROFL

  32. Re:Who wants your shitty little 10 dollar app? by Anonymous Coward · · Score: 0

    You morons all missed the point. I often times will write a small app that fills a need for myself. I think 'Gee, maybe a few others could use this..' and put a blurb in it about sending me $10 as a donation of sorts. Not necessarily to make a lot of profit, just hope someone cares and appreciates it enough to send the $10. Now, I owe TrollTech $1000 for Qt. F*ck them. I don't even plan to make money and certainly not $1000 off it, just a couple of 'donations'. I don't plan my life or my career around it. Get the point dickhead?

  33. KDE == Good by Foogle · · Score: 2
    When KDE 2.0 comes out, we will be able to really start themeing our look and feel, something the GTK has been much better at in the past. With KDE theming, we can finally make GTK and KDE apps *look* the same, and that's pretty cool in my book. Right now, the only themes that they both can do are Motif/Notif and Win95/Redmond. That's not much to work with.

    On a related topic - would it be possible to rework the Lesstif libraries in such a way that they would support a different look and feel? That would make UI integration almost perfect (except for statically linked binaries).

    Anyway, just my US$0.02

    -----------

    "You can't shake the Devil's hand and say you're only kidding."

    1. Re:KDE == Good by seth_hartbecke · · Score: 1

      Yes, everything.

      KDE has a theme manager that will both tell QT what do do and change as many other things as possiable (such as the title bar style in the window manager, the icons used on the desktop...). It even tries to get Motif applications to chage their theme (just the default colors) as much as possiable (you have to restart them after you install a new theme, and I cannot change everything on a Motif application.) If you want an preview of this get KDE 2. There is also a theme control panel in KDE 1.1.2, but because KDE 1.x is based on QT 1.4 it cannot change as many things.

      --
      END
    2. Re:KDE == Good by Guy+Harris · · Score: 2
      I can look like a mac, beos, or whatever i want.. even changing icons, title bars, everything really.

      Everything? Including, say, scrollbars? The theming added in Qt 2.0 is the ability to make the widgets look different (beyond the Windows vs. Motif stuff Qt 1.x can do), not just the stuff drawn by programs such as the window manager or file manager.

    3. Re:KDE == Good by Guy+Harris · · Score: 2
      Yes, everything.

      My question (which was rhetorical; I already knew the answer to said question was "no") was about KDE 1.x, as I was replying to somebody who said

      been able to theme kde for quite a while now..

      ...

      under 1.0 it didn't work well, but 1.1 added a great theme manager, and 1.1.1 built apon that even more.

      so the correct answer to my question is not "yes, everything", given that, as you note

      because KDE 1.x is based on QT 1.4 it cannot change as many things

      The poster to whom I was replying was presumably replying to

      When KDE 2.0 comes out, we will be able to really start themeing our look and feel, something the GTK has been much better at in the past.

      in another post, a comment that was referring to the ability to theme widgets (as is clear from the stuff following said comment).

      The whole point of my comment was that the ability to theme the UI to that extent is new in KDE 2.0; it's not something that people have "been able to [do] for quite a while now", unless they've been running pre-release KDE 2.

    4. Re:KDE == Good by Eccles · · Score: 2

      Everything? Including, say, scrollbars?

      Once when I was going overboard in coding, back in DOS/Win3.1 days, I started writing a scrolling manager that would have allowed things like a little animated climbing monkey to serve as the scroll bar. Fortunately for the world, I never did get that far; that's only a short step from talking paperclips...

      --
      Ooh, a sarcasm detector. Oh, that's a real useful invention.
    5. Re:KDE == Good by seth_hartbecke · · Score: 1

      >My question (which was rhetorical; I already knew the answer to said question was "no") was about KDE 1.x...

      I withdraw my flame then. Sorry.

      --
      END
  34. Quite ambitious... by Wayfarer · · Score: 1

    I rather like the idea of two levels of IPC: a basic set and the whole CORBA shebang. Maybe the existence of a simple set of common hooks in this department will encourage more developers to make their programs friendlier to other programs. More modularity is a good thing, to me.

    I'm looking forward to the release. Whenever that is. :)

    --

    -W-

    Is it all journey, or is there landfall?
    --Ellison & van Vogt, 'The Human Operators'

  35. Semantics of network transparancy by code4444 · · Score: 2

    I did some reading on the KDE mailing lists, and from what I gather the problem is not so much the efficiency of the calls, but their limitations.

    You can't use pointers across a network. All arguments are passed by value. That those values could be passed as fast as a shared library implementation isn't important. Sometimes you just need pointers.

    The straw that broke the camel's back for KDE seems to be the plugins for KImageShop. Those plugins would be processing bitmaps - potentially several megabytes of data. For a shared library you just pass a pointer. For something like CORBA you have to:

    a) serialize the bitmap to well defined external representation.
    b) transmit that to the plugin
    c) unserialize it to a bitmap object again.
    d) do the real processing
    e) serialize again
    d) transmit again
    f) unserialize again.

    This is silly. Nobody is going to run an image processing plugin over the network.

    CORBA has a place. When you do want to work across processors / OSes / toolkits / networks / programming languages you *have* to do these steps some way or another, and having something like CORBA is a huge improvement over the ad hoc solution du jour.

    You also have to deal with communications failures, the other end going ga ga, latency problems, bandwith problems, how do I find the other end on this big internet thingy anyway, security etc.

    If your application is distributed you inherently have these problems, and it's great to have a mechanism to help you solve them.

    If you just want a stinking plugin, it's a pain.

  36. Re:Neato. But... by Anonymous Coward · · Score: 0
    It's amazing to consider that some of these ideas are brilliant, yet simple, and never seem to make their way as simply into the corporate world than they do in the Open Source movement, where a program is an end in itself (as opposed to a marketable product) and tools like CORBA are a mean to an end.


    The reason I've noticed is that there are no managers, and no executives, and no stockholders in the OSS movement. The closest we come are people like Linus... think back on how many times you read posts to the kernel mailing list when he rejects patches with comments along the lines of "this patch is crap. try again when you can actually fix the problem." - the man has got FINAL authority and he's not a manager. After spending a full day at work surrounded by fsck'ing idiots in decision making roles it is so refreshing to come home and sink into the OSS world where technical decisions are made for technical reasons, not politics, not money.

    I could name quite a few instances where the folks in the trenches knew in their heart and soul that product X, or codebase Y was technically superior to W or Z but were overruled by management because they had been deemed "non-strategic". In OSS this simply wouldn't happen. The highest leaders would probably feel the same way, or if they didn't would open and lead a free (as in speech) technical discourse on the topic untill either a decision was made or the factions clearly stalemated and splintered. While splinters aren't usually good on the grand scheme of things, they're so much more important on the individual scale as they keep the developers interested in their work; rather than becoming bitter about the code they're forced to work on being such putrid slime.

    Oh, and to bring it back to the specific ideas... I can think of two corporate projects off the top of my head that were killed becuase they were NOT using CORBA, but in fact had implemented their own distributed object technology that was either incredibly lite weight or far more feature-full. And several more that are being forced to move to CORBA.

    p.s. I do have an account, but since many of my co-workers and a couple managers read /. there isn't a chance in hell I'm going to put my name to this! (I may be sick of thier crap, but not their cash! ;)
  37. A different take on things by itp · · Score: 4

    This article sounds a little bit like spin to me. Not trying to start a flamewar, but here we see a bit of the architectural advantage the Gnome folks have. Writing a completely new ORB (ORBit) might have been a bit 'o work, but it's paying off for the Gnome project, while KDE still struggles with MICO.

    Every application supports a basic set of IPC operations for communicating to other applications, and it is not reasonable to expect *every* application to link to any ORB.

    I'm no expert, but I'm not sure I understand this. If you're already going to have the ORB running, and you've got the libraries in memory, how much of a price do you pay having 100 applications using CORBA vs. 1 application using CORBA and 99 using some other mechanism?

    --
    Ian Peters

    1. Re:A different take on things by Arandir · · Score: 2

      I'm not trying to flame here, but what architectural advantage is there when your model won't allow a change in direction? ORB was not working out for everything KDE wanted it to do. So they did the sensible thing and came up with something else that was smaller, faster and easier to use, and kept ORB for those tasks where it was needed.

      It seems to me that ORB has become the holy grail of Gnome. A couple of weeks ago the so-called abandonment of ORB was touted by the Gnomies as *proof* of KDE's inferiority. Now that mosfet sttempts to correct a gross misunderstanding, you say it sounds like spin-control. To quote a great line from a great movie, "some men...you just can't reach." Face the fact if you can that there is room enough for two or more A+ desktops.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    2. Re:A different take on things by Anonymous Coward · · Score: 0

      While KDE turned out a highly polished set of applications, the Gnome project seemed to focus on a broader framework initially. Here it seems to pay off for them.

      That's wishful thinking. The 'polished set of applications' of KDE is based on the old 1.1 version and not developed much further. All efforts go into KDE pre2, which is very much focusing on the framework.

    3. Re:A different take on things by Anonymous Coward · · Score: 0

      I certainly hope that you didn't hear anyone from the Gnome project saying that this is proof of KDE's inferiority. Statements such as these only serve to undermine the spirit of cooperation we'd all like to see.

      Comming from the user's POV of both KDE and Gnome, I don't see why some folks make a fuss about the differences. I guess, like politics and religion, the closer you agree with someone the more violent the reaction on the little differences.

      I have both KDE and Gnome installed, and I use them both. The competition between the two is good.

      I'm thinking of ways to help out, though, since I've taken more than I've given, and that's not right. (Thanks to anyone who is on the giving side of the scale!)

      For example, I've started to write an interactive Introduction to KDE for my sister who thinks that learning MS Works makes her computer savy. While some of the tutorial is personalized, the rest can probably be used by any novice. I estimate that I've put about 30 hours into it so far, and it's not too bad. A version of this document could be made for Enlightenment+Gnome, or any other window manager fairly easily.

    4. Re:A different take on things by Telcontar · · Score: 1

      Yes, there definitely *is* a gain. CORBA's inter-process communication is, despite having a very elegant concept, rather heavyweight. Every RPC, while almost completely hidden from the programmer, transfers a large amount of data between processes (which may be on the same computer or distributed). The object identifier alone is some 200+ bytes large (which allows, in theory, nice things such as process migration, but is also quite cumbersome).
      The libICE mechanism is more lightweight, and remember, since it is also standard, involves no overhead from the point of view of loading new shared libraries.

    5. Re:A different take on things by itp · · Score: 3

      First off,

      I'm not trying to flame here, ... "some men...you just can't reach." Face the fact if you can that there is room enough for two or more A+ desktops.

      You're doing a poor job, then. FYI, I in no way deny the existence of two very high quality desktop environments. This despite the fact that I choose, for my own reasons, to use, support, and develop for Gnome. In much the same way that I, as do many people, choose to use GNU/Linux, while acknowledging that there are many "A+" OS's out there (the *BSD's, for instance).

      Now, to the meat of your comments.

      I'm not trying to flame here, but what architectural advantage is there when your model won't allow a change in direction? ORB was not working out for everything KDE wanted it to do. So they did the sensible thing and came up with something else that was smaller, faster and easier to use, and kept ORB for those tasks where it was needed.

      I'm afraid we've miscommunicated here, and I suspect the fault was mine. What I was trying to say was the the Gnome project seems to have a lead in working out these architectural issues. While KDE turned out a highly polished set of applications, the Gnome project seemed to focus on a broader framework initially. Here it seems to pay off for them.

      It seems to me that ORB has become the holy grail of Gnome. A couple of weeks ago the so-called abandonment of ORB was touted by the Gnomies as *proof* of KDE's inferiority.

      First, a technical note: I believe you are confusing the terms ORB and CORBA. Second, I certainly hope that you didn't hear anyone from the Gnome project saying that this is proof of KDE's inferiority. Statements such as these only serve to undermine the spirit of cooperation we'd all like to see.

      Now that mosfet sttempts to correct a gross misunderstanding, you say it sounds like spin-control.

      Yes. To me, this sounds like a way to put a nice face on some technical issues they were unable to resolve. This is merely my opinion, being shared in a forum which invites people to share their opinions.

      --
      Ian Peters

    6. Re:A different take on things by Shadow+Knight · · Score: 1

      To reinforce what an AC said before, and perhaps clarify it: the article by mosfet seems, to me, to be saying "We've resolved these technical issues, and here's how" rather than "Uh oh... uh... look over there!" Which is what you seem to be saying it says. That is to say, it isn't spin-control, because there's nothing to spin... they've resolved the issues, in a way that looks to me, as a programmer, to be good.

      That was probably more confusing than the original AC post by that other person...

      --

  38. www2.jorsm.com/~mosfet by Anonymous Coward · · Score: 0

    He also writes the widget/theme code for KDE 2.

  39. KDESoft! by Signal+11 · · Score: 3
    KDE is not the next Microsoft. They cannot, and will not develop "proprietary" protocols because of the way open source works. It's obvious Gnome and KDE are going two seperate paths. Rather than complaining about this, we should be commending both groups efforts in the GUI arena.

    The scenario alot of slashdotters believe (which is not addressed in the article) is that KDE is somehow going to become the de facto GUI. Well, due in part to the paranoia that alot of us have as well as the fact that the two groups have seperate goals, that isn't going to happen. One may be more popular than the other (How many people still use fvwm instead of E?), but because of open source (Yes, Richard, I know it's not free software..) it's impossible for either gnome or kde to co-op the other.

    Besides, if that happened the paranoia many of us share in this community would quickly fork the tree and continue along a "free" path, essentially killing the old version.

    So relax - there is NOTHING to worry about in this area. And while I'm up here on this soapbox - Redhat is OK too - so stop complaining about them becoming the next MS too.

    --

    1. Re:KDESoft! by Uruk · · Score: 1

      >It's obvious that Gnome and KDE are going two >seperate paths. Rather than

      Yep, and that's one of the best things about the two projects. I got the feeling at the inception of GNOME that it was created to compete in a way with KDE. That's fine, and choice between two desktop systems is good, but I think it's wonderful if they diverge in what their core focus is at a certain point in time because not only does it give you choices, but it gives you choices spread across a field rather than clustered in one area of desktop useability.

      I hope that made sense.

      --
      -- Truth goes out the door when rumor comes innuendo. -- Groucho Marx
  40. Evidence that /. is anti-KDE by Anonymous Coward · · Score: 0

    The fact that this flamebait is moderated up to three proves how anti-KDE some moderators are.

    1. Re:Evidence that /. is anti-KDE by Skip666Kent · · Score: 1

      It's a matter of perception. Where you see evidence of some sort of bias, I see mere silliness and tomfoolery. A waste of time and resources, to be sure, but that's nothing gnu around here, and welcome in small doses.

      I'm a huge fan of KDE and I thought it was damn funny. The original moderator must have mis-read "Insightful" as "InCITEful".

      --
      **>>BELCH
  41. LOL! by Anonymous Coward · · Score: 0

    (tears streaming)
    (writhing on floor)
    (curly shuffle)

    Whew.

    (quiet moment)

    LOL!

  42. Other KDE2 "technology" by Ledge+Kindred · · Score: 2
    I've tried a few times to get /. to post this link to a KDEForum article on "Magellan" - KDE2's new information manager system. It's EMail, News and PIM all in one, something like a Lotus Notes or Microsoft Exchange/Outlook except will be GPL'd. If the article is in any way accurate and not a hoax (it looks horribly functional and I have to take with a grain of salt that a project this massive has been kept under wraps and done up by only a few people working on it...) it will be a Big Win for KDE2 and any *NIX in general that can run it.

    Magellan Overview

    -=-=-=-=-

    --

    -=-=-=-=-
    My mom's going to kick you in the face!

    1. Re:Other KDE2 "technology" by Masker · · Score: 1

      Well, one thing, it's total vaporware. There are no downloadables yet (though it "should be ready" by Dec, '99.

      Also, what PIM needs a PII/233+ and 64MB of RAM to run (with faster processor/more RAM suggested)? Is it cracking RC5 blocks in the background? It's an email reader/addressbook/to-do list! How can it possibly need that many resources? Sorry, at home I may have a system that will support that, but at work I'm on a lowly P/166 w/ 64MB RAM that is shared as a server with 3 other people. If I can't use it on a reasonable machine, then forget it! That sort of bloat I surely don't need.

      --

      ---------The early bird gets the worm, but the second mouse gets the cheese.

  43. /. not politically correct enough! by negative_karma · · Score: 1

    This irresponsibility is proof that immature wannbe's should be allowed to moderation. Welcome to slashdot, folks.

    I completely agree! I'm supposed to be getting -1's folks, WTF are you moderators thinking?!?!?!?

    --
    Worse than an untouchable, when I reincarnate I'll be lucky to return as bacteria.
  44. Re:KDE looks like Windows, therefore it sucks by Yarn · · Score: 2

    This isnt insightful, its only marginally funny. I'm looking forward to when it gets to meta-moderation.

    It only takes one or two moderators with nothing better to do to get stuff like this to the top.

    I've noticed that once something starts going up it tends to accelerate past 3 and up to five, even if its only mildly worthwhile.

    --
    -Yarn - Rio Karma: Excellent
  45. People wonder why KDE thinks Gnomers. /. suck by Anonymous Coward · · Score: 0

    If little gnomies moderating this up to 5 is any indication, they are right.

  46. Divide And Conquer by Anonymous Coward · · Score: 0

    Now, make sure you also give strong support to the GNOME project.

    Divide and conquer, and all that.

  47. Gnome caught up?!? by Anonymous Coward · · Score: 0

    So, where is GNOME's Office suite? Where's the word processor, the spreadsheet, the presenter, the illustrator, the image maker, the database, etc etc, that are all part of one nice suite? Koffice.kde.org. gno-office.gnome.org. "caught up" please.

  48. Re:When IS CORBA appropriate? by samantha · · Score: 1

    What are distributed objects that are OS and platform independent good for? Presumably you already know the answer. (Hint: it is NOT "nothing")

  49. Re:KDE it *UGLY* *SLOW* and *NOT GPL* by warmi · · Score: 0

    No .. not really . here in my office there are 5 developers running linux and one free bsd. Of all linux people only one is running twm and the rest KDE.
    And I can assure you our office is most definately located in US ( Chicago).

  50. Re:KBasic? by warmi · · Score: 0

    This is not a problem of having scripting language like VB. There are good scripting tools available for unix. The problem is that Linux is lacking in infrastructure like unified access to databases (ODBC) and things like that.
    These things make VB so easy to use ...

  51. Re:XML by JamesHenstridge · · Score: 1

    XSL is an application of XML, not XML itself. You don't use the existence of C as proof that ASCII is a programming language.

  52. Re:XML by mill · · Score: 1

    Yes, and you don't markup text in XML either, but with an application of it.

    The original claim was "It is an important step to a completely component based architecture programmable via languages such as XML in as powerful a manner as the native API." but of course they mean an application of XML. Just like Glade doesn't save an representation of a Gtk GUI in XML.

    When people say "XML" they mostly mean "an application of XML" and in that context XML is an programming language - if one wants to.

    /mill

  53. I certainly know what I'm talking about ... by LizardKing · · Score: 2

    How the heck KDE is going to affect load on X caused be other apps ?

    Other KDE apps you twit.

    And as someone who has been programming X applications since the bad old days of OpenLook and then Motif, I have a feeling I know what I'm talking about.


    Chris Wareham

  54. Re:Comments on CORBA by grrussel · · Score: 1

    E is KDE compliant as Of 0.16 - so it'll work with the taskbar.

    George Russell

  55. Re:MMMMSSSS by Anonymous Coward · · Score: 0

    as someone with a wife suffering from MS I find this completely tasteless

  56. This is kindof funny by Anonymous Coward · · Score: 0

    There are seriously some people who think if it's not Xlib it's evil. Funny.

  57. Kpanel/Kicker: applet-screenshot: here! by Anonymous Coward · · Score: 0


    A screenshot of a well-known applet in kicker (formerly known as kpanel) can be found here.
    The new hicolor-icons are not in CVS-HEAD yet though. So if you don't like the icon above, be aware of the fact that it is still one of the old locolor-icon for people with 8-bit-graphics-adapters.
    If you haven't seen the new icons yet, have a look here (PNG) or here (JPG)!

    Have a nice day,

    ac

  58. Link requires authorization?!? by Brian+Knotts · · Score: 2
    What's up with that?

    Even http://www.kdeforum.org/ is asking for a username/password.

    --
    Interested in XFMail? New XFMail home page

  59. People fear controversy, there4 they're humorless by maynard · · Score: 2

    Man, the author writes up front that it's a (Score:-1, Troll). He obviously intended it to be slightly offensive because that's the point of HUMOR.

    You folks are WAY OVER-REACTING!

    KDE is fine. Gnome is fine. Go on and continue your boring and bland lives where everything is politically correct.

  60. Silly me - Sorry, replied to the wrong subject ... by Anonymous Coward · · Score: 0


    ac

  61. GuiltWare! by Anonymous Coward · · Score: 0

    Who wants your friggin blurb begging for money? Crap like that has no place on the street, much less Linux. That's called "pandering" or "panhandling" when done elsewhere.

    1. Re:GuiltWare! by C.Lee · · Score: 0

      >Who wants your friggin blurb begging for money? Crap like that has no >place on the street, much less Linux. That's called "pandering" or >"panhandling" when done elsewhere.

      And these guys are the first ones in line demanding that laws or ordinances be passed banning it in the areas where they live. Ironic isn't it?

  62. Re:Who wants your shitty little 10 dollar app? by C.Lee · · Score: 0

    >so you're basically saying that linux is only for the rich-either >large companies like IBM and Oracle or people who have enough time on >their hands to give away their work for free. Screw the small >developers huh?

    Damn right. They've been screwing us for years. It's exactly the 10 dollar crap app that's turned a hell of a lot of people off on shareware. A lot of that crap is buggy as hell and the people who release it know it. They figure they can con people into "upgrading" to the "professional" versions of the software. In other words shareware has become pretty much a "bait and switch" operation and it's something most of the people using Linux/BSD want no part of anymore.

  63. Mine is bigger than yours by Anonymous Coward · · Score: 0

    And my castle has a garden.

  64. Re:KDE Will Die and here is why.... by Anonymous Coward · · Score: 0

    Also, if you sell your something for Gnome for $10, that not free. That is wrong. The only GNOME library not under LGPL is the libgtop library, which I doubt you'd need anyway.

  65. Re:Comments on CORBA by Q*bert · · Score: 1
    No, it doesn't. I built it from the source RPM last week.


    Beer recipe: free! #Source
    Cold pints: $2 #Product

  66. Wow - no massive Gnome vs KDE flame war by Anonymous Coward · · Score: 0

    In the past this thread would have been nothing but unintelligent flames from both camps. Either the general maturity of KDE/Gnome advocates has increased or Slashdot moderation is really working. Either way, I'm impressed!

  67. Re:Comments on CORBA - good post by Anonymous Coward · · Score: 0

    Wouldn't it have been easier to implement an ORB that didn't suck (ye ghods, what were you using, anyway?) than throw away all your work?

  68. Re:People fear controversy, there4 they're humorle by Yarn · · Score: 2

    Thats fine, I personnally think it should be at about 2, funny. It was at 5, interesting when I posted. This post doesnt merit that ;)

    --
    -Yarn - Rio Karma: Excellent
  69. KDE == CRAP by Anonymous Coward · · Score: 0

    Take a look at winfiles.com and see all of the shareware available for windows. That is because, unlike TrollTech, even M$ doesn't charge a developer fee. I will not pay $1000 to TrollTech so I can develop a small app and sell it for $10. Not a chance in hell. I will do it for Gnome for free. KDE needs to REPLACE that crap from TrollTech or it will not succeed like windows has. My 2

  70. Re:Surely some mistake? by kip3f · · Score: 1

    Language, yes. Programming language, no.
    XML = eXtensible Modeling Language.
    --
    Man is most nearly himself when he achieves the seriousness of a child at play.

    --
    ****Gfx Scrollbar Special case hit!!*****
  71. Applet-screenshot: here! by Anonymous Coward · · Score: 1


    A screenshot of a well-known applet in kicker (formerly known as kpanel) can be found here.
    The new hicolor-icons are not in CVS-HEAD yet though. So if you don't like the icon above, be aware of the fact that it is still one of the old locolor-icon for people with 8-bit-graphics-adapters.
    If you haven't seen the new icons yet, have a look here (PNG) or here (JPG)!
    (This one is a screenshot of KDE 1.1.2)

    Have a nice day,

    ac

  72. What do you call the compiler costs? by Anonymous Coward · · Score: 0

    free?

    1. Re:What do you call the compiler costs? by Anonymous Coward · · Score: 0

      Certainly not $1000 per developer. That what I call compiler costs. If you pay that, then I have a copy of Redhat I'll sell you for about $3000US.

      Any Compiler/IDE for Windows is much cheaper than that and you get commercial support - for those interested in that.

    2. Re:What do you call the compiler costs? by shadrack · · Score: 1

      Cetainly more than $1000.00 per developer if you had actually known what you were talking about.

      Enterprise Edition of MS Visual Studio > $2500.00 US.
      Delphi Client/Server version > $1500.00 US

      BTW, thats per developer pricing. And yes there are cheaper versions (less tools/features) of each.

      Neither price includes long term support, thats extra, a lot extra.

      might get some discounts for large purchases at a very large organization. Small ISVs like most of us have to pay up for the latest and greatest.

  73. KDE Will Die and here is why.... by Anonymous Coward · · Score: 0

    Take a look at winfiles.com and see all of the shareware available for windows. That is because, unlike TrollTech, even M$ doesn't charge a developer fee. I will not pay $1000 to TrollTech so I can develop a small app and sell it for $10. Not a chance in he||. I will do it for Gnome for free.

    KDE needs to REPLACE that cr@p from TrollTech or it will not be as successful as windows has.

    My 2

    1. Re:KDE Will Die and here is why.... by Seli · · Score: 1

      Take a look at http://www.kde.org/applications.html ( and many other places ) and see all of the _freeware_ available.
      KDE dying because of lacking shareware ? A good joke. This is definitely not a reason for KDE to die.
      Also, if you sell your something for Gnome for $10, that not free.
      Oh, and btw, IMHO Qt is one of the reasons KDE is that successful as it is.

  74. Re:Comments on CORBA by yorkie · · Score: 2

    I applaud KDE for this decision.

    If you want to really see bloat with Corba, look at the agent processes supplied as part of CA Unicenter.

    It varies from OS to OS, but on most systems the agents, which do no more than monitor a few OS stats and parameters (and badly chosen ones too :-) ), take up at least 32MB of RAM, and a large percentage of CPU cycles. Neither of these are acceptable for the purpose this software was designed for - systems management. The system is consequentially unusable in the environment I have been tasked to install it in.

    It is often the case that software developers adopt a new technology without realising the full consequences, and when they do, it is too late to go back. I have seen a major application become unusable due to the developers wanting to recode the next version in C++, as opposed to ironing out the bugs in the C port. This application consumed four times as much memory, was noticably slower, and was incompatable with the majority of existing installations. CORBA appears to be the new fad.

    I may even get round to trying a development release KDE 2.0. I have not been able to install KDE 1.1.2, as I can't get Qt to compile with gcc-2.95.1. Maybe 2.95.2, just released will fix this.

  75. Qt for free for free software. by Anonymous Coward · · Score: 0

    If you want to write shareware crap like on winfiles.com you better stick to windows, your not wanted here.

    1. Re:Qt for free for free software. by Anonymous Coward · · Score: 0

      Bite my ass. That kind of shareware would help bring Linux to the forefront of the computing world.

  76. Yet another by Anonymous Coward · · Score: 0

    If adopting ORBit fixed things, KDE can adopt ORBit, just like GNOME adopted KDE's HTML widget.

  77. Yet another by Anonymous Coward · · Score: 0

    If adopting ORBit fixed things, KDE can adopt ORBit, just like GNOME adopted KDE's HTML library.

  78. Re:Get a clue! by Anonymous Coward · · Score: 0

    It's very lame that the Windows version isn't free for non-commericial use. I wanted to compile Qt Slash'em (nethack variant) on NT and those freaks charge for Windows Qt. Screw that - no open source group should be using Qt unless it's free for non-commercial use on all the platforms for which the product is available. I know - who cares about NT. Well - some of use it because we need it. Hell, some of us even prefer it to Unix and aren't the least bit ashamed to admit it.

  79. Re:KDE it *UGLY* *SLOW* and *NOT GPL* by warmi · · Score: 1

    Yep. Gnome is the future. All these 12 people who are using it can certainly confirm that.

  80. Great News by warmi · · Score: 2

    Really, KDE has a chance to develop something truly usable and something that will last. They actually do care about the user which can hardly be said about most GPL software.
    Way to go , guys ...

  81. Uh oh... by Ledge+Kindred · · Score: 2
    KDEforum.org looks like it's broken. Sorry. Keep checking back though, Magellan looks awesome.

    -=-=-=-=-

    --

    -=-=-=-=-
    My mom's going to kick you in the face!

    1. Re:Uh oh... by whoop · · Score: 1

      For what it's worth, I'm getting into it just fine right now.

  82. I think you missed the point. by Anonymous Coward · · Score: 0

    --
    this sounds like a way to put a nice face on some technical issues they were unable to resolve.
    --

    This IS the solution to the technical issues, thus
    they were not unable to resolve them.

  83. Re:Comments on CORBA by boots@work · · Score: 1
    There's a very good discussion of the problems that arise if you fail to choose distributed interfaces carefully at:

    Facades As Distributed Components
    Distributed Facade

    My heuristic is that one should design CORBA interfaces thinking of them as network protocols, not as collections of objects in a program.

  84. Re:XML by Rozzin · · Score: 1

    You don't appear to be someone unfamiliar with programming, so I'd love to see some of your code, and hear what languages you've written in.

    --
    -rozzin.
  85. Qt is free software for free software development by Anonymous Coward · · Score: 0

    You don't have to pay a dime. If you want to use it for commercial development you have to pay for it, just like the GPL can require you to do. If you are not contributing free software back to the community you have no right to take advantage of it for your commercial applications. That is very much in line with RMS, who dislikes the LesserGPL. As far as shareware is concerned, let that stay with Windows.

  86. Who wants your shitty little 10 dollar app? by Anonymous Coward · · Score: 0

    This is Linux, shareware isn't acceptable. *Real* commercial developers have no problem with the TT and free software developers get to use a free library.

  87. KDE is GPL and quite fast. by Anonymous Coward · · Score: 0

    Why you people spread FUD is beyond me. KDE's the best desktop for Linux available.

  88. Clue: Your wrong on all counts by Anonymous Coward · · Score: 0

    Idiots.

  89. Take a look at freshmeat... by GauteL · · Score: 1

    ..And see all the FREE software for Linux and
    KDE. Shareware and Linux rarely goes together,
    because most GPL-software is far better than
    shareware anyway.
    Big commercial-applications may be better,
    but the companies behind those have no problem
    with the license-fee.

  90. Re:MMMMSSSS by Anonymous Coward · · Score: 0

    umm. MS = Microsoft. not playing on the condition MS.

  91. KDE 2.0 *is* free by Unanimous+Coward · · Score: 1

    So says RMS. KDE 2.0 will use Qt 2.0 which is not only "open source", but better yet it is "free". Being a sysadmin at a shop that is migrating from Windows to Linux/Solaris/NetBSD I am really psyched about this great desktop environment that will make the migration much much easier.

  92. Forgive my English ... by LizardKing · · Score: 2

    > > ...it's a Windows killer. The usability is much better, and the optimised build much smoother. > Um, exactly how often to you tend to (re)build Windows, then? Perhaps you meant "... smoother than on previous versions" on that last part, and I'm just being picky? ;^) I meant that KDE 2.0 built with optimisation is much smoother than Windows - no annoying lock ups while apps load or do something mildly heavyweight.
    Chris Wareham

    1. Re:Forgive my English ... by warmi · · Score: 1

      How the heck KDE is going to affect load on X caused be other apps ??
      Do you know what are you taking about ?

    2. Re:Forgive my English ... by TerryMathews · · Score: 1

      KDE doesn't affect the load caused on the computer by other programs. However, KDE does place a sizeable strain on older x86 hardware w/ slow, small memory subsystems (P133 16mb EDO ram). It's not really possible to have KDE speed up X applications. However, it is possible to clean up the KDE code and have it use less memory and processor time.

      --
      -- Terry
  93. Ahhh, so now the kde crew gets the big picture by Anonymous Coward · · Score: 1

    All that fancy stuff that kde did via its fancy mechanisms is easily and best done by X. They now see that X itself has the power required to implement 95% of their management...it was there all along. Congrads KDE team for waking up.

  94. Re:XML by jilles · · Score: 3

    "XML is not a programming language"

    No, you are right but you could use it to model a program just like you would model other datastructure. I have often wondered why we still have to store our precious source code in flat file databases (ascii files). I don't see any apparent reason except that many people like to use text editors to work on their source code. Because of this much syntactic sugar is put into the languages at the cost of structure and readability.

    Treating a program as a DOM instead of a large set of ascii files scattered in multiple directories would allow for really cool tools. I'm thinking of code transformations, changing an identifier name and have the effect of the change spread through the whole program (no references to non existent stuff), no more syntax errors (the DTD prevents illegal edits), and a whole lot more.

    --

    Jilles
  95. Re:But will KDE get swallowed apps? by cdmoyer · · Score: 1

    That has to be my single-least-favorite part of KDE. No dock apps.
    Of course, I just have a bunch of Wmaker dock apps on the side
    of my screen and I tell the advanced window settings to make them
    start stikcy and never get focus. Works pretty well.


    I definately think that the panel is the weakest portion of kde (1.x) at least.
    Can you run the gnome panel and kill the kde panel? Hmmm?

    --
    /* CDM */
  96. Re:MMMMSSSS by Anonymous Coward · · Score: 0

    well that was what I ment ..... she's forced to use MS :-) .... it's a dread disease .... she'd rather use KDE like me

  97. Who needs standards? by Anonymous Coward · · Score: 0

    Component architecture has been touted and worked toward for many years by many of us. If KDE folk are proposing a new component architecture (which it is not totally clear they are) then that architecture needs to be published and subject to serious peer review. The new component architecture needs a way to bridge to the larger non-KDE component space. And no, just being told to go look at the CVS is not adequate at all. Does anyone know of a good detailed published description of this stuff?

  98. Re:Get a clue! by Arandir · · Score: 2

    I do indeed wish that Qt were free on the windows side as well. I wasn't arguing against it. I'm very sure that once Troll Tech can figure out the appropriate funding mechanism, they will. After all, their clientele aren't exactly the type that would use and pay for a support-based funding model.

    What I was arguing against was the myth that the QPL'd Qt is only free for freeware and that once you charge for your application you must use the professional version.

    If you look at it a certain way, Qt is free for NT for you to compile QTSlash'em, you just have to run it under X under NT.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  99. Is Gnome using Corba extensively? by Anonymous Coward · · Score: 0

    I'm not an expert in either field but from what I can tell all Gnome is really using Corba for is applets and it's office suite, not nowhere as much as KDE wants to use it for. The stuff KDE wants to use all over the place (the equivalent of Bonobo I guess), isn't used at all in the core AFAIK.

    1. Re:Is Gnome using Corba extensively? by itp · · Score: 2

      Bonobo is based upon CORBA as well.

      --
      Ian Peters

    2. Re:Is Gnome using Corba extensively? by Anonymous Coward · · Score: 0

      Sorry "itp", but nobody uses Bonobo.

  100. Surely some mistake? by Chalst · · Score: 1

    It is an important step to a completely component based architecture programmable via languages such as XML in as powerful a manner as the native API.

    XML a language? Surely not, or has it become more ambitious since I last checked up on it...

    Nitpicking apart, this strikes me as a very sensible approach. CORBA is a bloated enough standard as it stands without being made to do things it wasn't designed for. Has anyone ever heard of DCOM before? Where else is it used?

    1. Re:Surely some mistake? by Chalst · · Score: 1

      I meant DCOP of course...

    2. Re:Surely some mistake? by smileyy · · Score: 1
      XML a language? Surely not, or has it become more ambitious since I last checked up on it...

      Well, that is what the L stands for, after all. XML = eXtensible Markup Language

      --
      pooptruck
  101. But will KDE get swallowed apps? by MagPulse · · Score: 1

    I just can't live without swallowed apps in my Gnome and Window Maker docks. Will KDE ever get these?

    1. Re:But will KDE get swallowed apps? by ruud · · Score: 2

      I just can't live without swallowed apps in my Gnome and Window Maker docks. Will KDE ever get these?

      The current version KDE does have some basic support for them, but they do need to be the size of a panel-button. Don't know about KDE 2, though.


      --
      --
      bgphints - internet routing news, hints and ti
    2. Re:But will KDE get swallowed apps? by Anonymous Coward · · Score: 0

      What is a swallowable app? I see the option on the GNOME panel but I still don't know what it does.

  102. KDE looks like Windows, therefore it sucks by negative_karma · · Score: 1

    I boot up with the penguin,
    My system ain't no lie,
    I don't run that fascist MS crap,
    I got the birdy suit and tie!


    Boot up the lilo and watch dmesg roar,
    see init launch /bin/sh and rc galore,
    It's OK to startx,
    fvwm's my friend,
    but touch that KDE crap
    and stain your self with

    Chorus
    MMMMMSSSS MMMMMSSSS

    stain yourself with
    MMMMMSSSS MMMMMSSSS
    unchorus

    KDE's like Windows,
    It's DCOM by 'nother name,
    you want the real baby,
    you'd write it in pure Xlib!

    So next you boot the penguin,
    give yourself a pause,
    should you consider KDE,
    know it breaks the UNIX laws!

    Chorus
    MMMMMSSSS MMMMMSSSS

    stain yourself with
    MMMMMSSSS MMMMMSSSS
    unchorus

    --
    Worse than an untouchable, when I reincarnate I'll be lucky to return as bacteria.
  103. Re:Qt is NOT Truly FREE!!! by Seli · · Score: 1

    Not even GPL'd is truly free. Only public domain is truly free.
    Enough said.

  104. Re:Get a clue! by Arandir · · Score: 1

    Get a clue dude! Qt is 100% open source and RMS certified Free. Go to Troll Tech and download it! No questions asked. No need to enter in a credit card number.

    Yes, the ***Windows*** version is proprietary, but the X11 versions free. And there's nothing preventing you from porting one to the other. You can even use Free Qt to create proprietary X11 apps!

    You said: "even M$ doesn't charge a developer fee." I say bullshit. Go price out the full version of VC++. But then you may be comparing the much cheaper (but still charged for) VB to Qt, and if you are, you really need a clue if you think they're equivalent in any way.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  105. Re:Qt is NOT Truly FREE!!! by Anonymous Coward · · Score: 0

    True.

  106. Re:XML by mill · · Score: 1

    Umm, and what do you call XSL?

    /mill

  107. It's fixed by Avus · · Score: 1

    I had a major breakdown (someone fiddled around with the server, filling the disk), but it's up again (damn, why does it break just today :}).
    Unfortunately some newer comments were lost. I hope I can get them back, and then I'll move to Zope 2 ;)

    The login prompt was due to wrong TinyTable permissions after the backup.

  108. It's a possibility by Foogle · · Score: 2
    A surge of software could help Linux to become the perfect desktop environment that we're striving for. On the other hand, it might not make a difference at all. Any existing software would need to be ported to Qt before we'd get it, though new software would do just fine. Except for one thing:

    Linux/xBSD users (and people of the open source inclination) don't tend to pay for their software. You need only look at some of the threads about Opera vs. Mozilla to know their heated opinions on the matter. Linux shareware might just be a doomed failure. Anyway, if someone really wants to develop shareware for Linux, there are certainly more toolkits than just Qt. Not KDE compatible toolkits, but good ones nonetheless.

    Moreover, I don't think that the KDE people should necessarily have to change their toolkit just to suit the needs of other people. They've got a wonderful product and it's built upon Qt. They don't care about the license, because they develop it for free anyway. I personally agree with them but, of course, you may beg to differ.

    -----------

    "You can't shake the Devil's hand and say you're only kidding."

  109. Compiler isn't the issue by Foogle · · Score: 2
    Who cares how much VC++ costs? It's the toolkit that's so much money. You can download EGCS for windows at no charge. It's just as good as VC++, I assure you. The only drawback is that some of the newer APIs don't have headers written for them yet. In any case, you'll never see me paying serious money for a compiler OR a toolkit, unless the programs write themselves (and no, I'm not interested in VB, thanks)

    -----------

    "You can't shake the Devil's hand and say you're only kidding."

  110. Big Iron Desktop ? by copito · · Score: 1

    That's an oxymoron if I ever heard one...let's see a Sun E10k, that's big iron, but as a desktop?, for one thing it's too high and too hot, not to mention expensive.

    As for you main point, yes bloated office apps can make any computer slow, regardless of the OS.
    --

    --
    "L'IT c'est moi!"
  111. Re:Comments on CORBA - good post by Anonymous Coward · · Score: 0

    I agree with your assessment completely. We had to abandon a ten programmer 18 month CORBA development because the size and complexity of CORBA was getting out of hand. We replaced it with an asynchronous messaging solution (non-CORBA) in a quarter of the time and the system shrank from 100 Megs of binaries to 12 Megs. Our application runs much faster as result. If CORBA is the answer - what's the question? I welcome any solution such as DCOP that actually saves time - and money - not a solution that creates work and headaches.

  112. KPanel can already swallow apps by Anonymous Coward · · Score: 0

    And kicker (the new panel for 2.0) supports applets with libICE DCOP communication and stuff like adding and removing kicker menu items dynamically. Someone already wrote a wrapper for WindowMaker applets (mosfet@kde.org)

  113. Neato. But... by Enoch+Root · · Score: 3
    This all sounds really neat. It's amazing to consider that some of these ideas are brilliant, yet simple, and never seem to make their way as simply into the corporate world than they do in the Open Source movement, where a program is an end in itself (as opposed to a marketable product) and tools like CORBA are a mean to an end.

    However, I wish there was some effort being done in making the various desktop environments intercompatible... I'd love to see development aimed at making it easier to code stuff that will run as smoothly on Gnome and KDE.

    Linux definitely needs that sort of interportability, but unfortunately it seems that development of applications for Linux is mostly modular, which leads to various branching left and right. It's a good thing Gnome and KDE aren't branching.

    Hackers of the world, unite?
    "Knowledge = Power = Energy = Mass"

    1. Re:Neato. But... by voop · · Score: 1

      However, I wish there was some effort being done in making the various desktop environments intercompatible... I'd love to see development aimed at making it easier to code stuff that will run as smoothly on Gnome and KDE

      If I am not mistaken (but I have no references at hand) there is an ongoing effort to make KDE and Gnome more interoperable - e.g. by using the same window manager hints etc (okok, it may be details, but they still are).

      That said, I installed KDE 1.1.2 not long ago, and after overcoming some initial annoyances (formerly a die-hard fvwm-user) I must say that, asside from some minor glitches I am mostly positively surprised by the system (long rant about what could be better left out for readability)

      Awaiting kde-2.....

      --
      -- "Life is a bitch - and she hates me..."
  114. KDE does not require you use it at all. by Anonymous Coward · · Score: 0

    I check the CVS from time to time and there is no requirement to use an ORB at all in any of the core stuff anymore. Some applications need it, but they are optional.

  115. i think he meant XML RPC by Anonymous Coward · · Score: 0

    since that's mentioned elsewhere.

  116. XML by SpinyNorman · · Score: 2

    > > It is an important step to a completely
    > > component based architecture programmable via
    > > languages such as XML in as powerful a manner as
    > > the native API.
    >
    > XML a language? Surely not, or has it become more ambitious since I last checked up on it...

    FYI, XML is now starting to be used as the representation layer for RPC/RMI in XML-RPC and SOAP. AFAIK these are both Microsoft initiatives, but given that they are based on standards and replace Microsoft's proprietary DCOM, I wouldn't write them off just because of that.

    There's also libglade which allows a GTK UI to be configured at run-time via XML (not sure if there's anything equivalent in the Qt world yet).

    XML seems to be becoming pretty pervasive as a method of data representation...

  117. When IS CORBA appropriate? by Anonymous Coward · · Score: 0

    I know CORBA is good for consultants to fill their wallets - I do it myself - but seriously - what IS CORBA good for? You've got to read a 1000 page book to even understand the damn thing and when you're done you've got a bloated and slow system. Anyone ever deliver a large scale open source system that actually uses CORBA? (actual ORB implementations don't count)

  118. Re:KDE it *UGLY* *SLOW* and *NOT GPL* by Anonymous Coward · · Score: 0

    There are only 12 of us? But the lab I am working in seems really crowded, I don't understand...
    No KDE users, 15 WinNT users, 10 FVWM users, 8 GNOME users, a couple of SGIs and a guy running TWM

    Why no KDE users? Because it isn't getting any better. GNOME caught up, and all KDE have is promises for the future.
    Also because those damn WinNT users have Office, and Gnumeric + Abiword load MS Office documents, something KOffice won't deliver any time soon.

    I don't think the free-ness (or lack of it) in KDE 1.x even came into the decision...

  119. KBasic? by Anonymous Coward · · Score: 1

    I would love to see a development system like Visual Basic. Yeah I know, I can hear the flames already, but VB allows you to knock up some nice database apps in a snap. It's just a shame they only work under Windows.

    May not be appealing to serious developers, but VB has a lot of followers, and some of us (including me) make a nice living cooking up these bespoke apps for our customers. If I had something like VB, I could easily convert some of my customer over to Linux.

  120. There is no "standards" issue here by JohnZed · · Score: 3

    Last time this subject came up, a number of people lamented the idea that KDE would abandon the "open standard" of CORBA for a new approach. I'm glad Mosfet has cleared things up a bit by explaining that libICE is equally a standard which, in fact, is a lot more common in the Unix/Linux world than CORBA.
    What I find really strange is the argument that GNOME's use of CORBA makes it more standards compliant than KDE. Don't get me wrong, if ORBit works well for this application, that's fantastic, keep using it. But ORBit actually implements only a very small fraction of a modern CORBA standard (MICO is fully 2.2 compliant with all the bells and whistles, so it is a slug in terms of performance), and does not yet provide C++ or Java bindings. Essentially, it's a handy, GNOME-only solution, like KParts is a handy, KDE-only solution.
    --JRZ

    1. Re:There is no "standards" issue here by sopwith · · Score: 2
      And which large fraction of the CORBA standard does ORBit not implement? I think you're probably repeating what someone else told you, rather than looking at the latest version.

      The point of CORBA is that language bindings are a non-issue, since an ORB for one language can talk to an ORB for another language. If you want C++, you can use ORBit-C++, Mico, OmniORB or any other C++ ORB. If you want Java, you can use whatever Java ORBs are out there.

  121. Comments on CORBA by Laxitive · · Score: 5

    OK. Lots have people have posted messages to the effect of "In a good ORB, the overhead of a method call to an interface is almost the same as the library." First of, there _is_ an overhead, but we can ignore that.

    The big problem with CORBA is _bloat_. If you implement all your internal embedded interfaces with CORBA, it leads to really unweildy sizes.

    The server for a simple CORBA demonstration (one structure and 1 interface defining 1 method), compiles to ~70K.

    The same functionality, if implemented with sockets or shared libraries, will probably take up less than 10K compiled.

    This is the kind of overhead you see with CORBA. Putting CORBA into every nook and cranny of your GUI implementation does not make it 3r33t.

    There is a time and place for CORBA. It's not for IPC, and it's not for embedded controls. It's best suited for large distributed applications.

    The K people have made a very practical decision by choosing shared libraries.

    -Laxative

  122. That's implementation specific... by Svartalf · · Score: 1

    And as such, varies from ORB to ORB. In the case of our application that I'm working on for work, the ORB, TAO, is fast (In fact, it's one of the fastest ORBs around and is one of the only real-time, embeddable ones...). The only complaint is that it eats something like 2Mb in the system while operating- but once fielded, it's just there, each app gains from it.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas