Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 27 and Version 28 of WebsiteDesignComps


Ignore:
Timestamp:
May 4, 2007, 1:20:01 AM (17 years ago)
Author:
elb
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WebsiteDesignComps

    v27 v28  
    5858>>> [wiki:joekepley]: We do typically design for fixed width. While nearly everyone supports at least 1024x768 these days, most people find it less comfortable to read blocks of text that are excessively long horizontally. Also, many high-resolution users don't tend to use the browser maximized. Based on our experience, users tend to prefer vertically scrolling (mousewheel) to needing to resize the window to make the text reflow to a comfortable width (find resize handle, click, drag, repeat for next site with different layout).
    5959>> [wiki:lschiere]: I agree with Joe about fixed width design here.  I dislike having to grow my window horizontally to fit a page.
    60 > [wiki:metalzelot]: No one has to grow a window horizontally to fit a page, exactly this is the advantage of a dynamic width. The width automatically fits the screen width. And I've never heard of any high-resolution user who doesn't use their browser full width. I'd really prefer a dynamic width but of course I know that this makes programming a lot harder for you.
    61 >> [wiki:jordanm]: I see there's no link to a slackware package - if I can provide one, and one of the devs can test it, would you put it up? (ed: i've created one for b7 already, it seems trivial to provide one for 2.0 at final which works with a default slack 11 installation.)
     60> metalzelot: No one has to grow a window horizontally to fit a page, exactly this is the advantage of a dynamic width. The width automatically fits the screen width. And I've never heard of any high-resolution user who doesn't use their browser full width. I'd really prefer a dynamic width but of course I know that this makes programming a lot harder for you.
     61
     62>> jordanm: I see there's no link to a slackware package - if I can provide one, and one of the devs can test it, would you put it up? (ed: i've created one for b7 already, it seems trivial to provide one for 2.0 at final which works with a default slack 11 installation.)
     63> [wiki:elb]: We have a long-standing policy (after having had some troubles some time back) that we do not accept binary packages from non-developers; sorry.  If you wish to stick with us long-term, help out in #pidgin, and generally become a part of the group, we may be able to take your packages, but until then we will be slackware-package-free.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!