Another question

• Why use Absolute url ? LS(Yii) accept different url then no absolute url
• You must use getCOnfig('adminscripts') / generalscripts / styleurl / publicstyleurl everywhere (see https://bugs.limesurvey.org/view.php?id=10299)

And please : don't move expresssion.css or any other css in theme :

• The base css (core css) give some basic for all template
• Template can update

Some part can be moved to theme (example : surveylogicfile table color , maybe use boostrap color) but not other : iframe#dialog css is needed for all theme.

why not ?

By the way, the answer to the question

"why do you load the CSS in the header?",

is :
"because it was like that in 2.06" :

2014:
https://github.com/LimeSurvey/LimeSurvey/blob/b4d67861420d1f183914e50d26cdaf677a9d5cc1/application/views/admin/super/header.php

But sure, now that I know better the LS code, I see no objection to move all that to the footer.

Why not : because : we already have issue with admin template like this:

• Fix a css issue in "default"
• Mustr fix (same line) in another one
• Must fix -(same line) in another one agin

User report bug to tell : this was not fixed in mine.

Admin theme can be made elsewhere than LS core, then have "default" > theme system is really the better way.

well I'm using a script to generate all the admin themes from a SASS file.

but sure, we could have a default common css file.

Then ALL them dev must update Admin template each time we add a single line of css somewhere ?

And all company who hire a dev to do an admin template must payb again when we add a litlle line of css

Etc ....

Same behaviour for Public template ?

For now, each time I update the admin template I update all of them.
We yet spoke about that :

• The SASS part should be strictly limited to color definition (the changing part between templates)
• All other css definition should be in a different file (that can be easy copied to all template)

That's how are working for now the front end template. I will do it for the admin theme side in a second time.

The question is : should we have a CSS core file, that end dev can't update via template ? I don't see why it would be usefull, but why not.

All other css definition should be in a different file (that can be easy copied to all template) : no , because other people must want to have their own template without update it each time we add/update something.

CSS : Cascading Style Sheet ;

• Core , for example : set body with to margin:0. Any other guy can easily set it to margin : 150px in template.

Really CSS is Cascading .

Ok Denis, I finally just understood what you want.

Just add a css file in the config.xml.
It will be load after all the other ones.
;-)

all the css load has been rewritten, using packages.

Version 2.50+ Build 160426 released