For me it's:Assaf Raman wrote:I have a general question for the community - what is main use for the samples in the "Unified Samples Framework & Browser"?
1. Show off OGRE with the best samples possible.
2. Give developers use samples of how to use OGRE.
3. Test the major functionality of OGRE to prove that it still works
Followed by 1 and then 2. By nature unit testing visuals is very hard so the samples, plus 'PlayPen' was the way I've made sure bits still function correctly.
In the context of 2 it's a source of "snippets" rather than a from-the-ground-up tutorial. The thing is, people can learn from a tutorial, then when they have all the groundwork they can cherry pick ideas from the samples. They catagorically don't like starting with the samples; they didn't like that when it was ExampleApplication, they'll like it even less with SampleBrowser which has even more moving parts (which is of course perfect for our purposes, just not for the total newcomer).
I'm all for adding new samples testing / demonstrating other things. Regarding PlayPen, it would be great to refactor it so that it plugs in all of its test routines as separate samples but from one DLL, in its own category, but only when BUILD_TESTS is enabled. That will be ideal for quickly testing things.