Welcome to WebmasterWorld Guest from 22.214.171.124
Forum Moderators: incrediBILL
I'm a big beleiver in the concept of liquid design but, I know many of you prefer to code to fixed width/font criteria.
I prefer the liquid approach because I think it allows your pages to adapt to whatever the user is using. That may be a 1024x768 high rez monitor on a PC or it maybe 800x600 with a whole bunch of toolbars further diminishing screen real estate.
Whatever the case, a liquid layout will adapt to it.
I'm sure some of you disagree, let's here your thoughts...
But most I've seen are not all that good. Stuff out of position, stuff jumping all over the screen while the page figures out where it's supposed to be and what size. I don't know why it does that, but I know I don't much care for it.
So unless I learn to do liquid right, I'll have to stick with fixed.
Course one could argue that I don't know how to do fixed all that well, but.......
My first exposure to liquid layout was Evolt and since then I've liked the concept. In fact, when I actually get around to having my site designed it will probably be liquid utilising CF.
Aside from the aesthetic value, does a liquid layout help functionality? I find that with larger monitors my eye strain lessens but wrist cramps set in.:)
As far as SEO goes, give me layers any day though.
Find a fixed layout that is even *useable* to everyone from 640x480 up to 1600x1280, and I'll think about using it. If I used a fixed layout on one of the sites my wife an I both use several times a day, I would either have to waste a third of my screen real estate or make her side-scroll. Side-scrolling is the greater evil, but they both stink. With a fluid layout, the page looks about the same on her screen as on mine.
Depends on the project, sometime I will do liquid, sometime fixed. I must say however that when I do "fix it for 800*600" I (almost) always centre it, just seems to look beter floating in the centre rather than scrunched up to the left with all this white space on the right.
Same here, however, I do sometimes align it to the left and put a skyscraper on the right. That way if you view in 800x600 you see the site. If you view in 1024x768 you see the site plus a skyscraper add which must look good and fit with my site design/colour scheme.
As a result I usually have the fancydan stuff expanding to fill the white space with any content a fixed width.(He ignores the 640X480 issue) What a pain.
I have a feeling CSS should provide a better solution for this perhaps but I am too busy to research this at the moment. Any ideas?
I think fixed width with fixed text size is by far the easiest to make to look attractive in 800x600 & 1024x768 - its often I think therefore cheaper for clients taking less time per site.
The issue I find about fluid layouts is that its ok to have text reflow and allow users to resize etc but this does not resize images at the same time so the page flow is changed ...
Plus #1 you need to test it in more screen sizes which increases time to site completion.
Plus #2 for me the big issue .... larger screen sizes are more like an A4 page laid on its side (landscape), if you let the page fluidly fill the screen in 1600 wide screens yet also resize back to print filling a European A4 sheet I recon you often end up with long long lines of text which are harder to read / scan ..
Of course using css print stylesheets would solve lots of these issues and they are on my list of next things to suss out. :-)
So though I've committed to liquid design, I would really like to see the max-width and min-width settings work so you could go fluid to a point, and then have some static limits.
One possibility, and I don't know whether or not this is even on the horizon, is to be able to set a max width for text boxes in terms of number of characters so beyond a certain width the default would be to size up the font and keep the same number of larger characters in the box, rather than to fit more characters of the same size in the box.
it is possible that when someone views a liquid design on a large monitor, it will become difficult to read.
Not only possilble, completly true! However, people with very high rez monitors normally resize the window to a more 800x600 looking size.
I don't have any hard data to back this up but I've heard it from many reliable sources over the last couple of years and have seen it first hand on more than one occasion.
People with very high rez usually have it for some reason other that "because I can" and are fairly computer savvy. They know that there monitor is not the norm and adjust for it.
Those that are not so savvy will soon learn ;)
I would really like to see the max-width and min-width settings work so you could go fluid to a point, and then have some static limits.
One possibility, and I don't know whether or not this is even on the horizon, is to be able to set a max width for text boxes in terms of number of characters
Setting width in em is very suitable for that.
I prefer to layout my site readable for 800 x 600 resolution and which is center-aligned. Some would put "more-needed" information viewable within the 640x480.
I find it hard reading a very very long line of sentence when a liquid design tries to adjust itself with the width of the browser when using a larger monitor and a higher resolution. Its seems that you would need to move your head just to read. Anyway, I find it also difficult reading a very long line of sentence on a very big book, don't you?
anyway, its up to the coder/designer so that the layout would be beatiful for a vey very high resolution setup and not to forget the content to be very easy to read.
Just remember, they could easily adjust the browser size for people who use a higher resoultion and a biger monitor. And maybe that is why some site has a fixed left-align content and has a fixed width too.
BTW: people who use large monitor at work and is prohibited to browse the web while working would prefer adjusting the browser size. (make it hideable.) Anyone do this at work too? ;)
right of the screen but have it appear first in the html flow
See, this sort of stuff doesn't seem to be too technical with CSS...its the top down stuff after you turn it into liquid.
Can't seem to get solutions for a "bottom" div and the top-down hierarchy of divs sort of thing......though hopefully CSS does have the answer somewhere in its code without having to sacrifice its beauty for a table to nest everything in :)
The div may contain a few links, where it will not span across the "fold" of the page. However, the same div on another page may span across the fold.
But what if I want to add another div positioned below this....possible with CSS and a fluid layout?
Otherwise I'd be sitting a table in the div and chopping it into td's to make it *look* like different cells.
I'd much prefer just to declare divs that sit nicely on top of each other.
With absolute positioning the question of a footer div always comes up as the main problem. There are 2 things you can do:
I'm gonna miss those footers :( Thanks for the sticky for the alternative....it seems to work for your site but I don't know if that's a one size fits all solution.
If only everyone had the same resolution/browser/browser add ons stealing space....then I could just declare their positions without a prob. Otherwise it would seem this "browser sniffing" and a whole other mess of code would be needed to get the desired and exact effect.
my view : liquid for sure...good for the spiders, good for text->voice software (so i hear)....not good for footers! I'll go with the idea of liquid over fixed for the future though
Is it just if your footer is very narrow (height-wise).
I am designing a site at the minute which uses a footer div, and it is purely CSS, and I haven't had a problem with the div appearing where it shouldn't.
the min-height (CSS2) attribute is recognised by NS6 and Opera, so I have incorporated it into my main content div, as it doesn't affect viewing in IE.
Or am I missing something (which is possible ;))
Could you give me youir exact definition of a footer, and what you expect from one?
Because for the page I am working on now, according to my own definition of a footer, i have *exactly* what I want...
So enlighten me ;)
sorry i am n00b to may aspects of your lingo :)