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 -r1.1.2.1 -r1.1.2.2 --- openacs-4/packages/assessment/www/doc/display_types.adp 20 Aug 2015 17:36:21 -0000 1.1.2.1 +++ openacs-4/packages/assessment/www/doc/display_types.adp 25 Aug 2015 18:02:18 -0000 1.1.2.2 @@ -2,28 +2,32 @@ {/doc/assessment {Assessment}} {As_Item Display Types} As_Item Display Types - - -

Overview

Displaying items to users has a couple of +

Overview

+Displaying items to users has a couple of challanges. First of all the display of a single item can be different for each item_type (and even within a type). Second of all, the display of items within a section can be different from 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.

Note: please refer to the discussion -of Items here. That discussion +of assessment we are talking about. +

Note: please refer to the discussion +of Items here. That discussion complements the discussion here, and the data model graphic pertaining to the Item Display Types system is available there -also.

Item Display Types

Each item has an item_display_type object +also.

Item Display Types

+Each item has an item_display_type object associated with it, that defines how to display the item. Each item_display_type has a couple of attributes, that can be passed to the formbuilder for the creation of the widget. Each widget has at least one item_display_type associated with it. In the long run I think this system has the potential to become a part of OpenACS itself (storing additional display information for each acs_object), but we are not there yet :). Obviouslly we are talking -cr_item_types here as well.

Each item_display_type has a couple of -attributes in common.

Each item_display_type has a couple of +attributes in common.

item_display_type_id
item_type_name - name like "Select box, aligned right", stored in the name field of CR.
presentation_type - the type of "widget" @@ -50,14 +54,16 @@ defaults that ad_dateentrywidget expects: "" for "no date", "0" for "today", or else some specific date set by the author; see this example)

Depending on the presentation_types additonal +

Depending on the presentation_types additonal attributes (presentation_type attributes) 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 possibilities associated with each type (e.g. a textarea has width -and heigth..).

textbox - single-line typed entry
- abs_size - An abstraction of the real size value in "small","medium","large". Up to the developer how this @@ -109,23 +115,29 @@ but does need date validity check
- image_map - requires a linked image; the image map coordinates are handled as Item Choices
- file_upload - present a File box (browse button, file_name textbox, and submit button together) so user can upload a file
- many more
In addition, there are some potential presentation_types that +

In addition, there are some potential presentation_types that actually seem to be better modeled as a Section of separate -Items:

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).
...

Section +

Section display

Name: text. Name of the section like "test view sorted"
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 @@ -154,8 +166,8 @@ submitted will be treated as not being submitted at all.

section and assessment specification