The details of getting a copy of the relevant source code and compilation details first. The source code is being maintained in a CVS repository on vcell. From vcell, the appropriate value for the CVSROOT variable is 
	/home/mooadmin/cvsroot
and the project is named VCell (case sensitive). If you want to access the repository remotely, the current requirement is to use an appropriate vcell login. For remote access, the CVSROOT value should look something like 
	alogin@vcell.ndsu.nodak.edu:/home/mooadmin/cvsroot
with the note that we are currently using password authentication.

You will need a copy of the CosmoPlayer class files to compile the client. A copy of this file (npcosmop.zip) is located at 

	~vender/JavaClients/npcosmop.zip
on vcell.ndsu.nodak.edu. Of course, this file should also be present on any computer with CosmoPlayer installed on.

A command sequence which should work

  1. export CVSROOT=/home/mooadmin/cvsroot
  2. cvs checkout VCell
  3. cp ~vender/JavaClients/npcosmop.zip VCell
  4. cd VCell
  5. chmod +x MakeVCell
which does
  1. Set up the CVSROOT environment variable
  2. Get a copy of the VCell source files from the repository. This will create a VCell directory in the directory you execute it from .
  3. Gets a copy of npcosmop.zip (see above) so the MakeVCell script works.
  4. Move into the VCell directory.
  5. Make the MakeVCell script executable.
Now, if you execute the MakeVCell shell script from your VCell directory, it should compile the java files for the client, and produce a VCellClient.jar file.

In order to test the client, you will either need to either move or copy VCellClient.html VCellTest.html VCellRoot.wrl VCellClient.jar to a subdirectory of your ~/public_html directorary; or move your copy of the VCell directory tree to a subdirectory of your ~/public_html directory.

For technical reasons, the files VCellClient.html, VCellTest.html, VCellRoot.wrl, and VCellClient.jar have to be publicly readable, and the directories between those files and ~/public_html have to be publicly accessible. This is because the client currently won't function correctly without the CosmoPlayer plugin, which only works on Windows using the Netscape browser. This also means that your copy of the four VCell files mentioned above has to be located on VCell.

If you plan on doing your development work in some manner other than telneting into vcell to edit and compile your changes, you have to make sure that the updated jar file and/or class files get copied back to the relevant directories.

On a last note, if you decide to do something reasonable like get a decent IDE to work with the source code, you will need to figure out how to make your environment import a zip or jar archive of class files. The npcosmop.zip contains the class files for CosmoPlayer's implementation of the EAI, without which the client will not compile.