Switch Button - Revision history

Sarjona: This page will not be migrated to new devdocs

2022-05-27T14:56:23Z

This page will not be migrated to new devdocs

← Older revision		Revision as of 14:56, 27 May 2022
Line 1:		Line 1:
			{{Template:WillNotMigrate}}

	[[ Moodle User Interface Guidelines\|Moodle User Interface Guidelines]] > '''Guideline template'''		[[ Moodle User Interface Guidelines\|Moodle User Interface Guidelines]] > '''Guideline template'''

Pilpi: /* Solution */

2009-07-11T11:01:19Z

Solution

← Older revision		Revision as of 11:01, 11 July 2009
Line 23:		Line 23:
	** Does not reflect the current state but users have to guess		** Does not reflect the current state but users have to guess
	* An element (link/button) that shows the status		* An element (link/button) that shows the status
	** Button/link text should always reflect the target state		** Button/link text should always reflect the target state, variation confuses
	* Combination; first show status and then a button to change: Edit mode: On [Turn off]		* Combination; first show status and then a button to change: Edit mode: On [Turn off]
	** Takes more space		** Takes more space

Pilpi: /* Forces: factors that affect selection */

2009-07-11T10:58:26Z

Forces: factors that affect selection

← Older revision		Revision as of 10:58, 11 July 2009
Line 10:		Line 10:

	== Context ==		== Context ==
	== Forces: factors that affect selection ==		== Forces (factors that affect selection) ==

	* A form with a submit button may clutter up the user interface too much		* A form with a checkbox and a submit button may clutter up the user interface too much
	* The user needs to see what state the setting/mode is in currently		* The user needs to see what state the setting/mode is in currently
	* The user needs to be able to predict what will be the resulting state when after they click the control		* The user needs to be able to predict what will be the resulting state when after they click the control

Pilpi: New page: Moodle User Interface Guidelines > '''Guideline template''' {{Work in progress|forumurl=http://moodle.org/mod/forum/discuss.php?d=126884|...

2009-07-11T10:57:02Z

New page: Moodle User Interface Guidelines > '''Guideline template''' {{Work in progress|forumurl=http://moodle.org/mod/forum/discuss.php?d=126884|...

New page

[[ Moodle User Interface Guidelines|Moodle User Interface Guidelines]] > '''Guideline template'''

{{Work in progress|forumurl=http://moodle.org/mod/forum/discuss.php?d=126884|info=<br /><br />'''This is a guideline for a [[Moodle_User_Interface_Guidelines|Moodle Interface Guidelines]]. Comments: [http://moodle.org/mod/forum/discuss.php?d=126884 developer forum thread] '''}}
== Problem ==
There is a setting/mode that users need to switch on or off, but there is no space for a form with a submit button.

Example: [[Progressive_Disclosure#Problem|Progressive disclosure#Problem]]

Further information: [http://www.hillside.net/patterns/writing/patterns.htm#B.1 Mandatory Elements Present]

== Context ==
== Forces: factors that affect selection ==

* A form with a submit button may clutter up the user interface too much
* The user needs to see what state the setting/mode is in currently
* The user needs to be able to predict what will be the resulting state when after they click the control

== Solution ==
UNSOLVED. One of the alternatives need to be determined as Moodle standard so users will know what to expect.

Alternatives:
* An element, the label of which describes the end state: [Turn off edit mode]
** Does not reflect the current state but users have to guess
* An element (link/button) that shows the status
** Button/link text should always reflect the target state
* Combination; first show status and then a button to change: Edit mode: On [Turn off]
** Takes more space
* Replace toggle buttons but AJAX-based forms that appear with a click of a "Settings" link

== Examples and implementation ==

== Related issues in the tracker ==

== (Optional) Further information / Sources ==