Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?

From: tc lewis <tim(at)iuinc(dot)com>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: dustin sallings <dustin(at)spy(dot)net>, Stephan Doliov <statsol(at)statsol(dot)com>, pgsql-novice(at)postgreSQL(dot)org, pgsql-general(at)postgreSQL(dot)org
Subject: Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
Date: 1999-02-12 15:54:31
Message-ID: Pine.LNX.3.96.990212104623.14405D-100000@wopr.iuinc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Fri, 12 Feb 1999, The Hermit Hacker wrote:
>
> Like, pgsql-docs(at)postgresql(dot)org :) How much of what is already
> done by the Docs Team pertinent to all this, and, if not, why not? If our
> existing manuals don't make good documentation, then why not, and
> shouldn't those be fixed too?
>

since you asked, i don't like how the web page docs have each little
paragraph on a separate page. for example, in the frame at
http://www.postgresql.org/docs/programmer/index.html, i have to click on
"resources" to see that page, and then "terminology" is on a separate
page. it would be nicer, imho, if each chapter was on one page and the
subchapters were just links to labels within that page. for example, the
"1. introduction" and everything under it, "resources, terminology,
notation, ..." would all be on 1 page, instead of each on separate pages.

it's not a big deal i guess, it just seems really annoying to me when i'm
trying to read over stuff like that.

like, to me, mysql's documentation pages are laid out really well:
http://www.mysql.com/Manual_chapter/manual_toc.html

shrug.

-tcl.
tim(at)iuinc(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Clark Evans 1999-02-12 16:32:50 Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
Previous Message The Hermit Hacker 1999-02-12 14:22:35 Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?