Javascript-interface for repeat elements function - Revision history

Andrewnicols: Note about plan not to migrate this page to the new developer resources. See template for more info.

2022-06-24T13:51:26Z

Note about plan not to migrate this page to the new developer resources. See template for more info.

← Older revision		Revision as of 13:51, 24 June 2022
Line 1:		Line 1:
			{{Template:WillNotMigrate}}
	'''GOAL''': improve usability by using dynamic form editing.		'''GOAL''': improve usability by using dynamic form editing.

Gorelov.serj at 17:53, 21 October 2010

2010-10-21T17:53:51Z

← Older revision		Revision as of 17:53, 21 October 2010
Line 1:		Line 1:
	'''GOAL''': improve usability by using dynamic form editing.		'''GOAL''': improve usability by using dynamic form editing.

			'''PROBLEM''':
			* Adding blanks requires page reloading, if there are a lot of blanks with WYSIWYG it takes a lot of time to initialize them.
			* Changing blanks order is tedious.

	'''EXAMPLE''': let's imagine you have a multichoice question with 8 or more choices and the order of choices matters. Imagine you found you want add new choice at the start or delete first choice. With current interface you are in a BIG trouble.		'''EXAMPLE''': let's imagine you have a multichoice question with 8 or more choices and the order of choices matters. Imagine you found you want add new choice at the start or delete first choice. With current interface you are in a BIG trouble.

	~~At this moment form editing, especially adding new blank answers, units, choices and fields requires page reloading.~~
	~~Editing blanks order or blank removing is not possible without page reloading.~~

	'''TASK''': The main task is development of JavaScript-interface for repeat_elemens function. Other task is make ADD, REMOVE and MOVE actions without page reloading. If JavaScript is not available in user's browser this actions must work with page reloading, like it works now.		'''TASK''': The main task is development of JavaScript-interface for repeat_elemens function. Other task is make ADD, REMOVE and MOVE actions without page reloading. If JavaScript is not available in user's browser this actions must work with page reloading, like it works now.
Line 61:		Line 62:
	Blanks moving is available by dragging them with move button.		Blanks moving is available by dragging them with move button.
	Blank's original order will be reported on saving , by using hidden elements, named "ord", which will save order number of each blank. You could use it to determine where each element is go (even if edited). This is useful, for example, when editing question with existing attempts: saving procedure would know new indexes of all previous answers even if they are moved AND their content edited, so it could ajust student's responses accordingly.		Blank's original order will be reported on saving , by using hidden elements, named "ord", which will save order number of each blank. You could use it to determine where each element is go (even if edited). This is useful, for example, when editing question with existing attempts: saving procedure would know new indexes of all previous answers even if they are moved AND their content edited, so it could ajust student's responses accordingly.


	For example:		For example:
Line 79:		Line 81:

	So, the saving procedure would know that answer number 1 is deleted and answers number 0 and 2 changed their places.		So, the saving procedure would know that answer number 1 is deleted and answers number 0 and 2 changed their places.

			Besides, when user change blanks order, script changes names of fields of every blank. So in every moment names of blanks will be in order, that's why server-side will save them in the same order.

	== Function Interface ==		== Function Interface ==

Gorelov.serj at 18:15, 14 October 2010

2010-10-14T18:15:32Z

← Older revision		Revision as of 18:15, 14 October 2010
Line 86:		Line 86:
	In original vewrsion this names were separated and saved in two params: $repeathiddenname and $addfieldsname.		In original vewrsion this names were separated and saved in two params: $repeathiddenname and $addfieldsname.
	This preliminary change, simplifying the interface and helps to solve the basic problem without changing it.		This preliminary change, simplifying the interface and helps to solve the basic problem without changing it.
			--[[User:Сергей Горелов\|Сергей Горелов]] 18:15, 14 October 2010 (UTC)

Oasychev: /* Moving blanks */ - clearifying example

2010-10-13T21:41:47Z

Moving blanks: - clearifying example

← Older revision		Revision as of 21:41, 13 October 2010
Line 60:		Line 60:

	Blanks moving is available by dragging them with move button.		Blanks moving is available by dragging them with move button.
	Blank's original order will be ~~preserved~~ , by using hidden elements, named "ord", which will save order number of each blank.		Blank's original order will be reported on saving , by using hidden elements, named "ord", which will save order number of each blank. You could use it to determine where each element is go (even if edited). This is useful, for example, when editing question with existing attempts: saving procedure would know new indexes of all previous answers even if they are moved AND their content edited, so it could ajust student's responses accordingly.

	For example:		For example:
Line 76:		Line 76:
	We add two blanks. We've got ords: 0,2,-1,-1		We add two blanks. We've got ords: 0,2,-1,-1
	Moving:		Moving:
	We move last blank ~~betwen~~ first ~~and second~~. Ords: 0,-1,2,-1		We move last blank to be first. Ords: -1,0,2,-1

	So, ~~when we create or add new blanks, initial values of their ords are -~~1~~. When we load blanks, which were saved earlier, their ord's values are~~ 0~~,1,~~2~~,3...,n~~ .		So, the saving procedure would know that answer number 1 is deleted and answers number 0 and 2 changed their places.

	== Function Interface ==		== Function Interface ==

Oasychev: Example where it useful set

2010-10-13T21:35:40Z

Example where it useful set

← Older revision		Revision as of 21:35, 13 October 2010
Line 1:		Line 1:
	'''GOAL''': improve usability by using dynamic form editing.		'''GOAL''': improve usability by using dynamic form editing.

			'''EXAMPLE''': let's imagine you have a multichoice question with 8 or more choices and the order of choices matters. Imagine you found you want add new choice at the start or delete first choice. With current interface you are in a BIG trouble.

	At this moment form editing, especially adding new blank answers, units, choices and fields requires page reloading.		At this moment form editing, especially adding new blank answers, units, choices and fields requires page reloading.

Gorelov.serj: /* Moving blanks */

2010-10-13T20:00:59Z

Moving blanks

@@ Line 58: / Line 58: @@
 Blanks moving is available by dragging them with move button.
-Blank's original order will be preserved , by using hidden elements, which will save order number of each blank.
+Blank's original order will be preserved , by using hidden elements, named "ord", which will save order number of each blank.
 == Function Interface ==

Gorelov.serj at 20:13, 11 October 2010

2010-10-11T20:13:42Z

← Older revision		Revision as of 20:13, 11 October 2010
Line 45:		Line 45:
	*PASSWORD and PASSWORDUNMASK		*PASSWORD and PASSWORDUNMASK
	A password element. Empty, when it doesn't contains any text.		A password element. Empty, when it doesn't contains any text.
	*TEXT		TEXT
	Simple text input element. Empty, when it doesn't contains any text.		Simple text input element. Empty, when it doesn't contains any text.
	*TEXTAREA		*TEXTAREA
Line 59:		Line 59:
	Blanks moving is available by dragging them with move button.		Blanks moving is available by dragging them with move button.
	Blank's original order will be preserved , by using hidden elements, which will save order number of each blank.		Blank's original order will be preserved , by using hidden elements, which will save order number of each blank.

			== Function Interface ==

			Interface of repeat_elements function will receive 7 params instead of 8 in original version.
			New param $prefix gets prefix for additional form elements, added by the repeat_elements function.
			In original vewrsion this names were separated and saved in two params: $repeathiddenname and $addfieldsname.
			This preliminary change, simplifying the interface and helps to solve the basic problem without changing it.

Gorelov.serj: /* Moving blanks */

2010-10-11T19:59:52Z

Moving blanks

← Older revision		Revision as of 19:59, 11 October 2010
Line 57:		Line 57:
	== Moving blanks ==		== Moving blanks ==

	Blanks moving is available by dragging them with move button		Blanks moving is available by dragging them with move button.
	~~At any moment you can set all your blanks in default positions~~, using ~~button "Restore~~ order"		Blank's original order will be preserved , by using hidden elements, which will save order number of each blank.

Gorelov.serj: /* Removing blanks. */

2010-10-11T19:47:32Z

Removing blanks.

← Older revision		Revision as of 19:47, 11 October 2010
Line 54:		Line 54:
	Blank's removing realize by pushind remove button(see screenshot) and confirming your choise.		Blank's removing realize by pushind remove button(see screenshot) and confirming your choise.
	If blank's removing isn't possible user will get allert with reason.		If blank's removing isn't possible user will get allert with reason.
	~~[[Image:remove.jpg]]~~

	== Moving blanks ==		== Moving blanks ==

Gorelov.serj: /* Moving blanks */

2010-10-11T19:47:02Z

Moving blanks

← Older revision		Revision as of 19:47, 11 October 2010
Line 59:		Line 59:

	Blanks moving is available by dragging them with move button		Blanks moving is available by dragging them with move button
	~~[[Image:move.jpg]]~~
	At any moment you can set all your blanks in default positions, using button "Restore order"		At any moment you can set all your blanks in default positions, using button "Restore order"