From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
Cc: | pgsql-www(at)postgresql(dot)org |
Subject: | Re: [edit] links in CommitFestSubSection headers |
Date: | 2008-11-03 03:35:38 |
Message-ID: | 5979.1225683338@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
"Brendan Jurd" <direvus(at)gmail(dot)com> writes:
> On Mon, Nov 3, 2008 at 2:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Hm, what does "not quite so easy" mean?
> Currently, a subsection is just a template call, for example:
> {{CommitFestSubSection|SE-PostgreSQL and related}}
> That's pretty easy to read, and also quite easy to pick up and move
> elsewhere, or rename if you so desire.
> If we switch to using substitution, the contents of the subsection
> template will actually be copied into the page itself, so the same
> subsection will look like this instead:
> |-
> | colspan="4" |
> === SE-PostgreSQL and related ===
> These three lines will have to be shifted around as a single unit, and
> a slight error in the syntax could scramble the whole table. So the
> downsides are loss of readability and ease of editing, and increased
> fragility.
I see. Still, the template calls read like line noise too ;-),
and seem to be prone to breaking in strange ways --- I'm still nowhere
near confident enough to commit changes without previewing. I don't
think that the above is materially worse than what we do now.
Comments from others?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-11-03 03:37:17 | Re: [edit] links in CommitFestSubSection headers |
Previous Message | Brendan Jurd | 2008-11-03 03:28:55 | Re: [edit] links in CommitFestSubSection headers |