Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

*** empty log message ***

  • Loading branch information...
commit c74a276913d53401badf4cd8fc07c0c27be8cf2d 1 parent a2da49f
authored January 26, 2003
44  lang/de/docs/background.html
... ...
@@ -0,0 +1,44 @@
  1
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  2
+<HTML>
  3
+<HEAD>
  4
+  <TITLE>Moodle Docs: Background</TITLE>
  5
+  <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
  6
+</HEAD>
  7
+<BODY BGCOLOR="#ffffff">
  8
+  
  9
+<H2>Background</H2>
  10
+ 
  11
+<P>Moodle is an active and evolving work in progress.</P>
  12
+<P>I've been working on it, in some way or other, for several years. It started 
  13
+  in the 90's when I was webmaster at <a target=_top href="http://www.curtin.edu.au/">Curtin University 
  14
+  of Technology</a> and a system administrator of their WebCT installation. I 
  15
+  encountered many frustrations with the WebCT beast and developed an itch that 
  16
+  needed scratching - there had to be a better way (no, not Blackboard :-)</P>
  17
+<P>I also know a lot of people in schools and smaller institutions (and some big 
  18
+  ones!) who want to make better use of the Internet but don't know where to start 
  19
+  in the maze of technologies and pedagogies that are out there. I've always hoped 
  20
+  there would be a Free alternative that such people could use to help them move 
  21
+  their teaching skills into the online environment.</P>
  22
+<P>My strong beliefs in the unrealised possibilities of Internet-based education 
  23
+  led me to complete a Masters and then a PhD in Education, combining my former 
  24
+  career in Computer Science with newly constructed knowledge about the nature 
  25
+  of learning and collaboration.</P>
  26
+<P>Since then Moodle has progressed through several very different prototypes 
  27
+  until the release of version 1.0 upon a largely unsuspecting world on 
  28
+  August 20, 2002 and a steady series of improved releases since then.
  29
+<P>I've been using it in several courses and find it an 
  30
+  extremely usable and reliable tool for building high-quality online courses 
  31
+  - others are reporting the same. Given the context in which it's been designed, 
  32
+  it works particularly well for smaller institutions, or for smaller, more intimate 
  33
+  classes.</P>
  34
+<P>When compared to the big commercial tools such as WebCT or Blackboard I think 
  35
+  it still falls short in some areas (such as scalability and standards support), 
  36
+  but it comes out ahead in many others (see <a href="index.php?file=features.html">Features</a>). 
  37
+</P>
  38
+<P>&nbsp;</P>
  39
+
  40
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
  41
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
  42
+
  43
+</BODY>
  44
+</HTML>
215  lang/de/docs/credits.html
... ...
@@ -0,0 +1,215 @@
  1
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  2
+<HTML>
  3
+<HEAD>
  4
+  <TITLE>Moodle Docs: Credits</TITLE>
  5
+  <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
  6
+</HEAD>
  7
+  <BODY BGCOLOR="#ffffff">
  8
+        
  9
+<H2>Credits</H2>
  10
+       
  11
+<P><B>Moodle </B>itself is Copyright &copy; 2001-2002, <A TARGET=_top HREF="http://dougiamas.com/"> 
  12
+  Martin Dougiamas</A>. &nbsp;It is distributed under the <A HREF="licence.html"> 
  13
+  GNU Public License</A>.</P>
  14
+
  15
+
  16
+   
  17
+<H3><BR>Special thanks</H3>
  18
+<UL>
  19
+    <B><A TARGET=_top HREF="http://pctaylor.com">Dr Peter C. Taylor</A></B>, 
  20
+    at Curtin University of Technology in Perth, Australia, for working 
  21
+    with the earliest prototypes and making many useful suggestions along the way</LI>
  22
+</UL>
  23
+
  24
+
  25
+
  26
+<H3><BR>Translations</H3>
  27
+<BLOCKQUOTE>      
  28
+<P>Many thanks to these people - each translation takes many hours of work, as there are nearly 
  29
+   900 phrases to translate (plus all the help files!).  
  30
+   These are listed in the order they joined the project:
  31
+<UL>
  32
+    <LI><B>en - English</B>, by Martin Dougiamas
  33
+    <LI><B>fr - French</B>, by Sébastien Namèche, seb@gaia.anet.fr, <A HREF="http://gaia.anet.fr/">http://gaia.anet.fr/</A>
  34
+    <LI><B>fi - Finnish</B>, by Petri Asikainen (paca@sci.fi), Jaana Tolvanen (jaanat@cedunet.com)
  35
+    <LI><B>it - Italian</B>, by Davide Suraci, icarused@tiscalinet.it
  36
+    <LI><B>pt_br - Portuguese (Brazil)</B>, by Fabricio Valadares, webdesigner@unincor.br
  37
+    <LI><B>de - German</B>, by Holger Schadeck, Holger.Schadeck@webdesign-forum.de
  38
+    <LI><B>es_mx - Spanish (Mexico)</B>, by Claudio Tavares, <A HREF="http://enlaceacademico.com">enlaceacademico.com</A>
  39
+    <LI><B>es_es - Spanish </B>, by Antonio J. Navarro Vergara, anavarro@sextaisla.com, <A HREF="http://www.sextaisla.com">www.sextaisla.com</A>
  40
+    <LI><B>ca - Catalan</B>, by Carles Bellver with the help of Mercè Renau, 
  41
+           Clara Andrés and Jordi Adell, cent@uji.es, <A HREF="http://cent.uji.es">Centre d'Educació i Noves Tecnologies</A>
  42
+    <LI><B>no - Norwegian</B>, by Jøran Sørbø, joran.sorbo@teleweb.no
  43
+    <LI><B>id - Indonesian</B>, by Arfan Hidayat, ivanh@telkom.net, <A HREF="http://www.kursusmaya.com">http://www.kursusmaya.com</A>
  44
+    <LI><B>ja - Japanese</B>, by Mitsuhiro Yoshida, mits@mitstek.com, <A HREF="http://mitstek.com">http://mitstek.com</A>
  45
+    <LI><B>tr - Turkish</B>, by M. Cüneyt Birkök, cuneyt@birkok.net, <A HREF="http://birkok.net">http://birkok.net</A>
  46
+    <LI><B>zh_cn - Chinese</B>, by Zhang Dexuan, cncoolbit@hotmail.com
  47
+    <LI><B>ar - Arabic</B>, by Ahmed Nabil, ana@harf.com
  48
+    <LI><B>sv - Swedish</B>, by Set Lonnert, set@setlonnert.com, <A HREF="http://setlonnert.com">http://setlonnert.com</A>
  49
+    <LI><B>th - Thai</B>, by Wim Singhanart, minkowski@ntlworld.com, <A HREF="http://www.suthira.net">www.suthira.net</A>
  50
+    <LI><B>nl - Dutch</B>, by Hans Zwart (hans@hansdezwart.info) and Jacob Romeyn (jromeyn@thekingsschool.net)
  51
+    <LI><B>es_ar - Spanish (Argentina)</B>, by Rodrigo Vigil (rmvigil@frre.utn.edu.ar)
  52
+
  53
+</UL>
  54
+</BLOCKQUOTE>      
  55
+
  56
+<H3><BR>Themes</H3>
  57
+<BLOCKQUOTE>      
  58
+<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:
  59
+<UL>
  60
+    <LI><B>standard* and cordoroyblue</B>, by Martin Dougiamas
  61
+    <LI><B>oceanblue</B>, by Mitsuhiro Yoshida, <A HREF="http://mitstek.com">http://mitstek.com</A>
  62
+    <LI><B>brightretro</B>, by Thomas Murdock, <A HREF="http://sand-paper.org/">http://sand-paper.org</A>
  63
+    <LI><B>garden</B>, by Spiggy, <A HREF="http://phpgirl.com">http://phpgirl.com</A>
  64
+</UL>
  65
+</BLOCKQUOTE>      
  66
+
  67
+
  68
+<H3><BR>Other contributors</H3>
  69
+<BLOCKQUOTE>      
  70
+<P>Thanks to all of you who have
  71
+<UL>
  72
+    <LI>donated via the <A TARGET=_top HREF="http://moodle.com/donations">Donations page</A>,
  73
+    <LI>contributed to the <A TARGET=_top HREF="http://bugs.moodle.com">bug tracker</A>, and
  74
+    <LI>participated in the "<A TARGET=_top HREF="http://moodle.com/course/">Using Moodle</A>" course at moodle.com</A>
  75
+</UL>
  76
+</P>
  77
+
  78
+<P>Especially, thanks to those of you who have at some time contributed 
  79
+   with long constructive discussions and especially code.  This list is long 
  80
+   and always changing, but some names include (in the order I added them):
  81
+   <UL> 
  82
+   Art Lader, 
  83
+   Matt Hope, 
  84
+   Tom Murdock, 
  85
+   Sébastien Namèche,
  86
+   Petri Asikainen, 
  87
+   James Miller, 
  88
+   Dustin Rue, 
  89
+   Holger Schadeck, 
  90
+   Giovanni Tummarello, 
  91
+   John Windmueller, 
  92
+   Sean Keogh,
  93
+   Mitsuhiro Yoshida,
  94
+   Mark Kimes, 
  95
+   Greg Barnett, 
  96
+   Mary Hunter
  97
+   </UL>
  98
+</P>
  99
+
  100
+<P>I apologise if for some reason your name is not on this list - it's very
  101
+   difficult to maintain!  Mail me and demand to be on it. :-)
  102
+</P>
  103
+
  104
+</BLOCKQUOTE>      
  105
+
  106
+   
  107
+<H3><BR>Moodle libraries</H3>
  108
+   
  109
+<BLOCKQUOTE>      
  110
+  <P>Some of Moodle's libraries were written by other people, and are being 
  111
+redistributed as part of Moodle under the LGPL. My thanks go out to the 
  112
+authors of all these excellent products - without them Moodle would be missing 
  113
+important functionality.  Copyright information for each package is included below:</P>
  114
+       
  115
+  <P><B>ADOdb &nbsp; </B>- &nbsp;lib/adodb<BR>
  116
+    </P>
  117
+       
  118
+  <BLOCKQUOTE>          
  119
+    <P>Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle,
  120
+Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.</P>
  121
+     
  122
+    <P>Version: 2.00 14 May 2002&nbsp;<BR>
  123
+  Copyright &copy;  2000, 2001 John Lim (jlim@natsoft.com.my)<BR>
  124
+  License: Dual LGPL and BSD-style<BR>
  125
+  URL: &nbsp;<A HREF="http://php.weblogs.com/adodb" TARGET="newpage">http://php.weblogs.com/adodb</A><BR>
  126
+      </P>
  127
+      </BLOCKQUOTE>
  128
+     
  129
+    <P><B>Graph Class</B> &nbsp; - &nbsp;lib/graphlib.php </P>
  130
+           
  131
+    <BLOCKQUOTE>              
  132
+      <P>Class to draw line, point, bar, and area graphs, including numeric
  133
+ x-axis and double y-axis.</P>
  134
+       
  135
+      <P>  Version: 1.6.3 (with modifications)<BR>
  136
+  Copyright &copy;&nbsp;2000&nbsp; Herman Veluwenkamp,&nbsp;hermanV@mindless.com<BR>
  137
+  License: LGPL<BR>
  138
+        </P>
  139
+        </BLOCKQUOTE>
  140
+
  141
+
  142
+          <P><B>IP-Atlas</B>&nbsp; - &nbsp; lib/ipatlas</P>
  143
+                       
  144
+          <BLOCKQUOTE>PHP scripts to show the location of an IP address on a map.<BR>
  145
+              <BR>
  146
+  Version: 1.0 (with modifications)<BR>
  147
+ Copyright &copy; 2002 &nbsp; Ivan Kozik<BR>
  148
+ License: GNU GPL<BR>
  149
+  URL: <A HREF="http://www.xpenguin.com/ip-atlas.php" TARGET="newpage">http://www.xpenguin.com/ip-atlas.php</A><BR>
  150
+         </BLOCKQUOTE>
  151
+                           
  152
+               
  153
+      <P><B>PHP mailer</B> &nbsp; - &nbsp;lib/class.phpmailer.php<BR>
  154
+        </P>
  155
+              
  156
+      <BLOCKQUOTE>Class for sending email using either sendmail, PHP mail(), 
  157
+or SMTP.&nbsp; Methods are based upon the standard AspEmail(tm) classes.<BR>
  158
+         <BR>
  159
+          Version 1.60, Created 03/30/2002<BR>
  160
+  Copyright &copy; 2001 Brent R. Matzelle &lt;bmatzelle@yahoo.com&gt;<BR>
  161
+  License: LGPL<BR>
  162
+  URL: &nbsp; <A HREF="http://phpmailer.sourceforge.net" TARGET="newpage">http://phpmailer.sourceforge.net</A><BR>
  163
+          <BR>
  164
+          </BLOCKQUOTE>
  165
+
  166
+
  167
+
  168
+           <P><B>PHP Simple Excel File Generator</B>&nbsp; - &nbsp; lib/psxlsgen.php</P>
  169
+                       
  170
+          <BLOCKQUOTE>Class to generate very simple MS Excel files (xls)
  171
+via PHP.<BR>
  172
+              <BR>
  173
+  Version: 0.3b<BR>
  174
+ Copyright &copy; 2001 &nbsp;Erol Ozcan &lt;eozcan@superonline.com&gt;<BR>
  175
+ License: GNU LGPL<BR>
  176
+  URL: <A HREF="http://psxlsgen.sourceforge.net" TARGET="newpage">http://psxlsgen.sourceforge.net</A><BR>
  177
+              </BLOCKQUOTE>
  178
+
  179
+
  180
+
  181
+
  182
+
  183
+          <P><B>Richtext Editor</B>&nbsp; - &nbsp; lib/rte</P>
  184
+                       
  185
+          <BLOCKQUOTE>HTML text editor for embedding in web pages.<BR>
  186
+              <BR>
  187
+  Version: 0.30 beta 1 (plus modifications)<BR>
  188
+ Copyright &copy; 2001  Ramesys (Contracting Services) Limited &lt;Austin.France@Ramesys.com&gt;
  189
+ License: GNU LGPL<BR>
  190
+  URL: <A HREF="http://richtext.sourceforge.net" TARGET="newpage">http://richtext.sourceforge.net</A><BR>
  191
+         </BLOCKQUOTE>
  192
+                           
  193
+                   
  194
+        <P><B>SMTP class &nbsp; </B>- &nbsp;lib/class.smtp.php<BR>
  195
+          </P>
  196
+                   
  197
+        <BLOCKQUOTE>Class that can be used to connect and communicate with
  198
+ any SMTP server. <BR>
  199
+  It implements all the SMTP functions defined in RFC821 except TURN.<BR>
  200
+           <BR>
  201
+ Version: 03/26/2001 <BR>
  202
+ Copyright &copy; 2001 &nbsp;Chris Ryan &lt;chris@greatbridge.com&gt;<BR>
  203
+           <BR>
  204
+            </BLOCKQUOTE>
  205
+                       
  206
+                          
  207
+            <BLOCKQUOTE><BR>
  208
+                </BLOCKQUOTE>
  209
+                               
  210
+              <P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
  211
+              <P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
  212
+
  213
+                                    
  214
+              </BODY>
  215
+              </HTML>
151  lang/de/docs/cvs.html
... ...
@@ -0,0 +1,151 @@
  1
+<html>
  2
+<head>
  3
+<title>Moodle Docs: How to use CVS</title>
  4
+<link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">
  5
+</head>
  6
+<body bgcolor="#ffffff">
  7
+<h2>Using CVS to access and update Moodle source code</h2>
  8
+<blockquote> 
  9
+  <p>CVS is the Concurrent Versioning System. It's a commonly used way of storing 
  10
+    source code because it keeps versions of all files so that nothing is ever 
  11
+    lost, and usage by different people is tracked. It also provides ways to merge 
  12
+    code if two or more people are working on the same file. All code and all 
  13
+    versions are stored on a central server (in this case, at <a href="http://www.sf.net/">Sourceforge</a>). 
  14
+  </p>
  15
+  <p>To use <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/">Moodle's 
  16
+    CVS archive</a> (as a <a href="http://sourceforge.net/project/memberlist.php?group_id=30935">developer 
  17
+    with write access</a>), you first need to have an <a href="http://sourceforge.net/account/register.php">account 
  18
+    on Sourceforge</a>. For the examples on this page, let's assume your username 
  19
+    is <strong><font color="#990000">myusername</font></strong> and your password 
  20
+    is <strong><font color="#990000">mypassword</font></strong>. Once you have 
  21
+    a Sourceforge account, contact me (<a 
  22
+  href="http://dougiamas.com/">Martin Dougiamas</a>) so I can give you write access 
  23
+    to particular directories.</p>
  24
+  <p>To avoid being prompted for <strong><font color="#990000">mypassword</font></strong> 
  25
+    every time you run a CVS command, follow the <a href="http://sourceforge.net/account/editsshkeys.php">Sourceforge 
  26
+    directions for using authorized keys</a>. This step is optional, but it can 
  27
+    make your CVS experience a lot nicer.</p>
  28
+  <p>With that done, you should have all the permissions you need, so you just 
  29
+    need to set up your machine and download the current sources so you can start 
  30
+    working on them. Below are instructions for Unix and Windows systems.</p>
  31
+  <h3>1. Using CVS on Unix</h3>
  32
+  <blockquote> 
  33
+    <p>Sourceforge CVS uses ssh as a transport layer for security, so you will 
  34
+      have to set this CVS_RSH environment variable in your Unix shell:</p>
  35
+    <blockquote> 
  36
+      <pre><strong>setenv CVS_RSH ssh</strong> (for csh, tcsh etc)</pre>
  37
+      <pre><strong>export CVS_RSH=ssh</strong> (for sh, bash etc)</pre>
  38
+    </blockquote>
  39
+    <p>It's best to put this in your .bashrc or .cshrc so you don't have to type 
  40
+      it all the time. Then, check out Moodle using this (all one line): </p>
  41
+    <blockquote> 
  42
+      <pre><strong>cvs -z3 -d:ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle co moodle</strong></pre>
  43
+    </blockquote>
  44
+    <p>Don't try to do run this first CVS command into an existing moodle directory 
  45
+      - start fresh with a new directory.</p>
  46
+    <p>Note that you will be prompted for <strong><font color="#990000">mypassword</font></strong> 
  47
+      for each command unless you set up <a href="http://sourceforge.net/account/editsshkeys.php">authorized 
  48
+      keys</a></p>
  49
+    <p>Now, you should have a new 'moodle' directory. You can rename it and move 
  50
+      it around if you like. Go into it: </p>
  51
+    <blockquote> 
  52
+      <pre><strong>cd moodle </strong></pre>
  53
+    </blockquote>
  54
+    <p>All the latest Moodle files should be in there. You can now change files 
  55
+      in your copy. To compare your files against the main CVS copy on the server 
  56
+      use cvs diff, eg: </p>
  57
+    <blockquote> 
  58
+      <pre><strong>cvs diff -c config-dist.php
  59
+cvs diff -c lang</strong></pre>
  60
+    </blockquote>
  61
+    <p>To fetch the latest updates from the server use: </p>
  62
+    <blockquote> 
  63
+      <pre><strong>cvs update -dP</strong> </pre>
  64
+    </blockquote>
  65
+    <p>To copy your new files back to the server you would do something like: 
  66
+    </p>
  67
+    <blockquote> 
  68
+      <pre><strong>cd lang/ca 
  69
+cvs commit</strong> </pre>
  70
+    </blockquote>
  71
+    <p>You will be prompted to add some comments (depends on your default text 
  72
+      editor) ... add a meangingful comment and close the editor ... the files 
  73
+      will be sent to Sourceforge and stored. Done! </p>
  74
+    <p>To save more time you can put default arguments into a file called .cvsrc 
  75
+      in your home directory. For example, mine contains: </p>
  76
+    <blockquote> 
  77
+      <pre><strong>diff -c 
  78
+update -dP</strong> </pre>
  79
+    </blockquote>
  80
+    <p>Try 'cvs help' for more details ... </p>
  81
+    <p>&nbsp;</p>
  82
+  </blockquote>
  83
+  <h3>2. Using CVS on Windows</h3>
  84
+  <blockquote> 
  85
+    <p>These instructions are based on notes provided by Mitsuhiro Yoshida &lt;mits@mitstek.com&gt;.</p>
  86
+    <p>Firstly, download and install WinCVS.</p>
  87
+    <blockquote> 
  88
+      <p><a href="https://sourceforge.net/project/showfiles.php?group_id=10072">https://sourceforge.net/project/showfiles.php?group_id=10072</a></p>
  89
+    </blockquote>
  90
+    <p>Secondly, download sfsetup for SourceForge ssh access, install it and reboot 
  91
+      Windows.</p>
  92
+    <blockquote> 
  93
+      <p><a href="http://sourceforge.net/projects/sfsetup/">http://sourceforge.net/projects/sfsetup/</a></p>
  94
+    </blockquote>
  95
+    <p>Next, configure WinCVS. Launch it, and select Admin -&gt; Preferences. 
  96
+      Then change them as follows:</p>
  97
+    <blockquote> 
  98
+      <p> [General]<br>
  99
+        <strong>CVSROOT data</strong>:<br>
  100
+        <strong>Authentication</strong>: ssh<br>
  101
+        <strong>Path</strong>: /cvsroot/moodle<br>
  102
+        <strong>Host address</strong>: cvs.moodle.sourceforge.net<br>
  103
+        <strong>User name</strong>: <font color="#990000">myusername</font><br>
  104
+        <strong>CVSROOT</strong>: <font color="#990000">myusername</font>@cvs.moodle.sourceforge.net:/cvsroot/moodle</p>
  105
+      <p>[Globals]<br>
  106
+        <strong>Checkout read-only</strong>: uncheck<br>
  107
+        <strong>Supply control when adding files</strong>: check<br>
  108
+        <strong>Quiet mode</strong>: uncheck<br>
  109
+        <strong>TCP/IP compression</strong>: check and select 9<br>
  110
+        <strong>Dirty files support</strong>: check<br>
  111
+        <strong>Prune(remove) empty directories</strong>: check<br>
  112
+        <strong>Disable splash screen</strong>: uncheck</p>
  113
+    </blockquote>
  114
+    <p>Congratulations, WinCVS is set up. Now, you should check out a complete 
  115
+      working copy of the Moodle course code:</p>
  116
+    <ol>
  117
+      <li>Select 'Create -&gt; checkout'</li>
  118
+      <li>For the setting 'Module name and path on the server&quot;, type &quot;moodle&quot;, 
  119
+        then click OK.</li>
  120
+      <li>Type in <strong><font color="#990000">mypassword</font></strong> and 
  121
+        press Enter in the DOS window.</li>
  122
+    </ol>
  123
+    <p>After this first checkout, you can fetch updated files from the CVS server 
  124
+      like this:</p>
  125
+    <ol>
  126
+      <li> Select folders or files you want to update</li>
  127
+      <li>Press right mouse button and select '<strong>Update selection</strong>'</li>
  128
+      <li>Press OK button</li>
  129
+      <li>Type in <strong><font color="#990000">mypassword</font></strong> and 
  130
+        press Enter in the DOS window.</li>
  131
+    </ol>
  132
+    <p>After modifying files, you can commit them back to the CVS server like 
  133
+      this:</p>
  134
+    <ol>
  135
+      <li>Select folders or files you want to commit</li>
  136
+      <li>Press right button and select '<strong>Commit selection</strong>'</li>
  137
+      <li>Press OK button</li>
  138
+      <li>Type in a meaningful comment and press OK button.</li>
  139
+      <li>Type in <strong><font color="#990000">mypassword</font></strong> and 
  140
+        press Enter in the DOS window.</li>
  141
+    </ol>
  142
+  </blockquote>
  143
+  <p>&nbsp;</p>
  144
+  <p align="center">Good luck!</p>
  145
+  <p>&nbsp;</p>
  146
+</blockquote>
  147
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
  148
+<p align="CENTER"><font size="1">Version: $Id: features.html,v 1.2 2001/12/09 
  149
+  10:34:19 martin Exp $</font></p>
  150
+</body>
  151
+</html>
286  lang/de/docs/developer.html
... ...
@@ -0,0 +1,286 @@
  1
+<head>
  2
+    <title>Moodle Docs: Developers Manual</title>
  3
+	<link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">
  4
+</head>
  5
+
  6
+<body bgcolor="#FFFFFF">
  7
+<h2>Developers Manual</h2>
  8
+<p>This document describes some of Moodle's design and how you can contribute.</p>
  9
+<p>Sections in this document:</p>
  10
+<ol>
  11
+  <li><a href="#architecture">Moodle architecture</a></li>
  12
+  <li><a href="#contribute">How you can contribute</a> 
  13
+    <ul>
  14
+      <li><a href="#activities">Learning activities</a></li>
  15
+      <li><a href="#themes">Themes</a></li>
  16
+      <li><a href="#languages">Languages</a></li>
  17
+      <li><a href="#database">Database Schemas</a></li>
  18
+      <li><a href="#courseformats">Course formats</a></li>
  19
+      <li><a href="#doc">Documentation and articles</a></li>
  20
+      <li><a href="#bugs">Participating in the bug tracker</a></li>
  21
+    </ul>
  22
+  </li>
  23
+</ol>
  24
+<p>&nbsp;</p>
  25
+<h3><a name="architecture"></a>1. Moodle architecture</h3>
  26
+<p>From a system administrator's perspective, Moodle has been designed according 
  27
+  to the following criteria:</p>
  28
+<ol>
  29
+  <li><strong>Moodle should run on the widest variety of platforms</strong><br>
  30
+    <br>
  31
+    The web application platform that runs on most platforms is PHP combined with 
  32
+    MySQL, and this is the environment that Moodle has been developed in (on Linux, 
  33
+    Windows, and Mac OS X). Moodle also uses the ADOdb library for database abstraction, 
  34
+    which means Moodle can use <a href="http://php.weblogs.com/ADOdb_manual#drivers">more 
  35
+    than ten different brands of database</a> (unfortunately, though, it can not 
  36
+    yet <em><strong>set up tables</strong></em> in all these databases - more 
  37
+    on this later). <br><br>
  38
+  </li>
  39
+  <li><strong>Moodle should be easy to install, learn and modify</strong><br>
  40
+    <br>
  41
+    Early prototypes of Moodle (1999) were built using <a target=_top href="http://www.zope.org/">Zope</a> 
  42
+    - an advanced object-oriented web application server. Unfortunately I found 
  43
+    that although the technology was pretty cool, it had a very steep learning 
  44
+    curve and was not very flexible in terms of system administration. The PHP 
  45
+    scripting language, on the other hand, is very easy to get into (especially 
  46
+    if you've done any programming using any other scripting language). Early 
  47
+    on I made the decision to avoid using a class-oriented design - again, to 
  48
+    keep it simple to understand for novices. Code reuse is instead achieved by 
  49
+    libraries of clearly-named functions and consistent layout of script files. 
  50
+    PHP is also easy to install (binaries are available for every platform) and 
  51
+    is widely available to the point that most web hosting services provide it 
  52
+    as standard.<br><br>
  53
+  </li>
  54
+  <li><strong>It should be easy to upgrade from one version to the next</strong><br>
  55
+    <br>
  56
+    Moodle knows what version it is (as well as the versions of all plug-in modules) 
  57
+    and a mechanism has been built-in so that Moodle can properly upgrade itself 
  58
+    to new versions (for example it can rename database tables or add new fields). 
  59
+    If using CVS in Unix for example, one can just do a &quot;cvs update -d&quot; 
  60
+    and then visit the site home page to complete an upgrade.<br><br>
  61
+  </li>
  62
+  <li><strong>It should be modular to allow for growth</strong><br>
  63
+    <br>
  64
+    Moodle has a number of features that are modular, including themes, activities, 
  65
+    interface languages, database schemas and course formats. This allows anyone 
  66
+    to add features to the main codebase or to even distribute them separately. 
  67
+    More on this below in the next section.<br><br>
  68
+  </li>
  69
+  <li><strong>It should be able to be used in conjunction with other systems</strong><br>
  70
+    <br>
  71
+    One thing Moodle does is keep all files for one course within a single, normal 
  72
+    directory on the server. This would allow a system administrator to provide 
  73
+    seamless forms of file-level access for each teacher, such as Appletalk, SMB, 
  74
+    NFS, FTP, WebDAV and so on.  The authentication modules allow Moodle to use 
  75
+    LDAP, IMAP, POP3, NNTP and other databases as sources for user information.
  76
+    Otherwise, there is work yet to do. Features planned 
  77
+    for Moodle in future versions include: import and export of Moodle data using XML-based 
  78
+    formats (including IMS and SCORM); and increased use of style sheets for 
  79
+    interface formatting (so that it can be integrated visually into other web sites).</li>
  80
+</ol>
  81
+<p>&nbsp;</p>
  82
+<h3><a name="contribute" id="contribute"></a>2. How you can contribute</h3>
  83
+<p>As mentioned above, Moodle has a number of features that are modular. Even 
  84
+  if you are not a programmer there are things you can change or help with.</p>
  85
+<p><strong><a name="activities" id="activities"></a>Learning Activities</strong></p>
  86
+<blockquote> 
  87
+  <p>These are by far the most important modules, and reside in the 'mod' directory. 
  88
+    There are seven default modules: assignment, choice, forum, journal, quiz, 
  89
+    resource, and survey. Each module is in a separate subdirectory and consists 
  90
+    of the following mandatory elements (plus extra scripts unique to each module):</p>
  91
+  <ul>
  92
+    <li>mod.html: a form to set up or update an instance of this module</li>
  93
+    <li>version.php: defines some meta-info and provides upgrading code</li>
  94
+    <li>icon.gif: a 16x16 icon for the module</li>
  95
+    <li>db/: SQL dumps of all the required db tables and data (for each database 
  96
+      type) </li>
  97
+    <li>index.php: a page to list all instances in a course</li>
  98
+    <li>view.php: a page to view a particular instance</li>
  99
+    <li>lib.php: any/all functions defined by the module should be in here. If 
  100
+      the modulename if called widget, then the required functions include: 
  101
+      <ul>
  102
+        <li>widget_add_instance() - code to add a new instance of widget</li>
  103
+        <li>widget_update_instance() - code to update an existing instance</li>
  104
+        <li>widget_delete_instance() - code to delete an instance</li>
  105
+        <li>widget_user_outline() - given an instance, return a summary of a user's 
  106
+          contribution</li>
  107
+        <li>widget_user_complete() - given an instance, print details of a user's 
  108
+          contribution<br>
  109
+        </li>
  110
+        <li>To avoid possible conflict, any module functions should be named starting 
  111
+          with widget_ and any constants you define should start with WIDGET_ 
  112
+        </li>
  113
+      </ul>
  114
+    </li>
  115
+    <li>Lastly, each module will have some language files that contain strings 
  116
+      for that module. See below.</li>
  117
+  </ul>
  118
+  <p>The easiest way to start a new learning activity module is to use the template 
  119
+    in <strong><a href="http://moodle.com/mod/newmodule_template.zip">mod/newmodule_template.zip</a>.</strong> 
  120
+    Unzip it and follow the README inside. </p>
  121
+  <p>You might also like to post first in the <a href="http://moodle.com/mod/forum/view.php?id=44" target="_top">Activities 
  122
+    modules forum on Using Moodle</a>.</p>
  123
+  <p>&nbsp;</p>
  124
+</blockquote>
  125
+<p> <strong><a name="themes" id="themes"></a>Themes</strong></p>
  126
+<blockquote> 
  127
+  <p>Themes (or skins) define the look of a site. A number of simple themes are 
  128
+    provided in the main distribution, but you may want to create your own theme
  129
+    with your own colours, logo, styles and graphics.
  130
+
  131
+  <p>Each theme is in a subdirectory of the &quot;theme&quot; directory, and contains 
  132
+     at least the following files:</p>
  133
+  <ul>
  134
+    <li><strong>config.php</strong>: defines the theme colours used throughout 
  135
+      the site</li>
  136
+    <li><strong>styles.php</strong>: the style sheet, containing CSS definitions 
  137
+      for standard HTML elements as well as many Moodle elements.</li>
  138
+    <li><strong>header.html</strong>: Included at the top of each page. This is 
  139
+      what you need to edit to add a logo at the top of pages, for example.</li>
  140
+    <li><strong>footer.html</strong>: Included at the bottom of each page.</li>
  141
+  </ul>
  142
+  <p>To create your own themes for current versions of Moodle:</p>
  143
+  <ol>
  144
+    <li>Copy one of the existing theme folders to one with a new name.  I recommend
  145
+        starting with one of the standard themes.
  146
+    <li>Edit config.php and insert your own colours.
  147
+    <li>Edit styles.php and change your CSS styles.
  148
+    <li>Edit header.html and footer.html to add new logos, or change the layout.
  149
+  </ol>
  150
+  <p>Note that all these steps are optional - you can make a radically different
  151
+    look to your site simply by editing the colours in config.php</p>
  152
+  <p>Note also that Moodle upgrades <em>may</em> break themes slightly, so check the 
  153
+    release notes carefully if you are using a custom theme.</p>
  154
+  <p>In particular, Moodle 2.0 will have a completely new display system, probably based on
  155
+    XSL transformations of XML output from Moodle. It is likely that the 
  156
+    themes for this will be a completely different format, but the advantage will 
  157
+    be a much higher possible degree of customisation (including moving elements 
  158
+    around the page).</p>
  159
+  <p>More discussion about this in the <a target=_top href="http://moodle.com/mod/forum/view.php?id=46">Themes 
  160
+    forum on Using Moodle</a>.  If you create a nice theme that you think others
  161
+    might want to use, please post your zip file on the themes forum!<br>
  162
+  </p>
  163
+</blockquote>
  164
+
  165
+  <p>&nbsp;</p>
  166
+
  167
+<p><strong><a name="languages" id="languages"></a>Languages</strong></p>
  168
+<blockquote> 
  169
+  <p>Moodle has been designed for internationalisation. Each 'string' or 'page' 
  170
+    of text that is displayed as part of the interface is drawn from a set of 
  171
+    language files. Each language is a subdirectory of the directory 'lang'. The 
  172
+    structure of the lang directory is as follows:</p>
  173
+  <p><strong>lang/en</strong> - directory containing all files for one language 
  174
+    (eg English)</p>
  175
+  <ul>
  176
+    <li>moodle.php - strings for main interface</li>
  177
+    <li>assignment.php - strings for assignment module</li>
  178
+    <li>choice.php - strings for choice module</li>
  179
+    <li>forum.php - strings for forum module</li>
  180
+    <li>journal.php - strings for journal module </li>
  181
+    <li>quiz.php - strings for quiz module</li>
  182
+    <li>resource.php - strings for resource module</li>
  183
+    <li>survey.php - strings for survey module</li>
  184
+    <li>.... plus other modules if any.<br>
  185
+      <br>
  186
+      A string is called from these files using the <strong><em>get_string()</em></strong><em> 
  187
+      </em>or<em> <strong>print_string()</strong> </em>functions. Each string 
  188
+      supports variable substitution, to support variable ordering in different 
  189
+      languages.<em><br>
  190
+      <br>
  191
+      </em>eg $strdueby = get_string(&quot;assignmentdueby&quot;, &quot;assignment&quot;, 
  192
+      userdate($date)); <br>
  193
+      <br>
  194
+      If a string doesn't exist in a particular language, then the equivalent 
  195
+      in English will automatically be used instead.</li>
  196
+  </ul>
  197
+  <p><strong>lang/en/help</strong> - contains whole help pages (for popup context-sensitive 
  198
+    help)</p>
  199
+  <blockquote> 
  200
+    <p>Main help pages are situated here, while help pages specific to each module 
  201
+      are located in subdirectories with the module's name.</p>
  202
+    <p>You can insert a helpbutton in a page with the helpbutton function.</p>
  203
+    <p>eg helpbutton(&quot;text&quot;, &quot;Click here for help about text&quot;);</p>
  204
+    <p>and for modules:</p>
  205
+    <p>helpbutton(&quot;forumtypes&quot;, &quot;Forum types&quot;, &quot;forum&quot;);</p>
  206
+  </blockquote>
  207
+  <p>Note that you can edit languages online, using the administration web tools 
  208
+    under &quot;Check this language&quot;. This makes it easy to not to only create 
  209
+    new languages but to refine existing ones. If you are starting a new language, 
  210
+    please contact me, <a target=_top href="http://dougiamas.com/">Martin Dougiamas</a>. </p>
  211
+  <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 
  212
+    forum on Using Moodle</a>. </p>
  213
+  <p>If you are maintaining a language an ongoing basis, I can give you <a href="?file=cvs.html">CVS 
  214
+    write access to the Moodle source code</a> so that you can directly maintain 
  215
+    the files.</p>
  216
+</blockquote>
  217
+<p><br>
  218
+  <strong><a name="database" id="database"></a>Database Schemas</strong></p>
  219
+<blockquote> 
  220
+  <p>Given a working database with defined tables, the intentionally simple SQL 
  221
+    used in Moodle should work fine with a wide variety of database brands.</p>
  222
+
  223
+  <p>A problem exists with <strong>automatically creating</strong> new tables 
  224
+    in a database, which is what Moodle tries to do upon initial installation. 
  225
+    Because every database is very different, there doesn't yet exist any way 
  226
+    to do this in a platform-independent way. To support this automation in each 
  227
+    database, schemas can be created that list the required SQL to create Moodle 
  228
+    tables in a particular database. These are files in <strong>lib/db</strong> 
  229
+    and inside the <strong>db</strong> subdirectory of each module.</p>
  230
+
  231
+  <p>Currently, only MySQL and PostgreSQL are fully supported in this way. If you are 
  232
+    familiar with another database (especially open source databases) and are 
  233
+    willing to help port the existing schema, please get in contact with me (<a target=_top href="http://dougiamas.com/">Martin 
  234
+    Dougiamas</a>).</p>
  235
+</blockquote>
  236
+<p>&nbsp;</p>
  237
+<p><strong><a name="courseformats" id="courseformats"></a>Course Formats</strong></p>
  238
+<blockquote> 
  239
+  <p>Moodle currently supports three different course formats: weekly, topics and social. 
  240
+  </p>
  241
+  <p>These are a little more connected to the rest of the code (and hence, less 
  242
+    &quot;pluggable&quot;) but it is still quite easy to add new ones.</p>
  243
+  <p>If you have any ideas for different formats that you need or would like to 
  244
+    see, get in touch with me and I'll do my absolute best to have them available 
  245
+    in future releases.</p>
  246
+</blockquote>
  247
+<p>&nbsp;</p>
  248
+<p><strong><a name="doc" id="doc"></a>Documentation and articles</strong></p>
  249
+<blockquote> 
  250
+  <p>If you feel like writing a tutorial, an article, an academic paper or anything 
  251
+    else about Moodle, please do! </p>
  252
+  <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>
  253
+  </blockquote>
  254
+<p>&nbsp;</p>
  255
+<p><strong><a name="bugs" id="bugs"></a>Participating in the bug tracker</strong></p>
  256
+<blockquote> 
  257
+  <p>Finally, I would like to invite you to register on the &quot;bug tracker&quot; 
  258
+    at <a target=_top href="http://bugs.moodle.org">bugs.moodle.org</a> so you can file any 
  259
+    bugs that you find and perhaps participate in discussing and fixing them. 
  260
+  </p>
  261
+  <p>&quot;Bugs&quot; not only includes software bugs with current versions of 
  262
+    Moodle, but also new ideas, feature requests and even constructive criticism 
  263
+    of existing features. The beauty of open source is that anyone can participate 
  264
+    in some way and help to create a better product for all of us to enjoy. In 
  265
+    this project, your input is very welcome!</p>
  266
+</blockquote>
  267
+<p>&nbsp;</p>
  268
+<blockquote> 
  269
+  <blockquote> 
  270
+    <blockquote> 
  271
+      <p align="center">Thanks for using Moodle!</p>
  272
+      <p align="center">Cheers,<br>
  273
+        <a target=_top href="http://dougiamas.com/" target="_top">Martin Dougiamas</a></p>
  274
+    </blockquote>
  275
+  </blockquote>
  276
+</blockquote>
  277
+<p>&nbsp;</p>
  278
+<p>&nbsp;</p>
  279
+<blockquote> 
  280
+  <p>&nbsp;</p>
  281
+</blockquote>
  282
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
  283
+<p align="CENTER"><font size="1">Version: $Id: developer.html,v 1.2 2001/12/09 
  284
+  10:34:19 martin Exp $</font></p>
  285
+
  286
+</body>
160  lang/de/docs/features.html
... ...
@@ -0,0 +1,160 @@
  1
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  2
+<HTML>
  3
+<HEAD>
  4
+  <TITLE>Moodle Docs: Background</TITLE>
  5
+  <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
  6
+</HEAD>
  7
+<BODY BGCOLOR="#ffffff">
  8
+  
  9
+<H2>Features</H2>
  10
+<p>Moodle is an active and evolving product. This page lists some of the many 
  11
+  features it contains:</p>
  12
+<p><strong>Overall design</strong></p>
  13
+<UL>
  14
+  <LI>Promotes a social constructionist pedagogy (collaboration, activities, critical 
  15
+    reflection, etc)</LI>
  16
+  <LI>Suitable for 100% online classes as well as supplementing face-to-face learning 
  17
+  <LI>Simple, lightweight, efficient, compatible, low-tech browser interface</LI>
  18
+  <LI>Easy to install on almost any platform that supports PHP. Requires only 
  19
+    one database.</LI>
  20
+  <LI>Full database abstraction supports all major brands of database (except 
  21
+    for initial table definition)</LI>
  22
+  <LI>Course listing shows descriptions for every course on the server, including 
  23
+    accessibility to guests.</LI>
  24
+  <LI>Emphasis on strong security throughout. Forms are all checked, data validated, 
  25
+    cookies encrypted etc</LI>
  26
+</UL>
  27
+<p><strong>Site management</strong></p>
  28
+<UL>
  29
+  <LI>Site is managed by an admin user, defined during setup</LI>
  30
+  <LI>Plug-in "themes" allow the admin to customise the site colours, fonts, layout 
  31
+    etc to suit local needs</LI>
  32
+  <LI>Plug-in activity modules can be added to existing Moodle installations</LI>
  33
+  <LI>Plug-in language packs allow full localisation to any language. These can 
  34
+    be edited using a built-in web-based editor.  Currently there are language packs
  35
+    for more than <A HREF="http://moodle.com/download/lang/" TARGET="_top">19 languages</A>.</LI>
  36
+  <LI>The code is clearly-written PHP under a GPL license - easy to modify to 
  37
+    suit your needs</LI>
  38
+</UL>
  39
+<p><strong>User management</strong></p>
  40
+<UL>
  41
+  <LI>Goals are to reduce admin involvement to a minimum, while retaining high 
  42
+    security</LI>
  43
+  <LI>Supports a range of authentication mechanisms through plug-in authentication 
  44
+    modules, allowing easy integration with existing systems.</LI>
  45
+  <LI>Standard email method: students can create their own login accounts. Email 
  46
+    addresses are verified by confirmation.</LI>
  47
+  <LI>LDAP method: account logins can be checked against an LDAP server. Admin 
  48
+    can specify which fields to use.</LI>
  49
+  <LI>IMAP, POP3, NNTP: account logins are checked against a mail or news server. 
  50
+    SSL, certificates and TLS are supported.</LI>
  51
+  <LI>External database: any database containing at least two fields can be used 
  52
+    as an external authentication source.</LI>
  53
+  <LI>Each person requires only one account for the whole server - each account 
  54
+    can have different access</LI>
  55
+  <LI>An admin account controls the creation of courses and creates teachers by 
  56
+    assigning users to courses</LI>
  57
+  <LI>Security - teachers can add an "enrolment key" to their courses to keep 
  58
+    out non-students. They can give out this key face-to-face or via personal 
  59
+    email etc</LI>
  60
+  <LI>Teachers can unenrol students manually if desired, otherwise they are automatically 
  61
+    unenrolled after a certain period of inactivity (set by the admin)</LI>
  62
+  <LI>Students are encouraged to build an online profile including photos, description. 
  63
+    Email addresses can be protected from display if required.</LI>
  64
+  <LI>Every user can specify their own timezone, and every date in Moodle is translated 
  65
+    to that timezone (eg posting dates, assignment due dates etc)</LI>
  66
+  <LI>Every user can choose the language used for the Moodle interface (English, 
  67
+    French, German, Spanish, Portuguese etc)</LI>
  68
+</UL>
  69
+<p><strong>Course management</strong></p>
  70
+<UL>
  71
+  <LI>Teacher has full control over all settings for a course</LI>
  72
+  <LI>Choice of course formats such as by week, by topic or a discussion-focussed 
  73
+    social format</LI>
  74
+  <LI>Flexible array of course activities - Forums, Journals, Quizzes, Resources, 
  75
+    Choices, Surveys, Assignments.</LI>
  76
+  <LI>Recent changes to the course since the last login can be displayed on the 
  77
+    course home page - helps give sense of community</LI>
  78
+  <LI>Most text entry areas (resources, forum postings, journal entries etc) can 
  79
+    be edited using an embedded WYSIWYG HTML editor</LI>
  80
+  <LI>All grades for Forums, Journals, Quizzes and Assignments can be viewed on 
  81
+    one page (and downloaded as a spreadsheet file)</LI>
  82
+  <LI>Full user logging and tracking - activity reports for each student are available 
  83
+    with graphs and details about each module (last access, number of times read) 
  84
+    as well as a detailed "story" of each students involvement including postings, 
  85
+    journal entries etc on one page.</LI>
  86
+  <LI>Mail integration - copies of forum posts, teacher feedback etc can be mailed 
  87
+    in HTML or plain text.</LI>
  88
+</UL>
  89
+<B>Assignment Module</B> 
  90
+<UL>
  91
+  <LI>Assignments can be specified with a due date and a maximum grade.</LI>
  92
+  <LI>Students can upload their assignments (any file format) to the server - 
  93
+    they are date-stamped.</LI>
  94
+  <LI>Late assignments are allowed, but the amount of lateness is shown clearly 
  95
+    to the teacher</LI>
  96
+  <LI>For each particular assignment, the whole class can be assessed (grade and 
  97
+    comment) on one page in one form.</LI>
  98
+  <LI>Teacher feedback is appended to the assignment page for each student, and 
  99
+    notification is mailed out.</LI>
  100
+  <LI>The teacher can choose to allow resubmission of assignments after grading 
  101
+    (for regrading)</LI>
  102
+</UL>
  103
+<P><B>Choice Module</B> </P>
  104
+<UL>
  105
+  <LI>Like a poll. Can either be used to vote on something, or to get feedback 
  106
+    from every student (eg research consent)</LI>
  107
+  <LI>Teacher sees intuitive table view of who chose what</LI>
  108
+</UL>
  109
+<P><B>Forum Module</B> </P>
  110
+<UL>
  111
+  <LI>Different types of forums are available, such as teacher-only, course news, 
  112
+    open-to-all, and one-thread-per-user.</LI>
  113
+  <LI>All postings have the authors photo attached.</LI>
  114
+  <LI>Discussions can be viewed nested, flat or threaded, oldest or newest first.</LI>
  115
+  <LI>Individual forums can be subscribed to by each person so that copies are 
  116
+    forwarded via email, or the teacher can force subscription for all</LI>
  117
+  <LI>The teacher can choose not to allow replies (eg for an announcements-only 
  118
+    forum)</LI>
  119
+</UL>
  120
+<B>Journal Module</B> 
  121
+<UL>
  122
+  <LI>Journals are private between student and teacher.</LI>
  123
+  <LI>Each journal entry can be directed by an open question.</LI>
  124
+  <LI>For each particular journal entry, the whole class can be assessed on one 
  125
+    page in one form</LI>
  126
+  <LI>Teacher feedback is appended to the journal entry page, and notification 
  127
+    is mailed out.</LI>
  128
+</UL>
  129
+<P><B>Quiz Module</B> </P>
  130
+<UL>
  131
+  <LI>Teachers can define a database of questions for re-use in different quizzes</LI>
  132
+  <LI>Quizzes are automatically graded, and can be re-graded if questions are 
  133
+    modified </LI>
  134
+  <LI>Quizzes can have a limited time window outside of which they are not available</LI>
  135
+  <LI>At the teacher's option, quizzes can be attempted multiple times, and can 
  136
+    show feedback and/or correct answers</LI>
  137
+  <LI>Questions allow HTML and images</LI>
  138
+  <LI>Multiple-choice questions supporting single or multiple answers</LI>
  139
+  <LI>Short Answer questions (words or phrases)</LI>
  140
+  <LI>True-False questions </LI>
  141
+</UL>
  142
+<P><B>Resource Module</B> </P>
  143
+<UL>
  144
+  <LI>Supports display of any electronic content</LI>
  145
+  <LI>Files can be uploaded and managed on the server, or created on the fly using 
  146
+    web forms (text or HTML)</LI>
  147
+  <LI>External content on the web can be linked to or seamlessly included within 
  148
+    the course interface.</LI>
  149
+</UL>
  150
+<B>Survey Module</B> 
  151
+<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>
  152
+
  153
+<P>&nbsp;</P>
  154
+
  155
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
  156
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id: features.html,v 1.2 2001/12/09 
  157
+  10:34:19 martin Exp $</FONT></P>
  158
+
  159
+</BODY>
  160
+</HTML>
45  lang/de/docs/future.html
... ...
@@ -0,0 +1,45 @@
  1
+<HEAD>
  2
+    <TITLE>Moodle Docs: Future</TITLE>
  3
+	<LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
  4
+</HEAD>
  5
+
  6
+<BODY BGCOLOR="#FFFFFF">
  7
+
  8
+<H2>Future</H2>
  9
+<P>I'm committed to continuing my work on Moodle and on keeping it Open and Free. 
  10
+  I have a deeply-held belief in the importance of unrestricted education and 
  11
+  empowered teaching, and Moodle is the main way I can contribute to the realisation 
  12
+  of these ideals. 
  13
+
  14
+<P>As Moodle gains in maturity, I hope its directions are influenced by the community 
  15
+  of developers and users. A dynamic database of proposed features and their status 
  16
+  can be found at <A TARGET=_top HREF="http://bugs.moodle.org/">bugs.moodle.org</A>. 
  17
+  Your <A href="developer.html">contributions</a> in the form of ideas, code, 
  18
+  feedback and promotion are all very welcome. 
  19
+
  20
+<P>Until about April 2003, my own involvement will slow down while I finish my PhD thesis.
  21
+   During this time there will still be releases, but they will only contain minor 
  22
+   new features and bug fixes.  I will also be including modules and other code contributed 
  23
+   by others.
  24
+
  25
+<P>After this time, by around June/July 2003, I am expecting a major release called Moodle 2.0
  26
+   that will include major new features such as:
  27
+   <UL>
  28
+   <LI>Stronger pedagogical support for both teachers and students
  29
+   <LI>Support for groups and group work
  30
+   <LI>Rewritten display incorporating XML, XSL and CSS for full flexibility 
  31
+       and compatibility with all modern web standards.
  32
+   <LI>Basic support for IMS and SCORM
  33
+   <LI>A variety of new modules (chat, tracker etc)
  34
+   <LI>Whatever else seems most important at the time  :-)
  35
+   </UL>
  36
+
  37
+<P>About this time I will also be experimenting with ways of making 
  38
+   Moodle development more sustainable for the long term.  This may 
  39
+   include offering services for payment - although the software itself 
  40
+   will always remain Free.
  41
+   
  42
+<P ALIGN="CENTER">&nbsp;</P>
  43
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>
  44
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
  45
+</BODY>
385  lang/de/docs/install.html
... ...
@@ -0,0 +1,385 @@
  1
+<HEAD>
  2
+    <TITLE>Moodle Docs: Installation</TITLE>
  3
+	<LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
  4
+</HEAD>
  5
+
  6
+<BODY BGCOLOR="#FFFFFF">
  7
+<H2>Installing Moodle</H2>
  8
+<P>This guide explains how to install Moodle for the first time.  It goes into some detail
  9
+   about some of the steps, in order to cover the wide variety of small differences between
  10
+   web server setups, so this document may look long and complicated.  Don't be put off by this 
  11
+   - I usually set Moodle up in a few minutes!</P>
  12
+<P>Take your time and work through this document carefully - it will save you time later on.</P>
  13
+<P>Sections in this document:</P>
  14
+<OL>
  15
+  <LI><A HREF="#requirements">Requirements</A></LI>
  16
+  <LI><A HREF="#downloading">Download</A></LI>
  17
+  <LI><A HREF="#site">Site structure</A></LI>
  18
+  <LI><A HREF="#data">Create a data directory</A></LI>
  19
+  <LI><A HREF="#database">Create a database</A></LI>
  20
+  <LI><A HREF="#webserver">Check web server settings</A></LI>
  21
+  <LI><A HREF="#config">Edit config.php</A></LI>
  22
+  <LI><A HREF="#admin">Go to the admin page</A></LI>
  23
+  <LI><A HREF="#cron">Set up cron</A></LI>
  24
+  <LI><A HREF="#course">Create a new course</A></LI>
  25
+</OL>
  26
+<H3><A NAME="requirements"></A>1. Requirements</H3>
  27
+<blockquote>
  28
+  <p>Moodle is primarily developed in Linux using PHP, Apache and MySQL, and regularly 
  29
+    tested with PostgreSQL and in Windows XP and Mac OS X environments.</p>
  30
+  <p>All you should need are:</p>
  31
+  <ol>
  32
+    <li>a working installation of <A HREF="http://www.php.net/">PHP</A> (version 
  33
+      4.1.0 or later), with the following features enabled (most PHP installations 
  34
+      these days will have all of these):
  35
+      <ul>
  36
+      <LI><A HREF="http://www.boutell.com/gd/">GD library</A> with support for JPG and PNG formats</li>
  37
+      <LI>Sessions support</LI>
  38
+      <LI>File uploading allowed</LI>
  39
+      </UL>
  40
+</LI>
  41
+    <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>
  42
+  </ol>
  43
+  <p>On a Windows platform, the quickest way to satisfy these requirements is 
  44
+    to download <A HREF="http://www.foxserv.net/">FoxServ</A>, 
  45
+    or <A HREF="http://www.easyphp.org/">EasyPHP</A> which will install Apache, 
  46
+    PHP, and MySQL for you. Make sure you enable the GD module so Moodle can process 
  47
+    images - you may have to edit php.ini and remove the comment (;) from this 
  48
+    line: 'extension=php_gd.dll'. You may also have to fix the directory for 
  49
+    session.save_path - instead of the default "/tmp" use a Windows directory 
  50
+    like "c:/temp".</p>
  51
+
  52
+  <p>On Mac OS X I highly recommend the <a href="http://fink.sourceforge.net/">fink</a> 
  53
+    project as a way to download easily-maintainable packages for all of this.  If you are less
  54
+    confident with command-line stuff then <A HREF="http://www.entropy.ch/software/macosx/php/">Marc Liyanage's PHP Apache Module</A> is the easiest way to get PHP up and running on a new Mac OS X server.</p>
  55
+
  56
+  <p>If you're on Linux or another Unix then I'll assume you can figure all this out for yourself! ;-) </p>
  57
+
  58
+</blockquote>
  59
+<P>&nbsp;</P>
  60
+<H3><A NAME="downloading"></A>2. Download</H3>
  61
+<blockquote>
  62
+  <p>There are two ways to get Moodle, as a compressed package and via CVS. These 
  63
+    are explained in detail on the download page on <A HREF="http://moodle.com/">http://moodle.com/</A></p>
  64
+  <p>After downloading and unpacking the archive, or checking out the files via 
  65
+    CVS, you will be left with a directory called &quot;moodle&quot;, containing 
  66
+    a number of files and folders. </p>
  67
+  <p>You can either place the whole folder in your web server documents directory, 
  68
+    in which case the site will be located at <B>http://yourwebserver.com/moodle</B>, 
  69
+    or you can copy all the contents straight into the main web server documents 
  70
+    directory, in which case the site will be simply <B>http://yourwebserver.com</B>.</p>
  71
+</blockquote>
  72
+<P>&nbsp;</P>
  73
+<H3><A NAME="site"></A>3. Site structure</H3>
  74
+<BLOCKQUOTE>
  75
+  <p>Here is a quick summary of the contents of the Moodle folder, to help get 
  76
+    you oriented:</p>
  77
+  <blockquote>
  78
+    <p>config.php - the only file you need to edit to get started<br>
  79
+      version.php - defines the current version of Moodle code<BR>
  80
+      index.php - the front page of the site</p>
  81
+    <ul>
  82
+      <li>admin/ - code to administrate the whole server </li>
  83
+      <li>auth/ - plugin modules to authenticate users  </li>
  84
+      <li>course/ - code to display and manage courses </li>
  85
+      <li>doc/ - help documentation for Moodle (eg this page)</li>
  86
+      <li>files/ - code to display and manage uploaded files</li>
  87
+      <li>lang/ - texts in different languages, one directory per language </li>
  88
+      <li>lib/ - libraries of core Moodle code </li>
  89
+      <li>login/ - code to handle login and account creation </li>
  90
+      <li>mod/ - all Moodle course modules</li>
  91
+      <li>pix/ - generic site graphics</li>
  92
+      <li>theme/ - theme packs/skins to change the look of the site.</li>
  93
+      <li>user/ - code to display and manage users</li>
  94
+    </ul>
  95
+    <p>&nbsp;</p>
  96
+  </blockquote>
  97
+</BLOCKQUOTE>
  98
+<H3><A NAME="data"></A>4. Create a data directory</H3>
  99
+<blockquote>
  100
+  <p>Moodle will also need some space on your hard disk to store uploaded files, 
  101
+    such as course documents and user pictures.</p>
  102
+
  103
+  <p>Create a directory for this purpose somewhere.  For security, it's best that 
  104
+     this directory is NOT accessible directly via the web.  The easiest way to do this
  105
+     is to simply locate it OUTSIDE the web directory, otherwise protect it 
  106
+     by creating a file in the data directory called .htaccess, containing this line:
  107
+  <blockquote>
  108
+     <PRE>deny from all</PRE>
  109
+  </blockquote>
  110
+  
  111
+  <p>To make sure that Moodle can save uploaded files in this directory, check that 
  112
+     the web server software (eg Apache) has permission to write 
  113
+    to this directory. On Unix machines, this means setting the owner of the directory 
  114
+    to be something like &quot;nobody&quot; or &quot;apache&quot;.</p>
  115
+
  116
+  <p>On many shared hosting servers, you will probably need to restrict all file access 
  117
+     to your "group" (to prevent other webhost customers from looking at or changing your files), 
  118
+     but provide full read/write access to everyone else (which will allow the web server
  119
+     to access your files).  Speak to your server administrator if you are having 
  120
+     trouble setting this up securely.</p>
  121
+
  122
+</blockquote>
  123
+<P>&nbsp;</P>
  124
+<H3><A NAME="database"></A>5. Create a database</H3>
  125
+<blockquote>
  126
+<p>You need to create an empty database (eg "moodle") in your database system 
  127
+    along with a special user (eg "moodleuser") that has access to that database 
  128
+    (and that database only). You could use the "root" user if you wanted to, but 
  129
+    this is not recommended for a production system: if hackers manage to discover
  130
+    the password then your whole database system would be at risk, rather than 
  131
+    just one database.
  132
+</p>
  133
+  <p>Example command lines for MySQL: </p>
  134
+  <PRE>
  135
+   # mysql -u root -p
  136
+   > CREATE DATABASE moodle; 
  137
+   > GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,INDEX,ALTER ON moodle.* 
  138
+           TO moodleuser@localhost IDENTIFIED BY 'yourpassword'; 
  139
+   > quit 
  140
+   # mysqladmin -p reload
  141
+</PRE>
  142
+  <p>Example command lines for PostgreSQL: </p>
  143
+  <PRE>
  144
+   # su - postgres
  145
+   > psql -c "create user moodleuser createdb;" template1
  146
+   > psql -c "create database moodle;" -U moodleuser template1
  147
+   > psql -c "alter user moodleuser nocreatedb;" template1
  148
+</PRE>
  149
+  <p>(For MySQL I highly recommend the use of <a href="http://phpmyadmin.sourceforge.net/">phpMyAdmin</a> 
  150
+    to manage your databases).</p>
  151
+<p>As of version 1.0.8, Moodle now supports table prefixes, and so can safely share 
  152
+   a database with tables from other applications.</p>
  153
+</blockquote>
  154
+<P>&nbsp;</P>
  155
+<H3><A NAME="webserver" id="webserver"></A>6. Check your web server settings</H3>
  156
+<blockquote>
  157
+  <p>Firstly, make sure that your web server is set up to use index.php as a default 
  158
+    page (perhaps in addition to index.html, default.htm and so on).</p>
  159
+  <p>In Apache, this is done using a DirectoryIndex parameter in your httpd.conf 
  160
+    file. Mine usually looks like this:</p>
  161
+  <blockquote>
  162
+    <pre><strong>DirectoryIndex</strong> index.php index.html index.htm </pre>
  163
+  </blockquote>
  164
+  <p>Just make sure index.php is in the list (and preferably towards the start 
  165
+    of the list, for efficiency).</p>
  166
+  <p>Secondly, Moodle requires a number of PHP settings to be active for it to 
  167
+     work.  <B>On most servers these will already be the default settings.</B>
  168
+     However, some PHP servers (and some of the more recent PHP versions) may 
  169
+     have things set differently.  These are defined in PHP's configuration
  170
+     file (usually called php.ini):</p>
  171
+  <blockquote>
  172
+<pre>file_uploads = 1
  173
+magic_quotes_gpc = 1
  174
+short_open_tag = 1
  175
+session.auto_start = 0
  176
+</pre>
  177
+  </blockquote>
  178
+  <p>If you don't have access to httpd.conf or php.ini on your server, or you 
  179
+     have Moodle on a server with other applications that require different 
  180
+     settings, then you can OVERRIDE all of the default settings.
  181
+     
  182
+  <p>To do this, you need to create a file called <B>.htaccess</B> in Moodle's
  183
+     main directory that contains definitions for these settings.
  184
+     This only works on Apache servers and only when Overrides have been allowed.
  185
+     <BLOCKQUOTE><PRE>
  186
+DirectoryIndex index.php index.html index.htm
  187
+php_value magic_quotes_gpc 1
  188
+php_value file_uploads 1
  189
+php_value short_open_tag 1
  190
+php_value session.auto_start 0</BLOCKQUOTE></PRE>
  191
+     <P>You can also do things like define the maximum size for uploaded files:
  192
+     <BLOCKQUOTE><PRE>
  193
+php_value upload_max_filesize 2M
  194
+php_value post_max_size 2M
  195
+     </BLOCKQUOTE></PRE>
  196
+
  197
+  <p>The easiest thing to do is just copy the sample file from lib/htaccess 
  198
+     and edit it to suit your needs.  It contains further instructions.  For 
  199
+     example, in a Unix shell:
  200
+  <blockquote>
  201
+    <pre>cp lib/htaccess .htaccess</pre>
  202
+  </blockquote>
  203
+
  204
+</blockquote>
  205
+<p>&nbsp;</p>
  206
+<H3><A NAME="config"></A>7. Edit config.php</H3>
  207
+<blockquote>
  208
+  <p>Now you can edit the configuration file, <strong>config.php</strong>, using a 
  209
+     text editor. This file is used by all other files in Moodle.</p>
  210
+  <p>To start with, make a copy of config-dist.php and call it config.php. We 
  211
+    do this so that your config.php won't be overwritten in case you upgrade Moodle 
  212
+    later on. </p>
  213
+  <p>Edit config.php to specify the database details that you just defined (including 
  214
+    a table prefix - notice this is REQUIRED for PostgreSQL), as 
  215
+    well as the site address, file system directory and data directory. 
  216
+    The config file has detailed directions.</p>
  217
+  <p>For the rest of this installation document we will assume your site is at: 
  218
+    <u>http://example.com/moodle</u></p>
  219
+</blockquote>
  220
+<P>&nbsp;</P>
  221
+<H3><A NAME="admin"></A>8. Go to the admin page</H3>
  222
+<blockquote> 
  223
+  <p>The admin page should now be working at: <u>http://example.com/moodle/admin</u>. 
  224
+    If you try and access the front page of your site you'll be taken there automatically 
  225
+    anyway. The first time you access this admin page, you will be presented with 
  226
+    a GPL agreement with which you need to agree before you can continue with the setup.</p>
  227
+  <P>(Moodle will also try to set some cookies in your browser.  If you have 
  228
+     your browser set up to let you choose to accept cookies, then you <B>must</B>