This is kind of building on this thread (has been closed since): Importing additional JS resources to standalone html document - #2 by Bryan
Now this post is not about getting something to work, but that something I built works and I don’t know why/how! And I guarantee it’s simply knowing nothing about html/css, but if someone can explain this apparent voodoo to me it would greatly assist with my learning and understanding
What I’m trying to do:
Now the only “gotcha” to this is that there will be guaranteed cases where the person building the app wants to “manually override” the theme for just one model. Obviously since every layout is different there will be cases where individual models will need to be altered, font sizes shrunk to fit etc.
MRE/What I’ve built
What I Expected to Happen
Since I apply the “manual override” “first” in the code and apply the theme when I save the html “after” (during the call to save_html_wJSResources2), I expected the theme to “overwrite” my manual update (basically the two axis labels would be the same font size (14pt).
What Actually Happens
The manual override actually works!
So what do I think is actually happening then?
From what I can tell, there has to be some sort of “default” setting that gets written based on the applied theme… but if a particular model has been “manually overridden” by the user, a switch internally is triggered, signalling that it has been “hard coded” by the user, and therefore the default no longer applies to it, and the applied theme leaves it alone? Am I thinking correctly about this?
Follow up questions:
- Was this sort of setup was completely intentional by the devs? and
- Is this kind of setup the defacto standard for templating stuff on web apps?
Follow up statement from me regardless of the answers I get to these questions:
- That is freaking clever and the devs are way smarter than me