Slashdot Mirror


Trolltech Discontinue Non-Commercial Qt

An anonymous reader submits "Trolltech has quietly discontinued their non-commercial version of Qt for Windows. This eliminates Qt as a choice for those wanting to develop free multi-platform software." Actually, according to the linked page, "if you write Free software (Open Source software covered by the GPL) you are welcome to download and use the Free Edition of Qt," and Trolltech points out that one can buy the current edition of Qt -- seems fair enough.

32 of 101 comments (clear)

  1. No great loss by lpontiac · · Score: 4, Informative

    Qt/Free on Windows was decreasingly useful .. it was a crufty old binary-only Qt 2.3, which is quite aged when you consider that Qt is up to 3.2.x. Being pre-3.0 there were notable differences between it and more 'modern' Qt versions.

    By the way, you can still do Free (as in GPL) software development cross-platform on Qt, between X11 and Mac OS X.

    1. Re:No great loss by Spy+Hunter · · Score: 3, Insightful

      Well, you can do free cross-platform QT development on any platform you want, as long as that platform runs X11 and has a POSIX-like interface (and what platform doesn't, nowadays?). Now that XFree86 is available for Windows (which is awesome, BTW) it should hardly be any trouble at all to develop QT/X11 applications for Windows as well. But if you want native QT/Mac or native QT/Windows, you still have to pay.

      --
      main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
    2. Re:No great loss by lpontiac · · Score: 3, Informative
      ut if you want native QT/Mac or native QT/Windows, you still have to pay.

      Half right. QT/Mac is available under the GPL.

  2. Alternative Toolkits by oz_ko · · Score: 5, Informative
    I think one of the best free toolkits is the eclispse swt which can build binaries for almost any platform.

    There is also now a visual editor which should make development much easier.

    Check it out at http://www.eclipse.org

    Oz

    1. Re:Alternative Toolkits by IIEFreeMan · · Score: 3, Informative

      Agreed that SWT is a great toolkit but VEP (which is the visual editor you mention I think) doesn't do SWT yet. For the moment it's Swing/AWT only.
      However it's on their roadmap to add SWT support.

  3. Re:No big deal by BrianHV · · Score: 5, Informative

    The wxWindows license is LGPL with an exception to allow static linking and binary-only distribution without extra source distribution burdens. This is nice when you want to tweak a platform's behavior at the toolkit layer.

  4. Perhaps they are waiting for the Bill? by leonbrooks · · Score: 4, Interesting

    When Microsoft get around to Freeing Windows, perhaps TrollTech will Free the Windows version of Qt?

    As another poster points out, wxWindows does a lot of the Qt stuff in the WIMP arena, and I'd like to add that systems like libSDL pretty much cover the unWIMPy, less structured stuff anyway. Having a spectrum of alternatives is good, and since the smallest disk I can buy these days without going out of my way is 40GB, I don't have a problem with installing a dozen or so sets of libraries.

    --
    Got time? Spend some of it coding or testing
    1. Re:Perhaps they are waiting for the Bill? by wcbarksdale · · Score: 4, Informative
      Actually, I remember that being roughly their answer on an old FAQ. Their current one says more obliquely:
      Trolltech supports free software development on platforms where contributing to Free Software/Open Source development is part of the platform strategy. At the time being it does not seem natural for us to release a free edition for Qt/Windows.
  5. Re:No big deal by grotgrot · · Score: 2, Informative

    Technically the wxWindows license is LGPL with exceptions. The exceptions make people like me happy (*), while still keeping the source under strict GPL.

    There is one significant problem that still affects wxWindows and that is that many Linux based PDAs use Qtopia which is based on QT and the QT license. This makes it difficult to do wxWindows for the Zaurus etc.

    (*) My code is under an open source license, just not the GPL. Consequently I wouldn't be able to use GPL stuff although I would be able to use LGPL stuff

  6. Re:Canopy Company by Anonymous Coward · · Score: 5, Informative

    Look here. Trolltech is not a "Canopy Company". The Canopy Group owns 4.1% of Trolltech shares. Borland owns 8.3%--is Trolltech then a "Borland Company"? The employees own nearly 64.7%--is Trolltech then an "Employee Company"?

    Do you see how fucking inane your claim is?

  7. Re:No big deal by GreyWolf3000 · · Score: 2, Insightful
    No.

    Look around at crossplatform OSS projects. WxWindows is much more widely used. Hell, even the Win32 GTK port is more widely used.

    Also, can someone enlighten me as to why my post was flamebait?

    --
    Slashdot: Where people pretend to be twice as smart as they really are by behaving like children.
  8. Re:Canopy Company by be-fan · · Score: 2, Insightful

    Canopy group is delusional, what's your point? If a single-digit stake makes them a Canopy group company, than that's really grasping at straws. Linux Networx (which delivered a top-5 Linux-based supercomputer to LLNL) is also a "feature company" on Canopy's website. A search for "canopy" on their website doesn't even get any hits. Seriously, the TT -> Canopy relationship is hugely overblown.

    --
    A deep unwavering belief is a sure sign you're missing something...
  9. I must be missing something here... by shadow255 · · Score: 3, Interesting
    From the QT website:
    If you write Free software (Open Source software covered by the GPL) you are welcome to download and use the Free Edition of Qt
    Since there is no Free Edition of Qt for the Windows platform, is Trolltech making some kind of statement that Free software does not exist for Windows? I can think of an example off the top of my head of a GPL program which is available only on Win32: FileZilla.

    I'm not saying Trolltech is obligated to make a Qt Free edition for Windows, but perhaps they should word things a bit differently on their website, along the lines of "If you write Free software for X11/Mac..." It's just plain misleading, to my thinking, to state it the way they are.

    --

    Logic is a wonderful thing but doesn't always beat actual thought. -Terry Pratchett

    1. Re:I must be missing something here... by Brandybuck · · Score: 2, Insightful

      The per-developer license, having no relationship with the value of the final product, introduces a lot of uncertainity in the economic calulation.

      Virtually every commercial UNIX development tool I've ever used in the has been a per-user license. This is similar in some ways to a per-developer license, but more flexible. It's main drawback is that you need a license server. It still has the "uncertainty" factor you're talking about. Do we need licenses for 25 developers should we go with 50? On the other hand, most commercial Windows development tools have per-seat licenses. This ties the developer down to a specific workstation which can be quite annoying.

      The uncertain economic calculations can be a problem for some things, but not for tools. Carpenters buy hammers at a fixed price. They don't send monthly royalty payments to the hammer manufacturers.

      A royalties-based license, instead, is very clear: you make money, then you pay us. You don't, you owe us nothing.

      Could you list some popular commercial tools that have this pricing? I can't think of any off the top of my head. I do know of some embedded operating systems that somewhat follow this model, but no develoment tools per se.

      little by little, KDE is being marginalized, despite being by far the best desktop. IMHO, the QT license is the culprit.

      In terms of KDE, the license is the dual QPL/GPL. You're right, the GPL is completely inappropriate for a Free Software desktop. What were they thinking?

      --
      Don't blame me, I didn't vote for either of them!
  10. Before the trolls start by daaku · · Score: 4, Informative

    It needs to be mentioned that this doesnt not affect the GPL version of Qt, as used for KDE and never can. Its been said, and said over again. Go here to find out why:

    http://kde.org/whatiskde/kdefreeqtfoundation.php

    1. Re:Before the trolls start by nanop · · Score: 2, Informative

      Sorry, I'm wrong. Not enough reading on my part.

  11. Corrections to Timothy's $0.02 by Keith+Russell · · Score: 3, Troll
    Actually, according to the linked page, "if you write Free software (Open Source software covered by the GPL) you are welcome to download and use the Free Edition of Qt,"...

    Actually, if you read what the submitter wrote, he said "free multi-platform" software. OK, I'll grant that X/11 and Mac are "multi-platform", but when those platforms make up ~7% of the market, it's nothing to brag about. Trolltech continues to aggresively deny Qt developers the ability to distribute their works to the vast majority of the computing product. After all, cross-platform Open Source software can't possibly succeed, can it?

    ...and Trolltech points out that one can buy the current edition of Qt -- seems fair enough.

    MSRP of Microsoft Visual C++ .NET Standard Edition: US$109. MSRP of Qt/Windows Professional Edition: US$1550. <sarcasm>Oh, yeah. That's fair.</sarcasm> It's really discriminatory and punitive. And it's still not Open Source. What makes them think that taking the low road like that will convince Windows devlopers to consider Qt?

    --
    This sig intentionally left blank.
    1. Re:Corrections to Timothy's $0.02 by Brandybuck · · Score: 4, Interesting

      After all, cross-platform Open Source software can't possibly succeed, can it?

      How much money has GTK+ made for GNU? How much money has LGPL wxWindows made? How about plain XFree86? I'm not talking about donations from Redhat or SuSE, I'm talking about actual revenue from actual customers. Now ask yourself if that's enough to support even one full time developer?

      I do wish that Trolltech would release a QPL/GPL version of Qt for Windows. But they'll still have to charge proprietary prices for proprietary development if they want to stay in business.

      MSRP of Microsoft Visual C++ .NET Standard Edition: US$109. MSRP of Qt/Windows Professional Edition: US$1550.

      Rather than repeat the tired cliche about apples and oranges, let me merely remind you that filet mignon costs a lot more than canned tuna, yet no one complains about the discriminatory and punitive pricing of fine steaks.

      --
      Don't blame me, I didn't vote for either of them!
    2. Re:Corrections to Timothy's $0.02 by 0x0d0a · · Score: 2, Insightful

      How much money has GTK+ made for GNU? How much money has LGPL wxWindows made? How about plain XFree86? I'm not talking about donations from Redhat or SuSE, I'm talking about actual revenue from actual customers. Now ask yourself if that's enough to support even one full time developer?

      Yes, but instead of looking at it from a TrollTech point of view, look at it from a user point of view. Regardless of *why*, there are a number of developers supporting GTK+. It might be very difficult for TrollTech to make a profit doing th same thing (hell, it's hard for a company to compete with lots of free software), but that doesn't mean that users should then use TrollTech software.

    3. Re:Corrections to Timothy's $0.02 by angel'o'sphere · · Score: 2, Interesting


      What makes them think that taking the low road like that will convince Windows devlopers to consider Qt?


      I stopped developing for windows about 5 or 6 years ago. That was when the cross platform GUI library zApp got discontinued.

      If the prices you point out are correct, I would definitly consider using Qt if I was "forced" to code for windows and was forced to use C++.

      Of course I would prefere Java and SWING :-) And also: I cant be forced, LOL. Anyway my point is: Qt costs currently $1550 as you say. I would cost you about $900 a day. So if you can save 2 days of my worktime through using Qt instead of MFC, or lets say 4 days and lets buy a Windows Qt version and a HP or Solaris one ... you are even.

      The question I would ask a guy developing "free" software (and wanting to use Qt for windows is): how much do you value your own time? You rather spend 2 years writing an application instead of 1 year and spending an additional $1500?

      So a year of work is for your self less valuable than buying a good software?

      angel'o'sphere

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    4. Re:Corrections to Timothy's $0.02 by Keith+Russell · · Score: 2, Insightful

      If you're in a professional environment, that $1550 may justify itself. If you're successful, it's a drop in the bucket. But for the hobbyist, it's a brutal kick in the teeth. Never mind the money, though. It still doesn't solve the problem that buying Qt for Windows to develop Free/Open Source software is antithetical to both the spirit of the movement, and the letter of the law.

      Say, for example, me and my buddy Kyle use Qt to write the Greatest Program In The World, and we suck it up and pay the $1550 each for Qt/Win licenses. We decide to release it under the GPL, with the required exception clause for the Windows version. While the Linux/Unix and Mac OS X geeks tinker away at it, the Windows folk discover that they can't do squat with the source, unless they also fork over $1550 to Trolltech.

      This is precicely why the GPL does not allow you to use non-Free libraries from 3rd parties. Those libraries preemptively stifle any progress on the platform(s) that require them. And the sad part is that Trolltech recommended exception clauses with the non-commercial version! They're supposed to be such staunch advocates of Open Source, yet they suggest that Windows developers compromise their principles. Maybe Trolltech thinks that anyone who develops Open Source software for Windows has already compromised their principles. Pretty piss-poor attitude, if you ask me.

      --
      This sig intentionally left blank.
  12. Let them do what they want by endrek · · Score: 5, Insightful

    I've seen lots of grumblings about this, but lets think for a moment. Why should they be obliged to supply a windows version. Its software developed for unix. Windows is a big difference and porting to it is no fun (I know). If its not fun, why give it away for free. So they're currently only selling it. Looks like a proccess. If they don't make enough money to makeit a viable option they'll probably just dump windows support entirly. From the unix front they get lots of useage and thus advertising of a sorts, what with kde and all the related apps. But free stuff for windows using qt hasnt really caught on, so why bother supporting such a hassle. Its their work to do with as they will they were supllying a free service and it didn't work out for them don't harp on them Don't like it? the current code is gpl fork it yourself and continue developing it if you all really care the point is that probably no one cares enough and it won't happen, which is why I think they've largly abandoned it. The difference again being popularity of platform. If they stopped new release of the gpl unix versions, someone, most likely the kde group, would pick it up and keep it going.

  13. Change of policy or the plan all along? by Andy+Smith · · Score: 3, Insightful

    Methinks we'll be seeing a lot more of this in future, ie: release software for free, let it become established for a few years, then discontinue the "free version" so people are, to some extent, forced to buy the commercial version.

    Companies should either do free or commercial software, or both. They shouldn't establish their product as free and then start charging for it once people rely on it.

    This strikes me as more of a long-term market-share strategy rather than a recent change of policy.

    1. Re:Change of policy or the plan all along? by infiniti99 · · Score: 2, Informative

      Actually, the whole Non-Commercial version was an experiment in making Qt/Windows more accessable to free software developers. It was not intended as a bait-and-switch. Trolltech was very hesitant about releasing their flagship product for free on Windows (probably their biggest source of income), so in mid-2001, around the time Qt 3.0 was in the beta phase, they released a non-commercial version of Qt 2.x for Windows. The plan was that if their sales started to drop (implying that companies were freeloading off of the non-commercial version instead of buying licenses like they were supposed to), then in a few months they would release Qt 3.0, thus obsoleting the non-commercial version. In other words, by timing the release around that of Qt 3.0, they had an 'easy out' to prevent much harm if the move was a mistake.

      Well, guess what? It was a mistake. The sales data came in, and indeed they lost a bunch of money. Qt/Non-commercial was effectively dead later that year. I'd say the fact that they were even letting people download it through 2003 was just to be nice. There is very little reason for them to continue hosting a file they never update. Someone else can take over that job now. :)

  14. VEP download by FunkyRat · · Score: 2

    Check here.

  15. That's okay: Use ParaGUI instead... by torpor · · Score: 3, Informative

    www.paragui.org (follow the link to savannah)

    The market for cross-platform toolkits is wiiiiide open, and there's a lot of ground to be covered. ParaGUI (on top of SDL) is not such a bad choice ....

    --
    ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
  16. Somebody port it, then by __past__ · · Score: 2, Interesting
    Didn't somebody recently announce a new effort to port the Free version of Gt/X11 to Windows?

    That might help even if the project won't get finished itself. Remember the Big Qt/KDE Licensing Flamewar? Seeing both Gnome and Project Harmony, a free Qt clone, being developed because many people considered the old QPL to be not acceptable for the base of a free desktop, Trolltech gave in and adopted the current dual licence scheme. With a free port to Windows, and other cross-platform toolkits being available (and getting more support, like Borland now using wxWindows after having used Qt for Kylix), they might reconsider not offering a free version for Windows themselves.

    Or we can all just get along and use one of the other fine cross-platform toolkits.

    1. Re:Somebody port it, then by Haeleth · · Score: 2, Informative

      This is probably what you're referring to - an attempt to port the GPL version of Qt 3 to Win32.

  17. Port of Qt/X11-GPL to Qt/Windows almost done by fault0 · · Score: 3, Informative

    Yup folks, I've been trying it out the last few days, and the port of Qt/X11 to Qt/Windows (and is thus GPL'd) is almost done, and has progressed a lot over the past few months. Most of the graphical parts are done (replacing the x11 dependant parts of Qt with win32/GDI equivalents.)

    What's not done yet is replacing the non-GUI parts- e.g, moving from the "_unix" files and writing win32 equivalents. Thus it currently requires cygwin (but no X11).

    There are some screenshots here. Source is available there too.

  18. Re:No big deal by jensend · · Score: 2, Informative

    The Win32 GTK 1.x port had lots of serious issues. However, I haven't noticed any serious issues with the GTK 2 port (which is used by just about all the win32 gtk apps except the stable version of the gimp). Care to elaborate?

  19. Trolltech: "No Free Lunch" by jgardn · · Score: 2, Insightful

    Trolltech is saying that there is no free lunch. It gives the source out freely to Free Software users because they receive so much from Free Software and the Open Source model. They could build a viable business model with their free software alone.

    The reason why they refuse to give away their source code and add value to the Windows codebase is because they get nothing in return from them. In fact, they have to pay Microsoft for the "privilege".

    It's also much more difficult to code for the Windows platform than for the standard free software *NIX platforms.

    One of the reasons is the lack of reliable documentation. Sure, there are tons of documents out there on Windows, but there are too many contradictions in them. Which one is correct? Which calls may cause seg faults? Which ones will cause the entire system to fail? No one seems to know. Microsoft has a mysterious habit of presenting second-rank "experts" to the community, while hiding the first-rank and true experts from public view. This means when you go read an article written by an "expert" in the field, it is really a nice PR ploy with little or no true substance. I guess you have to pay a lot more or live on the Microsoft campus if you want access to the actual experts.

    The other is the short, abrupt upgrades that totally invalidate their previous work. Imagine rewriting the entire KDE codebase every year or so because Linux and XFree86 decide to move around all their APIs and invalidate previous ones. That is what Microsoft is forcing people to do. I've experienced it first-hand from about 1997-2000, as I was writing a game based on Direct3D. How many times did the API to Direct3D experience a complete rewrite? I don't recall, but I think it was something like 4. I also had to code up from '95, to '98, and then to 2000 and NT. That was a very painful experience for me. I feel the pain of the people who are chained to their desks and forced to code for windows. You really are slaves to the whims of Redmond.

    The other reason is that when they have a problem, they cannot "dig down" into the source code or the community to discover if the problem is on their end or the OS's end. When developing for Linux or *BSD, when you run into some serious problems, you can either look into the source code itself or even ask the kernel community if there is a bug there or what you are doing wrong. Such is not possible with Microsoft unless you shell out some cash and spend a lot of time speaking with phone monkeys.

    If you really, really need a Windows version of Qt, and if it really is going to save you a lot of time in your project, then you should gratefully shell out the money to get a developer's version of Qt for Windows. And you can't complain that it is not open source -- neither is Windows, and yet you use that. Your money is going to hire people who really don't want to code for Windows. You will be paying to have them trained on the latest versions of windows. Not just the APIs, but the new applications as well. Your money is going to be used to purchase the latest and "greatest" windows platform for them to code, test, and build on. Your money is going to go to the phone monkey department as they call in to see if there is a bug in the Windows OS or if they are just reading the wrong version of an "expert's" analysis. Your money is going to be spent lining Bill Gate's pockets, and hire a few people who would rather be coding for Linux, in other words.

    --
    The radical sect of Islam would either see you dead or "reverted" to Islam.
    1. Re:Trolltech: "No Free Lunch" by The+Bungi · · Score: 2, Insightful
      They could build a viable business model with their free software alone.

      Well, you must know about building a business model more than people who already run a company. I guess that makes you an expert.

      The reason why they refuse to give away their source code and add value to the Windows codebase is because they get nothing in return from them. In fact, they have to pay Microsoft for the "privilege".

      That's the way it works in the real world my man. You write software for a commercial OS, and then you sell it. Microsoft will give you nothing more than IBM will if you write an application for OS/390. And would you care to clarify and back up how TT "pays" Microsoft for the "privilege"?

      It's also much more difficult to code for the Windows platform than for the standard free software *NIX platforms

      Really? Last I looked (five minutes ago actually, since I happen to be coding) there are exactly two "widget" sets in Win32, one of which hasn't changed in 10 years. If you want more power you can extend them easily, or use something else, like wxWindows. And how is writing software for Windows more difficult again? More difficult than what?

      One of the reasons is the lack of reliable documentation

      OK now, this makes absolutely no sense whatsoever. What the hell are you talking about? Documentation segfaults and experts??

      The other is the short, abrupt upgrades that totally invalidate their previous work

      This is about as pathetic an argument as you can humanly come up with. DirectX is a graphics API and it's used to write games. Games. Get some perspective here. The Win32 API is bar none the most stable and backwards-compatible I've ever worked with (and yes, I've worked with commerical Unices and Linux).

      I feel the pain of the people who are chained to their desks and forced to code for windows. You really are slaves to the whims of Redmond.

      Typical "you poor idiots you don't know how green the grass is over here" zealot. Here's a newsflash: There are people out there who are not "chained to their desks" and enjoy writing software for Windows. You might conjure up images of slaves hitting keyboards all day if that makes you feel better, but that doesn't make it true. And "whims of Redmond"? I'd like to see you run a GUI-based application written in 1989 on RedHat 9. I mean, I can still run Windows 3.0 apps on Windows XP, so that would be a fair comparison.

      Oh wait, there was no GUI Linux in 1989. Never mind.

      The other reason is that when they have a problem, they cannot "dig down" into the source code or the community to discover if the problem is on their end or the OS's end.

      Really now. "I can't see the code so it must suck". Hundreds of thousands of developers writing successfull applications for Windows must be figments of my imagination. And BTW, I'd just as well have the vendor fix the problem instead of wading through and trying to understand their code. It's called "productivity", not tinkering. Well, at least if you expect to get paid for what you're doing.

      Your money is going to hire people who really don't want to code for Windows

      Yes, because everyone thinks like you do, all over the world. Everyone wants to code for Linux, with its seventeen mutually incompatible widget libraries. Yeah, I can't believe I hadn't seen the light until now. Oh and of course we all want to be freed of the "slavery", yes. Damn, that makes sense.

      Your money is going to be spent lining Bill Gate's pockets, and hire a few people who would rather be coding for Linux, in other words.

      In other words, you are about as disconnected from reality as the average open source code monkey. Which I guess doesn't surprise me that much.