Hallo. Me again, this time with a navbar suggestion.
The first time I saw the navbar it seemed rather indigestible -
so much text to read.
But I did understand that the square brackets were indicating buttons.
The second time was after visiting help, where I came to see that,
for me at any
On Fri, Oct 31, 2008 at 2:37 PM, Robin Bannister <[EMAIL PROTECTED]> wrote:
> Patrick McCarty wrote:
>>
>> I would greatly appreciate any feedback on the new color choices.
>
>
> My quoted "Yes please" was to "Blue in Green" which really shouted at you.
Oops. I meant to just quote myself. :-)
>
On Fri, Oct 31, 2008 at 12:35 PM, Valentin Villenave
<[EMAIL PROTECTED]> wrote:
> 2008/10/31 Patrick McCarty <[EMAIL PROTECTED]>:
>
>> http://uoregon.edu/~pmccarty/texi2html/lilypond-index.html
>>
>> I would greatly appreciate any feedback on the new color choices.
>
> I like it very much; maybe th
Patrick McCarty wrote:
I would greatly appreciate any feedback on the new color choices.
My quoted "Yes please" was to "Blue in Green" which really shouted at you.
This one is a lot more restrained but just as easy to read.
OK, the tocpane is not unified with the navbar in any way,
but I
2008/10/31 Patrick McCarty <[EMAIL PROTECTED]>:
> http://uoregon.edu/~pmccarty/texi2html/lilypond-index.html
>
> I would greatly appreciate any feedback on the new color choices.
I like it very much; maybe the links would look better in a more
green-ish tone (but still not too green-ish, otherwis
On Fri, Oct 10, 2008 at 3:33 AM, Robin Bannister <[EMAIL PROTECTED]> wrote:
> Patrick McCarty wrote:
>>
>> I've created another design with a color palette that passes the W3C Web
>> Content Accessibility guidelines for color contrast
>
> Yes, yes, yes! Thank you very much. At last I feel the web
Reinhold Kainhofer wrote:
No! After all, you are already reading the documentation, so a link
to "Documentation" simply does not make sense.
I was visiting LM 4.6.1 this morning, reading about tweaking output,
and I wondered afterwards if, while there, I could have argued that
a link to "Tw
On 2008/10/26 01:41 +0200, Robin Bannister wrote:
> Reinhold Kainhofer wrote:
> > How about "Overview" instead of "Index"?
>
> A better choice!
> And I counter with "Documentation Home".
>
> But a second word is overkill.
I'd like "Up to" proposed by Francisco, and "documentation home" i
Reinhold Kainhofer wrote:
How about "Overview" instead of "Index"?
A better choice!
And I counter with "Documentation Home".
But a second word is overkill.
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gn
Reinhold Kainhofer wrote:
unless someone can come up with something better than "<<",
which also indicates a navigational element
But *you* did, some time ago! [Top][Contents][Index][ ? ]
All you need is the above. See it at
http://lists.gnu.org/archive/html/lilypond-user/2008-10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 25. Oktober 2008 schrieb Robin Bannister:
> This is currently displayed as
><< Back to Documentation Index
>
> _a___
> I suppose the "<<" is echoing the "<<" in the navbar.
> There, it means up and along,
> i.e to the preceding position
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 25. Oktober 2008 schrieb Francisco Vila:
> 2008/10/25 Robin Bannister <[EMAIL PROTECTED]>:
> > Some usability comments, please, before this gets translated.
>
> ...
>
> > I suggest removing "<<", "Back to" and "Index". "Documentation" is
>
2008/10/25 Robin Bannister <[EMAIL PROTECTED]>:
> Some usability comments, please, before this gets translated.
...
> I suggest removing "<<", "Back to" and "Index". "Documentation" is probably
> sufficient. After all, when you arrive at the page, this is all the title
> says.
Yes. Another (verbos
Francisco Vila wrote [Re: translated big pages]:
Additionally, would it be possible to internationalize
the "Back To Documentation Index" link?
Some usability comments, please, before this gets translated.
This is currently displayed as
<< Back to Documentation Index
_a___
I suppos
Some thoughts on searching.
Valentin Villenave wrote:
the search function should show the results in the main "frame"
on the right, without making the tocframe disappear
The toc pane and the main pane are a coherent unit.
The user refers to the toc to see e.g.
- what part of the document
Hello all,
Just a side note...
I noticed that when I browse a full page document it takes quite a
long time for context menus (right click) to appear. I usually use
that feature to get back to the previous view. When the context menu
appears the horizontal and vertical scroll bars for the whole p
Patrick McCarty wrote:
I'm still experimenting with this. :-)
I've created another design with a color palette that passes the W3C
Web Content Accessibility guidelines for color contrast:
This is great for me!
Patrick
___
lilypond-user mailing
On Mon, Oct 13, 2008 at 1:02 PM, Reinhold Kainhofer
<[EMAIL PROTECTED]> wrote:
>
> Am Montag, 13. Oktober 2008 schrieb Kurt Kroon:
>> On 2008/10/11 1:00 PM, "Patrick McCarty" <[EMAIL PROTECTED]> wrote:
>> >
>> > It sounds like you know how to implement this. Would you be willing
>> > to work on it
I like the arrangement of the toc on the left side - but I wonder if it is be
possible to hide/unhide/resize it when needed!? thanks!
--
View this message in context:
http://www.nabble.com/WANTED%3A-Design-for-documentation-tp18572050p19956430.html
Sent from the Gnu - Lilypond - User mailing li
It's fine having the language bar down at the bottom of a docs page.
But in the bigpage case
you've probably done a lot of reading before you reach it,
and wish you had seen it earlier.
So I suggest something like bighead.png:
I
Put an additional language bar at the top of bigpages.
Che
Hi Kurt,
On Sat, Oct 11, 2008 at 10:34 AM, Kurt Kroon <[EMAIL PROTECTED]> wrote:
>
> Separate versions are not necessary: just offer the user an option to set
> the preference in a persistent cookie, which the server creates and sends
> back to the client. Then, the next time the server reads it,
On 2008/10/07 4:41 PM, "Alexander Kobel" <[EMAIL PROTECTED]> wrote:
>> A List Apart explains how to implement this with cookies, but we would
>> rather not use JavaScript:
Cookies != JavaScript
True, it's very easy to fiddle with them if you're using JavaScript, but
they started as a server-side
Patrick McCarty wrote:
I've created another design with a color palette that passes the
W3C Web Content Accessibility guidelines for color contrast
Yes, yes, yes! Thank you very much.
At last I feel the web designer was more concerned about
making it easy to read rather than easy to look at
2008/10/10 Patrick McCarty <[EMAIL PROTECTED]>:
> The blue links are very close to pure blue (#00F), which is a little
> bit intense, but there aren't very many blues that pass the
> guidelines. What does everyone think about this? Are there any
> colors from this design that you like more than
On Thu, Oct 9, 2008 at 6:56 PM, Andrew Hawryluk <[EMAIL PROTECTED]> wrote:
>
> For such a link-heavy document, #1a1aaa should still meet the spirit
> of the w3 guidelines without making the links leap off the page to
> such an extent. What do you think?
This color is definitely better. Thanks.
O
Patrick McCarty wrote:
I'm still experimenting with this. :-)
I've created another design with a color palette that passes the W3C
Web Content Accessibility guidelines for color contrast:
http://uoregon.edu/~pmccarty/texi2html/start-alt-alt.html
http://uoregon.edu/~pmccarty/texi2html/lilypon
On Thu, Oct 9, 2008 at 6:58 PM, Patrick McCarty <[EMAIL PROTECTED]> wrote:
> I've created another design with a color palette that passes the W3C
> Web Content Accessibility guidelines for color contrast:
>
> http://uoregon.edu/~pmccarty/texi2html/start-alt-alt.html
> http://uoregon.edu/~pmccarty/t
On Sat, Oct 4, 2008 at 7:11 PM, Robin Bannister <[EMAIL PROTECTED]> wrote:
> Patrick McCarty wrote:
>
>> What do you think?
>
> Yes, well the smoke has thinned a little.
> Look, when this thread started I thought I might keep an eye on what
> happened to the navigation, but I would keep well away f
Patrick McCarty wrote:
I agree with yours and Reinhold's idea to remove underlining and
visited link colors in the TOC pane. Should the same apply to the
main doc pane?
NAV BAR
What I said about TOC scanning doesn't apply here; there is no list.
There are probably two main sorts of usage
Me answering Rheinhold:
> The pale yellow/light brown would make the navbars almost invisible on TFT
> screens, so I think the current state is much better.
...
So what/where is the current state?
Sorry, I got mixed up; I thought this meant the navbars would disappear.
But now I think it mea
Alexander Kobel wrote:
A List Apart explains how to implement this with cookies, but we would
rather not use JavaScript:
And yes, I'm against JavaScript, too. This doesn't count as a real
client-side solution from my point of view.
?? What is the objection to JavaScript? And why do you not reg
On Mon, Oct 6, 2008 at 2:54 PM, Reinhold Kainhofer
<[EMAIL PROTECTED]> wrote:
>
> I thought about the different pros and cons of the colors, but I think the
> pros far outweight the cons. The pros are in particular:
> - -) You see which sections you have already visited, so you can either go to
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 8. Oktober 2008 schrieb Alexander Kobel:
> [EMAIL PROTECTED] wrote:
> >> "Patrick" == Patrick McCarty <[EMAIL PROTECTED]> writes:
> >>>
> >>> also offer a safe-and-sound version, and have this
> >>> "ugly-but-efficient" narrow-TOC solu
> A List Apart explains how to implement this with cookies, but we would
> rather not use JavaScript:
And yes, I'm against JavaScript, too. This doesn't count as a real
client-side solution from my point of view.
Simplest solution, server-sided, efficient and secure, but clearly not
nice: Keep a v
Patrick McCarty wrote:
>> Besides, I'm not completely sure if this idea can be easily added, since
>> you use the absolute positioning and do not really apply a width, but
>> set the margins s.t. the width constraints follow; correct?
>
> I was having trouble implementing a solution that works in
[EMAIL PROTECTED] wrote:
>> "Patrick" == Patrick McCarty <[EMAIL PROTECTED]> writes:
>
>>> also offer a safe-and-sound version, and have this
>>> "ugly-but-efficient" narrow-TOC solution as a "large screen
>>> optimized version"?
>
> Patrick> Good idea. I'll start experimenting with this.
>
On Tue, Oct 7, 2008 at 4:06 PM, Alexander Kobel <[EMAIL PROTECTED]> wrote:
> Patrick McCarty wrote:
>>
>> Hmm. I didn't consider the {min,max}-width rules. I think using a
>> max-width for the TOC pane would be more appropriate though.
>
> Yup, true.
>
> Besides, I'm not completely sure if this i
Patrick McCarty wrote:
>> I just looked at the manual at different sizes, and I agree that we
>> should not decrease the size of the navigation bar too far - it makes
>> things too worse for smaller screens.
>> But, couldn't we try a minimum-width in absolute values, say 240px (or
>> about 16em, to
> "Patrick" == Patrick McCarty <[EMAIL PROTECTED]> writes:
>> also offer a safe-and-sound version, and have this
>> "ugly-but-efficient" narrow-TOC solution as a "large screen
>> optimized version"?
Patrick> Good idea. I'll start experimenting with this.
Please make sure it still works on
On Mon, Oct 6, 2008 at 2:44 PM, Robin Bannister <[EMAIL PROTECTED]> wrote:
> Kurt Kroon wrote:
>
>> the CSS "quasi-frames" already provide the affordance of a fixed
>> navigation frame, so it isn't necessary to make their backgrounds
>> "matchy-matchy".
>
> I don't understand which background areas
On Mon, Oct 6, 2008 at 4:58 PM, Alexander Kobel <[EMAIL PROTECTED]> wrote:
> Sebastian Menge wrote:
>> Am Fri, 26 Sep 2008 17:47:56 +0200
>> schrieb Alexander Kobel <[EMAIL PROTECTED]>:
>>
>>> However, one suggestion: Have you talked about the size of the
>>> navigation sidebar? On my 13" MacBook (
On Mon, Oct 6, 2008 at 3:39 PM, Robin Bannister <[EMAIL PROTECTED]> wrote:
> Reinhold Kainhofer wrote:
>>
>> This is always a good argument (similar things should look similar),
>> however, I think in our case we can afford to use a "nicer" color in the
>> sidebar, since it is already spacially sep
Sebastian Menge wrote:
> [...]
>> For the long lines: I heard this stuff - 40 to 80 characters, best
>> between 50 and 60, serifs (although not on the screen, depending on
>> whom you ask), microtypographically fitted hyphens and dots at the
>
> Just looked up a research article on this. I dont un
Sebastian Menge wrote:
> Am Fri, 26 Sep 2008 17:47:56 +0200
> schrieb Alexander Kobel <[EMAIL PROTECTED]>:
>
>> However, one suggestion: Have you talked about the size of the
>> navigation sidebar? On my 13" MacBook (1280x800), there is /plenty/ of
>> space wasted [...] but I guess I'd prefer a li
Reinhold Kainhofer wrote:
This is always a good argument (similar things should look similar), however,
I think in our case we can afford to use a "nicer" color in the sidebar,
since it is already spacially separated from the contents (by having its own
column on the left).
I would turn this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 6. Oktober 2008 schrieb Robin Bannister:
> In fact, I think the TOC has too many sorts of indications at the moment.
>
> Unlike the main pane, it is not for normal reading, but for scanning:
> eyewise, you zoom out a bit and apply a sort o
Kurt Kroon wrote:
the CSS "quasi-frames" already provide the affordance of a fixed navigation
frame, so it isn't necessary to make their backgrounds "matchy-matchy".
I don't understand which background areas you are referring to.
By "navigation bars" I was referring to the horizontal stripes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 1. Oktober 2008 schrieb Patrick McCarty:
> > - -) On the NEWS page the title is not shown in the green (there's also
> > no navbar, but that's a texi2html issue, but then, a navbar is not needed
> > anyway...)
>
> That's really strange. A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 6. Oktober 2008 schrieb Patrick McCarty:
> Thanks! That's not a problem. It looks like the init file might need
> a slight adjustment though, because the structural changes didn't
> affect these pages:
>
> http://kainhofer.com/~lilypond/in
Hi Reinhold,
On Mon, Oct 6, 2008 at 8:13 AM, Reinhold Kainhofer
<[EMAIL PROTECTED]> wrote:
>
> I've added class="toc_uplink" to the element (and adjustes the .css
> accordingly), so I'm not restricted from using other elements in the toc
> frame.
>
>> These pages also include my latest styleshee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 5. Oktober 2008 schrieb Patrick McCarty:
> On Sat, Oct 4, 2008 at 3:22 PM, Robin Bannister <[EMAIL PROTECTED]> wrote:
> > Patrick McCarty wrote:
> >> Can you clarify what you mean by the latest styling hiding this feature?
> >
> > Well, at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 4. Oktober 2008 schrieb John Mandereau:
> Le samedi 04 octobre 2008 à 22:18 +0200, Reinhold Kainhofer a écrit :
> > Am Samstag, 4. Oktober 2008 schrieb Robin Bannister:
> > > Without the prefix the title is then just e.g. "Learning Manual",
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 6. Oktober 2008 schrieb Mark Polesky:
> > > However, one suggestion: Have you talked about the size of the
> > > navigation sidebar?
> >
> > ...One option (and my preferred) is to fix the width of the html and
> > center the whole thing...
>
> > However, one suggestion: Have you talked about the size of the
> > navigation sidebar?
>
> ...One option (and my preferred) is to fix the width of the html and
> center the whole thing...
Or allowing the user to move the separator left and right with the mouse.
- Mark
__
Am Fri, 26 Sep 2008 17:47:56 +0200
schrieb Alexander Kobel <[EMAIL PROTECTED]>:
> However, one suggestion: Have you talked about the size of the
> navigation sidebar? On my 13" MacBook (1280x800), there is /plenty/ of
> space wasted (default font settings in Firefox 3, haven't changed
> anything).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 5. Oktober 2008 schrieb Kurt Kroon:
> On 2008/10/04 7:11 PM, "Robin Bannister" <[EMAIL PROTECTED]> wrote:
> > Patrick McCarty wrote:
> >> What do you think?
> >
> > Well, I'm honoured.
> > And you are very quick off the mark.
> > In fact, y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 5. Oktober 2008 schrieb Patrick McCarty:
> On Sat, Oct 4, 2008 at 3:22 PM, Robin Bannister <[EMAIL PROTECTED]> wrote:
> > Patrick McCarty wrote:
> >> Can you clarify what you mean by the latest styling hiding this feature?
> >
> > Well, at
Patrick McCarty wrote:
Okay, see if this design looks better:
...
What do you think?
Well, I ought to be asleep.
But that hasn't worked out too well yet.
I realised I had messed up my last two posts (png uncompressed)
and got back online to patch things up a bit.
What do you think?
We
Reinhold Kainhofer wrote:
so basically, you want ... a link to the back to the documentation index
No, I didn't mean that.
That is in your TODO, and not at all urgent for regular users.
Robin Bannister wrote:
This is because I regard B as just another entry in the TOC.
The TOC does not ne
On Sat, Oct 4, 2008 at 3:22 PM, Robin Bannister <[EMAIL PROTECTED]> wrote:
> Patrick McCarty wrote:
>>
>> Can you clarify what you mean by the latest styling hiding this feature?
>
> Well, at the moment it is on a darkish grey background. I find it quite an
> effort reading on this background; it a
Le samedi 04 octobre 2008 à 22:18 +0200, Reinhold Kainhofer a écrit :
> Am Samstag, 4. Oktober 2008 schrieb Robin Bannister:
> > Without the prefix the title is then just e.g. "Learning Manual", which
> > corresponds to what you see in the documentation overview.
>
> Yes, but that was the only str
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 4. Oktober 2008 schrieb Robin Bannister:
> Reinhold Kainhofer wrote:
> > Am Montag, 22. September 2008 schrieb Robin Bannister:
> > > So I propose
> > >
> > > A
> > > Replace the (passive) text "Table of Contents" in the TOC panel,
> > > wi
On Sat, Oct 4, 2008 at 1:10 PM, Patrick McCarty <[EMAIL PROTECTED]> wrote:
>
> 1) The title link should be bold-faced like the rest of the TOC.
For 1) I meant: "...should be bold-faced like the rest of the
breadcrumbs in the TOC."
Thanks,
Patrick
__
Hi Robin,
On Sat, Oct 4, 2008 at 3:52 AM, Robin Bannister <[EMAIL PROTECTED]> wrote:
>> > B
>> > Make this document title [A] be like a breadcrumb at the document level
>> > i.e. it is a link to the start of the document.
>>
>> Also done.
>
> Maybe you consider this superfluous, but by "breadcrumb
Reinhold Kainhofer wrote:
Am Montag, 22. September 2008 schrieb Robin Bannister:
> So I propose
>
> A
> Replace the (passive) text "Table of Contents" in the TOC panel,
> with the document title, e.g. "Learning Manual".
> This nearly always visible (on biggish screens).
> (And when offscreen, nea
Hi Kurt,
On Wed, Oct 1, 2008 at 8:06 PM, Kurt Kroon <[EMAIL PROTECTED]> wrote:
>
> And while I'm thinking about it, you could deal with the line-height issue
> by setting it to 1.125, without any units.
>
> (
> See Eric Meyer's excellent article about this issue:
> http://meyerweb.com/eric/thought
On 02.10.2008 (07:18), Werner LEMBERG wrote:
> > Not only is texinfo the worst beast I've ever worked
> > with,
>
> You are exaggerating. The LaTeX kernel stuff is worse IMHO.
bibtex also comes to mind. But luckily, I've never had to work in any of
those directly.
Eyolf
--
"Why are we impo
> > Mhmm. texinfo.tex is quite complex. Nothing for the
> > fainthearted.
>
> Not only is texinfo the worst beast I've ever worked
> with,
You are exaggerating. The LaTeX kernel stuff is worse IMHO.
> it's badly documented too, at least once one moves past the basics
It's getting better. U
Kurt Kroon wrote:
And while I'm thinking about it, you could deal with the line-height issue
by setting it to 1.125, without any units.
Thanks! I'd read the section on this in the spec, (and just re-read
it), and it doesn't point out how much better it is for inheritance, and
I didn't get i
On 2008/10/01 8:30 AM, "Patrick McCarty" <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 30, 2008 at 11:53 PM, Kurt Kroon <[EMAIL PROTECTED]> wrote:
>>
>> -1, but I've got mad enough skillz to make a user style sheet. That way, I
>> can make it look however I please.
>>
>> I have attached my current u
On Wed, Oct 1, 2008 at 8:53 AM, Patrick Horgan <[EMAIL PROTECTED]> wrote:
> Patrick, if you add a line-height: 1.125em; to the .settitle section it
> fixes the strange overlap on small windows. The one it inherits from the
> body section uses a different em, and although you specify it in ems, it'
On 01.10.2008 (21:24), Werner LEMBERG wrote:
> > > The only possibility to customize the look of the PDF is to modify
> > > texinfo.tex.
> >
> > Ah, I see. Well, there *is* good news for Eyolf: any modifications
> > he makes can be added to the official docs instantly.
>
> Mhmm. texinfo.tex is
> > The only possibility to customize the look of the PDF is to modify
> > texinfo.tex.
>
> Ah, I see. Well, there *is* good news for Eyolf: any modifications
> he makes can be added to the official docs instantly.
Mhmm. texinfo.tex is quite complex. Nothing for the fainthearted.
Werner
On Wed, 01 Oct 2008 20:06:14 +0200 (CEST)
Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > If the built-in customization doesn't do what you want, then your
> > only option is to hack texi2pdf directly. That involves C
> > programming,
>
> Not at all. texi2pdf is a simple wrapper for the texi2dvi
> Take a look at texinfo's texi2pdf. That's how we build it; the
> program converts texinfo to tex (or maybe latex; I can't
> remember), and from that to pdf.
No, the document gets directly processed by tex.
> If the built-in customization doesn't do what you want, then your
> only option is to
> But what about the pdf version?
I suggest to ignore it for the time being. It hurts myself, but there
are so many things necessary to fix so that it becomes a well looking
document.
> I guess, sine it's so much raw tex, changing it may be more
> troublesome (at least the attempts I made fai
On Wed, 1 Oct 2008 19:06:53 +0200
Eyolf __strem <[EMAIL PROTECTED]> wrote:
> But what about the pdf version? I guess, sine it's so much raw tex,
Take a look at texinfo's texi2pdf. That's how we build it; the
program converts texinfo to tex (or maybe latex; I can't
remember), and from that to pdf
The recent changes to the html/css are really a significant improvement to
the web-based documentation. Kudos to all!
But what about the pdf version? I guess, sine it's so much raw tex,
changing it may be more troublesome (at least the attempts I made failed),
but it would really be good, either
Am Mittwoch, 1. Oktober 2008 schrieb Kurt Kroon:
> I have attached my current user style sheet, to be applied in lieu of
> Patrick's styles (in case anyone's interested).
I've now added your CSS as another alternative style sheet so that everyone
can have a look at it and judge the different styl
2008/9/30 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Mittwoch, 1. Oktober 2008 schrieb Neil Puttock:
>> I don't know whether it's something that's broken at my end (I've been
>> getting some weird docs breakages recently), but I've just compiled
Patrick McCarty wrote:
I like your stylesheet, in general. But I think some of the font
sizes you are using will render parts of the documentation illegible
on certain platforms (such as in the TOC). I like your choice of
color especially.
I know that most of this is personal, but I looked a
Patrick, if you add a line-height: 1.125em; to the .settitle section it
fixes the strange overlap on small windows. The one it inherits from
the body section uses a different em, and although you specify it in
ems, it's inherited in pixels. Or in CSS speak, you don't inherit the
specified val
On Tue, Sep 30, 2008 at 11:53 PM, Kurt Kroon <[EMAIL PROTECTED]> wrote:
>
> -1, but I've got mad enough skillz to make a user style sheet. That way, I
> can make it look however I please.
>
> I have attached my current user style sheet, to be applied in lieu of
> Patrick's styles (in case anyone's
On 2008/09/30 3:45 PM, "Reinhold Kainhofer" <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Mittwoch, 1. Oktober 2008 schrieb John Mandereau:
>> On 2008/09/30 14:04 -0700, Patrick Horgan wrote:
>>> Well done:) I still prefer Patrick's style and wish it were th
On Tue, Sep 30, 2008 at 3:07 PM, Neil Puttock <[EMAIL PROTECTED]> wrote:
>
> I don't know whether it's something that's broken at my end (I've been
> getting some weird docs breakages recently), but I've just compiled
> following your latest changes and the navigation's disappeared.
Strange... The
Patrick McCarty wrote:
On Tue, Sep 30, 2008 at 2:04 PM, Patrick Horgan <[EMAIL PROTECTED]> wrote:
Well done:) I still prefer Patrick's style and wish it were the default. I
also wish that Patrick's style affected the sidebar contents.
Hi Patrick,
What do you mean by t
[EMAIL PROTECTED] wrote:
On the front page, in Opera on Linux, the word `Reference' overlaps
the previous line:
http://kainhofer.com/~lilypond/Documentation/user/lilypond/index.html
Are you specifying an interline spacing, rather than using the
natural one for the font?
Peter C
When th
Reinhold Kainhofer wrote:
Huh, I don't quite understand what you mean with the last sentence... What
should be changed in the sidebar?
I like the white background on the main page, the contrast is low on the
sidebar. I think it would be much better with a white background as well.
Patrick
On Tue, Sep 30, 2008 at 2:22 PM, Reinhold Kainhofer
<[EMAIL PROTECTED]> wrote:
>
> Hmm, Does anyone have an idea how to properly format the language selection,
> so that it can be moved into the footer and still be clearly visible, so
> people don't overlook it?
I'll try something different for th
On Tue, Sep 30, 2008 at 2:04 PM, Patrick Horgan <[EMAIL PROTECTED]> wrote:
>
> Well done:) I still prefer Patrick's style and wish it were the default. I
> also wish that Patrick's style affected the sidebar contents.
Hi Patrick,
What do you mean by the "sidebar contents"?
Thanks in advance,
-
On Tue, Sep 30, 2008 at 1:49 PM, Reinhold Kainhofer
<[EMAIL PROTECTED]> wrote:
>
> I've now turned the current default stylesheet into a preferred stylesheet, so
> its settings won't have an effect on the alternative CSS. Does it now work as
> you expect?
It works great!
Thanks,
Patrick
___
On Tue, Sep 30, 2008 at 1:48 PM, Reinhold Kainhofer
<[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Donnerstag, 18. September 2008 schrieb Patrick McCarty:
>> My main focus with this design is cross-browser and cross-platform
>> compatibility. Since the default
On the front page, in Opera on Linux, the word `Reference' overlaps
the previous line:
http://kainhofer.com/~lilypond/Documentation/user/lilypond/index.html
Are you specifying an interline spacing, rather than using the
natural one for the font?
Peter C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 1. Oktober 2008 schrieb Neil Puttock:
> I don't know whether it's something that's broken at my end (I've been
> getting some weird docs breakages recently), but I've just compiled
> following your latest changes and the navigation's disap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 1. Oktober 2008 schrieb John Mandereau:
> On 2008/09/30 14:04 -0700, Patrick Horgan wrote:
> > Well done:) I still prefer Patrick's style and wish it were the
> > default.
>
> +1
Okay, it seems we are the majority ;-) I've now switched t
On 2008/09/30 14:04 -0700, Patrick Horgan wrote:
> Well done:) I still prefer Patrick's style and wish it were the
> default.
+1
John
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Reinhold,
I don't know whether it's something that's broken at my end (I've been
getting some weird docs breakages recently), but I've just compiled
following your latest changes and the navigation's disappeared.
One other thing I wanted to mention (I apologize if it's already been
discussed;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 30. September 2008 schrieb Patrick Horgan:
> Reinhold Kainhofer wrote:
> > http://kainhofer.com/~lilypond/Documentation/user/lilypond/index.html
> >
> > In particular, look at that page with both the current default and
> > Patrick's alter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 22. September 2008 schrieb Valentin Villenave:
> Hi Reinhold, hi everybody,
>
> I find the new documentation layout very impressive, but there's one
> feature I'm still missing: the integrated search function!
>
> In the attached html page I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 22. September 2008 schrieb John Mandereau:
> On 2008/09/17, Reinhold Jainhofer wrote:
> > On Sunday 14 September 2008 21:50:36 Patrick McCarty wrote:
> > > I agree that the language selection should be included in the footer,
> > > but I'm n
1 - 100 of 162 matches
Mail list logo
