Very much agree that awesome checkbox should be pachage, as well as table and "beautiful alert". That way you give template developers optimal freedom.

About table : i like to have a 'class' system by template. For example default allow

• no-more
• reponsible
• fixed
  template set 'default used' (currently no-more) , but user can choose fixed :)
  Feature : Question settings by template

I think, in general, a question setting must not be related to template. But here : except add no-more/reponsive/fixed in core : i don't found a cleanest way :/

If we have a way to add it in a clean way outside of template : why not.

responsible == responsive? ;-)

Could perhaps be fixed with custom class per question after choosing initial default...

Would be great if template could also have settings in the backend at a template page.

Oups, yes : http://getbootstrap.com/css/#tables-responsive

About settings : seem better for a settings by survey ? You think of

• Default setting by config.xml
• Settings by template (like a default but for this instance)
• Settings by survey

Foir final setting : test survey, if none => test template setting, if none => get config.xml ?

I am not sure if I understand correctly. But for users without FTP-access I would indeed promote to be able to make some settings in the backend.

At this moment we have the question classes, which I like very much. But also I woulod like to see:

• group classes
• survey classes
  which can be used to switch on/off some features in the template.

And in the longer run I would like to see some template settings on a settings page per template. Like in Drupal: see attachment.

Hi,

I really think Survey need settings for template (not classes) like you shown for drupal.
And have settings for instance (like we have for other settings) can be great too…
Unsure for group part :)

I agree, but for now (getting 3.0 live) I would not advise to design a new feature like a complete (complete?) settings page for a template, since we do not know what we would like to do with it all. But classe per survey would already help.

Template settings ideas:

• switch on/off awesome, table, other packages
• set defaults
• logo/icon
  *...

Settings are already in config.xml : https://github.com/LimeSurvey/LimeSurvey/blob/d07d269bc139cd2dfe8a781a3c2eead6caaa3594/templates/material/config.xml#L46 :)

I just like have a Survey settings tab for template settings :)

Will this also be in 3.0?
Will the user (with enough permissions) be able to edit this from the template editor?

Just for advice + information about template settings in Survey ;)

@tammo : i think we can close this one ? @LouisGac adding 'Template model' in DB, then seems outdated. And we have settings for template in Survey and Global.

All other are bug report or feature request on existing system :)

It's now possible to remove awesome checkbox, or any other css/js files of any package from the manifest of a theme:
https://github.com/LimeSurvey/LimeSurvey/commit/2398dda3b425da1a37d4611cd7963d39ac739987

Can this ticket be closed? The screenshot from Tammo seems to offer some inspiration for more ;-)

@LouisGac : i try to start SkelVanilla from scratch https://gitlab.com/SondagesPro/SurveyThemes/skelvanilla/commit/fd2f9c9d71946f2f6dc48664a863e764e00b94c5

But after testing still have awesome-bootstrap if i don't add it in remove.
But i don't add template-core (i test to remove it too : template-core).

It's another issue or same than this ?

template-core => awesome-boostrap : OK, but no template-core package added to a not child survey : no template-core : right ?

What is the status of this ticket? Is it still valid for LS4. Or can the ticket be closed?

Reset to new : Louis quit