source: Dev/trunk/TODO.txt @ 433

Todo
====

 * scale with multiple questions/items
   - create a configuration version of the widget (either built-in or
     separate) with click-to-edit labels (indicate by border, hover text?)
     and an extra 'Click to add row' in the text column.
   - make items in configuration an object, so you can add meta-data
 * export answers for a survey run
 * write a spec for the codes

Checklist
=========

 * Form validation
 * Input validation & escaping
 * Output escaping
 * Review current JSON formats, do they allow for extension or extra meta-data?
 
Open issues
===========

 * Do different inputs in one question get different codes? E.g. in 
   To ease exporting into other programs and easy communication, the codes
   are important I think. It should be easy to pronounce, and easy to
   find in the tool (people might get a dataset and not know where it
   came from).
 * What if a question is included in a survey multiple times. Use block
   or allow a pre/post-fix on the code to differentiate it.
   Should not be too much work, so if an scale with 5 items has 5 codes,
   you should be able to set a prefix on all of them at once.