Canonical Voices

What cool people talk about

Posts tagged with 'collie'

Marcin Juszkiewicz

What interest me in ARM world

September 29, 2012

by Marcin Juszkiewicz

Under archos , at91 , beagleboard , bug , collie , default , efikamx , linaro , maemo , nexus , nhk15 , nokia , nslu2 , omap , openmoko , pandaboard , poodle , sheevaplug , sim.one , tosa , ubuntu , zaurus | Comment

When I published my last post about ARM boards there were many questions and suggestions with interesting devices. Thank You all for it.

But there were also suggestions about ARM9 or ARM11 based devices. So I decided that it is good time to write what interest me now in ARM world.

But first some inventory. I had/used/have several devices with ARM cpu:

StrongARM (armv4) one:
- Sharp Zaurus SL-5500 (which took me to ARM world)
ARM920 (armv4t) ones:
- Openmoko GTA01 bv3, bv4 (s3c2410)
- EDB9301 (EP9301 cpu)
- Sim-One (EP9307)
ARM926 (armv5te) ones:
- Sharp Zaurus sl-5600 (pxa250)
- Sharp Zaurus c760/sl-6000 (pxa255)
- Sharp Zaurus sl-c3000 (pxa272)
- Sheevaplug (kirkwood)
- Atmel devboards (at91sam9263, at91sam9m10)
- ST-Microelectronics/ST-Ericsson NDK-15, NHK-15 (st88n15)
- Nokia 770 (omap1710)
- Linksys NSLU2 (ixp425 iirc)
ARM1136 (armv6) ones:
- Nokia N810 (omap2430)
- Bug r1.0, r1.2 (i.mx31)
Cortex-A8 (armv7a) ones:
- Beagleboard B7, B7, C3 (omap3430)
- Nokia N900 (omap3430)
- Nexus S (exynos3)
- Genesi Efika MX Smartbook (i.mx51)
- Freescale Quickstart (i.mx53)
Cortex-A9 (armv7a) ones:
- Pandaboard EA1, A1 (omap4430)
- Archos G9 80 (omap4430)

All of that during last 8 years. Most of my ARM live so far was around ARM926 based devices (some of them still can not be listed here) and I do not want to go there again. Kirkwood core was fastest one with 1.2GHz clock and 512MB of RAM it was really fast machine. I only missed Serial ATA in my Sheevaplug (rev 1.0) but even with hard drive on USB it was nice improvement.

Then I played a bit with ARM11 processors. Ok, they were faster than most of ARM9 cpus but I already had experience with Sheevaplug. And after few months first Cortex-a8 board landed on my desk — I got Beagleboard B7 from Bug labs as test platform for their new device. This was improvement!

I still remember my reaction when connected it to normal LCD monitor and saw it used at 720p resolution (1680×1050 was a bit hard for omap3). Moved to Nokia N900 few months later and found that fast cpu means nothing when paired with slow storage and not enough memory for system.

So today I prefer to not look below Cortex-A9 (or comparable cores like ones from Qualcomm or Marvell). Hope to play one day with Cortex-A5 (which should replace ARM926 one day) just to see how low-end armv7a cpu behave.

And wait for ARMv8 to hit market.

Related content:

All rights reserved © Marcin Juszkiewicz
What interest me in ARM world was originally posted on Marcin Juszkiewicz website

Marcin Juszkiewicz

Is designing UI simple with Qt?

September 17, 2010

by Marcin Juszkiewicz

Under collie , default , maemo , n900 , nokia , openzaurus , opie , qt , zaurus | Comment

I use Qt on my devices since my first LinuxPDA: Sharp Zaurus SL5000 on which I used OpenZaurus with OPIE as primary environment. It was based on Qt/Embedded 2.3.x and was looking ok. UI of most applications work properly in both portrait and landscape modes, adapted to size of fonts (I used smaller then default ones).

Then Zaurus c760 arrived at my place and I did some UI code tweaks to make everything looking better on VGA screen (not that it looked wrong — I just improved few things). At that time I had nearly every Zaurus model in hands and took care to make all looks proper in both orientations.

From time to time I was also playing with 3rdparty applications to adapt them to resolutions higher then QVGA (which was sort of standard in palmtops of that era). Usually loading UI files into Qt Designer and reordering them or adding layouts helped. One of them was Mileage which required adding huge amount of layout elements just to make it look properly (all elements were put as X,Y positions originally).

Some time later I moved to GTK/X11 based environments on portable devices and later my cellphones took PDA place.

But with Nokia N900 I decided to go back to programming with Qt – 4.6 version this time. First was my module player (which I probably never end) and some time later I decided to play a bit with Vexed released by
Paul Romanchenko (rmrfchik on #maemo) where I reorganized UI a bit, added portrait support and did few other tweaks.

But then I switched to ApMeFo and while idea of application is good the UI is disaster:

tabs in main window
lack of portrait support
unusable UI when forced to portrait mode
use of non standard button sizes
use of non standard font sizes

And sources lacked UI files… So one day I decided that it will be good occasion to learn something new. Author was not responding to my sources request so I launched Qt Designer and started to recreate UI from scratch — using existing sources as information what kind of widgets were used. Took me some time but I got new, a bit improved UI which even worked in portrait mode:

But it still was not what I wanted. It still had tabs and small buttons… First I got rid of tabs:

Rest of functionality was moved to menu and separate window:

I was not too proud of it. OK, it looked better, I even changed some non-UI code but it still was not what I wanted to achieve. But at least I had something what I could give to users for testing.

How does it look now? Let me show not yet published version:

First main window — all buttons are finger friendly. I also grouped them a bit — it is visible in portrait mode which is also great when user want to re-order items.

Dialog to select applications to add got some changes too. It is maybe not conform with UI style guide (OK not under but on right) but it gave me extra line in list widget. Think of multi selection…

As you see (de)activation and folders are now in menu. (De)Activation has also Yes/No requesters :)

Folders window is place which needs lot of work. Only delete works now (also with Yes/No requester).

List of things to do is long as users suggested many things. I probably will not add most of them because so far I did not checked how exactly ApMeFo works but once I will read rest of source code I think that something good will come from it.

And is designing UI simple with Qt? I think that it is — developer does not have to worry what kind of paddings are needed to be used, how to place widgets to make UI conform to style guide rules etc. Once you do design with layout elements application adapts itself to what is available.

Share/Bookmark