Hi there, and firstly, thanks for a GREAT start on this! I've been using a 960px grid for a lot of my sites but I really love the option to keep fluidity while still maintaining a grid. I ran across the fluidgrid concept and immediately thought, "how great would that be for my Drupal work?" I thought about starting down the road myself, but a quick search brought me to your project, and you've already done way more than I could. So thanks. I'll be keeping an eager eye on it.
A couple thoughts to share at this point...
One, a vote for almost-semantic sidebar names - rather than left and right, maybe go with "one" and "two" or something more flexible? I know truly semantic names would describe function more accurately, but something more flexible than left and right might be helpful for those times when we want two sidebars on the right or what-have-you.
(As a bonus, it might also help us break out of that stereotypical drupal 3-column look by not suggesting left and right sidebars...)
Two, have you any thought of developing a region system such as Acquia Marina's, where multiple regions are available as needed, and scale well horiztontally when not all are used? (ie. something like 4 across the page between header and content, and 4 more between content and footer, but still spanning the full width if only 2 are used - 50% each...) I see more and more sites using these, and having them built in to the theme would be a huge timesaver.
Or maybe a simpler way is to have some regions defined in the .info and .css files and then let the themer specify widths based on the grid. (ie. 4x span-4 regions in a 16-col grid , or 1x span-8 then 2x span-4, etc.). I confess I don't know if and/or how this would work with what you've built to switch the # of columns in the theme settings. But I'm supposing that if you'd fix the max # of regions (maybe at 4?) no matter how many columns, it could work without being too complicated.
But that's just my own supposition and possibly my lack of theming knowledge showing...
Three, I notice that the Admin Menu (the black bar one absolutely positioned at the top of the page) exhibits an odd behavior with this theme. The whole page is pushed down the height of the menu, but then the menu covers the first 1.4em of the container, rather than being placed in the space it's supposed to occupy. (screenshot attached)
It seems to be particular to fluidgrid, since switching the theme to a default one puts the menu back in its proper place. I'm sorry I don't have more info to help at this point - haven't had time to try to hunt down the problem. But I will if I get a chance in the next few days.
Thanks again for taking this on - I have the feeling it's going to become one of my core starting points for theming!
Michael.
| Comment | File | Size | Author |
|---|---|---|---|
| fluidgrid.jpg | 84.01 KB | michaelschutz |
Comments
Comment #1
Anonymous (not verified) commentedThanks for your interest in FluidGrid, and for taking the time to raise this points. It's always nice to have a different point of view.
To answer your questions :
1. Semantic names.
This makes sense, and I'll look into a better way to name the default regions.
2. Regions
This could be done, but I'll set this as low priority for two reasons. First, regions is fairly easy to create, and second, it would require a lot of work in the page template to get a basic flexible system working. Also it could make the page templates a bit too heavy on codes, but I'll think about a solution.
I like the idea of setting regions without assigning them to any layout property though.
3. Admin menu.
This is because I usually set the admin menu to always be on top of page, so it's fixed, and doesn't need the extra margin on top. You can change these settings in the admin menu configurations.
Cheers :)
Comment #2
Peter Bowey commentedHubert Florin,
Well done on your progress for the Fluid Grid System!
Having tried the usual 'fixed' pixel based framework systems. I am disappointed at the rather poor reasoning to establish a 'lazy' fixed dimension as 'pixel' rigid. Fixed frameworks look ‘ungainly’ on modern 22”-32” monitors!
After months of my own pain and research the 2 winners appear to be; A) An older version of
and B) A more recent adaptation of the
Please note that you have my full support for this project and the resulting Drupal code. I am already working hard to implement it on my production website!
I have carefully compared the results from Blueprint 'Liquid' and your own modification to ‘fluid 960’. You will be pleased to know that your current method has so much LESS display flaws. In fact I struggle to find any, but - I can easily break the Blueprint 'liquid' version by just changing the MS Windows IE's or FF's Window size. In this test situation - the Blueprint 'liquid' version only fully recovers after a forced browser refresh (CTRL + F5). Your code deals it just fine (liquid magic).
Thanks for sharing this Drupal project!
Regards,
Peter Bowey
Computer Engineer
Peter Bowey Computer Solutions
69 Sutherland Ave, Hayborough,
Victor Harbor, SA, Australia, 5211
Ph: (08) 8552 8630
Fax: (08) 8552 9185
Mobile: 0414 440 575
EMAIL: support@pbcomp.com.au
WebSite: www.pbcomp.com.au
Comment #3
Anonymous (not verified) commentedThanks for your support ! Have a look at the BETA 1, it just came out :)