I'm pretty well convinced that the new docs chapter "External Projects"
does not belong under the Client Interfaces volume. If it only covered
client interfaces then maybe it'd belong there, but it doesn't --- and
I'm sure that the discussion of non-interface projects will expand.
Another possibi
Tom Lane wrote:
I'm pretty well convinced that the new docs chapter "External Projects"
does not belong under the Client Interfaces volume. If it only covered
client interfaces then maybe it'd belong there, but it doesn't --- and
I'm sure that the discussion of non-interface projects will expand.
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I'm pretty well convinced that the new docs chapter "External Projects"
>> does not belong under the Client Interfaces volume.
> It seems that it should be broken up by the type of external project.
> Most I would gather belong in
Tom Lane wrote:
> I'm pretty well convinced that the new docs chapter "External Projects"
> does not belong under the Client Interfaces volume. If it only covered
> client interfaces then maybe it'd belong there, but it doesn't --- and
> I'm sure that the discussion of non-interface projects will
Bruce Momjian writes:
> Tom Lane wrote:
>> I'm about half tempted to add it to the Preface.
> The Preface would be OK if it didn't have so much client-interface
> specific stuff in it. I wonder if Appendix is best, with a pointer to
> the appendix at the end of the Client section.
We could do t
Tom Lane wrote:
> > The Preface would be OK if it didn't have so much client-interface
> > specific stuff in it. I wonder if Appendix is best, with a pointer
> > to the appendix at the end of the Client section.
>
> We could do that and put the pointer into the Client front-matter.
I think that i
