Revamp message formatting #49

New issue

Closed

opened 2023-03-08 08:53:50 +00:00 by badPointer · 4 comments

badPointer commented

2023-03-08 08:53:50 +00:00

(Migrated from git-old.n64.cc)

Use font weights in message formatting.
Package managers like pacman make use of font weight to symbolize the difference of messages from one (e.g. package name and package version)
Utilize colors in a classic fashion.
Aforementioned pacman utilizes white for most text and shades of gray for package versions (as seen on the reference image). For the indicators of a main stage, the :: symbol uses an accent color (blue in the screenshot), and for errors a generic red color is used for the "error" text only, not the whole message.
Indicate stages more obviously.
As seen in the screenshot, pacman makes use of indentation, symbols such as :: and ⇒ and numbering stages like (4/6). This makes following the process easier and allows easier debugging for what stage failed.
Use more varied Unicode symbols.
This is more of a UI enhancement, and doesn't really affect usability all that much but it would be nice.

For example, the dot symbols used in docker-compose v2 are animated while the command is running, which again makes following the process more user-friendly, and has the added benefit of letting the user know if the program is "stuck" or not.

1. Use font weights in message formatting. Package managers like pacman make use of font weight to symbolize the difference of messages from one (e.g. package name and package version) ![image](/uploads/25e0b6648b54cae5f1ed0abb212dadb9/image.png) 2. Utilize colors in a classic fashion. Aforementioned pacman utilizes white for most text and shades of gray for package versions (as seen on the reference image). For the indicators of a main stage, the :: symbol uses an accent color (blue in the screenshot), and for errors a generic red color is used __for the "error" text only__, not the whole message. 3. Indicate stages more obviously. As seen in the screenshot, pacman makes use of indentation, symbols such as :: and ⇒ and numbering stages like (4/6). This makes following the process easier and allows easier debugging for what stage failed. 4. Use more varied Unicode symbols. This is more of a UI enhancement, and doesn't really affect usability all that much but it would be nice. ![image](/uploads/a1c66a757a6d9194778c0d4bb2d889d0/image.png) For example, the dot symbols used in docker-compose v2 are animated while the command is running, which again makes following the process more user-friendly, and has the added benefit of letting the user know if the program is "stuck" or not.

badPointer commented

2023-03-08 08:55:05 +00:00

(Migrated from git-old.n64.cc)

changed the description

badPointer commented

2023-03-08 08:55:21 +00:00

(Migrated from git-old.n64.cc)

changed the description

netkas commented

2023-04-03 15:35:02 +00:00

(Migrated from git-old.n64.cc)

Certainly doable but would require a lot of re-working to make sure things work correctly, will play around with this idea.

netkas commented

2023-10-18 01:33:01 +00:00

(Migrated from git-old.n64.cc)

Implemented a newly designed progress bar in #2605b8d2181f573360b14170aa7b08b42b62a60e, however; I don't see the need for stage indicators just yet. The progress bar is a nice addition though.

Implemented a newly designed progress bar in [#2605b8d2181f573360b14170aa7b08b42b62a60e](https://git.n64.cc/nosial/ncc/-/commit/2605b8d2181f573360b14170aa7b08b42b62a60e), however; I don't see the need for stage indicators just yet. The progress bar is a nice addition though.

netkas (Migrated from git-old.n64.cc) closed this issue

2023-10-18 17:53:41 +00:00