All possible transitions (of pages, of state) a survey can undergo by user interaction are:
- start
- resume a survey
- save the survey
- cancel and exit
- go prev
- go next
- end

The state of the art is a non-homogeneous implementation:
- Exit and clear = < a> tag with a fixed url carrying a crucial get parameter
- Load unfinished = < input> tag with type="submit" and crucial value "Load unfinished survey"
- Save = < input> tag with type="submit" and crucial value "saveall"
- < < prev = < input> tag with type="Submit" and crucial value "< < Prev"
- next>> = < input> tag with type="Submit" and crucial value "Next>>"
- start = < input> tag with type "Submit" and crucial value "movenext"
- end = < input> tag with type "submit". Value unknown at the time of writing this.

These should be harmonized: use the same tag and discriminate over one (single) parameter.

template.js is the natural place of all user javascripts

BASIC TEMPLATE has the peculiarity of not using template.js because it lacks the proper inclusion of it.

In the Template Editor, template.js is always shown, even if it's not called inside *pstpl. When editing BASIC template, you can edit template.js, bit it will not be loaded at runtime.

I suggest to make it crystal clear that this is the default behavior.
If not, the user may waste time in debug & design, until he notices that his javascripts are not there and fix the basic template.
Also, COPYING BASIC for your own work will result in inactivated template.js, so the issue reinforces itself in the copies/clones