G'day Tux,

++ Thanks for this wealth of information. I played with everything but don't have time to go into it all, in any great depth, right now (it's late evening here): some funtime ahead for the weekend.

• xcolorsel — I had to change the shebang, but otherwise it worked out of the box; I like how you've displayed the full colour and the individual RGB components; I liked the second two dropdown lists ("/in name" & "/similar") which I see as being quite useful.
• dis_colors — That's handy to get the codes and gives an immediate visualisation of foreground & background combinations. Term::ANSIColor provides a variety of ways to specify colours (strings, constants & arrayrefs); I don't have an answer to how you might lay out the display to include them.
• vttests — I downloaded https://invisible-mirror.net/archives/xterm/current/xterm.tar.gz which was the latest. There are about 60 scripts in vttests/; I didn't see anything that looked like "color-tests"; I poked around in quite a few but didn't find the functionality you mentioned (i.e. "similar to your rgb_palette"). Could you provide specific filenames?
• ExtUtils::MakeMaker::prompt() — I was aware of this but thanks for mentioning it anyway (you weren't to know and it's possibly useful for others). I do like the feature-rich IO::Prompter module; the menus are perhaps my favourite bit.

At the outset, I'll say that I pretty much agree with what you said regarding light & dark backgrounds. In addition, I'm cognisant of accessibility issues (colour blindness, contrast, and so on).

At the start of this thread, I said that I didn't find the rgbRGB codes intuitive. Initially, this script simply printed a 6x6x6 grid of those codes and the colours they represented. At that point, it was just a quick-and-dirty piece of code to help me with that.

I then found the rNNNgNNNbNNN codes and realised, somewhat surprisedly, that I could use them. The script progressed from there, through multiple iterations, to what you see above. It was only after completion that I thought, "Others might find this useful; I should share".

For your, and indeed anyone else's, light background, I think you may just need to make some very minimal changes: for instance, white to black (2 instances; 3 if you've changed fg()) and cyan to green (1 instance). Alternatively, you could use "on_black" for all of the text; although, I think that might end up looking a little messy. If you do make such changes, I'd appreciate feedback on your choices.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.