Hi all,

Is it possible to move the progress bar to the bottom of the page and remove the numbers/percentage?

My research supervisor has just brought to me attention that there's been research on the most effective ways of displaying a progress bar, and results suggest it's best to have the progress bar at the bottom, no numbers, just the visual proportion.

Thanks (a lot) in advance!

~Fernanda

FeCanever wrote: Is it possible to move the progress bat to the bottom of the page and remove the numbers/percentage?

There is currently no settings inside LimeSurvey for doing that,
What version of LimeSurvey is used? There might be a workaorund possible.

Hi Jelo,

I'm using Version 3.13.2+180709.

I would be interested in this research on the most effective ways of displaying a progress bar and how they measured this and what the definition of "most effective" in this case is.

Do you have a link for that?

holch wrote: Do you have a link for that?

I'm interested too.

I can provide two links to papers
www.researchgate.net/publication/2633153...uality_and_Enjoyment
www.onlineumfragen.com/pic/matzat_progress_indicators.pdf

To move the progress bar, extend your theme, remove this block from layout_global.twig and either move it to a new position at the bottom of that file or add it to the end of outerframe.twig.


You may also want to edit the class-names in progress_bar.twig.

To hide the value, remove this from progress_bar.twig.

Is LS3 twig support capable of allowing to predefine a top and a bottom position and place a variable in the GUI (Theme or survey)? Instead of Show/Hide we would end up with a Top,Bottom and Hide-option. Perhaps with start and stop % values and hiding them as well. Twig is capable, but how much data does LS provide.

jelo wrote: Is LS3 twig support capable of allowing to predefine a top and a bottom position and place a variable in the GUI (Theme or survey)? Instead of Show/Hide we would end up with a Top,Bottom and Hide-option. Perhaps with start and stop % values and hiding them as well. Twig is capable, but how much data does LS provide.

The issue with theme options is the number of options …

See fruity ot bootsrap.

We can not put whole in options …

DenisChenu wrote: We can not put whole in options …

I don't understand "put whole". Whole of what?

Whole desired system,

For some example we can have in theme option
- More image
- Show index button : at top, at bottom, at bottom without js only, at top without js only
- Show save button : same
- Show save linl in headr
- Show index in header
- Show save link in footer (why not ?)
- etc … etc …
- Progress value : hide,show at top, show at bottom, show at both, show betwwen eah question …
- etc … etc …

I personally don't want to see that all in themeoptions. I would prefer to see that in the survey options. But too much technical debt is already inside LimeSurvey.

jelo wrote: I personally don't want to see that all in themeoptions. I would prefer to see that in the survey options. But too much technical debt is already inside LimeSurvey.

My Opinion :

1. All views can be managed in Theme
2. For example : i make a theme where question code are always shown
3. Then all of this (Show quiestioon code, show group description, show et …) if it's related to view must be moved to Theme Option
4. But Theme option are already big
5. Then LimeSurvey core must offer
5.1. some default theme options to replace current Survey view option
5.2. Must allow Sub-menu or multiple menu (example : Theme option color, theme-option-image, … )
5.3. Must allow a template can add options settings without broke parent one : issue bugs.limesurvey.org/view.php?id=13936 , pull request : github.com/LimeSurvey/LimeSurvey/pull/1196

EDIT :
5.4 : allow put settings on any default Survey settings view