From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: imbalanced columns
Date: Thu, 15 Jul 2010 13:37:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1007151330270.10484@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <4C3F4170.5080600@gmx.net>
On Thu, 15 Jul 2010, Peter Rolf wrote:
>>> also: i can't imagine how a user interface for this should look like.
>>
>> \setuptables[spanalign=balance]
>>
>
> right. you can implement all kind of different spanning algorithms. i
> would expect that 'balance' would share the additional space equally on
> all involved columns.
>
> but table macros in tex are really ugly. you need tons of bookkeeping
> data for maxima, styles, multi-column|row, whatever. and tex has no data
> types for bookkeeping (like a programming language), so you have to
> store all the data in macros, dimens... it's a complete mess. have a
> look at the macro definitions and you will agree :)
>
> anyhow, i expect much better functionality (e.g. clever spanning
> alternatives) with a lua based table implementation. we have to wait for
> that.
Also remember that the starttable macros are just a wrapper around TaBlE
macros written by Michael Wichura. I don't know if those have enough hooks
to support a high level interface.
Have you tried using natural tables. Now you can use them with almost the
same amount of typing as the old table macros.
\startTABLE
\NC text 1 \NC text 2 \NC\NR
\NC text 3 \NC text 4 \NC\NR
\stopTABLE
and you have a high level interface of \setupTABLE (although I do not know
if natural tables support equal column widths)
Aditya
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-07-15 17:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 18:42 Idris Samawi Hamid ادريس سماوي حامد
2010-07-14 18:51 ` Idris Samawi Hamid ادريس سماوي حامد
2010-07-14 20:26 ` Peter Rolf
2010-07-15 0:35 ` Idris Samawi Hamid ادريس سماوي حامد
2010-07-15 8:33 ` Peter Rolf
2010-07-15 14:53 ` Idris Samawi Hamid ادريس سماوي حامد
2010-07-15 17:12 ` Peter Rolf
2010-07-15 17:16 ` Idris Samawi Hamid ادريس سماوي حامد
2010-07-15 17:28 ` Peter Rolf
2010-07-15 18:04 ` Peter Rolf
2010-07-15 17:24 ` Peter Rolf
2010-07-15 17:37 ` Aditya Mahajan [this message]
2010-07-15 17:45 ` Tables for newbies [WAS Re: imbalanced columns] Idris Samawi Hamid ادريس سماوي حامد
2010-07-15 17:57 ` luigi scarso
2010-07-15 18:42 ` Hans Hagen
2010-07-16 13:05 ` Peter Münster
2010-07-16 15:51 ` Idris Samawi Hamid ادريس سماوي حامد
2010-07-16 18:21 ` luigi scarso
2010-07-15 18:43 ` imbalanced columns Hans Hagen
2010-07-15 18:47 ` Idris Samawi Hamid ادريس سماوي حامد
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=alpine.LNX.2.01.1007151330270.10484@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.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).