I just added some content to the new cute Qt community website.

Yes, sounds strange. Why should i did it ?
Well, first is known among the distros that qt-creator in first release is not the most friendly to packaging.
Not only beacuse qmake, but because some distros rely on things like splitted packages or 32/64 bits coexistent libs and plugins.
Second, was quite a challenge for me do this, because i need to learn some new tricks ( thanks dfaure for automoc4 help ).

Do you need a new telephone? A mobile one without a wire? Please consider buying a Nokia telephone.
When you buy a Nokia telephone you support free software. Do not buy an iPhone, do not buy a Palm, buy a Nokia.
Were you considering buying a Motorola or an HTC telephone? Think again. Think Free Software. Buy a Nokia.
Avoid Windows Mobile. Avoid the iPhone. Avoid WebOS. Buy a Nokia with Free Software.

And use Qt and KDE.

Well I have been mumbling for a few weeks now about this "Flo" project and so far I have gotten a ton of encouraging feedback. For those of you who don't know what Flo is, here is a gentle introduction.

“Perfection is reached not when there’s nothing left to add, but when there’s nothing left to remove.” - Antoine de St. Exupery

I have been frustrated with the UI of Flo now for the past week. As mindmaps grow larger, I keep feeling the UI get crowded. Now maybe there is nothing that can be done to fix this. I don't know, but I wonder what you in the audience think. I feel my input is now rendered useless because after 2 years I am so trained on how it works I don't notice the UI braindamages.

I have been facinated with mind mapping now for about 3 years. I have been using it on a regular basis for trying to organize disjointed thoughts, make coherent sense out of brainstorming sessions, and lately for every day design documentation. For those of you not familiar with mindmaps check out the wikipedia link on the subject.

I've been watching the development of KDE for a while, submitting bug reports and testing trunk, and last night I made my first patch. I received an svn account and decided to start working on Amarok 2, for which I'm currently fixing this bug. But I also intend to work on other areas of KDE, after I poke around for a while and learn the general layout of the project. Suggestions?

So I have been working underground for a while on a web framework based on Qt but its gotten out of control and I need more help on it. The initial goal was to write a creole 1.0 compliant wiki based on Qt, but soon it grew into a full framework because of the lack of good C++ tools to do web development.

So far I have the following features working:
1) Simple .UI to XHTML transformations.
2) Basic form widget support ( line edits, selection boxes, buttons etc).
3) Rudimentary DOM event to Qt slots working.
4) Full bidirectional mapping of QVariantMaps to JSON objects.

video Link : http://www.youtube.com/watch?v=GLMrAx4AYqk

In my last blog I found out that Qt is being evil when using QPainter::eraseRect() with a QImage based textured brush. How evil? Well, calling QPainter::fillRect() with the same brush results in something like a 30-50% speedup while achieving the exact same results. Not only that, but the QPainter::eraseRect() codepath makes QImage not thread safe for painting outside the main thread because it is silently using QPixmap behind the scenes.