Thanks for this. I've used kanban.bash [0] but I'm not married to it. I'll have to try clikan soon. I did make a slight modification to kanban.bash so that I could have a kanban board per directory/project [1].
Very nice looking! Didn't even know terminal-based kanban was a thing. A quick search turned up a couple of other [0] [1] similar looking projects (in addition to kanban.bash which was already mentioned)
is there particular reason why the commands take seemingly superfluous option thing; i.e. why `clikan promote --id [task id]` instead of just `clikan promote [task id]` etc?
probably me being dumb. IIRC the CLI library in play is Click, and it wasn't the most flexible things to work with - though infinitely better than parsing args manually. tis a good note though. will look into it.
It seems the columns are hardcoded (todo, in-progress, done). Is it possible to create different columns from the configuration or would that require a code change?
They are hard-coded. I think they _could_ be made configurable, just managed as "strings" with in the code. If you're really interested please create an issue at the Github project.
That's an interesting thought. I suppose if it works from the Python REPL it'd work there. Will dig into that a bit when I can. Thanks for the feedback!
Comments
Thanks for this. I've used kanban.bash [0] but I'm not married to it. I'll have to try clikan soon. I did make a slight modification to kanban.bash so that I could have a kanban board per directory/project [1].
[0] https://github.com/coderofsalvation/kanban.bash
[1] https://github.com/lpsantil/kanban.bash/commit/598505dfd91f2...
Very nice looking! Didn't even know terminal-based kanban was a thing. A quick search turned up a couple of other [0] [1] similar looking projects (in addition to kanban.bash which was already mentioned)
[0] https://github.com/klauscfhq/taskbook
[1] https://github.com/smallhadroncollider/taskell
is there particular reason why the commands take seemingly superfluous option thing; i.e. why `clikan promote --id [task id]` instead of just `clikan promote [task id]` etc?
probably me being dumb. IIRC the CLI library in play is Click, and it wasn't the most flexible things to work with - though infinitely better than parsing args manually. tis a good note though. will look into it.
It seems the columns are hardcoded (todo, in-progress, done). Is it possible to create different columns from the configuration or would that require a code change?
They are hard-coded. I think they _could_ be made configurable, just managed as "strings" with in the code. If you're really interested please create an issue at the Github project.
Just an idea: create also addon for Blender's "Python Console".[0]
[0] https://docs.blender.org/manual/en/latest/editors/python_con...
That's an interesting thought. I suppose if it works from the Python REPL it'd work there. Will dig into that a bit when I can. Thanks for the feedback!