Hi, I am using Qt4 under Maemo with Nokia N810. When I click a QLineEdit field, there comes up a field for handwriting input. How can I prevent this? It overlaps the actual QLineEdit, as this is quite on the lower part of the GUI.

Something which it needs to make clear: is it expected you'd put a package name; upstream unix name; English description; general description. One thing we've seen before (and seen again in Brainstorm) is explaining to users why "port wine" won't solve the problem they think it does.

man_in_shack: Err, Harmattan is roadmapped for release either late *next* year or the year after (my guess). The N810 is over two years old; running a cutting edge mobile OS on (at least) 4 year old hardware seems pretty unreasonable as an expectation.

man_in_shack: Mer's under development, and its developers are some of the most committed and dedicated volunteers in the community. Calling its in-development releases "unstable crap" is just plain trolling.

man_in_shack: You think Nokia is intentionally introducing new OSes which try to compete with the Androids, webOSes and iPhones of this world to gouge money out of existing customers by prematurely obsoleting hardware? Or were you (correctly) just saying that by constantly pushing forward the OS, they're trying to entice in new customers and increase market share in an increasingly competitive market?

man_in_shack: If you want to whine and moan that Nokia isn't going to support it on your device; tough - go somewhere else, we can't help. If you're having problems getting the community-provided solutions working, it seems people are trying to help.

man_in_shack: also, keep in my mind you just badmouthed my baby and i'm -still- helping you - you get very far with being kind and asking out of the blue if anyone can help you with X because you're stuck at Y

man_in_shack: we can agree on that the whole fixed in fremantle/harmattan thing is crap, but it's just because we as community haven't been strong enough to create pipelines for delivering these fixes, or organising people in a manner so it gets done..

man_in_shack: The main point is that this channel is a community channel, not a Nokia support channel. And we're focused on trynig to solve problems: we've done our sitting around in a moaning circle-jerk before and moved on. More productive times.

i thought the problem was that the built-in video chip on the OMAP2 wasn't actually part of the video pipeline because it was too low resolution so there is a different LCD controller powering the screen

Btrfs is under heavy development, and is not suitable for any uses other than benchmarking and review. The Btrfs disk format is not yet finalized, but it will only be changed if a critical bug is found and no workarounds are possible

The real issue is that SSDs have native sector size of a megabyte or so. Harddrives have 512 byte sectors. So in the worst case if you just want to change 512 bytes on the SSD, the SSD itself will read a megabyte and write back a megabyte. In worst worst case, it will read back, erase original, write new modified megabyte. This slows it down

But basically, Sandisk and other "shut up we're the big corporation here and WE will tell YOU how to work around our piece of shit hardware"-companies said that operating systems must learn how to deal with flash storage efficiently

Anyway... on the cheap SSDs their performance is so predictable/measurable that you can experimentally trivially determine the erase block size and other parameters that matter, and optimize your fs for that

BUT, that energy comes from the people (who in turn get it through this expensive sun -> plant -> animal -> processing -> processing -> processing -> microwave -> food chain), or from gasoline in the case of cars :P

pupnik: I decided to flash the OS to the internal memory card, I think there is plenty space to hold the OS and all the software I need, so I just followed the little tutorial up to the partitioning part ... I did even already partitioned my internal flash card