-
Notifications
You must be signed in to change notification settings - Fork 41
TutorialsTNG
We need to replace the dated and monolithic (SasView 2.x) Tutorial (here) that presently ships with SasView 4.x with new materials that are fresh, engaging, and modern.
Several existing tickets relating to the provision of 'tutorials' are now captured on this wiki page and the corresponding tickets closed:
- SasView/sasview#521 - Need new tutorial documentation
- SasView/sasview#649 - Add Pr Tutorial module
- SasView/sasview#650 - Add Invariant Tutorial Module
- SasView/sasview#651 - Add 1D model fitting tutorial
- SasView/sasview#652 - Add 2D model fitting Tutorial
- SasView/sasview#653 - Add constrained fit Tutorial
- SasView/sasview#654 - Add simultaneous fitting tutorial
- SasView/sasview#655 - Add Batch Fitting Tutorial
Some of the 'next generation' material will require our SasView documentation build processes to produce PDF files. Tickets relevant to this are:
- SasView/sasview#643 - Build PDF documentation along with HTML
- SasView/sasview#1009 - Add LibreOffice to Build Servers
- SasView/sasview#1014 - Slurp tutorial repo for tutorials
- SasView/sasview#1015 - Build new tutorials as PDF
Once LibreOffice is installed on the Build Servers it will also be straightforward to output the 'next generation' material as HTML and eBook. Tickets relevant to this are:
- SasView/sasview#1016 - Build new tutorials as HTML
- SasView/sasview#1017 - Build new tutorials as eBook
The issue of 'tutorials' has previously been raised on this Wiki at:
- http://trac.sasview.org/wiki/Documentation%20Work%20Package (first created Jan 2015)
- http://trac.sasview.org/wiki/Rework%20Proposal (first created Mar 2016)
Wojciech has also made some suggestions regarding frameworks and infrastructure for new tutorial material in this document
Any tutorials we produce will be part of a bigger portfolio of 'documentation' comprising:
- the in-program Help (actually called 'Documentation' in SasView itself) - this is invariably the first place any Sasview User looks for answers
- the Tutorials themselves
- the SasView Website - which has a good FAQ page created from actual questions from Users & links to other resources
- the SasView TRAC site - primarily for the Development Team, but a lot of content should be accessible to 'advanced' Users
Whilst there will be some cross-over between these different strands they should not seek to duplicate material unnecessarily.
A Tutorial is self-paced instruction that provides a step-by-step approach to some learning unit.
It should be interactive, visual (and/or possibly audio), goal-driven, and provide some form of feedback or test of learning (such as through question-answer exercises and/or providing access to comparative results).
The problem with the Tutorial definition above is that it potentially encompasses a wide range of delivery mechanisms. Within the SasView project we are, of necessity (given our available resources), going to need to focus on providing the key material in the most accessible form. That means Tutorial documents in HTML, PDF, and possibly (since the production overhead should essentially be zero given the first two) eBook formats.
Anything else simply cannot be a priority for us at the moment. It could, however, be provided by enthusiastic members of the Community if they so wished…
If we agree that we shall provide some Tutorial documents then, to ease production, maximise buy-in, and encourage Community contributions where applicable, we need a production platform that is free , intuitive (ie, WYSIWYG), and suitable for version control using TRAC. (The current Tutorial is written in Microsoft Powerpoint which only meets one of these criteria).
After looking around Andrew identified two possibilities:
- Oxygen XML Editor
- LibreOffice Writer - this is what used to be Open Office
Both of these are WYSIWYG and both provide output in a 'flat' Open XML format which would allow git to do difference-checking for version control purposes. But only LibreOffice is free.
Steve & Andrew tested git with a LibreOffice Writer .fodt file that they both independently edited and git behaved as expected.
Recommendation: We should use LibreOffice Writer to generate Tutorial documents saved in .fodt format
Click here for the current list of Tutorials and instructions on how to write and contribute them.
- View/Subscribe to the SasView Calendar
- Fortnightly developer's agenda/minutes
- Developer Guides
- Admin Processes and Procedure Notes
- Active Project Pages
- Historical Archive of Obsolete Pages
- Contributor e-Learning Course (free)
- Non Coding contribution needs/projects
- New functionality projects
- DRAFT for acknowledging contributions