And We’re In Business!
The blog has been successfully moved to the new domain and theme. Took longer than I wanted, but doesn't everything?
A few of the roadblocks I ran into include:
- MooTools & Syntax Highlighter didn't cooperate as I hoped. The issue was with Syntax Highlighter, but I've iron out this issue.
- Problems upgrading WordPress from 2.2 to 2.3. I've stayed with 2.2 for now.
- WordPress' list-driven navigation. A lot of WordPress revolves around lists, which in most cases is good, but why use UL/OL/LI if you can simply use "display:block;" CSS?
In any event, the new blog is up and I'd love to hear your thoughts on the design and how I can improve the website!
![Introducing MooTools Templated]()
One major problem with creating UI components with the MooTools JavaScript framework is that there isn't a great way of allowing customization of template and ease of node creation. As of today, there are two ways of creating:
new Element Madness
The first way to create UI-driven...
![CSS @supports]()
Feature detection via JavaScript is a client side best practice and for all the right reasons, but unfortunately that same functionality hasn't been available within CSS. What we end up doing is repeating the same properties multiple times with each browser prefix. Yuck. Another thing we...
![WebKit Marquee CSS: Bringin’ Sexy Back]()
We all joke about the days of Web yesteryear. You remember them: stupid animated GIFs (flames and "coming soon" images, most notably), lame counters, guestbooks, applets, etc. Another "feature" we thought we had gotten rid of was the marquee. The marquee was a rudimentary, javascript-like...
![spellcheck Attribute]()
Many useful attributes have been provided to web developers recently: download, placeholder, autofocus, and more. One helpful older attribute is the spellcheck attribute which allows developers to control an elements ability to be spell checked or subject to grammar checks. Simple enough, right?
