| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Documentation and explanatory diagrams |
| Date: | 2010-07-03 12:08:52 |
| Message-ID: | 4C2F2854.4090503@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 03/07/10 02:02, Robert Haas wrote:
> The page_layout image is kinda confusing - I can tell what the purple
> and brown arrows are supposed to represent, but only because I already
> know what they're supposed to mean.
I realize that these are just sample images, but I'd like to enact a
strict rule for any diagrams we include in the docs:
All diagrams must have a key.
Otherwise you don't know what all the boxes and arrows mean. Data flow,
control flow, dependency, inheritance, or what?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2010-07-03 12:59:00 | Re: Documentation and explanatory diagrams |
| Previous Message | Robert Haas | 2010-07-03 02:59:49 | Re: links to functions-window |