lilypond-devel
[Top][All Lists]
Advanced

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

Re: texi2html web page, second attempt


From: Patrick McCarty
Subject: Re: texi2html web page, second attempt
Date: Sat, 20 Jun 2009 15:59:59 -0700

On Sat, Jun 20, 2009 at 1:21 PM, Graham
Percival<address@hidden> wrote:
> On Sat, Jun 20, 2009 at 09:57:20AM -0700, Patrick McCarty wrote:
>> On Sat, Jun 20, 2009 at 01:54:30PM +0200, John Mandereau wrote:
>> > Le 13/06/2009 20:14, Graham Percival a écrit :
>> >
>> > > - also, if we end up going this route, somebody (I'm willing to do
>> > >   it, although I wouldn't mind delegating this :)  needs to make
>> > >   the nagivation menu show the current subsections in a second
>> > >   list.  (like the current webpage)
>> >
>> > This is possible, but I don't know how much Perl hacking it requires. It
>> > would be nice to generate the (sub)TOC as a drop-down menu activated by
>> > mouse hover/click BTW.
>>
>> I agree.
>
> Really?  I prefer the current webpage's display, since you can see
> all the sub-sections of each section.  (or all the sections of
> each "chapter")
>
> I mean, if somebody is reading Introduction->Features, I think
> it'd be nice to see Introduction->Examples and Introduction->Crash
> course, without having to hover the mouse around.

Well, I was mainly interested in it because I know how to do drop-down
menus.  But on second thought, the method does not work on IE (<=6),
so this will be more trouble than it's worth.


>> For this to happen, we would need to have *one* unordered list instead
>> of two separate lists.  I'm referring to the one in div#tocframe.
>> They would look like this:
>>
>> * unnumbered
>>   * unnumberedsec
>>   * unnumberedsec
>>     * unnumberedsubsec
>> * unnumbered
>> * unnumbered
>> * unnumbered
>>
>> I could create drop-down menus with this structure (with pure CSS),
>> but I don't know how much modification the init file would need.
>
> That was actually the default for the init file -- it took me
> about an hour to figure out how to hack-comment-out lines so it
> wouldn't do this!  :)

Okay, thanks for the patch.

I started from scratch on the CSS.  There might be some things I
forgot, but see what you think.  If this is an improvement (for now),
I can send a patch.  It should render decently.  Not sure if the
submenus will work in IE<=6, but you probably don't use those
browsers.  :-)

http://uoregon.edu/~pmccarty/web-lily/lilypond-general_1.html


-Patrick




reply via email to

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