Richard Huxton wrote:
Reworked jquery-based document menu is attached.
Untar will produce bin/ and html/
cd .../html
cp /path/to/htmldocs/* .
../bin/add_js.pl *html
The contents should be on almost all relevant pages, and:
- tested on FF3.5, IE7, Opera 9.x
- expanded if screen width 800px,
Peter Eisentraut wrote:
On Fri, 2009-07-17 at 13:58 +0100, Richard Huxton wrote:
2. Titles on navigation links.
Run ./STYLING/title_links.pl and it should add title attributes to the
navigation links. This means hovering over the top links gives the title
of the page they will go to.
David E. Wheeler wrote:
On Sep 29, 2009, at 8:55 AM, Richard Huxton wrote:
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
On Oct 1, 2009, at 1:12 AM, Richard Huxton wrote:
Why wouldn't the entire TOC be in a collapsed list?
Permanently on-screen? My only concern there would be for people
viewing
on phones etc.
I have to admit that I'm never looking at the Pg docs on my iPhone.
This is mainly because I use
David E. Wheeler wrote:
On Oct 1, 2009, at 1:12 AM, Richard Huxton wrote:
Why wouldn't the entire TOC be in a collapsed list?
Permanently on-screen? My only concern there would be for people viewing
on phones etc.
I have to admit that I'm never looking at the Pg docs on my iPhone. This
On Thu, Oct 1, 2009 at 10:24 AM, David E. Wheeler da...@kineticode.com wrote:
On Oct 1, 2009, at 1:12 AM, Richard Huxton wrote:
Why wouldn't the entire TOC be in a collapsed list?
Permanently on-screen? My only concern there would be for people viewing
on phones etc.
I have to admit that
Did this go anywhere?
Richard Huxton wrote:
OK, if you untar the attached in the docs dir there are a three
separate sets of changes in it. It all functions, but consider it a
discussion point rather than a patch. Presumably we'd need to
discuss a patch over on the docs mailing-list.
1.
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.
cheers
andrew
--
Sent via pgsql-hackers mailing list
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
On Sep 29, 2009, at 8:55 AM, Richard Huxton wrote:
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,
On Fri, 2009-07-17 at 13:58 +0100, Richard Huxton wrote:
2. Titles on navigation links.
Run ./STYLING/title_links.pl and it should add title attributes to the
navigation links. This means hovering over the top links gives the title
of the page they will go to. Presumably we could do this
Peter Eisentraut wrote:
I would like to combine all these elements in header and footer, so they both
say:
Prev Fast Backward Home Fast Forward Next
TitleP TitleFBTitleFFTitleN
I think this would be much more usable than just the tooltips.
On Monday 20 July 2009 02:32:01 Alvaro Herrera wrote:
Peter Eisentraut wrote:
On Friday 17 July 2009 15:58:27 Richard Huxton wrote:
1. Fixed navigation
2. Titles on navigation links.
Yes, the DSSSL stylesheet could do that.
Since it seems we can get both of these without
Peter Eisentraut wrote:
On Friday 17 July 2009 15:58:27 Richard Huxton wrote:
1. Fixed navigation
2. Titles on navigation links.
Yes, the DSSSL stylesheet could do that.
Since it seems we can get both of these without interfering with
anything else I vote +1 on getting them it.
3.
Alvaro Herrera wrote:
Peter Eisentraut wrote:
On Friday 17 July 2009 15:58:27 Richard Huxton wrote:
1. Fixed navigation
2. Titles on navigation links.
Yes, the DSSSL stylesheet could do that.
Since it seems we can get both of these without interfering with
On Friday 17 July 2009 15:58:27 Richard Huxton wrote:
1. Fixed navigation
Copy STYLING/stylesheet.css over the existing one and you will have
static navigation links top and bottom of the page.
Looks good.
2. Titles on navigation links.
Run ./STYLING/title_links.pl and it should add title
Peter Eisentraut wrote:
This looks very cool, but should probably be implemented via a stylesheet
change instead of some Perl parsing some HTML. :-) I'm not sure if this
actually addresses Andrew's original concern, though.
No, it doesn't. David Wheeler's navigation (see upthread)
Andrew Dunstan wrote:
Peter Eisentraut wrote:
This looks very cool, but should probably be implemented via a
stylesheet change instead of some Perl parsing some HTML. :-) I'm not
sure if this actually addresses Andrew's original concern, though.
No, it doesn't. David Wheeler's navigation
On Jul 18, 2009, at 9:54 AM, Richard Huxton wrote:
No, it doesn't. David Wheeler's navigation (see upthread) that he
uses for the Bricolage docs does, however.
Ah, if you can change the overall layout then the world is your
shellfish of choice. Would it be possible to include jquery? It's
On Jul 16, 2009, at 12:49 PM, Andrew Dunstan wrote:
I'm using jQuery to pull the proper doc into a div. I'm still
noodling with it, trying to fix encoding issues on Windows, but
it's pretty close to done.
Yes, that's nice, it's just the sort of thing I had in mind - if you
can do it with
OK, if you untar the attached in the docs dir there are a three separate
sets of changes in it. It all functions, but consider it a discussion
point rather than a patch. Presumably we'd need to discuss a patch over
on the docs mailing-list.
1. Fixed navigation
Copy STYLING/stylesheet.css over
On Jul 14, 2009, at 3:21 PM, Andrew Dunstan wrote:
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.
Hey Andrew,
David E. Wheeler wrote:
On Jul 14, 2009, at 3:21 PM, Andrew Dunstan wrote:
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
On Wednesday 15 July 2009 02:27:32 Richard Huxton wrote:
Andrew Dunstan wrote:
Richard Huxton wrote:
Andrew Dunstan wrote:
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
All,
For a very long time I have thought that it would be useful to have some
sort of navigation menu for the docs
Oh yes, pretty please :)
Navigating the docs requires far too much use of the back button and up
links, IMNSHO. A menu frame would make them far more usable.
No, please, no
Hi,
Le 14 juil. 09 à 22:17, Andrew Dunstan a écrit :
For a very long time I have thought that it would be useful to have
some sort of navigation menu for the docs
Oh yes, pretty please :)
Navigating the docs requires far too much use of the back button and
up links, IMNSHO. A menu frame
Dimitri Fontaine wrote:
Hi,
Le 14 juil. 09 à 22:17, Andrew Dunstan a écrit :
For a very long time I have thought that it would be useful to have
some sort of navigation menu for the docs
Oh yes, pretty please :)
Navigating the docs requires far too much use of the back button and
up links,
Le 15 juil. 09 à 00:21, Andrew Dunstan a écrit :
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.
Ok we don't share
Andrew Dunstan wrote:
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.
Are you talking about the online manuals, or
Richard Huxton wrote:
Andrew Dunstan wrote:
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.
Are you talking about
Andrew Dunstan wrote:
Richard Huxton wrote:
Andrew Dunstan wrote:
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.
2009/7/15 Andrew Dunstan and...@dunslane.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:
Brendan Jurd escribió:
2009/7/15 Andrew Dunstan and...@dunslane.net:
Dimitri Fontaine wrote:
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
33 matches
Mail list logo
