IBM Picks Qtopia Over PalmOS And PocketPC 285
Bill Kendrick writes "ZDNet,
Geek.com and others are reporting IBM's decision to choose Trolltech's Qtopia (the embedded version of their Qt library, used by the Sharp Zaurus PDA) in their forthcoming devices.
See the announcement at Trolltech's website, and an
earlier press release at IBM.com." Here's an earlier post about the new IBM reference platform.
Quite a shift (Score:5, Insightful)
Re:Quite a shift (Score:2)
quite a shift since its inception. Moving from massive, room-filling mainframes to miniature gigabyte pocket drives and Qt-toting PDAs.
Yes and no.
I would venture to guess that today's PDA's are almost comparable in performance with the mainframes from 3 decades ago.
Not to understate the magnitude of their business refocus - the range of uses changes just as rapidly as the price, weight, power consumption change, even if there is little performance difference between a 360 and a PDA.
Re:Quite a shift (Score:2)
I/O is the relevant performance metric for old IBM mainframes.
Re:Quite a shift (Score:3, Interesting)
Well that's assuming you don't count their long lived involvment in semiconductor development. You could say that they've been at both ends of the size spectrum for quite a while now. Notice that it is their semiconductor involvement that is pushing this decision (pushing their PPC405LP). They've also been making drives for a great long while now as well, the pocket drive is a natural evolution. So in many ways, things haven't changed at all
Re:Quite a shift (Score:3, Informative)
IBM is a lot older than you think. The company was started sometime in the late 1800s, and they built things like punch cards and typewriters. (Good typewriters too, as my finger recall, but appearently difficult to repair)
Re:Quite a shift (Score:5, Interesting)
It was Microsoft who wrestled the computer world from the headlock IBM had it in.
This is almost certainly a troll, but for those who might share the same misapprehension, it's worth pointing out that the above statement is completely false.
If there is a single cause of IBM's loss of control (and, actually, the company still is a monopoly in some spaces, though a relatively well-behaved one), it's the US Department of Justice. The consent decree IBM signed forced the company to stop bundling, which pretty much gutted the company's market strategy. If you want to add a second reason, it's the emergence of the personal computer, but the fact that IBM didn't retain control of that market is also largely attributable to the consent decree. At the time the IBM PC came out, IBM was deeply mired in red ink and floundering badly, which was a lot of the reason why IBM never put any real focus on the PC market and ended up giving it to Microsoft instead.
The reason that the DOJ hasn't had a similar effect on Microsoft's anti-competitive behavior, of course, is that Microsoft chose to ignore its consent decree and force the DOJ to make it stick in court, which has been so difficult, expensive and time-consuming that the US government has pretty much lost the will to press the charges home.
Re:Quite a shift (Score:3)
Re:Quite a shift (Score:3, Interesting)
Maybe I'm wrong, but I seem to recall IBM deliberately crippling the PC platform at the beginning in order to prevent it from eating at their mainframe sales.
I've never heard of anything like this, and I can't think what in the PC might have qualified as "crippled". I certainly don't believe that many in IBM were concerned with PCs (which were considered little better than toys) eating into their mainframe sales.
Wouldn't it really be the clonemakers who opened the 8088 architecture with cloned BIOSes and IBM-compatible hardware?
They're the ones who ate IBM's lunch in the PC hardware market, sure, but I have to think that if IBM had really been at the top of their game they'd have recognized the opportunity for software sales. Or not. My point was that they couldn't be bothered because the company was in serious trouble and had bigger fish to fry.
I was only a kid at the time, but I distinctly remember there being two factions in the PC world at the beginning. The evil IBM empire with sidekick Compaq, who were selling their machines at extremely high prices, and the rest of the clone world.
Well, I was more or less a kid at the time as well, but I'm pretty sure at least one part of this is wrong -- Compaq wasn't IBM's "sidekick". Compaq was the company that reverse-engineered IBM's machines, which couldn't have made IBM very happy.
IBM did try to regain control of the architecture with the PS/2, but the higher price of the hardware for the platform (general rule, add $100 for any PS/2 component as compared to an ISA or EISA version of the time) killed the interest.
Yep, but I'd say this is just another facet of the fact that IBM really couldn't be bothered. Sure, the people in the PC division tried to do what they could but they weren't given the money or the tools they needed to really find a winning strategy (which clearly wasn't in selling the hardware; IBM always has been a company that focuses on high-margin business).
Re:Not to mention... (Score:4, Informative)
Not to mention a change of administration in the executive branch leading to a kinder, gentler, nation for our formerly oppressed corporate underclass.
Go back and reread your the history of the case; the soft-pedaling started during the Clinton administration. This isn't a Clinton/Bush or Dem/Rep issue, more a failure of the system as a whole. I'd have to go back and look again myself, but ISTR that the DOJ was toughest near the beginning, which was during the Bush Sr. administration.
And for those who are convinced that only the Reps favor corporate America, keep in mind that the Dems are heavily behind the push to maintain Big Media's stranglehold.
You're factually correct (Score:3, Informative)
Without a doubt, once Bush took office and Ashcroft took the DOJ we had a new policy of dropping the case at all costs. The DOJ settled with defendant that had previously convicted. When have you ever seen that by a prosecutor? Extremely strange, and obviously political. This is not a Democrat vs. Republican thing, it's a Bush II policy issue, the effects of which are in the public record.
Cheers,
--Maynard
Go Trolltech! (Score:4, Insightful)
Re:Go Trolltech! (Score:3, Insightful)
Re:Go Trolltech! (Score:4, Insightful)
Don't forget the huge publicity boost KDE has given Qt. How many people here on Slashdot would have heard of Qt if it weren't for KDE? It works both ways.
Re:Go Trolltech! (Score:2, Funny)
This can hardly be a surprise (Score:3, Insightful)
Re:This can hardly be a surprise (Score:5, Funny)
Yep,
Just like OS/2....
Trolls? (Score:4, Funny)
Trolls! They invade everything nowadays
linux just won (Score:2, Interesting)
And we know what happened that last time ibm released a pc reference platform.
I would say that linux just won the future.
and the future is wareable -peace yall.
- the final invention says that
" we'll make great pets."
Re:linux just won (Score:2)
Do you mean PREP/CHRP. Oh, or were you referring to PS/2
Syncs with all OSes, opensource OS (Score:3, Interesting)
Also, Qtopia is open source... I think I want a Qtopia device now
Re:Syncs with all OSes, opensource OS (Score:4, Informative)
Go out and buy a Sharp Zaurus. It has a 206Mhz StrongArm, keyboard, SD slot, and a CF slot that accepts memory, cameras, ethernet, WiFi, and Bluetooth cards. What does the NX70 have over that, other than a built-in camera?
The Zaurus SL-5500 [sharp-usa.com] is a good PDA and an even better "handheld computer." The SL-5600M [sharp-usa.com] will be even more capable when it is released.
Broadening the user base (Score:5, Informative)
It says so..... (Score:3, Funny)
In the post: "the embedded version of their Qt library, used by the Sharp Zaurus PDA"
Huge! (Score:4, Interesting)
They deserve this success too. They have given us QT, which IMO is THE BEST Application Framework for C++ ever developed.
However I'm wondering if there isn't another faction inside IBM that we haven't heard about... waiting to kill off anything that isn't Windows based (sort of like what happened with the IBM PC Co and OS/2).
pretty good: linux on embedded devices (Score:3, Insightful)
It also goes a step further than motorola's annoucement earlier this week as here we have an opensource product in the middleware as well as the OS--and the middleware/interface makes a real difference in this type of device. Note that they will use a Montavista kernel, just as motorola: I guess the palm market is becoming so saturated that differentiation from competitors is also crucial at this stage--this will allow them to offer different apps etc than palm/pocket PC.
Goodie goodie, IBM is back on the handheld market with some fun stuff--we as consumers might see some great new apps.
X-less QT (Score:2, Insightful)
X windows reminds me of the space shuttle. It's big and old and we know it won't last forever, but we hide our heads in the sand and we don't want to hear about it. Well, that's a really stupid attitude, especially since there is such an inviting alternative.
Re:X-less QT (Score:5, Insightful)
But go on, just show us what you're up to and code something better. It will be adopted and enhanced if it's really good, the free software community is very good at joining well-thought projects.
GGI was never an X replacement (Score:5, Informative)
You might be thinking of the Berlin Project, which I see has moved over to something called Fresco. Haven't followed up on that in some time so I can't speak to its current development activity.
Cheers,
--Maynard
Re:X-less QT (Score:2)
Re:X-less QT (Score:5, Insightful)
Yes, let's all move over to a windowing system with serious licensing issues that's designed from the ground up to be run on embedded devices. That sounds perfect.
And what is this "plan" to start phasing out X windows? Was there a meeting I missed? Last I checked X was still being heavily developed.
"I'm not saying we take drastic steps now, but we'd be stupid to take no steps to transition the desktop to QT all the way down."
This is ridiculous. We'd be stupid TO take steps to transition "the desktop" to Qt all the way down. You're the only one who wants this. Not everyone loves KDE, and even less people love Qt. The seperation of the windowing system and the actual desktop is what gives *nix users the configurability to give their desktops personality. If you want a one-size-fits-all desktop, get windows.
As for you're space shuttle comparison, X windows is not inherently big (at least is doesn't have to be). It's not old. As I said, it is still under development, and there have been recent releases. Having history doesn't make software old.
As far as I can see, you're the only one with your head in the sand. It sounds like you're regurgitating all the inaccurate FUD-based trolling that goes on any time an article related to X is posted.
Qt is in no way a replacement for X, and it never will be, in it's current form.
Re:X-less QT (Score:3, Insightful)
Re:X-less QT (Score:2)
Re:X-less QT (Score:2)
Re:X-less QT (Score:2)
Actually, that method of cut-and-paste is a "bonus" on top of the clipboard functionality provided by the applications (GTK and Qt use essentially the same methods, which I believe is based on the XDND protocol). You should really only use the middle mouse button for simple text and for swapping text between terminals and such. For anything more complex (such as graphics, spreadsheet cells, etc) use CTRL-X/C/V or the edit menus.
As a power user, I love the convenience of the middle-button clipboard, and I get frustrated at apps that don't honor it (kdevelop, for one).
It also needs a way to change res on the fly but I hear thats going to be in 4.3.
Honestly, I haven't missed this feature, but early on I set up a user called "gamer" running a small window manager at 800x600 and I log into that user when I want to play games. I don't know why else I'd want to change the res on-the-fly, but as you said, they're working on it so I'll take it.
kde adds much of these things but they only work within kde not to mention kde is too much of a mem hog on slow systems
You may not realize that you can run all the KDE apps you want from any window manager. I run kdevelop, kmail, and konqueror all the time, but I don't run the KDE desktop (too slow for me). I use WindowMaker. I also use Gnome apps alongside the KDE apps... these desktop systems are not mutually exclusive! You may realize this, but a lot of new users coming from Windows don't realize that you can run Gnome apps within KDE and vice-versa because the "desktop environments" are pretty much veneers over the standard X protocol and are not incompatible.
Re:X-less QT (Score:2)
I do think we need some kind of propertie page type of thing like Windows, Mac, etc have that can control resolutions with a GUI. (There may already be one, but I just don't know about it...)
Re:X-less QT (Score:2)
Take a look at this page for more info:
http://www.xfree86.org/~keithp/talks/randr/rand
Re:X-less QT (Score:2)
You're ignoring the fact that Qt is only GPLd when using X11. You're ignoring a lot of facts actually.
X windows reminds me of the space shuttle. It's big and old and we know it won't last forever, but we hide our heads in the sand and we don't want to hear about it. Well, that's a really stupid attitude, especially since there is such an inviting alternative.
If you're going to compare X to the space shuttle. then the Linux framebuffer would be a light Cessna aircraft. X has features, it has hardware support, it has apps. DirectFB (presumably what you are talking about) does not.
Finally, remember that it's actually GTK that works on the Linux framebuffer - not Qt. See for yourself [directfb.org]. Qt is only GPLd when running on X, the code to make it work on the framebuffer isn't under the GPL afaik.
Re:X-less QT (Score:2)
Just to correct you, Qt/Embedded is available as GPL. Not that this helps the parent poster at all, though. If I wanted to use Qt in an X replacement, I would probably port from Qt/X11, since it is closer to home.
Re:X-less QT (Score:5, Insightful)
X windows reminds me of the space shuttle. It's big and old and we know it won't last forever
One thing I consistently don't see in posts critical of X is an explanation of *why* it won't last forever. Seriously, what's wrong with it? The only specific points I hear are not only vague, but wrong. Just to get the crap arguments out of the way, I'll list the most obvious ones and then maybe someone can give me some *real* reasons.
That's a good sample. What I'd like to see is some really good, technical arguments that point out significant deficiencies in X that cannot be addressed without a clean start. I won't even demand that the deficiencies be good enough to justify all of the effort that will be required to reimplement everything for the replacement, although a *really* good answer would cover that as well.
Any takers?
Re:X-less QT (Score:2, Interesting)
I'm not qualified to hold forth on the pros and cons of X but will point out this: when using MacOS X, it is such a relief to have a display system that just works. Want antialiasing? Just turn it on! Most users wouldn't even know it's something to which thought might be given, as opposed to desktop Linux use, where fighting XFree becomes an activity in its own right.
(And I still have XFree available on OS X for GIMP and remote Matlab sessions...)
Re:X-less QT (Score:2)
Well, most of the "X sucks" people really mean that XFree sucks, and have never used a commercial X server.
Good point.
Most users wouldn't even know it's something to which thought might be given, as opposed to desktop Linux use, where fighting XFree becomes an activity in its own right.
This is true but really just indicates that the configuration and management of XFree86 needs to be improved and, in fact, that is happening. For example, I'm typing this on a Linux box using anti-aliased fonts and I did *nothing* to enable them. XFree86 4.2 and KDE quietly conspired to turn anti-aliasing on by default and it just works. I know where I could go into the control panel to turn them off, or to tweak the settings, but the defaults are great by me.
I'll certainly admit that OSX is looking pretty tempting, though...
Re:X-less QT (Score:2)
Do a simple bitblit benchmark. The GDI doesn't perform anywhere near as well as X (4.1, in my tests). It isn't until you start writing DirectX code that you can get blit performance as good as X. Then, you've got 3D. 3D in Linux (through GLX) is just as fast as 3D in Windows (assuming a good driver like NVIDIA's).
On the client server bit -- Windows is more client-server than X! For example, when you create a process in windows, Win32 calls a thread-create function in the NT kernel, then sends a message to the Win32 server to set things up. The server runs in kernel space, but it still communicates via IPC mechanisms.
Re:X-less QT (Score:2)
I'll throw my $0.02 in with your rant, as well. People who claim that Windows apps all use the same widgets have obviously not used many Windows apps... many of them use their own custom widget sets as well.
Here's a test... load Office XP [shudder]. Note that regardless of the Windows settings, Office uses its own XP-style menus. How could this be if it wasn't implementing its own menus? Next, load Windows XP [double shudder]. Note that the drag behaviour of the standard combo box has changed... you can't click, hold, drag, and release. You must click, release, then click to select an item using the standard combo box (in say, a control panel app). Now, go to Office XP and open an Office dialog box (Tools | Options). The combo box works in the old way -- you can click-drag-release. It's implementing its own controls, or altering the standard ones.
Standard toolkits.... pfft.
X-less QT is a bad idea (Score:2)
In what regard is running Qt without X windows a "better desktop GUI"? Qt/Embedded doesn't run 99% of the UNIX GUI applications, it can't be used for remote access to compute servers, there is only a single implementation of it (from Troll Tech), it requires more memory and CPU, it only gives me a single toolkit, and every commercial software vendor has to spend $2000+ per developer.
I mean, a lot of effort has gone into a super-efficient X-less QT that requires minimal hardware to run well.
Qt/Embedded on the Zaurus uses a 200MHz ARM with 64Mbytes of RAM; that is not "minimal". If you look at its memory usage, it's upwards of a dozen megabytes. X11 clients run on 8bit microprocessors with 64kbytes of RAM, and X11 servers run on machines with less than 1Mbyte of RAM. The notion that Qt/Embedded is "super efficient" is some marketing fiction not grounded in reality.
Let me put it this way: if Qt/Embedded is so "super efficient", where are those savings supposed to come from concretely and specifically?
X windows reminds me of the space shuttle. It's big and old and we know it won't last forever, but we hide our heads in the sand and we don't want to hear about it. Well, that's a really stupid attitude, especially since there is such an inviting alternative.
You are confusing XFree86 and the X11 protocol. At some point, we should probably throw out XFree86, which has become a pretty messy and big codebase (even though you can compile it into very compact and efficient servers), but there is no reason to get rid of the X11 protocol--nobody has yet come up with anything better.
Re:X-less QT is a bad idea (Score:2)
Re:X-less QT is a bad idea (Score:2)
Re:X-less QT (Score:2)
I can't quite figure out what the problem is. People harp on X all of the time because they are too stupid to stop running Enlightenment in framebuffer mode. It's not X!
Why don't you anit-X trolls start posting some legitimate remarks about X problems. We'll be waiting.
Re: X-less QT (Score:5, Insightful)
The problem is not X, but rather XFree86. XF86 is monolithic, and contains its own drivers. I realize this is mainly because *nixes don't have their own video, but Linux does. For years I've had problems with mixing Framebuffer Consoles and X, simply because they both fight over the same video. In a better designed system, Linux would provide the video and X would ride on top of it.
There is nothing wrong with the Linux Framebuffer except for lack of decent drivers. The DirectFB intends to solve this, but at this point XFree86 totally beats out DirectFB in driver support. Why does Unreal Tournament 2003 require XFree86? Because it needs OpenGL. Why the hell does OpenGL, something you're never going to use remotely, require XFree86? Because everyone uses X!
And that's where things have gone stupid. NVidia's drivers are for XFree86. Other closed-source vendor video drivers are for XFree86. This is a problem guys. What if we want to use the video drivers for something other than XFree86? Oops, you can't. We need to separate the hardware and X protocol layers from XFree86. This would lead to better compatibility and stability, and give ease to future expansion. At least on Linux systems, XFree86 should not be trying to roll its own drivers.
If you don't think we need to clean this up, consider that nearly every Linux crash is always due to XFree86. And please, don't tell me how you shelled in from your other box to kill XFree86, you may as well reboot if it comes to that.
So you are right, people wrongfully blame X when they should really be blaming XFree86. Before flaming me, please note that I am not against the X protocol, but the idea of an X server having its own drivers. Even so, I think using X for local applications is a bit redundant.
Which brings me to my next argument, which is about replacing X as a fundamental application layer. IMO, it should be possible to have locally running apps that access the video directly without having to go through some weird pile of extensions. 99.99% of the time, I am running apps locally. For me, and nearly all Linux users out there, "remote" should be the exception, not the rule.
The trouble, of course, is that there is a lot more to X than just a framebuffer. Try DirectFB sometime and you will realize this quickly. X has some very important things, like Window Managers, Input methods, hinting (for things like docklets), keyboard/mouse grabbing, etc. We'd need good replacements for all of these, along with X compatibility for it all. This is not trivial.
Qtopia (nor Qt/Embedded) is not the answer to the desktop. It is a really cool system, but is pretty much limited to the scope of PDAs. What we really need is a Qt/DirectFB (there is already such a port of gtk). This is just one step of many, though.
Re: X-less QT (Score:2)
Re: X-less QT (Score:2)
I don't blame the authors of existing drivers for choosing XFree86, as there is no real alternative at the moment. Even though DirectFB is near-complete, it just isn't popular enough and does not integrate well with X enough for people to bother.
Re: X-less QT (Score:2)
Because OpenGL is meant for more than games. What if you need to render and manipulate a large quantity (huge...gigs of data) of remote sensing data in a 3d environment in realtime? In other words, you need a big honking machine that you can't get at BestBuy and put on your desk. You need a large cluster or SGI Reality machine that's being cared for in its own climate-controlled pen... it handles the massive data crunching while you use your NVidia (or other) desktop to remotely render the OpenGL commands it sends over the network.
It's really amazing how efficient this works... you should try it. I've used it in the instance described above (except the X-term was an SGI box), and I've also used it to get super-smooth framerates on the gl screensavers running on a PII-266 but displayed remotely on an Athlon/GeForce box over a 100mbit network. Things like glearth will run at 60+fps and only use about 60KB/sec of network bandwidth.
The important thing is that X is built for the long haul, and so it must include remote operation... the desktop configuration may not be the ideal solution in the future, and you don't want to limit yourself to the "one user, sitting next to the box" configuration over the decades (just ask Microsoft, who is trying desperately to turn single-user Windows into multi-user Unix).
Re:X-less QT: Build it yourself (Score:2)
On the other hand 486s also make good X terminals :).
Comment removed (Score:3, Insightful)
Still no sync for Mac (Score:2, Informative)
Re:Still no sync for Mac (Score:5, Insightful)
Re:Still no sync for Mac (Score:2)
Re:Still no sync for Mac (Score:2)
QuickTime...How does it work? (Score:3, Funny)
Boss Hog: We need to go back and dump sugar in them Duke Brothers' gas tank. Get onto it, Rosco!
IBM HINT: There is no QuickTime...
This is probably not needed, (Score:4, Informative)
Qt is a multiplatform, C++ application development framework. One source runs natively on Windows, Unix/Linux, Mac 0S X, and embedded systems.
Go here [trolltech.com] for a brief overview from Trolltech.
Pretty cool with the customization aspect.. Is there any programmers out there who have some real experience? This is pretty interesting to me, and I wouldn't mind hearing some feedback and maybe links or something. =)
Re:This is probably not needed, (Score:5, Informative)
I have no experience of the embedded version of Qt, so keep in mind I'm talking about the X11/Windows library here.
In three words: it fucking rocks.
Qt is simply the single best designed piece of software I have -ever- seen. While it sets out for a huge task, being a completely self-sufficient C++ framework, a multiplatform one at that (and it can indeed easily replace the entire MFC), the class hierarchy [trolltech.com] is extremely clean, and it's very easy to get the hang of it. Actually, the entire documentation [trolltech.com] is absolutely excellent, clear and very well cross-referenced. I've never stayed stuck while looking for some info in there (quite unlike the MSDN documentation!). Go take a peek, someday.
One of the nice things with Qt is, if you need to do some basic task, Qt makes it trivial. Reading a file line by line is an example I was confronted to just today: using the MFC's idea of files, it's tedious at best -- gotta do the nitty gritty job manually. Wasted time. Using Qt, it's, well, trivial [trolltech.com].
The other thing about Qt is, if you need to do something complex, Qt makes it very straightforward. For instance, yesterday, our VB programmer was trying to make a custom widget that lets you stack frames vertically, each under its own tab, and showing only one at a time. After hours of work, he got to work a simple version of it that couldn't resize, among other shortcomings. Well, it took me much less time to rapidly put together the same thing in Qt, only it worked right away without those shortcomings, could accept any kind of subwidget, and, oh, of course, could resize at will and would work right away on any platform. Keep in mind that this guy is very experienced with his tools, while I'm a relative beginner with Qt.
There are countless useful features in Qt. For instance, it doesn't duplicate data when duplication is not either required or specifically requested by the programmer. Copy a QString or a QPixmap ten times, and Qt will keep only one copy of the data in memory for all the instances. Modify one of the ten instances, and Qt will then replicate its data to modify it without touching the nine other instances.
And those guys actually license their boon of a tool under the GPL. That's almost too good to be true.
Anyway, enough rambling. If you're a programmer, do yourself a favor, and check out Qt. Even if you don't end up using it, you will likely learn quite a lot about how powerful object orientation can be when used by people who know what they are doing.
Re:This is probably not needed, (Score:4, Informative)
Qt is simply the single best designed piece of software I have -ever- seen. While it sets out for a huge task, being a completely self-sufficient C++ framework, a multiplatform one at that (and it can indeed easily replace the entire MFC), the class hierarchy [trolltech.com] is extremely clean, and it's very easy to get the hang of it. Actually, the entire documentation [trolltech.com] is absolutely excellent, clear and very well cross-referenced. I've never stayed stuck while looking for some info in there (quite unlike the MSDN documentation!). Go take a peek, someday.
The wxWindows documentation is online here [jussieu.fr]. Go take a peek - it's remarkably complete and detailed.
One of the nice things with Qt is, if you need to do some basic task, Qt makes it trivial. Reading a file line by line is an example I was confronted to just today: using the MFC's idea of files, it's tedious at best -- gotta do the nitty gritty job manually. Wasted time. Using Qt, it's, well, trivial [trolltech.com].
wxWindows provides a few ways of doing this:
you can either use a wxTextFile [jussieu.fr] or a wxTextInputStream [jussieu.fr].
Both give you a ReadLine method or equivalent.
The other thing about Qt is, if you need to do something complex, Qt makes it very straightforward. For instance, yesterday, our VB programmer was trying to make a custom widget that lets you stack frames vertically, each under its own tab, and showing only one at a time. After hours of work, he got to work a simple version of it that couldn't resize, among other shortcomings. Well, it took me much less time to rapidly put together the same thing in Qt, only it worked right away without those shortcomings, could accept any kind of subwidget, and, oh, of course, could resize at will and would work right away on any platform. Keep in mind that this guy is very experienced with his tools, while I'm a relative beginner with Qt.
Also easy with wxWindows. Their Sizer classes are by far the best method I've ever seen for laying out automatically resizable dialogs.
There are countless useful features in Qt. For instance, it doesn't duplicate data when duplication is not either required or specifically requested by the programmer. Copy a QString or a QPixmap ten times, and Qt will keep only one copy of the data in memory for all the instances. Modify one of the ten instances, and Qt will then replicate its data to modify it without touching the nine other instances.
wxWindows also reference-counts strings, bitmaps, and many other common data types.
And those guys actually license their boon of a tool under the GPL. That's almost too good to be true.
Unless you want the Windows version - that costs an arm and a leg. wxWindows is GPL for all platforms (and it currently supports more platforms than Qt).
Anyway, enough rambling. If you're a programmer, do yourself a favor, and check out Qt. Even if you don't end up using it, you will likely learn quite a lot about how powerful object orientation can be when used by people who know what they are doing.
Agreed. Check out both, though. Honestly, if I had a large budget to create a commercial cross-platform application, there's a good chance I'd choose Qt. But wxWindows has its advantages. For a free cross-platform software project, there's no contest: wxWindows is free on all platforms, with a very comparable feature set.
Re:This is probably not needed, (Score:2)
correction (Score:3, Informative)
After Sharp decided to use Qtopia on the Zarus, TrollTech seemed to lose interest in the Qtopia version for Familiar on the iPaq, so an open source fork was started called Opie http://opie.handhelds.org/
One of their goals is binary compatabilty with Qtopia though.
Seems like a no brainer. (Score:2, Interesting)
Lets ignore all the security issues for a moment. Let's just imagine that MS finally makes something truly secure, and no one is going to be hacking your phone or PDA.
The primary issues then become functionality and memory footprint. In terms of low cost buying power, you can't beat linux. In terms of memory scalability, you can't beat linux.
Add in stability, and the reality of security, and it seems wierd that anyone would go another direction.
Re:Seems like a no brainer. (Score:2)
I'm not saying that these IBM/QTopia devices won't be able to do all of the above, but I'm pretty sure that the Pocket PC devices will make it a lot easier.
But will IBM actually make PDAs? (Score:2)
IBM may have what it takes... (Score:2)
Wireless devices like this I would think would be right up IBM's alley, it's the next logical step.
-Pete
Re:IBM may have what it takes... (Score:2)
It won't be blazingly fast but could be good enough while Intel fixes it's XScale problems.
try:
http://www.zaurus.com
http://www.pellico
LoB
Is IBM serious about the PDA market? (Score:4, Interesting)
Nope, this looks like IBM pushing their PPC405 into the embedded market, any resemblence to a pda is purely incidental.
You do not understand the PDA market (Score:3, Insightful)
PDA's do not synch to each other. Period. I know that IR port on your Palm is ever so useful, neh? What does PDA OS compatibility mean? To the PDA user, not much. As long as the requisite apps exist, and the price is right, and the PDA can synch to the REAL computer (ie, desktop/laptop running Win/MacOS/Linux), in many people's eyes it is a serious PDA. Add in a standard memory card (Flash/Smart/SD), and ability to export/save as some standard file format, and you have a PDA that's as good as any PocketPC/Palm out there.
Good for Zaurus? (Score:2, Insightful)
This is the new battlefield (Score:3, Informative)
What's up with that ad for MS Visual Studio .Nyet (Score:2)
So does this mean.... (Score:2)
or are they just going to put the Qtopia on the palm pilot?
Over PalmOS and PocketPC? (Score:5, Insightful)
at Linuxworld... (Score:2)
On an unrelated(ish) note - they had the Japanese Zaurus there, and i got a chance to play with it a bit. I was about to trade in my iPaq right then and there. Really neat piece of tech.
PDA or Other? (Score:2, Interesting)
Re:PDA or Other? (Score:2)
Nobody has come up with a sales pitch for a connected phone/pda. The web is too 'fat', you need fairly recent computer to be able to enjoy it with all the flashy graphics and stupid <table> and 1px gif based layouts. Perhaps XHTML/XML will be the next step? (Get a clue, web "designers")
J.
Will this (Score:3, Funny)
Qtopia/Zaurus (Score:2, Interesting)
Just my 2 units of currency..
IBM track record is abysmal (Score:3, Funny)
If anything this is a test bed for some kind of embedded technology subproject.
Their heart isn't in it. This is a throwaway project - some bright execuweenie in training has been given a bag of burnable cash to show what he can do for the benefit of Sam Palmisano and Co.
Re:Why not Linux? (Score:5, Informative)
Re:Why not Linux? (Score:2, Informative)
"Why not?"
"It might make you look dumb."
"It's OK. This one just needs a little clarity".
QTopia is a development environment for portable and embeded devices. It runs on embeded versions of Linux.
Re:Linux footprint too general-purpose. (Score:5, Informative)
Re:Linux footprint too general-purpose. (Score:4, Funny)
Think of all the drivers people are downloading and will never use.
So don't build the parts you don't need. This is one of the huge advantages of having the source code.
Last time I checked, Linux may not be desirable in handhelds because the kernel is growing, growing, growing
Dang. I guess I need to find something else to run this handheld on. I mean, since the 2.4.18 kernel that it's currently running can't fit. And I thought I still had half of my 32MB free, even with Linux, busybox, Qt, and a couple dozen apps, but I guess "cat /proc/meminfo" is lying to me...
and the new features don't realy put a dent in the desire for such computing that needs to be small and quick on the sleep and resume modes.
You mean my PDA *doesn't* really suspend and resume in less than a second? Man, do me a favor and go tell kids that Santa Claus doesn't exist or something, because you're really getting me down.
Yes and No (Score:5, Informative)
Informative? WRONG information! (Score:2)
Yes, you can. You only have to distribute your product under the GPL licence. Red Hat does it. Suse does it. Caldera does it.
Re:Then that's not GPL... (Score:2)
If you want your app to be closed-source, you have to use the non-GPL'ed version of Qt, which will cost you.
I think it's a great situation, myself. Trolltech gets money, while providing an incentive to create GPL'ed apps.
That's not what it says... (Score:2)
Re:Then that's not GPL... (Score:3, Informative)
So... (Score:2)
Accidental confusion? (Score:3, Insightful)
Re:Then that's not GPL... (Score:3, Interesting)
Of course, it is encouraged that you support Trolltech if you are benefitting from their library. It's not every day that a company gives you their entire flagship product as open source. Plus their support is usually pretty good
Re:Then that's not GPL... (Score:3, Informative)
So you could use Qt GPL version and make an app and sell it, but you'd also have to release the source code with it under the GPL license.
Re:Sorry for this Redundant post (Score:2)
Seems like a good mix to me. Heck, the Qtopia SDK is what, US$100. Big woop. IMHO.
LoB
Feudalism? (Score:2, Funny)
Re:crazy (Score:2, Interesting)
Ah, not quite! Just as the presence of Athlons does not mean there are no embedded x86 Elans, the presence of the G4 doesn't mean there are no embedded PowerPCs! Don't confuse the architecture (PowerPC) with the implementation (G4).
The PowerPC has long been a staple of the embedded commuity (by 'long' here I mean 'half a decade or so'
The PowerPC's proven itself to be an astoundingly flexible architecture, and if IBM says they've got a low-power-consumption chip, I'd believe it, even if they posted good performance figures. As with the ARM, which was also not originally an embedded chip, performance and power consumption are not -always- mutually exclusive.
Also, as far as Linux on the PDA is concerned...I run Linux on my iPaq (and use it as a PDA) and have found it to be smaller and more stable than WinCE, and more stable (though larger) than PalmOS. My distribution of Linux fits handily into 16M of flash, and that includes Qtopia, all my PIM apps, Konqueror, Kinkatta (an AIM client), and various wlan mapping tools. Even my non-Linux friends prefer my 'feudal' Linux PDA -- and this was put together by a bunch of volunteers. I'm really looking forward to see what IBM's got.
Nuggets of truths--Linux PDA's do suck. (Score:2)
Too often, linux developers who have little or no knowledge of interface design say "Ah-ha! Because of linux's spectacular portability, I can port this application that runs on my pentium 4 machines with a 21" monitor to my StrongArm PDA with a 240 x 320 pixel screen." Unfortunately, they really don't take into account the difference in usage between a desktop machine that sits on your desk and something that's so small it fits into your pocket. You tend to see this screwed up way of thinking in PDA's like the Agenda and Zaurus. To be fair, you also tend to see it in messed up designs like WinCE. IBM really should have gone with PalmOS.
Qtopia is a prime example of a desktop UI that was shrunk 20 times to be put into a PDA without any real forthought. Maybe it'll be okay for something like set-top boxes or answering machines, but I would be very disappointed in IBM's human factors department if they actually approved using Qtopia with PDA's.
Re:From the same guys who brought us OS/2... (Score:2)
Regarding the PalmOS, well, it's not full featured enough and Linux already is.
That's my "take" on why IBM didn't go with WinCE or PalmOS.
LoB
Re:From the same guys who brought us OS/2... (Score:2)
For the same reason Henry Ford didn't use the proven, well-supported technology, based on the leading cart-puller of his time, i.e. the horse.