Open mxgrey opened 9 years ago
This is also a good opportunity for us to revisit all the old examples we have. Some are still good but need to be modified for DART 5.0 framework. Before we come up with a list of examples, let's first figure out the table of contents of our tutorial document. Once we know what topics we want to cover, it's easier to generate examples ideas for each topic.
This is a straw man proposal for the tutorial topics and examples. It includes what we currently have in dart-tutotiral.pdf and new features in later versions of DART.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
With all the new features coming up in the 5.0 release, it would seem appropriate to create some example applications that showcase the new DART features and how to use them.
The questions I have are: (1) What are some good toy problems for showcasing the features, and (2) What format should we use for the examples?
With respect to (1), it would be good to discuss what kinds of problems people are interested in, and what kinds of things people want to use DART for. I think there are some obvious simple things we can do:
I have more ideas for examples that might be interesting, but many of them would require more interaction than what we can get with the current SimWindow. Once I have the OSG features finished, I'll make more examples using that.
If anyone has ideas for more examples, or features they'd like to see in action, let me know. In particular, I think we should do something to demonstrate the use of Frame semantics, but I haven't thought of a good example yet.
Now regarding question (2) above, the way I would like to do this would be something like the
examples
folder that I have in my OSG branch. Each .cpp file is an individual and self-contained example. This is in contrast to the currentapps
directory in DART where each app has its own folder. I think putting all the code into a single file would be less confusing for beginners, and I don't think any of these examples would require very much code anyway.