ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: [***SPAM***] YATM (Yet Another Table Method)
Date: Sun, 08 Sep 2013 17:02:24 +0200	[thread overview]
Message-ID: <522C9180.8080309@wxs.nl> (raw)
In-Reply-To: <70B48C5D-10E8-4C6B-972B-5243A2F33D6E@gmail.com>

On 9/8/2013 2:17 PM, Wolfgang Schuster wrote:
>
> Am 08.09.2013 um 02:33 schrieb hwitloc@gmail.com:
>
>>
>> Thanks for the explanation.
>> Providing the mapping feature with  \mapTABLEtoxtabl  and \restoreTABLEfromxtable
>> was a very good choice.
>>
>> Cheers
>>
>> Hans Hagen  wrote:
>>
>>> On 9/7/2013 3:31 AM, hwitloc@gmail.com wrote:
>>>>
>>>> I just noticed the YATM, "yet another table method", built in ConTEXt, called "extreme tables", which is said to be a variant of the natural table mechanism.
>>>>
>>>> Is extreme-tables a superset of natural-tables functionality?
>>>>
>>>> Is the future in extreme-tables and will natural-tables eventually take a back seat and then fade away, being surpassed in development, features and usage?
>>>
>>> - the natural tables will stay (but frozen
>>> - you can overload them: \mapTABLEtoxtabl \restoreTABLEfromxtable
>>> - xtreme tables have more protential for extensions without
>>> sacrificing speed
>>> - xtreme tables are faster but for normal use both suit
>
> Do you plan to add something equivalent to \setupTABLE[<row>][<column>][<settings>]
> because xtables lack the function to set values for certain rows/columns.

in TABLE that is both flexible and a slow-downer but in xtreme table we 
have named cells, rows, cellgroups, rowgroups (also a bit better 
abstraction and fits nicely in the setup handler; in TABLE is boils down 
to storing the setup and reparsing)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2013-09-08 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07  1:31 hwitloc
2013-09-07 11:04 ` Hans Hagen
2013-09-08  0:33   ` hwitloc
2013-09-08 12:17     ` Wolfgang Schuster
2013-09-08 14:41       ` hwitloc
2013-09-08 15:04         ` Hans Hagen
2013-09-09  7:13           ` Procházka Lukáš Ing. - Pontex s. r. o.
2013-09-09 10:29             ` Hans Hagen
2013-09-08 15:02       ` Hans Hagen [this message]
2013-09-08 15:50         ` Wolfgang Schuster
2013-09-08 23:18           ` Hans Hagen

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=522C9180.8080309@wxs.nl \
    --to=pragma@wxs.nl \
    --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).