Known issues and upcoming features for Template 2.0

I update this list to remind myself what needs doing. It changes and is probably incomplete. Let me know if you want something added or want to help with anything, even if it's just testing whether it works with different browsers. Also, let me know if you want to use it, but one of these issues prevents you from doing so — some of these are easy to fix and you may just need to prod me a little.

Known issues, to do, upcoming features:

Priority: low, medium, high

Saving groups for between-subject design does not work yet. (Should be easy to fix, but I currently don't need it. Tell me if you do.)
Currently does not work without any cases (i.e. Cases = "";) (skips last page with demographics questions) (will fix this when I need it)
Needs to be tested with different browsers — maybe you can help? I always test in Firefox 3, but I've made some changes since testing with the following browsers, so some of this may be out of date:
- works with Firefox 3
- seems to work with Opera 9
- seems to work with Safari 4
- seems to work with Google Chrome 2
- seems to work with Internet Explorer 7
- Test with IE 8
- Test with IE 6
- let me know if you find it to work/ not work with other browsers.
Add option to present cases randomized but with different pages with questions adjacent to each other, like this:

Cases 2 2 2 0 0 0 1 1 1

Page w/ questions 0 1 2 0 1 2 0 1 2
Add ability to insert pages without questions between cases.
Setting "Force = false" now skips the questions correctly in the data file, but it also skips the header for omitted questions. This means if the first subject skips any questions, these questions will not have variable names written to the data file.
Support more answer formats:
- text input fields
- checkboxes that allow multiple answers
- Change radioline answer format so that researcher can pick number of answer points
- drag-and-drop for sorting answers by priority (v low priority)
Filter questions
Rewrite to use the newly discovered shuffle() function to make code more efficient
Implement regex test to check email address and age before submitting to saveform2.php
Add ability to define custom variable name for each question (currently, questions get variable names assigned automatically using a "Case_1_page_2_question_1" pattern).
Look at how times get saved (function SaveTime(x)).
- Jon's method apparently saves time for every question as difference from when page with questions was loaded, which sets time1, so times become progressively longer for each subsequent question (check whether this is true).
- I changed this so that SaveTime also resets time1, to get time difference between questions.
- However, since SaveTime gets called by onClick for each button, this means that saved times will be too short if participant changes her mind about an answer, or if she navigates buttons using arrows instead of tabs.

How you can help

Contact me and ...

... let me know if you use it or are interested in using it.
If you use it, give me feedback, both positive and negative.
Let me know any pointers how to get it to work with Internet Explorer.
Test it and let me know any issues you find.
Tell me what you would like to be able to do ("feature requests").

Cases	2	2	2	0	0	0	1	1	1
Page w/ questions	0	1	2	0	1	2	0	1	2