-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">\r
-<HTML>\r
-<HEAD>\r
- <TITLE>Moodle Docs: How to use CVS</TITLE>\r
- <LINK REL="stylesheet" HREF="../theme/standard/styles.css" TYPE="TEXT/CSS">\r
-</HEAD>\r
-<BODY BGCOLOR="#ffffff">\r
- \r
-<H2>How to use CVS</H2>\r
-<BLOCKQUOTE>\r
-<P>CVS is the Concurrent Versioning System. It's a commonly used way \r
-of storing source code because it keeps versions of all files so \r
-that nothing is ever lost, and usage by different people is tracked.</P>\r
-\r
-<P>To use Moodle's CVS archive (as a developer) from a Unix machine, you first \r
- need to have an account on <a href="http://www.sf.net/">Sourceforge</a>. For \r
- the example, let's assume your username is <strong>myusername</strong> and your \r
- password is <strong>mypassword</strong>. Secondly, you need to contact me (<A \r
- HREF="http://dougiamas.com/">Martin Dougiamas</A>) to get write access \r
- to particular directories.</P>\r
-<P>With that done, you should have all the permissions you need, so you just need \r
- to set up your machine and download the current sources so you can start working \r
- on them.</P>\r
-<P>Sourceforge CVS uses ssh as a transport layer for security, so you will have \r
- to set this CVS_RSH environment variable in your Unix shell:</P>\r
-<blockquote>\r
- <pre><strong>setenv CVS_RSH ssh</strong> (for csh, tcsh etc)</pre>\r
- \r
- <pre><strong>export CVS_RSH=ssh</strong> (for sh, bash etc)</pre>\r
-\r
-</blockquote>\r
-<p>It's best to put this in your .bashrc or .cshrc so you don't have to type it \r
- all the time. Then, check out Moodle using this (all one line): </p>\r
-<blockquote>\r
- <pre><strong>cvs -z3 -d:ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle co moodle</strong></pre>\r
-\r
-</blockquote>\r
-<p>Don't try to do run this first CVS command into an existing moodle directory \r
- - start fresh with a new directory.</p>\r
-<p>Note that you will be prompted for <strong>mypassword</strong> with each CVS \r
- command. To avoid this, follow the <a href="http://sourceforge.net/account/editsshkeys.php">Sourceforge \r
- directions about using authorized keys</a>.</p>\r
-<p>Now, you should have a new 'moodle' directory. You can rename it and move it \r
- around if you like. Go into it: </p>\r
-<blockquote>\r
- <pre><strong>cd moodle </strong></pre>\r
-\r
-</blockquote>\r
-<p>All the latest Moodle files should be in there. You can now change files in \r
- your copy. To compare your files against the main CVS copy on the server use \r
- cvs diff, eg: </p>\r
-<blockquote>\r
- <pre><strong>cvs diff -c config-dist.php\r
+<html>\r
+<head>\r
+<title>Moodle Docs: How to use CVS</title>\r
+<link rel="stylesheet" href="../theme/standard/styles.css" type="TEXT/CSS">\r
+</head>\r
+<body bgcolor="#ffffff">\r
+<h2>Using CVS to access and update Moodle source code</h2>\r
+<blockquote> \r
+ <p>CVS is the Concurrent Versioning System. It's a commonly used way of storing \r
+ source code because it keeps versions of all files so that nothing is ever \r
+ lost, and usage by different people is tracked. It also provides ways to merge \r
+ code if two or more people are working on the same file. All code and all \r
+ versions are stored on a central server (in this case, at <a href="http://www.sf.net/">Sourceforge</a>). \r
+ </p>\r
+ <p>To use Moodle's CVS archive (as a developer) from a Unix machine, you first \r
+ need to have an account on <a href="http://www.sf.net/">Sourceforge</a>. For \r
+ the examples on this page, let's assume your username is <strong><font color="#990000">myusername</font></strong> \r
+ and your password is <strong><font color="#990000">mypassword</font></strong>. \r
+ Once you have an account, you need to contact me (<a \r
+ href="http://dougiamas.com/">Martin Dougiamas</a>) to get write access to particular \r
+ directories.</p>\r
+ <p>To avoid being prompted for <strong><font color="#990000">mypassword</font></strong> \r
+ every time you run a CVS command, follow the <a href="http://sourceforge.net/account/editsshkeys.php">Sourceforge \r
+ directions for using authorized keys</a>. This step is optional, but it can \r
+ make your CVS experience a lot nicer.</p>\r
+ <p>With that done, you should have all the permissions you need, so you just \r
+ need to set up your machine and download the current sources so you can start \r
+ working on them. Below are instructions for Unix and Windows systems.</p>\r
+ <h3>1. Using CVS on Unix</h3>\r
+ <blockquote> \r
+ <p>Sourceforge CVS uses ssh as a transport layer for security, so you will \r
+ have to set this CVS_RSH environment variable in your Unix shell:</p>\r
+ <blockquote> \r
+ <pre><strong>setenv CVS_RSH ssh</strong> (for csh, tcsh etc)</pre>\r
+ <pre><strong>export CVS_RSH=ssh</strong> (for sh, bash etc)</pre>\r
+ </blockquote>\r
+ <p>It's best to put this in your .bashrc or .cshrc so you don't have to type \r
+ it all the time. Then, check out Moodle using this (all one line): </p>\r
+ <blockquote> \r
+ <pre><strong>cvs -z3 -d:ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle co moodle</strong></pre>\r
+ </blockquote>\r
+ <p>Don't try to do run this first CVS command into an existing moodle directory \r
+ - start fresh with a new directory.</p>\r
+ <p>Note that you will be prompted for <strong><font color="#990000">mypassword</font></strong> \r
+ for each command unless you set up <a href="http://sourceforge.net/account/editsshkeys.php">authorized \r
+ keys</a></p>\r
+ <p>Now, you should have a new 'moodle' directory. You can rename it and move \r
+ it around if you like. Go into it: </p>\r
+ <blockquote> \r
+ <pre><strong>cd moodle </strong></pre>\r
+ </blockquote>\r
+ <p>All the latest Moodle files should be in there. You can now change files \r
+ in your copy. To compare your files against the main CVS copy on the server \r
+ use cvs diff, eg: </p>\r
+ <blockquote> \r
+ <pre><strong>cvs diff -c config-dist.php\r
cvs diff -c lang</strong></pre>\r
-\r
-</blockquote>\r
-<p>To fetch the latest updates from the server use: </p>\r
-<blockquote>\r
- <pre><strong>cvs update -dP</strong> </pre>\r
-\r
-</blockquote>\r
-<p>To copy your new files back to the server you would do: </p>\r
-<blockquote>\r
- <pre><strong>cd lang/ca \r
+ </blockquote>\r
+ <p>To fetch the latest updates from the server use: </p>\r
+ <blockquote> \r
+ <pre><strong>cvs update -dP</strong> </pre>\r
+ </blockquote>\r
+ <p>To copy your new files back to the server you would do something like: \r
+ </p>\r
+ <blockquote> \r
+ <pre><strong>cd lang/ca \r
cvs commit</strong> </pre>\r
-\r
-</blockquote>\r
-<p>You will be prompted to add some comments (depends on your default text editor) \r
- ... add a comment and close the editor ... the files will be sent to Sourceforge \r
- and stored. Done! </p>\r
-<p>To save more time you can put default arguments into a file called .cvsrc in \r
- your home directory. For example, mine contains: </p>\r
-<blockquote>\r
- <pre><strong>diff -c \r
+ </blockquote>\r
+ <p>You will be prompted to add some comments (depends on your default text \r
+ editor) ... add a meangingful comment and close the editor ... the files \r
+ will be sent to Sourceforge and stored. Done! </p>\r
+ <p>To save more time you can put default arguments into a file called .cvsrc \r
+ in your home directory. For example, mine contains: </p>\r
+ <blockquote> \r
+ <pre><strong>diff -c \r
update -dP</strong> </pre>\r
-\r
+ </blockquote>\r
+ <p>Try 'cvs help' for more details ... </p>\r
+ <p> </p>\r
+ </blockquote>\r
+ <h3>2. Using CVS on Windows</h3>\r
+ <blockquote> \r
+ <p>These instructions are based on notes provided by Mitsuhiro Yoshida <mits@mitstek.com>.</p>\r
+ <p>Firstly, download and install WinCVS.</p>\r
+ <blockquote> \r
+ <p><a href="https://sourceforge.net/project/showfiles.php?group_id=10072">https://sourceforge.net/project/showfiles.php?group_id=10072</a></p>\r
+ </blockquote>\r
+ <p>Secondly, download sfsetup for SourceForge ssh access, install it and reboot \r
+ Windows.</p>\r
+ <blockquote> \r
+ <p><a href="http://sourceforge.net/projects/sfsetup/">http://sourceforge.net/projects/sfsetup/</a></p>\r
+ </blockquote>\r
+ <p>Next, configure WinCVS. Launch it, and select Admin -> Preferences. \r
+ Then change them as follows:</p>\r
+ <blockquote> \r
+ <p> [General]<br>\r
+ <strong>CVSROOT data</strong>:<br>\r
+ <strong>Authentication</strong>: ssh<br>\r
+ <strong>Path</strong>: /cvsroot/moodle<br>\r
+ <strong>Host address</strong>: cvs.moodle.sourceforge.net<br>\r
+ <strong>User name</strong>: <font color="#990000">myusername</font><br>\r
+ <strong>CVSROOT</strong>: <font color="#990000">myusername</font>@cvs.moodle.sourceforge.net:/cvsroot/moodle</p>\r
+ <p>[Globals]<br>\r
+ <strong>Checkout rad-only</strong>: uncheck<br>\r
+ <strong>Supply control when adding files</strong>: check<br>\r
+ <strong>Quiet mode</strong>: uncheck<br>\r
+ <strong>TCP/IP compression</strong>: check and select 9<br>\r
+ <strong>Dirty files support</strong>: check<br>\r
+ <strong>Prune(remove) empty directories</strong>: check<br>\r
+ <strong>Disable splash screen</strong>: uncheck</p>\r
+ </blockquote>\r
+ <p>Congratulations, WinCVS is set up. Now, you should check out a complete \r
+ working copy of the Moodle course code:</p>\r
+ <ol>\r
+ <li>Select 'Create -> checkout'</li>\r
+ <li>For the setting 'Module name and path on the server", type "moodle", \r
+ then click OK.</li>\r
+ <li>Type in <strong><font color="#990000">mypassword</font></strong> and \r
+ press Enter in the DOS window.</li>\r
+ </ol>\r
+ <p>After this first checkout, you can fetch updated files from the CVS server \r
+ like this:</p>\r
+ <ol>\r
+ <li> Select folders or files you want to update</li>\r
+ <li>Press right mouse button and select '<strong>Update selection</strong>'</li>\r
+ <li>Press OK button</li>\r
+ <li>Type in <strong><font color="#990000">mypassword</font></strong> and \r
+ press Enter in the DOS window.</li>\r
+ </ol>\r
+ <p>After modifying files, you can commit them back to the CVS server like \r
+ this:</p>\r
+ <ol>\r
+ <li>Select folders or files you want to commit</li>\r
+ <li>Press right button and select '<strong>Commit selection</strong>'</li>\r
+ <li>Press OK button</li>\r
+ <li>Type in a meaningful comment and press OK button.</li>\r
+ <li>Type in <strong><font color="#990000">mypassword</font></strong> and \r
+ press Enter in the DOS window.</li>\r
+ </ol>\r
+ </blockquote>\r
+ <p> </p>\r
+ <p align="center">Good luck!</p>\r
+ <p> </p>\r
</blockquote>\r
-<p>Try 'cvs help' for more details ... </p>\r
-<P> </P>\r
-\r
-</BLOCKQUOTE>\r
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id: features.html,v 1.2 2001/12/09 \r
- 10:34:19 martin Exp $</FONT></P>\r
-\r
-</BODY>\r
-</HTML>\r
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>\r
+<p align="CENTER"><font size="1">Version: $Id: features.html,v 1.2 2001/12/09 \r
+ 10:34:19 martin Exp $</font></p>\r
+</body>\r
+</html>\r
-<HEAD>\r
- <TITLE>Moodle Docs: Developers Manual</TITLE>\r
- <LINK REL="stylesheet" HREF="../theme/standard/styles.css" TYPE="TEXT/CSS">\r
-</HEAD>\r
+<head>\r
+ <title>Moodle Docs: Developers Manual</title>\r
+ <link rel="stylesheet" href="../theme/standard/styles.css" type="TEXT/CSS">\r
+</head>\r
\r
-<BODY BGCOLOR="#FFFFFF">\r
-<H2>Developers Manual</H2>\r
-<P>This document describes some of Moodle's design and how you can contribute.</P>\r
-<P>Sections in this document:</P>\r
-<OL>\r
- <LI><A HREF="#architecture">Moodle architecture</A></LI>\r
- <LI><A HREF="#contribute">How you can contribute</A> \r
+<body bgcolor="#FFFFFF">\r
+<h2>Developers Manual</h2>\r
+<p>This document describes some of Moodle's design and how you can contribute.</p>\r
+<p>Sections in this document:</p>\r
+<ol>\r
+ <li><a href="#architecture">Moodle architecture</a></li>\r
+ <li><a href="#contribute">How you can contribute</a> \r
<ul>\r
- <li><A HREF="#activities">Learning activities</A></li>\r
- <li><A HREF="#themes">Themes</A></li>\r
- <li><A HREF="#languages">Languages</A></li>\r
- <li><A HREF="#database">Database Schemas</A></li>\r
+ <li><a href="#activities">Learning activities</a></li>\r
+ <li><a href="#themes">Themes</a></li>\r
+ <li><a href="#languages">Languages</a></li>\r
+ <li><a href="#database">Database Schemas</a></li>\r
<li><a href="#courseformats">Course formats</a></li>\r
<li><a href="#doc">Documentation and articles</a></li>\r
<li><a href="#bugs">Participating in the bug tracker</a></li>\r
</ul>\r
- </LI>\r
-</OL>\r
-<P> </P>\r
-<H3><a name="architecture"></a>1. Moodle architecture</H3>\r
-<P>From a system administrator's perspective, Moodle has been designed according \r
- to the following criteria:</P>\r
+ </li>\r
+</ol>\r
+<p> </p>\r
+<h3><a name="architecture"></a>1. Moodle architecture</h3>\r
+<p>From a system administrator's perspective, Moodle has been designed according \r
+ to the following criteria:</p>\r
<ol>\r
<li><strong>Moodle should run on the widest variety of platforms</strong><br>\r
<br>\r
interface formatting (so that it can be integrated visually into other web sites).</li>\r
</ol>\r
<p> </p>\r
-<H3><a name="contribute" id="contribute"></a>2. How you can contribute</H3>\r
-<P>As mentioned above, Moodle has a number of features that are modular. Even \r
- if you are not a programmer there are things you can change or help with.</P>\r
-<P><strong><a name="activities" id="activities"></a>Learning Activities</strong></P>\r
+<h3><a name="contribute" id="contribute"></a>2. How you can contribute</h3>\r
+<p>As mentioned above, Moodle has a number of features that are modular. Even \r
+ if you are not a programmer there are things you can change or help with.</p>\r
+<p><strong><a name="activities" id="activities"></a>Learning Activities</strong></p>\r
<blockquote> \r
<p>These are by far the most important modules, and reside in the 'mod' directory. \r
- There are seven default modules: assignment, choice, forum, journal, quiz, resource, \r
- and survey. Each module is in a separate subdirectory and consists of the \r
- following mandatory elements (plus extra scripts unique to each module):</p>\r
+ There are seven default modules: assignment, choice, forum, journal, quiz, \r
+ resource, and survey. Each module is in a separate subdirectory and consists \r
+ of the following mandatory elements (plus extra scripts unique to each module):</p>\r
<ul>\r
<li>mod.html: a form to set up or update an instance of this module</li>\r
<li>version.php: defines some meta-info and provides upgrading code</li>\r
</ul>\r
</li>\r
<li>Lastly, each module will have some language files that contain strings \r
- for that module. See below.<br>\r
- </li>\r
+ for that module. See below.</li>\r
</ul>\r
+ <p>The easiest way to start a new learning activity module is to use the template \r
+ in <strong><a href="http://moodle.com/mod/newmodule_template.zip">mod/newmodule_template.zip</a>.</strong> \r
+ Unzip it and follow the README inside. </p>\r
+ <p>You might also like to post first in the <a href="http://moodle.com/mod/forum/view.php?id=44" target="_top">Activities \r
+ modules forum on Using Moodle</a>.</p>\r
+ <p> </p>\r
</blockquote>\r
<p> <strong><a name="themes" id="themes"></a>Themes</strong></p>\r
<blockquote> \r
<p>Themes (or skins) define the look of a site. A number of simple themes are \r
provided in the main distribution, but you may want to copy one of these and \r
customise it to suit your own needs (eg local logo, colours, styles, graphics \r
- etc)</p>\r
- <p>Each theme is in a subdirectory of the "theme" directory. You can \r
- copy the "standard" theme as a template.<br>\r
+ etc). Each theme is in a subdirectory of the "theme" directory. \r
+ You can copy the "standard" theme or any other theme as a template \r
+ for your own.</p>\r
+ <p>Here is what each of the files does:</p>\r
+ <ul>\r
+ <li><strong>config.php</strong>: defines your theme colours used throughout \r
+ the site</li>\r
+ <li><strong>styles.php</strong>: the style sheet, containing CSS definitions \r
+ for standard HTML elements as well as many Moodle elements.</li>\r
+ <li><strong>header.html</strong>: Included at the top of each page. This is \r
+ what you need to edit to add a logo at the top of pages, for example.</li>\r
+ <li><strong>footer.html</strong>: Included at the bottom of each page.</li>\r
+ </ul>\r
+ <p>Note that Moodle upgrades <em>may</em> break themes slightly, so check the \r
+ release notes carefully if you are using a custom theme.</p>\r
+ <p>In particular, Moodle 2.0 will have a completely new display system, based \r
+ on a XSL transformations of XML output from Moodle. It is likely that the \r
+ themes for this will be a completely different format, but the advantage will \r
+ be a much higher possible degree of customisation (including moving elements \r
+ around the page).</p>\r
+ <p>More discussion about this in the <a href="http://moodle.com/mod/forum/view.php?id=46">Themes \r
+ forum on Using Moodle</a>.<br>\r
</p>\r
</blockquote>\r
<p><strong><a name="languages" id="languages"></a>Languages</strong></p>\r
<p>and for modules:</p>\r
<p>helpbutton("forumtypes", "Forum types", "forum");</p>\r
</blockquote>\r
+ <p>Note that you can edit languages online, using the administration web tools \r
+ under "Check this language". This makes it easy to not to only create \r
+ new languages but to refine existing ones. If you are starting a new language, \r
+ please contact me, <a href="http://dougiamas.com/">Martin Dougiamas</a>. </p>\r
+ <p>You might also like to post in the <a href="http://moodle.com/mod/forum/view.php?id=43" target="_top">Languages \r
+ forum on Using Moodle</a>. </p>\r
+ <p>If you are maintaining a language an ongoing basis, I can give you <a href="cvs.html">CVS \r
+ write access to the Moodle source code</a> so that you can directly maintain \r
+ the files.</p>\r
</blockquote>\r
<p><br>\r
<strong><a name="database" id="database"></a>Database Schemas</strong></p>\r
and inside the <strong>db</strong> subdirectory of each module.</p>\r
<p>Currently, only MySQL is supported because that's what I know. If you are \r
familiar with another database (especially open source databases) and are \r
- willing to help port the MySQL schema, please get in contact with me (<a href="mailto:martin@moodle.com">martin@moodle.com</a>).</p>\r
+ willing to help port the MySQL schema, please get in contact with me (<a href="http://dougiamas.com/">Martin \r
+ Dougiamas</a>).</p>\r
</blockquote>\r
<p> </p>\r
<p><strong><a name="courseformats" id="courseformats"></a>Course Formats</strong></p>\r
<blockquote> \r
- <p>Moodle 1.0 supports three different course formats: weekly, topics and social. \r
+ <p>Moodle 1.x supports three different course formats: weekly, topics and social. \r
</p>\r
<p>These are a little more connected to the rest of the code (and hence, less \r
"pluggable") but it is still quite easy to add new ones.</p>\r
<p><strong><a name="doc" id="doc"></a>Documentation and articles</strong></p>\r
<blockquote> \r
<p>If you feel like writing a tutorial, an article, an academic paper or anything \r
- else about Moodle, please do! Put it on the web and make sure you include \r
-
links to <a href="http://moodle.com/">http://moodle.com/</a></p>
\r+ else about Moodle, please do! </p>\r
+
<p>Put it on the web and make sure you include links to <a href="http://moodle.com/">http://moodle.com/</a></p>
\r </blockquote>\r
<p> </p>\r
<p><strong><a name="bugs" id="bugs"></a>Participating in the bug tracker</strong></p>\r
<blockquote> \r
<p> </p>\r
</blockquote>\r
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id: developer.html,v 1.2 2001/12/09 \r
- 10:34:19 martin Exp $</FONT></P>\r
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>\r
+<p align="CENTER"><font size="1">Version: $Id: developer.html,v 1.2 2001/12/09 \r
+ 10:34:19 martin Exp $</font></p>\r
\r
-</BODY>\r
+</body>\r
projects / moodle.git / commitdiff