PR #545

Hi,

Think, there a more usable system : {ACTUALSTEP} {TOTALSTEP} : then you can easily do something like that :

• You done {ACTUALSTEP} on {TOTALSTEP}
  OR
  <div class="progress">
  <div class="progress-bar" role="progressbar" aria-valuenow="{ACTUALSTEP}/{TOTALSTEP}" aria-valuemin="0" aria-valuemax="100" style="width: {ACTUALSTEP}/{TOTALSTEP}%;">
  <span class="sr-only">{ACTUALSTEP}/{TOTALSTEP}% Complete</span>
  </div>
  </div>

:)

Then : see https://bugs.limesurvey.org/view.php?id=11432

And adding some in core plugins

Thanks for the PR.
Just in case PR is unknown to visitors
PR #545
https://github.com/LimeSurvey/LimeSurvey/pull/545

I submitted the feature request for a user in the forum.
https://www.limesurvey.org/forum/can-i-do-this-with-limesurvey/107142-is-there-a-replacement-field-for-number-of-groups
The number is only needed on the first page.

Personally I'm more concerned about the progress bar, which could need some information about how many groups, questions really shown and what position in the survey the respondent is.
https://bugs.limesurvey.org/view.php?id=9677

Hi jelo,
" The number is only needed on the first page."
This user need only on the first page. But when we adding a new feature : we don't have to think to only oine user but whole actual and future user.

Think have a way to easily extend replacement done is the best solution.

And we can add some in little core plugin : then you need it : you activate it. You don't need you don't activate and you get some ms less to compute the page .....

@Denis: In the long run we're all dead :-)
The PR is there. If PR is accepted, will it prevent any of your future plugins to blossom? Will accepting the PR, decrease the quality of the code?

OK, then i can make 256 PR to add 256 new replavcement . If i do this each time i see a user want it in the forum : i have surely more than 256 ...

It's not a long rune : it's shortest than LS 3.1 ....

@Denis: Will accepting this PR, decrease the quality of the code? You didn't answer that. Will it prevent something codewise, you're currently working on?

Why should this PR not be accepted?

For reference: https://www.surveymonkey.com/blog/2016/05/26/progress-bars-good-bad-survey-survey-says/

@jelo : i just give my Point Of View : it's just : if we merge this PR, there are no reason to merge any other PR adding an new REPLACEMENT. ANd finally we have 1 000 replacements ....

PS : in fact , i remove a lot Prgress bar and give some information on step on some group description.

https://github.com/LimeSurvey/LimeSurvey/pull/545/files