re: development of MARS s.t.s., a templating engine/CMS, which is taking huge jumps forward, esp. with regard to author2author compatibility (i.e., far less work involved for owner-users, and end-users notice little or no difference)…
miraculous! somehow, i got the new skin detector to work with setting up the selector jumpbox, even adding the preselection to the name of the current skin… and the old cookie worked well, because i set up a default value for the skin, in case the name has changed (which it has).
this is my to-do list:
- find & set defaults everywhere! (partly done)
set default for bad/renamed/outdated cookie (skin name)- identify ways around hard-coding of extra skin needs (“if ($skin == “skinname”) {
*perform action such as setting up special additional content as in for IE w/ CSS alpha filter causing < readable text*;
}
- redo the browser-sniffed additional/dynamic CSS so that additional rules can be included per new skins (or find a way to do this)
- known files needing skin-name arrays to be dynamically set via readdir() include switcher and selector files
- complete at least one skin to drop in and see if it REALLY works (not just for already-existing skins, which it should, since most of the skin info is now ghostly and the server now writes it in rather than it being hard-coded into the source) (damn this PHP shit is cool!)
- bug test like a mofo!!
- have a beer or five (when i’m done with current phase)
sorry for the geek-quotient, folks. i hope somebody’s getting something out of this. this PHP stuff is really a lot easier than you might think. after all, i’m arguably borderline retarded, and i’ve been relatively successful at it.
