MoodleDocs - User contributions [en]

User talk:Utkarshraj Atmaram

2007-12-19T09:00:44Z

Utcursch: m

'''Please sign your messages. You can sign using four tildes: <nowiki>~~~~</nowiki>'''.

User:Utcursch

2007-12-19T09:00:07Z

Utcursch: wrong page

#REDIRECT[[User:Utkarshraj Atmaram]]

User talk:Utcursch

2007-12-19T08:59:50Z

Utcursch: wrong page

#REDIRECT[[User talk:Utkarshraj Atmaram]]

User:Utcursch

2007-12-19T08:39:41Z

Utcursch: m

[http://en.wikipedia.org/wiki/User:Utcursch Utkarshraj Atmaram]. I managed [http://moodle.dbit.in moodle.dbit.in] during college days.

Activity modules

2006-04-18T07:02:19Z

Utcursch: +cat

'''Activity modules''' reside in the 'mod' directory. 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 is 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
:* Other functions available but not required are:
:** widget_delete_course() - code to clean up anything that would be leftover after all instances are deleted
:** widget_process_options() - code to pre-process the form data from module settings
:* To avoid possible conflict, any module functions should be named starting with widget_ and any constants you define should start with WIDGET_
* ''config.html'' - (optional) a form to set up or update global settings of this module
* Lastly, each module will have some language files that contain strings for that module.

IMPORTANT: When creating a new module, the new name of the module must not contain numbers or other special characters!

==See also==

* http://download.moodle.org/download.php/modules/NEWMODULE.zip - new module template for starting module development. Please follow the README instructions inside the zip.
* Using Moodle [http://moodle.org/course/view.php?id=5 Activity modules] forum

[[Category:Module]]

[[es:Módulos de actividades (desarrollador)]]

Question engine

2006-04-18T06:57:37Z

Utcursch: +cat

Moodle has a powerful question engine with a modular structure to allow question type plug-ins. The question engine is responsible for rendering the questions and for processing student responses. It is used by the [[Quiz developer docs|quiz module]] and it is planned that in future it will be used by the Lesson and other modules.

Historically the question engine started as a part of the quiz module. Only since Moodle 1.6 is it a separate core component of Moodle that can be used by any other Moodle component or module. During this restructuring the code was moved from mod/quiz/ to question/ and the tables and functions were renamed. Wherever the old table or function name contained 'quiz_' the new one will contain 'question_'

==Terminology==

When talking about the question engine there are certain terms that can cause confusion because they can be used with different meanings. In Moodle we have adopted a certain terminology that will be explained below.

===Questions===

A '''question''' is the set of definitions (question name, question text, possible answers, grading rules, feedback, etc.) that constitute a reusable assessment item. So it includes much more than what one would in everyday language understand under a question.
In the terminology of the QTI specification a 'question' is more appropriately called an '''assessment item''' or just 'item' for short.

There are different types of questions, like for example multiple-choice questions or numerical questions. These are referred to as '''[[Question engine#Question types|question types]]''' in Moodle.

Since version 1.5 Moodle is able to handle so-called '''[[Adaptive questions]]''', also known as 'adaptive items' in QTI speak. These are questions that walk the user through a directed graph of question states depending on the user's responses. For example a complicated mathematical question that is answered incorrectly, but is likely to be incorrect because of a common mistake, could provide the user with a hint towards this mistake, apply a penalty and allow a second attempt at this question. Quizzes can be run in 'adaptive mode', in which case Moodle provides buttons to mark each question individually.

===Answers===

In Moodle the term ''''answer'''' is used exclusively for the '''teacher-defined answers''' of a question. When talking about the quiz module it is easy to get confused between these teacher-defined answers and the answers that the students actually give. We have therefore adopted the convention to refer to the student-supplied answers as 'responses' and to reserve the term 'answers' to apply to teacher-defined answers. In question types that rely on teacher-supplied answers these are used in the grading process by comparing them with the student responses. Of course not all question types use teacher-defined answers but use some more intelligent way to process the student responses.

Perhaps one should also stress that 'answer' is not always used in the sense of 'correct answer'. For example every choice in a multiple-choice question is referred to as an answer. Other systems use the term 'distractor' for wrong answers.

In Moodle we always use the term ''''responses'''' to refer to the students' responses to a question because the term 'answers' that one might also be tempted to use for this is already used to refer to the teacher-defined answers, see above. This term is always used in plural, although for some questiontypes there is only one possible response.

There is unfortunately, for historical reasons, one exception to the above rule: The [[Question database structure#quiz_states|quiz_states table]] has a field 'answer' whose purpose it actually is to hold the student's responses.

===Attempts===

In Moodle the term ''''attempt'''' is used in the sense of "Attempt at a quiz" (or another activity involving questions). Depending on the quiz settings, a student may be allowed several attempts at a quiz. An attempt is finished when the student clicks on the corresponding button on the attempt page. Students do not have to complete an attempt in one visit. They can navigate away from the quiz page and return later to continue the same attempt.

Within one and the same quiz attempt a student may make several attempts at answering a particular question, at least if the questiontype allows it and the quiz is set up in adaptive mode. These will always be referred to as ''''attempts at a question'''', never just as 'attempts'.

Because a student can have several attempts at a question within the same attempt at the quiz, there is a lot of data that needs to be stored as the student takes the question through several ''''states'''' by repeated interactions with the question. A state object holds the most recent state of the question and whenever a student submits a response or a similar ''''event'''' occurs, the question goes to a new state. The complete history of question states that the question is taken through is saved and this is referred to as the question ''''session''''. Usually only the most recent state and the last graded state are of interest though.

===Sessions, States, Events===

When a new attempt is started, a new '''session''' is started for each question. So in a sense a session is for a question what an attempt is for a whole quiz. A question session lasts no longer than an attempt and for each question there can only by one session within one attempt.

Moodle allows the student to interact with a question repeatedly within one session and each such interaction leads to a new '''state'''. The first state is created when the session is created. A new state is then created when a student saves and answer or validates an answer or submits an answer or .... The student's responses and, if appropriate, the results of response processing (grading) are stored in the new state that gets created.

The type of '''event''' that led to the creation of a particular state is saved along with the state. The types of events currently used are:
;open :A new session has just been created and this is the opening state. Usually it doesn't hold student responses yet (except where a quiz attempt is based on a previous attempt because the 'attemptonlast' option is set).
;save:The student has clicked the save button.
;validate:The student has asked for his responses to be validated. This means it is checked that they are valid responses. In the case of mathematical questions which requires the input of a mathematical expression in some linear format the question type may want to display the validated result back to the student in typeset form. Similar things may apply to other subject-specific question types. If a student response is found to be invalid the student is told so but no penalty is applied. The invalid response is stored with the state.
;grade:The student has pressed the submit button. The grade is calculated and stored with the attempt.
;duplicategrade:The student has pressed the submit button but the response to this question has not actually changed. This happens a lot in quizzes with several questions on on page where the student may have changed the responses for one question only. I believe that states created by this type of event are not stored in the database.
;close:The last state in a session which is now closed. Currently a session closes only when the attempt closes, either because the student requests it or because the timelimit elapses.

There are now plans to introduce another event type
;submit:The student has submitted his responses for grading but grading has not yet taken place. This will be used by teacher-marked question types like the essay questions for example.

==Code documentation==

The code is documented according to phpdoc conventions. The explanations here in the wiki are meant to complement this.

Inline comments should be used liberally in the code. The following conventions make it easier to search for comments with special meaning:
* use TODO in comments about things that need to be done
* use ??? in comments that are questions about the code

==API==

The library lib/questionlib.php contains all functions that need to be available to any module wanting to use questions (this is new in Moodle 1.6, in Moodle 1.5 this was part of mod/quiz/locallib.php). Loading this library instantiates all questiontype classes by loading the questiontype.php files

A description of the API still needs to be written. Also lib/questionlib.php should be cleaned up a bit to distinguish between the API functions and the helper functions.

==Organisation==
The default questiontype class is defined in '''question/type/questiontype.php''' (in Moodle 1.5 this was still in mod/quiz/locallib.php). The individual questiontypes extend this class in their own questiontype.php file. For documentation of the questiontype classes one should often look at the documentation of the default question type because much of the documentation that is in the default class is not repeated in the other questiontype classes.

While questiontypes are realized as classes, the question engine is not written in a truly object-oriented way. Instead it follows the Moodle model of using objects mostly only as alternatives to arrays to hold database records. So none of the question, attempt, and state objects that play a central role in the module have any methods. Only the questiontype objects have methods. Strangely enough the quiz module instantiates one object of each questiontype class at the start and then reuses their methods for the different questions. If one is used to the Moodle way of programming then this is easy enough to handle.

==Objects and data structures==

Key to understanding how the quiz module works is to understand the different kinds of object work together. The most important ones are:

*Quizzes
*Questions
*Attempts
*States

Quizzes and Questions are data created by the teacher when setting up and editing a quiz. Attempts and States are data created by the student when interacting with a quiz.

Moodle allows students to make several attempts at a quiz. Data about such an attempt is stored in an attempt object. This holds for example how the quiz was randomized for this attempt and the ordering of the questions and answers. So attempts are indexed by user id and quiz id.

Moodle allows students to interact repeatedly with a single question. So for example the student might initially just save an answer, later mark it, then correct it if it was marked incorrect. Each time the student interacts with a particular question inside a particular attempt at a quiz a new state is created. So states are indexed by user id, attempt id and question id.

===Database structure===
All this data needs to be kept in Moodle's database. How this is achieved is explained on a separate page about the '''[[Quiz database structure]]''', which also contains a useful diagram.

As is customary in Moodle, most runtime objects simply represent the data from a particular database record. So for example a $quiz object has fields corresponding to all the fields in the [[Quiz database structure#quiz|quiz table]]. In some cases the objects have some additional fields that are added at runtime. This is particularly the case for $question and $state objects. These additional fields are also described on the page about the '''[[Quiz database structure]]'''. Many functions that are used to process these objects make use of the additional fields and it is therefore necessary to use the correct functions for creating these objects.

===Runtime objects===
Some objects used by the quiz module are purely runtime object and do not correspond to a database table. The structure of these objects is explained in detail on a separate page about the '''[[Quiz runtime objects]]'''.

The main script of the quiz module is attempt.php which will have to deal with all these objects. Studying the '''[[Quiz attempt|explanation of attempt.php]]''' is therefore a good way to start to study the quiz module code.

==Response storage==

The student's responses to a question are stored in <code>$state->responses</code>. Questiontypes are completely free to implement the storage mechanism of their responses (and other state information) the way they want. Still, the standard questiontypes all follow a similar model. The default storage model and the questiontype specific variations are explained below.

The flexibility for the questiontypes to choose their response storage mechanism freely and to convert from the storage model to the runtime model is provided by a set of three functions, which allow to initialise the runtime <code>$state->responses</code> field, to convert from the runtime to the storage model and vice versa:

;<code>create_session_and_responses()</code>
:Initializes the $state object, in particular the <code>$state->responses</code> field

;<code>restore_session_and_responses()</code>
:Loads the question type specific session data from the database into the <code>$state</code> object, in particular it loads the responses that have been saved for the given <code>$state</code> into the <code>$state->responses</code> field.

;<code>save_session_and_responses()</code>
:Saves the question type specific session data from the $state object to the database. In particular, for most questiontypes, it saves the responses from the <code>$state->responses</code> to the database.

The generic quiz module code saves the contents form the <code><nowiki>$state->responses['']</nowiki></code> field to the answer field in the [[Quiz database structure#quiz_states|quiz_states table]] and also automatically restores the contents of this field to <code><nowiki>$state->responses['']</nowiki></code>. This means that any questiontype, which only expects a single value as its response can skip the implementation of the three methods described above. All questiontypes that have multiple value responses need to implement these methods.

The default questiontypes handle this problem by serializing/de-serializing the responses to/from the answer field in the quiz_states table. However, it is also possible (and may be better practice) to extend the quiz_states table with a questiontype specific table, i.e. take the id of the quiz_states record as a foreign key in the questiontype specific table. Because the value of <code><nowiki>$state->responses['']</nowiki></code> is set to the value of the answer field, questiontypes that serialize their response need to overwrite (in <code>save_session_and_responses()</code>) whatever value the generic code set this field to with their serialized value (usually achieved with a simple set_field).

In the method <code>restore_session_and_responses()</code> the serialized value can be read from <code><nowiki>$state->responses['']</nowiki></code> because this is where the value from answer field of the quiz_states table has been moved. Care needs to be taken that this array value is then unset or the whole array overwritten, so that the array does not accidentally contain a value with the empty string index.

==Response processing==

The runtime model for responses dictates the structure of the $state->responses array. Starting with the names of the form elements this section goes through the relevant processing steps and thus attempts to clarify why the keys of the $state->responses array can differ for different questiontypes; even more, it explains how the array keys are chosen and set.

Although it may initially seem strange to start with the naming convention of the form fields, the reason for this will become clear later on. The controls (i.e. the form fields) of a question get printed by the method <code>print_question_formulation_and_controls()</code>. The convention only dictates that the name of the control element(s) must begin with the value of <code>$question->name_prefix</code>. The <code>$question->name_prefix</code> is a string starting with "resp" followed by the question id and an underscore, e.g. <code>resp56_</code>. In the default case, when there is only a single control element (this includes the case of a list of equally named radio buttons), no postfix is appended to the name prefix. For questiontypes that allow or require multiple form elements, an arbitrary string can be appended to the name prefix to form the name of these form elements. The postfix must not include any relational data (i.e. ids of records in the quiz_answers table), because this can lead to problems with regrading of versioned questions.

After the printing of the question the server only sees it again when it is submitted. So the submitted data will contain several values indexed by strings starting with <code>respXX_</code>. Upon submission, the function <code>quiz_process_responses()</code> is called, which assigns the submitted responses to the state of the question with id XX, using the postfix (i.e. everything after the underscore) as array keys. In the default case with only one control element the name only consists of the name prefix. This explains why the default index of the <code>$state->responses</code> array is the empty string. The value of each array element is obviously the value that was submitted by the form, basically a raw response.

The function <code>quiz_process_responses()</code> in turn calls the questiontype specific method <code>grade_responses()</code> to assign a grade to the submitted responses and <code>compare_responses()</code> to determine whether the response was identical to the previous submission and to avoid regrading the same responses repeatedly. These questiontype specific functions need to be aware of the expected keys of the <code>$state->responses</code> array.

Finally, the methods <code>restore_session_and_responses()</code> and <code>save_session_and_responses()</code> also need to know the questiontype specific layout of the <code>$state->responses array</code> and restore or save the information, e.g. by converting from or to the data representation.

==Question types==
{{Questiontype developer docs}}
The quiz module is itself modular and allows question type plug-ins. For each question type there should be a page, accessible via the menu at the right, which provides at least the dtails about
*Database tables
*Response storage
*Question options object
*State options object

It is hoped that Moodlers will contribute a lot of non-core question types in the future. For this it would be good to start a [[Guide to question type plugins]].

==Grades==

The handling of grades is a bit complicated because there are so many different grades around that get rescaled and combined in various ways. This section should summarize how this is done and why.

The following grade fields are being used:
*$question->defaultgrade
::This is the default value for the maximum grade for this question. This is set up when the teacher creates the question and it is stored in an int(10) field in the [[Quiz database structure#quiz_questions|quiz_questions]] table. However when the question is actually used in a particular quiz the teacher can overrule this default and this is stored in:
*$question->maxgrade
::This is the maximum grade that the teacher has assigned to this question in the context of the current quiz. This is by default equal to $questions->defaultgrade but the teacher can change this when editing the quiz. In the database it is stored in an int(10) field in the [[Quiz database structure#quiz_question_instances|quiz_question_instances table]].
*$question->penalty

*$state->raw_grade
*$state->grade
*$state->penalty
*$state->sumpenalty

*$attempt->sumgrades

The maximum grades set by the teacher, $question->defaultgrade and $question->maxgrade, are integers. All student-obtained grades are in principle floating point numbers. For historical reasons they are stored in the database as varchar(10) fields. Care has to be taken when writing to the database to make sure all grades are correctly rounded and squeezed into a string of no more than 10 characters, otherwise the writing to database will fail, see bug 4220.

The final outcome of the calculation of the grade for a user at a particular quiz is stored in the 'grade' field of the [[Quiz database structure#quiz_grades|quiz_grades table]]. This field has type double.

==Penalty mechanism==

===What it is for===

When the quiz is run in adaptive mode the student can interact with a question repeatedly. So in particular the student can try again when he gets a wrong answer. Clearly the final mark for the question must reflect the fact that the student did not get it right originally. Therefore a penalty is subtracted from the final mark.

===How the penalty is determined===

First of all penalties are relevant only if a quiz is run in adaptive mode. Only in this case can a student have a second attempt and therefore only in this mode can there be any occasion to subtract a penalty.

Even in adaptive mode the penalty mechanism is only used when it is selected in the quiz options. If "Apply penalties" is set to "No" then the final mark for the question is the mark for the last graded response.

Each question has a 'penalty' field (which should really be called 'penaltyfactor') which is a number between 0 and 1. The penalty for a wrong response is calculated as the product ($quiz->penalty * $quiz->grade), i.e., as the product of the penaltyfactor with the maximum achievable grade for the question. This product is stored in $state->penalty. So $quiz->penalty is the fraction of the maximum grade that is subtracted as a penalty for each wrong response.

The $quiz->penalty field has a default value of 0.1, both in the database and in mod/quiz/defaults.php. This default can of course be overwritten by the admin on the quiz configuration page. This admin-selected default is (as usual for admin defaults) stored in $CFG->quiz_penalty. The teacher can choose a different penalty factor for each individual question when adding or editing a question.

Now if a student makes repeated wrong attempts (or partially correct attempts) the penalties for all these attempts are added up in $state->sumpenalties. The mark for the question is then calculated as the mark for the last graded response minus the sum of the penalties.

One curious fact about $state->sumpenalties is that, for efficiency reasons, it is not stored in the quiz_states table but instead in the 'sumpenalty' field of the quiz_newest_states table. That way it only has to be stored once per attempt rather than once per response.

===Where it is done in the code===

The function quiz_apply_penalty_and_timelimit() subtracts the penalty in $state->sumpenalty from the raw grade in $state->raw_grade to obtain $state->grade for the response. However it is ensured that the grade of a new attempt at the question never falls below the previously achieved grade. This function also increases $state->sumpenalty by the amount in $state->penalty. The assumption is that $state->penalty has just been set appropriately by the code calling this function, e.g., quiz_process_responses.
[[Category:Quiz]]

Question formats

2006-04-18T06:57:19Z

Utcursch: +cat

Importing and exporting have in common the data structure of questions in moodle but different requirements about the import or export modules unless the import or export is related to the same standard (ex.QTI).
The moodle data structure should be avalable elsewhere.
(to be continued)
[[Category:Quiz]]

Quiz attempt

2006-04-18T06:57:09Z

Utcursch: +cat

{{Quiz developer docs}}The attempt.php script is one of the most complicated scripts of the quiz module. It is responsible for displaying questions to a user, to evaluate and grade the users' responses and additionally it needs to take various quiz settings into account and change the behaviour of the script accordingly. This script, which is vital for the functioning of the quiz module, is explained in this document in some detail in order to provide some context and examples for the use of the question/state model and to illustrate some of the functions provided in locallib.php.

In addition to the immediate benefit of explaining what happens in attempt.php, this piece of documentation should provide an entry point to the quiz module code. A number of functions are used in attempt.php that are likely to be used in other scripts as well.

Although the attempt.php script is useful for understanding how user interactions are handled, in order to gain an understanding of the teacher interface for editing quizzes and questions you should look at edit.php.

== A simplified perspective ==

From a simple functional point of view, the responsibilities of attempt.php is the handling of attempts at a quiz. This includes displaying questions and storing data provided or generated by the users. The interaction could be limited to opening the page and thus creating a new attempt and submitting the responses back to the server, which causes the responses to be graded. While the script is actually more sophisticated and allows to interrupt and continue attempts, this two step scenario provides a good starting point and covers the core functionality.

=== Starting a new attempt ===

When a new attempt is started the attempt object is created by the function <code>quiz_create_attempt()</code> (line 183). It returns an empty <code> $attempt</code> object, which is stored in the database immediately to record the fact that the student has seen the questions.

The next step is to load up all questions and to create initial states for all of them. Loading up the questions is a two step process: first the question records are extracted from the database, then the function <code> quiz_get_questions_options()</code> is called. This attaches the name_prefix field and calls the questiontype specific <code>get_question_options()</code> method for each question record in order to add any required data.

// Load the questions
if (!$questions = get_records_sql($sql)) {
...
}
// Load the question type specific information
if (!quiz_get_question_options($questions)) {
...
}
// Restore the question sessions to their most recent states
// creating new sessions where required
if (!$states = quiz_get_states($questions, $attempt)) {
...
}

After all questions are correctly initialised a state object is created for each by the function <code>quiz_get_states()</code>. This function is responsible for providing a state for each question and creates a new state if there isn't one to be restored. Any newly states are added to the database right away.

At this point all the required data has been generated or loaded, so the last step is to print the page. The printing happens towards the end of the attempt.php script and, apart from a simple call to <code>print_heading()</code> (line 409), is done in a loop through all the question records by calling <code> quiz_print_quiz_question()</code> (line 461), which is just a shorthand for calling the questiontype specific <code>print_question()</code> method. So, quite conveniently, each question is responsible for printing itself. To round up the printing, submit buttons and a footer are printed to the bottom of the page.

=== Processing responses ===

The next logical step after creating and displaying an attempt is that the user enters answers for all questions and submits them for marking. Now it is not necessary to create a new attempt, because there is already an open existing one in the database and the same holds for each question's state. So this time the attempt record is loaded from the database. The questions are loaded in the same way, by querying for the question records an then attaching any required questiontype specific fields by calling the function <code> quiz_get_question_options()</code>. Now the call to the function <code> quiz_get_states()</code> does actually restore the states from the database rather than generate new ones, so the same code works for the two scenarios, creating and closing an attempt.

Now that all data concerning the attempt under discussion has been loaded, the responses submitted by the student come to the scene. For each question they need to be evaluated and graded. The first step here is to determine how to deal with each question and the associated responses. In the simplified case this is clear; all responses need to be graded, the grades stored and then the attempt needs to be closed. However, there are more complicated cases, so the function <code> quiz_extract_responses()</code> is called to create the <code>$actions</code> array, which acts as a set of instructions for the function <code>quiz_process_responses()</code>, a quite complicated function, which encapsulates the entire response processing for one question and calls out to the questiontype specific <code>grade_responses()</code> method for grading.

After all submitted responses have been processed, the questions are rendered in the new states. An exception is if the student has requested to close the attempt (or if it is closed automatically due to a time limit). In this case the attempt is closed by setting the <code>timefinish</code> field to the current time. After this the user is redirected to review.php, which, depending on the quiz review settings, shows the questions including the student's responses, feedback, grades and correct answers.

== A more complicated perspective ==

Before an attempt may be started there are a series of mandatory and optional checks, to determine if the user is allowed to attempt the quiz. In addition to these checks, the page display and functionality are slightly different for users with and without teacher privileges. Also, when the quiz is set to start in "secure" mode (the $quiz->popup option), the printing of the page is slightly different. Including all of these scenarios evidently complicates the structure of the attempt.php script, deviating from the simple scenario described above.

First of all, access to the quiz is denied to guests. Additionally it is possible to restrict acces to an IP range ($quiz->subnet) and to set up a password for the quiz ($quiz->password). In both cases users that can't pass the required tests are denied access.

When a teacher "attempts" a quiz there is a tab navigation facility at the top of the page, which allows the teacher to jump between reviewing, previewing and editing the quiz (and possibly even more options). The teacher interface also contains a button to start a new attempt, which is not present on the student interface. Teachers' attempts are automatically marked as previews, which means that old attempts are automatically deleted when a new attempt is started. It also prevents previews to show up in the students' answers review and preview attempts don't block the possibility of editing the quiz, while students' attempts do.

Further complication is introduced by the feature to allow multiple pages with questions and navigation between these pages. This requieres mechanisms to determine which questions are on which page, which page is currently displayed and which page needs to be viewed next. This is not too hard to achieve, however, one subtlety should be noted: when the attempt is closed it is necessary to load all questions and their most recent states before they are marked, whereas in the case of navgation only the questions and related states of the page that was displayed before are loaded, processed and saved; and the questions and states for the next page are loaded.

Towards the end of the script there are two blocks of code that are responsible for timed quizzes ($quiz->timelimit). The first block prints the start element of the form using javascript to make sure that javascript is enabled (which obviously doesn't help a lot, because the quiz is printed as usual, only the submit won't work). The second block includes the file jstimer.php, which prints a timer that counts down and causes an auto-submit when time is up.
[[Category:Quiz]]

User talk:Helen Foster

2006-04-18T06:44:58Z

Utcursch: /* Template styles */

== More hierarchy ==

Hi Helen, I think this wiki is very useful and I would like to thank you for the work you are putting into it. I like your navigation boxes on the module pages. I have a suggestion for extending these: I think it would be nice to have an extra link that allows one to go higher up in the hierarcy to [[Teacher_documentation]]. What do you think? --[[User:Delius|Delius]] 17:48, 26 January 2006 (WST)

:Hi Gustav, thanks for your kind words. Your contributions to the documentation are most welcome. Please feel free to edit [[Template:Quizzes]] or any other template page. You may also wish to consider further use of category pages e.g. [[:Category:Teacher]] for navigation. -- [[User:Helen|Helen]] 18:26, 26 January 2006 (WST)

== Do you monitor all talk pages? ==

Helen, I have posted another question for you on [[Talk:mod/quiz/index]]. Do you get alerted to anything I put on any talk page or should I post on this page if I want you to see it? --[[User:Delius|Delius]] 18:01, 26 January 2006 (WST)

:Hi Gustav, please note that I often check [[Special:Recentchanges|Recent changes]] or the rss feed. --[[User:Helen|Helen]] 18:26, 26 January 2006 (WST)

::Yes, the [[Special:Recentchanges|Recent changes]] page is very useful. You can tell that I have never used a wiki intensively before. Thanks for your tips. --[[User:Gustav|Gustav]] 18:35, 26 January 2006 (WST)

:::Hey, let's discover the wiki way together! :-) --[[User:Helen|Helen]] 00:24, 27 January 2006 (WST)

==Moodle profile==

Helen- I think you should link to your moodle profile like Martin does (assuming you have one, which I assume <grin>). -- D.I. 29Jan06
Wow, you're fast.. .or I'm confused. --D.I. 29Jan06

:Hi D.I. thanks for your suggestion, which [[User:UrsHunkler|someone else]] seem to be following up! ;-) --[[User:Helen|Helen]] 05:00, 30 January 2006 (WST)

== German moodle docs possible? ==

Hello Helen,

thank you very much for these nice and structured doc pages.
When do you plan to launch a german part of the docs.moodle.org pages?
I ask these question because i can translate some of the english doc pages to german.

Greetings Christoph

:Hi Christoph, thanks for your kind offer of translation. Please email ''docs AT moodle DOT org'' so I may get in touch with you easily when the German Moodle documentation is launched. --[[User:Helen|Helen]] 05:17, 30 January 2006 (WST)

== German User Docs ==

Thanks a lot, Helen, for all your work.
I would also like to help with the German version.

Ulrike

:Hi Ulrike, thanks for your kind offer too. MoodleDocs in other languages will happen soon, for sure! --[[User:Helen|Helen]] 08:30, 31 January 2006 (WST)

== Documentation for different versions ==

Helen

Is there a mechanism for specifying which version of Moodle a particular document refers to? If, for instance, a feature is only available in version 1.6, how would a 1.5.3 user know they couldn't follow these instructions?

Equally, if something is done differently in two versions, how would we stop an edit war breaking out between 1.5.3 and 1.6 users?

I appreciate this probably isn't an issue just yet, but it's possible it may become one in later versions.

Cheers,

[[User:CHRISF|CHRISF]] 19:20, 1 February 2006 (WST)

:Hi ChrisF, thanks for highlighting the issue of differences in Moodle versions. Perhaps a Moodle 1.6 template, inserted using the code <code><nowiki>{{Moodle 1.6}}</nowiki></code>, may be used to show features specific to Moodle 1.6. What do you think? --[[User:Helen|Helen]] 04:22, 4 February 2006 (WST)

::Good idea. I think that would clear it up nicely. [[User:CHRISF|CHRISF]] 18:08, 7 February 2006 (WST)

==Hungarian Moodle Docs==

Hello Helen,
I may be knocking at the wrong door.
Could you please create a folder for me to start Moodle documentation in Hungarian please?
Thanks a lot.
Karoly

(Karoly Fabricz, kfabricz AT vnet DOT hu)

:Hi Karoly, thanks for your kind offer. Please read the information on [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]]. I'll be in touch soon. --[[User:Helen Foster|Helen Foster]] 17:09, 15 March 2006 (WST)

== Belarusian Docs is possible? ==

Dear Helen,

I would like to manage Moodle documentation on Belarusian. Could you create a folder for me to start Moodle documentation in Belarusian, please? Аlphabetic acronym of Belarusian language is be.

Sincerely,
Maryia Davidouskaia
(maryia at iatp dot by)

:Hi Maryia, thanks for your kind offer. As I said to Karoly, please read the information on [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]], and remember that the more people that are involved in creating the documentation, the better it will be. I'll be in touch soon. --[[User:Helen Foster|Helen Foster]] 17:09, 15 March 2006 (WST)

Ok, You are a STAR!

== Template styles ==
Hi Helen! I noticed that you reverted my edits on [[Template:Book]] and [[Template:Assignments]]. You were right -- I didn't realise that the [[MoodleDocs:Styling|style]] doesn't match [[MoodleDocs:Style guide|moodle.org style]]. However, the current template doesn't look right either. It should float to the right instead of occupying a substantial part of the upper screen (for eg. on [[Calculated question developer docs]] page) -- this wil provide easier navigation. Also, the tempalate should be colorful and/or bordered -- this looks more attractive and the reader can understand that it is not a part of the article. May be we can have orange or similar colored templates (such as [[Template:Large Installations]] and [[Template:excerpted from Jason Cole]]) that match with moodle.org style? Is there any official style documentation? Is there a moodle.org style guide which describes styles for templates -- I couldn't find one? [[User:Utkarshraj Atmaram|Utkarshraj Atmaram]] 17:40, 30 March 2006 (WST)

:Hi Utkarshraj, thanks for your contributions to Moodle Docs. As you've found, [[MoodleDocs:Style guide]] and [[MoodleDocs:Styling]] contain all the Moodle Docs styling documentation to-date. Please add your comments about template styling to [[MoodleDocs talk:Styling]]. --[[User:Helen Foster|Helen Foster]] 17:26, 31 March 2006 (WST)

::Thank you! I've started the discussion at [[MoodleDocs talk:Styling]]. [[User:Utkarshraj Atmaram|Utkarshraj Atmaram]] 19:14, 31 March 2006 (WST)

:::LoL, I just realized that the problem is not with the templates, but with themes. Templates just look find with the MoodleDocs theme, but when I am logged in, I use MonoBook theme -- it doesn't display them as right-aligned (at Wikipedia, we explicity make the templates right-aligned). Sorry for wasting your time! [[User:Utkarshraj Atmaram|Utkarshraj Atmaram]] 14:44, 18 April 2006 (WST)

== Slovak Moodle Documentation ==

Hi, Helen. We would like to start work on translation on Moodle Slovak (sk) documentation. Please, do you think is it possible? Thank you.

Sincerely, Juraj Chlebec
havran@gmail.com

:Hi Juraj, thanks for your offer. Please note that, for non iso-8859-1 languages we need to wait for moodle.org to be converted to UTF-8 (since Moodle Docs authenticates against moodle.org) before setting things up. I'll be in contact when this is done. --[[User:Helen Foster|Helen Foster]] 22:05, 10 April 2006 (WST)

== Polish Moodle Documentation ==

Hello, Helen. I saw Your comments to Juraj's post, so just want to let you know that we are ready to start polish translation. Hope the situation will change soon.

User:Utkarshraj Atmaram/temp

2006-04-06T04:13:18Z

Utcursch: test template style

{| align=right id=toc style="margin-left: 15px; background-color: #ffffff; border: 5px solid #ffc240"
!align=center style="border-bottom: 1px solid #ffc240" |'''[[Assignments]]'''
|-
| [[Adding/editing an assignment]]
|-
| [[Assignment details]]
|-
| [[Viewing an assignment]]
|-
| [[Assignment submissions]]
|}

User:Utkarshraj Atmaram

2006-04-06T04:09:15Z

Utcursch: fix link

*[http://moodle.org/user/view.php?id=6591&course=5 My Moodle Personal Profile]
*[http://en.wikipedia.org/wiki/User:Utcursch My Wikipedia page]

----
[[User:Utkarshraj Atmaram/temp|Template test]]

User:Utkarshraj Atmaram

2006-04-06T04:08:31Z

Utcursch: template test

*[http://moodle.org/user/view.php?id=6591&course=5 My Moodle Personal Profile]
*[http://en.wikipedia.org/wiki/User:Utcursch My Wikipedia page]

----
[[User:Utcursch/temp|Template test]]

User talk:Helen Foster

2006-03-31T11:14:31Z

Utcursch: /* Template styles */ thanks

== More hierarchy ==

Hi Helen, I think this wiki is very useful and I would like to thank you for the work you are putting into it. I like your navigation boxes on the module pages. I have a suggestion for extending these: I think it would be nice to have an extra link that allows one to go higher up in the hierarcy to [[Teacher_documentation]]. What do you think? --[[User:Delius|Delius]] 17:48, 26 January 2006 (WST)

:Hi Gustav, thanks for your kind words. Your contributions to the documentation are most welcome. Please feel free to edit [[Template:Quizzes]] or any other template page. You may also wish to consider further use of category pages e.g. [[:Category:Teacher]] for navigation. -- [[User:Helen|Helen]] 18:26, 26 January 2006 (WST)

== Do you monitor all talk pages? ==

Helen, I have posted another question for you on [[Talk:mod/quiz/index]]. Do you get alerted to anything I put on any talk page or should I post on this page if I want you to see it? --[[User:Delius|Delius]] 18:01, 26 January 2006 (WST)

:Hi Gustav, please note that I often check [[Special:Recentchanges|Recent changes]] or the rss feed. --[[User:Helen|Helen]] 18:26, 26 January 2006 (WST)

::Yes, the [[Special:Recentchanges|Recent changes]] page is very useful. You can tell that I have never used a wiki intensively before. Thanks for your tips. --[[User:Gustav|Gustav]] 18:35, 26 January 2006 (WST)

:::Hey, let's discover the wiki way together! :-) --[[User:Helen|Helen]] 00:24, 27 January 2006 (WST)

==Moodle profile==

Helen- I think you should link to your moodle profile like Martin does (assuming you have one, which I assume <grin>). -- D.I. 29Jan06
Wow, you're fast.. .or I'm confused. --D.I. 29Jan06

:Hi D.I. thanks for your suggestion, which [[User:UrsHunkler|someone else]] seem to be following up! ;-) --[[User:Helen|Helen]] 05:00, 30 January 2006 (WST)

== German moodle docs possible? ==

Hello Helen,

thank you very much for these nice and structured doc pages.
When do you plan to launch a german part of the docs.moodle.org pages?
I ask these question because i can translate some of the english doc pages to german.

Greetings Christoph

:Hi Christoph, thanks for your kind offer of translation. Please email ''docs AT moodle DOT org'' so I may get in touch with you easily when the German Moodle documentation is launched. --[[User:Helen|Helen]] 05:17, 30 January 2006 (WST)

== German User Docs ==

Thanks a lot, Helen, for all your work.
I would also like to help with the German version.

Ulrike

:Hi Ulrike, thanks for your kind offer too. MoodleDocs in other languages will happen soon, for sure! --[[User:Helen|Helen]] 08:30, 31 January 2006 (WST)

== Documentation for different versions ==

Helen

Is there a mechanism for specifying which version of Moodle a particular document refers to? If, for instance, a feature is only available in version 1.6, how would a 1.5.3 user know they couldn't follow these instructions?

Equally, if something is done differently in two versions, how would we stop an edit war breaking out between 1.5.3 and 1.6 users?

I appreciate this probably isn't an issue just yet, but it's possible it may become one in later versions.

Cheers,

[[User:CHRISF|CHRISF]] 19:20, 1 February 2006 (WST)

:Hi ChrisF, thanks for highlighting the issue of differences in Moodle versions. Perhaps a [[Template:Moodle 1.6|Moodle 1.6 template]], inserted using the code <code><nowiki>{{Moodle 1.6}}</nowiki></code>, may be used to show features specific to Moodle 1.6. What do you think? --[[User:Helen|Helen]] 04:22, 4 February 2006 (WST)

::Good idea. I think that would clear it up nicely. [[User:CHRISF|CHRISF]] 18:08, 7 February 2006 (WST)

==Hungarian Moodle Docs==

Hello Helen,
I may be knocking at the wrong door.
Could you please create a folder for me to start Moodle documentation in Hungarian please?
Thanks a lot.
Karoly

(Karoly Fabricz, kfabricz AT vnet DOT hu)

:Hi Karoly, thanks for your kind offer. Please read the information on [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]]. I'll be in touch soon. --[[User:Helen Foster|Helen Foster]] 17:09, 15 March 2006 (WST)

== Belarusian Docs is possible? ==

Dear Helen,

I would like to manage Moodle documentation on Belarusian. Could you create a folder for me to start Moodle documentation in Belarusian, please? Аlphabetic acronym of Belarusian language is be.

Sincerely,
Maryia Davidouskaia
(maryia at iatp dot by)

:Hi Maryia, thanks for your kind offer. As I said to Karoly, please read the information on [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]], and remember that the more people that are involved in creating the documentation, the better it will be. I'll be in touch soon. --[[User:Helen Foster|Helen Foster]] 17:09, 15 March 2006 (WST)

Ok, You are a STAR!

== Template styles ==
Hi Helen! I noticed that you reverted my edits on [[Template:Book]] and [[Template:Assignments]]. You were right -- I didn't realise that the [[MoodleDocs:Styling|style]] doesn't match [[MoodleDocs:Style guide|moodle.org style]]. However, the current template doesn't look right either. It should float to the right instead of occupying a substantial part of the upper screen (for eg. on [[Calculated question developer docs]] page) -- this wil provide easier navigation. Also, the tempalate should be colorful and/or bordered -- this looks more attractive and the reader can understand that it is not a part of the article. May be we can have orange or similar colored templates (such as [[Template:Large Installations]] and [[Template:excerpted from Jason Cole]]) that match with moodle.org style? Is there any official style documentation? Is there a moodle.org style guide which describes styles for templates -- I couldn't find one? [[User:Utkarshraj Atmaram|Utkarshraj Atmaram]] 17:40, 30 March 2006 (WST)

:Hi Utkarshraj, thanks for your contributions to Moodle Docs. As you've found, [[MoodleDocs:Style guide]] and [[MoodleDocs:Styling]] contain all the Moodle Docs styling documentation to-date. Please add your comments about template styling to [[MoodleDocs talk:Styling]]. --[[User:Helen Foster|Helen Foster]] 17:26, 31 March 2006 (WST)

::Thank you! I've started the discussion at [[MoodleDocs talk:Styling]]. [[User:Utkarshraj Atmaram|Utkarshraj Atmaram]] 19:14, 31 March 2006 (WST)

User talk:Helen Foster

2006-03-30T09:40:59Z

Utcursch: /* Template styles */

== More hierarchy ==

Hi Helen, I think this wiki is very useful and I would like to thank you for the work you are putting into it. I like your navigation boxes on the module pages. I have a suggestion for extending these: I think it would be nice to have an extra link that allows one to go higher up in the hierarcy to [[Teacher_documentation]]. What do you think? --[[User:Delius|Delius]] 17:48, 26 January 2006 (WST)

:Hi Gustav, thanks for your kind words. Your contributions to the documentation are most welcome. Please feel free to edit [[Template:Quizzes]] or any other template page. You may also wish to consider further use of category pages e.g. [[:Category:Teacher]] for navigation. -- [[User:Helen|Helen]] 18:26, 26 January 2006 (WST)

== Do you monitor all talk pages? ==

Helen, I have posted another question for you on [[Talk:mod/quiz/index]]. Do you get alerted to anything I put on any talk page or should I post on this page if I want you to see it? --[[User:Delius|Delius]] 18:01, 26 January 2006 (WST)

:Hi Gustav, please note that I often check [[Special:Recentchanges|Recent changes]] or the rss feed. --[[User:Helen|Helen]] 18:26, 26 January 2006 (WST)

::Yes, the [[Special:Recentchanges|Recent changes]] page is very useful. You can tell that I have never used a wiki intensively before. Thanks for your tips. --[[User:Gustav|Gustav]] 18:35, 26 January 2006 (WST)

:::Hey, let's discover the wiki way together! :-) --[[User:Helen|Helen]] 00:24, 27 January 2006 (WST)

==Moodle profile==

Helen- I think you should link to your moodle profile like Martin does (assuming you have one, which I assume <grin>). -- D.I. 29Jan06
Wow, you're fast.. .or I'm confused. --D.I. 29Jan06

:Hi D.I. thanks for your suggestion, which [[User:UrsHunkler|someone else]] seem to be following up! ;-) --[[User:Helen|Helen]] 05:00, 30 January 2006 (WST)

== German moodle docs possible? ==

Hello Helen,

thank you very much for these nice and structured doc pages.
When do you plan to launch a german part of the docs.moodle.org pages?
I ask these question because i can translate some of the english doc pages to german.

Greetings Christoph

:Hi Christoph, thanks for your kind offer of translation. Please email ''docs AT moodle DOT org'' so I may get in touch with you easily when the German Moodle documentation is launched. --[[User:Helen|Helen]] 05:17, 30 January 2006 (WST)

== German User Docs ==

Thanks a lot, Helen, for all your work.
I would also like to help with the German version.

Ulrike

:Hi Ulrike, thanks for your kind offer too. MoodleDocs in other languages will happen soon, for sure! --[[User:Helen|Helen]] 08:30, 31 January 2006 (WST)

== Documentation for different versions ==

Helen

Is there a mechanism for specifying which version of Moodle a particular document refers to? If, for instance, a feature is only available in version 1.6, how would a 1.5.3 user know they couldn't follow these instructions?

Equally, if something is done differently in two versions, how would we stop an edit war breaking out between 1.5.3 and 1.6 users?

I appreciate this probably isn't an issue just yet, but it's possible it may become one in later versions.

Cheers,

[[User:CHRISF|CHRISF]] 19:20, 1 February 2006 (WST)

:Hi ChrisF, thanks for highlighting the issue of differences in Moodle versions. Perhaps a [[Template:Moodle 1.6|Moodle 1.6 template]], inserted using the code <code><nowiki>{{Moodle 1.6}}</nowiki></code>, may be used to show features specific to Moodle 1.6. What do you think? --[[User:Helen|Helen]] 04:22, 4 February 2006 (WST)

::Good idea. I think that would clear it up nicely. [[User:CHRISF|CHRISF]] 18:08, 7 February 2006 (WST)

==Hungarian Moodle Docs==

Hello Helen,
I may be knocking at the wrong door.
Could you please create a folder for me to start Moodle documentation in Hungarian please?
Thanks a lot.
Karoly

(Karoly Fabricz, kfabricz AT vnet DOT hu)

:Hi Karoly, thanks for your kind offer. Please read the information on [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]]. I'll be in touch soon. --[[User:Helen Foster|Helen Foster]] 17:09, 15 March 2006 (WST)

== Belarusian Docs is possible? ==

Dear Helen,

I would like to manage Moodle documentation on Belarusian. Could you create a folder for me to start Moodle documentation in Belarusian, please? Аlphabetic acronym of Belarusian language is be.

Sincerely,
Maryia Davidouskaia
(maryia at iatp dot by)

:Hi Maryia, thanks for your kind offer. As I said to Karoly, please read the information on [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]], and remember that the more people that are involved in creating the documentation, the better it will be. I'll be in touch soon. --[[User:Helen Foster|Helen Foster]] 17:09, 15 March 2006 (WST)

Ok, You are a STAR!

== Template styles ==
Hi Helen! I noticed that you reverted my edits on [[Template:Book]] and [[Template:Assignments]]. You were right -- I didn't realise that the [[MoodleDocs:Styling|style]] doesn't match [[MoodleDocs:Style guide|moodle.org style]]. However, the current template doesn't look right either. It should float to the right instead of occupying a substantial part of the upper screen (for eg. on [[Calculated question developer docs]] page) -- this wil provide easier navigation. Also, the tempalate should be colorful and/or bordered -- this looks more attractive and the reader can understand that it is not a part of the article. May be we can have orange or similar colored templates (such as [[Template:Large Installations]] and [[Template:excerpted from Jason Cole]]) that match with moodle.org style? Is there any official style documentation? Is there a moodle.org style guide which describes styles for templates -- I couldn't find one? [[User:Utkarshraj Atmaram|Utkarshraj Atmaram]] 17:40, 30 March 2006 (WST)

User talk:Helen Foster

2006-03-30T09:40:36Z

Utcursch: Template styles

== More hierarchy ==

Hi Helen, I think this wiki is very useful and I would like to thank you for the work you are putting into it. I like your navigation boxes on the module pages. I have a suggestion for extending these: I think it would be nice to have an extra link that allows one to go higher up in the hierarcy to [[Teacher_documentation]]. What do you think? --[[User:Delius|Delius]] 17:48, 26 January 2006 (WST)

:Hi Gustav, thanks for your kind words. Your contributions to the documentation are most welcome. Please feel free to edit [[Template:Quizzes]] or any other template page. You may also wish to consider further use of category pages e.g. [[:Category:Teacher]] for navigation. -- [[User:Helen|Helen]] 18:26, 26 January 2006 (WST)

== Do you monitor all talk pages? ==

Helen, I have posted another question for you on [[Talk:mod/quiz/index]]. Do you get alerted to anything I put on any talk page or should I post on this page if I want you to see it? --[[User:Delius|Delius]] 18:01, 26 January 2006 (WST)

:Hi Gustav, please note that I often check [[Special:Recentchanges|Recent changes]] or the rss feed. --[[User:Helen|Helen]] 18:26, 26 January 2006 (WST)

::Yes, the [[Special:Recentchanges|Recent changes]] page is very useful. You can tell that I have never used a wiki intensively before. Thanks for your tips. --[[User:Gustav|Gustav]] 18:35, 26 January 2006 (WST)

:::Hey, let's discover the wiki way together! :-) --[[User:Helen|Helen]] 00:24, 27 January 2006 (WST)

==Moodle profile==

Helen- I think you should link to your moodle profile like Martin does (assuming you have one, which I assume <grin>). -- D.I. 29Jan06
Wow, you're fast.. .or I'm confused. --D.I. 29Jan06

:Hi D.I. thanks for your suggestion, which [[User:UrsHunkler|someone else]] seem to be following up! ;-) --[[User:Helen|Helen]] 05:00, 30 January 2006 (WST)

== German moodle docs possible? ==

Hello Helen,

thank you very much for these nice and structured doc pages.
When do you plan to launch a german part of the docs.moodle.org pages?
I ask these question because i can translate some of the english doc pages to german.

Greetings Christoph

:Hi Christoph, thanks for your kind offer of translation. Please email ''docs AT moodle DOT org'' so I may get in touch with you easily when the German Moodle documentation is launched. --[[User:Helen|Helen]] 05:17, 30 January 2006 (WST)

== German User Docs ==

Thanks a lot, Helen, for all your work.
I would also like to help with the German version.

Ulrike

:Hi Ulrike, thanks for your kind offer too. MoodleDocs in other languages will happen soon, for sure! --[[User:Helen|Helen]] 08:30, 31 January 2006 (WST)

== Documentation for different versions ==

Helen

Is there a mechanism for specifying which version of Moodle a particular document refers to? If, for instance, a feature is only available in version 1.6, how would a 1.5.3 user know they couldn't follow these instructions?

Equally, if something is done differently in two versions, how would we stop an edit war breaking out between 1.5.3 and 1.6 users?

I appreciate this probably isn't an issue just yet, but it's possible it may become one in later versions.

Cheers,

[[User:CHRISF|CHRISF]] 19:20, 1 February 2006 (WST)

:Hi ChrisF, thanks for highlighting the issue of differences in Moodle versions. Perhaps a [[Template:Moodle 1.6|Moodle 1.6 template]], inserted using the code <code><nowiki>{{Moodle 1.6}}</nowiki></code>, may be used to show features specific to Moodle 1.6. What do you think? --[[User:Helen|Helen]] 04:22, 4 February 2006 (WST)

::Good idea. I think that would clear it up nicely. [[User:CHRISF|CHRISF]] 18:08, 7 February 2006 (WST)

==Hungarian Moodle Docs==

Hello Helen,
I may be knocking at the wrong door.
Could you please create a folder for me to start Moodle documentation in Hungarian please?
Thanks a lot.
Karoly

(Karoly Fabricz, kfabricz AT vnet DOT hu)

:Hi Karoly, thanks for your kind offer. Please read the information on [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]]. I'll be in touch soon. --[[User:Helen Foster|Helen Foster]] 17:09, 15 March 2006 (WST)

== Belarusian Docs is possible? ==

Dear Helen,

I would like to manage Moodle documentation on Belarusian. Could you create a folder for me to start Moodle documentation in Belarusian, please? Аlphabetic acronym of Belarusian language is be.

Sincerely,
Maryia Davidouskaia
(maryia at iatp dot by)

:Hi Maryia, thanks for your kind offer. As I said to Karoly, please read the information on [[MoodleDocs:Starting MoodleDocs|starting Moodle Docs in another language]], and remember that the more people that are involved in creating the documentation, the better it will be. I'll be in touch soon. --[[User:Helen Foster|Helen Foster]] 17:09, 15 March 2006 (WST)

Ok, You are a STAR!

== Template styles ==

Hi Helen! I noticed that you reverted chat[[Template:Book]] and [[Template:Assignments]]. You were right -- I didn't realise that the [[MoodleDocs:Styling|style]] doesn't match [[MoodleDocs:Style guide|moodle.org style]]. However, the current template doesn't look right either. It should float to the right instead of occupying a substantial part of the upper screen (for eg. on [[Calculated question developer docs]] page) -- this wil provide easier navigation. Also, the tempalate should be colorful and/or bordered -- this looks more attractive and the reader can understand that it is not a part of the article. May be we can have orange or similar colored templates (such as [[Template:Large Installations]] and [[Template:excerpted from Jason Cole]]) that match with moodle.org style? Is there any official style documentation? Is there a moodle.org style guide which describes styles for templates -- I couldn't find one? [[User:Utkarshraj Atmaram|Utkarshraj Atmaram]] 17:40, 30 March 2006 (WST)

User:Utkarshraj Atmaram

2006-03-24T10:43:53Z

Utcursch:

*[http://moodle.org/user/view.php?id=6591&course=5 My Moodle Personal Profile]
*[http://en.wikipedia.org/wiki/User:Utcursch My Wikipedia page]

User:Utcursch

2006-02-13T12:17:06Z

Utcursch:

Debian User, [http://en.wikipedia.org/wiki/User:Utcursch Wikipedia Administrator]

Here is my moodle site: http://moodle.dbit.in

User talk:Utcursch

2005-09-15T12:42:16Z

Utcursch:

'''Please sign your messages. You can sign using four tildes: <nowiki>~~~~</nowiki>'''. [[User:Utcursch|Utcursch]] 15 September 2005 12:42 (WST) (This is my sign)

User talk:Utcursch

2005-09-15T12:41:27Z

Utcursch: sign

'''Please sign your messages. You can sign using four tildes: <nowiki>~~~~</nowiki>'''.

User:Utcursch

2005-09-15T11:30:58Z

Utcursch: about myself

Debian User, [http://en.wikipedia.org/wiki/User:Utcursch Wikipedia Administrator]