From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Feature Request: define colour in relation to existing colour
Date: Wed, 21 Aug 2013 10:55:29 +0200 [thread overview]
Message-ID: <52148081.8070101@wxs.nl> (raw)
In-Reply-To: <CAANrE7pAqzQH0kP50pF31gr2CekOdEpF22-Zd2a_+SFpNqj2=w@mail.gmail.com>
On 8/21/2013 2:25 AM, Thangalin wrote:
> Hi,
>
> What would it take to extend \definecolor so that:
>
> \definecolor[ColourA][ColourB][t=0.5, a=1]
>
> defines a new colour (ColourB) based on an existing colour (ColourA)?
>
> I know that \definespotcolor[ColourA][ColourB][t=0.5, a=1] works, but
> it seems like \definecolor would also be a natural fit.
hm, afaik no one ever needed that (normally one defines colors once on
top of the document and there are seldom many of them)
anyhow, as general inheritance is pretty fuzzy i.e. cloning a spot color
and changing some rgb component or cloning a cmyk color and setting rgb
components it will not be a feature of definecolor
I've added \defineprocesscolor that cna be used as follows:
\starttext
\defineprocesscolor[red][r=.5]
\blackrule[color=red,width=\hsize,height=1cm]
\defineprocesscolor[redish][red][a=1,t=.5]
\blackrule[color=redish,width=\hsize,height=1cm]
\stoptext
But ... as there is some checking of the preferred color space (in
context each defined color has a preferred color space and there is also
a current colorspace that gets applied) you need to be aware of this:
\starttext
\defineprocesscolor[red][r=.5]
\blackrule[color=red,width=\hsize,height=1cm]
\defineprocesscolor[redish][red][a=1,t=.5]
\blackrule[color=redish,width=\hsize,height=1cm]
\defineprocesscolor[yellowish][red]
\blackrule[color=yellowish,width=\hsize,height=1cm]
\defineprocesscolor[yellowish][red][a=1,t=.5,y=.5]
\blackrule[color=yellowish,width=\hsize,height=1cm]
\defineprocesscolor[cyan][c=.5]
\defineprocesscolor[yellowish][cyan][y=.5]
\blackrule[color=yellowish,width=\hsize,height=1cm]
\stoptext
Now .. as you requested it, you're also the one who's going to wikify
it. I'll upload a beta later.
Hans
ps. Transparency operates independently of colors but I never figured
out a decent way to let that cooperate with existing colors that have
transparency specs without breaking compatibility so it might never
happen (in fact we have: current color space, current color, current
transparency).
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-08-21 8:55 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 [this message]
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
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=52148081.8070101@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).