| Background and Setting |
| Last modified on November 14, 1996 by rms@cs.oberlin.edu. | ||
| Background and Setting |
| HtX was developed and used during a period of three terms | |
| All faculty members shared in the design and testing; Rich Salter wrote the actual implementation. |
| Last modified on November 14, 1996 by rms@cs.oberlin.edu. | ||
| Background and Setting |
| HtX was developed and used during a period of three terms |
| field experience was "fed back" into the design process | |
| We produced weekly laboratory manuals with HtX, adding features as needed, but always with greater generality in mind. |
| Last modified on November 14, 1996 by rms@cs.oberlin.edu. | ||
| Background and Setting |
| HtX was developed and used during a period of three terms |
| field experience was "fed back" into the design process |
| testing included production of large amounts of HTML | |
| A typical weekly lab manual comprises 30-45 pages, including exposition, graphics, exercises, question/answers (with hints), glossaries and examples. |
| Last modified on November 14, 1996 by rms@cs.oberlin.edu. | ||
| Background and Setting |
| HtX was developed and used during a period of three terms |
| field experience was "fed back" into the design process |
| testing included production of large amounts of HTML |
| used to bring student research assistants "on board" | |
| After the first term, student assistants (including course alumni) were using HtX to author lab materials; typical training period was only 1-2 days. |
| Last modified on November 14, 1996 by rms@cs.oberlin.edu. | ||