Yet another multicolumn layout - rocks!

test.jpgOne chasm between traditional desktop application development and web application development is layout/forms design. It’s my constant pain point “I just want a 2 column layout, with a data table in the middle” - many hours later you’re still tearing your hair out trying to get it working. It should not be this way (and that’s just for prototyping).

To get a production tested basic grid/column based layout, that looks reasonable across all browsers and is flexible enough to grow as the app grows - well we all know how much a top notch HTML/CSS wizard is going to cost us right ? Why for every project the same ground of IE hacks and cross browser issues are solved over and over again ? This is half the reason that a sandbox environment like AIR is very appealing - don’t deal with it, just get your users to use a standard environment.

Enter from stage left, in the why hasn’t anyone thought about it before category, are two CSS frameworks that I happened upon on Friday. One called Blueprint which is getting a bit of attention, and one with the rather confusing name of YAML. After seeing all of the examples of YAML, and reviewing the documentation I thought what the heck lets give this a go.

YAML is designed for ’standard’ column based layouts. It essentially says ‘create your main div structure this way, in a predefined page/top nav/nav/main body/footer layout. Then within your main body div, you have options for creating 1-3 columns, and then sub columns within those columns. Whilst I haven’t tested the limits, I’m sure so long as it fits within a grid you could use YAML to create it. It’s not designed for your highly creative CSS award winning page with umpteem divs all over it - however that audience wouldn’t be reading this blog. But for your standard store/blog/cms/other application I can see a huge head start in having the CSS pain removed from your desk.

So I put the theory to the test - 4 hours later, I had a couple of layouts running and working across IE 6, IE 7, Firefox, Safari… un-fricking-believable. About 30mins of that 4 hours was the actual job of getting the css setup with the basic grid structure - the rest, playing about with colours, table styles, and creating actual views. I abhor front end CSS work and this abstracted away all of the pain, leaving me just to get on with the job.

I’m not going to attempt to write a how-to or tutorial, as the original docs are so good I’ll leave well enough alone - the only caveat is don’t just blindly copy and paste, make sure you skim read the docs, you need to know where to put the appropriate patch files etc.

yaml.jpgBut wait there’s more !

Does the thought of manually constructing even your basic div structure seem a little off putting to you. Dirk Jesse (YAML’s wizard) has a browser based builder for constructing your layout and outputting the CSS. Very nice indeed !. Just jump to his site and check it out.

So you can expect to see some XChain screenshots gracing this site shortly.

One Comment, Comment or Ping

  1. I hear ya! I hate doing front end CSS work–the multi-computer-platform QA testing drives me crazy! I’ve used YAML to build a generic wordpress theme as well as a front for symfony development and its great. But what about Blueprint? I’d never heard of it before now–just curious what your take on it is.

Reply to “Yet another multicolumn layout - rocks!”

About

Rowan is a Product Development Manager, specialising in architecting, developing and putting web applications into production - in particular Ruby on Rails based apps. He lives in Toronto, Canada but speaks in a funny accent as he's originally from New Zealand. He's been working in the software and web business for over a decade. This blog covers Web Application development and deployment in the real world, dealing with topics from business fundamentals to Ruby on Rails, Merb, PHP, Flex, MySQL, Apache and more.

Read more ...

 

 

View Rowan Hick's profile on LinkedIn

 

Subscribe to my RSS feed