Development:Progressive Disclosure Implementation: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 3: | Line 3: | ||
{{Work in progress|info=<br /><br />''To give new developers a head start, add advice here on how to implement the recommended elements.'' (Of course, the APIs should be good enough to not require lots of extra code.) <br /><br /> | {{Work in progress|info=<br /><br />''To give new developers a head start, add advice here on how to implement the recommended elements.'' (Of course, the APIs should be good enough to not require lots of extra code.) <br /><br /> | ||
As an usability practitioner, this | As an usability practitioner, the implementation pages like this are where I am hoping to have developers have a play: there is probably some documentation available already about how to implement many of these things, but the developers who are already 'in' know how to find it best. <br /><br /> | ||
So add links to appropriate places - or if need be, implementation pages like this are perfect placeholders to put also new information about how to implement the recommended moodle UI elements. --[[User:Olli Savolainen]] 22:20, 3 June 2009 (UTC)}} | So add links to appropriate places - or if need be, implementation pages like this are perfect placeholders to put also new information about how to implement the recommended moodle UI elements. --[[User:Olli Savolainen]] 22:20, 3 June 2009 (UTC)}} |
Revision as of 14:30, 4 June 2009
Implementation instructions for Progressive Disclosure
Note: This article is a work in progress. Please use the page comments or an appropriate moodle.org forum for any recommendations/suggestions for improvement.
To give new developers a head start, add advice here on how to implement the recommended elements. (Of course, the APIs should be good enough to not require lots of extra code.)
As an usability practitioner, the implementation pages like this are where I am hoping to have developers have a play: there is probably some documentation available already about how to implement many of these things, but the developers who are already 'in' know how to find it best.
So add links to appropriate places - or if need be, implementation pages like this are perfect placeholders to put also new information about how to implement the recommended moodle UI elements. --Olli Savolainen 22:20, 3 June 2009 (UTC)
Simple progressive disclosure in a form
This will store the information in a session, about in which state the form was left, so if you press the 'Show advanced' button once, you will see the advanced controls shown anytime you come back to the form.
How to access this screen
- Create a quiz in a course, and open it. The configuration form will be shown
- Alternatively, open an existing quiz as a teacher and press the "Update this quiz" button
Address of this example in your Moodle
Assuming the quiz in question has the module id of 2, the address is:
/course/modedit.php?update=2&return=1
(add a link here to an actual demo installation? if so, that would have to keep its urls forever, i.e. probably have a moodle version installed that doesn't get upgraded)
The location of the code for this implementation
Please fill in location(s) in either http://cvs.moodle.org/ or in the code cross-reference (the latter is probably more useful), specifying the Moodle version where this information applies.
Implementation How-to
This example uses Moodle Formslib.
Please fill in, copying information as necessary from Development_talk:Progressive_Disclosure#Examples, specifying the Moodle version(s) where this information applies.