Difference between revisions of "Coot Janitors"

From CCP4 wiki
Jump to navigationJump to search
 
Line 1: Line 1:
 
'Coot Janitors' is a project to get new people involved in improving Coot, by acting as a clearing house for simple tasks which need doing, and providing documentation for doing them.
 
'Coot Janitors' is a project to get new people involved in improving Coot, by acting as a clearing house for simple tasks which need doing, and providing documentation for doing them.
 
_toc_
 
  
 
== Useful tasks which need doing ==
 
== Useful tasks which need doing ==
Line 11: Line 9:
  
 
== How to get started with Coot development ==
 
== How to get started with Coot development ==
 +
 +
=== Making and testing changes ===
  
 
Build your own coot using the build-it-gtk2-simple script.
 
Build your own coot using the build-it-gtk2-simple script.
Line 17: Line 17:
  
 
In the coot/src directory, the files c-interface.h and cc-interface.hh contain the definitions for all the native scripting functions. The function definitions are in the various c-interface-*.c and cc-interface-*.cc files.
 
In the coot/src directory, the files c-interface.h and cc-interface.hh contain the definitions for all the native scripting functions. The function definitions are in the various c-interface-*.c and cc-interface-*.cc files.
 +
 +
=== Commiting to the repository ===
 +
 +
For now, make a patch file using 'diff -c oldfile newfile' and send it to Paul, Bernhard or Kevin. Paul to develop a policy for external developers. Repository is on Google code here [http://code.google.com/p/coot/].

Latest revision as of 12:22, 27 February 2009

'Coot Janitors' is a project to get new people involved in improving Coot, by acting as a clearing house for simple tasks which need doing, and providing documentation for doing them.

Useful tasks which need doing[edit | edit source]

Improve the documentation. In the coot/src directory, the files c-interface.h and cc-interface.hh contain

XSLT conversion of doxygen markup to texinfo using xsltproc.


How to get started with Coot development[edit | edit source]

Making and testing changes[edit | edit source]

Build your own coot using the build-it-gtk2-simple script.

The go to the autobuild/MACHINENAME-*/coot-VERSION/ directory, you will have a copy of the Coot source code. If you make a modification to any file under this directory and type 'make', then Coot should be rebuilt. You should be able to run coot-real in the src directory.

In the coot/src directory, the files c-interface.h and cc-interface.hh contain the definitions for all the native scripting functions. The function definitions are in the various c-interface-*.c and cc-interface-*.cc files.

Commiting to the repository[edit | edit source]

For now, make a patch file using 'diff -c oldfile newfile' and send it to Paul, Bernhard or Kevin. Paul to develop a policy for external developers. Repository is on Google code here [1].