Done. Please find the first draft here. Please let me know, what you think about it and if you think that the direction is OK The example is a bit superficial , but I think it is possible to show some typical difficulties developer run into, especially regarding the packaging. Based on that I think we could create some more use-case examples like how-to use the location or what else comes into your mind. Feedback welcome!

Daniel

please read through existing comments.


but when that article is ready, please add a link for it to starting qt development -article.

install Nokia Qt SDK beta, http://www.forum.nokia.com/info/sw.n...ia_Qt_SDK.html
it has got a simulator and works on windows and Linux. it is great, and very easy to use.

Creating entry level articles about Qt development is really good.

But, please, don't overlook the fact that no matter how much information you gather and how small you make the baby steps, it won't help unless people are prepared to actually read what the tools tell them.

After having spent some time on this forum, the main reason for questions seems to be that Something failed in Some Way and now Help Is Needed. Nine times out of ten, the poster manages to both leave out what went wrong how and what was expected to happen making it both hard to help out and hard to believe that the poster actually tried to read the tool output.

To facilitate local problem solving, there is a need to help people both activate all the output and have resources to try to understand what has happened. This is, in my mind, best done with a liberal sprinkling of links to gcc/g++/Qt/Python documentation to stimulate people to actually read the documentation and very obvious encouragement to actually do it.

I have no idea how to unhide tool output in the IDEs that are recommended, but I'm sure someone might be able to provide this information. Links to documentation are easily found with Google and an FAQ section that is tool specific might be needed too.