Index: openacs-4/packages/assessment/www/doc/display_types.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/display_types.adp,v
diff -u -N -r1.1.2.4 -r1.1.2.5
--- openacs-4/packages/assessment/www/doc/display_types.adp	9 Jun 2016 13:03:12 -0000	1.1.2.4
+++ openacs-4/packages/assessment/www/doc/display_types.adp	4 Jul 2016 11:33:12 -0000	1.1.2.5
@@ -10,11 +10,11 @@
 assessment to assessment. Last but not least, the whole assessment
 might be displayed differently depending on attributes and the type
 of assessment we are talking about.</span>
-<p><span class="context"><strong><em>Note: please refer to the discussion
-of Items <a href="as_items">here</a>. That discussion
-complements the discussion here, and the data model graphic
-pertaining to the Item Display Types system is available there
-also.</em></strong></span></p>
+<p><span class="context"><strong><em>Note: please refer to the
+discussion of Items <a href="as_items">here</a>. That
+discussion complements the discussion here, and the data model
+graphic pertaining to the Item Display Types system is available
+there also.</em></strong></span></p>
 <h2><span class="context">Item Display Types</span></h2>
 <span class="context">Each item has an item_display_type object
 associated with it, that defines how to display the item. Each
@@ -28,60 +28,63 @@
 <p><span class="context">Each item_display_type has a couple of
 attributes in common.</span></p>
 <ul>
-<li><span class="context">item_display_type_id</span></li><li><span class="context">item_type_name - name like "Select box,
-aligned right", stored in the name field of CR.<br>
-</span></li><li><span class="context">presentation_type - the type of "widget"
-displayed when the Item is output in html. There are many types we
-should support beyond the stock html types. We are talking <a href="../../../acs-templating/www/doc/widgets/index">ACS Templating
+<li><span class="context">item_display_type_id</span></li><li><span class="context">item_type_name - name like "Select
+box, aligned right", stored in the name field of
+CR.<br>
+</span></li><li><span class="context">presentation_type - the type of
+"widget" displayed when the Item is output in html. There
+are many types we should support beyond the stock html types. We
+are talking <a href="../../../acs-templating/www/doc/widgets/index">ACS Templating
 widgets</a> here.<br>
 </span></li><li>
 <span class="context">item_answer_alignment - the orientation
 between the "question part" of the Item (the
-item_text/item_subtext) and the "answer part" -- the native Item
-widget (eg the textbox) or the 1..n choices. Alternatives
-accommodate L-&gt;R and R-&gt;L alphabets (or is this handled
-automagically be Internationalization?) and include:</span><ol>
-<li><span class="context">beside_left - the "answers" are left of
-the "question"</span></li><li><span class="context">beside_right - the "answers" are right of
-the "question"</span></li><li><span class="context">below - the "answers" are below the
-"question"</span></li><li><span class="context">above - the "answers" are above the
-"question"</span></li>
+item_text/item_subtext) and the "answer part" -- the
+native Item widget (eg the textbox) or the 1..n choices.
+Alternatives accommodate L-&gt;R and R-&gt;L alphabets (or is this
+handled automagically be Internationalization?) and include:</span><ol>
+<li><span class="context">beside_left - the "answers" are
+left of the "question"</span></li><li><span class="context">beside_right - the "answers"
+are right of the "question"</span></li><li><span class="context">below - the "answers" are below
+the "question"</span></li><li><span class="context">above - the "answers" are above
+the "question"</span></li>
 </ol>
 </li><li><span class="context">html_display_options - field to specify
 other stuff like textarea dimensions ("rows=10 cols=50"
 eg)</span></li><li><span class="context"><span class="context"><span class="reg">as_item_default - optional field that sets what the as_item
 will display when first output (eg text in a textbox; eg the
-defaults that ad_dateentrywidget expects: "" for "no date", "0" for
-"today", or else some specific date set by the author; see <a href="http://www.epimetrics.com/groups/Bay%20Area%20OpenACS%20Users%20Group/questionnaires/index#Date%20Test">
+defaults that ad_dateentrywidget expects: "" for "no
+date", "0" for "today", or else some
+specific date set by the author; see <a href="http://www.epimetrics.com/groups/Bay%20Area%20OpenACS%20Users%20Group/questionnaires/index#Date%20Test">
 this example</a>)</span></span></span></li>
 </ul>
 <p>Depending on the presentation_types <font color="red">additonal
 attributes (presentation_type attributes)</font> come into play
 (are added as attributes to the CR item type) (mark: this is not
 feature complete. It really is up to the coder to decide what
 attributes each widget should have, down here are only
-*suggestions*). Additionally we're not mentioning all HTML
+*suggestions*). Additionally we&#39;re not mentioning all HTML
 possibilities associated with each type (e.g. a textarea has width
 and heigth..).</p>
 <ul>
 <li>textbox - single-line typed entry
 <ul><li>abs_size - An abstraction of the real size value in
-"small","medium","large". Up to the developer how this
-translates.</li></ul>
+"small","medium","large". Up to the
+developer how this translates.</li></ul>
 </li><li>text area - multiple-line typed entry
 <ul><li>abs_size - An abstraction of the real size value in
-"small","medium","large". Up to the developer how this
-translates.</li></ul>
+"small","medium","large". Up to the
+developer how this translates.</li></ul>
 </li><li>radiobutton - single-choice multiple-option
 <ul>
 <li>choice_orientation - the pattern by which 2..n Item Choices are
-laid out when displayed. Note that this isn't a purely stylistic
-issue better left to the .adp templates or css; the patterns have
-semantic implications that the Assessment author appropriately
-should control here. Note also that Items with no Choices (eg a
-simple textbox Item) has no choice_orientation, but handles the
-location of that textbox relative to the Item label by the
-item_alignment option (discussed below).
+laid out when displayed. Note that this isn&#39;t a purely
+stylistic issue better left to the .adp templates or css; the
+patterns have semantic implications that the Assessment author
+appropriately should control here. Note also that Items with no
+Choices (eg a simple textbox Item) has no choice_orientation, but
+handles the location of that textbox relative to the Item label by
+the item_alignment option (discussed below).
 <ol>
 <li>horizontal - all Choices are in one line</li><li>vertical - all Choices are in one column</li><li>matrix_col-row - Choices are laid out in matrix, filling first
 col then row</li><li>matrix_row-col -Choices are laid out in matrix, filling first
@@ -95,15 +98,16 @@
 <li>choice_orientation (see above)</li><li>allow_multiple_p - Is it allow to select multiple values ?</li><li>sort_order: Numerical, alphabetic, randomized or by order of
 entry (sort_order field).</li>
 </ul>
-</li><li>select - multiple-option displayed in "popup menu"</li><li style="list-style: none"><ul>
+</li><li>select - multiple-option displayed in "popup
+menu"</li><li style="list-style: none"><ul>
 <li>sort_order: Numerical, alphabetic, randomized or by order of
 entry (sort_order field).</li><li><span class="context"><span class="reg">allow_multiple_p - Is
 it allow to select multiple values ?</span></span></li>
 </ul></li><li>multiple-choice-other: Consider, for instance, a combo box that
 consists of a radiobutton plus a textbox -- used for instance when
-you need a check "other" and then fill in what that "other" datum
-is. In effect this is a single Item but it has two different forms:
-a radiobutton and a textbox.
+you need a check "other" and then fill in what that
+"other" datum is. In effect this is a single Item but it
+has two different forms: a radiobutton and a textbox.
 <ul>
 <li>other_size: size of the other text field.</li><li>other_label: label (instead of "other").</li><li>display_type: What display type should be used for the
 multiple-choice-part ?</li>
@@ -121,11 +125,11 @@
 Items:</p>
 <ul>
 <li>ranking - a set of alternatives each need to be assigned an
-exclusive rank ("Indicate the order of US Presidents from bad to
-worse"). Is this one Item with multiple Item Choices? Actually,
-not, since each alternative has a value that must be separately
-stored (the tester would want to know that the testee ranked GWB
-last, for instance).</li><li><font color="red">...</font></li>
+exclusive rank ("Indicate the order of US Presidents from bad
+to worse"). Is this one Item with multiple Item Choices?
+Actually, not, since each alternative has a value that must be
+separately stored (the tester would want to know that the testee
+ranked GWB last, for instance).</li><li><font color="red">...</font></li>
 </ul>
 <h2><a name="section_display" id="section_display">Section
 display</a></h2>
@@ -138,12 +142,13 @@
 The section display page will be made up of the following
 attributes:<br>
 <ul>
-<li>Name: text. Name of the section like "test view sorted"</li><li>Number of questions per page: integer. THIS HAS TO BE CHANGED
+<li>Name: text. Name of the section like "test view
+sorted"</li><li>Number of questions per page: integer. THIS HAS TO BE CHANGED
 IN THE DATAMODELL FROM PAGINATION_STYLE. How many questions shall
 be displayed per page in this section. Usually the answer would be
-"" for all questions on one page (default), or "1" for one question
-per page (aka one question at a time), but any number is
-imagineable.</li><li>
+"" for all questions on one page (default), or
+"1" for one question per page (aka one question at a
+time), but any number is imagineable.</li><li>
 <span class="context"><span class="reg">ADP style: ADP to
 choose from that will control the makeup of the section along with
 the option to create a new one and a link to edit existing ones
@@ -159,11 +164,12 @@
 broken on purpose and result in an error.<br>
 </li><li>Submit Answer seperately: boolean. Shall each answer be
 answered seperately, even if we display multiple answers? If yes,
-display a "save" button next to each answer along with green "V" if
-the answer has been already submitted. To finish the section, you
-still have to click on the OK button at the buttom. Once the
-section is finished all answers that have not been seperatly
-submitted will be treated as not being submitted at all.<br>
+display a "save" button next to each answer along with
+green "V" if the answer has been already submitted. To
+finish the section, you still have to click on the OK button at the
+buttom. Once the section is finished all answers that have not been
+seperatly submitted will be treated as not being submitted at
+all.<br>
 </li>
 </ul>