[maemo-developers] Request: Tutorials & use-cases for documentation
From: Michael Hasselmann michael at taschenorakel.deDate: Fri Feb 12 11:44:06 EET 2010
- Previous message: Request: Tutorials & use-cases for documentation
- Next message: Request: Tutorials & use-cases for documentation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> ext Gary Birkett wrote: > > there is more than one method of doing everything. But that's part of the problem, at least for newcomers. They look for the best/easiest way, most likely. Am Freitag, den 12.02.2010, 10:29 +0200 schrieb Quim Gil: > There is a good point behind this which is how to cross use cases with > technologies. I don't think the answer is to aim to cover all > technologies equally for each use case e.g. > How to get a nice % progress bar I wouldn't neccessarily expect that the solution to a usecase looks similar with each toolkit. If you then start to explain the exceptions (and why things are different) then you'll quickly blow up the size of the tutorial-style usecase, without helping the reader. It'll only add to the confusion. > I guess developers first make a decision about the toolkit they are > going to use and then expect to find documentation specific to that > toolkit. Cross-links are nice but that's it. > [...] > Looking at http://wiki.maemo.org/Documentation/Use_case_template it is > not clear whether such links should be placed in the intro, Related > APIs... Tips & Tricks would force the template too much. A title suffix such as ".... (gtkmm)" plus wiki categories would help if one wanted to make usecases available for all toolkits. regards, Michael
- Previous message: Request: Tutorials & use-cases for documentation
- Next message: Request: Tutorials & use-cases for documentation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]