ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: "Rudd, Kevin" <kevin@lps.umd.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: problem embedding TABLE macros within wrapper macros "to reduce repetitive complexity")
Date: Wed, 9 Sep 2020 07:57:36 +0200	[thread overview]
Message-ID: <bf33a2cb-e555-c279-8561-0c73d439236d@gmail.com> (raw)
In-Reply-To: <DM5PR15MB192969428401DDC6188A47B4F1290@DM5PR15MB1929.namprd15.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 1496 bytes --]

Rudd, Kevin schrieb am 09.09.2020 um 00:30:
> Thanks. The immediate goal is to make a ”quad chart” w/ different 
> pains in the four (2x2 => NW, NE, SW, SE) quadrants. It seemed that 
> the concept was scalable to any NxM (even with multi-cell 
> spreads---useful for larger structured posters) based on TABLE. But 
> I'd settle for 2x2 at the moment; at one point I'd thought of 2x2+1 
> having a spanning block for publication references per slide but 
> decided a separate publications slide was a better idea visualy..
>
> If they have to see an end command, would before/after tags work 
> around a framedtext or buffer structure?
>
> 1. 2x2 panes, layout order not important, all panes independent; no 
> flow (like Framemaker used to do) requiredbetween panes.
> 2. was going to have inner frames (i.e. + frame for 2x2 which was 
> trivial to specify in TABLE) to separate the panes
> 3. other than wanting the + frame, inner margins &c. for panes wsn't 
> an issue either way.

When you need one than single block per line this definition

\define\startPaneRow{bTR\bTD}
\define\stopPaneRow{\eTD\eTR}

doesn't make sense because you limit yourself and after each table cell 
there is a new row.

While you can write code which moves your blocks around you should ask 
yourself the question is it worth it. When you have only two or three 
posters in this format use the extra commands for table rows and cells 
because it takes more time to write something which does the work.

Wolfgang


[-- Attachment #1.2: Type: text/html, Size: 2212 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-09-09  5:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08 17:50 Rudd, Kevin
2020-09-08 20:31 ` Wolfgang Schuster
2020-09-08 22:30   ` Rudd, Kevin
2020-09-09  5:57     ` Wolfgang Schuster [this message]
2020-09-09 13:02       ` Rudd, Kevin
2020-09-09 15:32         ` Rudd, Kevin
2020-09-10 13:17           ` Wolfgang Schuster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bf33a2cb-e555-c279-8561-0c73d439236d@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=kevin@lps.umd.edu \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).