Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

General Turnin Information

For this class, students will use the OwlSpace system to turn in assignments.

Students are also encouraged to use svn (subversion) to keep a cumulative record of the code they write for assignments. There are many resources available online if you want to learn more about subversion and its advanced features.

Since we are using the OwlSpace system for assignment submission, the use of svn is purely optional for students' benefit. With svn students can always recover prior versions of the program that you have committed to the svn repository.

File Names and Directories

For the first six weeks of this course, all programming assignments are written in the Scheme programming languages. All solutions to Scheme programming problems in an assignment should be placed in a single .ss file. Similarly, all solutions to the free response questions in an assignment should be placed in the same .ss file within block comment brackets.

For the remaining nine weeks of the course, programming assignments will be written in Java. These Some Java assignments all will involve creating multiple files. To submit a multi-file assignment, place those files in a separate directory (with a name as described below) and create a .zip file for that directory.

File names Files should be named with partner netIDs separated by a hyphen followed by a hyphen and the assignment abbreviation and either the .ss extension (for Scheme programming assignments requiring only a single file) or the .zip extension (for Java assignments consisting of multiple files). For example, the program file for hw01 (in Scheme) submitted by ids gcw5217 and gmalecha should be called gcw5217-gmalecha-hw01.ss . Similarly, the program file for hw07 consisting of a .java program file and a .java unit test file (with the file names specified in the assignment specifications) submitted by ids gcw5217 and gmalecha should be called gcw5217-gmalecha-hw07.zip

...

svn Repository Information

Repository Url:

https://svn.rice.edu/r/comp211/

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3ccf30b6-ad01-4be4-a0d4-5d713a006e2d"><ac:plain-text-body><![CDATA[

User Name:

[your rice netid]

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b2e0ec64-2f1a-421f-a91d-87f020f61fa1"><ac:plain-text-body><![CDATA[

Password:

[your rice password]

]]></ac:plain-text-body></ac:structured-macro>

If you have questions about subversion, please contact one of the labbies and we will respond as soon as we can.

Running svn on Linux

While some graphical clients may exist for Linux, subversion's command line interface is simple and powerful and is the recommended method for accessing subversion from a machine running Linux.

  1. Install svn Installing subversion varies based on the linux distribution that you use. Simply check your package manager ( apt-get , emerge , etc.) for a subversion or svn package and install it the same way that you install all other packages.
  2. *Create a comp211 directory.
  3. Wiki Markup
    *Adding a file to the repository* To add a file to the repository, save the file under your repository directory (the {{comp211/\[netid\]}} directory created by the {{svn checkout}} command) and, from the directory that it is saved in, execute the command. 
    Code Block
    
    svn add [filename]
  4. Committing a file to the server To save your work so that it can be recovered, you must send it to the server (called committing your work). To do this, from the comp211 directory, execute
    Code Block
    
    svn commit -m "[message describing your change]"
  5. Updating the repository You can update your copy of the repository by executing
    Code Block
    
    svn update
    Any work that has been committed to the repository will be copied to your disk and, if there are conflicts, you will have to resolve them.

A typical subversion session might look something like this.

...

.

...

Running svn on Windows

You can download a Windows version of the command line client from the Subversion site. However, you will probably want to use TortoiseSVN, a graphical client for Windows.

...

Creating your directory

...

Adding a file to your directory

...

Wiki Markup
*Adding a file to the repository* To add a file to the repository, save the file under your repository directory (the {{comp211/\[netid\]}} directory created when you checked out the repository). Then, right click on it and select "Add..." from the "SVN" menu.
\!http::^hope.cs.rice.edu/twiki/pub/Teaching/SvnTurnin^windows_add.png\|width=32"799", height=32"599", alt="The"<span class=\!TortoiseSVN Add menu option""/>

...

Updating your directory

...

Running svn in Mac

You can download a command line client for the Mac. After installing it, it works just like the Linux command line client. See the Linux section for further instructions.

Subversion Resources

Access Permissions: (Please don't edit)

...