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

47 of 615 comments (clear)

  1. 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 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?

    2. 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/
    3. 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.

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

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

    6. 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/

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

    You mean the GPL?

  3. 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 alext · · Score: 4, Funny

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

      You and Miguel?

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

  4. 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 ----
  5. 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.

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

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

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

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

  9. 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!
  10. 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.

  11. 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.
  12. 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?
  13. $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.

  14. 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.
  15. 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.

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

  17. 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.
  18. 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.
  19. 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.

  20. 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?
  21. 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.

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

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

  24. 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.
  25. 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)
  26. 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.

  27. *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:

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

  29. 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.)

  30. 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.
  31. 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
  32. 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