| It's cool to hear from you and see you're planning on working on a lot of this. > There is a little circle indicator on a task with the number of total vs done items on a task checklist, similar to how github does it. Is that what you meant? Yes and no - yes in the sense that that's basically what I'm talking about, but no in the sense that when I saw that button I was looking more for "a system of progress" - a way to configure what counts as progress, maybe? A progress bar of some sort, with different ranges. Something which acts more of a customizable tool than a single input field. Maybe something that lets you define weights to what counts as progress, or a number of days of work you expect things to take, or something of that form? This isn't so much me saying X feature is a good idea, but to describe what the mismatch was for me between expectation and result. > you'll need to create a task with a due date of next Tuesday and a repeating schedule of every week / every 7 days. Oof. I should have guessed that as a possibility. That's one of those fun workarounds you only get to know when you designed the system or get really invested in it and have to work around the flaws. I used Crontab (and making it so that you can't open a template twice) to handle scheduling - putting a UI over it - it's been pretty darn good, but crontab also has some serious flaws in it - mostly around things like repeating tasks once every X > 5 days. For hourly/monthly/day-of-month and day-of-week, it works very well though. > Out of curiosity, what are you building? It's hard to describe or show because it's a personal project with no presence online. I'll focus on the differences from Vikunja. My system: Focuses on repeating tasks first - it basically assumes everything inside of it will be a repeating task. I made the *mistake* of making "repeating templates" the first class citizen, so you don't create goals, you create templates and then use those templates to open up a "todo item". Focuses on much "smaller grain" tasks - things that you might do multiple times a day. Lets say, getting up every 3 hours while you're at work. It's more "building habit" focused than it is project focused. Scenarios for its use might be ensuring that you water your plants every day, and having the app force you to upload pictures of the plant in order to say "I'm done" - then you can go back into your history and see your plant grow over time. You might set up a task that will force you to sit quietly for 10 minutes every day. You might set up a list of exercises in one of the templates and the app will pull 2 random exercises every time that task cycles open. Is mobile first, which is super important for day to day data entry. There are no left/right bar systems because I assume you're going to use it on your phone and it's designed to be responsive. It works on the desktop, but it's not designed for the desktop. It's built around one-user. It wasn't built considering multi-user situations, although I want to be able to have that work as well - another mistake I've made creating it, because I'm going to have to redesign half the stupid thing to handle multi user scenarios and how to do permissions. Families and businesses will find this important, so it's a really really essential feature I just didn't bother with because I don't use it. |
Gotcha. Thanks for the input!
> I used Crontab (and making it so that you can't open a template twice) to handle scheduling - putting a UI over it - it's been pretty darn good, but crontab also has some serious flaws in it - mostly around things like repeating tasks once every X > 5 days. For hourly/monthly/day-of-month and day-of-week, it works very well though.
Crontab sounds nice but I probably can't give that to someone who has never used it. Still like the idea to use it to handle repeating intervals though.
Your tool sounds nice. Like the sweetspot between "here's a thing I need to do regularly" and the usual habit trackers.