From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | peter_e(at)gmx(dot)net |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Figures in docs |
Date: | 2016-02-18 02:29:55 |
Message-ID: | 20160218.112955.2188834010458018982.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> What we need is tooling around a new file format that is similar or
> analogous to our existing tooling, so that it is easy to edit, easy to
> review, easy to build, easy to test, and so on. Otherwise, the image
> files will not get maintained properly.
>
> As an example, if an image contains text (e.g., a flow chart or
> architecture diagram), then I expect that git grep will find it there,
> so that I know to update it when I rename or augment something.
>
> The above is all solvable. There are certainly image formats that fit
> those descriptions.
>
> Personally, I'd want to know specifically what images people would want,
> so we could discuss or prototype something around that.
One of the diagrams I want to have is a query processing flowchart.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2016-02-18 02:47:50 | pg_ctl promote wait |
Previous Message | Peter Eisentraut | 2016-02-18 02:19:08 | Re: exposing pg_controldata and pg_config as functions |