espehon / clocky-cli Goto Github PK

https://github.com/espehon/clocky/blob/f30fd7d08074c9f1af6f9b3f6d3a90fb356b90b6/clocky_pkg/clocky.py#L118

clocky was originally made to be "easy" installed but should now be changed to work with PYPI

Colorama is much more flexible and cross-platform

• #2
• #3
• #4

Current version is defined in inin.py
Should be stored in the toml and read in at runtime as metadata

• Define in the ini file as color1,color2,color3,...
• Split into a list after importing
• Apply the list to colour_scale() function (not the color_codes dict)

https://github.com/espehon/clocky/blob/896c754c5f595efdd1a8e919847a9b07aee11ea8/clocky_pkg/clocky.py#L37

The original color scale was made for an Ubuntu theme with a burgundy-like color as its 'magenta'.
If most themes use purple as their magenta, then the color scale should put purple between white and blue.

"\033[" should not appear anywhere in the code

The configparser module supports comments while the json module does not
There should comments for the user

{color_codes['reset']}
returns KeyError: 'reset'

#TODO : Should print a bar chart for hrs worked for N days/weeks.

https://github.com/espehon/clocky/blob/82d9a9273daae7819880daff60d7782e73f985e0/src/clocky/clocky.py#L149

I think I should swap out some of the current demo images with those of different color themes. Not everyone (probably no one) will be using my ubuntu-like theme. Should also note what each demo image is depicting.

• Alt Color Theme Demo Images
• Titles For Demo Images

Some advanced terminals can support ligatures. E.g. === will render as ≡.
This can ruin some TUI elements in console apps. If your --chart output has random tribars in it, disabling ligatures will resolve the problem.

Here is an example of the chart with tribars:
[============================≡==≡===============]

Nothing should need to be in the init file.
Suggesting the use of a json file in $HOME/.config/clocky/

Ideal: $HOME/.local/share/clocky

This happens on line 581