ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jonathan Barchi <barchij@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: next beta
Date: Wed, 20 Mar 2013 12:36:54 -0400	[thread overview]
Message-ID: <CAFBQp-v8Tg6NLhVGHs0=M3vfhrwBqns7Ld+OMtBWS0_VLwjuBg@mail.gmail.com> (raw)
In-Reply-To: <514976B1.2050200@wxs.nl>

On Wed, Mar 20, 2013 at 4:43 AM, Hans Hagen <pragma@wxs.nl> wrote:
> On 3/20/2013 8:14 AM, Keith J. Schultz wrote:
>>
>> Hi Hans, All,
>>
>> I find this nomenclature confusing and a little confusing from a design
>> standpoint!
>>
>>         1)  Color of the text background should be separate from the rest
>>                of the cell background
>>
>>         2) the names should reflect to what they apply
>>
>> That said we should have:
>>         CTBGC == Cell text background color
>>         CTC      == Cell text color
>>
>>         CBGC == Cell background color
>>                        or
>>           CC      == Cell color
>>
>>         CBGCR   == Cell background color in the space right of text
>>         CBGCM  == Cell background color in space middle of cell( above
>> below text)
>>         CBGCL   == Cell background color in the space right of text
>>
>> True, these are a lot of options/parameters, yet it offers the most
>> flexibility and
>> a cleaner interface. Furthermore, one can understand the names of the
>> parameters.
>
>
> preamble scanning is already quite tricky and there was already CR CM CL so
> adding CT was a few lines of extra code
>
> (i will probably make a key/val based variant some day but that is no fun
> either ... 10 lines of setup per table instead of a one line preeamble)
>
> (and i'm forbidden to fundamentally change an important mechanism like
> tabulate right now as for sure it will break some things)

Further, the declaration of a tabulate environment already tends to be pretty
tight on space, so IMO a little bit of obscurity in these parameters - provided
they stay documented - is an acceptable price to pay for keeping the keys to
two letters (three would probably be OK too, esp. for less frequently used
ones).

>> Another, advantage is that one could and at a later point a feature for
>> inverting the
>> color of the text according cell color and/or text background color.
>>
>> regards
>>         Keith.
>>
>> Am 19.03.2013 um 23:46 schrieb Sietse Brouwer <sbbrouwer@gmail.com>:
>>
>>>> i.e. we already had CL CM and CR, so CT is new .. should be wikified.

I've added this to the wiki.

Just to be clear: CT provides an alternate method to colorize the
text, instead of
using the standard \color[foo]{bar} - right? There is already a
section on using
the \color command to colorize the text, so I want to make sure I'm adding this
correctly as a complementary mechanism, or fix it if I misunderstood.

- Jon

>>> The wiki [1] describes these \C* commands:
>>>
>>> \CR      color is applied to the background of the text and the remaining
>>> space on the right;
>>> \CC      color is applied to the background of the text only;
>>> \CM      color is applied to the background of the text and the remaining
>>> space on both sides;
>>> \CL      color is applied to the background of the text and the remaining
>>> space on the left.
>>>
>>> [1] http://wiki.contextgarden.net/Tabulate
>>>
>>> What does CT do differently than CC? It's not quite clear from the
>>> example.
>>>
>>> Cheers,
>>>
>>
>>
>> ___________________________________________________________________________________
>> 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
>>
>> ___________________________________________________________________________________
>>
>
>
> --
>
> -----------------------------------------------------------------
>                                           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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2013-03-20 16:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 22:00 Hans Hagen
2013-03-19 22:46 ` Sietse Brouwer
2013-03-19 23:03   ` Hans Hagen
2013-03-20  7:14   ` Keith J. Schultz
2013-03-20  8:43     ` Hans Hagen
2013-03-20 16:36       ` Jonathan Barchi [this message]
2013-03-20 20:27         ` Hans Hagen
2013-03-20  7:24   ` next beta (tabulate) Alan BRASLAU
2013-03-20  9:42     ` Hans Hagen
2015-04-15 17:08 ` next beta Aditya Mahajan
2015-04-16 12:45   ` Hans Hagen
2013-05-28 11:07 Hans Hagen
2015-04-15  9:05 Hans Hagen
2016-02-25 10:47 Hans Hagen
2016-03-03 17:34 Hans Hagen
2016-06-27  8:38 Hans Hagen
2016-06-27 10:28 ` Meer, Hans van der
2017-01-15 16:19 Hans Hagen
2017-01-17 19:13 ` Henri Menke
2017-01-17 19:23   ` Hans Hagen
2017-01-17 19:27     ` Henri Menke
2017-01-17 19:51       ` Hans Hagen
2017-06-12 15:25 Hans Hagen
2017-06-12 15:56 ` Mathias Schickel
2017-06-12 16:17   ` Hans Hagen
2017-06-13 11:18     ` Mathias Schickel
2017-06-13 14:46       ` Hans Hagen
2017-06-13 15:52         ` Mohammad Hossein Bateni
2017-06-13 16:18         ` Aditya Mahajan
2017-06-14  9:33         ` Mathias Schickel
2017-06-14 11:23           ` Hans Hagen
2017-06-13  6:06 ` Aditya Mahajan
2017-06-13  8:05   ` Hans Hagen
2017-06-13 12:47 ` Hans Åberg
     [not found] <mailman.575.1497365252.2080.ntg-context@ntg.nl>
2017-06-17 13:48 ` Jeong Dal
2017-06-18 11:00   ` Hans Hagen
2017-06-18 15:39     ` Jeong Dal
2017-06-18 22:56     ` Henri Menke
2017-06-19  7:36       ` Hans Hagen
2017-06-19  7:44         ` Aditya Mahajan
2018-04-14 16:51 Hans Hagen
2018-04-18  6:34 ` Otared Kavian

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='CAFBQp-v8Tg6NLhVGHs0=M3vfhrwBqns7Ld+OMtBWS0_VLwjuBg@mail.gmail.com' \
    --to=barchij@gmail.com \
    --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).