[FFmpeg-devel] ffmpeg.org clean up

[Diego Biurrun]

On Wed, Feb 18, 2009 at 10:23:56AM +0000, Robert Swain wrote:
> 2009/2/18 Diego Biurrun <diego at biurrun.de>:
> > On Wed, Feb 18, 2009 at 03:25:17AM +0000, Robert Swain wrote:
> >> 2009/2/15 Jan Knutar <jknutar at nic.fi>:
> >> > On Sunday 15 February 2009, Dave Dodge wrote:
> >> >> On Sun, Feb 15, 2009 at 02:34:02AM +0000, Robert Swain wrote:
> >> >> > Don't you find reading lines as long as this uncomfortable? :
> >> >>
> >> >> I guess if you tend to maximize applications I can see how you might
> >> >> find it to be an issue.  Personally it would take a very special
> >> >> situation, such as viewing HD screencaps, for me to make my browser
> >> >> window anywhere close to that wide.
> >> >
> >> > Scalability is much nicer than assumptions about the amount of chars the
> >> > user can fit on the screen.
> >>
> >> So, you don't all object to having a maximum width because you don't
> >> run your browsers maximised, but rather you do complain about fixed
> >> width not scaling down to smaller widths on smaller screens. The
> >> suggestion of having:
> >>
> >> #container {
> >>     max-width: <some value>;
> >>     width: 100%;
> >> }
> >>
> >> Seems to be a reasonable compromise. How many people actually have
> >> their browsers maximised and want really long lines? Aurelien? Jan?
> >> Anyone?
> >
> > I run my browser maximised.  I don't think you should fiddle with width,
> > just let people resize their browsers if need be...
> 
> Surely if we cannot impose constraints on how long the lines of text
> are, we cannot impose constraints on how the user manages their
> windows... Yes, I am being facetious.

I'll say it another way: Stop worrying about width, it's entirely the
user's problem.

Diego