After blogging about Polka, my experiment with a radically new take on an address book, I got a lot of great feedback. I appreciate all the comments, questions, and encouragement. Two people made me particularly happy, as they not only sent feedback, but also contributed some welcome work. Sascha Manns built packages, and Saleel Velankar created a beautiful logo. Free software rocks.
When I started with Polka, one of the main ideas was to not do a traditional desktop user interface, but try out something more natural. One of the side thoughts was that this kind of interface might also work well on some non-desktop devices, for example on devices with a touch interface. But I didn't really know, if it would work. So I decided to try it out.
My first attempt resulted in a port of Polka to MeeGo. MeeGo is a system targeted at touch interfaces, and being Qt based it seemed to be close enough for a getting Polka to work on it. It took me a while to get a working development environment set up, but thanks to Google, and careful study of a bunch of Wiki pages, I finally was able to create MeeGo packages with QtCreator and run them in an emulator.
Porting Polka then was not a huge effort anymore. The proven approach of bundling it with a mini version of kdelibs covering only the functionality required by Polka on MeeGo worked out well again. So here is Polka Touch.
Unfortunately I didn't have a MeeGo device, and the emulator only gives a very limited impression, of how the user interface works. So I needed real hardware, and luckily I came across some cheap WeTab.
The WeTab comes with some version of MeeGo, but I didn't bother with trying to build packages for it, but installed openSUSE. Again some Googling and studying of Wiki pages was required, but then openSUSE ran on the WeTab like a charm. The WeTab might not be the greatest tablet hardware from an end user's perspective, but for a developer it's great. I even was able to compile Polka directly on the tablet.
So how does Polka work on a tablet with a touch interface? It works surprisingly well. Arranging people by moving them around on the canvas feels even better than on the desktop. The menus work well, not using traditional desktop menus definitely is a win here. The dialogs for input of data, are not that great, but it should be straight-forward to adapt them to some more native method to gather data from the user. Another thing which needs some improvement is the use of the canvas background to show a menu for adding labels. This is easily activated accidentally by just touching the screen. It would be better to support scrolling the canvas with touching the background. This might even be interesting on the desktop version.
Overall I have to say it's fun to use Polka on a tablet. Still needs some tweaks, but the first experience is already quite good. It's nice, when ideas work out.
How does it look like when you have hundreds of contacts?ReplyDelete
@uetsah: Polka is not designed for hundreds of contacts. It's designed for the groups of people you care about, where you actively maintain data. You could think of it as the inner circle of your contacts.ReplyDelete
That said, I don't know how it looks like with hundreds of contacts. I never tried.
I have a few suggestions, which I'm ready to implement myself if you give the go -ReplyDelete
1. Allow a menu action to be the default for that menu, meaning the action will be activated when i click on the item instead of hovering over it(for example, I am instinctively clicking on a contact when I want to 'show' it, a provision may be kept to make 'show' the default action in that menu)..
2. Allow custom fields to be added for contacts, for example, i may like to add IRC nick for some people, without putting it in the comment section.. I don't know how much this will be possible, I haven't looked into the data handling code yet.
Nevertheless, the solution for storing Address data in this way seems beautiful to me...especially has huge potential for the mobile platform... and no less on the desktop. Great work. Take a bow!
@Wyuka: I'm ok with 1. (and thanks for the patch :-). I'm hesitant with 2. What's wrong with putting it into the comment? There is so much additional unstructured data, does it really make a difference, if it's in a dedicated field or a comment?ReplyDelete