Right now the files are included verbatim. Instead, we should be including the results of compiling CSS and JS files with combine.php . This will do things like resolve relative paths in CSS, minify, etc.
This is probably already done since Q_Html::themedUrlAndFilename() already considers the "Q"/"environment" config field. Test it by setting up an Q/environments/live config field -- if so, we are almost good to go.
The only question is what should happen when the combine.php hasn't run, but the scripts and stylesheets are included inline. In this case, I guess we should break out the "relative urls" processing of Q_filters_reducisaurus into a separate function inside Q_Html or Q_Utils and call it in the inlineScripts, but only if there is no environment selected in the config. To understand how to break it out, study the fields parts and dest sent by combine.php and how the Q_filters_reducisaurus constructs the relative paths, in order to move this into its own function.
Right now the files are included verbatim. Instead, we should be including the results of compiling CSS and JS files with
combine.php. This will do things like resolve relative paths in CSS, minify, etc.This is probably already done since
Q_Html::themedUrlAndFilename()already considers the"Q"/"environment"config field. Test it by setting up anQ/environments/liveconfig field -- if so, we are almost good to go.The only question is what should happen when the
combine.phphasn't run, but the scripts and stylesheets are included inline. In this case, I guess we should break out the "relative urls" processing ofQ_filters_reducisaurusinto a separate function insideQ_HtmlorQ_Utilsand call it in theinlineScripts, but only if there is no environment selected in the config. To understand how to break it out, study the fieldspartsanddestsent bycombine.phpand how theQ_filters_reducisaurusconstructs the relative paths, in order to move this into its own function.