Slashdot Mirror


What to Expect From Qt 4

An anonymous reader writes "A presentation given by Matthias Ettrich (director of Qt development, author of LyX, and founder of the KDE project), was given to the annual KDE Developer's Conference in Nove Hardy, Czech Republic. In this presentation, Matthias details what's going to be new in Qt 4.0, which will be used as a base for the next version of KDE after 3.2. Apparently, Qt 4.0 will not only include faster startup times and lighter memory usage, but will have sweeping architectural changes, including a splitting of Qt's GUI classes and non-GUI classes."

58 of 386 comments (clear)

  1. It Sounds Nice by Jeagoss · · Score: 5, Insightful

    but, is it absolutely essential? In a time where code needs to remain compatible due to the large amount of projects that are depending on that code, huge architectual changes implemented in a large number at one time will just show that the project wont get used for quite a while. It will take time for developers to start supporting the new format, which will leave end users wanting.

    --
    Password Authentication Bypassed for Root
    1. Re:It Sounds Nice by siliconwafer · · Score: 4, Interesting

      The lighter memory usage and faster startup times sound very nice. Maybe not essential, but nice.

    2. Re:It Sounds Nice by Coventry · · Score: 4, Informative

      Remember, QT is a library, and trolltech makes their money from it. I'm pretty sure that all that will be needed for most apps using current QT is a recompile with the new tools (QT has a tool used as part of the Make process). To use the new features might require changes to code, but thats a different story - you're already changing your code to add new features.

      --
      man is machine
    3. Re:It Sounds Nice by stratjakt · · Score: 5, Interesting

      Qt 4 mostly tries to preserve source-compatibility with a little search and replace and a COMPAT compilation switch. More porting will be required for styles and code that uses the meta object system directly.

      Out with the old, in with the new.

      Developers can adapt or fail. It doesnt seem wise to quit working towards better systems because some guy doesnt feel like replacing his widgets.

      --
      I don't need no instructions to know how to rock!!!!
    4. Re:It Sounds Nice by Overly+Critical+Guy · · Score: 4, Insightful

      Why are Linux users so afraid of change? It's the very reason we suffer through so much legacy compability to slow things down.

      I welcome any sort of innovation. People will update their apps to meet any changes.

      --
      "Sufferin' succotash."
    5. Re:It Sounds Nice by ded_guy · · Score: 2, Insightful

      I dunno--sometimes things have to be broken to make them easier, faster, or more flexible or to allow for future growth. Or sometimes just because there is a Better Way. Look at the breakages going on in Perl 6.

      --
      In the future, all spacecraft will be made of cheese.
    6. Re:It Sounds Nice by Jeagoss · · Score: 2, Insightful

      I'm not saying change isn't good. Change is very good. The thing I see here is they aren't only implementing 5-6 new features and a small architecture change. Yes, they are trying to maintain source compatibility, but the style of coding is just far antiquated. Personally, when I write code, I implement a new feature, get it working very very well, and then move on to the next feature. This leaves room for other projects to implement the new feature, and start using it, while I then move onto the next feature. It proves to be a very stable, dependable method of coding. I'm not saying everyone should code this way, and I'm definitly not saying I'm better than everyone else. Rather, I am giving my unwanted $0.02. Coding in such a syle really lets people move forwared, in a very steady pace. Remember, the rabbit didn't win the race. The turtle did cause he was very steady and persistant.

      --
      Password Authentication Bypassed for Root
    7. Re:It Sounds Nice by Jeagoss · · Score: 2, Interesting

      Besides reading my profile, what is to say I am even talking about QT for a personal use, or even QT for linux. I work for a company that uses the Professional Version of QT for development of "in house" applications which run mainly on FreeBSD. Source compatibility isn't always the best thing. A recompile of our applications isn't the quickest thing either. And after the recompile, we still have policies that say we have to test the new compiled app for 2 weeks before we push it to the network, just to make sure everything is stable. Big change costs money. Our company is far from scared of change. We just need to consider the investment of time and manpower to cope with it.

      --
      Password Authentication Bypassed for Root
    8. Re:It Sounds Nice by Otter · · Score: 5, Interesting
      Developers can adapt or fail.

      Remember, though, that we're talking about volunteer developers. If they fail, there's no one rushing in to take their customers. I remember when the KDE 3 plans were being made, there was a recognition that KDE's weakness is in the number and quality of apps and so there was a goal of keeping the APIs stable for as long as possible.

      Now, greatly improved startup time would obviously be a huge reason to switch as soon as possible. Since pure Qt apps already start much faster than KDE apps, though, I wonder how much speed KDE would really gain.

    9. Re:It Sounds Nice by sketerpot · · Score: 2, Interesting
      From the article:
      Qt 4 mostly tries to preserve source-compatibility with a little search and replace and a COMPAT compilation switch. More porting will be required for styles and code that uses the meta object system directly.

      Not much Qt code uses the moc system directly, since this is deep black magic and typically a bad idea. They're preserving compatibility, and it seems like a pretty small price to pay.

  2. Faster? by Kenterlogic · · Score: 3, Interesting

    I have alwways preffered Gnome to KDE because of speed issues (and the new Gnome is a lot prettier). But if this new base is much faster, then I may be forced to start using KDE again. Then again, my G5 should be arriving soon-- so forget Linux.

    --
    The New Root Council, kickin' ass sinc
  3. Here's what I expect by Rosco+P.+Coltrane · · Score: 2, Informative

    Qt is great (well, if you like C++ and you don't mind the QPL), but there's really one thing I'd like: when will it ever have a font scheme that allows me to use AA fonts together with non-truetype X11 core fonts?

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    1. Re:Here's what I expect by DanMilburn · · Score: 2, Informative

      You're aware that the QPL is, more-or-less, an open source license right? People didn't like it because it didn't meet the Free Software Foundations definition of free (meaning that, according to a strict interpretation of the GPL, it was illegal to distribute KDE in binary form), so Trolltech started licensing it under the GPL, leaving the option of accepting the terms of the old license instead.

      As for dual-licensing it commercially and as free software, well, I don't see how that forces anyone to do anything. If you make non-free software, you pay the fee for a commercial license, and it's been that way since Qt was created. The growing success of Qt might encourage people to do this, but they're certainly not forced to. And if that happens, hey, Trolltech are successfully creating and supporting free software, and managing to make money. I don't see that as something to be wary of.

    2. Re:Here's what I expect by bongoras · · Score: 2, Insightful

      "There's nothing to stop Troll Tech from becoming unreasonable in their licensing demands... crippling all commercial KDE development. Since KDE is a desktop environment, commercial development is pretty important."

      Yes there is, it's called the GPL. If TrollTech decides to do something loathsome in a future release of Qt, the previously released versions will still be there under the GPL, and anyone who wants to will be able to modify it, fork it, etc to their hearts content.

      The GPL is what ensures that the freedom in free software -- both free as in beer and free as in RMS -- STAYS free.

    3. Re:Here's what I expect by be-fan · · Score: 2, Insightful

      So let's see. You want to use Trolltech's excellent toolkit, without paying them for it? Great... Hell, according to the FSF, stuff like this is supposed to be GPL'ed! Why do you think the LGPL is called "The Lesser GPL?" RMS says that "when a library provides a significant unique capability" it should be released under the GPL. Qt is one of the best GUI toolkits out there. Its a competitive advantage for free software projects like KDE to have it be GPL rather than LGPL.

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:Here's what I expect by be-fan · · Score: 3, Insightful

      They *can't* do that. The Free Qt foundation (made up of two members of TT and two members of the KDE Project) ensures taht Qt will always remain free. If TT goes away, or decides to discontinue work of the Free edition of Qt, the latest version automatically becoms BSD licensed.

      --
      A deep unwavering belief is a sure sign you're missing something...
  4. Trolltech and Canopy/SCO by bstadil · · Score: 2, Troll
    As you know 4% of TrollTech is owned by Canopy of SCO fame. We need to put some pressure on Trolltech to make sure that nobody from Canopy is on the board or has any saying whatsoever over Trolltech

    I have switched to Gnome until further

    --
    Help fight continental drift.
    1. Re:Trolltech and Canopy/SCO by be-fan · · Score: 4, Informative

      Dipshit.

      A 5.7% stake hardly makes TT a "Canopy puppet."

      Hint: Look at Canopy's website. Note that TT is listed under "Portfolio Companies." Understand that this in no way means that they are controlled by Canopy group. Hell, Microsoft owned about as much of Apple after their $150 million investment. Did that make Apple a Microsoft puppet?

      --
      A deep unwavering belief is a sure sign you're missing something...
  5. RTFA! by Anonymous Coward · · Score: 3, Informative

    Paragraph 2:

    "Qt 4 mostly tries to preserve source-compatibility with a little search and replace and a COMPAT compilation switch. More porting will be required for styles and code that uses the meta object system directly."

    How much stuff do you think uses the meta object system directly, aside from the internals of KDE?

    1. Re: RTFA! by Rimbo · · Score: 3, Interesting

      Jesus, I was wondering when someone was going to say this. Qt developers obviously aren't reading slashdot. other than you and me, that is :D

      I think the large number of complaints is that although source-compatibility is -basically- maintained, you still have to recompile your apps. One of the nice things Microsoft has done is that you don't have to recompile your Win32-based app to work in .NET -- well, not completely, anyhow. This does have the side effect of dirtying up the API a bit. So it's a trade-off. Backwards compatibility does make GUIs easier for people to adopt -- who wants to constantly have to download new apps to work with the latest version???

  6. Re:This is what I really want from Trolltech. by AugustMoon · · Score: 5, Insightful

    Big deal. There is no law against having your stock owned by questionable companies. Furthermore, no publicly traded company can really control who buys their shares. They are publicly traded, any one can buy or sell the ownership.

    It doesn't automatically mean Trolltech inherits all the vices of every one who owns shares.

    I would not be worried or even morally concerned until Trolltech's business decisions go south. Minor share holders don't dominate a company. Even 5.7% isn't a lot.

  7. New versions alway better in the long run by jj00 · · Score: 2, Interesting


    Now this is what I like about Linux; every time I think some annoying little thing about the interface/OS is really starting to annoy me, a new version comes out and something get tweaked to the way I like it.

    It's really the reason I have grown to like Linux so much: I can actually see the progress of its development moving forward. It seems in the past few years that Windows has just been moving backwards.

  8. What I would like to see.. by ErisCalmsme · · Score: 3, Interesting

    Is more apps that require QT but not all of kde to run. That's why I use gtk apps... because most of them dont require gnome. There are gnome apps of course, and there are progs like Gaim that will give you a little somethin' extra if you have gnome installed, but you don't need it... Are there any qt apps that dont require kde to be installed?

    --
    Chaos is Divine *
    1. Re:What I would like to see.. by Anonymous Coward · · Score: 2, Informative

      Yes, some of the common ones include

      Opera Web browser
      LyX word processor
      SuSE's YaST.
      Scribus destkop publisher.
      The Linux 2.6 QConf
      Kylix.
      YHBT Business books
      and hundreds more.

    2. Re:What I would like to see.. by AArmadillo · · Score: 2, Informative

      There are many. One of the advantages of Qt is that it provides a common interface to X-Windows, MS Windows, and Mac OS GUI programming. Qt is entirely independent of KDE, the only reason an application would be bound to KDE is if it utilizes the KDE extensions to Qt.

    3. Re:What I would like to see.. by RzUpAnmsCwrds · · Score: 2, Insightful

      "One of the advantages of Qt is that it provides a common interface to X-Windows, MS Windows, and Mac OS GUI programming."

      Thankfully, GTK+ also does this. Gaim/Win32 is proof of that. With the new Wimp skin, GTK+ even matches the Windows look, for the most part.

      Of course, there are also QT apps that I enjoy on Windows. MySQLAdmin, for one.

  9. gcc dynamic linking? by 4of12 · · Score: 4, Interesting

    A couple of years ago someone on the KDE team posted a nice analysis of the performance bottlenecks associated with dynamic linking, C++, and gcc, particularly as regards Qt use.

    So I have to wonder, with Qt 4, KDE 3, gcc 3.3, how many of the performance problems remain?

    --
    "Provided by the management for your protection."
    1. Re:gcc dynamic linking? by IamTheRealMike · · Score: 4, Interesting
      That's what all the talk about reducing number of symbols and relocs is about - KDE got hit really really hard by the way it requiries lots of fixup at startup time in the linker. In some cases it was THE biggest drain on startup time. By reducing the number of symbols in the code, you reduce the work needed to dynamically link it all, so improving the speed.

      Though, I can't help thinking that prelink is a better solution to that problem. But whatever, they are surely aware of that technology by now.

  10. Re:This might mean something to me by Bingo+Foo · · Score: 4, Insightful
    Their licensing scheme doesn't "suck." It's just incompatible with your goals, i.e. a free toolkit which you can use to create salable apps. If you don't like it, you can:
    1. Buy a Qt commercial developer license
    2. Release your own apps as open source
    3. Use a different toolkit
    It sounds like you have chosen #3. I'm sure the people at Trolltech are able to sleep well regardless.
    --
    taken! (by Davidleeroth) Thanks Bingo Foo!
  11. use of the standard library by Eponymous+Coward · · Score: 4, Interesting

    I'd like to see more use of the standard library. The traditional complaints of poorly conforming compilers is mostly just history. Except for support of the export keyword, most C++ compilers and standard library implementations are now quite good. Most platforms even have several excellent compiler / library combinations to choose from.

    Even though it would be hell for already existing apps, I would love to see use of standard library components rather than the re-invented QT versions. And even in those cases were the QT versions have extra features, I still think the advantages of using a library that is already familliar with most C++ programmers outweighs the disadvantages. Of course, that's just IMHO.

    ec

  12. Before you try to book a hotel room by SlashCrunchPop · · Score: 2, Informative

    I believe someone got the name of the town wrong, it's Nove Hrady and not Nove Hardy.

  13. QT4 by SlayerDave · · Score: 5, Insightful
    I have recently spent a good deal of time programming with QT3. While QT is the best C++ GUI library and application framework, I think it needs some improvement. Here are my gripes, in no particular order.

    First, the signal/slot mechanism really bugs me. I am annoyed with the need to use non-ANSI C++ techniques (e.g. public slots, moc) to achieve results that could easily be done with legal C++ code. While not strictly illegal, the use of the SIGNAL and SLOT macros, along with the Q_OBJECT macro, are not very good techniques. Specifically the reliance on macros to achieve basic GUI functionality violates a key principle in Meyers' "Effective C++", namely avoiding reliance on the preprocessor.

    Second, several GUI widgets do not have a proper separation of data from view. I am thinking specifically of QTable and QListView. A better approach, from an OO design perspective, is the one taken in Java Swing. The JTable and JTree provide a nice mechanism for separating the data model from the GUI display. I find it obnoxious to have to subclass QTable and build-in data model methods to achieve results that would be cleaner under a Model-View design paradigm.

    The QT online documentation is not easy to navigate. They should take a lesson from the Java API docs and reorganize the QT docs along those lines.

    1. Re:QT4 by SlayerDave · · Score: 3, Informative

      That's true, the Java API has a very large number of classes. But what I like about their docs is the use of frames, which is normally quite annoying, but is well-done in the case of JavaDoc. Also, you can select a particular package to view, such as javax.swing or java.util, which greatly limits the number of classes you have to browse. Also, I like the ability to see clearly what members are new in each class and what members are inherited and/or reimplemented. Also, getters and setters are listed together in the Java docs, but not in the QT docs. I think these features make the Java docs easier to navigate than the QT docs.

    2. Re:QT4 by SlayerDave · · Score: 2, Interesting
      It is matter of personal preference, to some degree. Personally, I prefer the EventListener mechanism in Java Swing to the signal/slot mechanism in QT. Of course, C++ does not support anonymous classes, but it does support inner classes with the same scoping (I think) as Java inner classes, so it would be relatively easy to write small Listener classes, registered with the appropriate widget, to handle callbacks and events. Again, personal preference.

      I should admit, though, that my main annoyance with the Qt signal/slot mechanism is that it confuses Emacs, screwing up indentation and syntax highlighting. Annoying, but not enough to make me stop using QT.

    3. Re:QT4 by chowells · · Score: 2, Informative

      Well plenty of KDE developers use emacs/xemacs so presumably with the emacs scripts things in kdesdk so presumably it is possible to get emacs sorted :)

    4. Re:QT4 by Arandir · · Score: 2, Informative

      First, the signal/slot mechanism really bugs me. I am annoyed with the need to use non-ANSI C++ techniques (e.g. public slots, moc) to achieve results that could easily be done with legal C++ code.

      There is no ISO C++ mechanism that does the same thing that signals/slots do. None. None at all.

      Now before you start talking about Boost::Signals, libsig++, gtkmm, etc., take a step back. Those things you're talking about are libraries, just the same as Qt. They are not standard mechanisms any more than gettext or libxml are standard mechanisms. Every bit of the code that is in Qt to implement signals/slots is standard ISO C++ code. No different than with Boost::Signals.

      And as opposed to those other "standard" mechanisms, Qt signal/slots are extremely flexible.

      The QT online documentation is not easy to navigate.

      You have been smoking crack, haven't you? Despite it's unfamiliarity to those children raised on the Holy Bible of JavaDoc, the Qt documentation is a breath of fresh air when it comes to the dissemination of useful information. No other body of technical documentation anywhere in the Open Source world even comes close.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  14. I'm not so sure its a good idea. by HanzoSan · · Score: 2, Insightful



    I agree with you exactly, it sounds nice but why do we need to change an architectual change when the current QT architecture is the best there is?

    Why fix what isnt broken? Especially when you are ahead of the curve and on the cutting edge? Why not polish what you have? Thats the exact problem Gnome has, they keep restarting and redoing everything and they get NO WHERE.

    KDE 4.0 would be better if it were based on the current QT because it could be polished, if they instead have to rewrite alot of code for a port, this is going to slow Linux on the desktop, and for what? A tiny bit more speed? I want to be sure that the benefits outway the cost here. The cost being time.

    --
    If you use Linux, please help development of Autopac
  15. Why turn KDE into Gnome? by HanzoSan · · Score: 4, Insightful



    This is the exact problem Gnome has. They keep messing around under the hood and nothing changes from the user point of view, development is moving at turtle pace because developers who want to write gnome apps cant figure out what to use because some new bonobo/mono type thing comes out every 6 months.

    Developers need stability if they are going to work on big projects, we need at least a few years before a big re-write. I cant develop for Gnome because everytime I try to start they change something.

    --
    If you use Linux, please help development of Autopac
    1. Re:Why turn KDE into Gnome? by IamTheRealMike · · Score: 4, Informative
      I guess you'll be pleased to hear that GNOME 2 remains fully backwards compatible throughout the 2.x cycle - in the history of the project, it's broken compatability in a major way only once, compared to KDEs 2 times (though 2->3 was extremely trivial for 99% of apps).

      Mono is entirely irrelevant - it's not related to the GNOME project other than having Miguel/Ximian involved, and you are certainly not forced to use it to write GNOME apps.

      Basically, I think you're misinformed - if you write an app for GTK2/GNOME2, it will continue to work for quite a long time, until the next major revision (which is going to be needed simply in order to properly sync KDE and GNOME around standards eventually anyway). So, I don't know what you're complaining about really.....

  16. Very nice. But they forgot one minor thing: by master_p · · Score: 4, Interesting

    I don't have any major complain from Qt, as I have been using it a lot in our company and found out that it is the best.

    I only have this problem: the TreeView widget is single-linked. This a major problem for us, since our apps contains lots of trees. We have to do a lot of tricks, like keeping a pointer to the last item all the time.

    I've posted this on the Qt newsgroup but I was ignored. Although many people have complained about it, Qt engineers ignored us. I think they should fix it in version 4.

    Other than that, Qt is indeed the finest toolkit out there. It simplifies development a lot, and it fills the great void that exists in C++ libraries. It's really like the Java libraries or the .NET libraries, providing almost everything needed under the sun.

    The biggest advantage of it is that it works as expected; in other words, you just create one widget inside the other, and voila, there is the app's gui. You can even do it programmatically, without the KDesigner.

    Finally, it does C++ justice. It's the only library that shows how powerful C++ can be. After having used Qt and Java, I may safely say its up on par with Java...even better I would say, since it uses all of C++ capabilities, including the most important one: templates.

    1. Re:Very nice. But they forgot one minor thing: by swillden · · Score: 2, Funny

      Except that it costs way more than the MS development tools... Shame because it is a decent cross-platform kit.

      Yeah, Microsoft's cross-platform development kit is much cheaper.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  17. Re:This might mean something to me by phurley · · Score: 3, Interesting

    I use and enjoy wxWindows, but I do not think your criticism of QT and their licensing is very fair. They have a completely free license (GPL) which you can use - to create completely free applications. They have commercial licensing (admittited too expensive for "shareware" type applications).

    There is a completely reasonable middle ground where you can release your application as GPL code - which you can legally sell for any price you want - yes you need to provide the source code to your customers (not a bad thing) and yes they can then give it away to their friends, family and even people they pass on the street - but if your application has true value - they will probably be more than willing to pay for it (especially if it is as low cost as you claim). Many users are not sophisticated enough to compile their own binaries and the making the "official" binaries what you sell - is legal.

    Now if you are just upset because they will not give you (or sell at the price you pick) their library for you to use in closed source for profit applications, then it is far better that you found a different library.

    --
    Home Automation & Linux -- now I know I'm a geek
  18. Hahahaa no we didnt by HanzoSan · · Score: 2, Informative



    Japan has a better powergrid than ours. Who gave you the idea that we had the best in the world? DO not assume our system is the best just because we are the USA. Japan has alot of things better than us, as does Korea. Japan has the best power grid in the world, the most efficient public transportation in the world, the best cellphone technology in the world. They also have better robotics than us,

    South Korea is the most wired country in the world, with the best internet technology in the world.

    just because its USA does not automatically equal best.

    --
    If you use Linux, please help development of Autopac
  19. GTK - nyed! by Moritz+Moeller+-+Her · · Score: 4, Informative

    Most of the applicatons you presented as GTK apps do not use GTK widgets:

    Openoffice/Staroffice does not use GTK at all (in fact the first SO port to Linux was done by Matthias Kalle Dallheimer, a KDE founder...)

    Mplayer has an optional GTK gui, which is hardly used by anyone. It also has at least two KDE guis. Not a very good GTK app.

    XMMS has it's own GUI, GTK is basically used for the file dialog, which is arguably not the most impressive part of GTK.

    Mozilla/Netscape uses XUL, it's own toolkit, again no GTK widgets are used, just some basic drawing routines.

    This leaves GIMP (functional, but ugly) and GAIM (never used it, AOL is not my thing) for GTK.

    --
    Moritz
  20. How about more standard C++ by Ed+Avis · · Score: 3, Interesting

    Is it too much to ask that the next Qt will use the standard C++ string class instead of its own reinvention and kitchen-sink-itis that it suffers from at the moment?

    --
    -- Ed Avis ed@membled.com
    1. Re:How about more standard C++ by Ed+Avis · · Score: 2, Interesting
      Well, to be honest, the QString class is substantially more powerful than the C++ string class. Most especially in casting to and from other data types.

      boost::lexical_cast

      Well, okay, I'm proposing a third party library to provide what Qt's string class has built-in. But in a way this illustrates an advantage of using the standard string (or other standard classes) rather than rolling your own. You are able to take advantage of lots of third-party code, including the excellent work at boost.org.

      Moreover, it supports the full range of internationalised characters,

      You can make a basic_string of whatever character type you wish, including wchar_t. I guess it's unfortunate that the standard 'string' is an alias for basic_string<char, ...> instead of using 16-bit or 32-bit characters, but it's not a disadvantage of the string class itself.

      it automatically casts as neede and passes by value as needed as well.

      The standard C++ string has value semantics, so you can pass it by value (and usually do so efficiently). In this respect it's just like an int - you can pass and return strings by value, and two strings are equal iff they have the same characters.

      I'm sure the Qt string class is great, the question is, is it so much more wonderful that it justifies being different from the rest of the world?

      --
      -- Ed Avis ed@membled.com
  21. Re:use of macros in C++ by js290 · · Score: 3, Informative

    Ever tried stepping through code with a debugger that's full of macros? Not fun, unless you like printf's. As far as Troll Tech using macros for their signal/slots, I don't care as someone using their toolkit. One less abstraction to worry about.

    --
    "Tempers are wearing thin. Let's just hope some robot doesn't kill everybody." --Bender
  22. Not exactly necessary... by Moritz+Moeller+-+Her · · Score: 2, Informative

    Just start e.g. kmoon or klipper. KDE and GNOME use the same docking protocol, so any existing docked program would suffice.

    --
    Moritz
  23. AC Comment from other Canopy Employee by bstadil · · Score: 3, Interesting
    Since my comment has been modded a Troll I think you should read this posting from another Canopy Company employee.

    Quote:

    As an employee of a company in the same office buildings as SCO and partly funded by Canopy Group, I strongly encourage a boycott of all companies funded by the Canopy Group.

    There was a lot of buzz about mergers a few weeks ago. It seemed that everyone was going to join into one large company called, you know it: SCO! .......

    --
    Help fight continental drift.
  24. Re:This might mean something to me by Cthefuture · · Score: 2, Interesting

    As others have mentioned, the problem isn't that we don't want to pay for a license.

    I have no problem paying for QT.

    I have a MSDN subscription in fact. That MSDN (Professional) was around $1000. Not too bad considering you get every single MS OS and the whole development environment (C/C++, C#, Java, VB, etc.) and all sorts of other bits. For the most part Microsoft is very good to their developers (hey, they make them money).

    Compare that with QT which is around $3000+ for all three platforms (or what, $1500 for one platform?!). And it's only a GUI toolkit (sure, with some extra "fluff"). Way, way too expensive for what it does. If QT was $1000 for all three platforms, then I'd own several copies And many, many other people feel the same way. Their license prices are holding them back. They would have so, so many more developers working in QT if their prices were reasonable. That would only help them in the end as I have a strong feeling the world would become more QT-centric (I mean, it is a pretty good GUI toolkit; although the current stuff is rather slow).

    --
    The ratio of people to cake is too big
  25. Backwards compatibility is important by ZorinLynx · · Score: 3, Insightful

    Sigh. I really hate to say this, but I must agree with keeping API's backwards compatible across versions of libraries.

    I've been using Linux for years now, and one of the biggest annoyances is that software packages tend to be tied very closely to a specific version of a library. Without backwards compatibility, you sometimes need to have two or three different versions of the same library installed in order to use different applications.

    When a library is used by a wide variety of applications, like Qt, GTK, libc, and so on, backwards compatibility should be ensured. Yes, this means the library may be a bit more bloated than it has to be, but the bloat isn't as bad as the bloat that results from having to install an ancient version of Qt in order to run an app that hasn't had active development for a few years.

    This is coming from someone who doesn't do much software development; I just maintain a lot of systems and software libraries.

  26. Re:HTML rendering by julesh · · Score: 2, Interesting

    Have you looked at this to solve your windows portability needs?

    http://kde-cygwin.sourceforge.net/

    It uses cygwin, which might mean some user confusion with filenames; if that's an issue for you you might want to forget about it. Also it'll mean you're stuck with GPL. Otherwise, I understand the results are quite impressive... if you don't want to use X, you can probably substitute the windows version of Qt, and everything should work OK. It'll be a lot of work to get it going, but after that it should be stable and usable...

  27. Moderators Suck ... by Anonymous Coward · · Score: 2, Interesting

    Troll? Come on guys, we're not bashing Apple.
    You don't have to throw a hissy fit cuz someone's bashing your fave tool.

    from http://www.pclinuxonline.com/modules.php?mop=modlo ad&name=Forums&file=viewtopic&topic=870&forum= 37
    As an employee of a company in the same office buildings as SCO and partly funded by Canopy Group, I strongly encourage a boycott of all companies funded by the Canopy Group.

    Taking money from Ralph Yarrow (Canopy) made all of us sick to our stomachs but we held our noses and moved into their offices in the hope their stake would stay small. And we were out of business if we didn't.

    There was a lot of buzz about mergers a few weeks ago. It seemed that everyone was going to join into one large company called, you know it: SCO! That buzz ended yesterday. Now the talk, all over the group, is how to distance ourselves from SCO and Canopy. The mention of our company on Slashdot resulted in very negative feedback and two potential customers walking away. Other's got it even worse. I hear Trolltech spent most of the day on the phone smoothing things over with their customers. Upper management meetings were held all afternoon among the group's companies (I'm not privvy to those, but can guess the subject matter). Companies that were considering a merger with SCO (some as close as 5 days away) are now backpedalling as fast as they can.

    Canopy Group is the key to pressuring SCO. Thats where they get their money and their actions could harm the whole group and Canopy's plans. Pressure on the Canopy Group's members will result in pressure on SCO.

    Save me from SCO! Boycott Canopy Group. If they want to point a gun at their own head, I'd rather they do it away from me. Write letters to the all the Canopy Group companies. We are all very small and even a few letters would have a major effect. The three we received yesterday sent management into a tizzy. Oh, yeah. And start at the bottom of the alphabetical list of companies, please.

    Thanks for listening...

    -------- more --------------

    Ignoring your personal attacks, the point remains that the pressure point here is Canopy and their group members. SCO could care less about a boycott, Canopy will continue to funnel money to them. The key is Canopy and Canopy is vulnerable through their holdings.
    Ralph Yarrow cares about only one thing: the bottom line.

    Only three emails to my company convinced mangement that there was a problem. They spent most of the afternoon in closed door meetings deciding on how best to distance themselves from this mess (at least that was the discussion when I was called into offer my opinions). They dreamed of the day we would be slashdotted, but are very dismayed that when it finally happened, it was entirely negative and harmful. From my colleagues in other companies, I gather the scene was common all over the office park yesterday. A couple hundred more emails will have a dramatic impact. The pressure will proceed directly from companies of the Canopy Group up to Ralph. When he sees the bottom line being attacked he will rein in SCO.

    Some have said that it is unfair to punish the other companies. But the other companies are already being punished for SCO's actions. We have already lost potential customers who informed us they did not want to be associated with Canopy/SCO in any way. My product's release date has been placed on hold indefinitely while this uproar is going on. I fear this nonsense will ruin us. It would be foolish to start the rollout under this dark cloud.

    The party line from SCO is that the opposition is from just a few disgruntled 'pot-smoking hippie-types' that can be ignored and they will go away. (From an overheard conversation in the restrooms. No doubt, Monday morning SCO employees will receive news of a new policy about talking in the restroom. But it wasn't the employees forgetting to check the stalls before tossing around disparaging remarks).

    Give them a reason to

  28. KDE Conference Talk Writeups by JRiddell · · Score: 3, Informative

    Writeups of the talks I went to are at:

    the Nove Hrady wiki.

  29. Qt 4 vs Qt 6 by egommer · · Score: 3, Funny

    I don't know why you all are worried about QuickTime 4 f. I personally use QuickTime 6 on my iMac. Sheesh. You can't even see the latest pron and movie trailer's with Qt 4. Oh Wait... I think this is somthing else.. Damn you! you- 133t linux users fooled me again.

    --
    Two Towers-Two Worlds.One seeks triumphs and freedom for man.The other deems man unworthy and wrecks them.
  30. Qt on DirectFB by dok666 · · Score: 2, Informative

    You might want to have a look at this new QtDirectFB screenshot:

    http://www.directfb.org/screenshots/FirstQt.png

    I'm really looking forward to having the KDE libraries independent from QtX11.

    Best Regards,
    Denis Oliver Kropp

  31. Re:I use linux but IANALH (I am not a linux hacker by be-fan · · Score: 2, Interesting

    Qt4 will definately help in some ways. In particular, the fact that all widgets will now be double-buffered (instead of just most of the widgets) means that a lot of tearing will go away. Startup time should be reduced a little bit as well. Hopefully, a lot of work will go into fixing synchronization issues, which is the real problem holding back X-based GUIs.

    KDE itself is getting much better. I'm using a CVS version of KDE, and can say that things are *much* faster. Konqueror starts instantly, and most apps start in less than 2 seconds. Konqueror has zero rubber-banding when resizing medium-complexity websites, and hardly noticible rubber-banding when doing reflow-heavy sites like Slashdot. The KOffice apps are all very fast, none exhibit any rubber-banding at all and all start up in a couple of seconds. All the standard widgets are really fast --- Juk for example, resizes with zero redraw even with a 2000-item listview. The only apps that really need work are those that use custom views or widgets (like Konqueror).

    My setup is KDE CVS from Aug. 8, 2003. I'm Gentoo 1.4 on a 2GHz P4.

    --
    A deep unwavering belief is a sure sign you're missing something...
  32. Re:Wrong... by 10Ghz · · Score: 2, Insightful
    The absolute success of KDE means that Troll tech will have a monopoly over commercial entrance to the Linux Desktop. Given that, why should anyone want KDE to become a standard desktop?


    Because KDE is superior to the alternatives? And if you write free software, you don't need to pay one dime. I fail to see the problem. And if TT starts to abuse it's power, users would migrate to other toolkits.

    Yes, I recognize that other toolkits can interact with the KDE environment, but if you need to use other toolkits or explain why Troll tech can exact a fee, why even support KDE as a standard desktop?


    If you can't recoup the cost of Qt-license, then you should REALLY reconsider your desision to write closed, commercial software, since there obviously isn't that much demand for it.

    It's not the money itself, it's the long and complex explanation as to why purchasing would have to be enaged to develop for a "free" software platform


    If you write free software you don't have to pay. If you want to write closed software, you have to pay. I fail to see the problem. WHy should you get the right to write closed software but you want to deny TT the same right? If you use their tools for profit, you need to pay them, IMO that is fair.

    Win32 doesn't even have this problem, and Gtk certainly doesn't have this problem.


    Then use Win32 or your precious Gtk, I fail to see the problem.
    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.