Re: documentation building: tutorials [was: what is going on with gtk.php.net?]

> I think there should be a series of tutorials, each tutorial covering > one theme, but in detail. Not only a "this is the function, and this are > its parameters" - we've got the reference for this - but a small demo > application which combines all the needed functions. The demo apps > should only contain the functionality needed for the tutorial, no "real" > apps - this would confuse newbies I think. > That makes a lot of sense. I have started at the weekend to write a tutorial, let me give you an outline of what I was planning and I'd like a general concencus as to if it will be useful or I should change to another subject. I build many php-gtk apps at work, so I have built a 'gtk' framework which is a class hiarachy that takes a lot of the grunt work out of writing gtk apps. I cant reproduce that code as it belongs to the company I work for, but I was planning to build a scaled down version of it to show the principles. Along with that I was going to build a small application that uses the framework and would dispatch goods from a warehouse. While not being quite bulletproof enough to be called a real world app would show a lot of the principles involved in building one. At the same time show some of the problems that people will come across building real gtk apps, such as database handles going stale if the app is unused for a while but lest open. Another thing I was planning to cover is how to roll the app out to many machines, not necessarily on the same site and how to maintain the code without having to update on each machine every time. As I started this I realised what a big tutorial this will be and that it may be a little overwhelming. What do you all think. If I'm going to spend my precious time writing an article I would like to make sure it will be useful. Tony