I tried to use this module on windows and found that if I override the isSupported() method to return true, the coloring works just fine, but otherwise the library thinks that coloring is not supported and so does not color the output.

New you can use all xterm-256 colors. Add following colors : light_gray, dark_gray, light_red, light_green, light_yellow, light_blue, light_magenta and light_cyan

Add 2 color converter gray and rgb.

gray => 24 level of gray. you can use gray[0-255] of gray[0-100%] rgb => 216 colors. you can use rgb[0-255|0-100%,0-255|0-100%,0-255|0-100%]

ex :

<?php
$c = new Colors\Color();
echo $c('gray')->fg('gray[75%]');
echo $c('color')->fg('rgb[200,10,30%]');

Love the project. Thanks a lot for it.

There are certain situations where forcing colors.php to output colors is desirable regardless of whether php is reporting that STDIN is a tty. In my particular situation grunt (node) is executing a php script using colors.php and I am unable to pass the tty to php regardless of what I do in node. Perhaps others will also experience a similar problem, and having the option will be as useful as it is to me.

Add support for a center method.

• Includes a test coverage
• Supports UTF-8 / multibyte strings
• Supports multiline strings

<?php
echo $c('')->center(80)->bg('blue') . PHP_EOL;
echo $c('Hello World!')->center(80)->white()->bold()->bg('blue') . PHP_EOL;
echo $c('This is centered text!')->center(80)->white()->bg('blue') . PHP_EOL;
echo $c('')->center(80)->bg('blue') . PHP_EOL;

Did not add anything to the example file or documentation.

Can you please release version 0.4 so we can use the new colors. I'm more comfortable with using a stable version instead of an unstable dev-master in Composer.

Thanks!

I went through the code and updated link references to use the docblock coding convention. Mainly just two links. I was wondering if the docblock coding convention way of doing things was something being considered for this project?

Changed log

• Add the php-7.2 and php-7.3 tests in Travis CI build.
• Set the PHPUnit be 4.8 version to support the latest stable PHPUnit versions in the future.
• Using the class-based PHPUnit namespace to be compatible with latest stable PHPUnit version.
• Remove the require_once 'PHPUnit/Framework/Assert/Functions.php'; file because this is not necessary and using the $this class instance for every assertion methods defined in PHPUnit\Framework\TestCase` class.
• The satooshi/php-coveralls is deprecated. Using the php-coveralls/php-coveralls instead.

$c->setTheme(
    array(
       'green' => ['green'],
    )
);

leads to recursion between:

Colors\Color->stylize() /src/Colors/Color.php:210
Colors\Color->applyUserStyle() /src/Colors/Color.php:152

This way it's possible to use colorize() more efficiently everywhere, without having to re-instance the class. Example: echo Color::instance()->colorize('<bold>ERROR:</bold> You made a mistake');

echo $c('Hello World!')->white()->bold()->highlight('green') . PHP_EOL;

if I use this in object and it will be like this: public $c = new \Colors\Color(); $this->c('Hello,World!); And this will give a message : Call to undefind method xxx\xxx::c();

setString method can be used to set the content, $c('Hello World!') cannot be used in some situations.

$c = new Color();
echo $c->setString('Hello World!')->white;

As title, I think it's time to drop the php-5.x version supports.

The php-5.x versions are too old to maintain and they're not maintained by official team anymore.