+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<HTML>
-
-<HEAD>
-
- <TITLE>Moodle Docs: Background</TITLE>
-
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
-
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-
-
-
-<H2>Background</H2>
-
-
-
-<P>Moodle is an active and evolving work in progress.</P>
-
-<P>I've been working on it, in some way or other, for several years. It started
-
- in the 90's when I was webmaster at <a target=_top href="http://www.curtin.edu.au/">Curtin University
-
- of Technology</a> and a system administrator of their WebCT installation. I
-
- encountered many frustrations with the WebCT beast and developed an itch that
-
- needed scratching - there had to be a better way (no, not Blackboard :-)</P>
-
-<P>I also know a lot of people in schools and smaller institutions (and some big
-
- ones!) who want to make better use of the Internet but don't know where to start
-
- in the maze of technologies and pedagogies that are out there. I've always hoped
-
- there would be a Free alternative that such people could use to help them move
-
- their teaching skills into the online environment.</P>
-
-<P>My strong beliefs in the unrealised possibilities of Internet-based education
-
- led me to complete a Masters and then a PhD in Education, combining my former
-
- career in Computer Science with newly constructed knowledge about the nature
-
- of learning and collaboration.</P>
-
-<P>Since then Moodle has progressed through several very different prototypes
-
- until the release of version 1.0 upon a largely unsuspecting world on
-
- August 20, 2002 and a steady series of improved releases since then.
-
-<P>I've been using it in several courses and find it an
-
- extremely usable and reliable tool for building high-quality online courses
-
- - others are reporting the same. Given the context in which it's been designed,
-
- it works particularly well for smaller institutions, or for smaller, more intimate
-
- classes.</P>
-
-<P>When compared to the big commercial tools such as WebCT or Blackboard I think
-
- it still falls short in some areas (such as scalability and standards support),
-
- but it comes out ahead in many others (see <a href="index.php?file=features.html">Features</a>).
-
-</P>
-
-<P> </P>
-
-
-
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
-
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
-
-
-
-</BODY>
-
-</HTML>
-
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<HTML>
-
-<HEAD>
-
- <TITLE>Moodle Docs: Credits</TITLE>
-
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
-
-</HEAD>
-
- <BODY BGCOLOR="#ffffff">
-
-
-
-<H2>Credits</H2>
-
-
-
-<P><B>Moodle </B>itself is Copyright © 2001-2002, <A TARGET=_top HREF="http://dougiamas.com/">
-
- Martin Dougiamas</A>. It is distributed under the <A HREF="licence.html">
-
- GNU Public License</A>.</P>
-
-
-
-
-
-
-
-<H3><BR>Special thanks</H3>
-
-<UL>
-
- <B><A TARGET=_top HREF="http://pctaylor.com">Dr Peter C. Taylor</A></B>,
-
- at Curtin University of Technology in Perth, Australia, for working
-
- with the earliest prototypes and making many useful suggestions along the way</LI>
-
-</UL>
-
-
-
-
-
-
-
-<H3><BR>Translations</H3>
-
-<BLOCKQUOTE>
-
-<P>Many thanks to these people - each translation takes many hours of work, as there are nearly
-
- 900 phrases to translate (plus all the help files!).
-
- These are listed in the order they joined the project:
-
-<UL>
-
- <LI><B>en - English</B>, by Martin Dougiamas
-
- <LI><B>fr - French</B>, by SñÃastien NamïÄhe, seb@gaia.anet.fr, <A HREF="http://gaia.anet.fr/">http://gaia.anet.fr/</A>
-
- <LI><B>fi - Finnish</B>, by Petri Asikainen (paca@sci.fi), Jaana Tolvanen (jaanat@cedunet.com)
-
- <LI><B>it - Italian</B>, by Davide Suraci, icarused@tiscalinet.it
-
- <LI><B>pt_br - Portuguese (Brazil)</B>, by Fabricio Valadares, webdesigner@unincor.br
-
- <LI><B>de - German</B>, by Holger Schadeck, Holger.Schadeck@webdesign-forum.de
-
- <LI><B>es_mx - Spanish (Mexico)</B>, by Claudio Tavares, <A HREF="http://enlaceacademico.com">enlaceacademico.com</A>
-
- <LI><B>es_es - Spanish </B>, by Antonio J. Navarro Vergara, anavarro@sextaisla.com, <A HREF="http://www.sextaisla.com">www.sextaisla.com</A>
-
- <LI><B>ca - Catalan</B>, by Carles Bellver with the help of Merc\8eè Renau,
-
- Clara AndrñÔ and Jordi Adell, cent@uji.es, <A HREF="http://cent.uji.es">Centre d'Educaci\8eó i Noves Tecnologies</A>
-
- <LI><B>no - Norwegian</B>, by Jøran Sørb\8eø, joran.sorbo@teleweb.no
-
- <LI><B>id - Indonesian</B>, by Arfan Hidayat, ivanh@telkom.net, <A HREF="http://www.kursusmaya.com">http://www.kursusmaya.com</A>
-
- <LI><B>ja - Japanese</B>, by Mitsuhiro Yoshida, mits@mitstek.com, <A HREF="http://mitstek.com">http://mitstek.com</A>
-
- <LI><B>tr - Turkish</B>, by M. Cüneyt Birkök, cuneyt@birkok.net, <A HREF="http://birkok.net">http://birkok.net</A>
-
- <LI><B>zh_cn - Chinese</B>, by Zhang Dexuan, cncoolbit@hotmail.com
-
- <LI><B>ar - Arabic</B>, by Ahmed Nabil, ana@harf.com
-
- <LI><B>sv - Swedish</B>, by Set Lonnert, set@setlonnert.com, <A HREF="http://setlonnert.com">http://setlonnert.com</A>
-
- <LI><B>th - Thai</B>, by Wim Singhanart, minkowski@ntlworld.com, <A HREF="http://www.suthira.net">www.suthira.net</A>
-
- <LI><B>nl - Dutch</B>, by Hans Zwart (hans@hansdezwart.info) and Jacob Romeyn (jromeyn@thekingsschool.net)
-
-
-
-</UL>
-
-</BLOCKQUOTE>
-
-
-
-<H3><BR>Themes</H3>
-
-<BLOCKQUOTE>
-
-<P>Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle distribution, along with their authors:
-
-<UL>
-
- <LI><B>standard* and cordoroyblue</B>, by Martin Dougiamas
-
- <LI><B>oceanblue</B>, by Mitsuhiro Yoshida, <A HREF="http://mitstek.com">http://mitstek.com</A>
-
- <LI><B>brightretro</B>, by Thomas Murdock, <A HREF="http://sand-paper.org/">http://sand-paper.org</A>
-
- <LI><B>garden</B>, by Spiggy, <A HREF="http://phpgirl.com">http://phpgirl.com</A>
-
-</UL>
-
-</BLOCKQUOTE>
-
-
-
-
-
-<H3><BR>Other contributors</H3>
-
-<BLOCKQUOTE>
-
-<P>Thanks to all of you who have
-
-<UL>
-
- <LI>donated via the <A TARGET=_top HREF="http://moodle.com/donations">Donations page</A>,
-
- <LI>contributed to the <A TARGET=_top HREF="http://bugs.moodle.com">bug tracker</A>, and
-
- <LI>participated in the "<A TARGET=_top HREF="http://moodle.com/course/">Using Moodle</A>" course at moodle.com</A>
-
-</UL>
-
-</P>
-
-
-
-<P>Especially, thanks to those of you who have at some time contributed
-
- with long constructive discussions and especially code. This list is long
-
- and always changing, but some names include (in the order I added them):
-
- <UL>
-
- Art Lader,
-
- Matt Hope,
-
- Tom Murdock,
-
- SñÃastien NamïÄhe,
-
- Petri Asikainen,
-
- James Miller,
-
- Dustin Rue,
-
- Holger Schadeck,
-
- Giovanni Tummarello,
-
- John Windmueller,
-
- Sean Keogh,
-
- Mitsuhiro Yoshida,
-
- Mark Kimes,
-
- Greg Barnett,
-
- Mary Hunter
-
- </UL>
-
-</P>
-
-
-
-<P>I apologise if for some reason your name is not on this list - it's very
-
- difficult to maintain! Mail me and demand to be on it. :-)
-
-</P>
-
-
-
-</BLOCKQUOTE>
-
-
-
-
-
-<H3><BR>Moodle libraries</H3>
-
-
-
-<BLOCKQUOTE>
-
- <P>Some of Moodle's libraries were written by other people, and are being
-
-redistributed as part of Moodle under the LGPL. My thanks go out to the
-
-authors of all these excellent products - without them Moodle would be missing
-
-important functionality. Copyright information for each package is included below:</P>
-
-
-
- <P><B>ADOdb </B>- lib/adodb<BR>
-
- </P>
-
-
-
- <BLOCKQUOTE>
-
- <P>Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle,
-
-Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.</P>
-
-
-
- <P>Version: 2.00 14 May 2002 <BR>
-
- Copyright © 2000, 2001 John Lim (jlim@natsoft.com.my)<BR>
-
- License: Dual LGPL and BSD-style<BR>
-
- URL: <A HREF="http://php.weblogs.com/adodb" TARGET="newpage">http://php.weblogs.com/adodb</A><BR>
-
- </P>
-
- </BLOCKQUOTE>
-
-
-
- <P><B>Graph Class</B> - lib/graphlib.php </P>
-
-
-
- <BLOCKQUOTE>
-
- <P>Class to draw line, point, bar, and area graphs, including numeric
-
- x-axis and double y-axis.</P>
-
-
-
- <P> Version: 1.6.3 (with modifications)<BR>
-
- Copyright © 2000 Herman Veluwenkamp, hermanV@mindless.com<BR>
-
- License: LGPL<BR>
-
- </P>
-
- </BLOCKQUOTE>
-
-
-
-
-
- <P><B>IP-Atlas</B> - lib/ipatlas</P>
-
-
-
- <BLOCKQUOTE>PHP scripts to show the location of an IP address on a map.<BR>
-
- <BR>
-
- Version: 1.0 (with modifications)<BR>
-
- Copyright © 2002 Ivan Kozik<BR>
-
- License: GNU GPL<BR>
-
- URL: <A HREF="http://www.xpenguin.com/ip-atlas.php" TARGET="newpage">http://www.xpenguin.com/ip-atlas.php</A><BR>
-
- </BLOCKQUOTE>
-
-
-
-
-
- <P><B>PHP mailer</B> - lib/class.phpmailer.php<BR>
-
- </P>
-
-
-
- <BLOCKQUOTE>Class for sending email using either sendmail, PHP mail(),
-
-or SMTP. Methods are based upon the standard AspEmail(tm) classes.<BR>
-
- <BR>
-
- Version 1.60, Created 03/30/2002<BR>
-
- Copyright © 2001 Brent R. Matzelle <bmatzelle@yahoo.com><BR>
-
- License: LGPL<BR>
-
- URL: <A HREF="http://phpmailer.sourceforge.net" TARGET="newpage">http://phpmailer.sourceforge.net</A><BR>
-
- <BR>
-
- </BLOCKQUOTE>
-
-
-
-
-
-
-
- <P><B>PHP Simple Excel File Generator</B> - lib/psxlsgen.php</P>
-
-
-
- <BLOCKQUOTE>Class to generate very simple MS Excel files (xls)
-
-via PHP.<BR>
-
- <BR>
-
- Version: 0.3b<BR>
-
- Copyright © 2001 Erol Ozcan <eozcan@superonline.com><BR>
-
- License: GNU LGPL<BR>
-
- URL: <A HREF="http://psxlsgen.sourceforge.net" TARGET="newpage">http://psxlsgen.sourceforge.net</A><BR>
-
- </BLOCKQUOTE>
-
-
-
-
-
-
-
-
-
-
-
- <P><B>Richtext Editor</B> - lib/rte</P>
-
-
-
- <BLOCKQUOTE>HTML text editor for embedding in web pages.<BR>
-
- <BR>
-
- Version: 0.30 beta 1 (plus modifications)<BR>
-
- Copyright © 2001 Ramesys (Contracting Services) Limited <Austin.France@Ramesys.com>
-
- License: GNU LGPL<BR>
-
- URL: <A HREF="http://richtext.sourceforge.net" TARGET="newpage">http://richtext.sourceforge.net</A><BR>
-
- </BLOCKQUOTE>
-
-
-
-
-
- <P><B>SMTP class </B>- lib/class.smtp.php<BR>
-
- </P>
-
-
-
- <BLOCKQUOTE>Class that can be used to connect and communicate with
-
- any SMTP server. <BR>
-
- It implements all the SMTP functions defined in RFC821 except TURN.<BR>
-
- <BR>
-
- Version: 03/26/2001 <BR>
-
- Copyright © 2001 Chris Ryan <chris@greatbridge.com><BR>
-
- <BR>
-
- </BLOCKQUOTE>
-
-
-
-
-
- <BLOCKQUOTE><BR>
-
- </BLOCKQUOTE>
-
-
-
- <P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
-
- <P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
-
-
-
-
-
- </BODY>
-
- </HTML>
-
+++ /dev/null
-<html>
-
-<head>
-
-<title>Moodle Docs: How to use CVS</title>
-
-<link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">
-
-</head>
-
-<body bgcolor="#ffffff">
-
-<h2>Using CVS to access and update Moodle source code</h2>
-
-<blockquote>
-
- <p>CVS is the Concurrent Versioning System. It's a commonly used way of storing
-
- source code because it keeps versions of all files so that nothing is ever
-
- lost, and usage by different people is tracked. It also provides ways to merge
-
- code if two or more people are working on the same file. All code and all
-
- versions are stored on a central server (in this case, at <a href="http://www.sf.net/">Sourceforge</a>).
-
- </p>
-
- <p>To use <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/">Moodle's
-
- CVS archive</a> (as a <a href="http://sourceforge.net/project/memberlist.php?group_id=30935">developer
-
- with write access</a>), you first need to have an <a href="http://sourceforge.net/account/register.php">account
-
- on Sourceforge</a>. For the examples on this page, let's assume your username
-
- is <strong><font color="#990000">myusername</font></strong> and your password
-
- is <strong><font color="#990000">mypassword</font></strong>. Once you have
-
- a Sourceforge account, contact me (<a
-
- href="http://dougiamas.com/">Martin Dougiamas</a>) so I can give you write access
-
- to particular directories.</p>
-
- <p>To avoid being prompted for <strong><font color="#990000">mypassword</font></strong>
-
- every time you run a CVS command, follow the <a href="http://sourceforge.net/account/editsshkeys.php">Sourceforge
-
- directions for using authorized keys</a>. This step is optional, but it can
-
- make your CVS experience a lot nicer.</p>
-
- <p>With that done, you should have all the permissions you need, so you just
-
- need to set up your machine and download the current sources so you can start
-
- working on them. Below are instructions for Unix and Windows systems.</p>
-
- <h3>1. Using CVS on Unix</h3>
-
- <blockquote>
-
- <p>Sourceforge CVS uses ssh as a transport layer for security, so you will
-
- have to set this CVS_RSH environment variable in your Unix shell:</p>
-
- <blockquote>
-
- <pre><strong>setenv CVS_RSH ssh</strong> (for csh, tcsh etc)</pre>
-
- <pre><strong>export CVS_RSH=ssh</strong> (for sh, bash etc)</pre>
-
- </blockquote>
-
- <p>It's best to put this in your .bashrc or .cshrc so you don't have to type
-
- it all the time. Then, check out Moodle using this (all one line): </p>
-
- <blockquote>
-
- <pre><strong>cvs -z3 -d:ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle co moodle</strong></pre>
-
- </blockquote>
-
- <p>Don't try to do run this first CVS command into an existing moodle directory
-
- - start fresh with a new directory.</p>
-
- <p>Note that you will be prompted for <strong><font color="#990000">mypassword</font></strong>
-
- for each command unless you set up <a href="http://sourceforge.net/account/editsshkeys.php">authorized
-
- keys</a></p>
-
- <p>Now, you should have a new 'moodle' directory. You can rename it and move
-
- it around if you like. Go into it: </p>
-
- <blockquote>
-
- <pre><strong>cd moodle </strong></pre>
-
- </blockquote>
-
- <p>All the latest Moodle files should be in there. You can now change files
-
- in your copy. To compare your files against the main CVS copy on the server
-
- use cvs diff, eg: </p>
-
- <blockquote>
-
- <pre><strong>cvs diff -c config-dist.php
-
-cvs diff -c lang</strong></pre>
-
- </blockquote>
-
- <p>To fetch the latest updates from the server use: </p>
-
- <blockquote>
-
- <pre><strong>cvs update -dP</strong> </pre>
-
- </blockquote>
-
- <p>To copy your new files back to the server you would do something like:
-
- </p>
-
- <blockquote>
-
- <pre><strong>cd lang/ca
-
-cvs commit</strong> </pre>
-
- </blockquote>
-
- <p>You will be prompted to add some comments (depends on your default text
-
- editor) ... add a meangingful comment and close the editor ... the files
-
- will be sent to Sourceforge and stored. Done! </p>
-
- <p>To save more time you can put default arguments into a file called .cvsrc
-
- in your home directory. For example, mine contains: </p>
-
- <blockquote>
-
- <pre><strong>diff -c
-
-update -dP</strong> </pre>
-
- </blockquote>
-
- <p>Try 'cvs help' for more details ... </p>
-
- <p> </p>
-
- </blockquote>
-
- <h3>2. Using CVS on Windows</h3>
-
- <blockquote>
-
- <p>These instructions are based on notes provided by Mitsuhiro Yoshida <mits@mitstek.com>.</p>
-
- <p>Firstly, download and install WinCVS.</p>
-
- <blockquote>
-
- <p><a href="https://sourceforge.net/project/showfiles.php?group_id=10072">https://sourceforge.net/project/showfiles.php?group_id=10072</a></p>
-
- </blockquote>
-
- <p>Secondly, download sfsetup for SourceForge ssh access, install it and reboot
-
- Windows.</p>
-
- <blockquote>
-
- <p><a href="http://sourceforge.net/projects/sfsetup/">http://sourceforge.net/projects/sfsetup/</a></p>
-
- </blockquote>
-
- <p>Next, configure WinCVS. Launch it, and select Admin -> Preferences.
-
- Then change them as follows:</p>
-
- <blockquote>
-
- <p> [General]<br>
-
- <strong>CVSROOT data</strong>:<br>
-
- <strong>Authentication</strong>: ssh<br>
-
- <strong>Path</strong>: /cvsroot/moodle<br>
-
- <strong>Host address</strong>: cvs.moodle.sourceforge.net<br>
-
- <strong>User name</strong>: <font color="#990000">myusername</font><br>
-
- <strong>CVSROOT</strong>: <font color="#990000">myusername</font>@cvs.moodle.sourceforge.net:/cvsroot/moodle</p>
-
- <p>[Globals]<br>
-
- <strong>Checkout read-only</strong>: uncheck<br>
-
- <strong>Supply control when adding files</strong>: check<br>
-
- <strong>Quiet mode</strong>: uncheck<br>
-
- <strong>TCP/IP compression</strong>: check and select 9<br>
-
- <strong>Dirty files support</strong>: check<br>
-
- <strong>Prune(remove) empty directories</strong>: check<br>
-
- <strong>Disable splash screen</strong>: uncheck</p>
-
- </blockquote>
-
- <p>Congratulations, WinCVS is set up. Now, you should check out a complete
-
- working copy of the Moodle course code:</p>
-
- <ol>
-
- <li>Select 'Create -> checkout'</li>
-
- <li>For the setting 'Module name and path on the server", type "moodle",
-
- then click OK.</li>
-
- <li>Type in <strong><font color="#990000">mypassword</font></strong> and
-
- press Enter in the DOS window.</li>
-
- </ol>
-
- <p>After this first checkout, you can fetch updated files from the CVS server
-
- like this:</p>
-
- <ol>
-
- <li> Select folders or files you want to update</li>
-
- <li>Press right mouse button and select '<strong>Update selection</strong>'</li>
-
- <li>Press OK button</li>
-
- <li>Type in <strong><font color="#990000">mypassword</font></strong> and
-
- press Enter in the DOS window.</li>
-
- </ol>
-
- <p>After modifying files, you can commit them back to the CVS server like
-
- this:</p>
-
- <ol>
-
- <li>Select folders or files you want to commit</li>
-
- <li>Press right button and select '<strong>Commit selection</strong>'</li>
-
- <li>Press OK button</li>
-
- <li>Type in a meaningful comment and press OK button.</li>
-
- <li>Type in <strong><font color="#990000">mypassword</font></strong> and
-
- press Enter in the DOS window.</li>
-
- </ol>
-
- </blockquote>
-
- <p> </p>
-
- <p align="center">Good luck!</p>
-
- <p> </p>
-
-</blockquote>
-
-<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
-
-<p align="CENTER"><font size="1">Version: $Id: features.html,v 1.2 2001/12/09
-
- 10:34:19 martin Exp $</font></p>
-
-</body>
-
-</html>
-
+++ /dev/null
-<head>
-
- <title>Moodle Docs: Developers Manual</title>
-
- <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">
-
-</head>
-
-
-
-<body bgcolor="#FFFFFF">
-
-<h2>Developers Manual</h2>
-
-<p>This document describes some of Moodle's design and how you can contribute.</p>
-
-<p>Sections in this document:</p>
-
-<ol>
-
- <li><a href="#architecture">Moodle architecture</a></li>
-
- <li><a href="#contribute">How you can contribute</a>
-
- <ul>
-
- <li><a href="#activities">Learning activities</a></li>
-
- <li><a href="#themes">Themes</a></li>
-
- <li><a href="#languages">Languages</a></li>
-
- <li><a href="#database">Database Schemas</a></li>
-
- <li><a href="#courseformats">Course formats</a></li>
-
- <li><a href="#doc">Documentation and articles</a></li>
-
- <li><a href="#bugs">Participating in the bug tracker</a></li>
-
- </ul>
-
- </li>
-
-</ol>
-
-<p> </p>
-
-<h3><a name="architecture"></a>1. Moodle architecture</h3>
-
-<p>From a system administrator's perspective, Moodle has been designed according
-
- to the following criteria:</p>
-
-<ol>
-
- <li><strong>Moodle should run on the widest variety of platforms</strong><br>
-
- <br>
-
- The web application platform that runs on most platforms is PHP combined with
-
- MySQL, and this is the environment that Moodle has been developed in (on Linux,
-
- Windows, and Mac OS X). Moodle also uses the ADOdb library for database abstraction,
-
- which means Moodle can use <a href="http://php.weblogs.com/ADOdb_manual#drivers">more
-
- than ten different brands of database</a> (unfortunately, though, it can not
-
- yet <em><strong>set up tables</strong></em> in all these databases - more
-
- on this later). <br><br>
-
- </li>
-
- <li><strong>Moodle should be easy to install, learn and modify</strong><br>
-
- <br>
-
- Early prototypes of Moodle (1999) were built using <a target=_top href="http://www.zope.org/">Zope</a>
-
- - an advanced object-oriented web application server. Unfortunately I found
-
- that although the technology was pretty cool, it had a very steep learning
-
- curve and was not very flexible in terms of system administration. The PHP
-
- scripting language, on the other hand, is very easy to get into (especially
-
- if you've done any programming using any other scripting language). Early
-
- on I made the decision to avoid using a class-oriented design - again, to
-
- keep it simple to understand for novices. Code reuse is instead achieved by
-
- libraries of clearly-named functions and consistent layout of script files.
-
- PHP is also easy to install (binaries are available for every platform) and
-
- is widely available to the point that most web hosting services provide it
-
- as standard.<br><br>
-
- </li>
-
- <li><strong>It should be easy to upgrade from one version to the next</strong><br>
-
- <br>
-
- Moodle knows what version it is (as well as the versions of all plug-in modules)
-
- and a mechanism has been built-in so that Moodle can properly upgrade itself
-
- to new versions (for example it can rename database tables or add new fields).
-
- If using CVS in Unix for example, one can just do a "cvs update -d"
-
- and then visit the site home page to complete an upgrade.<br><br>
-
- </li>
-
- <li><strong>It should be modular to allow for growth</strong><br>
-
- <br>
-
- Moodle has a number of features that are modular, including themes, activities,
-
- interface languages, database schemas and course formats. This allows anyone
-
- to add features to the main codebase or to even distribute them separately.
-
- More on this below in the next section.<br><br>
-
- </li>
-
- <li><strong>It should be able to be used in conjunction with other systems</strong><br>
-
- <br>
-
- One thing Moodle does is keep all files for one course within a single, normal
-
- directory on the server. This would allow a system administrator to provide
-
- seamless forms of file-level access for each teacher, such as Appletalk, SMB,
-
- NFS, FTP, WebDAV and so on. The authentication modules allow Moodle to use
-
- LDAP, IMAP, POP3, NNTP and other databases as sources for user information.
-
- Otherwise, there is work yet to do. Features planned
-
- for Moodle in future versions include: import and export of Moodle data using XML-based
-
- formats (including IMS and SCORM); and increased use of style sheets for
-
- interface formatting (so that it can be integrated visually into other web sites).</li>
-
-</ol>
-
-<p> </p>
-
-<h3><a name="contribute" id="contribute"></a>2. How you can contribute</h3>
-
-<p>As mentioned above, Moodle has a number of features that are modular. Even
-
- if you are not a programmer there are things you can change or help with.</p>
-
-<p><strong><a name="activities" id="activities"></a>Learning Activities</strong></p>
-
-<blockquote>
-
- <p>These are by far the most important modules, and reside in the 'mod' directory.
-
- There are seven default modules: assignment, choice, forum, journal, quiz,
-
- resource, and survey. Each module is in a separate subdirectory and consists
-
- of the following mandatory elements (plus extra scripts unique to each module):</p>
-
- <ul>
-
- <li>mod.html: a form to set up or update an instance of this module</li>
-
- <li>version.php: defines some meta-info and provides upgrading code</li>
-
- <li>icon.gif: a 16x16 icon for the module</li>
-
- <li>db/: SQL dumps of all the required db tables and data (for each database
-
- type) </li>
-
- <li>index.php: a page to list all instances in a course</li>
-
- <li>view.php: a page to view a particular instance</li>
-
- <li>lib.php: any/all functions defined by the module should be in here. If
-
- the modulename if called widget, then the required functions include:
-
- <ul>
-
- <li>widget_add_instance() - code to add a new instance of widget</li>
-
- <li>widget_update_instance() - code to update an existing instance</li>
-
- <li>widget_delete_instance() - code to delete an instance</li>
-
- <li>widget_user_outline() - given an instance, return a summary of a user's
-
- contribution</li>
-
- <li>widget_user_complete() - given an instance, print details of a user's
-
- contribution<br>
-
- </li>
-
- <li>To avoid possible conflict, any module functions should be named starting
-
- with widget_ and any constants you define should start with WIDGET_
-
- </li>
-
- </ul>
-
- </li>
-
- <li>Lastly, each module will have some language files that contain strings
-
- for that module. See below.</li>
-
- </ul>
-
- <p>The easiest way to start a new learning activity module is to use the template
-
- in <strong><a href="http://moodle.com/mod/newmodule_template.zip">mod/newmodule_template.zip</a>.</strong>
-
- Unzip it and follow the README inside. </p>
-
- <p>You might also like to post first in the <a href="http://moodle.com/mod/forum/view.php?id=44" target="_top">Activities
-
- modules forum on Using Moodle</a>.</p>
-
- <p> </p>
-
-</blockquote>
-
-<p> <strong><a name="themes" id="themes"></a>Themes</strong></p>
-
-<blockquote>
-
- <p>Themes (or skins) define the look of a site. A number of simple themes are
-
- provided in the main distribution, but you may want to create your own theme
-
- with your own colours, logo, styles and graphics.
-
-
-
- <p>Each theme is in a subdirectory of the "theme" directory, and contains
-
- at least the following files:</p>
-
- <ul>
-
- <li><strong>config.php</strong>: defines the theme colours used throughout
-
- the site</li>
-
- <li><strong>styles.php</strong>: the style sheet, containing CSS definitions
-
- for standard HTML elements as well as many Moodle elements.</li>
-
- <li><strong>header.html</strong>: Included at the top of each page. This is
-
- what you need to edit to add a logo at the top of pages, for example.</li>
-
- <li><strong>footer.html</strong>: Included at the bottom of each page.</li>
-
- </ul>
-
- <p>To create your own themes for current versions of Moodle:</p>
-
- <ol>
-
- <li>Copy one of the existing theme folders to one with a new name. I recommend
-
- starting with one of the standard themes.
-
- <li>Edit config.php and insert your own colours.
-
- <li>Edit styles.php and change your CSS styles.
-
- <li>Edit header.html and footer.html to add new logos, or change the layout.
-
- </ol>
-
- <p>Note that all these steps are optional - you can make a radically different
-
- look to your site simply by editing the colours in config.php</p>
-
- <p>Note also that Moodle upgrades <em>may</em> break themes slightly, so check the
-
- release notes carefully if you are using a custom theme.</p>
-
- <p>In particular, Moodle 2.0 will have a completely new display system, probably based on
-
- XSL transformations of XML output from Moodle. It is likely that the
-
- themes for this will be a completely different format, but the advantage will
-
- be a much higher possible degree of customisation (including moving elements
-
- around the page).</p>
-
- <p>More discussion about this in the <a target=_top href="http://moodle.com/mod/forum/view.php?id=46">Themes
-
- forum on Using Moodle</a>. If you create a nice theme that you think others
-
- might want to use, please post your zip file on the themes forum!<br>
-
- </p>
-
-</blockquote>
-
-
-
- <p> </p>
-
-
-
-<p><strong><a name="languages" id="languages"></a>Languages</strong></p>
-
-<blockquote>
-
- <p>Moodle has been designed for internationalisation. Each 'string' or 'page'
-
- of text that is displayed as part of the interface is drawn from a set of
-
- language files. Each language is a subdirectory of the directory 'lang'. The
-
- structure of the lang directory is as follows:</p>
-
- <p><strong>lang/en</strong> - directory containing all files for one language
-
- (eg English)</p>
-
- <ul>
-
- <li>moodle.php - strings for main interface</li>
-
- <li>assignment.php - strings for assignment module</li>
-
- <li>choice.php - strings for choice module</li>
-
- <li>forum.php - strings for forum module</li>
-
- <li>journal.php - strings for journal module </li>
-
- <li>quiz.php - strings for quiz module</li>
-
- <li>resource.php - strings for resource module</li>
-
- <li>survey.php - strings for survey module</li>
-
- <li>.... plus other modules if any.<br>
-
- <br>
-
- A string is called from these files using the <strong><em>get_string()</em></strong><em>
-
- </em>or<em> <strong>print_string()</strong> </em>functions. Each string
-
- supports variable substitution, to support variable ordering in different
-
- languages.<em><br>
-
- <br>
-
- </em>eg $strdueby = get_string("assignmentdueby", "assignment",
-
- userdate($date)); <br>
-
- <br>
-
- If a string doesn't exist in a particular language, then the equivalent
-
- in English will automatically be used instead.</li>
-
- </ul>
-
- <p><strong>lang/en/help</strong> - contains whole help pages (for popup context-sensitive
-
- help)</p>
-
- <blockquote>
-
- <p>Main help pages are situated here, while help pages specific to each module
-
- are located in subdirectories with the module's name.</p>
-
- <p>You can insert a helpbutton in a page with the helpbutton function.</p>
-
- <p>eg helpbutton("text", "Click here for help about text");</p>
-
- <p>and for modules:</p>
-
- <p>helpbutton("forumtypes", "Forum types", "forum");</p>
-
- </blockquote>
-
- <p>Note that you can edit languages online, using the administration web tools
-
- under "Check this language". This makes it easy to not to only create
-
- new languages but to refine existing ones. If you are starting a new language,
-
- please contact me, <a target=_top href="http://dougiamas.com/">Martin Dougiamas</a>. </p>
-
- <p>You might also like to post in the <a target=_top href="http://moodle.com/mod/forum/view.php?id=43" target="_top">Languages
-
- forum on Using Moodle</a>. </p>
-
- <p>If you are maintaining a language an ongoing basis, I can give you <a href="?file=cvs.html">CVS
-
- write access to the Moodle source code</a> so that you can directly maintain
-
- the files.</p>
-
-</blockquote>
-
-<p><br>
-
- <strong><a name="database" id="database"></a>Database Schemas</strong></p>
-
-<blockquote>
-
- <p>Given a working database with defined tables, the intentionally simple SQL
-
- used in Moodle should work fine with a wide variety of database brands.</p>
-
-
-
- <p>A problem exists with <strong>automatically creating</strong> new tables
-
- in a database, which is what Moodle tries to do upon initial installation.
-
- Because every database is very different, there doesn't yet exist any way
-
- to do this in a platform-independent way. To support this automation in each
-
- database, schemas can be created that list the required SQL to create Moodle
-
- tables in a particular database. These are files in <strong>lib/db</strong>
-
- and inside the <strong>db</strong> subdirectory of each module.</p>
-
-
-
- <p>Currently, only MySQL and PostgreSQL are fully supported in this way. If you are
-
- familiar with another database (especially open source databases) and are
-
- willing to help port the existing schema, please get in contact with me (<a target=_top href="http://dougiamas.com/">Martin
-
- Dougiamas</a>).</p>
-
-</blockquote>
-
-<p> </p>
-
-<p><strong><a name="courseformats" id="courseformats"></a>Course Formats</strong></p>
-
-<blockquote>
-
- <p>Moodle currently supports three different course formats: weekly, topics and social.
-
- </p>
-
- <p>These are a little more connected to the rest of the code (and hence, less
-
- "pluggable") but it is still quite easy to add new ones.</p>
-
- <p>If you have any ideas for different formats that you need or would like to
-
- see, get in touch with me and I'll do my absolute best to have them available
-
- in future releases.</p>
-
-</blockquote>
-
-<p> </p>
-
-<p><strong><a name="doc" id="doc"></a>Documentation and articles</strong></p>
-
-<blockquote>
-
- <p>If you feel like writing a tutorial, an article, an academic paper or anything
-
- else about Moodle, please do! </p>
-
- <p>Put it on the web and make sure you include links to <a target=_top href="http://moodle.com/">http://moodle.com/</a></p>
-
- </blockquote>
-
-<p> </p>
-
-<p><strong><a name="bugs" id="bugs"></a>Participating in the bug tracker</strong></p>
-
-<blockquote>
-
- <p>Finally, I would like to invite you to register on the "bug tracker"
-
- at <a target=_top href="http://bugs.moodle.org">bugs.moodle.org</a> so you can file any
-
- bugs that you find and perhaps participate in discussing and fixing them.
-
- </p>
-
- <p>"Bugs" not only includes software bugs with current versions of
-
- Moodle, but also new ideas, feature requests and even constructive criticism
-
- of existing features. The beauty of open source is that anyone can participate
-
- in some way and help to create a better product for all of us to enjoy. In
-
- this project, your input is very welcome!</p>
-
-</blockquote>
-
-<p> </p>
-
-<blockquote>
-
- <blockquote>
-
- <blockquote>
-
- <p align="center">Thanks for using Moodle!</p>
-
- <p align="center">Cheers,<br>
-
- <a target=_top href="http://dougiamas.com/" target="_top">Martin Dougiamas</a></p>
-
- </blockquote>
-
- </blockquote>
-
-</blockquote>
-
-<p> </p>
-
-<p> </p>
-
-<blockquote>
-
- <p> </p>
-
-</blockquote>
-
-<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
-
-<p align="CENTER"><font size="1">Version: $Id: developer.html,v 1.2 2001/12/09
-
- 10:34:19 martin Exp $</font></p>
-
-
-
-</body>
-
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<HTML>
-
-<HEAD>
-
- <TITLE>Moodle Docs: Background</TITLE>
-
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
-
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-
-
-
-<H2>Features</H2>
-
-<p>Moodle is an active and evolving product. This page lists some of the many
-
- features it contains:</p>
-
-<p><strong>Overall design</strong></p>
-
-<UL>
-
- <LI>Promotes a social constructionist pedagogy (collaboration, activities, critical
-
- reflection, etc)</LI>
-
- <LI>Suitable for 100% online classes as well as supplementing face-to-face learning
-
- <LI>Simple, lightweight, efficient, compatible, low-tech browser interface</LI>
-
- <LI>Easy to install on almost any platform that supports PHP. Requires only
-
- one database.</LI>
-
- <LI>Full database abstraction supports all major brands of database (except
-
- for initial table definition)</LI>
-
- <LI>Course listing shows descriptions for every course on the server, including
-
- accessibility to guests.</LI>
-
- <LI>Emphasis on strong security throughout. Forms are all checked, data validated,
-
- cookies encrypted etc</LI>
-
-</UL>
-
-<p><strong>Site management</strong></p>
-
-<UL>
-
- <LI>Site is managed by an admin user, defined during setup</LI>
-
- <LI>Plug-in "themes" allow the admin to customise the site colours, fonts, layout
-
- etc to suit local needs</LI>
-
- <LI>Plug-in activity modules can be added to existing Moodle installations</LI>
-
- <LI>Plug-in language packs allow full localisation to any language. These can
-
- be edited using a built-in web-based editor. Currently there are language packs
-
- for more than <A HREF="http://moodle.com/download/lang/" TARGET="_top">19 languages</A>.</LI>
-
- <LI>The code is clearly-written PHP under a GPL license - easy to modify to
-
- suit your needs</LI>
-
-</UL>
-
-<p><strong>User management</strong></p>
-
-<UL>
-
- <LI>Goals are to reduce admin involvement to a minimum, while retaining high
-
- security</LI>
-
- <LI>Supports a range of authentication mechanisms through plug-in authentication
-
- modules, allowing easy integration with existing systems.</LI>
-
- <LI>Standard email method: students can create their own login accounts. Email
-
- addresses are verified by confirmation.</LI>
-
- <LI>LDAP method: account logins can be checked against an LDAP server. Admin
-
- can specify which fields to use.</LI>
-
- <LI>IMAP, POP3, NNTP: account logins are checked against a mail or news server.
-
- SSL, certificates and TLS are supported.</LI>
-
- <LI>External database: any database containing at least two fields can be used
-
- as an external authentication source.</LI>
-
- <LI>Each person requires only one account for the whole server - each account
-
- can have different access</LI>
-
- <LI>An admin account controls the creation of courses and creates teachers by
-
- assigning users to courses</LI>
-
- <LI>Security - teachers can add an "enrolment key" to their courses to keep
-
- out non-students. They can give out this key face-to-face or via personal
-
- email etc</LI>
-
- <LI>Teachers can unenrol students manually if desired, otherwise they are automatically
-
- unenrolled after a certain period of inactivity (set by the admin)</LI>
-
- <LI>Students are encouraged to build an online profile including photos, description.
-
- Email addresses can be protected from display if required.</LI>
-
- <LI>Every user can specify their own timezone, and every date in Moodle is translated
-
- to that timezone (eg posting dates, assignment due dates etc)</LI>
-
- <LI>Every user can choose the language used for the Moodle interface (English,
-
- French, German, Spanish, Portuguese etc)</LI>
-
-</UL>
-
-<p><strong>Course management</strong></p>
-
-<UL>
-
- <LI>Teacher has full control over all settings for a course</LI>
-
- <LI>Choice of course formats such as by week, by topic or a discussion-focussed
-
- social format</LI>
-
- <LI>Flexible array of course activities - Forums, Journals, Quizzes, Resources,
-
- Choices, Surveys, Assignments.</LI>
-
- <LI>Recent changes to the course since the last login can be displayed on the
-
- course home page - helps give sense of community</LI>
-
- <LI>Most text entry areas (resources, forum postings, journal entries etc) can
-
- be edited using an embedded WYSIWYG HTML editor</LI>
-
- <LI>All grades for Forums, Journals, Quizzes and Assignments can be viewed on
-
- one page (and downloaded as a spreadsheet file)</LI>
-
- <LI>Full user logging and tracking - activity reports for each student are available
-
- with graphs and details about each module (last access, number of times read)
-
- as well as a detailed "story" of each students involvement including postings,
-
- journal entries etc on one page.</LI>
-
- <LI>Mail integration - copies of forum posts, teacher feedback etc can be mailed
-
- in HTML or plain text.</LI>
-
-</UL>
-
-<B>Assignment Module</B>
-
-<UL>
-
- <LI>Assignments can be specified with a due date and a maximum grade.</LI>
-
- <LI>Students can upload their assignments (any file format) to the server -
-
- they are date-stamped.</LI>
-
- <LI>Late assignments are allowed, but the amount of lateness is shown clearly
-
- to the teacher</LI>
-
- <LI>For each particular assignment, the whole class can be assessed (grade and
-
- comment) on one page in one form.</LI>
-
- <LI>Teacher feedback is appended to the assignment page for each student, and
-
- notification is mailed out.</LI>
-
- <LI>The teacher can choose to allow resubmission of assignments after grading
-
- (for regrading)</LI>
-
-</UL>
-
-<P><B>Choice Module</B> </P>
-
-<UL>
-
- <LI>Like a poll. Can either be used to vote on something, or to get feedback
-
- from every student (eg research consent)</LI>
-
- <LI>Teacher sees intuitive table view of who chose what</LI>
-
-</UL>
-
-<P><B>Forum Module</B> </P>
-
-<UL>
-
- <LI>Different types of forums are available, such as teacher-only, course news,
-
- open-to-all, and one-thread-per-user.</LI>
-
- <LI>All postings have the authors photo attached.</LI>
-
- <LI>Discussions can be viewed nested, flat or threaded, oldest or newest first.</LI>
-
- <LI>Individual forums can be subscribed to by each person so that copies are
-
- forwarded via email, or the teacher can force subscription for all</LI>
-
- <LI>The teacher can choose not to allow replies (eg for an announcements-only
-
- forum)</LI>
-
-</UL>
-
-<B>Journal Module</B>
-
-<UL>
-
- <LI>Journals are private between student and teacher.</LI>
-
- <LI>Each journal entry can be directed by an open question.</LI>
-
- <LI>For each particular journal entry, the whole class can be assessed on one
-
- page in one form</LI>
-
- <LI>Teacher feedback is appended to the journal entry page, and notification
-
- is mailed out.</LI>
-
-</UL>
-
-<P><B>Quiz Module</B> </P>
-
-<UL>
-
- <LI>Teachers can define a database of questions for re-use in different quizzes</LI>
-
- <LI>Quizzes are automatically graded, and can be re-graded if questions are
-
- modified </LI>
-
- <LI>Quizzes can have a limited time window outside of which they are not available</LI>
-
- <LI>At the teacher's option, quizzes can be attempted multiple times, and can
-
- show feedback and/or correct answers</LI>
-
- <LI>Questions allow HTML and images</LI>
-
- <LI>Multiple-choice questions supporting single or multiple answers</LI>
-
- <LI>Short Answer questions (words or phrases)</LI>
-
- <LI>True-False questions </LI>
-
-</UL>
-
-<P><B>Resource Module</B> </P>
-
-<UL>
-
- <LI>Supports display of any electronic content</LI>
-
- <LI>Files can be uploaded and managed on the server, or created on the fly using
-
- web forms (text or HTML)</LI>
-
- <LI>External content on the web can be linked to or seamlessly included within
-
- the course interface.</LI>
-
-</UL>
-
-<B>Survey Module</B>
-
-<UL><LI>Built-in surveys (COLLES, ATTLS) have been proven as instruments for analysing online classes</LI><LI>Online survey reports always available, including many graphs. Data is downloadable as an Excel spreadsheet or CSV text file.</LI><LI>Survey interface prevents partly-finished surveys.</LI><LI>Feedback is provided to the student of their results compared to the class averages</UL>
-
-
-
-<P> </P>
-
-
-
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
-
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id: features.html,v 1.2 2001/12/09
-
- 10:34:19 martin Exp $</FONT></P>
-
-
-
-</BODY>
-
-</HTML>
-
+++ /dev/null
-<HEAD>
-
- <TITLE>Moodle Docs: Future</TITLE>
-
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
-
-</HEAD>
-
-
-
-<BODY BGCOLOR="#FFFFFF">
-
-
-
-<H2>Future</H2>
-
-<P>I'm committed to continuing my work on Moodle and on keeping it Open and Free.
-
- I have a deeply-held belief in the importance of unrestricted education and
-
- empowered teaching, and Moodle is the main way I can contribute to the realisation
-
- of these ideals.
-
-
-
-<P>As Moodle gains in maturity, I hope its directions are influenced by the community
-
- of developers and users. A dynamic database of proposed features and their status
-
- can be found at <A TARGET=_top HREF="http://bugs.moodle.org/">bugs.moodle.org</A>.
-
- Your <A href="developer.html">contributions</a> in the form of ideas, code,
-
- feedback and promotion are all very welcome.
-
-
-
-<P>Until about April 2003, my own involvement will slow down while I finish my PhD thesis.
-
- During this time there will still be releases, but they will only contain minor
-
- new features and bug fixes. I will also be including modules and other code contributed
-
- by others.
-
-
-
-<P>After this time, by around June/July 2003, I am expecting a major release called Moodle 2.0
-
- that will include major new features such as:
-
- <UL>
-
- <LI>Stronger pedagogical support for both teachers and students
-
- <LI>Support for groups and group work
-
- <LI>Rewritten display incorporating XML, XSL and CSS for full flexibility
-
- and compatibility with all modern web standards.
-
- <LI>Basic support for IMS and SCORM
-
- <LI>A variety of new modules (chat, tracker etc)
-
- <LI>Whatever else seems most important at the time :-)
-
- </UL>
-
-
-
-<P>About this time I will also be experimenting with ways of making
-
- Moodle development more sustainable for the long term. This may
-
- include offering services for payment - although the software itself
-
- will always remain Free.
-
-
-
-<P ALIGN="CENTER"> </P>
-
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
-
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
-
-</BODY>
-
+++ /dev/null
-<HEAD>
-
- <TITLE>Moodle Docs: Installation</TITLE>
-
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
-
-</HEAD>
-
-
-
-<BODY BGCOLOR="#FFFFFF">
-
-<H2>Installing Moodle</H2>
-
-<P>This guide explains how to install Moodle for the first time. It goes into some detail
-
- about some of the steps, in order to cover the wide variety of small differences between
-
- web server setups, so this document may look long and complicated. Don't be put off by this
-
- - I usually set Moodle up in a few minutes!</P>
-
-<P>Take your time and work through this document carefully - it will save you time later on.</P>
-
-<P>Sections in this document:</P>
-
-<OL>
-
- <LI><A HREF="#requirements">Requirements</A></LI>
-
- <LI><A HREF="#downloading">Download</A></LI>
-
- <LI><A HREF="#site">Site structure</A></LI>
-
- <LI><A HREF="#data">Create a data directory</A></LI>
-
- <LI><A HREF="#database">Create a database</A></LI>
-
- <LI><A HREF="#webserver">Check web server settings</A></LI>
-
- <LI><A HREF="#config">Edit config.php</A></LI>
-
- <LI><A HREF="#admin">Go to the admin page</A></LI>
-
- <LI><A HREF="#cron">Set up cron</A></LI>
-
- <LI><A HREF="#course">Create a new course</A></LI>
-
-</OL>
-
-<H3><A NAME="requirements"></A>1. Requirements</H3>
-
-<blockquote>
-
- <p>Moodle is primarily developed in Linux using PHP, Apache and MySQL, and regularly
-
- tested with PostgreSQL and in Windows XP and Mac OS X environments.</p>
-
- <p>All you should need are:</p>
-
- <ol>
-
- <li>a working installation of <A HREF="http://www.php.net/">PHP</A> (version
-
- 4.1.0 or later), with the following features enabled (most PHP installations
-
- these days will have all of these):
-
- <ul>
-
- <LI>JPEG and/or PNG image editing support via the <A HREF="http://www.boutell.com/gd/">GD library</A></li>
-
- <LI>Sessions support</LI>
-
- <LI>File uploading allowed</LI>
-
- </UL>
-
-</LI>
-
- <li>a working database server: <A HREF="http://www.mysql.com/">MySQL</A> or <A HREF="http://www.postgresql.org/">PostgreSQL</A> are recommended. (MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 or ODBC are also theoretically supported but will require you to manually set up the database tables).</li>
-
- </ol>
-
- <p>On a Windows platform, the quickest way to satisfy these requirements is
-
- to download <A HREF="http://www.foxserv.net/">FoxServ</A>,
-
- or <A HREF="http://www.easyphp.org/">EasyPHP</A> which will install Apache,
-
- PHP, and MySQL for you. Make sure you enable the GD module so Moodle can process
-
- images - you may have to edit php.ini and remove the comment (;) from this
-
- line: 'extension=php_gd.dll'.</p>
-
-
-
- <p>On Mac OS X I highly recommend the <a href="http://fink.sourceforge.net/">fink</a>
-
- project as a way to download easily-maintainable packages for all of this.</p>
-
-
-
- <p>If you're on Linux or another Unix then I'll assume you can figure all this out for yourself! ;-) </p>
-
-
-
-</blockquote>
-
-<P> </P>
-
-<H3><A NAME="downloading"></A>2. Download</H3>
-
-<blockquote>
-
- <p>There are two ways to get Moodle, as a compressed package and via CVS. These
-
- are explained in detail on the download page on <A HREF="http://moodle.com/">http://moodle.com/</A></p>
-
- <p>After downloading and unpacking the archive, or checking out the files via
-
- CVS, you will be left with a directory called "moodle", containing
-
- a number of files and folders. </p>
-
- <p>You can either place the whole folder in your web server documents directory,
-
- in which case the site will be located at <B>http://yourwebserver.com/moodle</B>,
-
- or you can copy all the contents straight into the main web server documents
-
- directory, in which case the site will be simply <B>http://yourwebserver.com</B>.</p>
-
-</blockquote>
-
-<P> </P>
-
-<H3><A NAME="site"></A>3. Site structure</H3>
-
-<BLOCKQUOTE>
-
- <p>Here is a quick summary of the contents of the Moodle folder, to help get
-
- you oriented:</p>
-
- <blockquote>
-
- <p>config.php - the only file you need to edit to get started<br>
-
- version.php - defines the current version of Moodle code<BR>
-
- index.php - the front page of the site</p>
-
- <ul>
-
- <li>admin/ - code to administrate the whole server </li>
-
- <li>auth/ - plugin modules to authenticate users </li>
-
- <li>course/ - code to display and manage courses </li>
-
- <li>doc/ - help documentation for Moodle (eg this page)</li>
-
- <li>files/ - code to display and manage uploaded files</li>
-
- <li>lang/ - texts in different languages, one directory per language </li>
-
- <li>lib/ - libraries of core Moodle code </li>
-
- <li>login/ - code to handle login and account creation </li>
-
- <li>mod/ - all Moodle course modules</li>
-
- <li>pix/ - generic site graphics</li>
-
- <li>theme/ - theme packs/skins to change the look of the site.</li>
-
- <li>user/ - code to display and manage users</li>
-
- </ul>
-
- <p> </p>
-
- </blockquote>
-
-</BLOCKQUOTE>
-
-<H3><A NAME="data"></A>4. Create a data directory</H3>
-
-<blockquote>
-
- <p>Moodle will also need some space on your hard disk to store uploaded files,
-
- such as course documents and user pictures.</p>
-
-
-
- <p>Create a directory for this purpose somewhere. For security, it's best that
-
- this directory is NOT accessible directly via the web. The easiest way to do this
-
- is to simply locate it OUTSIDE the web directory, otherwise protect it
-
- by creating a file in the data directory called .htaccess, containing this line:
-
- <blockquote>
-
- <PRE>deny from all</PRE>
-
- </blockquote>
-
-
-
- <p>To make sure that Moodle can save uploaded files in this directory, check that
-
- the web server software (eg Apache) has permission to write
-
- to this directory. On Unix machines, this means setting the owner of the directory
-
- to be something like "nobody" or "apache".</p>
-
-
-
- <p>On many shared hosting servers, you will probably need to restrict all file access
-
- to your "group" (to prevent other webhost customers from looking at or changing your files),
-
- but provide full read/write access to everyone else (which will allow the web server
-
- to access your files). Speak to your server administrator if you are having
-
- trouble setting this up securely.</p>
-
-
-
-</blockquote>
-
-<P> </P>
-
-<H3><A NAME="database"></A>5. Create a database</H3>
-
-<blockquote>
-
-<p>You need to create an empty database (eg "moodle") in your database system
-
- along with a special user (eg "moodleuser") that has access to that database
-
- (and that database only). You could use the "root" user if you wanted to, but
-
- this is not recommended for a production system: if hackers manage to discover
-
- the password then your whole database system would be at risk, rather than
-
- just one database.
-
-</p>
-
- <p>Example command lines for MySQL: </p>
-
- <PRE>
-
- # mysql -u root -p
-
- > CREATE DATABASE moodle;
-
- > GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,INDEX,ALTER ON moodle.*
-
- TO moodleuser@localhost IDENTIFIED BY 'yourpassword';
-
- > quit
-
- # mysqladmin -p reload
-
-</PRE>
-
- <p>Example command lines for PostgreSQL: </p>
-
- <PRE>
-
- # su - postgres
-
- > psql -c "create user moodleuser createdb;" template1
-
- > psql -c "create database moodle;" -U moodleuser template1
-
- > psql -c "alter user moodleuser nocreatedb;" template1
-
-</PRE>
-
- <p>(For MySQL I highly recommend the use of <a href="http://phpmyadmin.sourceforge.net/">phpMyAdmin</a>
-
- to manage your databases).</p>
-
-<p>As of version 1.0.8, Moodle now supports table prefixes, and so can safely share
-
- a database with tables from other applications.</p>
-
-</blockquote>
-
-<P> </P>
-
-<H3><A NAME="webserver" id="webserver"></A>6. Check your web server settings</H3>
-
-<blockquote>
-
- <p>Firstly, make sure that your web server is set up to use index.php as a default
-
- page (perhaps in addition to index.html, default.htm and so on).</p>
-
- <p>In Apache, this is done using a DirectoryIndex parameter in your httpd.conf
-
- file. Mine usually looks like this:</p>
-
- <blockquote>
-
- <pre><strong>DirectoryIndex</strong> index.php index.html index.htm </pre>
-
- </blockquote>
-
- <p>Just make sure index.php is in the list (and preferably towards the start
-
- of the list, for efficiency).</p>
-
- <p>Secondly, Moodle requires a number of PHP settings to be active for it to
-
- work. <B>On most servers these will already be the default settings.</B>
-
- However, some PHP servers (and some of the more recent PHP versions) may
-
- have things set differently. These are defined in PHP's configuration
-
- file (usually called php.ini):</p>
-
- <blockquote>
-
-<pre>file_uploads = 1
-
-magic_quotes_gpc = 1
-
-short_open_tag = 1
-
-session.auto_start = 0
-
-</pre>
-
- </blockquote>
-
- <p>If you don't have access to httpd.conf or php.ini on your server, or you
-
- have Moodle on a server with other applications that require different
-
- settings, then you can OVERRIDE all of the default settings.
-
-
-
- <p>To do this, you need to create a file called <B>.htaccess</B> in Moodle's
-
- main directory that contains definitions for these settings.
-
- This only works on Apache servers and only when Overrides have been allowed.
-
- <BLOCKQUOTE><PRE>
-
-DirectoryIndex index.php index.html index.htm
-
-php_value magic_quotes_gpc 1
-
-php_value file_uploads 1
-
-php_value short_open_tag 1
-
-php_value session.auto_start 0</BLOCKQUOTE></PRE>
-
- <P>You can also do things like define the maximum size for uploaded files:
-
- <BLOCKQUOTE><PRE>
-
-php_value upload_max_filesize 2M
-
-php_value post_max_size 2M
-
- </BLOCKQUOTE></PRE>
-
-
-
- <p>The easiest thing to do is just copy the sample file from lib/htaccess
-
- and edit it to suit your needs. It contains further instructions. For
-
- example, in a Unix shell:
-
- <blockquote>
-
- <pre>cp lib/htaccess .htaccess</pre>
-
- </blockquote>
-
-
-
-</blockquote>
-
-<p> </p>
-
-<H3><A NAME="config"></A>7. Edit config.php</H3>
-
-<blockquote>
-
- <p>Now you can edit the configuration file, <strong>config.php</strong>, using a
-
- text editor. This file is used by all other files in Moodle.</p>
-
- <p>To start with, make a copy of config-dist.php and call it config.php. We
-
- do this so that your config.php won't be overwritten in case you upgrade Moodle
-
- later on. </p>
-
- <p>Edit config.php to specify the database details that you just defined (including
-
- a table prefix - notice this is REQUIRED for PostgreSQL), as
-
- well as the site address, file system directory and data directory.
-
- The config file has detailed directions.</p>
-
- <p>For the rest of this installation document we will assume your site is at:
-
- <u>http://example.com/moodle</u></p>
-
-</blockquote>
-
-<P> </P>
-
-<H3><A NAME="admin"></A>8. Go to the admin page</H3>
-
-<blockquote>
-
- <p>The admin page should now be working at: <u>http://example.com/moodle/admin</u>.
-
- If you try and access the front page of your site you'll be taken there automatically
-
- anyway. The first time you access this admin page, you will be presented with
-
- a GPL agreement with which you need to agree before you can continue with the setup.</p>
-
- <P>(Moodle will also try to set some cookies in your browser. If you have
-
- your browser set up to let you choose to accept cookies, then you <B>must</B>
-
- accept the Moodle cookies, or Moodle won't work properly.)
-
- <p>Now Moodle will start setting up your database and creating tables to store data.
-
- Firstly, the main database tables are created. You should see a number of SQL statements followed by
-
- status messages (in green or red) that look like this:</p>
-
- <blockquote>
-
- <p>CREATE TABLE course ( id int(10) unsigned NOT NULL auto_increment, category
-
- int(10) unsigned NOT NULL default '0', password varchar(50) NOT NULL default
-
- '', fullname varchar(254) NOT NULL default '', shortname varchar(15) NOT
-
- NULL default '', summary text NOT NULL, format tinyint(4) NOT NULL default
-
- '1', teacher varchar(100) NOT NULL default 'Teacher', startdate int(10)
-
- unsigned NOT NULL default '0', enddate int(10) unsigned NOT NULL default
-
- '0', timemodified int(10) unsigned NOT NULL default '0', PRIMARY KEY (id))
-
- TYPE=MyISAM</p>
-
- <p><FONT COLOR="#006600">SUCCESS</FONT></p>
-
- <p>...and so on, followed by: <FONT COLOR="#FF0000">Main databases set up
-
- successfully</FONT>. </p>
-
- </blockquote>
-
- <p>If you don't see these, then there must have been some problem with the database
-
- or the configuration settings you defined in config.php. Check that PHP isn't
-
- in a restricted "safe mode" (commercial web hosts often have safe mode turned
-
- on). You can check PHP variables by creating a little file containing <?
-
- phpinfo() ?> and looking at it through a browser. Check all these and try
-
- this page again.</p>
-
- <p>Scroll down the very bottom of the page and press the "Continue"
-
- link.</p>
-
- <p>Next you will see a similar page that sets up all the tables required by
-
- each Moodle module. As before, they should all be green.</p>
-
-
-
- <p>Scroll down the very bottom of the page and press the "Continue"
-
- link.</p>
-
-
-
- <p>You should now see a form where you can define more configuration variables
-
- for your installation, such as the default language, SMTP hosts and so on.
-
- Don't worry too much about getting everything right just now - you can always
-
- come back and edit these later on using the admin interface. Scroll down
-
- to the bottom and click "Save changes".</p>
-
-
-
- <p>If (and only if) you find yourself getting stuck on this page or the next
-
- page, unable to continue, then your server probably has what I call the
-
- "buggy referrer" problem. This is easy to fix: just edit
-
- your config.php and set the variable buggy_referrer to <i>true</i>, then
-
- try the page again.</p>
-
-
-
- <p>The next page is a form where you can define parameters for your Moodle site and the
-
- front page, such as the name, format, description and so on.
-
-
-
- Fill this out (you can always go back and change these later) and then press
-
- "Save changes".</p>
-
-
-
- <p>Finally, you will then be asked to create a top-level administration user
-
- for future access to the admin pages. Fill out the details with your own name,
-
- email etc and then click "Save changes". Not all the fields are
-
- required, but if you miss any important fields you'll be re-prompted for them.
-
- </p>
-
- <blockquote>
-
- <blockquote>
-
- <blockquote>
-
- <blockquote>
-
- <blockquote>
-
- <p><strong>Make sure you remember the username and password you chose
-
- for the administration user account, as they will be necessary to
-
- access the administration page in future.</strong></p>
-
- </blockquote>
-
- </blockquote>
-
- </blockquote>
-
- </blockquote>
-
- </blockquote>
-
- <p>Once successful, you will be returned to the main admin page, which contain
-
- a number of links arranged in a menu (these items also appear on the home
-
- page when you are logged in as the admin user). All your further administration
-
- of Moodle can now be done using this menu, such as:</p>
-
- <ul>
-
- <li>creating and deleting courses</li>
-
- <li>creating and editing user accounts</li>
-
- <li>administering teacher accounts</li>
-
- <li>changing site-wide settings like themes etc</li>
-
- </ul>
-
-</blockquote>
-
-<P> </P>
-
-<H3><A NAME="cron"></A>9. Set up cron</H3>
-
-<blockquote>
-
- <p>Some of Moodle's modules require continual checks to perform tasks. For example,
-
- Moodle needs to check the discussion forums so it can mail out copies of posts
-
- to people who have subscribed.</p>
-
- <p>The script that does all this is located in the admin directory, and is called
-
- cron.php. However, it can not run itself, so you need to set up a mechanism
-
- where this script is run regularly (eg every five minutes). This provides
-
- a "heartbeat" so that the script can perform functions at periods
-
- defined by each module.</p>
-
- <P>Note that the machine performing the cron <B>does not need to be the same
-
- machine that is running Moodle</B>. For example, if you have a limited web hosting
-
- service that does not have cron, then you can might choose to run cron on another
-
- server or on your home computer. All that matters is that the cron.php file is
-
- called every five minutes or so.</p>
-
- <p>First, test that the script works by running it directly from your browser:</p>
-
- <blockquote>
-
- <PRE>http://example.com/moodle/admin/cron.php</PRE>
-
- </blockquote>
-
- <p>Now, you need to set up some of way of running the script automatically and
-
- regularly. </p>
-
- <H4> Running the script from a command line</H4>
-
- <p>You can call the page from the command line just as you did in the example
-
- above. For example, you can use a Unix utility like 'wget':</p>
-
- <blockquote>
-
- <PRE>wget -q -O /dev/null http://example.com/moodle/admin/cron.php</PRE>
-
- </blockquote>
-
- <p>Note in this example that the output is thrown away (to /dev/null).</p>
-
- <p>The same thing using lynx:</p>
-
- <blockquote>
-
- <pre>lynx -dump http://example.com/moodle/admin/cron.php > /dev/null</pre>
-
- </blockquote>
-
- <p>Alternatively you could use a standalone version of PHP, compiled to be run
-
- on the command line. The advantage with doing this is that your web server
-
- logs aren't filled with constant requests to cron.php. The disadvantage is
-
- that you need to have access to a command-line version of php.</p>
-
- <blockquote>
-
- <PRE>/opt/bin/php /web/moodle/admin/cron.php
-
-
-
-
-
-(Windows) C:\apache\php\php.exe C:\apache\htdocs\moodle\admin\cron.php
-
-
-
-</PRE>
-
- </blockquote>
-
- <h4>Automatically running the script every 5 minutes</h4>
-
- <p>On Unix systems: Use <B>cron</B>. Edit your cron settings from the commandline
-
- using "crontab -e" and add a line like:</p>
-
- <blockquote>
-
- <PRE>*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php</PRE>
-
- </blockquote>
-
- <p>On Windows systems: The simplest way is to use my package <A TITLE="Click to download this package (150k)" HREF="http://moodle.com/download/moodle-cron-for-windows.zip">moodle-cron-for-windows.zip</A>
-
- which makes this whole thing very easy. You can also explore using the built-in
-
- Windows feature for "Scheduled Tasks".</p>
-
- </p>
-
-</blockquote>
-
-<H3><A NAME="course"></A>10. Create a new course</H3>
-
-<blockquote>
-
- <p>Now that Moodle is running properly, you can create a course. </p>
-
- <p>Select "Create a new course" from the Admin page (or the admin
-
- links on the home page).</p>
-
- <p>Fill out the form, paying special attention to the course format. You don't
-
- have to worry about the details too much at this stage, as everything can
-
- be changed later by the teacher.</p>
-
- <p>Press "Save changes", and you will be taken to a new form where
-
- you can assign teachers to the course. You can only add existing user accounts
-
- from this form - if you want to create a new teacher account then either ask
-
- the teacher to create one for themselves (see the login page), or create one
-
- for them using the "Add a new user" on the Admin page.</p>
-
- <p>Once done, the course is ready to customise, and is accessible via the "Courses"
-
- link on the home page.</p>
-
- <p>See the "<A HREF="./?file=teacher.html">Teacher Manual</A>" for more details
-
- on course-building.</p>
-
-</blockquote>
-
-<P> </P>
-
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
-
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
-
-
-
-</BODY>
-
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<HTML>
-
-<HEAD>
-
- <TITLE>Moodle Docs: Introduction</TITLE>
-
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
-
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-
-
-
-<H2>Introduction</H2>
-
-
-
-<P>Moodle is a software package for producing internet-based courses and web sites.
-
- It's an ongoing development project designed to support a <A HREF="http://dougiamas.com/writing/herdsa2002/">social constructionist</A> framework of education. </P>
-
-
-
-<P>Moodle is provided freely as <A HREF="http://www.opensource.org/docs/definition_plain.html">
-
- Open Source</A> software (under the <A HREF="http://www.gnu.org/copyleft/gpl.html">
-
- GNU Public License</A>). Basically this means Moodle is copyrighted, but that you have additional
-
- freedoms. You are allowed to copy, use and modify Moodle <B>provided</B> that you agree: to provide
-
- the source to others; to not modify or remove the original license, and apply this same
-
- license to any derivative work.
-
-
-
-<P>Moodle will run on any computer that can run <A HREF="http://www.php.net/">
-
- PHP</A>, and can support many types of database (particularly <a href="http://www.mysql.com/">MySQL</a>).</P>
-
-
-
-<P>The word Moodle is an acronym for Modular Object-Oriented Dynamic Learning
-
- Environment, which is mostly useful to programmers and education theorists.
-
- It's also a verb that describes the process of lazily meandering through
-
- something, doing things as it occurs to you to do them, an enjoyable tinkering
-
- that often leads to insight and creativity. As such it applies both to the way
-
- Moodle was developed, and to the way a student or teacher might approach studying
-
- or teaching an online course.</P>
-
-<P><BR>
-
-</P>
-
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
-
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
-
-
-
-</BODY>
-
-</HTML>
-
+++ /dev/null
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<HTML>
-
-<HEAD>
-
- <TITLE>Moodle Docs: Copyright License</TITLE>
-
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
-
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-
-
-
-<H2>Copyright License for Moodle</H2>
-
-
-
-<P>Moodle is Copyright © 2001-2002, <A HREF="http://dougiamas.com/">Martin
-
- Dougiamas</A>.</P>
-
-<P>This program is free software; you can redistribute it and/or modify<BR>
-
- it under the terms of the GNU General Public License as published by<BR>
-
- the Free Software Foundation; either version 2 of the License, or<BR>
-
- (at your option) any later version.</P>
-
-<P>This program is distributed in the hope that it will be useful,<BR>
-
- but WITHOUT ANY WARRANTY; without even the implied warranty of<BR>
-
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<BR>
-
- GNU General Public License for more details (attached below).<BR>
-
-</P>
-
-<HR WIDTH="100%" SIZE="2"><BR>
-
-
-
-<PRE> GNU GENERAL PUBLIC LICENSE<BR> Version 2, June 1991<BR><BR> Copyright (C) 1989, 1991 Free Software Foundation, Inc.<BR> 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA<BR> Everyone is permitted to copy and distribute verbatim copies<BR> of this license document, but changing it is not allowed.<BR><BR> Preamble<BR><BR> The licenses for most software are designed to take away your<BR>freedom to share and change it. By contrast, the GNU General Public<BR>License is intended to guarantee your freedom to share and change free<BR>software--to make sure the software is free for all its users. This<BR>General Public License applies to most of the Free Software<BR>Foundation's software and to any other program whose authors commit to<BR>using it. (Some other Free Software Foundation software is covered by<BR>the GNU Library General Public License instead.) You can apply it to<BR>your programs, too.<BR><BR> When we speak of free software, we are referring to freedom, not<BR>price. Our General Public Licenses are designed to make sure that you<BR>have the freedom to distribute copies of free software (and charge for<BR>this service if you wish), that you receive source code or can get it<BR>if you want it, that you can change the software or use pieces of it<BR>in new free programs; and that you know you can do these things.<BR><BR> To protect your rights, we need to make restrictions that forbid<BR>anyone to deny you these rights or to ask you to surrender the rights.<BR>These restrictions translate to certain responsibilities for you if you<BR>distribute copies of the software, or if you modify it.<BR><BR> For example, if you distribute copies of such a program, whether<BR>gratis or for a fee, you must give the recipients all the rights that<BR>you have. You must make sure that they, too, receive or can get the<BR>source code. And you must show them these terms so they know their<BR>rights.<BR><BR> We protect your rights with two steps: (1) copyright the software, and<BR>(2) offer you this license which gives you legal permission to copy,<BR>distribute and/or modify the software.<BR><BR> Also, for each author's protection and ours, we want to make certain<BR>that everyone understands that there is no warranty for this free<BR>software. If the software is modified by someone else and passed on, we<BR>want its recipients to know that what they have is not the original, so<BR>that any problems introduced by others will not reflect on the original<BR>authors' reputations.<BR><BR> Finally, any free program is threatened constantly by software<BR>patents. We wish to avoid the danger that redistributors of a free<BR>program will individually obtain patent licenses, in effect making the<BR>program proprietary. To prevent this, we have made it clear that any<BR>patent must be licensed for everyone's free use or not licensed at all.<BR><BR> The precise terms and conditions for copying, distribution and<BR>modification follow.<BR>\f<BR> GNU GENERAL PUBLIC LICENSE<BR> TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION<BR><BR> 0. This License applies to any program or other work which contains<BR>a notice placed by the copyright holder saying it may be distributed<BR>under the terms of this General Public License. The "Program", below,<BR>refers to any such program or work, and a "work based on the Program"<BR>means either the Program or any derivative work under copyright law:<BR>that is to say, a work containing the Program or a portion of it,<BR>either verbatim or with modifications and/or translated into another<BR>language. (Hereinafter, translation is included without limitation in<BR>the term "modification".) Each licensee is addressed as "you".<BR><BR>Activities other than copying, distribution and modification are not<BR>covered by this License; they are outside its scope. The act of<BR>running the Program is not restricted, and the output from the Program<BR>is covered only if its contents constitute a work based on the<BR>Program (independent of having been made by running the Program).<BR>Whether that is true depends on what the Program does.<BR><BR> 1. You may copy and distribute verbatim copies of the Program's<BR>source code as you receive it, in any medium, provided that you<BR>conspicuously and appropriately publish on each copy an appropriate<BR>copyright notice and disclaimer of warranty; keep intact all the<BR>notices that refer to this License and to the absence of any warranty;<BR>and give any other recipients of the Program a copy of this License<BR>along with the Program.<BR><BR>You may charge a fee for the physical act of transferring a copy, and<BR>you may at your option offer warranty protection in exchange for a fee.<BR><BR> 2. You may modify your copy or copies of the Program or any portion<BR>of it, thus forming a work based on the Program, and copy and<BR>distribute such modifications or work under the terms of Section 1<BR>above, provided that you also meet all of these conditions:<BR><BR> a) You must cause the modified files to carry prominent notices<BR> stating that you changed the files and the date of any change.<BR><BR> b) You must cause any work that you distribute or publish, that in<BR> whole or in part contains or is derived from the Program or any<BR> part thereof, to be licensed as a whole at no charge to all third<BR> parties under the terms of this License.<BR><BR> c) If the modified program normally reads commands interactively<BR> when run, you must cause it, when started running for such<BR> interactive use in the most ordinary way, to print or display an<BR> announcement including an appropriate copyright notice and a<BR> notice that there is no warranty (or else, saying that you provide<BR> a warranty) and that users may redistribute the program under<BR> these conditions, and telling the user how to view a copy of this<BR> License. (Exception: if the Program itself is interactive but<BR> does not normally print such an announcement, your work based on<BR> the Program is not required to print an announcement.)<BR>\f<BR>These requirements apply to the modified work as a whole. If<BR>identifiable sections of that work are not derived from the Program,<BR>and can be reasonably considered independent and separate works in<BR>themselves, then this License, and its terms, do not apply to those<BR>sections when you distribute them as separate works. But when you<BR>distribute the same sections as part of a whole which is a work based<BR>on the Program, the distribution of the whole must be on the terms of<BR>this License, whose permissions for other licensees extend to the<BR>entire whole, and thus to each and every part regardless of who wrote it.<BR><BR>Thus, it is not the intent of this section to claim rights or contest<BR>your rights to work written entirely by you; rather, the intent is to<BR>exercise the right to control the distribution of derivative or<BR>collective works based on the Program.<BR><BR>In addition, mere aggregation of another work not based on the Program<BR>with the Program (or with a work based on the Program) on a volume of<BR>a storage or distribution medium does not bring the other work under<BR>the scope of this License.<BR><BR> 3. You may copy and distribute the Program (or a work based on it,<BR>under Section 2) in object code or executable form under the terms of<BR>Sections 1 and 2 above provided that you also do one of the following:<BR><BR> a) Accompany it with the complete corresponding machine-readable<BR> source code, which must be distributed under the terms of Sections<BR> 1 and 2 above on a medium customarily used for software interchange; or,<BR><BR> b) Accompany it with a written offer, valid for at least three<BR> years, to give any third party, for a charge no more than your<BR> cost of physically performing source distribution, a complete<BR> machine-readable copy of the corresponding source code, to be<BR> distributed under the terms of Sections 1 and 2 above on a medium<BR> customarily used for software interchange; or,<BR><BR> c) Accompany it with the information you received as to the offer<BR> to distribute corresponding source code. (This alternative is<BR> allowed only for noncommercial distribution and only if you<BR> received the program in object code or executable form with such<BR> an offer, in accord with Subsection b above.)<BR><BR>The source code for a work means the preferred form of the work for<BR>making modifications to it. For an executable work, complete source<BR>code means all the source code for all modules it contains, plus any<BR>associated interface definition files, plus the scripts used to<BR>control compilation and installation of the executable. However, as a<BR>special exception, the source code distributed need not include<BR>anything that is normally distributed (in either source or binary<BR>form) with the major components (compiler, kernel, and so on) of the<BR>operating system on which the executable runs, unless that component<BR>itself accompanies the executable.<BR><BR>If distribution of executable or object code is made by offering<BR>access to copy from a designated place, then offering equivalent<BR>access to copy the source code from the same place counts as<BR>distribution of the source code, even though third parties are not<BR>compelled to copy the source along with the object code.<BR>\f<BR> 4. You may not copy, modify, sublicense, or distribute the Program<BR>except as expressly provided under this License. Any attempt<BR>otherwise to copy, modify, sublicense or distribute the Program is<BR>void, and will automatically terminate your rights under this License.<BR>However, parties who have received copies, or rights, from you under<BR>this License will not have their licenses terminated so long as such<BR>parties remain in full compliance.<BR><BR> 5. You are not required to accept this License, since you have not<BR>signed it. However, nothing else grants you permission to modify or<BR>distribute the Program or its derivative works. These actions are<BR>prohibited by law if you do not accept this License. Therefore, by<BR>modifying or distributing the Program (or any work based on the<BR>Program), you indicate your acceptance of this License to do so, and<BR>all its terms and conditions for copying, distributing or modifying<BR>the Program or works based on it.<BR><BR> 6. Each time you redistribute the Program (or any work based on the<BR>Program), the recipient automatically receives a license from the<BR>original licensor to copy, distribute or modify the Program subject to<BR>these terms and conditions. You may not impose any further<BR>restrictions on the recipients' exercise of the rights granted herein.<BR>You are not responsible for enforcing compliance by third parties to<BR>this License.<BR><BR> 7. If, as a consequence of a court judgment or allegation of patent<BR>infringement or for any other reason (not limited to patent issues),<BR>conditions are imposed on you (whether by court order, agreement or<BR>otherwise) that contradict the conditions of this License, they do not<BR>excuse you from the conditions of this License. If you cannot<BR>distribute so as to satisfy simultaneously your obligations under this<BR>License and any other pertinent obligations, then as a consequence you<BR>may not distribute the Program at all. For example, if a patent<BR>license would not permit royalty-free redistribution of the Program by<BR>all those who receive copies directly or indirectly through you, then<BR>the only way you could satisfy both it and this License would be to<BR>refrain entirely from distribution of the Program.<BR><BR>If any portion of this section is held invalid or unenforceable under<BR>any particular circumstance, the balance of the section is intended to<BR>apply and the section as a whole is intended to apply in other<BR>circumstances.<BR><BR>It is not the purpose of this section to induce you to infringe any<BR>patents or other property right claims or to contest validity of any<BR>such claims; this section has the sole purpose of protecting the<BR>integrity of the free software distribution system, which is<BR>implemented by public license practices. Many people have made<BR>generous contributions to the wide range of software distributed<BR>through that system in reliance on consistent application of that<BR>system; it is up to the author/donor to decide if he or she is willing<BR>to distribute software through any other system and a licensee cannot<BR>impose that choice.<BR><BR>This section is intended to make thoroughly clear what is believed to<BR>be a consequence of the rest of this License.<BR>\f<BR> 8. If the distribution and/or use of the Program is restricted in<BR>certain countries either by patents or by copyrighted interfaces, the<BR>original copyright holder who places the Program under this License<BR>may add an explicit geographical distribution limitation excluding<BR>those countries, so that distribution is permitted only in or among<BR>countries not thus excluded. In such case, this License incorporates<BR>the limitation as if written in the body of this License.<BR><BR> 9. The Free Software Foundation may publish revised and/or new versions<BR>of the General Public License from time to time. Such new versions will<BR>be similar in spirit to the present version, but may differ in detail to<BR>address new problems or concerns.<BR><BR>Each version is given a distinguishing version number. If the Program<BR>specifies a version number of this License which applies to it and "any<BR>later version", you have the option of following the terms and conditions<BR>either of that version or of any later version published by the Free<BR>Software Foundation. If the Program does not specify a version number of<BR>this License, you may choose any version ever published by the Free Software<BR>Foundation.<BR><BR> 10. If you wish to incorporate parts of the Program into other free<BR>programs whose distribution conditions are different, write to the author<BR>to ask for permission. For software which is copyrighted by the Free<BR>Software Foundation, write to the Free Software Foundation; we sometimes<BR>make exceptions for this. Our decision will be guided by the two goals<BR>of preserving the free status of all derivatives of our free software and<BR>of promoting the sharing and reuse of software generally.<BR><BR> NO WARRANTY<BR><BR> 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY<BR>FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN<BR>OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES<BR>PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED<BR>OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF<BR>MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS<BR>TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE<BR>PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,<BR>REPAIR OR CORRECTION.<BR><BR> 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING<BR>WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR<BR>REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,<BR>INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING<BR>OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED<BR>TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY<BR>YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER<BR>PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE<BR>POSSIBILITY OF SUCH DAMAGES.<BR><BR> END OF TERMS AND CONDITIONS<BR></PRE>
-
-
-
-
-
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
-
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
-
-
-
-</BODY>
-
-</HTML>
\ No newline at end of file
+++ /dev/null
-<HEAD>
- <TITLE>Moodle Docs: Release notes</TITLE>
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
- <style type="text/css">
- DT {font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif; font-weight: bold;}
- DD {margin-bottom:1em;}
- </style>
-</HEAD>
-
-<BODY BGCOLOR="#FFFFFF">
-<H2>Release notes</H2>
-
-<H3> New in Moodle 1.0.8 (6th January, 2003) :</H3>
-<UL><DL>
-<DT> Databases</DT>
-<DD> Moodle now has complete native support support for <B>PostgreSQL 7</B> databases (thanks
- to Mary Hunter for the SQL files and other ideas!).
- Moodle also now supports table prefixes, which means you can install
- Moodle into any database, even if it already contains tables from
- other web applications.
- A number of other changes have also been made to the code structure that will
- make it fairly easy now to add full support for other database types.</DD>
-
-<DT> Languages </DT>
-<DD> <B><U>Six</U> new languages have been added!</B> Chinese (from Zhang Dexuan),
- Arabic (from Ahmed Nabil), Turkish (from M. Cüneyt Birkök), Swedish (from Set Lonnert),
- Thai (from Wim Singhanart) and Dutch (from Hans Zwart and Jacob Romeyn). Many thanks
- to all these hard-working people! Most other languages have also had updates and fixes since 1.0.7.
- The language editor has been improved slightly, making it easier to see
- new strings and empty strings that need translating. The main documentation manual is
- also now able to be localised and will appear in the current language if
- translated versions exist.</DD>
-
-<DT> Layout</DT>
-<DD> A number of small improvements have been made in the layout of many pages (such
- as the forum posting screen) to make them clearer, neater and smaller. Almost all text entry screens
- now have specific help items alongside them (depending on the pedagogical
- focus). The forums now have a quick search form available on every page.</DD>
-
-<DT> Themes </DT>
-<DD> Theme support of CSS has been extended to give theme makers more control
- over more of the Moodle web site. A variety of new themes has been added
- to the distribution.</DD>
-
-<DT> Resources</DT>
-<DD> A new type of resource has been added, called "Program", which allows
- Moodle to cooperate with external web applications by passing information
- about the current user and session to them.
- Uploaded HTML files can now be edited using the WYSIWYG HTML editor. </DD>
-
-<DT> Choices</DT>
-<DD> Results can now be "published" (either with names or anonymously) so that
- everyone can see the statistics. Choice text can be edited using HTML editor.</DD>
-
-<DT> Grades</DT>
-<DD> Students can now see all their own grades for a course on one page, accessible
- from the course home page.</DD>
-
-<DT> Quizzes</DT>
-<DD> Students can now review all their past quiz attempts, but only if the quiz has been closed,
- and if the teacher allows it.</DD>
-
-<DT> Authorisation </DT>
-<DD> The database module now supports databases that contain md5-encrypted passwords,
- which means it should now be compatible with systems like PostNuke. When using
- external authorisation students are now forced to fully fill-out their information
- before they can enter any course. An ADOdb bug was also causing some mischief
- when the external database type was the same as the Moodle database.
- Overall it's now quite usable.</DD>
-
-<DT> Administration </DT>
-<DD> The admin can now assign other people to also be admins. The interface to the
- Database Manager has been cleaned up, and it now always uses the same
- language as the current Moodle language (see separate download for <A HREF="http://moodle.com/mod/resource/view.php?id=8">moodle-1.0.8-mysql-admin.zip</A>).</DD>
-
-<DT> Debugging mode </DT>
-<DD> Admins/developers can use a "debugging mode" which prints more information
- and warning messages about unset variables and so on - making it easier to
- find bugs. To make this work a LOT of cleaning up has been done on existing
- Moodle code to make it more robust.</DD>
-
-<DT> Other things</DT>
-<DD>
- <LI> Unpacked template module is ignored by Moodle.
- <LI> A default country can be set by the admin
- <LI> View source button in Richtext editor was missing with some languages
- <LI> A bug affecting grades page on some installations was fixed.
- <LI> File upload problems on 4.3.0 have been fixed.
- <LI> Some minor problems with the display of logs has been fixed.
- <LI> Improved GD detection that works with PHP 4.3.0
- <LI> If GD is not present then Moodle is now more usable (just less capable)
- <LI> A bug causing the wrong display of the date has been fixed.
- <LI> Usernames can now contain "." and "-" characters.
- <LI> Cookies now use table prefixes for unique naming, so that many
- different moodle sites can be run on the same web site and database.
- <LI> Site news forum heading can now be changed (edit the forum).
- <LI> Improved code for gathering form input
- <LI> The buggy_referrer variable is fixed and now works as expected
- <LI> Some small performance improvements here and there
- <LI> Other improvements I probably forgot to add here
- <LI> Many little code clean-ups.
-</DD>
-
-</DL></UL>
-
-
-<HR>
-<H3> New in Moodle 1.0.7 (10th December, 2002): </H3>
-<UL><DL>
-<DT> Simpler version numbers!</DT>
-<DD> The four-digit version numbers were getting a bit ridiculous (too complex),
- so I've switched back to simpler 3-digit numbers. The first digit is the
- major structural version, the second digit is for decent-sized upgrades
- and the third digit is for minor upgrades.</DD>
-
-<DT> Languages</DT>
-<DD> Two completely new languages have been added: Indonesian (from Arfan Hidayat)
- and Japanese (from Mitsuhiro Yoshida). A US English version was added too.
- Most other languages contain some updates. All languages now contain locale
- information, which means that when a user changes the language all the dates
- will display properly too.</DD>
-
-<DT> Database access</DT>
-<DD> ADOdb was upgraded to 2.50 which should fix some problems with very
- new versions of PHP (4.3.0).</DD>
-
-<DT> Layout improvements</DT>
-<DD> Cleaned up the display of "side boxes" and added CSS style control over
- more elements on the site and course pages. You may need to upgrade
- your custom themes to get the full effect. Changes are in styles.php,
- config.php and one line in header.html.
-
- <P>The interface when
- courses are on front page and there is more than one category has
- been improved (no longer just shows short course names).</P>
-
- </DD>
-
-<DT> Class interface</DT>
-<DD> A wrapper file provides a class interface to main Moodle library
- (for external programs interfacing to Moodle) - moodle/lib/makeclass.php</DD>
-
-<DT> Small improvements and bug fixes</DT>
-<DD>
- <LI> Quizzes now have a confirmation dialog when submitting an attempt
- <LI> Courses now default to having "show recent activity" on (again).
- <LI> Abolished leading zeroes in dates (introduced in last release)
- <LI> Some formatting fixes for Japanese and old Netscape browsers
- <LI> Teacher can allow larger assignments to be uploaded
- <LI> Change password button on user page now always functions like the one on login page
- <LI> Forum search now searches subjects as well as messages
- <LI> Various HTML fixes
- <LI> Fixes to grades display when there are no grades, also no forum ratings
- <LI> Slashes in requested filenames are now stripped
- <LI> Updates to the documentation
-</DD>
-
-
-</DL></UL>
-
-
-
-<HR>
-<H3> New in Moodle 1.0.6.4 (24th November, 2002) : </H3>
-<UL><DL>
-
-<DT> Authentication</DT>
-<DD> Moodle now features seven different authentication mechanisms,
- making it possible to hook Moodle up to nearly any external list
- of users!</P>
- <P>New methods just added include IMAP, POP3 and NNTP servers (including
- those using SSL or certificate-based authentication), and also
- authentication against user-specified fields in ANY
- external database table.</P>
- <P>The login page can now be partially customised
- by the admin with personalised instructions, and the guest login can be
- hidden if desired. </P>
- <P>"Mappings" can be defined so that other fields (such as email, firstname,
- lastname, department, language etc) can also be copied from LDAP or an
- external database when accounts are first used.</P>
-
- <P>Finally, Moodle now sports a cool
- new admin GUI for configuring all of this, so it should be pretty
- easy now to set up external authentication.
- Many thanks to contributor Petri Asikainen for helping with the admin GUI.</P></DD>
-
-<DT> Languages</DT>
-<DD> Complete new Norwegian translation (from Jøran Sørb\8eø), and updates for several others.</DD>
-
-<DT> Assignments</DT>
-<DD> Students can now resubmit assignments after grading if the teacher allows it</DD>
-
-<DT> Contributed code</DT>
-<DD> Standalone user-contributed code is now distributed under the /contrib directory. This directory
- could get quite large, and the quality/security of it has usually not been checked by me,
- and so this code is not included in the standard releases and nightlies. However, people
- who are interested in it can access it via CVS (or see <A HREF="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/contrib/">CVS web view</A>). As these new features become polished or if demand grows for them,
- then I'll integrate them into the main Moodle distribution.
- <BR><BR>
- The first contributor is Holger Schadeck (compuproggy), who has written some <A HREF="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/contrib/compuproggy/">interesting code</A> to help with translating all the Moodle help files. Check it out!</DD>
-
-<DT> Bug fixes</DT>
-<DD>
- <LI> Day value in dates (eg forum posts, weekly listing) are
- now displayed correctly on Windows servers.
- <LI> config-dist.php and README.txt is now in DOS format to make it easier for Windows users to get started (Unix users shouldn't be affected).
- <LI> Added a workaround (and new config switch in config-dist.php) for
- some systems which have buggy referer variables. This should help
- those people getting "stuck" on a form during setup.
- <LI> Logout now sends you to the home page and clears the session completely.
- <LI> Timezones now range between -13 to 13 hours (for daylight saving).
- <LI> Character set in email now matches current language.
- <LI> User pictures are now uploaded even if other fields have errors.
- <LI> Full-size user pictures on user profile page no longer clickable.
- <LI> Long user listing now has a small notice at the bottom about automatic unenrolment
- <LI> Unenrol and change password buttons are hidden for guest student
- <LI> Fixed occasional case where submitted assignments were sometimes having their owner changed.
- <LI> User log graphs are now faster, cleaner and translatable.
- <LI> Fixed HTML display errors with courses in category boxes on front page.
- <LI> Admin and guest accounts now always work, even with external authentication activated.
- <LI> Slightly more security when writing/reading files (now checks for embedded scripting).
- <LI> The same user can now be deleted more than once (create, delete, recreate, delete caused error).
- <LI> Language editor now works with multibyte languages (Thanks, Mits)
-</DD>
-
-</DL></UL>
-
-
-<HR>
-<H3> New in Moodle 1.0.6.3 (14th November, 2002) : </H3>
-<UL><DL>
-
-<DT> Bug fix for no-name forums.</DT>
-<DD> New sites created with 1.0.6.2 had some forums appearing with no names
- (for example the News forum on the home page).
- A workaround is to add a new activity to that section (all the names
- will be refreshed), but this release will fix it too. </DD>
-
-<DT> New languages!</DT>
-<DD> Catalan and Spanish (Spain) translations have arrived!</DD>
-
-<DT> Some display improvements for old Netscape browsers (headers and quizzes)</DT>
-
-<DT> Guest language now ALWAYS the same as the current site language</DT>
-
-<DT> "Recent Activity" can now be disabled completely if desired </DT>
-
-<DT> For very large classes (larger than 500) participant list is not displayed</DT>
-
-</DL></UL>
-
-<HR>
-
-<H3> New in Moodle 1.0.6.2 (11th November, 2002) : </H3>
-<UL><DL>
-<DT> Course formatting improvements </DT>
-<DD> The weekly and topic formats now have an extra "general" area up
- the top where "general" activities are listed - these are things
- that apply throughout the course, not just to one particular topic
- or week. This general area is not shown if it is completely empty.</DD>
-
-<DT> Popup "jump" menu. </DT>
-<DD> You can now jump from one activity directly to any other using a
- popup menu in the upper-right corner of the page</DD>
-
-<DT> Speed improvements </DT>
-<DD> Course activity details are now cached for each course, which
- greatly reduces the amount of database access required to display
- the course page. On heavily accessed systems this should improve speed.</DD>
-
-<DT> Languages </DT>
-<DD> Surveys are now completely translatable.</DD>
-
-<DT> Admin improvements </DT>
-<DD> Paging was added to the user admin page, so that the admin can now
- browse large numbers of users. </DD>
-
-<DT> Fixes and tweaks </DT>
-<DD> Various other small improvements to formatting</DD>
-</DL></UL>
-
-
-<HR>
-
-<H3> New in Moodle 1.0.6.1 (6th November, 2002) : </H3>
-<UL><DL>
-<DT> New assignment type: offline assignments </DT>
-<DD> In addition to "upload a file" assignments, you can now have "offline"
- assignments. These don't require the student to do anything online.
- They are useful for grading activities that are not on in Moodle, and a
- also useful for adding "manual" columns to the grade page.</DD>
-
-<DT> Languages </DT>
-<DD> Spanish (Mexican) has been added to the distribution. Other languages have various improvements.</DD>
-
-<DT> SMTP authentication </DT>
-<DD> SMTP mail now supports SMTP username and password if needed</DD>
-
-<DT> Documentation </DT>
-<DD> Some parts rewritten, and documentation cleaned up (upgrade info now part of main docs)</DD>
-
-<DT> Other fixes </DT>
-<UL><LI>Better checking on teachers using "loginas" to stop them roaming other courses as a student
- <LI>While using "loginas", teachers can return to their own identity using a link in the footer
- <LI>Some strings fixed in assignments, journals, and forums.
- <LI>Guest language is now the same as the site
- <LI>etc
- </UL></DD>
-
-</DL></UL>
-
-
-<HR>
-<H3> New in Moodle 1.0.6 (26th October, 2002) : </H3>
-
-<UL><DL>
-<DT> New feature - WYSIWYG Text editing! </DT>
-<DD> A WYSIWYG text editor has been added to many of the forms in Moodle. These are currently
- only visible when using Microsoft Internet Explorer 5.5 or later - other browsers see the
- normal forms exactly as before.</DD>
-
-<DT> New feature - Quiz module! </DT>
-<DD> Finally, the most requested new module is here! Multiple choice, short answer, and true-false
- questions with automatic marking, multiple attempts, teacher regrading and many other features.
- Questions are stored in a categorised database, and may be "published" to other courses.</DD>
-
-<DT> New feature - Grade manager! </DT>
-<DD> A new tool has been added for teachers to see all grades for a course on one page.
- You can also download/export grades as a tab-separated text file or an Excel
- Spreadsheet. In future more features will be added to this page like sorting, manual
- columns and calculations, but it's still pretty useful right now.</DD>
-
-<DT> New feature - LDAP authentication! </DT>
-<DD> Moodle can now authenticate against external directories that use the
- LDAP protocol (including Novell etc). Many thanks to Petri Asikainen for
- developing this authentication plug-in!</DD>
-
-<DT> New feature - New smilies </DT>
-<DD> Many new smilies have been added, and are now also accessible using a GUI in the text editor.</DD>
-
-<DT> Improved text editing </DT>
-<DD> You can now include all major HTML tags in all texts. This is now safe because
- of newly added functionality that strips all Javascript and faulty tags from texts
- before they can cause security or display problems.</DD>
-
-<DT> Languages </DT>
-<DD> German and Italian have been added! Many thanks to the translators (see the credits).</DD>
-
-<DT> Reading module => Resource module </DT>
-<DD> After much thought and a vote of support (21 "yes" to 6 "no") on the "Using Moodle"
- web site I changed the name of the "reading" module to "resource" (at the code level
- and also the language packs). It was better to do this earlier than later.
- This more generic name will be more meaningful to more people and opens the way to
- some real development on a resource library.
- But I don't want to ever change a module name again! :-)
- If you have any hard-coded URLs pointing to readings that you don't want to break,
- you can add a line like this to your Apache httpd.conf to redirect them:
- <P><CODE>Redirect /mod/reading http://yourserver.com/mod/resource</CODE></P>
- <FONT COLOR=RED>Note: if upgrading to 1.0.6 you may have some "reading" errors in "Recent activity" ... logging
- out and then logging in again will fix this</FONT></DD>
-
-<DT> Other additions </DT>
-<DD> An admin script to totally delete the Moodle data directory has been included (admin/delete.php)
- for people who need to tear down a Moodle installation but don't have root access on their
- server.</DD>
-
-<DT> Miscellaneous </DT>
-<DD> Many small improvements have been made to the interface, and many small bugs have been fixed.
- Some examples:
- <UL>
- <LI> Big "Edit this page" buttons at the top of pages (replacing the tiny icon)
- <LI> LDAP authentication module (thanks to Petri)
- <LI> Authentication from external sources can now import any fields
- <LI> Student assignment list now shows submission status properly
- <LI> Default language for users is now the site language
- <LI> Users have a 'Change Password' button on their profile page
- <LI> Journals that need teacher feedback are highlighted
- <LI> More documentation and more context help buttons
- <LI> Database-specific upgrade code
- <LI> Uses character-set codes to make the browser do the right thing
- <LI> User's name in footer is now a link
- <LI> News and social forums are now editable
- <LI> Forums that don't allow posting don't have uneccessary "discuss" links
- <LI> Improved algorithm for shortening posts in forum listings
- <LI> Choice module now allows up to six choices
- </UL>
-</DD>
-</DL></UL>
-
-<P>Older releases can be seen in the <A HREF="http://moodle.com/mod/forum/view.php?f=1">Moodle.com announcement forum</A>.
-
-
-<P> </P>
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="../doc/" TARGET="_top">Moodle Documentation</A></FONT></P>
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
+++ /dev/null
-<HEAD>
-
- <TITLE>Moodle Docs: Teachers Manual</TITLE>
-
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
-
-</HEAD>
-
-
-
-<BODY BGCOLOR="#FFFFFF">
-
-
-
-<H2>Teacher Manual</H2>
-
-<P>This page is a quick guide to creating online courses with Moodle. It outlines
-
- the main functions that are available, as well as some of the main decisions
-
- you'll need to make.</P>
-
-
-
-<P>Sections in this document:</P>
-
-<OL>
-
- <LI><A HREF="#started">Getting started</A></LI>
-
- <LI><A HREF="#settings">Course settings</A></LI>
-
- <LI><A HREF="#upload">Uploading files</A></LI>
-
- <LI><A HREF="#activities">Setting up activities</A></LI>
-
- <LI><A HREF="#course">Running the course</A></LI>
-
- <LI><A HREF="#further">Further information</A></LI>
-
-</OL>
-
-<H3><A NAME="started"></A>Getting started</H3>
-
-<blockquote>
-
- <p>This document assumes your site administrator has set up Moodle and given
-
- you new, blank course to start with. It also assumes you have logged in to
-
- your course using your teacher account.</p>
-
- <p>Here are three general tips that will help you get started.</p>
-
- <ol>
-
- <li><strong>Don't be afraid to experiment:</strong>
-
- <blockquote>feel free to poke around and change things. It's hard to break anything
-
- in a Moodle course, and even if you do it's usually easy to fix it.
-
- </blockquote>
-
- <li><strong>Notice and use these little icons</strong>:
-
- <blockquote>
-
- <p> <img src="../pix/i/edit.gif"> - the <strong>edit icon</strong>
-
- lets you edit whatever it is next to.</p>
-
- <p><img src="../pix/help.gif" width="22" height="17"> - the <strong>help
-
- icon</strong> will provide you with a popup help window </p>
-
- </blockquote>
-
- </li>
-
- <li><strong>Use the navigation bar at the top of each page</strong>
-
- <blockquote>this
-
- should help remind you where you are and prevent getting lost.
-
- </blockquote></li>
-
- </ol>
-
- <hr>
-
-</blockquote>
-
-<h3><A NAME="settings"></A>Course settings</h3>
-
-<blockquote>
-
- <p>The first thing you should do is look under the "Administration"
-
- on your course home page and click on "<strong>Settings...</strong>"
-
- (Note that this link, and in fact the whole Administration section is only
-
- available to you (and the site administrator). Students will not even see
-
- these links).</p>
-
- <p>On the Settings page you can change a number of settings about your course,
-
- ranging from its name to what day it starts. I won't talk here about all these,
-
- as they all have a help icon next to them which explains them all in detail.
-
- However, I will talk about the most important of these - the <strong>course
-
- format</strong>.</p>
-
- <p>The course format that you choose will decide the basic layout of your course,
-
- like a template. Moodle version 1.0 has three formats - in future there will
-
- probably be many more (please send new ideas to <a href="mailto:martin@moodle.com">martin@moodle.com</a>!)</p>
-
- <p>Here are some screenshots of three sample courses in each of these three
-
- formats (ignore the different colours, which are set for a whole site by the
-
- site administrator):</p>
-
- <p align="center"><strong>Weekly format:</strong></p>
-
- <p align="center"><img src="pix/weekly.jpg" width="570" height="527"></p>
-
- <p align="center"> </p>
-
- <p align="center"><strong>Topics format:</strong></p>
-
- <p align="center"><img src="pix/topics.jpg" width="570" height="463"></p>
-
- <p align="center"> </p>
-
- <p align="center"><strong>Social format:</strong></p>
-
- <p align="center"><img src="pix/social.jpg" width="570" height="429"></p>
-
- <p> </p>
-
- <p>Note that the weekly and topics formats are very similar in structure. The
-
- main difference is that each box in the weekly format covers exactly one week,
-
- whereas in the topic format each box can cover whatever you like. The social
-
- format doesn't use much content at all and is based around just one forum
-
- - this is displayed on the main page.</p>
-
- <p>See the help buttons on the Course Settings page for more details.</p>
-
- <HR>
-
-</blockquote>
-
-<H3><A NAME="upload"></A>Uploading files</H3>
-
-<blockquote>
-
- <p>You may have existing content that you want to add to your course, such as
-
- web pages, audio files, video files, word documents, or flash animations.
-
- Any type of file that exists can be uploaded into your course and stored on
-
- the server. While your files are on the server you can move, rename, edit
-
- or delete them.</p>
-
- <p>All of this is achieved through the <strong>Files</strong> link in your Administration
-
- menu. The Files section looks like this:</p>
-
- <p align="center"><img src="pix/files.jpg" width="400" height="347"></p>
-
- <p> </p>
-
- <p>This interface is only available to teachers - it is not accessible by students.
-
- Individual files are made available to students later on (as "Resources"
-
- - see the next section).</p>
-
- <p>As you can see in the screenshot, files are listed alongside subdirectories.
-
- You can create any number of subdirectories to organise your files and move
-
- your files from one to the other.</p>
-
- <p>Uploading files via the web is currently restricted to one file at a time.
-
- If you want to upload a lot of files at once (for example a whole web site),
-
- it can be a lot easier to use a <strong>zip program</strong> to compress them
-
- into a single file, upload the zip file and then unzip them again on the server
-
- (you will see an "unzip" link next to zip archives).</p>
-
- <p>To preview any file you have uploaded just click on its name. Your web browser
-
- will take care of either displaying it or downloading it to your computer.</p>
-
- <p>HTML and text files can be edited in-place online. Other files will need
-
- to be edited on your local computer and uploaded again. if you upload a file
-
- with the same name as an existing file it will automatically be overwritten.</p>
-
- <p>A final note: if your content resides out on the web then you don't need
-
- to upload the files at all - you can link directly to them from inside the
-
- course (see the Resources module and the next section).</p>
-
- <HR>
-
-</blockquote>
-
-<H3><A NAME="activities"></A>Setting up activities</H3>
-
-<blockquote>
-
- <p>Building a course involves adding course activity modules to the main page
-
- in the order that students will be using them. You can shuffle the order any
-
- time you like.</p>
-
- <p>To turn on editing, click "Turn on editing" under Administration.
-
- This toggle switch shows or hides the extra controls that allow you to manipulate
-
- your main course page. Note in the first screenshot above (of the Weekly format
-
- course) that the editing controls are turned on.</p>
-
- <p>To add a new activity, simply go to the week or topic or section of the screen
-
- where you want to add it, and select the type of activity from the popup menu.
-
- Here is a summary of all the standard activities in Moodle 1.0:</p>
-
- <dl>
-
- <dt><strong>Assignment</strong></dt>
-
- <dd>An assignment is where you set a task with a due date and a maximum grade.
-
- Students will be able to upload one file to satisify the requirements. The
-
- date they upload their file is recorded. Afterwards, you will have a single
-
- page on which ou can view each file (and how late or early it is), and then
-
- record a grade and a comment. Half an hour after you grade any particular
-
- student, Moodle will automatically email that student a notification. </dd><BR>
-
- <BR>
-
- <dt><strong>Choice</strong></dt>
-
- <dd>A choice activity is very simple - you ask a question and specify a choice
-
- of responses. Students can make their choice, and you
-
- have a report screen where you can see the results. I use it to gather research
-
- consent from my students, but you could use it for quick polls or class
-
- votes.</dd>
-
- <BR>
-
- <BR>
-
- <dt><strong>Forum</strong></dt>
-
- <dd>This module is by far the most important - it is here that discussion
-
- takes place. When you add a new forum, yu will presented with a choice of
-
- different types - a simple single-topic discussion, a free-for-all general
-
- forum, or a one-discussion-thread-per-user.</dd>
-
- <BR>
-
- <BR>
-
- <dt><strong>Journal</strong></dt>
-
- <dd>Each journal activity is an entry in the whole course journal. For each
-
- one you can specify an open-ended question that guides what students write,
-
- as well as a window of time in which the journal is open (weekly course
-
- format only). Encourage students to write reflectively and critically in
-
- these journals, as they are only available to them and you. Afterwards,
-
- you will be able to grade and comment all the entries for that week or topic,
-
- and students will receive an automatic email informing them of your feedback.</dd>
-
- <BR>
-
- <BR>
-
- <dt><strong>Resource</strong></dt>
-
- <dd>Resources are the content of your course. Each resource can be any file
-
- you have uploaded or can point to using a URL. You can also maintain simple text-based pages by typing them
-
- directly into a form.</dd>
-
- <BR>
-
- <BR>
-
- <dt><strong>Quiz</strong></dt>
-
- <dd>This module allows you to design and set quiz tests, consisting of
-
- multiple choice, true-false, and short answer questions. These
-
- questions are kept in a categorised database, and can be re-used
-
- within courses and even between courses. Quizzes can allow
-
- multiple attempts. Each attempt is automatically marked, and the
-
- teacher can choose whether to give feedback or to show correct answers.
-
- This module includes grading facilities.
-
- </dd>
-
- <BR>
-
- <BR>
-
- <dt><strong>Survey</strong></dt>
-
- <dd>The survey module provides a number of predefined survey instruments that are useful in
-
- evaluating and understanding your class. Currently they include the COLLES and the ATTLS instruments.
-
- They can be given to students early in the course as a diagnostic tool and at the end of the
-
- course as an evaluation tool (I use one every week in my courses).</dd>
-
- </dl>
-
- <BR>
-
- <p>After adding your activities you can move them up and down in your course
-
- layout by clicking on the little arrow icons (<img src="../pix/t/up.gif" width="9" height="10">
-
- <img src="../pix/t/down.gif" width="9" height="10">) next to each one. You
-
- can also delete them using the cross icon <img src="../pix/t/delete.gif" width="10" height="10">,
-
- and re-edit them using the edit icon <img src="../pix/t/edit.gif" width="10" height="11">.</p>
-
- <HR>
-
-</blockquote>
-
-<H3><A NAME="course"></A>Running the course</H3>
-
-<blockquote>
-
- <p>I could write a thesis about this. Actually I <strong>am</strong> writing
-
- a thesis about this. <img src="../pix/s/biggrin.gif" width="15" height="15"></p>
-
- <p>Until then here are just a few quick pointers:</p>
-
- <ol>
-
- <li>Subscribe yourself to all the forums.</li>
-
- <li>Encourage all the students fill out their user profile (including photos)
-
- and read them all - this will help provide some context to their later writings.</li>
-
- <li>Keep notes to yourself in the private "<strong>Teacher's Forum</strong>"
-
- (under Administration). This is especially useful when team teaching.</li>
-
- <li>Use the "<strong>Logs</strong>" link (under Administration)
-
- to get access to complete, raw logs. In there you'll see a link to a popup
-
- window that updates every sixty seconds and shows the last hour of activity.
-
- This is useful to keep open on your desktop all day so you can feel in touch
-
- with what's going on in the course.</li>
-
- <li>Use the "<strong>Activity Reports</strong>" (next to each name
-
- in the list of all people, or from any user profile page). These provide
-
- a great way to see what any particular person has been up to in the course.</li>
-
- <li>Respond quickly to students. Don't leave it for later - do it right away.
-
- Not only is it easy to become overwhelmed with the volume that can be generated,
-
- but it's a crucial part of building and maintaining a community feel in
-
- your course.</li>
-
- </ol>
-
- <HR>
-
-</blockquote>
-
-<H3><A NAME="further"></A>Further information</H3>
-
-<blockquote>
-
- <p>If you have any particular problems with your site, you should contact your
-
- local site administrator.</p>
-
- <p>If you have some great ideas for improvements to Moodle, or even some good
-
- stories, come over to <a href="http://moodle.com/" target="_top">moodle.com</a> and join
-
- in the course called "<A HREF="http://moodle.com/course/view.php?id=5" target=_top >Using Moodle</A>".
-
- We'd love to hear from you, and you can help Moodle improve.</p>
-
- <p>If you want to contribute to coding new modules, or writing documentation,
-
- or papers, contact me: <a href="http://dougiamas.com/" target="_top">Martin
-
- Dougiamas</a> or browse the "bug tracker" site for Moodle, at <a href="http://bugs.moodle.com" target="_top">bugs.moodle.com</a></p>
-
- <p align="center">Thanks for using Moodle - good luck!</p>
-
- <HR>
-
- <p> </p>
-
-</blockquote>
-
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
-
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id: teacher.html,v 1.4 2002/08/18 10:00:01
-
- martin Exp $</FONT></P>
-
-
-
-</BODY>
-
+++ /dev/null
-<HEAD>
-
- <TITLE>Moodle Docs: Upgrading</TITLE>
-
- <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
-
-</HEAD>
-
-
-
-<BODY BGCOLOR="#FFFFFF">
-
-<H2>Upgrading Moodle</H2>
-
-
-
-<p>Moodle is designed to upgrade cleanly from any earlier version to any later
-
- version. </p>
-
-<p>When upgrading a Moodle installation you should follow these steps:</p>
-
-<h2>1. Backup important data</h2>
-
-<blockquote>
-
- <p>Although it is not strictly necessary, it is always a good idea to make a
-
- backup of any production system before a major upgrade, just in case you need
-
- to revert back to the older version for some reason. In fact, it's a good
-
- idea to automate your server to backup your Moodle installation daily, so
-
- that you can skip this step.</p>
-
- <p>There are three areas that need backing up:</p>
-
- <blockquote>
-
- <p><strong>1. The Moodle software directory itself</strong></p>
-
- <blockquote>
-
- <p>Make a separate copy of these files before the upgrade, so that you can
-
- retrieve your config.php and any modules you have added like themes, languages
-
- etc<strong><br>
-
- </strong></p>
-
- </blockquote>
-
- <p><strong>2. Your data directory.</strong></p>
-
- <blockquote>
-
- <p>This is where uploaded content resides (such as course resources and
-
- student assignments) so it is very important to have a backup of these
-
- files anyway. Sometimes upgrades may move or rename directories within
-
- your data directory.<strong><br>
-
- </strong></p>
-
- </blockquote>
-
- <p><strong>3. Your database</strong></p>
-
- <blockquote>
-
- <p>Most Moodle upgrades will alter the database tables, adding or changing
-
- fields. Each database has different ways to backup. One way of backing
-
- up a MySQL database is to 'dump' it to a single SQL file. The following
-
- example shows Unix commands to dump the database called "moodle":</p>
-
- <blockquote>
-
- <p><font face="Courier New, Courier, mono">mysqldump moodle > moodle-backup-2002-10-26.sql</font></p>
-
- </blockquote>
-
- <p>You can also use the "Export" feature in Moodle's "Manage
-
- Database" web interface to do the same thing on all platforms.</p>
-
- </blockquote>
-
- </blockquote>
-
-</blockquote>
-
-<h2> </h2>
-
-<h2>2. Install the new Moodle software</h2>
-
-<blockquote>
-
- <p><strong>Using a downloaded archive</strong></p>
-
- <blockquote>
-
- <p>Do not overwrite an old installation unless you know what you are doing
-
- ... sometimes old files can cause problems in new installations. The best
-
- way it to rename the current Moodle directory to something else, then unpack
-
- the new Moodle archive into the old location.</p>
-
- <blockquote>
-
- <p><font face="Courier New, Courier, mono">mv moodle moodle.backup<br>
-
- tar xvzf moodle-1.0.6.tgz</font></p>
-
- </blockquote>
-
- <p>Next, copy across your config.php and any other plugins such as custom
-
- themes:</p>
-
- <blockquote>
-
- <p><font face="Courier New, Courier, mono">cp moodle.backup/config.php moodle<br>
-
- cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme</font></p>
-
- </blockquote>
-
- </blockquote>
-
- <p><strong>Using CVS</strong></p>
-
- <blockquote>
-
- <p>If you are using CVS, just go into the Moodle root directory and update
-
- to the new files:</p>
-
- <blockquote>
-
- <p><font face="Courier New, Courier, mono">cvs update -dP</font></p>
-
- </blockquote>
-
- <p>Make sure you use the "d" parameter to create new directories
-
- if necessary, and the "P" parameter to prune empty directories.</p>
-
- <p>If you have been editing Moodle files, watch the messages very closely
-
- for possible conflicts. All your customised themes and non-standard plugins
-
- will be untouched.</p>
-
- </blockquote>
-
- <p> </p>
-
-</blockquote>
-
-<h2>3. Finishing the upgrade</h2>
-
-<blockquote>
-
- <p>The last step is to trigger the upgrade processes within Moodle.</p>
-
- <p>To do this just visit <a target=_top href="../admin/index.php">the admin page of your
-
- installation</a>.</p>
-
- <blockquote>
-
- <p><font face="Courier New, Courier, mono">http://example.com/moodle/admin</font></p>
-
- </blockquote>
-
- <p>It doesn't matter if you are logged in as admin or not.</p>
-
- <p> Moodle will automatically detect the new version and perform all the database
-
- or filesystem upgrades that are necessary. If there is anything it can't do
-
- itself (very rare) then you will see messages telling you what you need to
-
- do. </p>
-
-</blockquote>
-
-<p> </p>
-
-<p> Assuming all goes well (no error messages) then you can start using your new
-
- version of Moodle and enjoy the new features!</p>
-
-<p>If you have trouble with the upgrade, visit <a target=_top href="http://moodle.com/">moodle.com</a>
-
- and post on the <a target=_top href="http://moodle.com/mod/forum/view.php?id=28">Installation
-
- Support Forum</a>.</p>
-
-<p> </p>
-
-<P> </P>
-
-<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
-
-<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
-
-
-
-</BODY>
-
projects / moodle.git / commitdiff