Posts like this, while rant-like, are actually very helpful, in my opinion:
http://taz.net.au/blog/2008/05/07/fixed-width-style-sheets-suck/
I’ve got to start using “em” instead of “px”, and this is a good excuse.
Author Archive for Albert
We’re trying to get the style feature of K2 (Kubrick 2), a Wordpress theme, to work a certain way on the Healthy Bot blog. The tabs are behaving a little funky, and we’ll post the fix here - once we figure it out that is…
In web design, URLs are often overlooked. I usually use virtual URLs, meaning that they don’t always correspond to a real file or path. I had been using forward slashes ( “/” ) in my virtual URLs, but I’m changing those to dashes ( “-” ). I think underscores are a bit extreme; the hyphen has a softer feel to it.
I do use underscores in actual resource file names though. It seems to be a trend I’m following to use hyphens in virtual urls, and underscores in real life, but that isn’t always true.
Oh and by the way, I do plan to continue using forward slashes, aka directory separators when necessary on real paths.
This is a great post:
http://particletree.com/features/lightbox-gone-wild/
I found it looking for a javascript form on the same page, aka modal window, aka lightbox form.
Thanks!
The following link takes you to my first dive into Javascript and XML. The sandbox at Sketch99 shows you two different approaches to one goal. The objective was to create a web page that could change the color, location, and size of the number “99″.
The Javascript approach…
Javascript enabled me to make my three different variables independent of one another. Meaning I could make it change the size of the text, the color, of the text and the position of the text, all at the same time. If I wanted green 99, in the top left corner, in a small font *poof* “your wish is my command”. It also allowed me to assign different names for each variable (size, color, position). The reason Javascript offers so much freedom of option is because it works directly in the users web browser. All changes are made there on the spot, so the computer doesn’t have to go back to the server to find what it wants to do. The drawback to this is that it can be cumbersome with too many options. For every individual change that is made a corresponding function must be provided. However it synched very nicely with my understanding of HTML. the way the functions used HTML tags to identify what they were changing was very easy to grasp.
The XSLT approach…
The XSLT worked a little differently than the Java Script. XSLT is server based technology, which means any changes that were made had to be retrieved from the server via a url. The XSLT was more conducive to making bulk changes to the text. but not independent variables that could stack on top of one another. If I wanted to change the position of the text I could do that, but I could not make a green 99 go to the top left hand corner. Unless I pre-programmed that option, which would mean to have the same flexibility as the Java script every possible combination of variables would have to be preset. Which would completely undermine the XML’s ability to be less cumbersome than the Javascript. The XML also stacked very nicely with my knowledge of HTML.