search

BradleyChatha / jcli

A CLI framework for D
MIT License
23 stars 4 forks source link

What to do about some of the utility modules. #43

Closed BradleyChatha closed 3 years ago

BradleyChatha commented 3 years ago

shell.d is just depressing.

userio.d is next to useless, I had bigger plans for it but I really can't be bothered with it.

I like ansi.d, it just needs some QoL (e.g. a type that can concat multiple AnsiText).

config.d is to specifically aid in prototyping and smaller, simpler tools, so I'm fine with that.

helptext.d is a bit overkill for its purpose, but it works enough to leave it alone.

For the latter 3, I think I'm just going to keep them as-is and simply improve upon them.

The first 2 however... shell.d basically only exists for Shell.pushLocation and Shell.popLocation, and userio.d is as I said, mostly useless. I'm considering whether to remove them in the future or not.

BradleyChatha commented 3 years ago

Oh, there's also text.d, which I feel will pull it's weight when/if I decide to start adding things like a Table or Progress bar component.

It does also beg the question about whether JCLI should be split up into different parts, so those that just want the command parsing don't have to include a bunch of baggage.

BradleyChatha commented 3 years ago

I've rebuilt ansi.d as jansi as an example of what I mean.

BradleyChatha commented 3 years ago

I think I'll just keep them there, but not touch them anymore.