Just a quick update: Andy is perusing the Sandbox repo. We await his expertise and coder-editor judgments as we approach a release of a revised Sandbox. Very exciting.
So before the release is finalized and designers of Sandbox “skins” begin receiving e-mails from confused, I thought I’d provide an working example of what has changed in versions and how it may apply to your skin.
First, to avoid confusion, let’s settle on the term “design” for what was previously called a skin. Why? It’s just a request. Call it whatever you what. It’s semantics, after all.
Anyhow, I first suggest you, designers, check out revision 24 in the Sandbox repository. Compare the changes in the Kubrick CSS file with the previous revision. That should give you an idea of what updates you might have to make due to changed structures and class names.
And of course, let me know what you think of the changes so far. Since May 5, 2007, I’ve managed to drop 20 commits on the Sandbox. It’s gotta be done sooner or later.
7 Comments
since google code is a second-rate SVN host (no offense), here’s the colored changes.
No argument there. It’s definitely light on the features. And SVN repos are a good example of where more features are usually better.
The link’s producing a 404, by the way.
hmmm. i deleted the file in rev 58, so the url needs and extra argument:
…/kubrick-sandbox.css?r1=56&r2=57&pathrev=57
just out of curiousity, what’s the DESIGN stuff in the opening comment for?
i think tossing the GUI for switching designs/skins means designers will more likely want to release standalone
Template: sandboxthemes, rather than a zip file with a weird install path and instructions to hack style.css by handYes, Adam, that’s correct: Sandbox-based templates/themes.
I imagine that designs for the Sandbox will be released with a
style.cssto replace the default one and a relative/images/subfolder to be placed at the same level as the aforementioned file.The reason we removed the GUI skin-switcher is because we don’t really want to try and control how people use the Sandbox. So I’d like the file structure in the Sandbox to be as open as possible.
Maybe it’s best to rename the
/sandbox-kubrick/style.csstokubrick-style.cssand remove its commented header to avoid any confusion. Those included CSS files are mere reference tools.I just realized that there are relative links in the Kubrick CSS file. So it’ll have be in a fixed location. I think the better instruction for the default file set is like I described above. Or, maybe not. Not sure.
i think giving the example designs/skins their own folder is good.
and i’m not advocating removing the comment altogether. i’m just saying it should be more descriptive, with less pseudo-formatting. (more along the lines of the readme, actually).
One Trackback
[...] Kubrick ported by Scott [...]