Changes between Version 12 and Version 13 of BoltRef
- Timestamp:
- Dec 13, 2007, 12:05:37 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BoltRef
v12 v13 8 8 * '''Exercises''', used for reinforcement and/or assessment. 9 9 * A '''course document''' describing the order in which lessons and exercises are shown. 10 11 To use Bolt: 12 * [MakeProject create a BOINC project]. 13 * Put your lessons, exercises and course document in the project's html/user directory 14 * Edit and run the html/ops/bolt_setup_sample.php script to create one or more courses. 10 15 11 16 == Lessons == … … 135 140 }}} 136 141 137 == Changing course documents == 138 139 Course documents need not be static. 140 You can change them whenever you want (that's the point of Bolt). 141 142 What happens if a course changes while 143 students are in the middle of it? 144 The general answer is the Bolt recovers as gracefully as possible. 142 === Changing course documents === 143 144 Course documents can change over time. 145 In fact, that's the whole point of Bolt: 146 to constantly study the effectiveness of course materials, 147 and change the course based on the results of that study. 148 149 If a course changes while students are in the middle of it, 150 Bolt recovers as gracefully as possible. 145 151 For each student, Bolt maintains a "course state" - a set of data, 146 152 for each control structure that the student has visited in the course, … … 164 170 * If you change the sequence to (red, yellow) then the student will have finished the sequence. 165 171 166 == Nesting and functions==172 === Nesting and functions === 167 173 168 174 Control structures may be nested. … … 198 204 }}} 199 205 200 == Names and state==206 === Logical names and state === 201 207 202 208 In general, units must have unique logical names.