CSC 290A, Spring 2009: Wiki-related Hints

The following page lists some general TWiki formatting and managing hints, plus some conventions we are following throughout the class wiki pages. Assignment submission through TWiki, or any other user-added content, could/should stick to these guidelines.


To format your answer, you can use wiki editting short-cuts, html, or an pdf file upload. Here are some useful resources:

  • TWiki Welcome Page: The department TWiki welcome page contains instructions and examples on how to create new pages and other basic operations . Follow its links !
  • TWiki Formatting Rules: for simple instructions on wiki formatting
  • TWiki Access Control: contains information specifically on how to set up access control for your topics. For the assignments in our class, we want the instructor, the TA, and the assignment author to have read/write/move access, so you should set the following:
  • It would be nice if you could upload your source code with html-like syntax highlighting. We haven't managed to get javascript to run on wiki (which would do it automatically on our behalf), so we suggest you take a look at the Code2HTML converter.
  • Useful little one liners:
    • prepend an exclamation mark ! to a wiki-word, to have it appear as a regular word
    • surround your "appear as fixed font" text with the equal sign (like this: = this = produces this).
    • surround your "appear verbatim" text with the verbatim tags, as in the following example:
       <verbatim> text goes in here </verbatim> 
  • You can add valid html to TWiki, but TWiki syntax is very convenient. In all, formatting shouldn't be hard - as soon as you get used to it you will find Raw Edit to be the most convenient.
Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r4 - 2009-01-24 - KonstantinosMenychtas
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding URCS? Send feedback