While answering #878, I realized, that both user manual and quick guide could be improved. Goal should be to get first time users started as quickly as possible.
Thinking back to my first time contact with picocli I remembered it wasn't straightforward for me to get things up and running, either. Don't get me wrong: The picocli manual is very complete, concise and was/is of great help for me in m

Not sure if it's already possible but it would be great to be able to overlay/place, and if possible with z-index, an image such as a PNG, JPG, GIF, etc. on a console or on a cell.

Make it easy to distribute on Windows! I literally have no idea how to do this myself, so help wanted.

Currently creating a table with headers requires quite some effort.
However, it should be relatively easy to provide this functionality in the library.
At the very least some better examples could be supplied.

Here is a rather simplistic approach that works quite well:

const { table } = require('table');
const chalk  = require('chalk');

function printTable(data, options) 

I am trying to evaluate adapting ArduinoMenu to run under Mongoose OS, and am looking at a two stage implementation plan:

1. get it running on Linux (with a very generic serial input and output device, similar to the Blink or Button examples). I want to do this so I can quickly get the menus going, and make sure I really understand what's going on.

2. move it to Mongoose OS (with an ILI9341

We just released Chalk 3 with some large performance improvements. This is what I'm seeing with Chalk 3 and Node.js 12:

~/Downloads/ansi-colors/bench master*
❯ node index

# All Colors
  ansi-colors x 150,257 ops/sec ±0.95% (90 runs sampled)
  chalk x 490,982 ops/sec ±0.48% (94 runs sampled)

# Chained colors
  ansi-colors x 20,

The achievments list isn't spaced properly, after the "8:12pm" or other entries that don't have two digits, a space should be entered 'automatically' so the spacing remains the same.

see screenshot:

link

Currently the mxml_type_e enumerations are not named so it is obvious they are values of that type. Rename them to MXML_TYPE_foo to fix that.