*************************************************************************
* The P.R.O.F. plug-in lets the user publish projects to be downloaded with
* the Ambient plug-in. P.R.O.F. The plug-in depends on Ambient and WILL NOT
* work if ambient is not installed.
*************************************************************************

Setup:
1.
The CVS space used by the Ambient plug-in should have the following structure:
                 __CVSROOT___
                |     |      |
               CPS6  CPS100 CPS108......
In order for the publisher in P.R.O.F. to work, a directory named ".bin" 
should be created under the CVS root, containing the following scripts
(copy them from publisher_scripts):
 
publisher.sh
setup_students.sh
setup_project.sh

These files are located in the binscripts directory. 

2.
When a new project is started, the scripts create the folder for the specified
project and the student directories (and set all the permissions). A new
project cannot be started without the file called "students.conf". The file
is located under the course directory in a directory called students:
                 __CVSROOT___
                |     |      |
               CPS6  CPS100 CPS108......
                |
            students
                |
           students.conf

The students.conf file has the following format:

students.conf
--------------------------------
pkn
pgi
pmg3
ola
.
.
.
-------------------------------

Note: The directory containing the student file is not visible to the
students when they checkout projects or to the professors when they publish
projects.

**********************************************************************
* Publishing a project: No screenshots here...
**********************************************************************

When  P.R.O.F. is used for publishing a project, the name of the project
in the Eclipse workspace does not have to  match the name of the project that
the students will check out. For example, the project on the workspace before
publishing might be called "Foo" and be published as "Anagrams". The first 
page of the publishing wizard contains all the projects on the workspace.
The one that has to be published has to be selected. The next page will show
the CVS space. A project can be published as:

1.New Project:
  This will prompt for the location of the project. The user has to selected
  the parent directory for the new project and go to the next page.On
  the next page, the name of the project has to be specified. Example:
  
  
  Before publishing:__________________________________
                _______CVSROOT____
                |      |     |
               CPS6  CPS100 CPS108......
  
If the name of the project is "Foo", the following structure will be created

             _______CVSROOT____
             |      |     |
            CPS6  CPS100 CPS108......
                    |
                    |
                   Foo
        ___________| __________
       |     |     |     |
 .skeleton   pkn  pgi  pmg3...........................

If the project name is foo/part1, the structure will look like this: 


             _______CVSROOT____
            |      |     |
            CPS6  CPS100 CPS108......
                    |
                    |
                  Part1
                    |
                   Foo
        ___________| ___________
       |     |     |     |
 .skeleton   pkn  pgi  pmg3 ...........................


Publishing a project as update assumes that the directory structure has already
been created. A project has to be published with "Start new project" before
published as update....Updating the project will remove the old .skeleton
directory and make a new one. However, if a student has already checked out, 
she/he will not be able to get the update.
