the only reason why i mentioned it is because the accelerometer page on the wiki currently contains such an overview. it shows multiple ways to do the same thing, some in python, some in c and even differences there. it seems to work well and give information to people who need it, no matter which language or method they prefer :)
http://wiki.maemo.org/Accelerometers gary On Fri, Feb 12, 2010 at 9:44 AM, Michael Hasselmann < mich...@taschenorakel.de> wrote: > > 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 > > >
_______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
