Slashdot Mirror


Novell Desktop To Standardize On Qt [updated]

Balinares writes "NewsForge reports that Novell has settled for Qt as its Linux desktop development environment, casting more light on their strategy to unify KDE and GNOME. This ought to be interesting. The prospect of using Mono to code against Qt makes me drool in advance. Maybe programming will suck no longer!" Update: 03/30 00:01 GMT by T : Sounds like that story doesn't quite hold water; Nat Friedman writes in this Slashdot comment that "We have not decided that we are standardizing on Qt for the desktop. ... We support development with a variety of toolkits, and our internal development is done using the right tool for the right problem. This includes Qt, Gtk, VCL, XUL and others, depending on the application."

149 of 615 comments (clear)

  1. Novell... by BJZQ8 · · Score: 3, Redundant

    Novell is slowly changing my opinion of them...

    1. Re:Novell... by attemptedgoalie · · Score: 2, Redundant

      I'd say me too, but I still have this gut feeling that they're going to screw up heinously somehow.

      --
      My mom says I'm cool.
  2. GTK is out, then? by 1010011010 · · Score: 4, Interesting
    What about that Ximian purchase? I guess it was just for Mono.
    1. Will they be writing a GTK-on-top-of-QT layer?
    2. Ditching GTK apps?
    3. Using GTK apps but not encouraging their creation?
    4. Just using QT for Novell-specific stuff (like Redhat uses GTK for its configurators, etc)?
    *confused*
    --
    Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    1. Re:GTK is out, then? by Directrix1 · · Score: 2, Interesting

      I personally would much rather see GTK adopted instead of QT, just because of licensing costs alone.

      --
      Occam's razor is the blind faith in the natural selection of least resistance and in universal oversimplification. -- EF
    2. Re:GTK is out, then? by Otter · · Score: 4, Interesting

      Not that I know anything but:

      1) I believe #4 is correct, at least for today's news.

      2)In the big picture, Novell wants to be a major Linux player, bought a lot of expertise, and is trying to integrate the two development platforms and environments without antagonizing either the developers from both sides or the screaming fanboys. I doubt if they themselves have a long-term plan yet.

      As long as I'm posting -- here's something I've asked a zillion times and still don't understand: given the GTK and Qt bindings for Mono, will it be possible to make run-anywhere applications on Linux that will work on Windows? Will generic .NET apps routinely work on Linux? Or is all developed code going to be toolkit specific?

    3. Re:GTK is out, then? by SoTuA · · Score: 2, Informative
      NEWSFLASH: Qt is available under the GPL!

      So, if you want to do your closed source software with Qt, you can pay through the nose. However, if you develop GPL software you are free and free. Like with GTK, right?

    4. Re:GTK is out, then? by pe1rxq · · Score: 4, Informative

      Actually it doesn't matter much...

      You can do object oriented and event oriented programming in c fine.
      Besides C is much more portable and there is a C++ interface for GTK to.

      So the only difference between QT and GTK from a language perspective is that with GTK you get a choice, QT you only get C++. (Not counting even higher languages such as C# since both have wrappers for that and are sort of equal)

      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    5. Re:GTK is out, then? by t4k1s · · Score: 5, Informative

      No, GTK is licensed using the LGPL license. Meaning that you can develop GPL software with it and commercial software without paying a dime.

    6. Re:GTK is out, then? by miguel · · Score: 5, Informative

      As Nat has posted elsewhere, the Heise article is wrong.

      My team and other teams within Novell continue to
      develop and use Gtk as their toolkit (recently
      open sourced Simias/iFolder for instance) and
      all of the Mono GUI development tools.

      The only use of Qt that am aware of today
      is SUSE's recently open sourced YAST.

      Btw, if you have been following my posts on
      my blog and on the desktop-devel-list, you will
      know that my feeling is that all of the existing
      toolkits today (Gtk, Qt, XUL and VCL) will
      become obsolete and we need to start looking
      at the next generation toolkit system.

      Miguel

    7. Re:GTK is out, then? by Valar · · Score: 4, Insightful

      It should be possible to make a run anywhere application on linux that will run on windows-- for the most part. Of course, details like file path formats are different between the platforms, so in certain cases a little mojo might be needed to work. Actually, it is mostly a case of 'best practices' and assuming nothing about the user's configuration (i.e. don't guess whether they have windows installed on C:\, find out. Don't guess that their home directory is /home/blah, use the objects given to you and find out).

      As far as the UI libs go, a lot of the time, they are going to have bindings into native code-- but that is something the libraries handle for you. So assuming your qt library or whatever has linux and windows support, it should work on both platform. Obviously, if a coder screws up one side or the other, there will be issues, but that can be said of any kind of multiplatform development-- or any development at all.

    8. Re:GTK is out, then? by Cthefuture · · Score: 2, Informative

      Will generic .NET apps routinely work on Linux? Or is all developed code going to be toolkit specific?

      It's been a long time since I looked at this stuff but this is what I knew back then.

      C# is a lot like Java in that is it "portable" but not really. That is, all the underlying API's have to be there or it won't work and Mono does not currently have all the stuff that you get with Microsoft.

      For example, on Windows the default C# GUI API is using the Windows.Forms interface (or whatever it is called). Mono doesn't have that interface yet. Last I heard they were planning to use Wine to provide the GUI .Forms interface. Good luck is all I have to say. Seems like it would be better to make a Forms-to-Gtk (prefer) or Forms-to-Qt interface.

      And the same holds for other API's not yet in Mono.

      So some apps will work but most won't even though the bytecode is compatible.

      --
      The ratio of people to cake is too big
    9. Re:GTK is out, then? by Rick+and+Roll · · Score: 3, Informative
      You can do object oriented and event oriented programming in c fine.

      Yeah, but it will be spaghetti code, using type-unsafe macros. Have you looked at a custom GTK+ widget implementation in C before? It is some real ugly code.

      So the only difference between QT and GTK from a language perspective is that with GTK you get a choice, QT you only get C++. (Not counting even higher languages such as C# since both have wrappers for that and are sort of equal)

      Actually, there are a lot of bindings for Qt. PyQt, for instance. Many consider them to be superior to their GTK+ equivelents.

      Writing something in C so it can have a lot of bindings is IMHO not the way to go. There should be other good reasons for writing it in C. You can always add a C interface to it, even one that doesn't use sockets. And many high-level languages have their binding interfaces specifically designed to support C++.

    10. Re:GTK is out, then? by phutureboy · · Score: 2, Interesting

      and is trying to integrate the two development platforms and environments without antagonizing either the developers from both sides or the screaming fanboys

      It seems to me that the easiest way to accomplish this is to put the developers from both sides in the same room, or in adjacent offices. I once worked in a web dev team which was one door down from the video production studios. Since we were all very creative and in contact all day long, we rather naturally ended up collaborating on lots of cool cross-media stuff.

    11. Re:GTK is out, then? by twener · · Score: 4, Insightful
      > The Gtk and Qt event loops aren't compatible (don't know the exact details since I haven't used Qt), so it isn't a trivial matter to take a Gtk program and make it use Qt.

      Wrong. http://dot.kde.org/1073668213/

    12. Re:GTK is out, then? by Espectr0 · · Score: 2, Insightful

      my feeling is that all of the existing
      toolkits today (Gtk, Qt, XUL and VCL) will
      become obsolete and we need to start looking
      at the next generation toolkit system.


      Which IS the next gen toolkit?

    13. Re:GTK is out, then? by InfoTaku · · Score: 2, Interesting

      Actually, Im on the mono IRC channel pretty much constantly, and I've also contributed a couple simple patches here and there.

      I can tell you that we've had many interesting discussions on IRC about this very subject.

      During our latest discussion Miguel de Icazza chimed in and settled things down. According to him this is all basically a miss understanding.

      Nobody from Novel has yet to make *any* official statement regarding the issue, and according to the people working for Novel that I have talked to they are *not* going to standardize the desktop around Qt.

      Novel will be making an official statement on this sometime soon.

      Personally Im expecting the press release to go something like this:

      1. Yes, there will be Qt apps. (This does make sense considering that Novel now employs a large number of KDE hackers thanks to the recent Suse acquisition.)

      2. Yes, Suse is mainly a KDE distro at the moment and that is probably not going to be changing drastically any time soon.

      3. No, GTK#/GTK+ apps are not going to disappear or otherwise be replaced in any way whatsoever. In fact if you look at one of Novels newest opensource offerings named iFolder you will see that it is in fact a GTK# application.

      4. Yes, Novel is looking for ways to better integrate its Ximian desktop with the KDE desktop.

      But don't make the mistake of thinking that GTK+/GTK# is diminishing or that Novel doesn't have a lot of Gnome love going on.

      I sabmoc, hear me snore..

      --
      [favorite blog] http://planet.gnome.org/
    14. Re:GTK is out, then? by be-fan · · Score: 2, Informative

      Eh? There are lots of bindings for Qt. Binding to C++ isn't actually that hard once you get certain tricky things worked out. KDE has a library (libSMOKE) that abstracts out those tricky things, to make writing bindings much easer.

      --
      A deep unwavering belief is a sure sign you're missing something...
    15. Re:GTK is out, then? by Electrum · · Score: 2, Insightful

      Don't guess that their home directory is /home/blah, use the objects given to you and find out

      UNIX apps doing things like that are hosed anyway for portability. For example, on Mac OS X, there is no /home.

    16. Re:GTK is out, then? by dozer · · Score: 3, Informative
      Last I heard they were planning to use Wine to provide the GUI .Forms interface. Good luck is all I have to say. Seems like it would be better to make a Forms-to-Gtk (prefer) or Forms-to-Qt interface.

      Microsoft clumsily exposed a lot of the Win32 API underneath the Forms API. Bindings must either reimplement significant portions of the Win32 API (good luck!), or call through and let Wine handle the messy bits.

      Either way is sub-optimal, but at least using Wine is realistic!

    17. Re:GTK is out, then? by Krondor · · Score: 2, Informative

      What about that Ximian purchase? I guess it was just for Mono.

      The Ximian purchase was for a number of reasons most importantly Mono and Red Carpet. Novell hopes to leverage RedCarpet into Zenworks for Linux. If you aren't familiar with Zenworks you should read up, because that is what will catalyst large scale Enterprise client rollouts (that aren't terminal based).

    18. Re:GTK is out, then? by circusnews · · Score: 2, Interesting

      Miguel,

      I tend to agree that the existing toolkits leave a lot to be desired. But, what I would really like to know is what direction you (and others in the know) see toolkits going in?

      Are we looking more towards things like gnustep or Y Windows?

      Should we be looking to take the best aspects of each of these toolkits and create something new? (and if so, what do you see being included?)

    19. Re:GTK is out, then? by ajs · · Score: 2, Insightful

      Sounds great. Given your track-record, I can't wait to see what you're refering to.

      Gtk+ is a nice toolkit, and had a very novel (Novell? ;-) approach to C programming, but almost all of that has been factored out at this point, and I could certainly see a Gnome/Gtk hybrid library sitting on top of Gdk and Glib that would be far, far better suited to modern development.

    20. Re:GTK is out, then? by dreamchaser · · Score: 2, Interesting

      Gee, that's funny, because according to the Mono project FAQ, GUI.Forms support is indeed being worked on.

    21. Re:GTK is out, then? by wtrmute · · Score: 2, Insightful

      Server-side widgets like Y-Windows means to use are really cool, and if I were given to futurology (I am not) I'd venture that's the direction we should move in... IF we ever got to figure out a natural method for extensibility.

      For now, creating a custom widget would involve ordering a remote y-server to download a module from somewhere (big security no-no) or drawing on top of canvas (which is what we have today with X, really). I'll be watching whatever comes out of there with interest.

    22. Re:GTK is out, then? by davidle · · Score: 2, Informative

      Why, then, is Novell continuing with Evolution and not Kontact? Hmmmm? :-)

      Novell is not continuing with anything at the moment. Besides, Suse hasn't been a part of Novell for long.

      Also, a lot of KDE users use Evolution as well.

      Don't know where you get that idea. I certainly don't.

      Take a look at the design of each, Evolution's is superior (well, except in the case of imap - they both suck there, but I've noticed just today that there is an all new IMAP implementation in the Evolution source tree in CVS which looks to be _really_ good).

      I have. Kontact is nice and modular, meaning you can embed its components in other things. Besides, it depends on what you're looking for.

      I've also looked at KMail sources as I'm overall a KDE fan and was the first mailer I had thoughts about contributing to but their codebase is a complete mess.

      Your opinion. I could say that no one in their right mind develops object-oriented GUI applications in C.

      Evolution has at its core (asked on irc once) around 10 developers total, including GtkHTML development and QA. Kmail (which is only *part* of the KDE PIM suite) has approximately 50 developers (according to their website - kmail.kde.org)

      Mmm, nice try. There are a core of developers paid to work on Evolution, and then there are numerous contributors. It is, afterall, a Ximian product. With KMail I expect you are looking at the authors page and every person who ever contributed to the project! This doesn't mean that they are still involved and it certainly doesn't mean that they are paid to work on it. Besides, I'm not talking about KMail.

      Lets assume for the sake of argument that the contacts portion of the KDE PIM suite is only 1 developer and that there is only 1 developer on the KDE PIM Calendaring component. That's still 40+ developers more than the Evolution team, which, until recently, had almost no outside contributors (even if you add up all the contributors and count them as Evolution developers, you'd still have a far smaller count than 50).

      See above. Besides, you're saying that if KDE PIM has one developer then that is 40+ more than Evolution. So Evolution has -39- developers does it?

      Oh, and KMail at the very least has been in development for a number of years longer (ie. at least 2+ years).

      I'm actually talking about Kontact here, which is something I can actually compare to Evolution. Kontact as a whole has been around for less than two years.

    23. Re:GTK is out, then? by fejjie · · Score: 2, Informative

      Actually, AC is correct - Novell *is* continuing with Evolution development. Being that I'm an Evolution developer, I think that puts me in the know.

      We've also been busy extending GroupWise's protocol so that Evolution can talk to it for remote Calendaring (and Contacts too I think?).

      This will all be available with Evolution 2.0 and the next release of GroupWise (6.5. something er other).

      There are also plans to integrate iFolder as an Evolution backend for Contacts.

      -- fejj

  3. Re:QT? What about licensing? by Anonymous Coward · · Score: 5, Funny

    You mean the GPL?

  4. Re:QT? What about licensing? by FooAtWFU · · Score: 3, Insightful
    I'm pretty sure you can use QT with all your GPL stuff all you want. If you want to do commercial work, on the other hand, yeah.

    But I am *not* a license expert. This is pure hearsay.

    --
    The World Wide Web is dying. Soon, we shall have only the Internet.
  5. Boy. by Anonymous Coward · · Score: 5, Funny

    The prospect of using Mono to code against Qt makes me drool in advance.

    Boy, you really need to get out more.

    1. Re:Boy. by Chuck+Bucket · · Score: 5, Funny

      Boy, you really need to get out more.

      you must be new here.

    2. Re:Boy. by sosume · · Score: 2, Interesting

      Actually, this may be the event I was waiting for to start writing X desktop apps instead of Windows. Mono is very very powerful and combined with Qt its even better. Who'd have thought that .NET could actually lead developers away from Microsoft..

    3. Re:Boy. by alext · · Score: 4, Funny

      Who'd have thought that .NET could actually lead developers away from Microsoft[?]

      You and Miguel?

    4. Re:Boy. by S.Lemmon · · Score: 5, Interesting

      Heh heh... Even now I can picture Balmer rubbing his fat little hands together and giggling gleefully. Micorsoft's fondest hope is that a good chunk of open source software will come to depend on mono before they play the patent card. Assurances that Microsoft would "just never do such a thing", somehow leave me unconvinced. ...and I'm sure someone will tempted to respond with the "but, but C# is a standard!" line too - don't bother, just submitting the "standard" in no way prevents Microsoft from enforcing related patents anytime they choose.

      Regardless of NET's good or bad points, it's a potential legal land mine for open source that could make the SCO fiasco look postiviely quaint. Unlike SCO, Microsoft would have an actual case.

  6. Re:QT? What about licensing? by nurb432 · · Score: 4, Insightful

    Not anymore, most of them have been resolved some time ago.

    Besides, whats wrong with software you have to pay for?

    --
    ---- Booth was a patriot ----
  7. Re:QT? What about licensing? by Anonymous Coward · · Score: 5, Informative

    I'm pretty sure you can use QT with all your GPL stuff all you want.

    Given that Qt is available under the GPL itself, it's an absolute certainty you can use Qt in a GPLed project.

  8. How Much to dev with? by DAldredge · · Score: 4, Informative

    How much will it cost to use QT to write business apps?

    From the trolltech site: http://www.trolltech.com/products/qt/licensing.htm l

    " Use the Qt Commercial License to:
    Build commercial software.
    Build software that is not sold, but that advances the business goals of a commercial enterprise."

    1. Re:How Much to dev with? by kensai · · Score: 2, Informative

      IIRC, it's $1000/seat.

    2. Re:How Much to dev with? by MAXOMENOS · · Score: 4, Informative
      Qt is released under GPL, and so Novell has every right to sell the desktop. Of course, everyone who purchases the software also has their GPL rights.

      Persons who develop GPL-incompatible software for the new desktop will probably have to GPL their code or purchase both a Qt license and a separate Novell license. Not cheap, but other than that, definitely fun.

    3. Re:How Much to dev with? by Otter · · Score: 3, Informative

      You're assuming wrong. This has to do with QT development -- ie, you can't develop proprietary internal apps with the free Qt version. As opposed to the GPL which only deals with release. (Apple has similar restraints on using modified Darwin internally.)

    4. Re:How Much to dev with? by Frequanaut · · Score: 3, Informative

      From their website

      (Either Qt/Windows or Qt/X11 or Qt/Mac)
      Prices per developer. Includes one year of support and maintenance. See also the Professional/Enterprise Comparison Chart
      Developers Professional Edition Enterprise Edition
      1 $ 1550,- $ 2490,-
      2 - 5 $ 1500,- $ 2250,-
      6 - 10 $ 1410,- $ 2120,-
      11 - 20 $ 1330,- $ 2000,-

      Which sort of sucks, because it sounds like I buy a license to develop under X and then need another to debug the problems that crop up under win32.

      It's not a lot of cash, but it's sort of tough to compete with a robust, free product.(i.e. GTK)

    5. Re:How Much to dev with? by lavalyn · · Score: 3, Informative

      It costs nothing to use Qt to build software that advances the business goals of a commercial enterprise, so long as it is not distributed outside the enterprise. Liken it to the GPL restriction: if you are bound by both the GPL and another license (say a proprietary development framework) the only distribution option is to not distribute at all.

      --
      Doing the Right Thing should not be preempted by making a buck.
    6. Re:How Much to dev with? by RevAaron · · Score: 3, Informative

      ie, you can't develop proprietary internal apps with the free Qt version. As opposed to the GPL which only deals with release

      Sure you can. The GPL does not require that you *RELEASE* your software to the rest of the world. This would work quite well, if your users were mostly ignorant, and didn't go on demanding the source and sharing with the outside world. But for most internal business users, they wouldn't care less.

      However, you cannot use the free Qt version to create software that you intend to keep closed- whether you're giving it away as freeware or if you're selling it. Or, if you want to use a license other than the GPL- for example, the LGPL, BSD or MIT. For that you need the commercial license.

      --

      Working toward a usable PDA environment in the spirit of Newton OS: Dynapad
    7. Re:How Much to dev with? by Richard_at_work · · Score: 2, Insightful

      Seriously, under what licensing stipulations can they force you to pay for a license if you are using the GPLed version of QT, internal or otherwise, and you comply with the GPL 100%? As far as im aware, they cant stop you using the GPL version for internal products, as wouldnt that restriction itself be a breach of the GPL? Note that if the company is using it internally, it doesnt have to provide the source to the end users, as they are deemed to be part of the company and therefor the company is distributing to itself.

    8. Re:How Much to dev with? by slamb · · Score: 4, Informative
      Lumpy wrote: in other words, every company out there that uses KDE legally needs to buy a QT license???

      Otter replied: You're assuming wrong. This has to do with QT development -- ie, you can't develop proprietary internal apps with the free Qt version. As opposed to the GPL which only deals with release. (Apple has similar restraints on using modified Darwin internally.)

      I don't think that's right either. Qt is available under two licenses:

      • the GPL. (Qt/X11 only.)
      • a more permissive licenses that costs $$$ per developer. (All Qt versions.)

      ...and the big thing with the GPL is that you application can only be distributed under its terms if it's based on any GPL software (including Qt/X11).

      That's not a problem with internal applications. They're not distributed at all. Thus, you can develop internal apps against the GPLed Qt/X11. No money required.

      Where you do need to buy a license is if you are doing any of these things:

      • distributing a Qt-based application without source code. (violates the GPL)
      • distributing a Qt-based application without allowing your users to redistribute it. (violates the GPL)
      • distributing a Qt-based application there are patents on, unless your users are unconditionally granted usage without charge. (violates the GPL)
      • developing an application against Qt/Windows, Qt/Mac, or Qt/Embedded. (Even if you're not distributing it.) (These versions are not available under the GPL at all.)

      Of course, you should read the GPL yourself, where the terms are stated much more precisely.

    9. Re:How Much to dev with? by r00zky · · Score: 3, Informative

      developing an application against Qt/Windows, Qt/Mac, or Qt/Embedded. (Even if you're not distributing it.) (These versions are not available under the GPL at all.)

      a correction:
      Qt/Mac and Qt/Embedded are available under the GPL:
      http://www.trolltech.com/download/index.html

      It seems it's just the Winblows version which isn't GPL'd

      --
      I'm a chainsmokin' alcoholic sociopath, so-ci-o-path
    10. Re:How Much to dev with? by Brandybuck · · Score: 3, Insightful

      If you're going to write software either write it as a hobby and make it free-beer, or go whole hog and be a real professional. Shareware is facing the end of its existance. Once Free Software catches on in the Windows world, shareware is dead.

      --
      Don't blame me, I didn't vote for either of them!
    11. Re:How Much to dev with? by hey! · · Score: 2, Informative

      You are right -- if you are developing on and deploying to X11 and using the GPL version.

      The issue is that there is no GPL version from Trolltech that you can use and deploy to Windows even internally.

      If you have to deploy to Windows, internally or not, you have to fork over major dough to Trolltech. I think this is a major obstacle to even evaluating Qt for many IT organizations, because they rely upon pilot projects to prove a technology's value.

      Qt really needs one more license in its arsenal: a per deployment commercial license. This would allow people who have to target windows to conduct pilot projects affordably before they decide to "drink the kool aid". Something like $50-100 per runtime user, nothing per developer, ability to distribute under standard commercial license later provided each developer is bought a seat.

      That way people who want to develop in the open source world can create GPL software for open source operating systems. People who need to operate in the commercial software world could affordably test the waters, and once the value of the system was proven they would be incented to buy the commercial license. Granted they'd lose a few commercial licenses in shops that don't like the software, but this would be offset by many more shops adopting the software, and paying a number of per user seat licenses before going for the developer seat.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  9. Programming by Bingo+Foo · · Score: 5, Funny
    Maybe programming will suck no longer!

    Hey, if programming were easy, people would do it for free.

    --
    taken! (by Davidleeroth) Thanks Bingo Foo!
    1. Re:Programming by davecb · · Score: 4, Funny
      I think mixing C, C, ++, GTK and QT should make programming much more fun, by making it almost totally impossible (;-))

      --dave

      --
      davecb@spamcop.net
    2. Re:Programming by thames · · Score: 4, Insightful

      Hey, if programming were easy, people would do it for free.

      I don't see why this is funny. It is clear that if programming were easy then people would do it for free (like everything else that is easy). On the other hand it dosen't mean that because people program for free, that programming is easy (it's not!). That's why we should all celebrate all those programmers that program for free and share their work with the rest of the world!.

  10. Re:QT? What about licensing? by Anonymous Coward · · Score: 5, Informative

    No. Qt hasn't had annoying license restrictions in years, as it was released under the GPL four years ago, allowing for such projects as a GPL'd Qt3/Win32.

    Somehow, this is still news to people...

  11. Makes sense for desktop interop by IGnatius+T+Foobar · · Score: 4, Insightful

    This does make a lot of sense, actually. And it might actually be early enough in the game for it to work.

    Right now, there is still the opportunity to attract developers to cross-platform .NET API's. .NET might, in fact, actually be the fastest route there (aside from Java, which I think people ought to be using for this purpose, but let's set that aside for a moment). Perhaps if, boosted by a Novell push, developers begin writing and publishing .NET code that uses Qt libraries, there will be that many more cross-platform desktop apps available that won't be bound to Windows.Forms, Avalon, or whatever other Windows-bound API's Microsoft wants everyone to use.

    It would be a double-bonus if Novell could make Mono a unified framework for writing apps that can be backended by KDE, GNOME, or Microsoft Windows without a rewrite. Let's see what happens. What's really a shame is that .NET is, on its face, a good design, but that we have to worry about Microsoft using it as a cudgel to beat back its competition.

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
  12. Discussions elsewhere say this article is invalid. by Rahga · · Score: 4, Informative

    It's a bit odd that this article wasn't posted to /. sooner, as most people first noticed it when it made osnews almost a week ago.

    Many BrainShare attendees have already dismissed this as a badly written article, as it combines statements from Novell about their desire to see a unified Linux desktop (see one of the worst examples of tech reporting in years) with rumors and rampant speculation. There is no basis of truth in the heise article.

    I'm sure Novell will send out someone with authority in due time to stomp this out, but this is just what I've heard so far.

  13. Re:QT? What about licensing? by Anonymous Coward · · Score: 3, Insightful


    Besides, whats wrong with software you have to pay for?
    .

    Inappropriate for basic foundations of Linux software.

  14. Re:QT? What about licensing? by Frymaster · · Score: 3, Interesting
    Besides, whats wrong with software you have to pay for?

    the most obvious is that it is a barrier to adoption. if your model is to sell software and make yr money that way, everything's fine... but if you're model is have free wares to drive sales of other commodities (hardware, support, data &c) then the extra pricetag on the software can tank your business.

    since you asked....

  15. HEISE confirms by Anonymous Coward · · Score: 2, Informative

    The german newsmagazine HEISE a very popular and creditible organisation was reporting about that as well. As they got told from first hand QT/KDE is doing the run.

    You can read more here on their site.

  16. So this means C# is bring embraced? by Offwhite98 · · Score: 3, Insightful

    The old Microsoft approach is to Embrace an Extend. I often hear people say that Mono is going to die because MS has the staff to write more and more APIs and Mono will not be able to keep up. But my thoughts are that Mono and other Open Source projects should be able to implement some impressive and highly usable C# and .NET implementations completely independent of MS influence and support. Essentially the community will have the ability to Embrace and Extend a MS created technology with just the ECMA standard C# and CLI recommendation.

    I have been impressed with the CLI implementation and the SOAP and Web Services technologies that are a part of the .NET framework are very robust when compared to traditional network communications such as CGI or OLE. It is clearly an ideal glue language for a diverse Linux desktop which often mixes many programming and scripting languages together.

    --
    Brennan Stehling - http://brennan.offwhite.net/blog/
  17. As a new Qt programmer... by scorp1us · · Score: 5, Interesting

    I can say that there is nothing easier outside of web development. I am an old MFC programmer. I am often lost in developing Qt apps, but I am very comforatable with that because the documentation is copius cnad clear. Whats more is it is soooooooo well thought out. It makes MFC look like the crap that it is (C++ wrappers for C objects). Learning Qt is like learning to walk the right way. It's amazingly simple. I will always request that Qt be used regardless of platform in future jobs.

    Now the license is different. I often wish there was a small-business or starting-business license, but this is only pertanant if you are going commercial work. for GPL work it is completely free.

    Right now I'm doing some advanced work with QSA (Javascripted Qt apps) It is easy and cross platform. I can now replace a browser (and the rendering issues with a user interface file (loaded at run-time) and ECMA script code (platform indep. cause we run on various architectures with limited space, whose list may change at any time)

    The Troll Tech stuff is top notch.

    --
    Slashdot's rate-of-post filter: Preventing you from posting too many great ideas at once.
  18. Re:QT? What about licensing? by Anonymous Coward · · Score: 2, Informative
    "Doesn't QT have a bunch of annoying licensing restrictions?"
    It seems Novell does not think the same as Bruce Perens
  19. mono and linux is a wonderful combination by Christopher+Anthony · · Score: 2, Informative

    The combination of Mono with Qt and Linux is great. The Open Source nature of these applications means that they are virtually bug free. I am glad to see that Novell is in top form once more, supporting Linux. I have used Mono extensively and it really is great. It is not proprietary like Java, and it is a wonderful tool to use. Mono is the programming platform that will put Microsoft to rest once and for all!

  20. Redhat got it right by OmniVector · · Score: 3, Interesting

    I'm surprised redhat has stuck with gnome this long as their DE of choice. It is more usable, and that's why I am glad personally they have.

    With so many of the gtk programs riviling the qt equivalents, I wonder why companies always flock towards Qt.

    --
    - tristan
    1. Re:Redhat got it right by Anonymous Coward · · Score: 3, Interesting

      Because due to the plain well organized OO API coded in an OO language Qt is very easy to code in.

      The bindings are no problem as well, there are bindings for most of the commonly used OO languages including excellent ones for java.

      It is a matter of time, I think a license for Qt is well invested given that the license costs itself probably are gathered in within weeks due to the speed you can code the thing in.

      The problem with Qt is, that the current license costs basically locks out single developers who dont want to go the GPL route. I know at least two excellent shareware projects which didnt use Qt for exactly that reason.

      TrollTech should offer a small developers license which would be affordable by individuals.

    2. Re:Redhat got it right by Drinian · · Score: 2

      With so many of the gtk programs riviling the qt equivalents, I wonder why companies always flock towards Qt.

      Because QT is solid, elegant and well supported. It makes coding in C++ trivial, which means time saved, which means money saved, and that's what companies think about. People seem to appreciate the gtk look and feel over QT, but for a framework QT is awesome.

    3. Re:Redhat got it right by Wylfing · · Score: 5, Insightful
      The problem with Qt is, that the current license costs basically locks out single developers who dont want to go the GPL route.

      I was going to moderate, but this is driving me insane. There are just too many posts like this. How is $1000 "locking out" single developers who intend to sell closed-source licenses? Even for sole proprietorships $1K is nothing special. Besides, you are talking about selling closed-source software, which by definition requires other people to pay you money per license, but somehow you think TrollTech is a fiend for wanting to do the same thing. If you want to be open, TrollTech is right there with you.

      --
      Our intelligent designer has never created an animal that we couldn't improve by strapping a bomb to it.
  21. Re:QT? What about licensing? by slipstick · · Score: 5, Insightful

    Hmm. I hope you mean free as in speech not as in beer because otherwise that's not much of an argument.

    The point of "free" software is that it is open for perusal, poking, sharing, etc. not that it's gratis so you don't have to pay for it. Granted because of the first the gratis part is often the case but the mentality that free speech software MUST mean free beer software is just wrong.

    --
    Sure information wants to be free, but how much are you willing to pay for the packaging?
  22. $0.00 by FreeLinux · · Score: 5, Informative

    It costs nothing to develop business applications qith the QT toolkit. The only requirement is that if you use the $0.00 license(GPL) the app must be GPL. It really isn't much to ask.

    The fact that Novell is going to use QT is very telling. Novell is a software corporation whose existence past, present and future relies on selling software. That means that while they will throw the open source community a GPLed bone (Yast, Evolution) they will also offer up lots of closed source applications and some will be QT based.

    Novell is not afraid of having to pay a very reasonable licensing cost for commercial development and neither are most other software companies. They already pay licensing for MS Visual DEs, Borland DEs and probably many others. Paying for a QT license is a minor cost of doing business and it will not deter any serious software house.

    1. Re:$0.00 by be-fan · · Score: 2, Interesting

      Because Qt is a better, faster, and more well-documented toolkit than GTK+? Its got many more commercial users (including a lot of big-name companies) and a dedicated team of full-time developers.

      --
      A deep unwavering belief is a sure sign you're missing something...
  23. Re:QT? What about licensing? by Roberto · · Score: 2, Insightful

    > Inappropiate for basic foundations of linux software.

    Says who? Oh, nevermind.

  24. I think by Anonymous Coward · · Score: 3, Insightful

    I think that many commercial development companies would consider the GPL to be "annoying license restrictions" if all they want to do is write a GUI app.

    1. Re:I think by LMCBoy · · Score: 5, Insightful

      Oh, pity the poor proprietary software company! All they ask is that someone give them a first-class GUI toolkit at no cost, and with no strings attached! Is that so much to ask?

      Please. Cry me a river. Trolltech spent a huge investment on making Qt the best cross-platform GUI toolkit available anywhere. I think they're decision to provide a GPL'd version was an incredibly noble thing for them to do (althogh in truth, they do get a lot out of it in return, especially through their relationship with KDE). My hat is off to Trolltech.

      Do you not see the hypocrisy in demanding that one software company (TT) must give away its product for free so that other companies can profit from the work? How does that make any kind of sense?

      --
      Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
    2. Re:I think by mcc · · Score: 3, Insightful

      All they ask is that someone give them a first-class GUI toolkit at no cost, and with no strings attached! Is that so much to ask?

      Sounds reasonable to me.

    3. Re:I think by Welsh+Dwarf · · Score: 4, Insightful

      You're not a coder are you? none of your examples are in the same league as Qt, in either speed of developpement, ease of use, documentation or compleatness.

      --
      Ask 8 slackers a question, get 10 awnsers (a citation, but I can't remember from who)
  25. Re:QT? What about licensing? by InfiniteWisdom · · Score: 3, Insightful

    Besides, whats wrong with software you have to pay for?
    Nothing if you aren't using it as a core library for a free desktop system

  26. This is good news by jared_hanson · · Score: 5, Interesting

    I personally have been hoping for a while now something like this would happen for the Linux desktop. It's going to take a corporation to step up and unify this effort in order to gain mass acceptance. I'm sure there will be some grumbling in the community, but open source is open so feel free to customize to your hearts content if you don't like it. Most people don't want to have to go to this effor though.

    The only potential problem I see is Trolltech's insistance on license fees for commercial development. Not that this is any different in the Windows world, but it'd be nice to give ISVs a completely royalty free solution. I'd like to see Novell take that $50 million that IBM gave them and purchase TT outright and put Qt under a more liberal open license. The wording on the KDE Free Qt clause seems a bit unclear to me. Does Qt get automatically BSD'ed when any company buys Trolltech. What if the purchasing company doesn't make the license any more closed that currently, does that have an effect.

    Anyway, I've never understood the reasons people chose to write a whole desktop environment in straight C. C++ just seems a far more natural fit. I've looked over both GNOME and KDE fairly extensively, and there is no doubt in my mind that KDE has a cleaner code base and architecture. With all the "higher level language" rumblings going on in the GNOME community, I suspect that those developers are hitting a brick wall in terms of where they want to go and what the current code is capable of becoming. That sort of thing isn't happening in the KDE world, so I think that speaks volumes.

    Good luck Novell, you've got at least one supporter here.

    --
    -- Fighting mediocrity one bad post at a time.
    1. Re:This is good news by jared_hanson · · Score: 2, Interesting

      It is entirely different in the Windows world. You can use win32, MFC, or .NET without any royalties or super-expensive tools.

      Well, it still costs the company and the consumer, just in different areas. With Trolltech, you pay a per developer license and be done with it. Free to distribute to whoever you want for whatever you want.

      If you develop a Microsoft solution, the the consumer has to pay for Windows licenses and the developer has to pay for Windows licenses and likely Visual Studio licenses as well (though this isn't strictly necessary). If you use one MS product, you likely use others too, so start paying out money for SQL Server, Exchange, and whatever other traps you get yourself into.

      By the way, you are entirely free to develop with Qt without paying any royalties or super-expensive tools as well.

      --
      -- Fighting mediocrity one bad post at a time.
    2. Re:This is good news by justins · · Score: 3, Interesting
      If you develop a Microsoft solution, the the consumer has to pay for Windows licenses and the developer has to pay for Windows licenses and likely Visual Studio licenses as well (though this isn't strictly necessary).

      It's not necessary at all. There are a lot of good free-software development tools for the Windows platform. As for the cost of windows, when you're making a windows app your target audience already has that...

      By the way, you are entirely free to develop with Qt without paying any royalties or super-expensive tools as well.

      "Use the GPL for your project or pay us thousands of dollars" is hardly free. By contrast, in my view GTK+ and wxWidgets are free.
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    3. Re:This is good news by jared_hanson · · Score: 2, Interesting

      It's not necessary at all. There are a lot of good free-software development tools for the Windows platform.

      Every place I've ever seen that does commercial development for Windows uses Visual Studio for development. The only people I've ever seen use the free/open compilers were doing open source work.

      We are just splitting hairs here, but if a company is serious about using open tools to do development work on Windows, they'd be further ahead to pay the reasonable fees to trolltech and could write code to target Linux, Mac OS X, and Windows.

      You may in fact be more free under a license such as the QPL than you would be under LGPL'd GTK and wx. Qt is an extremely high quality toolkit and you are not being forced into anything that you yourself don't choose.

      --
      -- Fighting mediocrity one bad post at a time.
    4. Re:This is good news by justins · · Score: 2, Interesting
      Every place I've ever seen that does commercial development for Windows uses Visual Studio for development.

      Yeah, but they don't have to. And Visual Studio Professional is a lot cheaper per seat than Qt.

      We are just splitting hairs here, but if a company is serious about using open tools to do development work on Windows, they'd be further ahead to pay the reasonable fees to trolltech and could write code to target Linux, Mac OS X, and Windows.

      Only if they need something that Qt offers but the other, genuinely free, toolkits do not offer. I don't concede that the fees are "reasonable," though.

      You may in fact be more free under a license such as the QPL than you would be under LGPL'd GTK and wx.

      How is "free to GPL your program or pay huge per-seat developer fees, your choice" any freer than "free to do whatever you want"?
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
  27. Re:Give me a break! by squarooticus · · Score: 2, Informative

    > That is the same as GTK,

    False. GTK is licensed under LGPL, which is far less restrictive. Do some research before you spout this drivel.

    --
    [ home ]
  28. God Dammit!!! by AyeRoxor! · · Score: 3, Funny

    I hate QUICKTIME!!! /should I rtfa?

  29. Re:About time by Saven+Marek · · Score: 2, Interesting

    This is what good widespread systems need, and it's understandable that Novell is aiming for consistency.

    In the whole world of UI/Desktop use, choice is a good thing. It means complete customisation control from one purpose such as industrial process control, to corporate desktop, to games system (humor me and look to the future when this is the case with Linux. It will happen eventually). However for Novell who will be supporting a system, and selling it as a solution for businesses, then there needs to be stability, if not from a support point of view then for a User point of view.

    Users don't care, and shouldn't, about the technicalities of their tools, and that's what support is for. Only when they have a well constructed and supported toolset (their desktop in this case) can they perform with 100% concentration on their REAL job be it marketing, secretarial, analysis and so on

    Acker's Nude & Anime Desktop Gallery

  30. Re:QT? What about licensing? by Erik+Hensema · · Score: 3, Informative

    It seems to be confusing that one can buy a commercial version of Qt. That version however is extra. If you don't want it, just stick to plain old GPL'ed Qt.

    MySQL is doing something similar. Nobody seems to be confused by that one though.

    --

    This is your sig. There are thousands more, but this one is yours.

  31. QT vs. GTK by Anonymous Coward · · Score: 2, Informative

    What about wxwidgets (the GUI development library formerly known as WxWindows? Sounds like a safe compromise with strong portablility and no licensing hassles.

  32. Wait a sec... by daniel+borgmann · · Score: 3, Interesting

    The only source of this so far has been Heise. In their original article, they word this quite unclear (I'm german) basically just mentioning that this information "slipped through during the day", without any source or confirmation.
    However, derStandard.at asked for confirmation at Novell and they assured that no decision would have been fallen yet.
    They (Novell) also demoed quite a few new Gtk applications at the keynotes, most notably the interesting iFolders (using Gtk on Linux), while I don't think there has been shown any _new_ Qt program.

    So take this all with a grain of salt, I can't really imagine that this is a clear decision yet.

  33. If only by Anonymous Coward · · Score: 3, Funny

    If only Sun had embraced Open Source the way Microsoft did, maybe Java/Swing would find itself beginning to be the consensus cross-platform GUI development platform instead of Mono... pity

  34. C++ and binary compatibility by 11223 · · Score: 2, Insightful

    Why, oh why, did they choose a C++ toolkit? Issues of gcc binary compatibility aside, C++ suffers from the Fragile Base Class (FBC) problem, where adding new instance variables to base classes can break binary compatibility for every derived class. This is why QT has broken binary compatibility twice already in the past. C structures suffer from this same problem, but Mono classes, Objective C classes, et al do not.

    I still don't understand the popularity of QT. It's as if people don't want linux to be taken seriously as a deployment platform. Why target a host that won't run your binaries next year?

    1. Re:C++ and binary compatibility by SQLz · · Score: 2, Informative

      They chose it because C++ is basically the standard for GUI development. Programmers who do a lot of work with MFC will find the transition to QT easier and there is also the STL. So, to me, the choice of a C++ toolkit seems obvious and is probably the only reason QT was chosen.

    2. Re:C++ and binary compatibility by be-fan · · Score: 2, Informative

      GCC has had a stable binary C++ ABI for awhile now. In fact, its the same stable binary C++ ABI Intel C++ uses. So the ABI bit is an old argument. While C++ suffers from the FBC problem, Trolltech is careful about hitting that problem in Qt. Thus, Qt has remained binary compatible throughout the whole 3.x series, which is nearly three years old at this point.

      --
      A deep unwavering belief is a sure sign you're missing something...
  35. Re:QT? What about licensing? by Chess_the_cat · · Score: 2, Interesting
    the most obvious is that it is a barrier to adoption

    Linux has been free for years and yet only accounts for 5% of the desktop max. So what is the real barrier to people adopting Linux then?

    --
    Support the First Amendment. Read at -1
  36. there's nothing wrong with keeping them separate by Stevyn · · Score: 4, Insightful

    keeping kde and gnome separate for a little while longer, or possibly forever, might be a good plan. There's one catch though, they need to be completely interoperable. I want to be able to install the same program on both desktops and have it work seamlessly. I also want an icon put on the desktop or the taskbar menus. Is this possible? I don't have the expertise but I'm sure it can be done if these programs are on top of a standard api.

    Why do I think this is a good idea? Keeping them separate but equal promotes competition between them. It makes them work harder to fix those little glitches that annoy users. KDE is looking kind of like windows xp, and gnome mac os X. It'd be nice if they took on more of an original look, but hey rome wasn't built in a day. I think that having the choice between both desktops knowing that most applications will work the same without needing a hundred different rpms for each thing is what's needed. I also think that libraries need to be consolidated. Basically I guess I'm saying this: the ease of installing programs on windows, but the ability to run them on a mac. Sound difficult? eh, look how far things have come.

  37. Setting the record straight. by Nat+Friedman · · Score: 5, Informative


    We're not really sure where the rumor came from that Novell is standardizing on Qt as its desktop platform. Chris Stone said no such thing during his keynote; the video for the keynote is available here:

    http://www.novell.com/brainshare/keynotes2004.ht ml

    Novell supports GNOME and KDE, Qt and Gtk. We have not decided that we are standardizing on Qt for the desktop. First of all, most software developed for the Linux desktop is developed by the broader community, and Novell could never impose a standard platform on the community at large. We support development with a variety of toolkits, and our internal development is done using the right tool for the right problem. This includes Qt, Gtk, VCL, XUL and others, depending on the application.

    We do not regard the variety of toolkits and platforms in the Linux world as a problem, as long as there are standards and shared code which allow applications to work together.

    And frankly, today's Linux toolkits and platforms are one of the least interesting topics on the Linux desktop today. The important issues for this industry and market are our opportunity to innovate in information management and collaboration, improving interoperability with Windows users and services, bringing more ISVs and developers to the Linux platform, enhancing the usability and consistency of the various components that make up the desktop, enabling Windows migration with tools and training and documentation, and creating a manageable Linux desktop to enable large-scale deployments.

    We see freedesktop.org as one of the most important and central elements of the Linux desktop for the next several years. The desktop today is made up of a number of components, including OpenOffice, Mozilla, Evolution, and of course GNOME and KDE. Over time we hope to work with freedesktop.org to unify the key interfaces and functionality of these components, to improve integration for users and provide a common open
    source desktop platform.

    Nat Friedman
    Novell/SUSE Linux Desktop Lead

    1. Re:Setting the record straight. by Anonymous Coward · · Score: 4, Interesting

      Apparently Chris Stone said it in the press gaggle following the talk.

      I see you are *still* presenting yourself as the desktop lead, Nat. Interesting since from all accounts, Chris Stone occupies that position.

      Why don't you set the record straight as to the organizational heirarchy of the company and where you and Miguel sit in the organizational tree? Do you answer to Chris Stone or Richard Seibt or do they answer to you? Or are you all just a bunch of middle management?

    2. Re:Setting the record straight. by logical1010 · · Score: 2, Informative

      It seems this /. article is based on an anonymous post to newsforge, which in turn is based on a german news article tranlated to english.

      No wonder he's misquoted.
      --
      There is something wonderful in seeing a wrong-headed majority assailed by truth. ~John Kenneth Galbraith
    3. Re:Setting the record straight. by Anonymous Coward · · Score: 2, Interesting

      I see you are *still* presenting yourself as the desktop lead, Nat. Interesting since from all accounts, Chris Stone occupies that position.

      From the Novell web site I would have guessed that it is Markus Rex:
      "He is also responsible for Novell's Linux desktop activities."

    4. Re:Setting the record straight. by Rich · · Score: 2, Troll

      Nat Friedman
      Novell/SUSE Linux Desktop Lead

      Erm, last I read that was VP of 'Novell Ximian Services'.

      I'm sorry Nat, but while I don't know if this story is true or not, I don't think a comment from you is likely to help. You said a lot when the SuSE Novell merger started which turned out to be rubbish so how can anyone trust you to do more than push your own position now?

      Rich.

    5. Re:Setting the record straight. by ainsoph · · Score: 4, Funny

      The only way for Linux to succeed is to mimic MS's API's.

      To that, we must throw out everything and clone Longhorn.

      This is so beneficial I cant believe its not obvious to everyone.

    6. Re:Setting the record straight. by Anonymous Coward · · Score: 2, Insightful

      Maybe that was his title before the acquisition?

      Funny, at Novell Brainshare, Nat did the Novell Linux Desktop presentation (which was XD2 for the
      most part), including Novell's iFolder/Simias, ZenWorks.

      de Icaza finished with the Mono and Gtk platform demostrations.

      People have to resort to personal attacks to appease their own fears, you my friend are a
      fearful person.

    7. Re:Setting the record straight. by iwbcman · · Score: 2, Insightful

      I am glad that Nat and Miguel finally spoke out. Heise, the oh-so respectd german IT publication, either knowingly or unknowingly allowed itself to be used in a rumor/speculation propaganda war-a power push from A group of hackers within Novell against another group of hackers within Novell to force some big "decision", which when the Novell execs, who are new to Linux and are prone to make such noobie mistakes, start thinking clearly again isn't even a question.

      The depths of ridiculousness which comments here at slashdot have reached are mindboggling. People attacking Nat and Miguel, questioning their position, their right to speak as representatives of Novell...utterly assinine. The whole "QT is not free (enough)" stuff is also pretty braindead-if this were the case(already) KDE would not be so widely used.

      Freedesktop.org is the organization which *is* the answer to the common desktop which Novell exec's are looking for. KDE developers and GNOME developers are already working together on a variety of projects-this will only increase with time. There is far more consistency across the GNOME/KDE divide today than ever before- even SuSE used a cvs-patched version of KDE in 9.0 so that KDE and GNOME used the same .desktop files. Gstreamer is already being integrated into kdemultimedia, sodipodi is integrating optional KDE-dialogs, both KDE and GNOME have adopted DBUS-GNOME is going to use cairo for 2.8, KDE/QT won't be far behind.

      SuSE has a whole lot of expertise in kernel and XFree86 hacking-their enterprise offerings, based on cooperation with IBM makes SuSE from the server point of view invalualble. For many home users SuSE has been known as a good desktop distribution- but SuSE has not made any big splash on the desktop in the corporate world. Novell purchased SuSE primarily due to the SuSE-IBM connection and the quality of their programmers.

      In Europe SuSE reigns uncontested as *the* Linux distribution-but yet again, more so because of SuSE as a server than as a desktop-corporations are only now beginning to show an interest in the Linux desktop.

      Ximian is all about the desktop and all about integrating/migrating Windows data, applications, users and developers into the Linux world. Why is it that none of computers at the brainshare conference were running KDE -but all of them were running ximian-patched GNOME ? Why is it that Ximian is an unknown name to those who work primarily in the server world?

      Novell has made a brilliant decision purchasing both Ximian and SuSE. They, Novell, have great kernel hackers, xfree86 hackers, desktop specialists par excellance-the best in the Linux world and the developers of one of the most trusted names in enterprise server Linux in addition to great QT/KDE programmers.

      Novell will itself onl be producing a very small set of software-perhaps in total in 5 years 1/2 of one of the 6 CD 's ditributed in the Novell/SuSE distribution. Even if at some point down the road Novell chose to use QT# for it's development projects-who really cares ? QT# is dependendant upon MONO-and that is one of the key technologies which Ximian brings to the table.

      Novell is not going to single handely re-write the Linux desktop with QT-such is pure and utter nonsense-as if any singly company could do so-hello- Linux consists of thousands of programs written by 10's of thousands of hackers from all over the globe.

      For the near future the desktop applications released by Novell will be written in Mono + GTK#-this is already clear-the iFolders software is already being written in GTK# and it is not the only GTK# project being written right now, as we speak, at Novell. Once the QT# library get's up to speed their will probably be some desktop apps written to use this new library-think integration with YAST-appending new modules to administer the OpenSever technology which Novell wants to integrate with their Novel/SuSE distribution.

      If and when Novell's customers start to want to build new application

  38. Re:Give me a break! by LMCBoy · · Score: 3, Informative

    That's bullshit.

    The first correct statement in your post. Nothing stops your customers from using Qt to develop software, as long as the software is either GPL'd or for internal use only. If your customer wants to develop proprietary software to distribute for profit, perhaps you can do them a favor and recommend Windows, since windows users are more likely to buy into (literally) the proprietary software model.

    --
    Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
  39. Complete Bullshit by sn0wman3030 · · Score: 5, Informative

    Bullshit. I've watched that keynote from Novell's website. (and you can too) All he said is that SuSE 9.1 will be getting a QT-based Openoffice. THAT IS ALL. nothing more. The journalist completely missinterpreted this, saying that SuSE is going to standardize on QT. It's all a missunderstanding.

    --
    Life is offtopic.
  40. Re:more "Utah software" ? by scorp1us · · Score: 3, Interesting

    Give it up man. Everytime I see Qt mentioned, someone posts this FUD. Yeap, you're uding your own FUD against Linux.

    I'll admit it, the first time I read this conspiracy thoery I was worried. I looked into it. Trust me there are no black helicopters being dispatched from SCO.

    KDE Myths #60: http://kdemyths.urbanlizard.com/viewMyth.php?mythI D=60
    "According to http://www.trolltech.com/newsroom/investors.html the Canopy Group only has 5.7% shares of Trolltech while 64.7% are in posession of Trolltech employees with an additional 5% controlled by the Trolltech founders. One can hardly say that the Canopy Group owns or controls Trolltech."

    Don't forget Canopy is just an investent group. They'd probably like to see TrollTech get this boost because SCO is a loss at the moment, and they aren't going to get better.

    It is like saying that you own a mutual fun that invests in two competitors, and that you are going to devalue one so the other can rise. The problem is that you want BOTH to perform.

    --
    Slashdot's rate-of-post filter: Preventing you from posting too many great ideas at once.
  41. Novell made the right choice by niom · · Score: 3, Insightful

    Novell is trying to create a professional desktop environment for Linux. To this end, choosing the highest quality toolkit is much more important than having to pay a small fee for the development of non-GPL applications.

    Gtk's licensing only has an advantage over Qt's for those shops that want to create commercial non-GPL applications yet are too small to afford Qt's relatively cheap license. Novell have obviously decided that those shops aren't such an important market to sway their choice.

    --
    -- Repeat with me: "There is no right to profits".
  42. MOD THIS AS HIGH AS YOU CAN. by The+One+KEA · · Score: 3, Interesting

    Your company's stance on the GUI toolkits available for Linux is a good one, and makes a lot of sense - as you said, Novell should not standardise on one particular toolkit.

    So how could the keynote speech have been misconstrued?

    --
    SCREW THE ADS! http://adblock.mozdev.org/ Proud user of teh Fox of Fire - Registered Linux User #289618
  43. Redhat got it wrong by BiggsTheCat · · Score: 3, Flamebait

    I find that Gnome's apps are far more primitive than KDE's, and behind the times. Let's take a look at your examples:

    The Gimp: Well, it uses Gtk+, but it isn't officially a part of the Gnome platform, is it? It doesn't use too many other Gnome libraries. I don't really count it as a Gnome app. And, er, why was it in development for three frickin' years to get to 2.0?

    Gaim: Yes, Gaim is very good, but you should see the new Kopete messenger in KDE 3.2. Very slick, supports MSN, Yahoo, AIM, ICQ, and IRC, with a plugin interface, XSLT to generate the chat windows, etc. etc. It's at least comparable to Gaim.

    Rhythmbox: Hmm, looks like a pretty nice music player. But have you seen the new JuK in KDE 3.2? Very serviceable, and very solid MP3 player. It even looks similar to Rhythmbox. On the other hand, it lacks net Radio... maybe in the next version?

    Galeon: Umm... Galeon is just a wrapper around Mozilla, the 10-thousand pound gorilla of a web browser. I prefer Konqueror and the KHTML widget. KHTML, though not perfect at CSS, is way faster, and is far easier to embed that Mozilla. It now supports mouse gestures with KHotKeys, and conforms properly to your UI theme.

    And look, I seriously have to point out that Konqueror beats Nautilus. The KIOSlave system means drag-and-drop "just works" across many protocols (ftp, sftp, fish, audiocd ripping, http, samba (smb protocol)). I have yet to see Nautilus do anything like this, except with CD Burning (but KDE has K3b, so I don't mind).

    KDE is an extremely capable desktop with many more mature applications than Gnome. Plus, most companies prefer dealing with standard C++ for GUI apps, as opposed to learning some weird custom OO model like glib, even if they have to pay a bit.

    --

    Time is an illusion. Lunchtime doubly so. --Ford Prefect

  44. Re:Give me a break! by 1010011010 · · Score: 2, Informative

    On Windows and Mac there is no cost for a license to use the bult-in widget kit, only for extra tools, like compilers, IDEs, etc.

    On Novell Linux, there will be a cost. So-long, shareware market! Not that there is really a Linux shareware market now, but this would be pretty effective in stopping one from appearing. I also wonder if Trolltech will try to submarine Linux at some point in the future, ala SCO.

    Novell could sell "Novell Developer Studio," which includes KDevelop, QT Designer, etc. plus a QT license. This would make it look like "Windows plus Visual Studio," except more expensive.

    --
    Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
  45. Microsoft's Trump Card? by DroopyStonx · · Score: 3, Interesting

    What are the legal ramifications of using something like Mono? I'm guessing there isn't, as I'm sure Novell would've taken it into consideration any possibility of Microsoft trying to patent .net technology.

    I don't know if it's just heresay, but could MS patent .net and totally screw over any open source projects that use Mono?

    --
    We have secretly replaced these Slashdot mods' sense of humor with a rusty nail. Let's see if they notice!!
  46. Re:QT? What about licensing? by BiggerIsBetter · · Score: 2, Informative

    From the Trolltech website:

    When Qt Free Edition is Open Source and GPL, can I use it to make commercial (proprietary/closed-source) software?

    No.

    You will still need to purchase the Professional or Enterprise Edition to make commercial (proprietary/closed-source) software with Qt.

    Which suggests that I cannot make a GPL'ed commercial application? Perhaps that should be clarified. I also cannot make a GPL'd native (non-Cygwin) Windows application at all. QT is nice to work in, but it's a long way from being truely free software. I guess that theoretically, QT Free could be ported to Windows by a 3rd party, or that you could go to court over commercial GPL'd software, but I doubt it's worth the hassle while there's other free-er alternatives.

    --
    Forget thrust, drag, lift and weight. Airplanes fly because of money.
  47. Re:Give me a break! by LMCBoy · · Score: 2, Insightful

    Except wouldn't the entire point of Novell's current initiative-- the one as part of which they are standardizing on Qt-- to be to open up Linux such that it appeals at least to some extent to persons beyond the rather limited OSS set that uses it now?

    I would hope that Novell will try to do this by bringing those persons into *our* way of doing things, not by trying to change the Linux community into the Windows community. If the latter is their goal (which I seriously doubt), then I say no thanks.

    --
    Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
  48. Re:QT? What about licensing? by unoengborg · · Score: 3, Insightful

    No not really. You can licence it through GPL, if you do open source work, or you can buy licences from Trolltech at a reasonalble price if you want to do closed source work.

    The fact that you have to buy a licence for closed source may be a problem for hobby developers that have more time than money. To companies like Novell the quality is more important than the price . To them, time to market is everything. And they will spend far more money on developer saleries and marketing than they will spend on QT licences. So they will go for the best tool. And QT is one of the best there is. (Cross platform, good development tools, well designed framework...)

    And if they want to release free software they have less risk of being hurt by some competitor if they release it under GPL than under LGPL or BSD type licences. I guess this was the reason MySQL AB changed the licence on their client libs to GPL.

    So, QT would be a very good choise.

    --
    God is REAL! Unless explicitly declared INTEGER
  49. Re:QT? What about licensing? by rsidd · · Score: 4, Informative
    Which suggests that I cannot make a GPL'ed commercial application?

    Where did you read that? It only says you cannot make proprietary/closed-source software with Qt, just as you can't with the GNU Readline library or the GNU Scientific Library or any other GPL'd software.

  50. Re:QT? What about licensing? by Ianoo · · Score: 2, Informative

    Whatever they say in the FAQ is bollocks. They have released their code under the GPL, hence you follow the GPL, not any "extra rules" they've come up with. The GPL says nothing about whether software is "commercial" or "non-commercial", it only states you must make available and distribute the source under the GPL. They've violating their own software license if they try and enforce extra rules (see clause 4). I agree that the Windows think is a big PITA, however IIRC there is a project attempting to write a GPL'd port of QT for Windows.

  51. Re:QT? What about licensing? by GreyPoopon · · Score: 3, Insightful
    Linux has been free for years and yet only accounts for 5% of the desktop max. So what is the real barrier to people adopting Linux then?

    First off, the cost of the software was only listed as a barrier to adoption, not the only one. As for what the additional barriers there are, two that I can think of quickly are learning curve and OEM buy-in. It is human nature to be reluctant to learn to use product B when you already are comfortable using product A. It takes a pretty good incentive to push people to expend the necessary energy. As for the OEMs, if they aren't already locked into a restrictive exclusive contract with Microsoft, they are probably reluctant to spend the resources to support installation of an alternative operating system on the machines they sell unless they see a sizable market. Given that it's a chicken and egg argument, adoption of Linux on the desktop will be slow until the market gathers enough mass. If and when that point is reached, you'll probably see very quick gains in market share. Getting large companies like IBM and Novell behind the push will go a long way in helping adoption.

    --

    GreyPoopon
    --
    Why is it I can write insightful comments but can't come up with a clever signature?

  52. Re:QT? What about licensing? by Ianoo · · Score: 2, Interesting

    I don't rate $1000 per seat as a reasonable price when I could give each developer Windows XP and bulk-licensed Visual Studio for a much lower price. I think QT is a great toolkit and am glad it's licensed under the GPL, however their closed-source version is much too expensive and I have to wonder whether many people actually buy it when there are equally as valid business models that involve GPL'd products these days anyway.

  53. Re:QT? What about licensing? by slipstick · · Score: 4, Insightful

    How can I say that? Well let's see, there are many boxed versions of Redhat & Suse that have been sold and I don't think anyone was ripped off.

    While it is probably impossible for Redhat not to create a free as in beer version of their free as in speech software, the fact that it can and is paid for is very telling.

    The main advantage of Open Source to most people is absolutely NOT the free binary whether they know it or not. It is not a "few geeks such as yourself" there is a very large world of geeks out here that value the source to their programs for many reasons other than that it may be free as in beer as well.

    If in fact you value the monitary freeness of your software over the freedom of the source than I would argue that your not a geek at all but just someone who wants to ride a gravy train.

    Furthermore the dichotomy you used between KDE & gnome is false because both are GPL'd. Would you rather pay for an Open Source KDE or get a closed source Windows for free? If you choose the Windows option than you definitely don't understand freedom and your no geek I want to hang out with.

    The fact is that people have to stop with this idea that "free" in the GPL'd way means "free beer". Free software is a costly thing,I have spent untold hours of my valuable time helping to code free software, but that's fine I don't expect payment for that work because I was paid in kind by other coders. But users who just take and never give back must understand exactly what they are doing. I can't force anyone to pay for software they can get for "free" but your mentality that software MUST be free as in beer is totally antithema to the actual freedom that is espoused by free(dom) software.

    Freedom software is about having the source, never looking over your shoulder for the thought police, adding to something and feeling you've contributed, learning, sharing. "Free beer" software is about being a leech!

    --
    Sure information wants to be free, but how much are you willing to pay for the packaging?
  54. Stop whining about QT licence... by Anonymous Coward · · Score: 2, Interesting

    Please specify a single popular commercial app that uses GTK...

    People fail to understand that you don't pay only for the right for developing commercial programs when you buy a QT licence. You are also paying for SUPPORT.

    There exist lot of free software for Linux, thus if you want to SELL your software, you need to invest lot of money in any case to create something much, much better.

    Last time I checked, there were lot of undocumented widgets in the GTK. How are you supposed to figure them out? $1000-$2000 QT licence pays itself quickly back with faster development times.

  55. haha by Ianoo · · Score: 2, Insightful

    GTK is much prettier than QT.. But seriously, beauty is in the eye of the beholder. There are just as many people who prefer Gnome's look over KDE's as there are who prefer KDE's over Gnome's.

  56. Re:I wonder... by theendlessnow · · Score: 5, Insightful
    Hee, hee... all these posts about the evils of KDE/Qt are hilarious.

    Use GNOME/Gtk, because you can USE Gtk as much as you want for COMMERCIAL development without paying anything.

    Don't use KDE/Qt, because you can only develop FREE software using it, otherwise it costs money.


    So.. NOW KDE/Qt is the champion of free software, whereas GNOME/Gtk is for the COMMERCIAL (and apparently not so evil after all) PROPRIETARY closed source solutions.


    You make me laugh!


    If GNOME/Gtk is REALLY a friend, let's see them place everything under GPL (for true software protection) rather than the LGPL.


    What's the big deal about support Qt is you use the toolkit? Yep.. it's commercial...and if you use it for commercial development, it costs money... so?? Is someone suggesting their software business plan is only to sell like 10 copies of their software, so they can't afford to by a real development license?? Just seems weird.

  57. Re:QT? What about licensing? by Espectr0 · · Score: 4, Informative

    Maybe for unix and mac, but there is no windows version. The windows version was 2.something, and if you buy a book you get an older 3.1 version as well.

  58. GPL != noncommercial by Rex+Code · · Score: 3, Insightful

    Now the license is different. I often wish there was a small-business or starting-business license, but this is only pertanant if you are going commercial work. for GPL work it is completely free.

    There's no reason a small business can't do commercial work and license it under the GPL. It's done all the time by the Linux distributors both large and small, and many other development groups.

    Anyway, I see this misconception about QT's licensing all the time, and I think part of it stems from Trolltech's own use of the word commercial to describe their other license. The word they (and you) are looking for is proprietary, not commercial. If you don't want to use the GPL (usually because you're paranoid about people stealing the ideas, or because you want to link with some other proprietary code), then you have to pay for commercial (i.e. proprietary) Qt licensing. However, you're free to use the free (GPL) version of Qt commercially, as long as you follow the GPL.

    1. Re:GPL != noncommercial by scorp1us · · Score: 2, Insightful

      How widespread do you think Linux would be if it had the same license as Qt?

      Actually MORE. Because there is commercial support. Businesses would have picked it up and ran with it years ago. If you don't belive that then you are too young to understand businesses.

      They don't care about open source. They care about profit margins and who to yell at when somethign goes wrong. If OpenSource results in a better product then they don't care as long as they are benefitted by it and not harmed. If it were proprietary, they'd still not care.

      History has computers as a trickle-down from companties to homes. If you run XYZ OS at work, then tog et work done at home you prolly have to run XYZ at home. Having business penetration would mean overal penetrations sooner. The company -wide linux deployments and tests would have happened years ago.

      Yeap its true.

      --
      Slashdot's rate-of-post filter: Preventing you from posting too many great ideas at once.
  59. GTK (and most GNOME libs) are LGPL by oddityfds · · Score: 4, Informative

    GTK (and most GNOME libs) are LGPL. As in: Permits linking with proprietary apps.

    So please mod parent down.

  60. This is inaccurate by mcc · · Score: 2, Informative

    If they don't want to pay for a commercial QT license, they are in exactly the same boat that they would be if they wrote a GTK app; i.e., if they want to distribute, they have to distribute under GPL.

    GTK has no such restriction. It is released under the LGPL.

  61. Re:Give me a break! by be-fan · · Score: 2, Insightful

    Not that there is really a Linux shareware market now, but this would be pretty effective in stopping one from appearing.
    What's stopping a shareware market from appearing is OpenSource, not Qt licenses.

    --
    A deep unwavering belief is a sure sign you're missing something...
  62. Re:QT? What about licensing? by pyros · · Score: 4, Informative

    It specifically clarifies commercial to mean closed source/proprietary. That's the whole purpose of the parenthetical. If that statement is unclear to you (the figurative 'you', not BiggerIsBetter specifically), then you probably shouldn't be responsible for making legal decisions on behalf of a company.

  63. *Proprietary* Qt is Dangerous to Linux!!! by Anonymous Coward · · Score: 5, Interesting

    Well, it appears that it was actually SuSE, with their Trolltech connections, that took over Novell, and not the other way around.

    And if we are not careful, Trolltech is going to end up controlling Linux. [We also need to consider the possibility of a backroom deal between Trolltech and Microsoft, similar to the deal between Microsoft and SCO.]

    The danger, of course, is not the GPL'd version of Qt. KDE is also not a problem. Both of those are Open Source, so we don't have to worry about them, and I have no reason to talk about them.

    The real danger of Trolltech is the proprietary version of Qt and the applications that depend on it.

    Or, in more general terms, the danger is proprietary middleware.

    Let's look at an example from history. Remember when the PC platform was open, from bottom to top? Remember when you could not only buy the hardware from any number of vendors, but there were also competing vendors for the BIOS, there was more than one windowing architecture (Gem, Geoworks, Borland's GUI libs,...), and there were dozens of development environments, and thousands of code libraries? Remember when standards were simple, when it was easy to write code to interface directly with printers, with video cards, and so on?

    What happened? Microsoft introduced Windows.

    After a while, Windows became an indespensible component of the PC. Applications depended on it, and hardware manufacturers had to support it. And there was only one supplier of the Windows component, namely, Microsoft.

    Soon, Microsoft started using its control of Windows to make itself the winner in the applications market. And today, Microsoft (with a few accomplices) also dictates the standards for PC hardware, its BIOS, its peripherals, and its network protocols.

    What was special about Windows? It was proprietary middleware!

    Windows sat in the middle, in between the applications and the PC. Any applications that wanted to access PC hardware used (and became dependent on) Windows APIs. And any PC manufacturer that wanted applications had to support Windows APIs. Bill Gates once said that by controlling the APIs, he controlled the industry.

    Likewise, PC users became locked in. They could replace their hardware. They could replace an application. But they couldn't replace Windows. As the PC became cheaper, Windows became more expensive, as did the Microsoft applications that Windows "encouraged" users to use.

    The proprietary version of Qt is just like Windows. It is proprietary middleware. It sits between the applications and Linux. The applications that use Qt are dependent on its APIs. And if Linux wants to be able to run those applications, then it has to support Qt.

    What applications are we talking about? Applications like Kylix, Hancom Office, Opera, the professional versions of Quanta and Rekall and various other TheKompany products, ATI's setup utility, Quasar Accounting, Adobe Photoshop Album, and so on. If a Linux distribution wants to be able to run those applications, then it must support the proprietary version of Qt.

    So how bad is it? Has Linux been taken over by proprietary middleware, the way the PC was taken over by Windows?

    In other words, Have we reached the point where the proprietary version of Qt, with its single supplier, is an indedpensible component of Linux?

    If this article is correct, and Novell is standardizing on Qt as the foundation of its desktop and development environment, then things are very bad.

    Others have also argued that it has become almost impossible to have Linux without proprietary Qt...

    In their paper Conquering the Enterprise Desktop, a group of developers argued that Bruce Perens' UserLinux would have trouble succeeding, unless it included the Qt Library in its basic install. Were those developers just talking about the GPL'd version of Qt? No, as shown by these statements:

    1. Re:*Proprietary* Qt is Dangerous to Linux!!! by IgnoramusMaximus · · Score: 2, Interesting
      This is one of most insightful AC post I have ever seen. This is precisely my main beef with QT. Its easy and sexy for the evelopers and has a following of enthusiasts. It has a good commercial presence amd marketing aimed at commercial developers.

      And its DEADLY for future of Linux as a free and open platform. Mark my words, a few years from now Slashdot will be full of suprised QT appologists going "What happened?! We thought Trolltech was on our side!" when TT turns into a Microsoft or SCO-like monstrosity and unlike SCO we will be all fucked since there seem to be a lot of developers who learn by sticking their asses into the fire because it looked "cute". No matter how many times were they warned about it.

      Dismissing critics as GNU Zealots and blabbering about dual-licensing does not hide the fact that TT is positioning itself as the nexus for ALL of the commercial application development on Linux. To be followed shortly by TT dictating Linux standards. Remember, commercial applications are where the mainstream acceptance of Linux will come from (at least in the near future) and it its the commercial applications which will be the most visible to the corporate desktop user. In fact those applications will be Linux as far as millions of corporate users are concerned. Their failure or success will directly impact the impressions of those poeple and subsequent adoption of Linux into their homes and small businesses.

    2. Re:*Proprietary* Qt is Dangerous to Linux!!! by IgnoramusMaximus · · Score: 2, Interesting
      This wont work for the simple reason that in order to charge varying license fees, Troltech would have to retain exclusive control of the licenses. Thus at any point of time (presumably when QT is an indispensable part of 90% of desktop Linux applications) the licensing could change. I (and probably most other opponents of QT) are not arguing that Troltech has no right to do as they wish with their code. We merely argue that blind depnedance on good will of Trolltech is foolish to say the least.

      Since QT is licensed under a childlish scheme of "dual-licenses" whereby Trolltech seems to think they can apply GPL willy-nilly only to certain applications of their choosing, there is nothing stopping them from changing the rules and proclaiming that GPL "only" applies to applications developed free of charge, on Friday the 13th between 4 and 4:15pm, during hailstorm and while a stampede of wild elephants in in progress...

  64. Well by mcc · · Score: 2, Interesting

    I've used Swing on small projects, but never used GTK, Qt or GNUStep.

    I had a job for part of which I spent about four or five months writing WxWindows. It seemed fairly easy to pick up, entirely reasonable as a development platform, and the quibbles I had with the functionality and documentation only came up a couple of times (one of the class docs was misleadingly written at one point, and one of the classes, WxListBox or something, turned out to only work on the Windows platform). Is Qt "better" than it? I wouldn't know. All I know is I had no objections to WxWindows whatsoever.

    Most of the stuff I do is not GUI. However what I do all of my personal GUI development in is Cocoa, one of the two Mac OS X GUI libraries, which I consider as elegant, complete and (usually) well-documented as I could possibly imagine a GUI library to be. From my perspective, it is generally a joy to use. And, um, well, it doesn't cost me anything to use. The development tools came free with the OS. Now, given, I had to pay money for OS X itself, and anyone who uses my programs will have to have paid money for the OS as well. But, um, you know what? I don't really mind paying for the OS so much. Personally. I feel like I'm getting what I paid for there. And I CERTAINLY prefer paying money to use the OS and then getting dev tools and a lovely dev library that I can do anything I want with to either YOU WILL USE THE GPL PERIOD or having to pay, um, what appears to be a per-year, per-developer, per-platform fee of at least either $500 or $1500, i can't tell which, to develop software. What I'm currently getting just sounds like a better deal to me, so personally I'm going to stick with it.

    (And since Cocoa is what GNUStep aims toward, who knows, if I really wanted to I think I could probably port my software to GNUStep without *too* much trouble. I know GNUStep is woefully incomplete, but this is why I mentioned it.)

    But this is of course totally just my opinion. And it isn't entirely germane. But hey, you asked.

  65. CORBA vs. DCOP by Anonymous Coward · · Score: 2, Informative

    My question is what about the interapplication communication issues. GNOME uses CORBA and KDE (Qt?) uses DCOP; then there is also DBUS, an extension (superset?) of DCOP. Is Novell planning on causing GNOME to move away from CORBA and toward DCOP/DBUS? Are they planning to add CORBA support to Qt? Are they ignoring this issue and hoping it will go away?

    1. Re:CORBA vs. DCOP by Anonymous Coward · · Score: 3, Insightful

      After 7 years of CORBA push, GNOME uses CORBA for pretty much nothing.

      Try to get a GNOME guy to give you five real, practical examples of how they use CORBA. He won't.

      He will mention that some apps can embed a gnumeric sheet, though.

  66. Re:QT? What about licensing? by pyros · · Score: 4, Informative
    I couldn't tell from your post if you're aware, so I'll state it just in case. The GPL only requires you to give source to those people to whom you have distributed binaries. So you can sell GPL software and not have to give the code to any random person who asks for it.

    It also sounds like you don't recognize the legitimacy of dual-licensing models. Do you support or oppose the LGPL? The LGPL enables companies to use GPL libraries, free of charge, to build closed source software (just like the BSD licenses).

    All Trolltech is saying is that if you want to use Qt to build closed source software, then you have to pay for Qt. They don't offer a GPL version for Windows because people were abusing it.

    At core is whether or not an application built on Qt is a derivative work or not. If it is, the GPL means you can't build a closed source application on top of. This is a feature that has prevented corporations from using GPL libraries. Hence the LGPL, and dual-licensing in general.

    It sounds like you're just mad that Trolltech decided not to go with a "free for commercial use" model like the LGPL.

  67. Hmmm - anybody else catch this? by Glonoinha · · Score: 2, Interesting

    Maybe programming will suck no longer!

    At first I read this as 'Maybe programs will suck no longer!"
    Good luck with that one, given the direction of the current corporate development climate.
    Probably applies to programming also, same reason.

    --
    Glonoinha the MebiByte Slayer
  68. Re:QT? What about licensing? by rsidd · · Score: 5, Insightful
    It sounds like you're just mad that Trolltech decided not to go with a "free for commercial use" model like the LGPL

    I'm perennially amazed that the GNOME zealots, who started out from the GNU "all software must be free" zealot camp, now argue that Qt is bad because it doesn't allow proprietary applications. (Actually, it does, if you buy a licence from Qt. Unlike, say, GNU's readline library, which was deliberately GPL'd and not LGPL'd by Stallman, who will not issue you a commercial licence.)

    In fact, RMS even wrote an article on why you shouldn't use the LGPL for your next library. Without the backing RMS gave GNOME in its early days, when it was an unusable piece of crap and KDE had already hit a high-quality 1.0, it would never have got off the ground. (Remember GNOME 1.0? *shudder*) And yet the selling point now is that GNOME is more suitable to proprietary apps? I just can't figure out where all this is coming from.

    If anything, Qt is a shining success story on how to make money with GPL'd software using a dual-licensing strategy. Far from continuing to vilify Troll Tech, the GNU/GNOME zealots ought to trumpet this story as a way to encourage more proprietary software companies to play nice with the linux world. (Peter Deutsch did the dual-licence thing long back with ghostscript, but he only released year-old versions of ghostscript under the GPL, and that's still the practice. Troll Tech releases current versions of Qt under GPL as well as their commercial licence.)

  69. Re:QT? What about licensing? by lspd · · Score: 2, Insightful

    You can licence it through GPL, if you do open source work, or you can buy licences from Trolltech at a reasonalble price if you want to do closed source work.

    "Reasonable" is a very relative word. Visual C++ costs $100 for the standard edition. QT standard edition for a single platform costs 15 times as much and doesn't include an IDE. Forget for a moment about all the other things that are included with Visual C++ and pretend it's just a license to distribute software developed with MFC. It's an absoloute bargain compared to QT.

    But what about cross platform development, you're saying... Well, if you go the QT route your price jumps up to $2490 for both X11 and Win32. If you go the MFC/Visual Studio route your price stays at $100 and you invest a little effort in porting your MFC app to wxWidgets (they are very similar.) If you were thinking ahead you would have started with wxWidgets from the get-go and porting would be a non-issue.

    Like I said though, "reasonable" is relative. Maybee you have thousands of dollars just burning a hole in your pocket. Personally, I don't.

  70. Re:OOP and C++ vs. C -- probably Offtopic -- or no by Tony · · Score: 4, Insightful

    Yes, but Gtk+ doesn't restrict you to C, whereas Qt is almost entirely C++ (except for some scripting language bindings, like Ruby, Perl, and Python).

    I despise C++. Hate it. It is an abomination both to C, and to OO programming. The syntax extensions to C are complex, as is the OO model. The only thing I think C++ did right is the templating system.

    I prefer Objective C, which takes a minimalist approach, and the late dynamic binding makes templating irrelevent. It's a much cleeaner language.

    So, the issue comes down to choice. I know a lot of people prefer C++ to Objective C. You can't account for taste-- it seems more people prefer Budweiser to any other beer, and McDonald's to any other food source, and MS-Windows to any other desktop OS. But the point is, there is choice. I know I don't want to declare a single standard language for all programmers to use, and I distrust anyone who does.

    If they standardize on any one toolkit, we are screwed as developers. Instead, they should concentrate on standardizing protocols. And, from a comment Nat Friedman made somewhere along the line in this topic, that's exactly what Novell is doing.

    Anyway, just my two bits.

    - Tony

    --
    Microsoft is to software what Budweiser is to beer.
  71. Re:QT? What about licensing? by pyros · · Score: 2, Informative

    I couldn't tell if you were directing that at me or not, but since only quoted that one like and mention zealots, I'll assume you weren't. I totally agree with you. I actually use GNOME as my desktop, but have used a commercial version of Qt, and commercially licensed Psi, to produce a closed source app. I think the big thing is when people talk about freedom for the developer and freedom for the consumer without realising they're contradicting themselves when they change point of view between developer and consumer.

  72. Re:QT? What about licensing? by jmorris42 · · Score: 4, Informative

    > Ironic, that a GPL'ed toolkit should be considered inappropriate for
    > basic foundations of Linux software..

    But that is the reality. Core libraries should be LGPL to prevent no end of problems. Imagine trying to get Mozilla or OO.o up and running in a world where Qt was the only suitable toolkit. Either the Windows & Mac ports would have to be dropped or each and every developer would need to possess a license for the commercial version of Qt.

    --
    Democrat delenda est
  73. Re:QT? What about licensing? by slipstick · · Score: 2, Interesting

    You almost have it.

    I haven't actually been arguing about profit in a monetary sense at all. What I'm trying to argue is that users of freedom software must be conditioned to know that the expectation is that they give back something. I don't care what it is, coding, documentation, word of mouth of how freedom helps them or money.

    In your case I've been trying to condition you to react by both giving back software and evangelizing freedom NOT free beer.(since you mentioned your a coder)

    This started because it seemed to me that you expect that software must be free of cost in a monetary sense. Monetary free is only a possibility from freedom source not a mandatory requirement.

    "The only way to make money with information is to either generate new information or to provide a more efficient way to spread,gather or copy information"

    There you go you got it. Well at least you have part of it. Where in your above statement does it say anything about the nature of the license attached to the information? It doesn't matter if the information is licensed under the GPL, if I make my product more attractive, easier to use, more worth while, more...something. Than people will pay, either through their own hard work, word of mouth or with money. In fact it should be expected that people do pay in one of these manners. Anyone not paying somehow, not necessarily with money, is a free loader pure and simple. In the long run enough people will see the value of paying for freedom software to make it profitable.

    As to the music,movie, television industries. Their problem isn't that they are losing control of distribution it's that they are LAZY. They refuse to charge the correct amount for the information or they refuse to provide sufficient value-added to make buying the information desirable.

    I will pay a reasonable amount to have a CD,book,DVD or easy cable access. Currently all of these are too high for the product that is sold. I care not a wit for "Top 40" music it's not worth even a penny to me. If a music exec asked himself why than maybe they'd understand. The reason is there is absolutely no value in that information to me. I won't even waste bandwidth on it. However, if you somehow got George Clinton and Parliament back together, put together a good CD of funk, with bitchin' liner notes and maybe throw in the possibility of tickets to see them at a concert in New York(e.g. put a coupon in random jewel cases) I might pay $30,$40 or even more dollars for that. In both cases the information is free(the music) but only in the latter is there a value added service that I'd pay for.

    As a physicist by training and a coder by profession I KNOW information wants to be free. The question is what are you willing to pay for sharing in it?(Again pay is not just in a monetary sense.)

    --
    Sure information wants to be free, but how much are you willing to pay for the packaging?
  74. Re:QT? What about licensing? by gabebear · · Score: 2, Informative
    You can use QT for proprietary stuff, you just have to pay.

    They offer versions(Mac/X11) under either the GPL, or you can buy any version under a license for commercial apps. TrollTech also recently released a version for Windows for non-commercial apps, this license doesn't seem to require you to distribute your source.

    Pricing info is here, it's pretty reasonable, they have some decent GUI design tools too.

  75. Trolltech 'commercial' clear as mud by Jayfar · · Score: 2, Informative

    Restrictions
    Software created with Qt Free Editions is governed by the terms of the GPL and QPL.
    The Free Edition licenses do not allow the development or distribution of commercial software.

  76. Re:QT? What about licensing? by Brandybuck · · Score: 2, Informative

    Last time I checked, the GPL license for QT is only avaliable for QT/X11, NOT on QT for Windows.

    It doesn't matter because the topic of the day is "Novell Linux Desktop".

    --
    Don't blame me, I didn't vote for either of them!
  77. Is Novel smoking the same crack as Darl? by AstroDrabb · · Score: 4, Interesting
    This is not a post about Gnome vs KDE. I like them both, though I use Gnome more because I still think the KDE widgets are a little to blocky/clunky. If QT starts making some good money, they should hire a graphic artist to draw out their widgets to make them smoother and round those stinken corners. I have seen KDE desktops that look great just as I have seen Gnome desktops that look great. I guess, to my eyes, QT widgets still look too blocky.

    Anyway, I wonder what in the world would make Novell pick QT? I don't have a problem with the QT license since it is free for GPL'ed code and if you want to do closed source, you pay, just like the rest of the world. I am fine with that. What I don't understand is what is Novell's game plan concerning all the Ximinan "IP" that they bought? There is no acceptable QT based groupware application that is ready _NOW_, while there is GTK+ based Ximian Evolution that even works very well with MS Exchange. There is Mozilla that is GTK+ based. Novell is not going to get all those users to switch to konq when, IMO Konq is not standards compliant enough yet and the rendering engine is not up to snuff with Gecko. What about OOo? Again, it uses GTK+, I cannot see Novell porting that beast to QT. These three apps are critical to the Linux desktop, everything else is fluff in comparision.

    Maybe they plan to do some good QT/GTK+ integration? I hope so, since the two tool-kits have issues with simple interoperation such as drag-n-drop and copy-n-paste, not to mention how different the widgets look. I personally don't want a Linux desktop that has no consistency between the widgets. This is the main reason I always look for Gnome apps over KDE apps to keep my desktop consistent (with the exception of K3b, since it is one great app).

    Oh, there is also the issues of the different technologies that the two desktops use. What sound server are they going to use? arts or esd? Are they going to make the coding changes to to the all the other apps or do they expect a user to have both running? DCOP or Orbit? etc vs etc. IMO, Novell should have picked one desktop and then ported any of the very good apps from the other desktop over. It would take a long time to port Evolution, Mozilla/Firefox and OOo to QT and have it be stable.

    Since Redhat dropped interest in the desktop, I was hoping for Novell to help push Desktop Linux, though this move makes me less optimistic.

    --
    If Tyranny and Oppression come to this land,
    it will be in the guise of fighting a foreign enemy. -James Madison
  78. Non-Free Qt Makes Non-Free Software Unsafe by Valdrax · · Score: 2, Insightful

    News at 11:00!

    Seriously, the only threat that Qt provides to the Free status of Linux is thanks to non-Free code built on top of it. If you build GPL code with Qt, then you can always from now until the end of days use the GPL version of Qt. The only products that can be screwed by an about-face attitude from Trolltech are the ones that Free Software advocates AREN'T USING IN THE FIRST PLACE. If Trolltech turns into a monster, the GPL Qt libraries can be forked and Trolltech can be told to go hang themselves.

    --
    If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
  79. Programming doesn't suck now... by Erisian · · Score: 2

    Bliss = Python + wxWindows

    --
    What's the difference between an orange?
  80. Re:Well. by be-fan · · Score: 2, Informative

    That doesn't make any sense. Novell is competing against Microsoft, so the MS toolkit(s) aren't a choice for them. Besides, Qt is better than anything MS has yet to release. Even the .NET toolkit is stone-age compared to Qt. Its not font-sensitive, it doesn't have a layout manager, etc. So MS won't have a toolkit competitive with Qt until the next iteration of the .NET toolkit, which is slated to have these features, comes out with Longhorn.

    --
    A deep unwavering belief is a sure sign you're missing something...
  81. Re:QT? What about licensing? by mdwh2 · · Score: 2, Insightful

    Though note that the Windows version is based on an old version (2.3, released March 2001), and they seem to have no intention of releasing newer versions (and oddly, I couldn't find it linked at all from their page, I could only find that by searching).

    A shame - I got all excited when I thought there might be a reasonable GUI toolkit available for Windows that didn't rely on visual-designing and x/y absolute coordinate layouts, but I'm not sure if it's worthwhile learning what is effectively going to be a discontinued and already outdated version of the product (no, I'm not paying $1550, that might be reasonable for a company, but not for someone who wants it for programming for fun in their spare time! ;)

  82. What is really going down here? by Findus+Krispy · · Score: 3, Insightful

    I am really missing the point of all of this. We have a link to a German article that is uninteligble to the majority of posters here, and a lot of people talking absolute nonsense. Why?

    When the previous article about Novell merging KDE and Gnome I immediately thought, which platform will they use as the base. I guessed KDE since the KDE people are already doing all the work whereas the Gnome people don't seem so interested. Nobody asked that fundamental question. Why?

    Now, assuming that article says what it is claimed, I am left wondering why people think Gtk is being dropped, and scratching there heads over the Ximian aquisition. Why do people think that Gtk is being dropped, and what does integration mean to you anyway?

    When Novell say *they* are standardising on Qt why do people then say that everyone else must now develop their apps in Qt too? How do you explain the fact that Gtk apps have long worked under KDE, and now Novell wants to integrate them more tightly?

    To me this all sounds like Novell are going to make more use of Qt for their own future development, are going to use KDE as a base system for their OS, but are going to continue and extend the work being done in the KDE camp so that Gtk based applications work flawlessly in KDE (print dialogs, file dialogs, look 'n feel, font settings, control center options, etc).

    The only question I am left wondering is whether they will also offer a Gnome desktop and do the exact same integration the other way round so that KDE applications work flawlessly in Gnome. Anyone care to comment?

  83. Bad comparison, QT !~ Windows. by je4d · · Score: 2, Interesting

    impossible to have Linux without proprietary Qt...

    that a Linux distribution must include support for proprietary Qt

    In effect, they are saying that proprietary Qt is to Linux, as Windows has been to the PC.


    etc.

    There's a BIG difference between windows and Proprietary QT here, and the difference is that Windows costs money per-user. So to use the windows middleware, your *users* have to pay Microsoft.

    However, with Proprietary QT the only cost is per-developer. So to install opera, hancom office, etc, I don't have to pay a penny to Trolltech. Only the companies developing these proprietary apps need to.

    For that reason alone, trolltech is not going to fall into the control of trolltech.

    1. Re:Bad comparison, QT !~ Windows. by IgnoramusMaximus · · Score: 2, Informative
      There's a BIG difference between windows and Proprietary QT here, and the difference is that Windows costs money per-user...

      Not in the area that is being discussed. We are discussing control. Money usually follows control but it does not need to be "per-user" charge. Merely ridiculous "per-deployment" surcharge on the toolkit. It amounts to the same thing since you will then collect per-user form of a tax on all revenues of software vendors. Better, since you yourself do not need to deal with those pesky users directly.

      So in your example: to install Opera you pay Opera who in turn pays portion of thier per-user revenue to Trolltech. Etc. Right now the per-developer fee is flat but thats only because QT is not an indispensable part of Linux desktop... yet. Wait utill it becomes so and you will find out there is no limit to corporate greed once a company has a lock-in control of something.