search

damianfral / th

A command-line todo list manager in the style of http://stevelosh.com/projects/t/ written in Haskell.
Mozilla Public License 2.0
1 stars 3 forks source link

Future plans? #6

Open danse opened 7 years ago

danse commented 7 years ago

Hi, i am thinking to use this script to manage my todos, but i see that the last commit is dated 2014. I wonder whether you are using this, and planning to develop it in the future. For example i was thinking to add timestamps and other features. If you are using this, i could start using it as well and contribute to the code

damianfral commented 7 years ago

Hi @danse , I stopped using it some time ago. Since then I've been switching between more advance things like Asana, Trello, etc but actually I feel more comfortable with CLI tools. I've been thinking on extending th to support duration of tasks and sync with toogl. So, if you want to contribute with ideas/code, that would encourage me to work on this. :D

danse commented 7 years ago

I would be happy to do so! I use several tools written by myself in order to track todo lists, time and other quantities like money. I think that the data format is one of the main topics in order to have a set of tools that play well together. For example i can generate streamgraphs on files of the right format that keep my data, getting a result like the following for my time tracking data: screenshot from 2017-04-24 14-28-32

You mention Toggl. I was planning to write a conversion script from Toggl data to a data format that i can use for visualisation. I am also looking for a data format that is more standard, for example the one used by HLedger. There is a community developing tools and best practices around plain text accounting. I am collecting info in danse/margin#2.

This tool is about todo lists though. So, it's not exactly the same data as in plain text accounting, as far as i understand. Maybe let's discuss a bit about the data format we want to use in the long term. It would be great to use something standard that we both like, but i am afraid that such a standard does not exist.

For me, the command line is the first step in order to validate a concept. Once we define the data format we can easily built command line interfaces to interact with it, but later any kind of web or mobile application can be built that exports or imports data in that format. I have my own timetracker that exports data for me in the format i want.

I find that what i want from a todo list manager is to support online sharing and offline operativeness, so whichever format we define, it would be cool if the data files could be human readable and plain text, in order to use Git or any other version control system to keep tasks synchronised with a remote repo.

I think that we can chose between two directions, depending on our main use case:

  1. opt for a data format which plays well with existing repositories. This would probably be a single file, so that it does not clutter the repo
  2. go for the best that we can imagine, using freely the file system in order to maximise readability and usability. This means that a whole set of todo items could be stored in multiple folders and files, thus it would probably be better for the user to keep a repo for the todo files only