Ubuntu Mobile Looks At Qt As GNOME Alternative 262
Derwent sends along a Computerworld piece which begins: "The Ubuntu Mobile operating system is undergoing its most radical change with a port to the ARM processor for Internet devices and netbooks, and may use Nokia's LGPL Qt development environment as an alternative to GNOME. During a presentation at this year's linux.conf.au conference, Canonical's David Mandala said Ubuntu Mobile has changed a lot over the past year... 'I worked on ARM devices for many years so a full Linux distribution on ARM is exciting,' Mandala said, adding one of the biggest challenges is reminding developers to write applications for 800 by 600 screen resolutions found in smaller devices. 'The standard [resolution] for GNOME [apps] is 800 by 600, but not all apps are. For this reason Ubuntu Mobile uses the GNOME Mobile (Hildon framework) instead of a full GNOME desktop, but since Nokia open sourced Qt under the LGPL it may consider this as an alternative.'"
Full 'nix for arm? (Score:5, Insightful)
There's already a full 'nix for ARM complete with working packaging and so on, in the form of OpenBSD, just in case anyone has forgotten it. Also, the developers need to be reminded that screens are 640x480 on small devices, not 800x600. It would start if they got out of the habit of using excessively lavish button bars with enourmous, heavily padded buttons.
Anyway, it would be nice to see a proper "full" linux distribution. I'm not much of a fan of the special PDA ones since they're cut down. Then again, I'm not much of a fan of ubuntu either, but I appreciate that (say) Arch isn't to everyone's taste.
Re: (Score:2)
"It would start if they got out of the habit of using excessively lavish button bars with enourmous, heavily padded buttons."
I'm glad I'm not the only one annoyed by this. The strange padding fetish that the GTK folks has results in terrible feng shui for most GNOME apps, especially Nautilus. Even tweaking the theme manually to reduce the insane amounts of padding only helps a little, and often causes subtle and not-so-subtle rendering glitches.
Re:Full 'nix for arm? (Score:5, Insightful)
Re: (Score:2, Offtopic)
I don't want to click on your stupid big buttons. If I want to do something fast, I use the keyboard. You do provide keyboard shortcuts for your buttons, right? And if you say that you really really need an 800 pixel wide dialog, I say bullshit. We got by just fine ten years ago with 640x480 screens, and before you can say "we have more features now", I'll tell you to get rid of them and fix the bugs first. Call me bitter, but after a week of trying to play Fallout 3 with the screen freezing every five minu
Re:Full 'nix for arm? (Score:5, Interesting)
http://www.asktog.com/TOI/toi06KeyboardVMouse1.html [asktog.com]
Try timing yourself on some web browsing/text editing/file managing tasks. Keyboarding may be faster occasionally, but you'll be surprised how often mousing wins.
Re:Full 'nix for arm? (Score:4, Insightful)
I use Vim all day, almost every day. Using a mouse and a word processor is very much not faster for me.
Re: (Score:3, Insightful)
I use vim exclusively, but counting out how many words I want to move, followed by typing [ESC(which is the "capslock" key)] 17w, or even just hitting "w" or "W" repeatedly while tracking with my eyes wherever the cursor has ended up /this/ time based on whatever is considered a "word boundary"...
has _ALWAYS_ been slower than moving my hand to the mouse and clicking. and USUALLY been slower than just holding down an arrow key, especially if using an editor which sanely handles the use of arrow keys to move
Re: (Score:2)
This is only true for people who havent *learned* the keyboard shortcuts, or dont even touch-type to begin with. It was a rigged test and TOG, while usually good, shouldnt stoop so low as to imply otherwise.
Give me a system with keyboard shortcuts that I know well (i.e. have in muscle memory) and I'll blow away the fastest mouser in the world. I'm not even a particularly fast typist either.
Put me on a system with unfamiliar shortcut keys however and you will get results similar to what he's describing.
Re:Full 'nix for arm? (Score:4, Insightful)
Keyboard shortcuts are not amenable to muscle memory, as the muscle movement differs depending on the previous shortcut. Returning to the home position between each keypresses allows muscle memory, but I'd be very surprised if it were enough to compensate for the movement inefficiency. Consecutive strings of keyboard shortcuts can be memorized by muscle memory (as with typing whole words), but if you use a string of shortcuts frequently enough to memorize in this way it would be better consolidated to a single shortcut.
On the other hand, mouse gestures or pie menus require the exact same movement each time, so are highly amenable to muscle memory.
Re:Full 'nix for arm? (Score:4, Insightful)
You're obviously not a touch typist. That's absurd. A practiced touch typist on a decent keyboard can select a paragraph for manipulation in about the time it takes you to get your hand from the keyboard to the mouse, let alone actually using the mouse to select the paragraph and THEN move the hand back into home position.
Re: (Score:3, Insightful)
Unfortunately for that comparison, mouse input is highly srialized while keyboarding is very parallel. I only have one arm to manipulate a mouse but 10 fingers to manipulate a keyboard.
Re:Full 'nix for arm? (Score:4, Insightful)
My reflexive control-X control-S (when I'm /not/ in Emacs) would beg to differ. It's gotten so ingrained that I'll use those shortcuts in other things as well; similarly, shift-delete will delete a whole line in my Other Editor, which annoys the heck out of me, as i'm expecting to cut what I have highlighted. ;) So, I'm pretty sure muscle memory works quite well with keystrokes ... whereas when mousing, I am always looking at where it's going. Perhaps with a tablet it'd be easier.... but even then I had trouble and needed to look.
Re: (Score:2)
If everything you do requires two hands on the keyboard hitting keys in programs you are ALWAYS familiar with you'll get what you're describing.
How many people browse the web with only a keyboard? How many people edit pictures/music/movies with only a keyboard? How many people use a dozen programs in a different day, each with different keyboard shortcuts that would need to be muscle-memoried? I think a strong case could be made that people who use one hand on the keyboard with their other on the mouse will
Re: (Score:3, Insightful)
How many people that *think* they've been educated on computer usage never learned to type to begin with? How many keyboards these days are so shoddily made they are effectively useless for those of us that do know how to use them, clearly designed for use by hunt-and-peckers only? How many computer programs just assume the current answers to those facts and dont bother to even consider exce
Re: (Score:2)
I prefer (for small things) one hand on the mouse (trackball) other on the keyboard. Otherwise I like to use both hands on the keyboard and even in a full GUI environment, it's easier to just put in the right key combination than search through menu's for it. The fact that those keys are standard across the Apple platform makes it even easier. Heck, some of my comments in XCode (which I use for PHP, Perl, C and C++ development) have been known to have (or won't compile because of) :wq at the end (my previou
Re: (Score:2)
I think, these days, from the year that Tog wrote that article, your comment needs to be qualified. What he was talking about were primitive user interface elements: bolding, opening a file, saving a file, etc. But the qualification needs to be about expressability of the input method. So, if you are repeating the same or similar tasks over and over again, yeah it would be more productive to use the mouse. But, one may argue, if one is repeating the same task over and over again, that is something that
Re: (Score:3, Insightful)
Let's see...
Open a new browser tab (winner: keybd)
Close a browser tab (winner: keybd)
Go to a history/bookmarked URL (winner: keybd)
Navigate forward/back in the history (winner: keybd)
Click a link (Tie. I generally hit / and start typing the link text, hit escape, then enter to visit the link. Sometimes moving the mouse over the link is faster.)
Run an application (winner: keybd)
Cut/copy/paste/save/print/quit/etc (winner: keybd)
Scrolling via arrow, pgup/dn, home/end vs. wheel (winner: keybd)
Switching between
Re: (Score:2)
Go to a history/bookmarked URL (winner: keybd)
The AwesomeBar makes this SOOO fucking true!
Re: (Score:3, Insightful)
Those are all arguably faster with gestures.
With most browsers, I'd say this is true. With Opera's Speed Dial, it becomes a matter of whether you've memorized the name of the site (or bookmark). Just open a new tab, and you see a (fairly large) picture of each of your bookmarked sites. Click on the one you want to visit (or Ctrl+Number). T
Re:Full 'nix for arm? (Score:4, Interesting)
It depends SO much in what people are trying to accomplish that the discussion is NOT worth it.
I mean, if im a designer, the mouse is better. If im a programmer, the keyboard shortcuts will be the best way to not loose the rythm (yeah, there is rythm in this bussiness).
If Im a bussiness exec, I dont know why I have a computer.
Re: (Score:2)
I agree 100%. GNOME has those stupid big ugly buttons (which always look better with ugly colours too; brown, beige, etc). And I've heard 'The bigger the better'. Even the old KDE design guide says it. Regardless, there is a reasonable limit and GNOME just goes too far. With that, I found GNOME to be TOO simple as a GUI and not for power-users. KDE all the way.
Re: (Score:2)
Re: (Score:2)
Throwing more powerful hardware at an unstable game will not fix the bugs.
Unless the defect in the game engine manifests itself only on less powerful hardware. Texture management and shader unimplementation bugs tend to act this way.
Re: (Score:3, Informative)
Throwing more powerful hardware at an unstable game will not fix the bugs.
Unless the defect in the game engine manifests itself only on less powerful hardware. Texture management and shader unimplementation bugs tend to act this way.
While that is technically possible, I've seen Fallout 3 on 8 and 9 series graphics cards with plenty of crashes. Besides, Fallout 3 wouldn't run on a Geforce 3 anyway - I think it is fair to assume the graphics card in question is fairly modern otherwise they would have given up due to framerate issues.
Re: (Score:2)
Fallout 3 is pretty crashy here, too.
Not quite as crashy as the OP (and the patch helped a *little*) but still more crashy than any game I've played in recent memory.
[It's more crashy than Dystopia 1.0, FFS.]
R420 AGP
Athlon XP @ 2.1Ghz
2 GB of DDR400 RAM
SB Audigy PCI
~4GB of swap space.
Re: (Score:2)
The problem is that we are in a state of denial when it comes to scaling usability. Supporting devices with tiny displays using the same library will compromise the mainstream case one way or the other.
Using the same code from mainframe to hand-held may be a beautiful abstraction, but it sucks for real-world users.
Re: (Score:2)
Re: (Score:2)
Gee, your UI can't allow you to choose themes? Has GNOME been so simplified that you can't choose any other theme?
Re: (Score:2)
So use a theme with more padding. siride was saying (I think) that it's not a good default, not that it shouldn't be allowed. I know that one of my number one issues with a lot of GTK+ stuff is that with so much room taken up by toolbars and other crap, the amount of screen real estate available for actual working is kind of small. (Go look at MonoDevelop versus Visual Studio for an example.)
Re: (Score:2, Funny)
Hello? Linus Torvalds? Is that you?
Re: (Score:3, Informative)
Anyway, it would be nice to see a proper "full" linux distribution.
You might want to look at Debian [debian.org]. It has been running on ARM for quite a while.
Too big (Score:2)
The really cheep netbooks in the pipeline, the ones most likely to be ARM based at first, tend to only have 800x480 displays so an app that barely fits in 800x600 isn't going to be usable.
I'm still waiting for one of the cheap netbooks to be available to purchase though. Lots of talk, but to date no URL to go with a credit card to buy quantity one. Really hope the different groups putting together these new ARM based machines can agree on some standards for bootloading and such so each one won't be all bu
Re:Too big (Score:4, Insightful)
I saw a MIPS based netbook for about US $150 a week or two ago. Trying to remember where.
It strikes me that the best way to improve usability of X apps might be to send these little babies off to as many developers as you can find - and then preferably putting a gun to their heads and forcing them to try and use their apps on them.
The gun to the head part, of course, is tongue in cheek - but wow! seldom is such a bad idea so tempting.
Re: (Score:2)
TightVNC's vncviewer doesn't. So try krdc instead.
Re: (Score:2)
That's the one. I love how the site you found poo-poos the specs though. $expletive-string-here, this thing has hundreds of times the ram of machines that only a few decades ago were being used by dozens of scientific users doing real work concurrently, and a processor to easily match that, and it's not considered sufficient to read a news article
Why just netbooks? (Score:3, Insightful)
Sure the big blocky feel of pretty much every window manager out there sucks on my Eee, but this is one reason I stick with GTK+ 1.x. I don't have a 1280x1024 monitor just so I can see the same material I could see on an 800x600 10 years ago but with cleaner rounded edges.
And I have the bigger Eee. 1024x600 resolution, and some dialogs don't even fit on the screen.
Re: (Score:2)
I stick with ion3 because my screen isn't that big. 1024x768. With a tiling wm it feels big, but with gnome, kde, etc I can barely fit a single app on the screen.
Of course, the learning curve for a tiling wm is kind of intense:-)
GTK2.x theming to the rescue (Score:3, Interesting)
Martin Ankerl has a potential solution for you then, he made a HOWTO and has released a compact version of Human and Clearlooks which really make a difference! I even use them when I'm on my desktop these days to cut down on screen bloat. Find the HOWTO and linsk to the themes here: http://martin.ankerl.com/2008/10/10/how-to-make-a-compact-gnome-theme/ [ankerl.com]
--bornagainpenguin
Re: (Score:3, Insightful)
I'm a huge fan of Netbook Remix and "maximus". The former provides an awesome launcher sort of like the Eee's default interface but way better, and the second provides fullscreen, borderless windows. You might see what you think of it.
Yah for the LGPL (Score:5, Insightful)
For too many years the GPL has been killing adoption of Qt. That's a fact. Maybe it shouldn't have. Maybe people should be willing to be dictated to on what license they can use for their product because they dare to use the Qt framework. Maybe that's your opinion.
Of course, now that so many people are piling on-board to use Qt thanks to the license change, I wonder how many of them have actually bothered to read the LGPL [gnu.org]. My favourite part is section 4.
You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications,
Yeah, didn't see that did ya? Almost every boiler plate EULA includes a clause prohibiting reverse engineering and I wonder how many have not been updated to comply with the LGPL (thankfully a lot of us can just ignore these restrictions as the government in our part of the world recognizes reverse engineering as a right that cannot be contracted out of).
I'll be looking for violations.. just for shits and giggles.
Re: (Score:2)
Personally I'll be downloading the Windows version as soon as there is an LGPL variant. I've always wanted to work with Qt, but none of the companies I've worked for would accept the GPL restrictions and they weren't willing to pony up the license fees when they could get GTK-based applications for free.
Qt looks like a nice successor to Neuron Data's Open Interface, based on C++ instead of C with C++ wrappers. Plus Qt seems to have better platform coverage and a much livelier support group.
Re: (Score:2)
Re: (Score:2)
This is true. And you no longer have to worry about the insanity of Trolltech's lawyers who claimed that you couldn't do private commercial development with the GPL licensed library.
Reverse engineering (Score:2)
Certain companies won't touch LGPL for such reasons, preferring apache-licensed stuff.
Re: (Score:2)
Notice the words "for debugging such modifications".
It pretty much means that your users are allowed to attach to your process with GDB to debug their libraries and that's about it.
Re:Yah for the LGPL (Score:4, Insightful)
Note the words "reverse engineering". If you forbid reverse engineering, as typical EULAs do, for any purpose, then that is forbidding reverse engineering for debugging modifications to the library. So they at least need to modify their EULA to permit reverse engineering for this purpose. And it also means they can't put any anti-debugging tricks in the application, because it will interfere with that reverse engineering.
Re: (Score:2)
It's certainly possible to use anti-debugging tricks, if they do not interfere with linked libraries.
In practice, shareware authors can (and do) legally use anti-cracking protectors with their own code if they do not interfere with LGPL libraries.
In any case, anti-circumvention prohibitions in EULAs are the most stupid clauses...
Re: (Score:2)
Whatever you say man.
Re: (Score:2)
If you're looking for violations, check out all those little devices (routers, media players etc.) which link to uClibc without shared libraries...
uClibc is LGPL. When it's not a shared library, that conveyes certain rights to a relinkable form of the object code of all applications on the device, including proprietary apps.
I've never seen such relinkable object code of the proprietary apps offered, for download or in any other form. In other words, flagrant LGPL violations everywhere.
Re: (Score:3, Insightful)
Yeah, didn't see that did ya? Almost every boiler plate EULA includes a clause prohibiting reverse engineering
It is my understanding that you can reverse-engineer the LGPLed library, but nothing else. And that isn't much of an issue: the LGPLed part should come with the complete source (or equivalent), so being able to debug/disassemble binaries for which you have the source isn't a big deal. In fact the purpose of this clause (again, to my understanding) is simply to be able to ensure that the source of the LGPLed library indeed corresponds to the binary of said LGPLed library.
So yes, EULAs might need to change
Re:Yah for the LGPL (Score:4, Interesting)
No. You fail. To understand what the LGPL means you need to actually read the LGPL. I know it's scary, but there ya go. The provisions actually say that you have to permit reverse engineering of the application, and take no action to permit said reverse engineering, so that one can debug changes to the LGPL library. The purpose of these provisions is to allow someone to fix problems in the LGPL library and have your application work with those changes.
"" may "" "" consider "" (Score:2)
enough said for now. this is just speculation. nobody is seriously looking into dumping gtk+/gnome.
Re:"" may "" "" consider "" (Score:4, Informative)
Ok, I'll bite.
Top 10 Reasons GNOME isn't going anywhere:
10. Firefox and Thunderbird are GTK+
9. Konqueror and KHTML, without WebKit, is hobbled by severe rendering and JavaScript bugs
8. GIMP is GTK+
7. The OOo KDE integration, last I checked anyway, was nowhere near as good as the GNOME integration.
6. Pidgin is GTK+ and Kopete is still very immature compared to it.
5. Inkscape is a GTK+/GNOME app.
4. Audacity is GTK+
3. Most of the popular major distros have GNOME as the default desktop (Ubuntu, Fedora, Mandriva, Debian, etc.)
2. GNOME is easier to use than KDE
and the number one reason GNOME isn't going anywhere:
1. Germans just love David Hasselhoff!
Re: GIMP (Score:2)
8. GIMP is GTK+
8a. GTK+ is The GIMP Toolkit.
Re: (Score:2)
Frankly, I hope that GNOME+GTK die a quick death.
10. FireFox already has QT build (http://browser.garage.maemo.org/news/10/ff3qt.png). Thunderbird will be easy to port, since libxul is already ported.
9. Who cares about WebKit? I have never seen anyone using Konqueror or Epiphany.
8. GIMP must die. KDE has Krita.
7. That's a problem.
6. Pidgin is dying (mainly because its developers can't find their asses with both hands), Empathy is slowly replacing it even in GNOME. Kopete is maturing very fast.
5. Scribus.
4.
Re: (Score:2)
Just a note: Scribus and Inkscape aren't even close to each other. Inkscape is more akin to Illustrator - it's a vector drawing application - whereas Scribus is more akin to Publisher or InDesign - it's a publishing layout application.
Re: (Score:2)
*looks at krita*
I'm not sure that I like it, but I'll give it a try over the next couple of weeks.
Re: (Score:2)
Wrong. Audacity is wxWidgets, which uses GTK on X11, and the native windowing toolkit elsewhere.
Re: (Score:2)
4. Audacity is GTK+
Wrong. Audacity is wxWidgets, which uses GTK on X11
Until wxWidgets is ported to Qt, all wxWidgets apps will be GTK+.
Re: (Score:2)
9 webkit and khtml were remerged
3 is a good reason, 2 I'd argue with, but is very subjective.
The rest? Who cares? I use KDE and have no issues running them.
Re: (Score:2)
6. Pidgin is GTK+ and Kopete is still very immature compared to it.
Did you mean that sarcastically? Pidgin doesn't even doesn't even support proper metacontacts last time I checked. Every time I've been stuck using Pidgin, it becomes a game of finding out what they've removed "to make it easier".
Re: (Score:2)
Did you mean that sarcastically? Pidgin doesn't even doesn't even support proper metacontacts last time I checked.
"aliasing" multiple contacts to the same name collapses them into a single group. Is this the same as metacontacts?
Every time I've been stuck using Pidgin, it becomes a game of finding out what they've removed "to make it easier".
Yeah. I kinda hate that. ;)
OTOH, I've just stopped using "advanced" features, so maybe I'm a victim of Stockholm Syndrome?
Re: (Score:3, Informative)
Pidgin is GTK+ and Kopete is still very immature compared to it.
I was totally onboard with your post until you said Kopete was immature compared to Pidgin...As far as I am concerned the complete opposite is true. I am regularly a Gnome user but I switched to KDE for a few weeks (for reasons beyond my control) and I completely fell in love with Kopete. It matches GAIM/Pidgin feature for feature then adds 100 more on top of that. Just the appearance and skinning options alone dwarf Pidgin's. All the best Pidgin plugins are represented in Kopete too. Plus Kopete has grea
Re: (Score:3, Interesting)
Most of the reasons you mention are "people are already using it" rather than addressing the question "it's better".
Here's my top 11 (top 6 are not about inertia):
11 Firefox has been ported to Qt
9. Skype is Qt based.
8. Google Earth is Qt based.
7. Qt's cross-platform support is so good that some people (e.g. doxygen) use it who have no/very few GUI components.
6. Qt is C++ based.
5. Localization support. And these guys even thought about making number suffixes right in Czech.
4. Qt is easier to use.
3.
Re: (Score:2)
>> Top 10 Reasons GNOME isn't going anywhere:
You're confusing GTK and GNOME.
>> 10. Firefox and Thunderbird are GTK+
Neither of them "are" GTK. Both can use multiple toolkits to render their widgets. One of these is GTK.
>> 9. Konqueror and KHTML, without WebKit, is hobbled by severe rendering and JavaScript bugs
And this has to do with GTK how?
>> 8. GIMP is GTK+
Great. Haven't used it in years. Most people are far better served with a photo manager that does some light editing than a
Re: (Score:2)
2. GNOME is easier to use than KDE
Huge Myth. So much is missing in Gnome that it makes ones head spin. The reality is that its very easy to do nearly nothing in Gnome, whereas KDE has lots to configure, but actually does something for you.
Re: (Score:2)
GNOME seems to be about on par with Mac OS X in terms of configurability, and I hear that Apple is barely selling any machines these days.
But, seriously.... customization doesn't even need to occur via preference panels (if it needs to happen at all). Developers should strive to write apps that are both simple and intuitive. KDE apps tend to suffer from feature-bloat.
Look at Transmission [transmissionbt.com] versus Azureus [sourceforge.net]: Azureus does a whole lot more, but suffers from *serious* feature bloat. Transmission does almost eve
Re: (Score:2)
Wow, Mandriva is there already? I recall it being a very KDE-centric distro some time ago...
BTW, didn't SUSE switch as well?
Re: (Score:2)
What's wrong with the Layer palette? What am I missing?
Does he mean 800x480? (Score:2)
Most ARM handhelds have 800x480 screens, or smaller. 4:3 isn't that common, unless you're talking about relatively new tablets where larger displays matter.
Gnome is rather heavy. Nice to see them using something lighter, at least until ARM processors reach netbook speeds.
Re: (Score:3, Informative)
hell, at *small* end its 320x200, either color or with 4 bit greyscale
Debian Has Supported ARM For Years (Score:5, Informative)
You mean. for example, Debian GNU/Linux on ARM [debian.org]?
Re: (Score:2)
Just like Debian GNU/Linux couldn't possibly exist without the work of, say, the GNU and Linux developers.
You know, there'd be no need to duck if you'd just say "derived from" instead of "ripped off" :-)
AT LAST (Score:4, Insightful)
Hoo-fucking-ray!
At last some common sense..
Qt outstrips GTK/GNOME just as a GUI toolkit and a bunch of middleware, even before you start thinking about stuff like KDE.
The only thing stopping it's use - at least in the strange mix of preinstalled Linux distributions on standard hardware - was that weird problem of having to have every one of your developers buy a license just to run their app - on a Dell for example - if their license was even slightly incompatible. That was a real turn-off if you were a hardware company wanting to take advantage of open source and build communities around open source software.
I'm glad that so soon after Nokia announced the LGPL relicensing, people are taking notice of what is quite obviously a far superior middleware solution than the GTK/GNOME nightmare, and considering developing solutions that work because of code quality and wealth of features, and not *just* because it's GPL.
Re: (Score:2)
Why? If you were not selling the software you didn't need a commercial licence. The idea was simply to stop people making money from Trolltech's efforts for free, but if you aren't making anything from it (eg. selling the hardware but giving the software away) then you didn't need to give them anything.
Re:what the fuck are you on about? (Score:5, Funny)
Folks, I propose we take this good fellow as the perfect example of a non-biased and uncharged commentator.
Kudos to you on your stellar objectivity!
Re: (Score:2)
It's not an objective view - I've used Qt before, for several projects (it's our standard GUI toolkit where I work).
And, yes, I've done complex applications using it.
Re: (Score:2)
Having to run a compiler means less control over your code. If you are really that anal about it, use assembly, or better yet, just code in a hex editor.
MOC doesn't really do that much. It just generates some much-needed code for limited object introspection. Otherwise, it's not much more advanced than what you already get with the C preprocessor.
hmnn (Score:2)
What *is* happening? (Score:3, Insightful)
Ubuntu Mobile is not switching to Qt.
Ubuntu Mobile is not even considering switching to Qt.
At some point in the future, they may consider switching.
How is this news?
Re: (Score:3, Informative)
I was at the particular session where David spoke. His comment was more along the lines that mobile GUI's were a fast moving target, and Qt may gain more momentum given Nokia acquired it and made it LGPL. (aside, Nokia is now pushing Qt for Symbian/S60 dev)
The comment regarding screen resolution is that the majority of developers haven't designed their GUI under a low res environment, and given that such resolutions are starting to appear again, some work needs to be done.
Re: (Score:2)
So in other words they are NOT seriously consider basing ubuntu mobile on qt or kde in the future? Just so I'm sure I understand right what you're saying... if that is in fact what you're saying. (If it is, it would be somewhat of a relief.)
Kubuntu Mobile? (Score:3, Funny)
How is this news?
It opens the door for Kubuntu Mobile.
Nokia open sourced Qt under the LGPL (Score:4, Insightful)
Qt was already Open Source, of course, under the GPL.
Re: (Score:2)
That is not entirely accurate.
Qt was previously dual-licensed by Trolltech with certain restrictions. If you used the GPL version of the Qt development tools and IDE then it was required a viral GPL license be applied to any application developed. You could not use the "Free" version of Qt to develop a closed source application. I may be mistaken but there may have been other restrictions, such as the ability to develop commercial application with the
Re: (Score:3, Informative)
It was certainly not a traditional GPL software development toolkit in the sense of the restrictions placed on the developer.
Of course it was, it's the GPL, nothing more, nothing less.
What you are referring to is a condition of the commercial license, (to prevent you from finally buying 1 single license to release your 20-man-years-application commercially). You are free to accept, reject, or try and renegotiate the conditions of this commercial license. If you don't like them, stick with the GPL, it's yo
Re: (Score:2)
Qt was already Open Source, of course, under the GPL.
That is not entirely accurate.
Sorry, but that _is_ entirely accurate. Qt _was_ already very much free software and open source, under the GPL.
You could not use the "Free" version of Qt to develop a closed source application.
That is the case with ANY GPL licensed library!
The GPL version of Qt was intended by Trolltech to only be used for educational, non-commercial, and personal use.
It is not true that the GPL'd version of Qt couldn't be used for commercial software development -- any GPL'd software can be used in creating any other piece of software, whether commercial or not. Maybe you meant to say proprietary rather than commercial?
It was certainly not a traditional GPL software development toolkit in the sense of the restrictions placed on the developer.
It WAS a "traditional GPL software development toolkit" in the sense of the rules you had to fol
Kubuntu? (Score:2)
Qt is *NOT* Gnome alternative itself (Score:5, Insightful)
Re:Qt is *NOT* Gnome alternative itself (Score:5, Informative)
Hildon is GTK for Mobile Devices. It was developped by Nokia. One distribution that uses this the most is Maemo. Considering Maemo is a Nokia-motivated (read coded/funded) project, and that Nokia bought Trolltech and told them to GPL Qt, they now have an extra incentive to boost Qt adoption. One of the tactics used to boost Qt adoption is that from their next version of Maemo (code named Fremantle), the UI is going to be moving from Hildon to Qt. Fremantle will still be using the Hildon libraries, but the version after Fremantle (Harmattan?) will include the Qt libraries by default, and will be officially supported.
Considering that Hildon is very closely entied to Maemo, if Maemo drops its use (read: if Nokia drops it), keeping it up to date is going to be a hard task, which is probably why UbuntuM is switching to Qt as well, as they don't want to have to maintain the UI library on their own; quite the smart move.
We've seen full Linux distributions running on ARM platforms for quite a while. Yes, Debian works, Maemo does as well, and some people might even be intersted in projects such as Mer (Mer is project that forked from Maemo and that is basically the Maemo community yelling at Nokia that they'd better not drop support for the n800/n810 in Fremantle, as they're proving they could very well take care of themselves --software wise-- and that they won't buy new devices just because Nokia wants them to). We've even seen fully fledged KDE desktops run on the n8x0, or Android for that matter.
The main problem on these devices is the lack of support for languages like C++. Yes, we have libhildonmm (C++ bindings for Hildon), but this is all pretty limited. They don't add the flexibility and power that Qt has; and they most probably won't ever do so. At this point, the devices are too slow to even think about compiling C++ on it, so most people default to shit languages like Python.
But I digress, let me summarise:
- Nokia created Hildon, and Maemo.
- Maemo uses Hildon.
- Ubuntu Mobile came along, liked Hildon and said "Hey, let's use that!".
- Nokia bought Trolltech, that develop Qt.
- Nokia is switching Maemo to use Qt instead of Hildon.
- Ubuntu Mobile doesn't want to hold on to the losing end, and switches to Qt before Hildon dies.
Re: (Score:3, Interesting)
Someone should mod parent up as informative.
What is striking about all these comments is that there seems to be a lack of clarity about what Ubuntu Mobile is, and whether it even needs to exist.
It's not for netbooks. Netbooks currently run Intel processors, most have 1024x600 displays, and they all can run standard Linux distributions (after the usual wifi struggles). Linpus and Ubuntu Netbook Remix provide alternative desktops with big icons. A lot of people immediately turn that stuff off.
Ubuntu Mobile se
Merging Qt and Gtk (Score:3, Informative)
There is an ongoing discussion [ubuntuforums.org] about the possibility of porting Gnome 3 to use the Qt toolkit over at Ubuntu Forums.
There also exists an Ubuntu Brainstorm Idea [ubuntu.com] with several possible solutions, with Solution #4: Change Qt to render using the Gtk widgets my favorite.
Err... (Score:3, Informative)
You mean something like this [trolltech.com]? It's already in HEAD and will ship with Qt 4.5.
Re: (Score:3, Insightful)
If you want to build from source you should be competent enough to figure out how to download it; it's really not hard. Otherwise, let your vendor do the packaging for you. Most Linux distributions make it so you don't have to care about building anything; and the BSDs make building easy anyhow.
Granted, if you are building from source, Qt's build method is mildly stupid compared to the (end-user) ease of autotools or CMake. But really, if you're just wanting to run programs, let your vendor take care of
Re:Whiney complaints (send to /dev/null) (Score:5, Insightful)
WTF? What is that all about to someone who just wants to run an application that uses Qt?
If you want only to run a Qt-based app then you do not need to do anything except to install the application. It should install the Qt runtime libraries for you.
Why the hell am I even looking at this when I just want to run an application?
A good question indeed :-)
If you want Qt widely used you need to make it easy to get and install.
If you are a developer then installation of Qt is the least of your worries. If you are an end user then, as I said, you should not install Qt at all.
Re:Whiney complaints (send to /dev/null) (Score:5, Insightful)
I know my comment will be burried for saying this, but this kind of crap is what we all know is wrong with open source software. The front end delivery is done by geeks and bean counters who don't actually use the products as end users.
You may notice the fact that QT was originally developed by a commercial company, Trolltech. You may also notice the fact that since, until lately, they sold commercial licenses for the same software they licensed as GPL, practically all contributions to the 'main' branch of QT were done by Trolltech (and now Nokia) employees. Therefore, if anything, this proves the failings of cathedral-style development, of which closed-source is the biggest exponent.
Ohh and also, being a person unwilling to use pre-compiled packages to be able to use a library you do *not* plan to use as a developer puts you amongst the minority of a minority of a minority of users, therefore do not be surprised if Trolltech/Nokia doesn't care about you at all.
Re: (Score:2)
Re: (Score:2)
I'd say "what we all know is wrong with open source software" is what is actually right about it. I'm sorry that the fact that it runs on multiple platforms and is available under multiple licenses inconveniences you. Perhaps you should check out http://www.microsoft.com. Most of their stuff runs on exactly one platform and is available under one license, so you won't have to worry about making those pesky decisions.
Re:Whiney complaints (send to /dev/null) (Score:4, Informative)
If you want Qt widely used you need to make it easy to get and install.
They (Qt Software) make it easy to use and install for their intended user-base. Namely: developers
As an end-user you have no business going there.
The applications you are trying to install should be installed using apt-get which will install the needed Qt libs. .deb for the requested app, apt-get ubuntu's libqt4-dev, download the source, go to the source directory where the .pro (project) file is located. run qmake-qt4 in that directory and then run a normal make.
If there's no
It's not that hard, even from sources. Sure, some problems might arise if the app is using features of a newer Qt version than the 1 bundled with your distro. Even that is easy to solve if you are a developer and if you're not, go complain to the author of the app...
Re: (Score:2)
(I could see this becoming a meme)
Linus Torvalds is a god damn thief!!! I gave Linux my credit card number, and two days later, he stole my virginity! Again!