Tuesday, December 18, 2007

Text editor pet peves

  1. Copying whitespace - I do this all the time and every time it's by accident. I go to hit Ctrl+V and hit Ctrl+C instead so rather than pasting I overwrite the copy from before. It's frustrating. I know some people may want to copy empty whitespace, but never once have I wanted to.
I know this isn't really a list yet, I'm sure I'll think of something to add in the future.

Monday, December 17, 2007

Paging - Ordered List (ol), Unordered List (ul), or what?

Does anyone have a stance on this?

It's pretty clear that there isn't a standard for this. Go to Google, Yahoo!, Ask, eBay, or Amazon, and you are going to see vastly different markup.

It's crazy how different it is. Some are ul, some are links, some are spans, some are h4s. What the H-E-(double-hockey-stick)?

I think it should be a list, but which one? It definitely is an ordered list as pages are in order but if the content is numbered it's kind of stupid. Particularly if the Previous/Next links are in the list. Then you'd get:

  1. Prev
  2. 1
  3. 2
  4. 3
  5. Next

I'm going to use an unordered list for now. But I'd like to know what you think.

Thursday, December 06, 2007

Rails Steals Brain, Police are Apathetic

I started working with Rails at home and have finally got a chance to try out haml, a ruby templating language that replaces Rhtml. I'm really excited about using it and SASS to create some really clean source.

Plus since I'm learning RoR I'll be able to create sites of much greater complexity on my own then I could being just a front-end developer. I have taken programming classes before so I should be okay.

I cool site that teaches the basics of ruby. It helped me understand some of the peculiarities of ruby. After working with C++ and JavaScript I had a little unlearning to do.

Link: Sexy Stylesheets

Cool post on Vitamin: Creating Sexy Stylesheets I've thought about this stuff a lot in the creation of my own stylesheets, but it's cool to see it explicitly written. I started organizing my css properties a couple weeks ago. Here's what I was doing: #subNav{

  1. Display props
  2. Dimentions
  3. Margins
  4. Padding
  5. Border
  6. Background
  7. Typography
} Basic logic being that I'm putting properties that affect layout first. You could argue that font-size impacts layout more than background, but I wanted to keep font properties together. And it makes sense to keep background near border. I've been using inheritance-based tabbing to keep my CSS source readable after looking at SASS. It's working pretty well, and I don't have to make nearly as many comments to keep it all straight.