https://docs.moodle.org/test/api.php?action=feedcontributions&feedformat=atom&user=Vf 2026-06-24T07:53:13Z User contributions MediaWiki 1.43.5 https://docs.moodle.org/test/index.php?title=Flashcard_module&diff=48493 2008-12-29T00:15:02Z

<p>Vf: </p> <hr /> <div>The '''flashcard module''' may be downloaded (for Moodle 2.0) from http://download.moodle.org/plugins/mod/flashcard.zip .<br /> <br /> Actual stable version is at http://download.moodle.org/plugins19/mod/flashcard.zip .<br /> <br /> The flashcard module allows editing and playing flashcards. Flashcards are a &quot;memory training&quot; device that uses the concept of repetition. Checking a flashcard deck will present the student the couples of relationships to be memorized. More often the associations are reviewed, deeper the memorization will be engraved into our memorial circuits.<br /> <br /> ==Features==<br /> <br /> * Getting cards from a &quot;matching question&quot;<br /> * Editing cards<br /> * Multimedia cards: text, image, sound and image + sound together<br /> * Automated backpropagation of cards (can be disabled)<br /> * Customizable decks<br /> <br /> ==Configuration==<br /> <br /> [[Flashcard module: Configuration Parameters]]<br /> <br /> [[Flashcard module: Capabilities]]<br /> <br /> ==Screens==<br /> <br /> ===Student Screens=== <br /> <br /> *[[Flashcard module: Freeplay Screen|Freeplay Screen]]<br /> * Leitner Play Screens<br /> ** [[Flashcard module: Leitner Choose A Deck|Choose a deck to play with]]<br /> ** [[Flashcard module: Leitner Use A Deck|Use a deck]]<br /> <br /> ===Teacher Screens===<br /> <br /> * Summary Screens<br /> **[[Flashcard module: By User Summary|By User Summary]]<br /> **[[Flashcard module: By Card Summary|By Card Summary]]<br /> *[[Flashcard module: Edit Screen|Edit Screen]]<br /> <br /> == See also ==<br /> * [[Lesson_module#The_Flash_card_lesson|Flash card presentation]] in the [[Lesson module]] is an alternative to this module.<br /> * Using Moodle [http://moodle.org/mod/forum/view.php?id=7180 Flashcard module forum]<br /> <br /> [[Category:Contributed code]]<br /> [[fr: Flashcard]]</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:comment&diff=45932 2008-10-29T21:40:22Z

<p>Vf: </p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> People who have this capability in the current context are allowed to post comments on a ticket. Usually, roles who have &quot;developer&quot; or &quot;resolver&quot; capability should also have &quot;comment&quot; capability in order to inform about progression status the reporter.<br /> <br /> [[Category:Capabilities]]</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:develop&diff=45931 2008-10-29T21:40:06Z

<p>Vf: </p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> This capability allows discriminating potential resolvers.<br /> <br /> (note : capabilities where setup in order to make the tracker working approximatively on 1.9. There are still some further reflexion in progress to enhance role management in the tracker module. Resolver/Developer role distinction is one of this further work we need to checkup).<br /> <br /> [[Category:Capabilities]]</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:report&diff=45930 2008-10-29T21:39:45Z

<p>Vf: </p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> People who get this capability within the current context can post request to the tracker.<br /> <br /> this capability should be given to anyone. It may be removed from unauthentified users if we want the tracker not to be anonymous.<br /> <br /> [[Category:Capabilities]]</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:managewatches&diff=45929 2008-10-29T21:39:29Z

<p>Vf: </p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> People who have this capability in the current context can add and remove watchers to a ticket.<br /> <br /> [[Category:Capabilities]]</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:manage&diff=45928 2008-10-29T21:39:09Z

<p>Vf: </p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> Users who have this capability can manage tracker's form structure, by defining, adding or removing custom form elements.<br /> <br /> This is basically a Tracker administrator typical capability.<br /> <br /> [[Category:Capabilities]]</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:viewallissues&diff=45927 2008-10-29T21:38:51Z

<p>Vf: </p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> Having this capability in the current context will allow users to browse the complete list of tickets, wether they are owner or not. This capability is usefull for making cooperative bugtrackers.<br /> <br /> It should not be given to users in case of use as a user support help desk.<br /> <br /> [[Category:Capabilities]]</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:seeissues&diff=45926 2008-10-29T21:38:29Z

<p>Vf: </p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> People who have this capability in the current context can inspect issue details.<br /> <br /> [[Category:Capabilities]]</div>

Vf https://docs.moodle.org/test/index.php?title=File:sample_collection_form.jpg&diff=45924 2008-10-29T21:18:30Z

<p>Vf: Sample of ticket recollection form.</p> <hr /> <div>Sample of ticket recollection form.</div>

Vf https://docs.moodle.org/test/index.php?title=Tracker_module/Bug_recollection_form&diff=45923 2008-10-29T21:17:52Z

<p>Vf: </p> <hr /> <div>[[Tracker_module|index]]<br /> <br /> [[Image:sample_collection_form.jpg]]<br /> <br /> The ticket recollection form is a single form having at least a summary textfield and a description textarea. <br /> <br /> In addition, there is provision to add any set of recollection fields that can be picked within the module scope definition, or a site wide shared set of form components.<br /> <br /> All form elements can be textfields, textareas, dropdown lists, checkbox (multianswer) or radio button sets.<br /> <br /> Radio and checkbox set elements can be arranged in vertical layout or horizontal layout.</div>

Vf https://docs.moodle.org/test/index.php?title=Tracker_module/Bug_recollection_form&diff=45922 2008-10-29T21:14:35Z

<p>Vf: </p> <hr /> <div>[[Tracker_module|index]]<br /> <br /> The ticket recollection form is a single form having at least a summary textfield and a description textarea. <br /> <br /> In addition, there is provision to add any set of recollection fields that can be picked within the module scope definition, or a site wide shared set of form components.<br /> <br /> All form elements can be textfields, textareas, dropdown lists, checkbox (multianswer) or radio button sets.<br /> <br /> Radio and checkbox set elements can be arranged in vertical layout or horizontal layout.</div>

Vf https://docs.moodle.org/test/index.php?title=Tracker_module/Bug_recollection_form&diff=45921 2008-10-29T21:11:26Z

<p>Vf: New page: index The ticket recollection form is a single form having at least a summary textfield and a description textarea. In addition, there is provision to add any set of ...</p> <hr /> <div>[[Tracker_module|index]]<br /> <br /> The ticket recollection form is a single form having at least a summary textfield and a description textarea. <br /> <br /> In addition, there is provision to add any set of recollection fields that can be picked within the module scope definition, or a site wide shared set of form components.<br /> <br /> All form elements can be textfields, textareas, dropdown lists, checkbox (multianswer) or radio button sets.</div>

Vf https://docs.moodle.org/test/index.php?title=Tracker_module&diff=45920 2008-10-29T21:08:20Z

<p>Vf: </p> <hr /> <div>==Module overview==<br /> <br /> This module provides a light but full featured bug tracker within a Moodle environment. This tracker could be used by administrators to collect issues from Moodle end users, or may be as a real bug tracking tool for project oriented activities.<br /> <br /> ==Screens==<br /> ===Common user screens===<br /> * [[Tracker_module/Bug recollection form|Bug recollection form]]<br /> * Viewing bug list<br /> ** Exploring bug list (non manager mode)<br /> ** Searching a bug <br /> ** Viewing a bug description<br /> * User profile, stats and shortcuts<br /> ** My preferences : choosing on which events to be notified<br /> ** My watches : managing which bug entries I receive notifications from<br /> ** My searches : managing stored search queries for my own<br /> <br /> ===Resolver screens===<br /> * Viewing bug list<br /> ** Exploring bug list (manager mode)<br /> ** Editing a bug entry<br /> <br /> ===Administrator screens===<br /> * Activity summary<br /> * Managing bug tracking form elements<br /> <br /> ==Capabilities==<br /> <br /> [[Tracker_module/Capabilities|Capabilities for Tracker module (1.9)]]<br /> <br /> [[Category:Contributed code]]</div>

Vf https://docs.moodle.org/test/index.php?title=Tracker_module/Capabilities&diff=45919 2008-10-29T21:06:56Z

<p>Vf: </p> <hr /> <div>[[Tracker_module|index]]<br /> <br /> Tracker module's capabilities allow to control who have access to some particuliar behaviour of the module. <br /> <br /> *[[Capabilitites/mod/tracker:seeissues|mod/tracker:seeissues]]<br /> *[[Capabilitites/mod/tracker:viewallissues|mod/tracker:viewallissues]]<br /> *[[Capabilitites/mod/tracker:manage|mod/tracker:manage]]<br /> *[[Capabilitites/mod/tracker:managewatches|mod/tracker:managewatches]]<br /> *[[Capabilitites/mod/tracker:resolve|mod/tracker:resolve]]<br /> *[[Capabilitites/mod/tracker:report|mod/tracker:report]]<br /> *[[Capabilitites/mod/tracker:develop|mod/tracker:develop]]<br /> *[[Capabilitites/mod/tracker:comment|mod/tracker:comment]]</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:comment&diff=45918 2008-10-29T21:06:02Z

<p>Vf: New page: index People who have this capability in the current context are allowed to post comments on a ticket. Usually, roles who have &quot;developer&quot; or &quot;resolver&quot; ca...</p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> People who have this capability in the current context are allowed to post comments on a ticket. Usually, roles who have &quot;developer&quot; or &quot;resolver&quot; capability should also have &quot;comment&quot; capability in order to inform about progression status the reporter.</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:develop&diff=45917 2008-10-29T21:01:19Z

<p>Vf: New page: index This capability allows discriminating potential resolvers. (note : capabilities where setup in order to make the tracker working approximatively on ...</p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> This capability allows discriminating potential resolvers.<br /> <br /> (note : capabilities where setup in order to make the tracker working approximatively on 1.9. There are still some further reflexion in progress to enhance role management in the tracker module. Resolver/Developer role distinction is one of this further work we need to checkup)</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:report&diff=45916 2008-10-29T20:52:24Z

<p>Vf: </p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> People who get this capability within the current context can post request to the tracker.<br /> <br /> this capability should be given to anyone. It may be removed from unauthentified users if we want the tracker not to be anonymous.</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:report&diff=45915 2008-10-29T20:51:18Z

<p>Vf: New page: index People who get this capability within the current context can post request to the tracker.</p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> People who get this capability within the current context can post request to the tracker.</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:resolve&diff=45914 2008-10-29T20:50:14Z

<p>Vf: New page: index People who have the &quot;resolve&quot; capability are known as &quot;resolvers&quot;. They are allowed to edit the ticket data sheet and change status of the ticket. Re...</p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> People who have the &quot;resolve&quot; capability are known as &quot;resolvers&quot;. They are allowed to edit the ticket data sheet and change status of the ticket. Resolvers can be assigned a ticket and cannot change this assignation unless giving the ticket back to a manager. <br /> <br /> Resolvers can edit an issue and change any information field in it. It may also write a conclusion article when solving the issue.<br /> <br /> Resolvers automatically swithc a ticket to open when first viewing a new posted ticket.<br /> <br /> A resolver can potentially be choosen in a list of designated developpers.</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:managewatches&diff=45913 2008-10-29T20:35:16Z

<p>Vf: New page: index People who have this capability in the current context can add and remove watchers to a ticket.</p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> People who have this capability in the current context can add and remove watchers to a ticket.</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:manage&diff=45912 2008-10-29T20:33:42Z

<p>Vf: New page: index Users who have this capability can manage tracker&#039;s form structure, by defining, adding or removing custom form elements. This is basically a Tracke...</p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> Users who have this capability can manage tracker's form structure, by defining, adding or removing custom form elements.<br /> <br /> This is basically a Tracker administrator typical capability.</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:viewallissues&diff=45911 2008-10-29T20:32:08Z

<p>Vf: </p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> Having this capability in the current context will allow users to browse the complete list of tickets, wether they are owner or not. This capability is usefull for making cooperative bugtrackers.<br /> <br /> It should not be given to users in case of use as a user support help desk.</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:viewallissues&diff=45910 2008-10-29T20:31:48Z

<p>Vf: New page: Tracker_module/Capabilities Having this capability in the current context will allow users to browse the complete list of tickets, wether they are owner or not. This capability is use...</p> <hr /> <div>[[Tracker_module/Capabilities]]<br /> <br /> Having this capability in the current context will allow users to browse the complete list of tickets, wether they are owner or not. This capability is usefull for making cooperative bugtrackers.<br /> <br /> It should not be given to users in case of use as a user support help desk.</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:seeissues&diff=45909 2008-10-29T20:28:00Z

<p>Vf: </p> <hr /> <div>[[Tracker_module/Capabilities|index]]<br /> <br /> People who have this capability in the current context can inspect issue details.</div>

Vf https://docs.moodle.org/test/index.php?title=Capabilitites/mod/tracker:seeissues&diff=45908 2008-10-29T20:27:43Z

<p>Vf: New page: Tracker_module/Capabilities People who have this capability in the current context can inspect issue details.</p> <hr /> <div>[[index|Tracker_module/Capabilities]]<br /> <br /> People who have this capability in the current context can inspect issue details.</div>

Vf https://docs.moodle.org/test/index.php?title=Tracker_module/Capabilities&diff=45907 2008-10-29T20:26:05Z

<p>Vf: </p> <hr /> <div>Tracker module's capabilities allow to control who have access to some particuliar behaviour of the module. <br /> <br /> *[[Capabilitites/mod/tracker:seeissues|mod/tracker:seeissues]]<br /> *[[Capabilitites/mod/tracker:viewallissues|mod/tracker:viewallissues]]<br /> *[[Capabilitites/mod/tracker:manage|mod/tracker:manage]]<br /> *[[Capabilitites/mod/tracker:managewatches|mod/tracker:managewatches]]<br /> *[[Capabilitites/mod/tracker:resolve|mod/tracker:resolve]]<br /> *[[Capabilitites/mod/tracker:report|mod/tracker:report]]<br /> *[[Capabilitites/mod/tracker:develop|mod/tracker:develop]]<br /> *[[Capabilitites/mod/tracker:comment|mod/tracker:comment]]</div>

Vf https://docs.moodle.org/test/index.php?title=Tracker_module/Capabilities&diff=45906 2008-10-29T20:23:46Z

<p>Vf: </p> <hr /> <div>Tracker module's capabilities allow to control who have access to some particuliar behaviour of the module. <br /> <br /> *[[mod/tracker:seeissues]]<br /> *[[mod/tracker:viewallissues]]<br /> *[[mod/tracker:manage]]<br /> *[[mod/tracker:managewatches]]<br /> *[[mod/tracker:resolve]]<br /> *[[mod/tracker:report]]<br /> *[[mod/tracker:develop]]<br /> *[[mod/tracker:comment]]</div>

Vf https://docs.moodle.org/test/index.php?title=Tracker_module/Capabilities&diff=45905 2008-10-29T20:23:25Z

<p>Vf: New page: Tracker module&#039;s capabilities allow to control who have access to some particuliar behaviour of the module. mod/tracker:seeissues mod/tracker:viewallissues mod/tracker:manage...</p> <hr /> <div>Tracker module's capabilities allow to control who have access to some particuliar behaviour of the module. <br /> <br /> [[mod/tracker:seeissues]]<br /> [[mod/tracker:viewallissues]]<br /> [[mod/tracker:manage]]<br /> [[mod/tracker:managewatches]]<br /> [[mod/tracker:resolve]]<br /> [[mod/tracker:report]]<br /> [[mod/tracker:develop]]<br /> [[mod/tracker:comment]]</div>

Vf https://docs.moodle.org/test/index.php?title=Tracker_module&diff=45904 2008-10-29T20:20:17Z

<p>Vf: /* Screens */</p> <hr /> <div>==Module overview==<br /> <br /> This module provides a light but full featured bug tracker within a Moodle environment. This tracker could be used by administrators to collect issues from Moodle end users, or may be as a real bug tracking tool for project oriented activities.<br /> <br /> ==Screens==<br /> ===Common user screens===<br /> * Bug recollection form<br /> * Viewing bug list<br /> ** Exploring bug list (non manager mode)<br /> ** Searching a bug <br /> ** Viewing a bug description<br /> * User profile, stats and shortcuts<br /> ** My preferences : choosing on which events to be notified<br /> ** My watches : managing which bug entries I receive notifications from<br /> ** My searches : managing stored search queries for my own<br /> <br /> ===Resolver screens===<br /> * Viewing bug list<br /> ** Exploring bug list (manager mode)<br /> ** Editing a bug entry<br /> <br /> ===Administrator screens===<br /> * Activity summary<br /> * Managing bug tracking form elements<br /> <br /> ==Capabilities==<br /> <br /> [[Tracker_module/Capabilities|Capabilities for Tracker module (1.9)]]<br /> <br /> [[Category:Contributed code]]</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_Edit_Screen&diff=38014 2008-06-21T18:06:42Z

<p>Vf: /* Editing a sound or image input */</p> <hr /> <div>[[Flashcard module|back to index]]<br /> <br /> The edit screen allows the teacher to design and update the complete card set.<br /> <br /> [[Image:flashcard_edit.jpg]]<br /> <br /> ==Editing a text input==<br /> <br /> To edit a standard text input, just enter the text in the presented textarea. You may use multilang tags for making multiple language questions (resp. answers).<br /> <br /> ==Editing a sound or image input==<br /> <br /> Both sounds and image will use the text description as a path to a stored file. You ''need uploading your resources first''. The directory for uploading media resources is automatically created when creating a new flashcard activity. It is constructed as moddata/flashcard/%flashcardId% in the course file folder.<br /> <br /> For pointing a resource file, once the directory fed with resources, just click on the choose button below the textfield. You will be prompted a popup directly bound to the resource directory for choosing a file.<br /> <br /> ==Editing a sound/image couple==<br /> <br /> In the &quot;image + sound&quot; mode, you have to choose both an image and a sound. The procedure is just twice the above, each media component having its own input field.</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_Edit_Screen&diff=38013 2008-06-21T18:06:14Z

<p>Vf: /* Editing a text input */</p> <hr /> <div>[[Flashcard module|back to index]]<br /> <br /> The edit screen allows the teacher to design and update the complete card set.<br /> <br /> [[Image:flashcard_edit.jpg]]<br /> <br /> ==Editing a text input==<br /> <br /> To edit a standard text input, just enter the text in the presented textarea. You may use multilang tags for making multiple language questions (resp. answers).<br /> <br /> ==Editing a sound or image input==<br /> <br /> Both sounds and image will use the text description as a path to a stored file. You ''need uploading your resources first''. The directory for uploading media resources is automatically created when creating a new flashcard activity. It is constrcuted as moddata/flashcard/%flashcardId% in the course file folder.<br /> <br /> For pointing a resource file, once the directory fed with resources, just click on the choose button below the textarea. You will be prompted a popup directly bound to the resource directory for choosing a file.<br /> <br /> ==Editing a sound/image couple==<br /> <br /> In the &quot;image + sound&quot; mode, you have to choose both an image and a sound. The procedure is just twice the above, each media component having its own input field.</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_Edit_Screen&diff=38012 2008-06-21T18:05:55Z

<p>Vf: </p> <hr /> <div>[[Flashcard module|back to index]]<br /> <br /> The edit screen allows the teacher to design and update the complete card set.<br /> <br /> [[Image:flashcard_edit.jpg]]<br /> <br /> ==Editing a text input==<br /> <br /> To edit a standard text input, just enter the text in the presented textfield. You may use multilang tags for making multiple language questions (resp. answers). <br /> <br /> ==Editing a sound or image input==<br /> <br /> Both sounds and image will use the text description as a path to a stored file. You ''need uploading your resources first''. The directory for uploading media resources is automatically created when creating a new flashcard activity. It is constrcuted as moddata/flashcard/%flashcardId% in the course file folder.<br /> <br /> For pointing a resource file, once the directory fed with resources, just click on the choose button below the textarea. You will be prompted a popup directly bound to the resource directory for choosing a file.<br /> <br /> ==Editing a sound/image couple==<br /> <br /> In the &quot;image + sound&quot; mode, you have to choose both an image and a sound. The procedure is just twice the above, each media component having its own input field.</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module&diff=38011 2008-06-21T17:17:25Z

<p>Vf: /* See also */</p> <hr /> <div>The '''flashcard module''' may be downloaded from http://download.moodle.org/plugins/mod/flashcard.zip .<br /> <br /> The flashcard module allows editing and playing flashcards. Flashcards are a &quot;memory training&quot; device that uses the concept of repetition. Checking a flashcard deck will present the student the couples of relationships to be memorized. More often the associations are reviewed, deeper the memorization will be engraved into our memorial circuits.<br /> <br /> ==Features==<br /> <br /> * Getting cards from a &quot;matching question&quot;<br /> * Editing cards<br /> * Multimedia cards: text, image, sound and image + sound together<br /> * Automated backpropagation of cards (can be disabled)<br /> * Customizable decks<br /> <br /> ==Configuration==<br /> <br /> [[Flashcard module: Configuration Parameters]]<br /> <br /> [[Flashcard module: Capabilities]]<br /> <br /> ==Screens==<br /> <br /> ===Student Screens=== <br /> <br /> *[[Flashcard module: Freeplay Screen|Freeplay Screen]]<br /> * Leitner Play Screens<br /> ** [[Flashcard module: Leitner Choose A Deck|Choose a deck to play with]]<br /> ** [[Flashcard module: Leitner Use A Deck|Use a deck]]<br /> <br /> ===Teacher Screens===<br /> <br /> * Summary Screens<br /> **[[Flashcard module: By User Summary|By User Summary]]<br /> **[[Flashcard module: By Card Summary|By Card Summary]]<br /> *[[Flashcard module: Edit Screen|Edit Screen]]<br /> <br /> == See also ==<br /> * [[Lesson#The_Flash_card_lesson|Flash card presentation]] in the [[Lesson module]] is an alternative to this module.<br /> * Using Moodle [http://moodle.org/mod/forum/view.php?id=7180 Flashcard module forum]<br /> <br /> [[Category:Contributed code]]<br /> [[fr: Flashcard]]</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module&diff=38010 2008-06-21T17:08:11Z

<p>Vf: /* See also */</p> <hr /> <div>The '''flashcard module''' may be downloaded from http://download.moodle.org/plugins/mod/flashcard.zip .<br /> <br /> The flashcard module allows editing and playing flashcards. Flashcards are a &quot;memory training&quot; device that uses the concept of repetition. Checking a flashcard deck will present the student the couples of relationships to be memorized. More often the associations are reviewed, deeper the memorization will be engraved into our memorial circuits.<br /> <br /> ==Features==<br /> <br /> * Getting cards from a &quot;matching question&quot;<br /> * Editing cards<br /> * Multimedia cards: text, image, sound and image + sound together<br /> * Automated backpropagation of cards (can be disabled)<br /> * Customizable decks<br /> <br /> ==Configuration==<br /> <br /> [[Flashcard module: Configuration Parameters]]<br /> <br /> [[Flashcard module: Capabilities]]<br /> <br /> ==Screens==<br /> <br /> ===Student Screens=== <br /> <br /> *[[Flashcard module: Freeplay Screen|Freeplay Screen]]<br /> * Leitner Play Screens<br /> ** [[Flashcard module: Leitner Choose A Deck|Choose a deck to play with]]<br /> ** [[Flashcard module: Leitner Use A Deck|Use a deck]]<br /> <br /> ===Teacher Screens===<br /> <br /> * Summary Screens<br /> **[[Flashcard module: By User Summary|By User Summary]]<br /> **[[Flashcard module: By Card Summary|By Card Summary]]<br /> *[[Flashcard module: Edit Screen|Edit Screen]]<br /> <br /> == See also ==<br /> * [[Lesson#The_Flash_card_lesson|Flash card presentation]] in the [[Lesson module]] is an alternative to this module.<br /> * Using Moodle [http://moodle.org/mod/forum/view.php?id=7180 Flashcard module forum]<br /> <br /> [[Category:Contributed code]]<br /> [[fr:Module Flashcard]]</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_Configuration_Parameters&diff=38009 2008-06-21T17:06:17Z

<p>Vf: </p> <hr /> <div>[[Flashcard module|Back to index]]<br /> <br /> [[Image:flashcard_parameters.jpg]]<br /> <br /> ===Time range (1)===<br /> <br /> The time range parameters allow to define an aperture time slot for the module. If disabled, the module is available at any time, pursuant it is set to visible state.<br /> <br /> ===Question to Import (2)===<br /> <br /> You can ask the module to import a &quot;matching question&quot; from the question bank. You must check the &quot;force reload&quot; option to import the questions (see below).<br /> <br /> ===Force Reloading (3)===<br /> <br /> You must check this box to have question definitions imported within the flashcard question set.<br /> <br /> ===Customization (4)===<br /> <br /> This is not really a parameter, but some indications about how to customize the flashcard appearance. Teachers can use course files to change the stylesheet. Needs some very little skills in CSS.<br /> <br /> ===Media Type Selectors (5)===<br /> <br /> Both dropdown lists allows selecting a media type for question and/or answers. Question and/or answer could be textual, image or sound. Media type can be selected independantly for question and answers.<br /> <br /> ===Flip Answers and Questions (6)===<br /> <br /> Checking this box will swap question and answers so question become answers and reverse.<br /> <br /> ===Decks (7)===<br /> <br /> A number of decks can be choosen, from 2 to 4.<br /> <br /> Using 2 decks will be usefull for small sized cardset (up to more or less 12), or for memorizing easy things.<br /> <br /> The standard Leitner system uses 3 decks, that should be enough for medium size sets as vocabulary lists. Set size of 20 to 50 items should fit in the 3 decks system.<br /> <br /> 4 decks may be used for large lists, or for medium lists that present memorization difficulties (such as questionning with images that have a lot of semantics in, or very alike sounds). 4 decks should be used on a larger training period, as all cards must be able to go 3 decks down to complete the exercise.<br /> <br /> ===Enable Auto Downgrade (8)===<br /> <br /> If disabled, the cards will remain in their current deck forever (or until the game has not be reset by teacher). <br /> <br /> If enabled, the cards will jump up to a harder deck after a delay, if the student do not review the cards. Completing the exercise may be harder if there is no regularity in the memorisation work.<br /> <br /> ===Auto Downgrade Delay (9)===<br /> <br /> These fields will allow fixing the delay (in hours) the cards will jump up to a harder deck. The delay is counted relatively to the end of the review time.<br /> <br /> This delay can be setup distinctly for each deck.<br /> <br /> ===Review Triggering Delay (10)===<br /> <br /> These fields will allow setting the delay a user should come review the deck. The autodowngrade delay will start counting after this review delay is elapsed.<br /> <br /> This delay can be setup distinctly for each deck.</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_Configuration_Parameters&diff=38008 2008-06-21T17:05:44Z

<p>Vf: /* Auto Downgrade Delay (9) */</p> <hr /> <div>[[Flashcard module|back to index]]<br /> <br /> [[Image:flashcard_parameters.jpg]]<br /> <br /> ===Time range (1)===<br /> <br /> The time range parameters allow to define an aperture time slot for the module. If disabled, the module is available at any time, pursuant it is set to visible state.<br /> <br /> ===Question to Import (2)===<br /> <br /> You can ask the module to import a &quot;matching question&quot; from the question bank. You must check the &quot;force reload&quot; option to import the questions (see below).<br /> <br /> ===Force Reloading (3)===<br /> <br /> You must check this box to have question definitions imported within the flashcard question set.<br /> <br /> ===Customization (4)===<br /> <br /> This is not really a parameter, but some indications about how to customize the flashcard appearance. Teachers can use course files to change the stylesheet. Needs some very little skills in CSS.<br /> <br /> ===Media Type Selectors (5)===<br /> <br /> Both dropdown lists allows selecting a media type for question and/or answers. Question and/or answer could be textual, image or sound. Media type can be selected independantly for question and answers.<br /> <br /> ===Flip Answers and Questions (6)===<br /> <br /> Checking this box will swap question and answers so question become answers and reverse.<br /> <br /> ===Decks (7)===<br /> <br /> A number of decks can be choosen, from 2 to 4.<br /> <br /> Using 2 decks will be usefull for small sized cardset (up to more or less 12), or for memorizing easy things.<br /> <br /> The standard Leitner system uses 3 decks, that should be enough for medium size sets as vocabulary lists. Set size of 20 to 50 items should fit in the 3 decks system.<br /> <br /> 4 decks may be used for large lists, or for medium lists that present memorization difficulties (such as questionning with images that have a lot of semantics in, or very alike sounds). 4 decks should be used on a larger training period, as all cards must be able to go 3 decks down to complete the exercise.<br /> <br /> ===Enable Auto Downgrade (8)===<br /> <br /> If disabled, the cards will remain in their current deck forever (or until the game has not be reset by teacher). <br /> <br /> If enabled, the cards will jump up to a harder deck after a delay, if the student do not review the cards. Completing the exercise may be harder if there is no regularity in the memorisation work.<br /> <br /> ===Auto Downgrade Delay (9)===<br /> <br /> These fields will allow fixing the delay (in hours) the cards will jump up to a harder deck. The delay is counted relatively to the end of the review time.<br /> <br /> This delay can be setup distinctly for each deck.<br /> <br /> ===Review Triggering Delay (10)===<br /> <br /> These fields will allow setting the delay a user should come review the deck. The autodowngrade delay will start counting after this review delay is elapsed.<br /> <br /> This delay can be setup distinctly for each deck.</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_Configuration_Parameters&diff=38007 2008-06-21T17:03:55Z

<p>Vf: /* Enable Auto Downgrade (8) */</p> <hr /> <div>[[Flashcard module|back to index]]<br /> <br /> [[Image:flashcard_parameters.jpg]]<br /> <br /> ===Time range (1)===<br /> <br /> The time range parameters allow to define an aperture time slot for the module. If disabled, the module is available at any time, pursuant it is set to visible state.<br /> <br /> ===Question to Import (2)===<br /> <br /> You can ask the module to import a &quot;matching question&quot; from the question bank. You must check the &quot;force reload&quot; option to import the questions (see below).<br /> <br /> ===Force Reloading (3)===<br /> <br /> You must check this box to have question definitions imported within the flashcard question set.<br /> <br /> ===Customization (4)===<br /> <br /> This is not really a parameter, but some indications about how to customize the flashcard appearance. Teachers can use course files to change the stylesheet. Needs some very little skills in CSS.<br /> <br /> ===Media Type Selectors (5)===<br /> <br /> Both dropdown lists allows selecting a media type for question and/or answers. Question and/or answer could be textual, image or sound. Media type can be selected independantly for question and answers.<br /> <br /> ===Flip Answers and Questions (6)===<br /> <br /> Checking this box will swap question and answers so question become answers and reverse.<br /> <br /> ===Decks (7)===<br /> <br /> A number of decks can be choosen, from 2 to 4.<br /> <br /> Using 2 decks will be usefull for small sized cardset (up to more or less 12), or for memorizing easy things.<br /> <br /> The standard Leitner system uses 3 decks, that should be enough for medium size sets as vocabulary lists. Set size of 20 to 50 items should fit in the 3 decks system.<br /> <br /> 4 decks may be used for large lists, or for medium lists that present memorization difficulties (such as questionning with images that have a lot of semantics in, or very alike sounds). 4 decks should be used on a larger training period, as all cards must be able to go 3 decks down to complete the exercise.<br /> <br /> ===Enable Auto Downgrade (8)===<br /> <br /> If disabled, the cards will remain in their current deck forever (or until the game has not be reset by teacher). <br /> <br /> If enabled, the cards will jump up to a harder deck after a delay, if the student do not review the cards. Completing the exercise may be harder if there is no regularity in the memorisation work.<br /> <br /> ===Auto Downgrade Delay (9)===<br /> <br /> These fields will allow fixing the delay (in hours) the cards will jump up to a harder deck. The delay is counted relatively to the end of the review time.</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_Configuration_Parameters&diff=38006 2008-06-21T17:02:22Z

<p>Vf: /* Decks (7) */</p> <hr /> <div>[[Flashcard module|back to index]]<br /> <br /> [[Image:flashcard_parameters.jpg]]<br /> <br /> ===Time range (1)===<br /> <br /> The time range parameters allow to define an aperture time slot for the module. If disabled, the module is available at any time, pursuant it is set to visible state.<br /> <br /> ===Question to Import (2)===<br /> <br /> You can ask the module to import a &quot;matching question&quot; from the question bank. You must check the &quot;force reload&quot; option to import the questions (see below).<br /> <br /> ===Force Reloading (3)===<br /> <br /> You must check this box to have question definitions imported within the flashcard question set.<br /> <br /> ===Customization (4)===<br /> <br /> This is not really a parameter, but some indications about how to customize the flashcard appearance. Teachers can use course files to change the stylesheet. Needs some very little skills in CSS.<br /> <br /> ===Media Type Selectors (5)===<br /> <br /> Both dropdown lists allows selecting a media type for question and/or answers. Question and/or answer could be textual, image or sound. Media type can be selected independantly for question and answers.<br /> <br /> ===Flip Answers and Questions (6)===<br /> <br /> Checking this box will swap question and answers so question become answers and reverse.<br /> <br /> ===Decks (7)===<br /> <br /> A number of decks can be choosen, from 2 to 4.<br /> <br /> Using 2 decks will be usefull for small sized cardset (up to more or less 12), or for memorizing easy things.<br /> <br /> The standard Leitner system uses 3 decks, that should be enough for medium size sets as vocabulary lists. Set size of 20 to 50 items should fit in the 3 decks system.<br /> <br /> 4 decks may be used for large lists, or for medium lists that present memorization difficulties (such as questionning with images that have a lot of semantics in, or very alike sounds). 4 decks should be used on a larger training period, as all cards must be able to go 3 decks down to complete the exercise.<br /> <br /> ===Enable Auto Downgrade (8)===<br /> <br /> If disabled, the cards will remain in their current deck forever (or until the game has not be reset by teacher). <br /> <br /> If enabled, the cards will jump up to a harder deck after a delay, if the student do not review the cards. Completing the exercise may be harder if there is no regularity in the memorisation work.</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_Configuration_Parameters&diff=38005 2008-06-21T16:59:53Z

<p>Vf: /* Flip Answers and Questions (6) */</p> <hr /> <div>[[Flashcard module|back to index]]<br /> <br /> [[Image:flashcard_parameters.jpg]]<br /> <br /> ===Time range (1)===<br /> <br /> The time range parameters allow to define an aperture time slot for the module. If disabled, the module is available at any time, pursuant it is set to visible state.<br /> <br /> ===Question to Import (2)===<br /> <br /> You can ask the module to import a &quot;matching question&quot; from the question bank. You must check the &quot;force reload&quot; option to import the questions (see below).<br /> <br /> ===Force Reloading (3)===<br /> <br /> You must check this box to have question definitions imported within the flashcard question set.<br /> <br /> ===Customization (4)===<br /> <br /> This is not really a parameter, but some indications about how to customize the flashcard appearance. Teachers can use course files to change the stylesheet. Needs some very little skills in CSS.<br /> <br /> ===Media Type Selectors (5)===<br /> <br /> Both dropdown lists allows selecting a media type for question and/or answers. Question and/or answer could be textual, image or sound. Media type can be selected independantly for question and answers.<br /> <br /> ===Flip Answers and Questions (6)===<br /> <br /> Checking this box will swap question and answers so question become answers and reverse.<br /> <br /> ===Decks (7)===<br /> <br /> A number of decks can be choosen, from 2 to 4.<br /> <br /> Using 2 decks will be usefull for small sized cardset (up to more or less 12), or for memorizing easy things.<br /> <br /> The standard Leitner system uses 3 decks, that should be enough for medium size sets as vocabulary lists. Set size of 20 to 50 items should fit in the 3 decks system.<br /> <br /> 4 decks may be used for large lists, or for medium lists that present memorization difficulties (such as questionning with images that have a lot of semantics in, or very alike sounds). 4 decks should be used on a larger training period, as all cards must be able to go 3 decks down to complete the exercise.</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module&diff=38004 2008-06-21T16:54:27Z

<p>Vf: /* Features */</p> <hr /> <div>The '''flashcard module''' may be downloaded from http://download.moodle.org/plugins/mod/flashcard.zip .<br /> <br /> The flashcard module allows editing and playing flashcards. Flashcards are a &quot;memory training&quot; device that uses the concept of repetition. Checking a flashcard deck will present the student the couples of relationships to be memorized. More often the associations are reviewed, deeper the memorization will be engraved into our memorial circuits.<br /> <br /> ==Features==<br /> <br /> * Getting cards from a &quot;matching question&quot;<br /> * Editing cards<br /> * Multimedia cards: text, image, sound and image + sound together<br /> * Automated backpropagation of cards (can be disabled)<br /> * Customizable decks<br /> <br /> ==Configuration==<br /> <br /> [[Flashcard module: Configuration Parameters]]<br /> <br /> [[Flashcard module: Capabilities]]<br /> <br /> ==Screens==<br /> <br /> ===Student Screens=== <br /> <br /> *[[Flashcard module: Freeplay Screen|Freeplay Screen]]<br /> * Leitner Play Screens<br /> ** [[Flashcard module: Leitner Choose A Deck|Choose a deck to play with]]<br /> ** [[Flashcard module: Leitner Use A Deck|Use a deck]]<br /> <br /> ===Teacher Screens===<br /> <br /> * Summary Screens<br /> **[[Flashcard module: By User Summary|By User Summary]]<br /> **[[Flashcard module: By Card Summary|By Card Summary]]<br /> *[[Flashcard module: Edit Screen|Edit Screen]]<br /> <br /> == See also ==<br /> * [[Lesson#The_Flash_card_lesson|Flash card presentation]] in the [[Lesson module]] is an alternative to this module.<br /> * Using Moodle [http://moodle.org/mod/forum/view.php?id=7180 Flashcard module forum]<br /> <br /> [[Category:Contributed code]]</div>

Vf https://docs.moodle.org/test/index.php?title=File:flashcard_per_card_summary.jpg&diff=38003 2008-06-21T16:53:33Z

<p>Vf: </p> <hr /> <div></div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_By_Card_Summary&diff=38002 2008-06-21T16:53:20Z

<p>Vf: </p> <hr /> <div>[[Flashcard module|Back to index]]<br /> <br /> The &quot;per card&quot; summary should allow to check if a card is massively difficult to memorize, and other &quot;card&quot; related indications.<br /> <br /> [[Image:flashcard_per_card_summary.jpg]]</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_By_User_Summary&diff=38001 2008-06-21T16:51:38Z

<p>Vf: </p> <hr /> <div>[[Flashcard module|Back to index]]<br /> <br /> The &quot;per user&quot; summary will allow the teacher to check the memorisation progresses of the students. <br /> <br /> [[Image:flashcard_per_user_summary.jpg]]<br /> <br /> ==Knowing how many cards remain==<br /> <br /> In each user row, the decks will grow in height as much as they have many cards in. You can roll over the deck to get the exact card count in this deck.<br /> <br /> The display will show you as many decks than used in the flashcard configuration parameters.<br /> <br /> ==Knowing the lateness of a student==<br /> <br /> The clocks will tell you how many days the student has left before having to review a deck. If the student is late, Red clocks will tell how many days late was the student.<br /> <br /> ==Resetting a user==<br /> <br /> You may click on the reset button of a user to fully reset the Leitner deck. It will be considered has having seen no cards at all.<br /> <br /> ===Little hack : I don't want to see teacher's status in &quot;per user results&quot;===<br /> <br /> This is a little hack that needs uncomment just one line in the flashcard code (usersummaryview.php §35).</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_By_User_Summary&diff=38000 2008-06-21T16:47:02Z

<p>Vf: </p> <hr /> <div>[[Flashcard module|Back to index]]<br /> <br /> The &quot;per user&quot; summary will allow the teacher to check the memorisation progresses of the students. <br /> <br /> [[Image:flashcard_per_user_summary.jpg]]<br /> <br /> ==Knowing how many cards remain==<br /> <br /> In each user row, the decks will grow in height as much as they have many cards in. You can roll over the deck to get the exact card count in this deck.<br /> <br /> The display will show you as many decks than used in the flashcard configuration parameters.<br /> <br /> ==Knowing the lateness of a student==<br /> <br /> The clocks will tell you how many days the student has left before having to review a deck. If the student is late, Red clocks will tell how many days late was the student.<br /> <br /> ==Resetting a user==<br /> <br /> You may click on the reset button of a user to fully reset the Leitner deck. It will be considered has having seen no cards at all.</div>

Vf https://docs.moodle.org/test/index.php?title=File:flashcard_per_user_summary.jpg&diff=37999 2008-06-21T16:42:39Z

<p>Vf: </p> <hr /> <div></div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_By_User_Summary&diff=37998 2008-06-21T16:42:24Z

<p>Vf: </p> <hr /> <div>[[Flashcard module|Back to index]]<br /> <br /> The &quot;per user&quot; summary will allow the teacher to check the memorisation progresses of the students. <br /> <br /> [[Image:flashcard_per_user_summary.jpg]]</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module&diff=37997 2008-06-21T16:40:59Z

<p>Vf: /* Teacher Screens */</p> <hr /> <div>The '''flashcard module''' may be downloaded from http://download.moodle.org/plugins/mod/flashcard.zip .<br /> <br /> The flashcard module allows editing and playing flashcards. Flashcards are a &quot;memory training&quot; device that uses the concept of repetition. Checking a flashcard deck will present the student the couples of relationships to be memorized. More often the associations are reviewed, deeper the memorization will be engraved into our memorial circuits.<br /> <br /> ==Features==<br /> <br /> *Getting cards from a &quot;matching question&quot;<br /> *Editing cards<br /> *Multimedia cards: text, image and sound<br /> *Automated backpropagation of cards (can be disabled)<br /> * Customizable decks<br /> <br /> ==Configuration==<br /> <br /> [[Flashcard module: Configuration Parameters]]<br /> <br /> [[Flashcard module: Capabilities]]<br /> <br /> ==Screens==<br /> <br /> ===Student Screens=== <br /> <br /> *[[Flashcard module: Freeplay Screen|Freeplay Screen]]<br /> * Leitner Play Screens<br /> ** [[Flashcard module: Leitner Choose A Deck|Choose a deck to play with]]<br /> ** [[Flashcard module: Leitner Use A Deck|Use a deck]]<br /> <br /> ===Teacher Screens===<br /> <br /> * Summary Screens<br /> **[[Flashcard module: By User Summary|By User Summary]]<br /> **[[Flashcard module: By Card Summary|By Card Summary]]<br /> *[[Flashcard module: Edit Screen|Edit Screen]]<br /> <br /> == See also ==<br /> * [[Lesson#The_Flash_card_lesson|Flash card presentation]] in the [[Lesson module]] is an alternative to this module.<br /> * Using Moodle [http://moodle.org/mod/forum/view.php?id=7180 Flashcard module forum]<br /> <br /> [[Category:Contributed code]]</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_Leitner_Use_A_Deck&diff=37996 2008-06-21T16:28:01Z

<p>Vf: /* Reset Deck */</p> <hr /> <div>[[Flashcard module|Back to index]]<br /> <br /> Using a deck is that simple !! <br /> <br /> Start with first card. <br /> <br /> [[Image:flashcard_presented.jpg]]<br /> <br /> Guess the answer, searching in your own memory. You now just can check if you were right or wrong, clicking on the card to turn it round.<br /> <br /> [[Image:flashcard_turned.jpg]]<br /> <br /> Now you were really right or mistaken. The flashcard module just would like you tell it what how was your guess. You may cheat here, but there is far no interest in it... and would have no consequence.<br /> <br /> ==I got it !!==<br /> <br /> You were right, and tell the flashcard. This card will be stripped off the deck and will be added to the easier deck (or may stay in this deck if it is the easiest). You may be asked to review that card less often.<br /> <br /> ==I failed !!==<br /> <br /> You were wrong (and you know you were !). The card will be stripped off for that play, but remains in this cardset. You will have to review it next round. Make a little effort and try to find a way to memoize it.<br /> <br /> ==Reset Cardset== <br /> <br /> You can reload this deck to make a new play.</div>

Vf https://docs.moodle.org/test/index.php?title=Flashcard_module:_Leitner_Use_A_Deck&diff=37995 2008-06-21T16:27:45Z

<p>Vf: </p> <hr /> <div>[[Flashcard module|Back to index]]<br /> <br /> Using a deck is that simple !! <br /> <br /> Start with first card. <br /> <br /> [[Image:flashcard_presented.jpg]]<br /> <br /> Guess the answer, searching in your own memory. You now just can check if you were right or wrong, clicking on the card to turn it round.<br /> <br /> [[Image:flashcard_turned.jpg]]<br /> <br /> Now you were really right or mistaken. The flashcard module just would like you tell it what how was your guess. You may cheat here, but there is far no interest in it... and would have no consequence.<br /> <br /> ==I got it !!==<br /> <br /> You were right, and tell the flashcard. This card will be stripped off the deck and will be added to the easier deck (or may stay in this deck if it is the easiest). You may be asked to review that card less often.<br /> <br /> ==I failed !!==<br /> <br /> You were wrong (and you know you were !). The card will be stripped off for that play, but remains in this cardset. You will have to review it next round. Make a little effort and try to find a way to memoize it.<br /> <br /> ==Reset Deck== <br /> <br /> You can reload this deck to make a new play.</div>

Vf https://docs.moodle.org/test/index.php?title=File:flashcard_turned.jpg&diff=37994 2008-06-21T16:23:45Z

<p>Vf: </p> <hr /> <div></div>

Vf