From 92ce3481fcdf81b4d417d81f29d54f90aad706fd Mon Sep 17 00:00:00 2001 From: moodler Date: Fri, 9 May 2003 12:41:20 +0000 Subject: [PATCH] Please don't put English docs in non-English packs ... they are changing rapidly so these just go out of date for no reason. Cheers, Martin --- lang/de/docs/background.html | 45 ---- lang/de/docs/credits.html | 216 ------------------ lang/de/docs/cvs.html | 152 ------------- lang/de/docs/developer.html | 287 ------------------------ lang/de/docs/faq.html | 42 ---- lang/de/docs/features.html | 161 -------------- lang/de/docs/future.html | 46 ---- lang/de/docs/install.html | 391 --------------------------------- lang/de/docs/intro.html | 38 ---- lang/de/docs/licence.html | 33 --- lang/de/docs/release.html | 415 ----------------------------------- lang/de/docs/teacher.html | 238 -------------------- 12 files changed, 2064 deletions(-) delete mode 100644 lang/de/docs/background.html delete mode 100644 lang/de/docs/credits.html delete mode 100644 lang/de/docs/cvs.html delete mode 100644 lang/de/docs/developer.html delete mode 100644 lang/de/docs/faq.html delete mode 100644 lang/de/docs/features.html delete mode 100644 lang/de/docs/future.html delete mode 100644 lang/de/docs/install.html delete mode 100644 lang/de/docs/intro.html delete mode 100644 lang/de/docs/licence.html delete mode 100644 lang/de/docs/release.html delete mode 100644 lang/de/docs/teacher.html diff --git a/lang/de/docs/background.html b/lang/de/docs/background.html deleted file mode 100644 index 0040379823..0000000000 --- a/lang/de/docs/background.html +++ /dev/null @@ -1,45 +0,0 @@ - - - - Moodle Docs: Background - - - - - -

Background

- -

Moodle is an active and evolving work in progress.

-

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 Curtin University - of Technology 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 :-)

-

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.

-

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.

-

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. -

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.

-

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 Features). -

-

 

- -

Moodle Documentation

-

Version: $Id$

- - - diff --git a/lang/de/docs/credits.html b/lang/de/docs/credits.html deleted file mode 100644 index 0c21f7dfa7..0000000000 --- a/lang/de/docs/credits.html +++ /dev/null @@ -1,216 +0,0 @@ - - - - Moodle Docs: Credits - - - - - -

Credits

- -

Moodle itself is Copyright © 2001-2002, - Martin Dougiamas.  It is distributed under the - GNU Public License.

- - - -


Special thanks

- - - - -


Translations

-
-

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: -

-
- -


Themes

-
-

Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle distribution, along with their authors: -

-
- - -


Other contributors

-
-

Thanks to all of you who have -

-

- -

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): -

-

- -

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. :-) -

- -
- - -


Moodle libraries

- -
-

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:

- -

ADOdb   -  lib/adodb
-

- -
-

Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, -Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.

- -

Version: 2.00 14 May 2002 
- Copyright © 2000, 2001 John Lim (jlim@natsoft.com.my)
- License: Dual LGPL and BSD-style
- URL:  http://php.weblogs.com/adodb
-

-
- -

Graph Class   -  lib/graphlib.php

- -
-

Class to draw line, point, bar, and area graphs, including numeric - x-axis and double y-axis.

- -

Version: 1.6.3 (with modifications)
- Copyright © 2000  Herman Veluwenkamp, hermanV@mindless.com
- License: LGPL
-

-
- - -

IP-Atlas  -   lib/ipatlas

- -
PHP scripts to show the location of an IP address on a map.
-
- Version: 1.0 (with modifications)
- Copyright © 2002   Ivan Kozik
- License: GNU GPL
- URL: http://www.xpenguin.com/ip-atlas.php
-
- - -

PHP mailer   -  lib/class.phpmailer.php
-

- -
Class for sending email using either sendmail, PHP mail(), -or SMTP.  Methods are based upon the standard AspEmail(tm) classes.
-
- Version 1.60, Created 03/30/2002
- Copyright © 2001 Brent R. Matzelle <bmatzelle@yahoo.com>
- License: LGPL
- URL:   http://phpmailer.sourceforge.net
-
-
- - - -

PHP Simple Excel File Generator  -   lib/psxlsgen.php

- -
Class to generate very simple MS Excel files (xls) -via PHP.
-
- Version: 0.3b
- Copyright © 2001  Erol Ozcan <eozcan@superonline.com>
- License: GNU LGPL
- URL: http://psxlsgen.sourceforge.net
-
- - - - - -

Richtext Editor  -   lib/rte

- -
HTML text editor for embedding in web pages.
-
- Version: 0.30 beta 1 (plus modifications)
- Copyright © 2001 Ramesys (Contracting Services) Limited <Austin.France@Ramesys.com> - License: GNU LGPL
- URL: http://richtext.sourceforge.net
-
- - -

SMTP class   -  lib/class.smtp.php
-

- -
Class that can be used to connect and communicate with - any SMTP server.
- It implements all the SMTP functions defined in RFC821 except TURN.
-
- Version: 03/26/2001
- Copyright © 2001  Chris Ryan <chris@greatbridge.com>
-
-
- - -

-
- -

Moodle Documentation

-

Version: $Id$

- - - - diff --git a/lang/de/docs/cvs.html b/lang/de/docs/cvs.html deleted file mode 100644 index 19635fed65..0000000000 --- a/lang/de/docs/cvs.html +++ /dev/null @@ -1,152 +0,0 @@ - - -Moodle Docs: How to use CVS - - - - -

Using CVS to access and update Moodle source code

-
-

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 Sourceforge). -

-

To use Moodle's - CVS archive (as a developer - with write access), you first need to have an account - on Sourceforge. For the examples on this page, let's assume your username - is myusername and your password - is mypassword. Once you have - a Sourceforge account, contact me (Martin Dougiamas) so I can give you write access - to particular directories.

-

To avoid being prompted for mypassword - every time you run a CVS command, follow the Sourceforge - directions for using authorized keys. This step is optional, but it can - make your CVS experience a lot nicer.

-

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.

-

1. Using CVS on Unix

-
-

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:

-
- 
setenv CVS_RSH ssh (for csh, tcsh etc)
- 
export CVS_RSH=ssh (for sh, bash etc)
-
-

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):

-
- 
cvs -z3 -d:ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle co moodle
-
-

Don't try to do run this first CVS command into an existing moodle directory - - start fresh with a new directory.

-

Note that you will be prompted for mypassword - for each command unless you set up authorized - keys

-

Now, you should have a new 'moodle' directory. You can rename it and move - it around if you like. Go into it:

-
- 
cd moodle
-
-

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:

-
- 
cvs diff -c config-dist.php
-cvs diff -c lang
-
-

To fetch the latest updates from the server use:

-
- 
cvs update -dP
-
-

To copy your new files back to the server you would do something like: -

-
- 
cd lang/ca 
-cvs commit
-
-

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!

-

To save more time you can put default arguments into a file called .cvsrc - in your home directory. For example, mine contains:

-
- 
diff -c 
-update -dP
-
-

Try 'cvs help' for more details ...

-

 

-
-

2. Using CVS on Windows

-
-

These instructions are based on notes provided by Mitsuhiro Yoshida <mits@mitstek.com>.

-

Firstly, download and install WinCVS.

-
-

https://sourceforge.net/project/showfiles.php?group_id=10072

-
-

Secondly, download sfsetup for SourceForge ssh access, install it and reboot - Windows.

-
-

http://sourceforge.net/projects/sfsetup/

-
-

Next, configure WinCVS. Launch it, and select Admin -> Preferences. - Then change them as follows:

-
-

[General]
- CVSROOT data:
- Authentication: ssh
- Path: /cvsroot/moodle
- Host address: cvs.moodle.sourceforge.net
- User name: myusername
- CVSROOT: myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle

-

[Globals]
- Checkout read-only: uncheck
- Supply control when adding files: check
- Quiet mode: uncheck
- TCP/IP compression: check and select 9
- Dirty files support: check
- Prune(remove) empty directories: check
- Disable splash screen: uncheck

-
-

Congratulations, WinCVS is set up. Now, you should check out a complete - working copy of the Moodle course code:

-
    -
  1. Select 'Create -> checkout'
    2. -
  2. For the setting 'Module name and path on the server", type "moodle", - then click OK.
    3. -
  3. Type in mypassword and - press Enter in the DOS window.
    4. -
-

After this first checkout, you can fetch updated files from the CVS server - like this:

-
    -
  1. Select folders or files you want to update
    2. -
  2. Press right mouse button and select 'Update selection'
    3. -
  3. Press OK button
    4. -
  4. Type in mypassword and - press Enter in the DOS window.
    5. -
-

After modifying files, you can commit them back to the CVS server like - this:

-
    -
  1. Select folders or files you want to commit
    2. -
  2. Press right button and select 'Commit selection'
    3. -
  3. Press OK button
    4. -
  4. Type in a meaningful comment and press OK button.
    5. -
  5. Type in mypassword and - press Enter in the DOS window.
    6. -
-
-

 

-

Good luck!

-

 

-
-

Moodle Documentation

-

Version: $Id: features.html,v 1.2 2001/12/09 - 10:34:19 martin Exp $

- - diff --git a/lang/de/docs/developer.html b/lang/de/docs/developer.html deleted file mode 100644 index 31d31a7f76..0000000000 --- a/lang/de/docs/developer.html +++ /dev/null @@ -1,287 +0,0 @@ - - Moodle Docs: Developers Manual - - - - - -

Developers Manual

-

This document describes some of Moodle's design and how you can contribute.

-

Sections in this document:

-
    -
  1. Moodle architecture
    2. -
  2. How you can contribute - -
    3. -
-

 

-

1. Moodle architecture

-

From a system administrator's perspective, Moodle has been designed according - to the following criteria:

-
    -
  1. Moodle should run on the widest variety of platforms
    -
    - 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 more - than ten different brands of database (unfortunately, though, it can not - yet set up tables in all these databases - more - on this later).

    -
    2. -
  2. Moodle should be easy to install, learn and modify
    -
    - Early prototypes of Moodle (1999) were built using Zope - - 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.

    -
    3. -
  3. It should be easy to upgrade from one version to the next
    -
    - 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.

    -
    4. -
  4. It should be modular to allow for growth
    -
    - 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.

    -
    5. -
  5. It should be able to be used in conjunction with other systems
    -
    - 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).
    6. -
-

 

-

2. How you can contribute

-

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.

-

Learning Activities

-
-

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):

-
    -
  • mod.html: a form to set up or update an instance of this module
    • -
  • version.php: defines some meta-info and provides upgrading code
    • -
  • icon.gif: a 16x16 icon for the module
    • -
  • db/: SQL dumps of all the required db tables and data (for each database - type)
    • -
  • index.php: a page to list all instances in a course
    • -
  • view.php: a page to view a particular instance
    • -
  • lib.php: any/all functions defined by the module should be in here. If - the modulename if called widget, then the required functions include: -
      -
    • widget_add_instance() - code to add a new instance of widget
      • -
    • widget_update_instance() - code to update an existing instance
      • -
    • widget_delete_instance() - code to delete an instance
      • -
    • widget_user_outline() - given an instance, return a summary of a user's - contribution
      • -
    • widget_user_complete() - given an instance, print details of a user's - contribution
      -
      • -
    • To avoid possible conflict, any module functions should be named starting - with widget_ and any constants you define should start with WIDGET_ -
      • -
    -
    • -
  • Lastly, each module will have some language files that contain strings - for that module. See below.
    • -
-

The easiest way to start a new learning activity module is to use the template - in mod/newmodule_template.zip. - Unzip it and follow the README inside.

-

You might also like to post first in the Activities - modules forum on Using Moodle.

-

 

-
-

Themes

-
-

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. - -

Each theme is in a subdirectory of the "theme" directory, and contains - at least the following files:

-
    -
  • config.php: defines the theme colours used throughout - the site
    • -
  • styles.php: the style sheet, containing CSS definitions - for standard HTML elements as well as many Moodle elements.
    • -
  • header.html: 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.
    • -
  • footer.html: Included at the bottom of each page.
    • -
-

To create your own themes for current versions of Moodle:

-
    -
  1. Copy one of the existing theme folders to one with a new name. I recommend - starting with one of the standard themes. -
  2. Edit config.php and insert your own colours. -
  3. Edit styles.php and change your CSS styles. -
  4. Edit header.html and footer.html to add new logos, or change the layout. -
-

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

-

Note also that Moodle upgrades may break themes slightly, so check the - release notes carefully if you are using a custom theme.

-

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).

-

More discussion about this in the Themes - forum on Using Moodle. If you create a nice theme that you think others - might want to use, please post your zip file on the themes forum!
-

-
- -

 

- -

Languages

-
-

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:

-

lang/en - directory containing all files for one language - (eg English)

-
    -
  • moodle.php - strings for main interface
    • -
  • assignment.php - strings for assignment module
    • -
  • choice.php - strings for choice module
    • -
  • forum.php - strings for forum module
    • -
  • journal.php - strings for journal module
    • -
  • quiz.php - strings for quiz module
    • -
  • resource.php - strings for resource module
    • -
  • survey.php - strings for survey module
    • -
  • .... plus other modules if any.
    -
    - A string is called from these files using the get_string() - or print_string() functions. Each string - supports variable substitution, to support variable ordering in different - languages.
    -
    -     eg $strdueby = get_string("assignmentdueby", "assignment", - userdate($date));
    -
    - If a string doesn't exist in a particular language, then the equivalent - in English will automatically be used instead.
    • -
-

lang/en/help - contains whole help pages (for popup context-sensitive - help)

-
-

Main help pages are situated here, while help pages specific to each module - are located in subdirectories with the module's name.

-

You can insert a helpbutton in a page with the helpbutton function.

-

eg helpbutton("text", "Click here for help about text");

-

and for modules:

-

helpbutton("forumtypes", "Forum types", "forum");

-
-

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, Martin Dougiamas.

-

You might also like to post in the Languages - forum on Using Moodle.

-

If you are maintaining a language an ongoing basis, I can give you CVS - write access to the Moodle source code so that you can directly maintain - the files.

-
-


- Database Schemas

-
-

Given a working database with defined tables, the intentionally simple SQL - used in Moodle should work fine with a wide variety of database brands.

- -

A problem exists with automatically creating 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 lib/db - and inside the db subdirectory of each module.

- -

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 (Martin - Dougiamas).

-
-

 

-

Course Formats

-
-

Moodle currently supports three different course formats: weekly, topics and social. -

-

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.

-

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.

-
-

 

-

Documentation and articles

-
-

If you feel like writing a tutorial, an article, an academic paper or anything - else about Moodle, please do!

-

Put it on the web and make sure you include links to http://moodle.com/

-
-

 

-

Participating in the bug tracker

-
-

Finally, I would like to invite you to register on the "bug tracker" - at bugs.moodle.org so you can file any - bugs that you find and perhaps participate in discussing and fixing them. -

-

"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!

-
-

 

-
-
-
-

Thanks for using Moodle!

-

Cheers,
- Martin Dougiamas

-
-
-
-

 

-

 

-
-

 

-
-

Moodle Documentation

-

Version: $Id: developer.html,v 1.2 2001/12/09 - 10:34:19 martin Exp $

- - diff --git a/lang/de/docs/faq.html b/lang/de/docs/faq.html deleted file mode 100644 index f777d0d669..0000000000 --- a/lang/de/docs/faq.html +++ /dev/null @@ -1,42 +0,0 @@ - - Moodle Docs: Frequently Asked Questions (FAQ) - - - - - -

Frequently Asked Questions (FAQ)

-

This page contains some of the most frequently asked questions with their - answers. If you have a problem it may be quickest to check this page first.

- -
-

Cannot access uploaded files

-
-

Question: I have a strange problem with my new installation of Moodle. Whenever I try -to access or view an uploaded resource, whether in the "Files" menu or on the course page, -I get a 404 error like this one: -

-Not Found
-The requested URL /moodle/file.php/2/myfile.jpg was not found on this server. -
-
-

- -
-
-

Answer: Some web servers don't support the default method Moodle uses to pass arguments to a script.

-

As Admin, go into the "Configure Variables" page and change the setting for - "slasharguments". You should now be able to access your uploaded files.

-
- - - - -
- - -

 

-

Moodle Documentation

-

Version: $Id$

- - diff --git a/lang/de/docs/features.html b/lang/de/docs/features.html deleted file mode 100644 index 5caa122745..0000000000 --- a/lang/de/docs/features.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - Moodle Docs: Background - - - - - -

Features

-

Moodle is an active and evolving product. This page lists some of the many - features it contains:

-

Overall design

- -

Site management

- -

User management

- -

Course management

- -Assignment Module - -

Choice Module

- -

Forum Module

- -Journal Module - -

Quiz Module

- -

Resource Module

- -Survey Module - - -

 

- -

Moodle Documentation

-

Version: $Id: features.html,v 1.2 2001/12/09 - 10:34:19 martin Exp $

- - - diff --git a/lang/de/docs/future.html b/lang/de/docs/future.html deleted file mode 100644 index 94abbd5f66..0000000000 --- a/lang/de/docs/future.html +++ /dev/null @@ -1,46 +0,0 @@ - - Moodle Docs: Future - - - - - - -

Future

-

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. - -

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 bugs.moodle.org. - Your contributions in the form of ideas, code, - feedback and promotion are all very welcome. - -

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. - -

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: -

- -

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. - -

 

-

Moodle Documentation

-

Version: $Id$

- diff --git a/lang/de/docs/install.html b/lang/de/docs/install.html deleted file mode 100644 index e6975caa59..0000000000 --- a/lang/de/docs/install.html +++ /dev/null @@ -1,391 +0,0 @@ - - Moodle Docs: Installation - - - - - -

Installing Moodle

-

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!

-

Take your time and work through this document carefully - it will save you time later on.

-

Sections in this document:

-
    -
  1. Requirements
    2. -
  2. Download
    3. -
  3. Site structure
    4. -
  4. Create a data directory
    5. -
  5. Create a database
    6. -
  6. Check web server settings
    7. -
  7. Edit config.php
    8. -
  8. Go to the admin page
    9. -
  9. Set up cron
    10. -
  10. Create a new course
    11. -
-

1. Requirements

-
-

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.

-

All you should need are:

-
    -
  1. a working installation of PHP (version - 4.1.0 or later), with the following features enabled (most PHP installations - these days will have all of these): -
      -
    • GD library with support for JPG and PNG formats
      • -
    • Sessions support
      • -
    • File uploading allowed
      • -
    -
    2. -
  2. a working database server: MySQL or PostgreSQL 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).
    3. -
-

On a Windows platform, the quickest way to satisfy these requirements is - to download FoxServ, - or EasyPHP 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'. You may also have to fix the directory for - session.save_path - instead of the default "/tmp" use a Windows directory - like "c:/temp".

- -

On Mac OS X I highly recommend the fink - project as a way to download easily-maintainable packages for all of this. If you are less - confident with command-line stuff then Marc Liyanage's PHP Apache Module is the easiest way to get PHP up and running on a new Mac OS X server.

- -

If you're on Linux or another Unix then I'll assume you can figure all this out for yourself! ;-)

- -
-

 

-

2. Download

-
-

There are two ways to get Moodle, as a compressed package and via CVS. These - are explained in detail on the download page on http://moodle.com/

-

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.

-

You can either place the whole folder in your web server documents directory, - in which case the site will be located at http://yourwebserver.com/moodle, - or you can copy all the contents straight into the main web server documents - directory, in which case the site will be simply http://yourwebserver.com.

-
-

 

-

3. Site structure

-
-

Here is a quick summary of the contents of the Moodle folder, to help get - you oriented:

-
-

config.php - the only file you need to edit to get started
- version.php - defines the current version of Moodle code
- index.php - the front page of the site

-
    -
  • admin/ - code to administrate the whole server
    • -
  • auth/ - plugin modules to authenticate users
    • -
  • course/ - code to display and manage courses
    • -
  • doc/ - help documentation for Moodle (eg this page)
    • -
  • files/ - code to display and manage uploaded files
    • -
  • lang/ - texts in different languages, one directory per language
    • -
  • lib/ - libraries of core Moodle code
    • -
  • login/ - code to handle login and account creation
    • -
  • mod/ - all Moodle course modules
    • -
  • pix/ - generic site graphics
    • -
  • theme/ - theme packs/skins to change the look of the site.
    • -
  • user/ - code to display and manage users
    • -
-

 

-
-
-

4. Create a data directory

-
-

Moodle will also need some space on your hard disk to store uploaded files, - such as course documents and user pictures.

- -

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: -

- 
deny from all
-
- -

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".

- -

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.

- -
-

 

-

5. Create a database

-
-

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. -

-

Example command lines for MySQL:

- 
-   # 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
-
-

Example command lines for PostgreSQL:

- 
-   # su - postgres
-   > psql -c "create user moodleuser createdb;" template1
-   > psql -c "create database moodle;" -U moodleuser template1
-   > psql -c "alter user moodleuser nocreatedb;" template1
-
-

(For MySQL I highly recommend the use of phpMyAdmin - to manage your databases).

-

As of version 1.0.8, Moodle now supports table prefixes, and so can safely share - a database with tables from other applications.

-
-

 

-

6. Check your web server settings

-
-

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).

-

In Apache, this is done using a DirectoryIndex parameter in your httpd.conf - file. Mine usually looks like this:

-
- 
DirectoryIndex index.php index.html index.htm
-
-

Just make sure index.php is in the list (and preferably towards the start - of the list, for efficiency).

-

Secondly, Moodle requires a number of PHP settings to be active for it to - work. On most servers these will already be the default settings. - 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):

-
- -
magic_quotes_gpc = On
-magic_quotes_runtime = Off
-file_uploads = On
-short_open_tag = On
-session.auto_start = Off
-session.bug_compat_warn = Off
-
-
-

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. - -

To do this, you need to create a file called .htaccess in Moodle's - main directory that contains definitions for these settings. - This only works on Apache servers and only when Overrides have been allowed. - 

-DirectoryIndex index.php index.html index.htm
-php_value magic_quotes_gpc On
-php_value magic_quotes_runtime Off
-php_value file_uploads On
-php_value short_open_tag On
-php_value session.auto_start Off
-php_value session.bug_compat_warn Off
-

You can also do things like define the maximum size for uploaded files: - 

-php_value upload_max_filesize 2M
-php_value post_max_size 2M
-
- -

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: -

- 
cp lib/htaccess .htaccess
-
- -
-

 

-

7. Edit config.php

-
-

Now you can edit the configuration file, config.php, using a - text editor. This file is used by all other files in Moodle.

-

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.

-

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.

-

For the rest of this installation document we will assume your site is at: - http://example.com/moodle

-
-

 

-

8. Go to the admin page

-
-

The admin page should now be working at: http://example.com/moodle/admin. - 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.

-

(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 must - accept the Moodle cookies, or Moodle won't work properly.) -

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:

-
-

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

-

SUCCESS

-

...and so on, followed by: Main databases set up - successfully.

-
-

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.

-

Scroll down the very bottom of the page and press the "Continue" - link.

-

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.

- -

Scroll down the very bottom of the page and press the "Continue" - link.

- -

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".

- -

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 true, then - try the page again.

- -

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".

- -

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. -

-
-
-
-
-
-

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.

-
-
-
-
-
-

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:

-
    -
  • creating and deleting courses
    • -
  • creating and editing user accounts
    • -
  • administering teacher accounts
    • -
  • changing site-wide settings like themes etc
    • -
-
-

 

-

9. Set up cron

-
-

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.

-

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.

-

Note that the machine performing the cron does not need to be the same - machine that is running Moodle. 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.

-

First, test that the script works by running it directly from your browser:

-
- 
http://example.com/moodle/admin/cron.php
-
-

Now, you need to set up some of way of running the script automatically and - regularly.

-

Running the script from a command line

-

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':

-
- 
wget -q -O /dev/null http://example.com/moodle/admin/cron.php
-
-

Note in this example that the output is thrown away (to /dev/null).

-

The same thing using lynx:

-
- 
lynx -dump http://example.com/moodle/admin/cron.php > /dev/null
-
-

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.

-
- 
/opt/bin/php /web/moodle/admin/cron.php
-
-
-(Windows) C:\apache\php\php.exe C:\apache\htdocs\moodle\admin\cron.php
-
-
-
-

Automatically running the script every 5 minutes

-

On Unix systems: Use cron. Edit your cron settings from the commandline - using "crontab -e" and add a line like:

-
- 
*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php
-
-

On Windows systems: The simplest way is to use my package moodle-cron-for-windows.zip - which makes this whole thing very easy. You can also explore using the built-in - Windows feature for "Scheduled Tasks".

-

-
-

10. Create a new course

-
-

Now that Moodle is running properly, you can create a course.

-

Select "Create a new course" from the Admin page (or the admin - links on the home page).

-

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.

-

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.

-

Once done, the course is ready to customise, and is accessible via the "Courses" - link on the home page.

-

See the "Teacher Manual" for more details - on course-building.

-
-

 

-

Moodle Documentation

-

Version: $Id$

- - diff --git a/lang/de/docs/intro.html b/lang/de/docs/intro.html deleted file mode 100644 index 5fe4728cdb..0000000000 --- a/lang/de/docs/intro.html +++ /dev/null @@ -1,38 +0,0 @@ - - - - Moodle Docs: Introduction - - - - - -

Introduction

- -

Moodle is a software package for producing internet-based courses and web sites. - It's an ongoing development project designed to support a social constructionist framework of education.

- -

Moodle is provided freely as - Open Source software (under the - GNU Public License). Basically this means Moodle is copyrighted, but that you have additional - freedoms. You are allowed to copy, use and modify Moodle provided 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. - -

Moodle will run on any computer that can run - PHP, and can support many types of database (particularly MySQL).

- -

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.

-


-

-

Moodle Documentation

-

Version: $Id$

- - - diff --git a/lang/de/docs/licence.html b/lang/de/docs/licence.html deleted file mode 100644 index 10fb83ce65..0000000000 --- a/lang/de/docs/licence.html +++ /dev/null @@ -1,33 +0,0 @@ - - - - Moodle Docs: Copyright License - - - - - -

Copyright License for Moodle

- -

Moodle is Copyright © 2001-2003, Martin - Dougiamas.

-

This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.

-

This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details (attached below).
-

- -

- -
		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

			    Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it.  (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.)  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their
rights.

  We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

  Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software.  If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

  Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary.  To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

  The precise terms and conditions for copying, distribution and
modification follow.

		    GNU GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License.  The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language.  (Hereinafter, translation is included without limitation in
the term "modification".)  Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

  2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices
    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

    c) If the modified program normally reads commands interactively
    when run, you must cause it, when started running for such
    interactive use in the most ordinary way, to print or display an
    announcement including an appropriate copyright notice and a
    notice that there is no warranty (or else, saying that you provide
    a warranty) and that users may redistribute the program under
    these conditions, and telling the user how to view a copy of this
    License.  (Exception: if the Program itself is interactive but
    does not normally print such an announcement, your work based on
    the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code.  (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it.  For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.  However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License.  Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

  5. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Program or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

  7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all.  For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

  10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission.  For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this.  Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

			    NO WARRANTY

  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

		     END OF TERMS AND CONDITIONS
- - -

Moodle Documentation

-

Version: $Id$

- - - diff --git a/lang/de/docs/release.html b/lang/de/docs/release.html deleted file mode 100644 index 431372b920..0000000000 --- a/lang/de/docs/release.html +++ /dev/null @@ -1,415 +0,0 @@ - - Moodle Docs: Release notes - - - - - - -

Release notes

- -

New in Moodle 1.0.8.1 (12th January, 2003) :

- - -
- - -

New in Moodle 1.0.8 (6th January, 2003) :

- - - -
-

New in Moodle 1.0.7 (10th December, 2002):

- - - - -
-

New in Moodle 1.0.6.4 (24th November, 2002) :

- - - -
-

New in Moodle 1.0.6.3 (14th November, 2002) :

- - -
- -

New in Moodle 1.0.6.2 (11th November, 2002) :

- - - -
- -

New in Moodle 1.0.6.1 (6th November, 2002) :

- - - -
-

New in Moodle 1.0.6 (26th October, 2002) :

- - - -

Older releases can be seen in the Moodle.com announcement forum. - - -

 

-

Moodle Documentation

-

Version: $Id$

diff --git a/lang/de/docs/teacher.html b/lang/de/docs/teacher.html deleted file mode 100644 index f7fc7654d3..0000000000 --- a/lang/de/docs/teacher.html +++ /dev/null @@ -1,238 +0,0 @@ - - Moodle Docs: Teachers Manual - - - - - - -

Teacher Manual

-

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.

- -

Sections in this document:

-
    -
  1. Getting started
    2. -
  2. Course settings
    3. -
  3. Uploading files
    4. -
  4. Setting up activities
    5. -
  5. Running the course
    6. -
  6. Further information
    7. -
-

Getting started

-
-

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.

-

Here are three general tips that will help you get started.

-
    -
  1. Don't be afraid to experiment: -
    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. -
    -
  2. Notice and use these little icons: -
    -

      - the edit icon - lets you edit whatever it is next to.

    -

    - the help - icon will provide you with a popup help window

    -
    -
    3. -
  3. Use the navigation bar at the top of each page -
    this - should help remind you where you are and prevent getting lost. -
    4. -
-
-
-

Course settings

-
-

The first thing you should do is look under the "Administration" - on your course home page and click on "Settings..." - (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).

-

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 course - format.

-

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 martin@moodle.com!)

-

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):

-

Weekly format:

-

-

 

-

Topics format:

-

-

 

-

Social format:

-

-

 

-

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.

-

See the help buttons on the Course Settings page for more details.

-
-
-

Uploading files

-
-

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.

-

All of this is achieved through the Files link in your Administration - menu. The Files section looks like this:

-

-

 

-

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).

-

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.

-

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 zip program 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).

-

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.

-

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.

-

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).

-
-
-

Setting up activities

-
-

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.

-

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.

-

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:

-
-
Assignment
-
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.

-
-
Choice
-
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.
-
-
-
Forum
-
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.
-
-
-
Journal
-
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.
-
-
-
Resource
-
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.
-
-
-
Quiz
-
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. -
-
-
-
Survey
-
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).
-
-
-

After adding your activities you can move them up and down in your course - layout by clicking on the little arrow icons ( - ) next to each one. You - can also delete them using the cross icon , - and re-edit them using the edit icon .

-
-
-

Running the course

-
-

I could write a thesis about this. Actually I am writing - a thesis about this.

-

Until then here are just a few quick pointers:

-
    -
  1. Subscribe yourself to all the forums.
    2. -
  2. 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.
    3. -
  3. Keep notes to yourself in the private "Teacher's Forum" - (under Administration). This is especially useful when team teaching.
    4. -
  4. Use the "Logs" 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.
    5. -
  5. Use the "Activity Reports" (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.
    6. -
  6. 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.
    7. -
-
-
-

Further information

-
-

If you have any particular problems with your site, you should contact your - local site administrator.

-

If you have some great ideas for improvements to Moodle, or even some good - stories, come over to moodle.com and join - in the course called "Using Moodle". - We'd love to hear from you, and you can help Moodle improve.

-

If you want to contribute to coding new modules, or writing documentation, - or papers, contact me: Martin - Dougiamas or browse the "bug tracker" site for Moodle, at bugs.moodle.com

-

Thanks for using Moodle - good luck!

-
-

 

-
-

Moodle Documentation

-

Version: $Id: teacher.html,v 1.4 2002/08/18 10:00:01 - martin Exp $

- - -- 2.39.5