Am 08.09.2013 um 02:33 schrieb hwit...@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, hwit...@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. Wolfgang ___________________________________________________________________________________ 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 ___________________________________________________________________________________
