On Thursday 15 September 2011 11:45:36 Alan Alpert wrote:
> This sounds to me like it's missing a key point of our examples. They aren't
> just there for documentation, they're also very useful for validation and
> testing. The examples for a feature are currently one of the few ways we
A bit late, but ... Two things I miss dearly from the current example
structure:
1. No reference-to-example linking, so when looking at a class, one sees
snippets (good), but if one wants to quickly fire up an example implementing
that (to avoid boilerplate and copy-paste-itis), one has to traverse/search
through examples (or demos) and try to figure out just which ones use the
class in question.
2. Clear indication what (and which version of it) the example is an example
for (this ties into the validation part). I understand that examples are
supposed to be short, but we often lack context. The examples are just
extracted into a directory hierarchy that does not reflect
requirements/recommendations, so it's not that easy to tell if an example
fails that it's really a failure, or is it just being used with the wrong
target/Qt version/settings/use case. This was especially true for Mobility
classes, but as those are headed for inclusion into Qt5 modules, I guess
that's the same story.
Best regards,
Attila Csipa
_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
