QT/Win 3.3.3 To 'Reach Production State Soon' 114
sebFlyte writes "The KDE Cygwin team are reportedly closing in on a native port for QT to allow said graphical framework to run over Windows. This has upset a few people, who think that porting open source apps to Windows is strengthening MS's near monopoly and damaging Linux." (Of course, KDE also runs on OSes besides Linux.)
I disagree (Score:5, Insightful)
As for QT running in Windows, I think this would be great. I'd love to use Amarok and k3b when I'm in Windows.
Re:I disagree (Score:2)
Except about the k3b, I can't stand to use it in Linux, I can't imagine why anyone would want to in Windows.
I am curious... (Score:2)
Re:I am curious... (Score:2)
I much prefer gcombust.. It's similar to Buckley's cough syrup. It's ugly as sin, but it works every time.
Re:I disagree (Score:5, Insightful)
In plain English:
When you run platform independant applications you can run them on any platform. Switching platforms becomes more like the switch of a back end. The user is oblivious to the back end.
Microsoft recognise this, why can't we? (Score:2)
Thankfully, their efforts along these lines in the past have mostly come to nought. Does anyone remember Blackbird? Or the original MSN?
Re:I disagree (Score:5, Interesting)
That way the next time someone offers them proprietary software they'll ask
And when the answer comes back "no no no" they'll say "no thank you" to proprietary software.
Re:I disagree (Score:1, Interesting)
Re:I disagree (Score:4, Interesting)
Re:I disagree (Score:1, Insightful)
Of course, that can be good or bad depending on how much you love the GPL. BSD license people probably like GTK better because LGPL is closer to their license.
Re:I disagree (Score:2)
I think that this is cool news, as the reason for OS is to keep options open and to promote open standards... To deny windows this app would be as bad as the 'enemy'.
Re:I disagree (Score:2)
Re:I disagree (Score:1, Insightful)
Re:I disagree (Score:3, Insightful)
Moving directly to Linux means a forced change of all software at once. As a rule, users hate sudden changes. I love the fact that I can now recommend a whole suite of Open Source software to my unfortunate Windows-using friends. Since they've already bought their machines, it's too late to avoid paying the "PC tax." But if they can become accustomed to using almost entirely OSS, their next system purchase can easily come pre-installed with Linux instead. Create the de
Re:I disagree (Score:2)
Re:I disagree (Score:1)
A glance at the freshmeat [freshmeat.net] page would agree, but it appears the homepage is down
Bill.
Re:I disagree (Score:2)
Not to say that it would be very difficult to create a "drop-in" cdrecord clone that uses Windows's CD burning system...
Windows (Score:2, Interesting)
Linux doesn't have to kill Micro$oft Bill Gates is doing a fine job on his own.
Re:Windows (Score:1)
Re:Windows (Score:1)
Re:Windows (Score:2)
Re:Windows (Score:2)
1) Microsoft Office
2) Wordperfect/Corel Office
3) Lotus' old office suite
4) OpenOffice
5) Piecemeal office products (LyX, Mindjet, Filemaker, etc...)
Re:Windows (Score:3, Interesting)
Sure, there are millions of apps for Linux, but you know how many of them most Windows users know? 0. The problem is not lack of apps--the problem is familiarity with the apps.
Let's say you sit a Windows user down in front of a nice KDE desktop and ask them to try to chat with their friend on Yahoo Messenger or burn a CD or crop a digital photo. Th
Re:Windows (Score:2)
Re:Windows (Score:2)
Re:Windows (Score:1)
Maybe his phone wiring is so shoddy he cant use dial up above 32kbps (like me. it sucks - thank god for open 802's)
Dial up used to be acceptable for installing windows, not any more. When's the last time you checked to see how much downloading updating WinXP (from base install to fully updated) takes?
Re:Windows (Score:2)
I had an installation of XP Pro on my desktop machine. The hard drive died on it, and I had recently replaced the motherboard (and I was using the onboard NIC and sound card). Thus, when I went to activate Windows XP via the Internet, it refused (too many components were different - apparently the MAC address of your NIC carries a lot of weight for
Not so. (Score:4, Interesting)
Re:Not so. (Score:2)
The operating system really shouldn't do much more than allow applicat
WTF (Score:4, Insightful)
Re:WTF (Score:3, Informative)
In short, the Qt version for Windows is only available under the GPL/QPL license for an ancient version, 2.3.0 I believe. There is a GPL version for 3.3.3 for X11, but the modern Windows versions are only available under a commercial license. Thus, I assume the KDE are modifying the X11 one to run natively under Windows so that they can use the GPL licensed version.
Re:WTF (Score:2)
Re:WTF (Score:2)
Maybe you missed the fact that the new Windows dual licensing applies from Qt 4.0 onwards. This effort is for Qt 3.x.
Qt 4 is (a) not entirely backwards compatible and (b) not available yet.
Re:WTF (Score:2)
Re:WTF (Score:4, Insightful)
Possibly, but when the KDE-QT porters began their project, they didn't know that Trolltech was going to change licenses.
I wonder if Trolltech changed licenses because of the porting project...
Re:WTF (Score:1)
To some extent, certainly, but it's not entirely redundant, as QT 4 will not be 100% backwards compatible [trolltech.com]. In other words, many QT 3 applications will not necessarily compile with QT 4, and their authors will not necessarily want to update them immediately - or at all.
So there may in theory be some situations in which having access to a Win32 version of QT 3 will enable people to
Re:WTF (Score:2)
Apparently you didn't notice, but I actually linked to it in my comment. I thought a lot of the discussion in that story was relevant and did a better job explaining the subtleties than I could do in a short amount of time.
As you correctly point out, this port of 3.3.3 is probably going to be useless as of 4.0 because of Trolltech's annoucement, but I thought I might explain the reasons why it
Re:WTF (Score:2)
Re:WTF (Score:2)
GPL qt (Score:2)
QT runs on MS windows, but there is no GPL version that runs under MS windows. (at least not an up to date version, there are free-licensed older versions)
Now the most recent stable qt for X11 has been ported to run native under MS windows. Some speculate this is a motivation for making qt 4.0 GPL under Ms Windows.
Maybe I Don't Understand... (Score:5, Informative)
Re:Maybe I Don't Understand... (Score:4, Interesting)
Perhaps not... one might speculate that Trolltech released Qt for Windows under the GPL specifically because the port was almost there. Also, Trolltech claims that their GPLed version doesn't come with tools that will work with Visual Studio, whereas the public port does.
Furthermore, does this mean we'll see an influx of Qt apps being ported to Windows now that they're free to use Qt on that platform?
One would hope. There are certainly some KDE apps that I'd like to be able to use on Windows.
Re:Maybe I Don't Understand... (Score:4, Informative)
Re:Maybe I Don't Understand... (Score:5, Informative)
second time this has happened (Score:3, Interesting)
Now, people undertake the effort to port Qt to Windows under the GPL, and after they have invested a lot of
other os's? (Score:2, Insightful)
Re:other os's? (Score:2, Insightful)
In theory, sure; I'm using Firefox, Blackbox, GIMP, et al. on my Windows box right now, but switching to *nix is highly impractical for me. Why? I have a Radeon 9800XT and an Audigy 2; support for these sorts of things is piss-poor in *nix at the moment. If GNU/Linux wants to attract the
Re:other os's? (Score:2)
I waited almost a year for performance drivers from ATI before, in January, buying a Nv card. I hate that I sound like your average slashbot in this but you actually have a choice, buy hardware you know is working on Linux.
Unless what you meant is "no games work reliably on Linux" - I'll agree with you. I'm a great fan of cedega but I realise it's not for everyone and the 60USD a year is non
Re:other os's? (Score:2)
I used to say the exact same thing... Now I just say to heck with it and use Windows anyway (except at work where I do Linux development, and my tools will only run under Linux). Windows gives me a PC that works out of the box, and with 2000/XP, it works very well. I would use Windows at work if I could actually rebuild the cross-compilers and be 100% sure that I'd get the same binary cod
Re:other os's? (Score:2)
Re:other os's? (Score:2)
I'll admit that I'm a pessimistic and cynical person... Most places where you buy computer parts, they don't even know what the heck they're selling you, never mind whether or not it will work with Linux. Unless you encounter somebody knowledgeable, you'll get the wrong answer either way.
Going for the one with Linux support also often means getting a product
What? (Score:4, Funny)
Re:What? (Score:2)
Re:What? (Score:1)
Re:What? (Score:2)
Re:What? (Score:2)
great.... (Score:4, Interesting)
another library to suck up more RAM/CPU cycles on my windows box.
Lets see what I've got running
Standard win32 controls / libraries
GTK+ controls for GAIM/GIMP
Whatever the heck iTunes uses
Java windowing stuff...
Firefox's XUL and XPCOM.....
and now QT -- all to provide the exact same functions.
nice! Has it ever occured to anybody here that this is a little excessive? Personally, I'd lean twoard an OpenSTEP like implementation as shown in the demo posted to
I don't want an inconsistent user experience. I want my dialogs / menus / print box / file manager to be the EXACT SAME IN EVERY APPLICATION I RUN. I don't care if Linux or MacOS look a bit different than windows. All I care is that Windows looks like Windows, Linux looks the same all around, and Mac Looks like Mac. It's really not a hard concept.
Re:great.... (Score:5, Interesting)
Imagine a QT-GTK-Windows-wxWindows-SWING-Cocoa-etc. Program using absolutely any GUI style coding you know, and let the catch-all library intercept the call, and pass it to whatever windowing system you want. I know this will be rough work, but where virtually all windowing systems do the same thing, I'm sure it can be done. The hardest part will be tearing apart the Macros that each implementation uses, and then optimizing it once you've stripped it to its most verbose state.
Then the problem won't be "What libraries are in RAM?", but instead "Which can perform the interpretation from X to X fastest?". More kudos to QT-GTK, but I hope it keeps going.
Re:great.... (Score:2)
Re:great.... (Score:1)
definitely a better approach than rewriting each toolkit for each primitive drawing system...
Re:great.... (Score:2)
We're pretty much there. On Windows XP, there's a system library called themexp.dll that accepts primitive UI calls ("draw a listbox frame", "draw a button"). It's what takes care of the switch between the new XP look and the older classic Windows look.
Qt (the commercially licensed one from Trolltech, don't know about this new GPLed port), GTK and Mozilla's stuff all call down into this library to
Re:great.... (Score:2)
You can have an API-soup low level lib which higher levels libs write to.
You can have a simple low level lib which higher levels libs write to but don't try to expand upon.
You can have a simple low level lib which higher leve
Re:great.... (Score:2)
Xlibs real
Re:great.... (Score:2)
Okay, grea
Re:great.... (Score:2, Insightful)
By saying, "Personally, I'd lean toward...", you've demonstrated exactly why there are so many implementations of the same concept.
Re:great.... (Score:2, Interesting)
Re:great.... (Score:2, Insightful)
Which "standard" Win32 controls would you be talking about?
The ones build into user32.dll? Those don't even include a listview.
The ones in CTL3DV2.DLL?
The ones in MFC?
The custom stuff that Microsoft comes up with for each new version of Office?
The Windows.Forms stuff that most .NET applications use?
The notion that there's a "standard Win32 set of controls" is a myth.
Re:great.... (Score:2)
And how does adding another toolkit and language into the mix reduce the diversity?
Apple's already proven it to be successful/easy to the point that most developers choose to rewrite their frontends using cocoa instead of using a ported windowing toolkit.
You're kidding, right? A huge number of applications on OS X use Carbon, and many of those are toolkit wrappers around Carbon. In fact, it is quite common to see Carbon, Cocoa, Mozilla, Gtk+, Qt, and Ja
my humble opinion (Score:3, Insightful)
having an open-source QT and KDE on Windows encourages QT's use, making it easier by far to port these applications across multiple platforms. likewise with TK and GTK+ and xWidgets. since these toolkits work on linux, having a Windows port and encouraging their use ultimately brings more applications to linux by expanding portability.
this is why i like the Cygwin project: it brings a full POSIX layer to Windows that makes it easier to port applications back and forth. another benefit is that a Cygwin application with a working linux port gives end users one more avenue to make transitioning to another platform easier.
the ultimate benefit won't be immediate by any means, but portability sure brings it close....
Huh? Why? (Score:4, Insightful)
The article says that they are getting ready to release an updated version of Qt for Windows for GPLed software to use. So far this is much like article posted a few days ago.
But the article here talks about this being important so that people can run KDE (the desktop environment) on Windows without having to rurn Cygwin. Now while I understand not wanting to use Cygwin (it works, but it feels like a hack because in a way it is). That said, here is my main question:
Why would you want to run KDE on Windows. I understand the "because you can" theory (which is cool), but does anyone actually want to do this full time? Why? Why not run Linux or BSD? I understand wanting to be able to run GPLed software that uses QT (JuK as one example, or other such software, maybe even Konq), but why KDE?
Can someone explain?
Re:Huh? Why? (Score:2)
I would. I dual-boot, because I have to run Windows for certain purposes (ie, not games). Cygwin is OK, but the way that Windows looks and acts kinda ruins it. I'd love to use KDE's WM on Windows, for consistency with my Linux install if nothing else.
Re:Huh? Why? (Score:1)
Re:Huh? Why? (Score:2)
KDE has a nice file explorer than Windows and it comes with tons of useful applications that are all integrated well together. Yet, by running it on top of Windows, you still get full Windows compatibility for commercial apps. It's a good thing for people who would like to use KDE but are forced to use Windows.
(The same argument works for Gnome on Windows)
Qt doesn't matter;KDE doesn't matter; KOffice DOES (Score:1)
Then there is Qt to challenge gdi32.dll. Great too, but won't change at Nasdaq.
Now we have KDE to challenge user32.dll. OK, great too, we continue the track. Still, none of my loosy users will notice anything. Technically, or for the lawyer, sure it is great. Fonctionnaly, this is widely different.
Next on the track is, of course, KOffice. And this is the place where these people will actually notice some
Re:Huh? Why? (Score:2)
Ever use LiteStep? What do you say to LiteStep users? Do you say "Why not just use NeXT?"? "Why not just use AfterStep or WindowMaker?"?
Do you like commercial games?
Do you see my points?
Re:Huh? Why? (Score:2)
But why KDE the desktop environment? I don't see how there is much of a call for that at all.
Re:Huh? Why? (Score:1)
Re:Huh? Why? (Score:3, Informative)
That and I find myself consistently annoyed by various things about windows: single entry clipboard, lack of "Always o
Re:Huh? Why? (Score:3, Informative)
Because the Windows desktop sucks. Of all the desktops out there, Windows is the worst. Hear me out! I'm not talking about installing applications (even though I prefer package managers to installers), because that's not the "destkop". I'm not talking about the plethora of drivers for Windows, because that's not the desktop either. And I'm not talking about the feature packed-ness Word, Visual Studio or Outlook, because again, those are not the desktop.
There is not z-o
Re:Huh? Why? (Score:3, Informative)
Qt apps on Windows will help Linux (Score:5, Insightful)
This has upset a few people, who think that porting open source apps to Windows is strengthening MS's near monopoly and damaging Linux.
There are two sides to this argument and if you state them both, I think it's very clear which one is stronger. They are:
Now, what are the odds that any one unfamiliar app, or even a large set of unfamiliar apps are going to be so good that they'll convince people to undergo a wrenching transition in which they have to learn an entirely new environment and application set? I won't say it's impossible, and I will say that a number of my relatives have lusted over KimDaBa when I showed it to them, but I have a hard time imagining anyone but a geek who is interested in learning new computer systems for the sheer joy of doing it will be willing to put themselves through a complete change of their daily computing environment. Hell, I'm a geek and I dual-booted for a long time, and still use some Windows apps under Wine and VMWare.
On the other hand, it's a fact that to most computer users the operating system is beyond irrelevant -- it's invisible. "What operating system are you using?". "Umm, I think it's Internet Outlook XP". What matters is the applications. And most users are willing to look at something new, from time to time, if it's not too difficult, and if it doesn't prevent them from falling back on what they know when they need to get some work done.
I think it's extremely clear that if your goal is to break the Microsoft monopoly, the first thing you have to do is provide, bit by bit, a comfortable set of cross-platform tools that run well on Windows. Even now many who might like to migrate away from Windows can't do it because they're locked in by Office, Outlook/Exchange, and IE. Let them slowly migrate to open source replacements and then one day they will suddenly realize that everything they do on Windows can be done the same way on Linux, or a Mac, or whatever, and then Windows will suddenly find itself having to compete on its own merits, not on the strength of its application set.
Trying to "lock" people into Linux by providing an application set that only runs on that platform is trying to beat Microsoft at their own game. Open source lives by different rules, and if it's to be successful it has to play by those rules, not co-opt Microsoft's.
I, for one, welcome the porting frenzy to come, and look forward to introducing my Windows-using friends to some of the great open source apps I love.
Mixed thoughts... (Score:2)
Waiting for Gentoo/Windows (Score:1)
I can now see Gentoo/Windows on the horizon.
Re:Waiting for Gentoo/Windows (Score:1)
Linux Hoes (Score:2)
Have we forgotten? (Score:3, Informative)
It was the KERNEL!
Getting people to run GNU apps on "real" Unix came first. Perhaps we can get people to run good apps and a good desktop on Windoze, then bring them over to Linux.
And even if we don't we open up a whole new area for the superior, Open Source apps!
How opensource took over Unix (Score:5, Insightful)
-- Free software for most apps they cared about
-- Free software to extend their OS enough to make it functional
-- Solaris apps where they weren't getting any additional value
-- at most 1 or 2 commercial applications for Solaris from vendors that had no particular loyalty to Sun and weren't at all unwilling to bring out Linux versions
This was why these users were even able to consider a transition to Linux. They could replace their current systems, with additional value (or at much reduced cost). Virtually everything they used was free.
Similarly on AIX and IRIX the fact that there weren't that many OS specific features that were vital was the reason that IBM and SGI jumped on the LInux bandwagon to offset OS costs while still making hardware sales. If AIX or SGI were still way ahead of Linux by the late 90's they never would have done it.
On the Windows platform we haven't come close to this. Windows users use: a Microsoft shell (explorer), a Microsoft office suite, other productivity apps written for Windows only, corporate in house software written in VB or
Apache/Firefox over IIS/Explorer is one of our first major victories in replacing part of the Windows lock-in. KDE offers a wealth of applications which might be able to attack Microsoft/Windows specific apps in hundreds of places at once that will probably result in dozens of victories.
We don't need a killer app yet. What we need is to make the transition even thinkable. People on
1) Don't tend to be experts in specific productivity apps
2) Don't have a great deal of investment in application specific data
Average users however do fulfill these two criteria. Lets win the app war, the middle ware war, the OS extensions war and then worry about the kernel.
Re:How opensource took over Unix (Score:1)
This is how my wife transitioned to Linux. Firefox, OO.o, Evolution, etc. was introduced to her one at a time until one day she realized my Linux desktop didn't look so different from her Win
Re:How opensource took over Unix (Score:2)
Ah, you inspire me my friend. I have that goal, and she has realized how interested I am in Linux, and the potential to get away from the buying/registering annoyance of Windows. About a year ago, I was trying to start learning Linux on a 300MHz K6-2 with less than supported hardware(ISA 16-bit soundcard-
Re:How opensource took over Unix (Score:1)
You think it's hard today? I was trying to install a no-name ISA soundcard with Redhat 4.0 back in the day (1996). That was my first linux box, a P-100 16 megs of RAM. Man that was a sweet system! It took me a year to learn enough to get it working right. Part of the problem was an ISA video capture/TV-tuner card that was keeping the mouse from working properly. When I finally took that card out after 6 months of tinkering and the mouse magically worked I was simultaneousl
Re:How opensource took over Unix (Score:1)
Re:How opensource took over Unix (Score:2)
Tch, kids these days think they have it rough. I ad to get an ISA *modem* working back with a 2.2 kernel (this is when isapnptools was not in the kernel, mind you) and I had no manuals and no money for manuals or books. Just a Red Hat CD and a lot of determination. If it weren't for my dial-up connection on a nearby win98 to look up docs for me I'd never have succeeded.
This was where I fell i
Good, I suppose. (Score:2)
Besides, I don't think people run Win for itself. So the less apps are linked to it, the easier it will be to switch (look OO.o, if you are accustomed to it, no pb to switch OS - except the 699$ of course)
TT is releasing a QTWin w/gpl license (Score:2)
Trolltech to Extend Dual Licensing to Qt for Windows.
Re:TT is releasing a QTWin w/gpl license (Score:2)
my big beef is... (Score:1)
The way I see it as from a purely business point of view though. On the off chance we can convinc
Re:my big beef is... (Score:1)
Multiple screens? (Score:1)
Limited to one screen? How primitive!
Re:Public service announcement: DO NOT CODE FOR QT (Score:3, Interesting)
Re:Public service announcement: DO NOT CODE FOR QT (Score:2)