From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Feature Request: define colour in relation to existing colour
Date: Wed, 21 Aug 2013 11:27:29 -0700 [thread overview]
Message-ID: <CAANrE7pcoYHOavBwb+zaHt1iku4wpjNLcBT73OwOTY18fsg4gA@mail.gmail.com> (raw)
In-Reply-To: <52148081.8070101@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 913 bytes --]
For context, here is the question on TeX.SE:
http://tex.stackexchange.com/questions/129297/define-colour-transparency-in-relation-to-existing-colour
I agree with Marco:
Are you sure it's a good idea to add another colour definition
> mechanism? Then we have
>
\definecolor
\defineglobalcolor
\definenamedcolor
\definespotcolor
\definemultitonecolor
\defineprocesscolor
That is a little confusing. I can understand a speed requirement, but
surely that can be taken into consideration beneath the definition?
\definecolor[A][r=1, g=0, b=0]
\definecolor[B][A][a=1, t=0.5]
That seems fairly reasonable. Also, why not embed colour spaces within the
command?
\definecolor[A][colorspace=spot]
\definecolor[A][colorspace=multitone]
\definecolor[A][colorspace=pantone]
One command to define a colour, rather than several commands for specific
variations of defining colours.
Kind regards.
[-- Attachment #1.2: Type: text/html, Size: 1444 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-08-21 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 0:25 Thangalin
2013-08-21 8:55 ` Hans Hagen
2013-08-21 11:11 ` Marco Patzer
2013-08-21 12:10 ` Hans Hagen
2013-08-21 14:23 ` Aditya Mahajan
2013-08-21 15:18 ` Hans Hagen
2013-08-21 15:28 ` Aditya Mahajan
2013-08-21 18:27 ` Thangalin [this message]
2013-08-21 22:06 ` 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=CAANrE7pcoYHOavBwb+zaHt1iku4wpjNLcBT73OwOTY18fsg4gA@mail.gmail.com \
--to=thangalin@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).