Welcome back dear readers. This is my second post of the day talking about what is happening in the development of animated layouts in Qt Kinetic.
As I said in my previous post, we discussed about new good examples that could show use cases of this new API. In the end, only one example was created, but it’s really cool =) .
Maybe some of you will recognize this interface, it looks like canola2’s main menu, another software developed by INdT for Nokia internet tablets (e.g. N810) -- and as you can read here, an old bug was fixed and canola2 is now a free software, released under GPLv3. In this post you can read more about the development of that interface.
So, we wrote an example based on that concept. During the development we had nice discussions regarding the algorithm for the engine that controls the icons distribution on the screen.
Check it out:
http://www.youtube.com/watch?v=eJcTBJaPRZg
The source code is not available yet, but it will be published soon in a git repository near you, then you will be able to check how animated layouts were used and also see that algorithm I’ve just mentined. So, stay tuned!
A quick introduction: in the end of February I posted a video showing the first example of layouts animations. At that time, the API wasn’t complete and there was no integration with states and some stuff were hardcoded.
In March some Trolls visited Recife to speak at Bossa Conference 2009 (you can watch the presentations on http://openbossa.blip.tv). It was nice because we could talk about the work we’re doing together using whiteboards, what makes a huge difference =) .
After Bossa, we continued the development of the Animated Layouts API, making layout proxies transparent and integrating with the Qt State Machine Framework. It now allows the customization of animations per widget, bringing more flexibility in the creation of rich user interfaces using Qt.
The following video shows the old example with these improvements:
link: http://www.youtube.com/watch?v=wZo1wskBs0A
After that, we created some examples in order to show use cases and also to test what had been developed, but it is the next post’s subject! (remember what I said in the beginning? )
)