From: | Brendan Jurd <direvus(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: navigation menu for documents |
Date: | 2009-07-15 02:11:18 |
Message-ID: | 37ed240d0907141911xa4bc771j8b0cae228c7ac14b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/7/15 Andrew Dunstan <andrew(at)dunslane(dot)net>:
> Dimitri Fontaine wrote:
>>
>> What I'm thinking about is to extend current "breadcumb" at the top of the
>> page to include chapter, section, subsection. So that for exemple the
>> following page:
>>
>> http://www.postgresql.org/docs/8.3/interactive/datatype-geometric.html#AEN5480
>>
>> Would have at its top:
>> Home → Documentation → Manuals → PostgreSQL 8.3 → Data Types → Geometric
>> Types → Points
>>
> Yes, really. What you suggest here is just not adequate, IMNSHO. I don't
> want to have to scroll to the top or bottom of the page to get navigation,
> and I want to be able to see the navigation and go where I want directly.
Even if we are going to have some kind of tree-based navigation
sidebar beastie, I would be a hearty +1 in favour of doing Dmitri's
breadcrumb suggestion anyway.
I think we can agree that a full breadcrumb/ancestry trail is superior
to "Up/Home", and unlike the sidebar nav idea doesn't require any
fancy scripting shenanigans or possible browser compatibility strife.
>
> Compared with what things like doxygen or webhelp give you it's not remotely
> what I want.
So let's have both.
Cheers,
BJ
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2009-07-15 02:11:35 | execute on log_rotation |
Previous Message | Tatsuo Ishii | 2009-07-15 01:16:13 | Re: CommitFest 2009-07 is Now Closed |