Message-ID: <4AC22DE5.8060805@archonet.com>
Date: Tue, 29 Sep 2009 16:55:17 +0100
From: Richard Huxton <dev@archonet.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Andrew Dunstan <andrew@dunslane.net>
CC: Alvaro Herrera <alvherre@commandprompt.com>,
	Peter Eisentraut <peter_e@gmx.net>,
	pgsql-hackers@postgresql.org, Dimitri Fontaine <dfontaine@hi-media.com>
Subject: Re: navigation menu for documents
References: <4A5CE7EB.20809@pgexperts.com> <4A5D10AD.6060305@dunslane.net>
	<4A5D1464.4040202@archonet.com>
	<200907151333.02260.peter_e@gmx.net> <4A607573.60904@archonet.com>
	<20090929151548.GD6116@alvh.no-ip.org>
	<4AC22933.2030701@dunslane.net>
In-Reply-To: <4AC22933.2030701@dunslane.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Andrew Dunstan wrote:
> 
> 
> Alvaro Herrera wrote:
>> Did this go anywhere?
> 
> Well, it was sorta nice but what Richard sent wasn't really what I want,
> at least, which is more along the lines of the menu David Wheeler uses
> for the Bricolage API docs.

Well, if we nail down the details I'm happy to do the grunt-work.


I think #1, #2 (fixed navigation links, titles) are a separate question
and just need to be decided upon by those who feel strongly one way or
t'other.


For the browser, does the following match what you're after, Andrew?
- clicking chapter title opens the browser panel
- panel stays open until you click close icon
- panel contains collapsable tree of chapter/section headings
Alternatively, could just auto-open the browser panel if javascript is
enabled and window is wider than N pixels.


In addition we'll presumably want to meet:
- no external js libraries (or do we care, if we just reference it from
google?)
- navigation is optional, disabling js leaves docs as at present
- works on all reasonable browsers (anything not IE6)
- works online and in downloaded docs (except Windows .chm of course)

-- 
  Richard Huxton
  Archonet Ltd