Written by evan the 28 Apr 10 at 05:04.

In the 'Edit survey settings' > 'Presentation & navigation' tab add a yes/no drop down titled "Display question codes" This would then be checked when populating the template then apply if 'yes'

In the 'Edit survey settings' > 'Presentation & navigation' tab add a yes/no drop down titled "Display question codes" This would then be checked when populating the template then apply if 'yes'

Written by Shnoulle the 23 Mar 10 at 12:11.

We can use some value of semantic, for example : span , div , p , strong , em in code with some class.

For errormandatory, just a <strong class="errormandatory"> and just one thing for all.

Problem : template had to be modified : if the semantic way is good enough, we can just look at default and limespired template.

We can use some value of semantic, for example : span , div , p , strong , em in code with some class. For errormandatory, just a &lt;strong class="errormandatory"&gt; and just one thing for all. Problem : template had to be modified : if the semantic way is good enough, we can just look at default and limespired template.

Written by Shnoulle the 23 Mar 10 at 12:19.

Some of template sytem had the ability to make conditionnal branch.

For example smarty :
if $logged_in
Welcome, $name!
else
hi, $name
/if


We can use something lime that :
{if QUESTION_MAN_MESSAGE}{QUESTION_MAN_MESSAGE}{/if}

Or more easy for template maker :
{optionnal_code QUESTION_MAN_MESSAGE optionnal_code}

and QUESTION_MAN_MESSAGE are only text from langage.

This is more difficult to do i think. (i can't help, but i can help to the first solution)

Some of template sytem had the ability to make conditionnal branch. For example smarty : if $logged_in Welcome, <font color="#fontColor#">$name!</font> else hi, $name /if We can use something lime that : &#123;if QUESTION_MAN_MESSAGE&#125;&#123;QUESTION_MAN_MESSAGE&#125;&#123;/if&#125; Or more easy for template maker : &#123;optionnal_code QUESTION_MAN_MESSAGE optionnal_code&#125; and QUESTION_MAN_MESSAGE are only text from langage. This is more difficult to do i think. (i can't help, but i can help to the first solution)

Written by evan the 23 Apr 10 at 06:02.

I did a lot of work putting in the classes to make it easier for designers to style LimeSurvey by moving styling out of hard coded (and invalid) HTML styling into easily (with the right knowledge) customisable CSS. Most of these classes names use meaningful if your survey is in English. If your survey is not in English then the classes are not meaning full so do not contribute to the semantic quality of the survey.

The following might be a slightly weird solution but...

One possible solution is to parse both the template files and CSS files when the survey is activated, dumping the cached versions of these files into a locale based templates directory.

Also on the same idea. Have a parser to translate class and ID names in template.css files into other languages to make it easier for non-english speakers to style templates.

I did a lot of work putting in the classes to make it easier for designers to style LimeSurvey by moving styling out of hard coded (and invalid) HTML styling into easily (with the right knowledge) customisable CSS. Most of these classes names use meaningful if your survey is in English. If your survey is not in English then the classes are not meaning full so do not contribute to the semantic quality of the survey. The following might be a slightly weird solution but... One possible solution is to parse both the template files and CSS files when the survey is activated, dumping the cached versions of these files into a locale based templates directory. Also on the same idea. Have a parser to translate class and ID names in template.css files into other languages to make it easier for non-english speakers to style templates.

Written by Shnoulle the 25 May 10 at 14:22.

in common.php

Replace
if (strpos($line, "QUESTION_HELP") !== false) $line=str_replace("QUESTION_HELP", $question['help'], $line);

by

if(preg_match("~(.*)(\)(.*)QUESTION_HELP(.*)(\)(.*)~",$line)$line=preg_replace( "~(.*)(\)(.*)QUESTION_HELP(.*)(\)(.*)~","$1$3$question['help']$4$6",$line);


I put some diff on bugtracker after 1.90 was out.

in common.php Replace if (strpos($line, "QUESTION_HELP") !== false) $line=str_replace("QUESTION_HELP", $question['help'], $line); by if(preg_match("~(.*)(\)(.*)QUESTION_HELP(.*)(\)(.*)~",$line)$line=preg_replace("~(.*)(\)(.*)QUESTION_HELP(.*)(\)(.*)~","$1$3$question['help']$4$6",$line); I put some diff on bugtracker after 1.90 was out.

Written by evan the 25 Feb 10 at 01:42.

1 it might be worth making the question Array (Multi Flexi) (Text) (attribute: numbers only) into it's own question type

2 add the following attributes:
Show totals
* row = total for each row (an additional column)
* col = total for each column (an additional row)
* both = totals for both columns and rows (an additional row and column)

store totals in results
* 1 = store column/row totals in results

Grand total
* 1 = show grand total only
* 2 = store grand total in results (do not display)
* 3 = show grand total and store in results

Java script would calculate totals for columns/rows and would be able to hand negative numbers and floating point numbers.

for visual example see

1 it might be worth making the question Array (Multi Flexi) (Text) (attribute: numbers only) into it's own question type 2 add the following attributes: Show totals * row = total for each row (an additional column) * col = total for each column (an additional row) * both = totals for both columns and rows (an additional row and column) store totals in results * 1 = store column/row totals in results Grand total * 1 = show grand total only * 2 = store grand total in results (do not display) * 3 = show grand total and store in results Java script would calculate totals for columns/rows and would be able to hand negative numbers and floating point numbers. for visual example see http://apps.acu.edu.au/~evanw/LimeSurvey_custom-q-type_array-mulit-flexi-text-numbers-only.html Please ignore styling as this should be done with CSS. I can help with the HTML side but can't help with JS, DB LS admin stuff.

Written by apps the 5 Feb 10 at 16:12.

The use case can be safely split in 2 use cases, by looking at the level of interaction the user need with the settings.

A "survey messages" +
A "survey settings " (Retain old name)

The use case can be safely split in 2 use cases, by looking at the level of interaction the user need with the settings. A "survey messages" + A "survey settings " (Retain old name)