Amazing Art Skills; Amarok Database Schema and such

The Graffiti Facebook app, despite looking pretty lame initially, turns out to be a lot of fun. It's very simple. There's only one tool, a brush, and it only has three parameters: opacity, width and color.

Check out Seb's Amarok icon:

I retaliated with a Tux:

So OK, Seb's Amarok is better.



This weekend I was visiting my Aunt and Grandma and so was without Internet. I had some fun with Krita and Inkscape.



In (more relevant) Amarok news, I plan on spending some time tomorrow devoted to thinking about the Amarok 2 SQL schema. My Summer of Code project is supposedly about the playlist, but really its more then that since pretty much every major subsystem in Amarok 2.0 is getting a rethink. This includes a complete overhaul and much-needed normalization of Amarok's database schema. I'm thinking of saving the playlist state in the database (to ease and speed up undo/redo, make it crash-proof), so to procede much further on the Playlist::Model rethinking the playlist model is needed.



Similarly all of the various Amarok systems need to be ported to our new (and absolutely fantastic) Meta:: framework from the currently MetaBundle before they can be used by the Playlist::Model.



Its easy to get mired in trying to understand some piece Amarok code. I need to work on creating smaller goals as I go along.