Editors Structure

[marco9446]

Editors Structure

The idea is to maintain the structure of the current editor with some small changes.

• Create an editor for each question
• Create reusable components for shared code
• hard-code properties for each editor inside the editor itself
• Have the ability to check the code of the question generated by the editor

The question properties should be an array which contains one object for each property with the following attributes:

var questionProperties=[
  {
    name:  <property name>
    label: OPTIONAL < property's name shown  to users. if not specified will be used the 'name' attribute >
    type:  < Boolean | Number | String | Enum  > ,
    widgetType: OPTIONAL < colour | richText  | range | code | text-code>
    description: OPTIONAL  <property description> ,
    default: OPTIONAL <default property value, if type == Enum will bean array of strings>
    referenceId: * OPTIONAL  <id of the item you want to apply this property> ,
    value:  <return the value of the property. Useful for data binding>
    isAdvancedProperty: <is visible only to advanced users>
    isAdvancedUser: <property use to set the level of the user>
  },
  {...},
  {...},
  {...}
]
*referenceId can be avoided using polymer data binding in declarative way

Each editor should contains the asq-stem and the asq-solution components and a way to modify them. In order to insert the solution the editor should have two 'modes' one for the creation of the question and the other where the user should answer the question in the correct way and save the state.

To prevent an overflow of informations to the user, there should be an option to enable or disable the view of the most advanced properties

Multi choice editor (asq-multi-choice-q)

questionProperties

• Non advanced properties
  • disabled
  • Multi
• Advanced properties
  • value
  • attrForSelected
  • selectedAttribute
  • selectable
  • selectedClass
  • selected
  • selectedValues

    Common characteristics

• Ability to insert, edit and remove text or code snippets as question description

  Specific characteristics

• create, sort, delete and edit multi choice options

  Text editor (asq-text-input-q)

  questionProperties

• Non advanced properties
  • label
  • disabled
  • value
• Advanced properties
  • floatingLabel

    Common characteristics

• Ability to insert, edit and remove text or code snippets as question description

  Highlight editor (asq-highlight-q)

  questionProperties

• Non advanced properties
  • fontSize
  • disabled
  • mode
  • tabSize
  • theme
• Advanced properties
  • value
  • wrap
  • aceValue

    Common characteristics

• Ability to insert, edit and remove text as question description

  Specific characteristics

• Ability to insert, sort, edit and remove colour variables
• Ability to select code to answer the question

  Rating editor (asq-rating-q)

  Specific characteristics

• Ability to insert, sort and remove asq-rating-item and change their name, disable and rating attributes

  Buckets editor (asq-buckets-q)

  questionProperties

• Non advanced properties
  • disabled
  • mode
• Advanced properties
  • attrForMatched
  • xMatchable
  • yMatchable
  • matchedClass
  • matchedAttribute
  • xBucket
  • yLabel

    Specific characteristics

• Ability to insert and remove Buckets and labels

[triglian]

Looks good. Some comments:

• the type of the questionProperties array should accept the same values as the Polymer property types, but you can add enum if you want. You can have a widget or widgetType property that indicates whether it's rich text etc.
• Some properties should have more user-friendly names when displayed in the editors.
• <asq-text-input-q>: ability to connect to an <asq-text-input-q-stats> element.
• there's still <asq-code-q>, <asq-fiddle-q>, <asq-js-function-body-q>, <asq-sqlite-q> and asq-order-q. Maybe they worth taking a look at.