Slashdot Mirror


Trolltech Releases First Qt 4 Technology Preview

An anonymous reader writes "Trolltech has announced the availability of the first Qt 4 Technical Preview. Qt 4, the next major release of the popular cross-platform C++ application framework which KDE is based on, is scheduled for final release in late Q1, 2005. Download mirrors here, here and here."

95 comments

  1. I love Qt! by Per+Wigren · · Score: 4, Insightful

    I just wish I could use it when developing cross-platform GPL-programs. :(

    --
    My other account has a 3-digit UID.
    1. Re:I love Qt! by cyborch · · Score: 1

      What prevents you from developing cross-platform GPL programs with QT?

    2. Re:I love Qt! by Anonymous Coward · · Score: 1, Informative

      I just wish I could use it when developing cross-platform GPL-programs. :(

      Your wish is trolltechs command.

    3. Re:I love Qt! by Anonymous Coward · · Score: 1, Interesting

      moolah, or lack thereof.

    4. Re:I love Qt! by Anonymous Coward · · Score: 0

      IT'S FREE!

      It's only not free if you intend to create non-free programs with it.

    5. Re:I love Qt! by EnglishTim · · Score: 4, Informative

      Your wish is trolltechs command.

      Well, no it's not. There is no free edition of Qt for Windows. If you want to develop a program that will run on Windows, you'll need to buy it.

      If you can't do Windows, it kind of throws out the whole crossplatform thing.

    6. Re:I love Qt! by EnglishTim · · Score: 5, Informative

      IT'S FREE!

      It's only not free if you intend to create non-free programs with it.


      It's not free for the Windows version, even if you want to create a free program that will run on Windows, which is why the original poster said crossplatform.

    7. Re:I love Qt! by Anonymous Coward · · Score: 0

      Ahhh... I didn't know that.

      So, I stand corrected (twice -- since I also made the "IT'S FREE" comment)

      That's pretty lame that it's not free for windows too. But, I guess it helps promote Linux development, so maybe it's not so lame afterall.

    8. Re:I love Qt! by xophos · · Score: 1
      Well GNU/Linux, *-BSD, ...


      That certainly IS cross platform. :-P

    9. Re:I love Qt! by alex_tibbles · · Score: 1

      Is there an alternative? Is the GTK+ port to Window production-ready? I use Gaim and Gimp on Windows, and have had no particular problems, but are they equal to supported Qt (when you pay)?

    10. Re:I love Qt! by Apreche · · Score: 1

      I love GTK. I wish I could use it when developing cross-platform GPL programs.

      wait a minute.....

      --
      The GeekNights podcast is going strong. Listen!
    11. Re:I love Qt! by squiggleslash · · Score: 2, Informative
      The X11 version is released under the GPL, the source to the Windows version - unless something has changed recently - remains firmly under wraps.

      I guess you could compile the X11 version to run under Cygwin/X11. But I'm not sure that counts as "cross platform"...

      --
      You are not alone. This is not normal. None of this is normal.
    12. Re:I love Qt! by Per+Wigren · · Score: 4, Informative

      You really can't compare Qt with GTK because Qt is more like a development platform/framework than a just a GUI-library. WxWidgets is much closer to Qt than GTK will ever be (and it uses GTK for GUI-drawing on X11), but Wx is nowhere as mature as Qt at this point.

      I started to use Wx for an application I'm working on, but it was impossible to even get a decent looking TreeView/CList with checkboxes which resizes in a sane way. After much frustration with Wx I switched to plain GTK in which I could great a GUI the way I wanted to, but now instead I have to look for external libraries for everything like sound playback, database connectivity, networking support, regexps, and much much more. It's like hell to support on several platforms. :P

      If Qt-Free was avaiable on Windows I could stick to Qt-conventions and support the application on all platforms with just a simple recompile.

      --
      My other account has a 3-digit UID.
    13. Re:I love Qt! by EnglishTim · · Score: 1

      Yes, it says that the Free Editions are released under the GPL and QPL. But if you'd looked on the Licensing Overview page, you'd note that there is no Free Edition for Windows.

    14. Re:I love Qt! by arkanes · · Score: 4, Insightful


      Check out wxWidgets (formerly known as wxWindows) for an alternative. No, the support isn't as good as Qt, even if you pay. On the other hand, unlike GTK, your app won't look and run like ass on windows. And the community support via IRC and mailing list is excellent. wxWidgets is, in fact, the only toolkit I know of that is mature, cross-platform, and free. (I don't consider GTK to be mature in the cross-platform category)
      </plug>

    15. Re:I love Qt! by burnetd · · Score: 2, Informative

      This does not seem to have been posted yet...

      I've you really want to have GLP'd QT on Win32 help out here...

      Otherwise stop moaning about it.

    16. Re:I love Qt! by Narchie+Troll · · Score: 2, Informative

      GTK+/Win looks fine nowadays, especially with the native skin. I know lots of people that happily use Gaim without knowing it's in a different toolkit.

    17. Re:I love Qt! by Anonymous Coward · · Score: 0

      Well GNU/Linux, *-BSD, ...
      That certainly IS cross platform. :-P


      And a BASIC program that can be compiled on Apple IIs and Commodore 64s is also cross-platform. But we both know that's not what he meant.

    18. Re:I love Qt! by jmv · · Score: 1

      developing cross-platform GPL-programs

      OK, I'm not familiar with the all the licensing details (no flames please), but isn't the Windows license for Qt non-GPL (as in you need to pay for it). In that case, wouldn't it be illegal to link a GPL application against it on Windows. I'm guess I've missed something here, can someone give more details?

    19. Re:I love Qt! by Brandybuck · · Score: 1

      There is a non-commercial version for Windows available. It isn't free-beer-ware, but it's only $39 by buying the book. And it allows you to use the GPL. Of course you might have to use a one line exception in your license, but as a developer I think you can handle that.

      --
      Don't blame me, I didn't vote for either of them!
    20. Re:I love Qt! by Brandybuck · · Score: 2, Interesting

      There's no free edition for QNX/Photon either. Heck, there's a lot of platforms that don't have native free Qt editions. What's up with that?

      On to a serious note. GTK+ for Windows did not magically pop out of someone's ass. It had to be ported from X11 to Win32 by hand. There is absolutely nothing stopping anyone from doing to same with free edition Qt.

      --
      Don't blame me, I didn't vote for either of them!
    21. Re:I love Qt! by Brandybuck · · Score: 1

      If Qt-Free was avaiable on Windows I could stick to Qt-conventions and support the application on all platforms with just a simple recompile.

      A non-commercial 3.1.2 version comes with the new $39 book. It is complete and not crippled in any way. Or if you're really cheap, the old 2.x NC version is still on Trolltech's FTP site.

      --
      Don't blame me, I didn't vote for either of them!
    22. Re:I love Qt! by Anonymous Coward · · Score: 0

      While Qt is not free-as-in-speech for Windows, its commercial distribution includes redistributables which you can include for free-as-in-beer, even when your own application is free-as-in-*.

      Of course, don't use the GPL for your own app there. Trolltech won't mind, as the copyright owner you may also create binaries, but the GPL doesn't grant users to create those binaries (since they'd have to link your GPL code to Qt). The LGPL would work for your app.

    23. Re:I love Qt! by Qwavel · · Score: 2, Interesting


      On the one hand I agree that wxWidgets is very good.

      On the other hand I think that GTK on Windows looks good and works well.

      wxWidgets is particularly good if you are writing in C++ or Python. GTK is particularly good for C.

      Both are good options.

    24. Re:I love Qt! by natmsincome.com · · Score: 1

      In this case you did have a couple of other options.

      1. Go to the source and add the features you wanted.
      2. Subclass and add a fork for the GTK version of your software. That means that the other version are Crap and the GTK version is ok, this might not seem like a big deal but it means in later version of wXWidgets you may be able to remove your hack. It also means you can do the same hack for the other sub systems without having to make that many chabges.

  2. New and Improved by UPi · · Score: 3, Insightful

    Qt has always been techically superior and rather geek-friendly. Looks like in the new release they have found PHB-friendly names for their existing components. For example, they call the QTL (Qt Template Library - their replacement for STL) "Tulip".

    Seems like they have changed more classes than they usually do, and have moved a whole set of "obsolete" classes into a separate compatibility library to help the transition from Qt3 to Qt4. This probably means that developers have a few years to remove these classes from their codebase before they go from "deprecated" to "completely removed".

    The press release seems to be quiet about their previous challenge to Java (they have claimed a few months ago to produce a Qt4 that will be in "direct competition" to Sun's offerings). I'm kind of happy about this.

  3. How soon in KDE? by agent+dero · · Score: 2, Interesting

    According to the article, they implementing some nice big changes, like a new paint framework, and unicode renderer, etc.

    But by Q1 of 2005?

    How long after that will we need to wait until KDE switches over? (assuming that QT4 will be a step up from QT3)

    KDE team?

    --
    Error 407 - No creative sig found
    1. Re:How soon in KDE? by alex_tibbles · · Score: 2, Informative

      I seem to remember seeing notes from a KDE conference where there was a presentation about Qt4, and KDE plan was to make the next major release use it. I think I misunderstood or KDE plans have changed, since they released 3.3 beta1 with a very ambitious release schedule. Perhaps the plan is to get 3.3 out with some good features and fixes, before the massive turmoil of moving Qt3->Qt4 begins for KDE 4... But AINA KDE Developer

    2. Re:How soon in KDE? by Anonymous Coward · · Score: 1, Informative

      KDE 4.0 will be based on QT 4.

      Now there's 3.3 point release before that :)

    3. Re:How soon in KDE? by Carnildo · · Score: 1

      I seem to remember seeing notes from a KDE conference where there was a presentation about Qt4, and KDE plan was to make the next major release use it. I think I misunderstood or KDE plans have changed, since they released 3.3 beta1 with a very ambitious release schedule.

      I think you did. KDE 3.3 is a minor release, while KDE 4 will be a major release.

      --
      "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
  4. C++ by RAMMS+EIN · · Score: 4, Interesting

    Does Qt still use that layer of C++ compiler workaround cruft?

    I never understood why they went and wrote their framework in a language that had such sucky implementations. I think GTK had it right - develop it in a language that works, then provide (de-uglified) bindings for other languages. gtkmm is a very clean API, IMO.

    --
    Please correct me if I got my facts wrong.
    1. Re:C++ by alex_tibbles · · Score: 3, Insightful

      Depends how long term you plan. There are benefits as well as problem associated with using C++, you know(!). My concern would be that now that there are decent C++ implementations (G++ 3.3 is pretty adequate, 3.4 will be good when fully stable, GNU libstdc++ is fine too, then there is stlport....) that they junk the non-standard re-implementations (slowly) and migrate to using standard code (reducing bloat).

    2. Re:C++ by OmniVector · · Score: 2, Insightful

      it's not so much performance/bloat that many of us are concerned with, but the language used. Not only does Qt require a hack language on top of C, but it requires moc, a hack on top of a hack language.

      by hack i more or less mean a poorly designed language. of course gcc's implementation is good, but that has little to do with the design of c++. C has many advantages over c++ including but not limited to the fact that: you can write c++ in c (or at least do OOP in C to the similar functionaly of c++) and you can bind with just about every other language with minimal effort.

      --
      - tristan
    3. Re:C++ by alex_tibbles · · Score: 1

      Yes, C++ has flaws, but writing OOP in C suggests that you are using an insufficiently expressive language. I don't want to implement multiple dispatch in C++, I'd use CLOS if I needed multiple dispatch. Language features like this belong in the language implementation.
      If you don't like C++ but want to do OOP, why not use a better OOP language, rather than hacking it on C? I don't see how hacking pseudo-OOP onto C is better than using a problematic OOP language (C++).

    4. Re:C++ by Brandybuck · · Score: 1

      You could do OOP in assembly as well, but I've never seen anyone do it...

      --
      Don't blame me, I didn't vote for either of them!
    5. Re:C++ by FudgePackinJesus · · Score: 1

      C does not support generic programming (templates) in any way. Sure C, in being turing complete, can perform any function that C++ can produce but the amount of extra textual expression required in C to match what the C++ compiler does for you is staggering. Less code equals less chance of bugs, lower maintenance and faster development (well, that last point is arguable given you really need a C++ language lawer at times). This is a very important difference in these languages that some people fail to remember when comparing.

      Sure I'll give you that C++ is huge and messy with differing implementations but it is also the most cabable native-compiled language on the market with mass acceptance (i.e. portable). In a market such as GUI toolkits, using an expressive, natively compiled and portable language is crucial. This is where C++ is actually a sane choice over, C, Java, Object Pascal, OCaml and many others.

      Idealism loses out to realism in business

    6. Re:C++ by OmniVector · · Score: 1

      much in the same way game developers first and foremost target windows for game development, C++ is targted for commercial or large project development.

      it doesn't mean windows and c++ are better, just that they are the "defacto" standard. i know as well as the others why c++ was chosen for qt, but that doesn't mean i enjoy using the language to do development with it. my motives for programming are not for profit, but for enjoyment. money is a side effect for me really, so if i'm not enjoying it.. why am i doing it? of course it's always more complex than that. people have to put food on the table. however when i have a choice on a project's development where we start from scratch, or if it's a personal project, c++ is pretty far down on my list of languages to choose. somewhere near perl and pascal.

      btw, a competent, and enjoyable, replacement for c++ does exist today. check out objective-c sometime. here's my tutorial page or Wikipedia's article on it. despite the common misconception, it's not a mac only language. it's just as portable as c++, with a compiler on just about every major platform (thanks to gcc) and you can easily write code with c-linked libraries.

      --
      - tristan
    7. Re:C++ by FudgePackinJesus · · Score: 1

      Neat. Thanks for the link. I got interested in ObjC when I first installed windowmaker a couple of years ago. I think the message syntax (method invocation) looked too alien for me at the time but now after trying to learn a couple of more languages I can get past that now. Functional languages are really interesting to use too. OCaml's use of cutting edge programming concepts: type inference; pattern-matching; robust types (allowing functions to return multiple values via tuples) makes for one of the most concise natively-compiled languages I've ever seen.

      But in regards to your second thought, I wasn't trying to imply that C++ was the end all be all language (...oh good lord no). Just that for TrollTech, at time when they started, it was the right tool for the job. Just as the MOC is the right tool for the job to implement a very slick object communication mechanism. I just becomes very hard to watch other programmers pine for a "elegant" replacement where all of the faculties are provided by the language with an ideal API meanwhile forgetting that any complex system, such as a GUI toolkit, is going to develop quirks and work-arounds over time.

      This is why TrollTech should be commended because they are making highly stable tools (moc turns out to be very easy to get along with) that work around the limitations of the language without being too intrusive to the language (think MFC message maps, glib, and GTK upcast macros here) and they have always strived for source, and even binary, compatability when reworking large portions of their API because they realize the value of just extending a tried and true codebase (something Joel Spolsky enlightened all of us to with this peice).

      Good times.

    8. Re:C++ by MemoryDragon · · Score: 1

      What workaround cruft do you mean? As for the bindings, not a big deal, as long as you stay in a oo context a binding is possible and there are bindings for many languages alreaday available.

  5. SVG render ? by johnjones · · Score: 2, Insightful

    so...

    this would be a great thing to have and cross platform would be a killer feature
    IMHO

    regards

    John Jones

  6. Just to sort things out... by dbglt · · Score: 4, Informative
    For those who are uniformed or unaware, QT is dual licensed:

    Firstly, under a commercial license (which is ~$1000)

    Secondly, under the GPL for non-commercial usage only

    However, QT for Windows is not released under the second license, meaning that if you want to develop with QT and the Windows platform - even if you are a non-commercial entity - you must purchase a commercial license (or manage to persuade the nice folk at TT to grant you a license, as a few open source projects have managed to do).

    I feel this limits the target market... as one of the reasons to even begin coding in QT (other than the WONDERFUL documentation :p), is the promise of cross platform availibility. I have heard it is possible to compile under win32 platform with cygwin and mingw - but I cannot confirm this

    Anyway, as I develop primarily for *nix platforms, this is not a big issue for me, but I would like to see QT opened up for the windows platform. That way I'm not limited in the future if I decide to work with another platform.

    1. Re:Just to sort things out... by jemfinch · · Score: 1

      Secondly, under the GPL for non-commercial usage only

      This is a contradiction of terms. If it's under the GPL, it is, by definition, usable commercially.

      See this FAQ for more information.

      If Trolltech has limited QT such that it cannot be used commercial, then QT is not licensed under the GPL. It may be a variant of the GPL, but it is not the GPL.

      Jeremy

    2. Re:Just to sort things out... by zbik · · Score: 1
      For those who are uniformed or unaware, QT is dual licensed:
      1. Firstly, under a commercial license (which is ~$1000)
      2. Secondly, under the GPL for non-commercial usage only

      Technically it is triple-licensed, as it can also be used under the QPL -- this is what KDE does. The QPL is easier to combine with certain other free software licenses. See Peter Vandenabeele's answer to "Why did UserLinux decide to not include Qt" in the UserLinux FAQ.

    3. Re:Just to sort things out... by aCC · · Score: 1

      Secondly, under the GPL for non-commercial usage only

      Erm... if it's GPL, then it can't be "for non-commercial usage only". Not possible, because then it wouldn't be GPL anymore.

      You can be commercial with the GPL. No problem. (But not proprietary. Maybe you meant that.)

      Here's the GPL FAQ: http://www.gnu.org/licenses/gpl-faq.html

      (But yeah, bummer, it's not GPL for Windows. They would really gain in my opinion like they did with GPL'ing it for *nix systems.)

    4. Re:Just to sort things out... by agraupe · · Score: 0

      I think QT is doing its part to break our dependence on Windows. As long as there is good Free software for Windows, many people won't convert entirely to Linux (I'm guilty; Firefox on Windows ATM). Mind you, not even M$ has made it easy to develop on Windows (this includes the development of Qt). I'm not surprised that Trolltech wants to punish M$ and its users for making it work so hard :)

    5. Re:Just to sort things out... by kunudo · · Score: 1

      For those who are uniformed or unaware...

      Yes, the military allways has a hard time with things like this. How good of you to point things out for them. Very patriotic, I might add.

    6. Re:Just to sort things out... by fredzouille · · Score: 1

      > Secondly, under the GPL for non-commercial usage only

      Wrong, see this.

      Under the GNU GPL you could even sell copies of the Linux version of QT.

    7. Re:Just to sort things out... by 4of12 · · Score: 1

      if you want to develop with QT and the Windows platform you must purchase

      Even for developing?

      What if the developed code is used exclusively by the developer and no one else?

      It would seem to make more sense if the commercial license were required upon distribution of QT/Windows code, not development of the application.

      --
      "Provided by the management for your protection."
    8. Re:Just to sort things out... by Anonymous Coward · · Score: 0

      > Firstly, under a commercial license (which is ~$1000)

      For which I can get the entireity of MSDN Universal. Yes, they have the right to charge as much as they want, and they have the right to wish to stay in business. But practically speaking, I have to wonder how many people are bothering to bite?

    9. Re:Just to sort things out... by cant_get_a_good_nick · · Score: 1

      Though the GPL doesn't explicitly rule out commercial use, it does effectively seriously curtail the ability to sell software for money. Even when you do try, you generally get flamed for it - there was a fork of CDex that (under my understanding) technically did not violate the letter of the GPL, but many felt it violated the spirit, and they got hammered on it.

      That said, "being able to sell your software" is a pretty narrow description of "commercial use". We use things here internally all the time. RedHat uses GPL software to promote it's commercial services, etc.

    10. Re:Just to sort things out... by Anonymous Coward · · Score: 0

      Even for developing?

      What if the developed code is used exclusively by the developer and no one else?

      It would seem to make more sense if the commercial license were required upon distribution of QT/Windows code, not development of the application.


      Think about it:

      If the license is for distribution, you sell one license per product per company.

      If the license is for developing, you sell one license per developer per company.

      Most companies have more developers than products. You do the math.

    11. Re:Just to sort things out... by Anonymous Coward · · Score: 0

      or manage to persuade the nice folk at TT to grant you a license, as a few open source projects have managed to do

      Which ones?

    12. Re:Just to sort things out... by Brandybuck · · Score: 1

      Which makes it so ironic that the first thing the GPL fanboys yell about is the cost of the commercial edition of Qt...

      --
      Don't blame me, I didn't vote for either of them!
    13. Re:Just to sort things out... by gregfortune · · Score: 1

      It's an excellent development framework and for developers with cross platform needs, the cost is well justified in the amount of time/effort saved. I bit some time ago and am very happy with the decision. When Qt4 releases, I'll probably bite again and upgrade my license...

    14. Re:Just to sort things out... by Senjutsu · · Score: 2, Informative

      Yup, even if developing. I was evaluating some toolkits to use for some strictly-for-my-own-use apps which had to be crossplatform (between Windows XP and Linux, at least) and that took QT out of the running instantly.

    15. Re:Just to sort things out... by elflord · · Score: 1
      f Trolltech has limited QT such that it cannot be used commercial, then QT is not licensed under the GPL.

      They release different versions of Qt under different licenses.

    16. Re:Just to sort things out... by Anonymous Coward · · Score: 0

      Psi is one. Don't know about others.

  7. wxWidgets by redragon · · Score: 4, Informative

    I've been using wxWidgets for quite a while. I must admit that it took a little getting used to, but I don't think the parent post does wx justice. Sure wx isn't as mature as Qt, but it is Open Source (which /. ers should like), it can be used in commercial apps (which people that like selling software should like), and the guys working on it put in a ton of time making a great library. The differences between wx 2.4.2 and 2.5.2 are quite impressive, and their current MacOS guy seems to be making an effort to bring wxMac along by leaps and bounds.

    Resizing isn't as tough as you think, look into wxSizer objects. If you want a more robust basic tree control, take a look at wxTreeMultiCtrl, or sub-class wxTreeCtrl and make your own. It's the beauty of the system. I've used tree controls in several applications without such pains.

    It's always a bit of a trip learning a new GUI toolkit, but the sheer volume of great tools included in wxWidgets overshadows any pitfalls found right now.

    Just MHO.

    --
    - Sighuh?
  8. major clarification by Ender+Ryan · · Score: 3, Insightful
    # Secondly, under the GPL for non-commercial usage only

    I'm not a QT "fanboy," but I have to point out that GPL != non-commercial.

    With the GPLed version, you can do whatever you want, but if you distribute your program, it must also be licensed under the GPL.

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
  9. Atleast in articles about by vijaya_chandra · · Score: 1, Funny

    Troll tech should trolls be modded up for a change

    1. Re:Atleast in articles about by Axeus · · Score: 0, Offtopic

      No.

      Get it? I'm a troll? Hahahaha...
      Well at least it was better than the parent's joke.

  10. Re:C++, bad news by Qwavel · · Score: 2, Interesting


    I hate to tell you this, but they are doing the opposite of what you (and many other C++ developers) are hoping for.

    Instead of slowly migrating towards standard C++, the way that other frameworks have, they are taking deliberate steps towards a more proprietary language.

    For example, in QT4, they are moving to new template containers, but instead of using the STL (which even MFC developers tend to use) they having decided to develop their own container classes.

  11. Re:GPL VS not-GPL by rbk17 · · Score: 1

    I never really understod, how QT or Mysql can release stuff under GPL and non-GPL. How do they handle bugfixes and new features from 3. parties (guessing a bugfix is covered under the GPL)? How do they put it back into the non-GPL version?

  12. The nail in the coffin release by Qwavel · · Score: 3, Interesting


    I am a C++ developer, and I recognize that KDE/Qt are better in most ways than Gnome/GTK+, but this release is not acceptable to me.

    Unfortunately, when TrollTech tries to find the right balance between it's own interests and those of its community, I think it tries to error on its side, but ends up hurting both itself and the community.

    Other frameworks are migrating towards the C++ standard, but Qt seems to be migrating away from it, ensuring a lack of interopability of code and skills.

    Other technologies are trying to open up to more languages, but TrollTech has decided that C++ (their own version of C++) is all that anyone needs. Even as a C++ developer, I recognize that this is a bad strategy.

    Other open-source projects are moving towards cross-platform (eg. AbiWord and Gnumeric will both be available for Windows soon), but TrollTech continues to keep 90+% of the market (ie. Windows) away from open-source Qt developers and their software.

    1. Re:The nail in the coffin release by jd10131 · · Score: 3, Interesting

      I develop commercial software with Qt

      I do not see how Qt is "moving away from the C++ standard" Trolltech produces a library, standards conformance depends upon your compiler.

      Trolltech does not produce their own version of C++; but their library does provide some macros that may appear to change the language. (ie: the new foreach)

      You are free not to use these things, or you may use as much fancy-pants standard C++ as your compiler will let you get away with. I mix Qt and some pretty steep template metaprogramming code with (uh, relative) ease.

      Furthermore, there is are excellent bindings to python, if you'd like to write something in another language. http://www.riverbankcomputing.co.uk/pyqt/

      Trolltech is a company that derives revenue from Qt. Without that revenue TT, and thus Qt, would not exist. I believe the reason for not releasing a regular GPL version for windows is the entrenched culture of piracy.

      There is a book available with a recent version of Qt included on CD. I am not aware of the license it is under, but I've heard the book is quite good.

    2. Re:The nail in the coffin release by Bob+The+Cowboy · · Score: 1
      Other open-source projects are moving towards cross-platform (eg. AbiWord and Gnumeric will both be available for Windows soon)


      Err... I don't know about Gnumeric, but AbiWord has had a windows port for well over 4 years... normally I wouldn't be anal about this, but AbiWord's a good program, and I wouldn't want people to think its not available for windows yet when it certainly is.
    3. Re:The nail in the coffin release by Qwavel · · Score: 1


      Hey, I'm honored to be getting so much attention from the moderators.

      Seems to be a battle between those who find it 'overrated' and those who find it 'interesting'.

      But I didn't mean to troll. I probably should have chosen a different subject though.

    4. Re:The nail in the coffin release by Qwavel · · Score: 2, Interesting


      The STL is part of the C++ standard. So, when TT decides to create some new template based container classes, hut to create their own rather than using the STL, I consider this to be non-standard.

      Microsoft did the same thing years ago, back when the standard wasn't ready. People got really mad at them (which was quite ligit because MS knew this would be bad for developers though good for themselves).

      As the standard and its acceptance have improved, MS has improved their compiler and their STL to the point where they are now (v7.1) very good, and very compatible with GCC 3.4 and with Intel. They have not retrofitted the STL to MFC, but they haven't changed MFC much in a long long time. If they came out with a new library at this stage and didn't use the STL I would accuse them of undermining the standard and I would not accept the need to make money as an excuse.

      I understand, of course, that companies don't do these things to be evil, they do it to make money. But TT doesn't do a very good job of balancing the bottom line, with PR, and the general interests of the community. Even they admit that they (not to mention the rest of us) would have been better off if they had GPL'ed QT much sooner.

      Using the version of Qt in the book is dead-end since using it would mean being stuck with that version on all platforms.

    5. Re:The nail in the coffin release by elflord · · Score: 2, Informative
      So, when TT decides to create some new template based container classes, hut to create their own rather than using the STL, I consider this to be non-standard.

      Trolltech had container classes before C++ was standard. Recently, Trolltech have built in a substantial amount of STL compatibility to their classes. They're not moving away from the standard at all. BTW, the python bindings for Qt are very nice.

    6. Re:The nail in the coffin release by be-fan · · Score: 3, Insightful

      Qt doesn't use "non-standard" C++. You can write Qt code in regular C++ code --- moc simply writes a lot of boiler-plate for you. What you're complaining about is not that Qt uses non-standard C++ (since it doesn't), but that it doesn't use the STL style of programming. However, given that C++ is a multiparadigm language, that's perfectly valid.

      GUIs are inherently object-oriented and amenable to dynamic programming techniques. That's why people like Objective-C (Cocoa), and Smalltalk so much for GUI programming. The STL style of C++ is very anti OOP and anti dynamic programming. Indeed, the creator of the STL, Alexander Stepanov, has said OOP is a hoax. While Stepanov is entitled to his opinion, and the STL is certainly useful for a wide range of tasks, it's silly to try to shoe-horn Qt into a programming style that doesn't fit it's problem domain.

      --
      A deep unwavering belief is a sure sign you're missing something...
    7. Re:The nail in the coffin release by be-fan · · Score: 1

      The STL and Trolltech's containers are totally different. The STL is homogeneous and value-oriented. Trolltech's containers are heterogeneous and reference oriented. Trolltech is defining their own containers not because they want to, but because the STL doesn't encompass what they are trying to do.

      --
      A deep unwavering belief is a sure sign you're missing something...
  13. Re:GPL VS not-GPL by spitzak · · Score: 1

    People contributing bug fixes would be aware of the license terms of Qt. If they want their bug fix to be GPL-only then they should clearly state this (TrollTech may ignore the bug fix then).

    I'm pretty certain if you sent a block of code to TrollTech in a letter that said "Can you please add this nice fix I made to your code" that in court that would be an acknoledgement that you are allowing TrollTech to copy your code and put it under it's license.

  14. Qt Non-commercial version for Windows by SeanAhern · · Score: 3, Interesting

    I've been reading a lot of posts to this article which claim that there is no free version of Qt for Windows. If so, then what's this?

    I don't program on Windows, so I can't tell definitively, but that web page reads right. It sounds like there's a GPL version for Windows that lets you write non-commercial software without paying a dime to Trolltech. It's based on version 2.3, but it is Qt.

    If I'm wrong here, please educate me.

    1. Re:Qt Non-commercial version for Windows by Brandybuck · · Score: 4, Informative

      There is a non-commercial 3.1.2 version, but it's only available with the new Qt book (forget the title). It's much better than the 2.3 NC version. Besides being newer, it also supports many more compilers (and even comes with an older BCC).

      Unfortunately, as you can see by those verions, it limits you to certain versions. How long after 4.0 is released until a NC version is available somewhere? For some people this is an insurmountable problem. For others, like me, it's merely an annoyance because Unix/Linux is my primary target platform.

      --
      Don't blame me, I didn't vote for either of them!
  15. Re:C++, bad news by mean+pun · · Score: 1
    For example, in QT4, they are moving to new template containers, but instead of using the STL (which even MFC developers tend to use) they having decided to develop their own container classes.

    Qt3 also has container classes, Qt4 just has more of them. I for one welcome this, since they are much more useful than the STL ones. Ditto for QString versus string. Standards are great, but the Qt people have the courage to fix their mistakes.

  16. MySQL-Trigger called by Anonymous Coward · · Score: 0

    eggbot::startPostgreSQLFUDding {{{/*

    Yeah, but PostgreSQL has and . And does qour MySQL have ? Huh? Huh?

    --

    yeah, ima gnetwo usar. i can compyl a kernal in 2 minites!!

    go, gnetwo, go!!

  17. Why avoid Qt Non-commercial by tepples · · Score: 2, Informative

    Qt Non-commercial for Windows is based on ancient Qt 2.3.

    Qt Non-commercial for Windows requires Microsoft Visual Studio 6, which is priced out of my league. Most hobbyists on Windows would prefer something that works with MinGW, a port of GCC to Windows, and Dev-C++, an IDE around MinGW.

    Qt Non-commercial for Windows is not published as source code and is thus incompatible with libraries published under the GNU General Public License.

    Qt Non-commercial for Windows is not compatible with selling copies of the program, even at cost: "A non-commercial setting means that you must not use the package in the course of your employment or whilst engaged in activities that will be compensated. A non-commercial application is an application that cannot be sold, leased, rented or otherwise distributed for recompense."

    1. Re:Why avoid Qt Non-commercial by scrytch · · Score: 1

      > Qt Non-commercial for Windows requires Microsoft Visual Studio 6, which is priced out of my league.

      Free is out of your price range?

      Everything else I do agree with however.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    2. Re:Why avoid Qt Non-commercial by yamla · · Score: 1

      That's a link for the vc toolkit 2003. The Qt non-commercial Windows edition requires Visual Studio 6 and will not work with earlier or later compilers.

      --

      Oceania has always been at war with Eastasia.
  18. Re:C++, bad news by FudgePackinJesus · · Score: 1

    While the STL is a powerfull base of collection structures and algorithms it's not as robust as what Qt has to offer in some respects. std::string, for example, is pretty bare bones as far as it's implementation and developers end up having to create to a whole slew helper functions just to do basic formating operations.

    At this point they have only a couple of options: wait for the standards comitte to catch up with the real world (out of the question for a business); standardize on somebody else's library, like boost; or develop their own to fit their customer's needs exactly. I don't think TrollTech is losing sleep over their choice.

  19. Re:C++, bad news by Qwavel · · Score: 1


    I don't think you are understanding the purpose of a standard.

    Of course they can come up with something better by starting fresh, tailoring it for their environment, and taking advantage of the passage of time since the standard.

    I could improve the whole language pretty easily too, but we need to agree on some standards for lots off reasons (I don't think I need to explain them on /.). You should have a very, very good reason before you start undermining standards.

    The STL is now generally accepted (more so than std::string, and much more so than std::iostreams).

  20. But does it work with newer command line tools? by tepples · · Score: 1

    Visual C++ Toolkit 2003 is the command line compiler, roughly comparable to the MinGW 3.0 distribution; it's not the Studio (IDE). I guessed that Qt for Windows required some sort of IDE integration. Even if not, is Visual C++ 2003 compatible with libraries and project files from Visual Studio 6? There are two differences involved here: newer compiler (different flags) and lack of IDE (possible different project file format).

    1. Re:But does it work with newer command line tools? by scrytch · · Score: 1

      It's a commandline compiler, yes, but it's fully optimizing and all, it's the full blown compiler. It's so much faster than gcc it's not funny. I can hardly imagine it requires the graphical capabilities of the IDE, merely the workspace/project file format. I think you can be pretty sure the flags won't change -- it's converting MSVC5 projects that's cumbersome, since MSVC6 got rid of LIB.EXE for LINK.EXE (which *is* different). If you know someone with MSVC6, you can ask them to output makefiles from the workspace, if they're not included already. However, .dsp files are themselves very close to being makefiles already, so it's not too hard to convert them by hand.

      Of course for all your trouble, you'll merely succeed in compiling a rather retrograde version of Qt that's GPL-encumbered. Serviceable, but not very satisfying.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
  21. Non-commercial 3.2 version for Windows - $31.49 by gregfortune · · Score: 2, Informative

    While not completely free, a book written by two trolls is available here and sold through Amazon.com for $31.49. That book includes a non-commercial version of Qt 3.2 for Windows.

  22. Try THIS! by gregfortune · · Score: 1

    Come on people....

    While not completely free, a book written by two trolls is available here and sold through Amazon.com for $31.49. That book includes a non-commercial version of Qt 3.2 for Windows.

    So, you are able to develop free apps across both Windows and Linux for a very nominal cost. Consider it a $32 license fee with a free book if you like.

  23. Pretty close to free - Only $31.49 with a book by gregfortune · · Score: 2, Informative

    While not completely free, a book written by two trolls is available here and sold through Amazon.com for $31.49. That book includes a non-commercial version of Qt 3.2 for Windows.

    Bite the bullet and buy the book. Or consider it $32 for the license and get a free book...

  24. Re:C++, bad news by Anonymous Coward · · Score: 2, Interesting

    You're right, there are a number of reasons to support standards. But the raison d'etre of standards is simple: compatibility.

    This issue is clearly moot in Trolltech's case, because anyone who would be using the QTL is using Qt and will have to distribute libraries anyway.

    The side benefits provided by standards can be extensive. For example, using the STL would mean that programmers wouldn't have to learn as much new API.

    However, if the standard is ineffective, or the new QTL is enough of an improvement, increased programmer productivity due to the superior tech. will outweigh the initial cost of learning.

    The net result of all this is that Trolltech has no reason at all to use the STL merely because it is a de facto "standard."

  25. Re:yeah! by flex941 · · Score: 1

    That's why I can't understand why nobody moderated it Funny.

  26. Re:C++, bad news by be-fan · · Score: 1

    I don't think you are understanding the purpose of a standard.
    I don't think you understand the purpose of a standard. The library standard defines what libraries all C++ implementations must support. The standard is there to allow programmers to assume that certain services are available on all implementations. The standard is not there to force all programmers to use a certain set of services that may not necessarily be the best ones to use.

    --
    A deep unwavering belief is a sure sign you're missing something...
  27. RTFA by philci52 · · Score: 1

    Gotta love the fact that this whole comment page is filled with plugs for WxWindows and arguments over licenses that I've heard 100 times. Qt is GPL, get over it, so is the linux kernel. You want a Qt backend for Windows, then visit sourceforge or pay up. I don't think anyone actually read the damn article and discuss the new features. The new paint engine, SVG and Unicode Text layout I'm really excited about. Not so much about the template stuff, although interesting.

  28. Trolltech, Canopy, and SCO by Anonymous Coward · · Score: 0

    No thanks, I'm avoiding QT like the plague.

    ScottM

  29. It does not work by Anonymous Coward · · Score: 0

    The non-commercial Qt windows version is delivered without source. The libary files are NOT COMPATIBLE with visual c++ 7.1 (Microsoft changed the lib format).