lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond ./ChangeLog Documentation/bibliography...


From: Stephen
Subject: Re: lilypond ./ChangeLog Documentation/bibliography...
Date: Thu, 21 Jul 2005 13:24:27 -0500

One more point, while the general recommendations still cite (I finally figured out how to spell it) an assumption that the general user might still only have a screen resolution of 800x600, it is a good assumption that a user of a graphic oriented program like Lilypond is likely to have a minimum screen resolution of 1024x768 nowadays. So a minimum width of 972 would be acceptable.

Even when you accept general guidelines and recommendations, they still need to be adjusted to fit the specific situation. When I see a fixed width web site, I think it is controlling and condescending and while I think it looks pretty, inwardly I am thinking I will have to scroll more that I would wish. In this case Han-Wen rejects the general wisdom and with good reason. The layout has already been tuned to look good in flexible width format. More that just the width would need to be adjusted to tune it properly for fixed width presentation and the problem that less information would be present on each page and more scrolling would be necessary could not be overcome.

When I am having trouble understanding something in the documentation, I find myself jumping between paragraphs rearranging the order of the explanation until I understand it. That is harder to do if I have to scroll between paragraphs.

Stephen

----- Original Message ----- From: "Heikki Junes" <address@hidden>
To: "Stephen" <address@hidden>
Cc: "Han-Wen Nienhuys" <address@hidden>; <address@hidden>
Sent: Thursday, July 21, 2005 12:44 PM
Subject: Re: lilypond ./ChangeLog Documentation/bibliography...


Stephen wrote:

Even in the documentation, the blank line between paragraphs, which you do not see in a news column, and the frequent examples prevent the columns of text from getting too tall, making it easier not to mistake which line we are on.

Although I like pages that flow into the entire browser window I have, because it reduces the amount of scrolling needed to read each page.

Stephen

These are good points.

The main pages look better when they span over full screen. But I would still like to restrict the width of the manual pages: If the width of the rendered examples is fixed to 671px or less, it make it easier to follow the text&examples if the width of the text is not much larger than the width of the examples, so that the text is close to the example in hand.

Heikki







reply via email to

[Prev in Thread] Current Thread [Next in Thread]