4 ms·
These are quite nice. Only one thing gives away their age. Every choice is fluid. The Web seems to have reached an informal consensus that having a maximum or f
by petercooper 16y ago
These are quite nice. Only one thing gives away their age. Every choice is fluid. The Web seems to have reached an informal consensus that having a maximum or fixed width for lines of text is a "Good Thing™"
- derefr 16y agoI'm not sure; I enjoy playing with these pages, resizing my browser window down until it's perfect for me, rather than having the width predefined. But I might be strange that way (and most users won't even know how to resize their windows...)
- andybak 16y agoThe main issue with not having a maximum width is the lack of readability of long lines of text.
- carussell 16y agoStop maximizing your browser.
- andybak 16y agoI like to maximize whatever window is in focus to minimize visual clutter. (one of my pet hates about Safari and Mac OS in general is it's aversion to full-screen windows. As I've ranted about before multiple overlapping windows solve more problems than they create. Give me a single full-screen window plus the option to occasionally tile 2 (or 4) windows for those few occasions when I need that.
- nitrogen 16y agoI always assumed that was laziness on the part of the designers, and decided to make my layouts as fluid as possible as a result. But, since I'm more of a code guy than a CSS guy, I'd end up spending hours perfecting the layout, instead of developing, and I'd end up setting max-width and min-width anyway (to wide ranges, something like 600 to 1500px, but I'd use em). I also always used em for units, in case the user was using large fonts. I always hated a site with lots of text that fixed its width to something small like 550px, until I found out about the Readability bookmarklet. So, 1: is there a good reason not to use fluid layouts? 2: What should a code guy like me do to minimize time spent designing prototype fluid layouts, before I'm ready to pay for design?