Home
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas

Contributor mdekker on the Templates category

Individual CSS for each survey  
Written by mdekker the 1 Mar 10 at 10:42. Related project: 1.x all. New
When you want to style question for an individual survey you have to manually include a css file or edit the overall template. It would be nice to have additional, surveyspecific CSS in a separate CSS file that can be edited from the survey screen instead of from the template editor.
2
votes
up equal down
Solution #1: Include a surveyid.css
Written by mdekker the 1 Mar 10 at 10:42.
Have the template check if a .css exists and include it when it does. (could be generated for a new survey but left blank initially)

Add an edit survey css button to the survey toolbar where one can jump to a special template editor screen where you can edit this sid.css
Would be nice if there were links in the screen to point people to the appropriate item in the wiki for help.
2
votes
up equal down
Solution #2: Name the body with the survey id
Written by Shnoulle the 19 Mar 10 at 01:31.
More simple :

body class survey#SID group#ID (if by group/question) question#ID (if by question)

Add a comment or propose a solution >>

Harmonization of navigation buttons  
Written by apps the 23 Feb 10 at 14:39. Related project: 1.x all. In development
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.
4
votes
inprogress
Selected solution (#1): Transform Exit&Clear into < input>
Written by apps the 23 Feb 10 at 14:39.
This way, the less effort is required, since the other action are already unified into a < input> tag

At the end, all possible actions will be < input>s.

Add a comment or propose a solution >>