[FFmpeg-devel] ffmpeg.org clean up

[Aurelien Jacobs]

Robert Swain wrote:

> 2009/2/15 Robert Swain <robert.swain at gmail.com>:
> > 2009/2/15 Robert Swain <robert.swain at gmail.com>:
> >> 2009/2/15 Aurelien Jacobs <aurel at gnuage.org>:
> >>> Robert Swain wrote:
> >>>> 2009/2/15 Michael Niedermayer <michaelni at gmx.at>:
> >>>> > On Sun, Feb 15, 2009 at 12:25:45AM +0000, Robert Swain wrote:
> >>>> >> 2009/2/15 Stefan Gehrer <stefan.gehrer at gmx.de>:
> >>>> >> > Robert Swain wrote:
> >>>> >> >> I realise we're in the thick of a duel, but I spent my day working on
> >>>> >> >> ffmpeg.org. I'm fed up of it being disorganised and ugly and have been
> >>>> >> >> for a long time. My web development skills aren't the best and I
> >>>> >> >> haven't touched any for a couple of years or so.
> >>>> >> >>
> >>>> >> >> Anyway, I reorganised the pages a little into sections and
> >>>> >> >> subsections, made all pages XHTML 1.0 Strict compliant and
> >>>> >> >> consequently added a little CSS for centering. Would this update be
> >>>> >> >> welcome?
> >>>> >> >
> >>>> >> > I would welcome it and also have one small wish:
> >>>> >> > If there is any CSS coming in, I would really like to see the site
> >>>> >> > setting a font without serifs. That IMHO looks much clearer.
> >>>> >> >
> >>>> >> > BODY { font-family: sans-serif; }
> >>>> >>
> >>>> >> Sure, I can add that. The CSS will be easy enough to edit anyway. I
> >>>> >> may play around with colours and stuff tomorrow, else do the more
> >>>> >> important work of cleaning up the content that is on the site.
> >>>> >
> >>>> > one request from me as well
> >>>> > the page should still display sanely if the browser doesnt support CSS
> >>>>
> >>>> Indeed. I just tested this by removing the CSS file and it looks fine.
> >>>> I haven't done anything at all fancy. As people on IRC were requesting
> >>>> that they could have a peek at it before I commit anything, I stuck it
> >>>> on my FTP.
> >>>>
> >>>> http://www.swains.plus.com/ffmpeg-test/index.html
> >>>>
> >>>> Not all pages are accessible (changelog.html etc) and I have more
> >>>> renaming and a big docs overhaul to do, but it should give you a
> >>>> little taste.
> >>>>
> >>>> Comments welcome but note that I prefer it fixed width
> >>>> (when using CSS) to keep the line length limited to something sane
> >>>> without having to mess with zoom and stuff. :)
> >>>
> >>> This is damn ugly ! With this fixed size, more than half of my screen
> >>> is blank ! And on an EeePC 701, you get horizontal scroll bar :-(
> >>> Fixed width looks like a very bad idea...
> >>
> >> Fine. Too many people have complained about fixed width so I'll make
> >> it non-fixed. But I still think the really long lines are fugly.
> >
> > Have another look. No more fixed width.
> 
> Don't you find reading lines as long as this uncomfortable? :
> 
> http://www.swains.plus.com/superdump/images/screen-capture-8.png
> 
> To me that feels like I'm trying to read two pages side-by-side or something.

If lines looks too long, just adjust the width of your web browser window !
The definition of "too long" is very dependent on the person, the screen,
etc... As I already said, the fixed width you previously chose was still
"too long" for EeePC 701 users. If you use a fixed size, you can't please
everyone. On the other hand, with variable width, everyone can adjust the
width of the window to what feels most comfortable.

Aurel