| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tomas Vondra <tv(at)fuzzy(dot)cz>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: FDW API / flow charts for the docs? |
| Date: | 2013-10-19 17:56:23 |
| Message-ID: | 1382205383.24583.1.camel@vanquo.pezone.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2013-10-18 at 18:46 -0400, Stephen Frost wrote:
> As to your point about not wanting to do it for a single image- it seems
> we could potentially say that for every individual image proposed, but
> if we don't keep track of those images anywhere then we may not realize
> that 5 or 10 have actually been done and proposed but never integrated.
> If they're kept on the wiki then perhaps we would both keep track of the
> ones proposed and realize when it's worthwhile to add support for them
> to the doc build system.
Right.
> As to Tom's point on the previous thread, that we would need to actually
> maintain these images, that is helped by using dia, imv, since it's a
> pretty simple tool to use and understand and is available on many
> platforms.
I'd also take a look at ditaa, which might make this even simpler.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-10-19 17:58:20 | Re: FDW API / flow charts for the docs? |
| Previous Message | David Fetter | 2013-10-19 15:20:00 | Commitfest II CLosed |