the only reason why i mentioned it is because the accelerometer page on the wiki currently contains such an overview.<br>it shows multiple ways to do the same thing, some in python, some in c and even differences there.<br>
it seems to work well and give information to people who need it, no matter which language or method they prefer :)<br><br><a href="http://wiki.maemo.org/Accelerometers" target="_blank">http://wiki.maemo.org/Accelerometers</a><br>
<br>gary<br><br><div class="gmail_quote">On Fri, Feb 12, 2010 at 9:44 AM, Michael Hasselmann <span dir="ltr"><<a href="mailto:michael@taschenorakel.de">michael@taschenorakel.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">> ext Gary Birkett wrote:<br>
> > there is more than one method of doing everything.<br>
<br>
</div>But that's part of the problem, at least for newcomers. They look for<br>
the best/easiest way, most likely.<br>
<br>
Am Freitag, den 12.02.2010, 10:29 +0200 schrieb Quim Gil:<br>
<div class="im">> There is a good point behind this which is how to cross use cases with<br>
> technologies. I don't think the answer is to aim to cover all<br>
> technologies equally for each use case e.g.<br>
> How to get a nice % progress bar<br>
<br>
</div>I wouldn't neccessarily expect that the solution to a usecase looks<br>
similar with each toolkit. If you then start to explain the exceptions<br>
(and why things are different) then you'll quickly blow up the size of<br>
the tutorial-style usecase, without helping the reader. It'll only add<br>
to the confusion.<br>
<div class="im"><br>
> I guess developers first make a decision about the toolkit they are<br>
> going to use and then expect to find documentation specific to that<br>
> toolkit. Cross-links are nice but that's it.<br>
</div>> [...]<br>
<div class="im">> Looking at <a href="http://wiki.maemo.org/Documentation/Use_case_template" target="_blank">http://wiki.maemo.org/Documentation/Use_case_template</a> it is<br>
> not clear whether such links should be placed in the intro, Related<br>
> APIs... Tips & Tricks would force the template too much.<br>
<br>
</div>A title suffix such as ".... (gtkmm)" plus wiki categories would help if<br>
one wanted to make usecases available for all toolkits.<br>
<br>
regards,<br>
<font color="#888888">Michael<br>
<br>
<br>
</font></blockquote></div><br>