61–70 of 97 posts
I love vikunja. I set it up on my raspberry pi and been using it daily
I’ve been a paying Todoist customer for many years. For some reason, they steadfastly refuse to introduce blocking/blocked by flags. It seems so strange to me to do all the hard work of allowing arbitrarily nested projects and tasks, sub-tasks, labels, complex filters and collaboration, but then not do dependencies. Imo dependencies is the big difference between something you can use on complex projects, and a “mere”…
I don't want to steal the thread (lets focus on Vikunja), but I currently use Obsidian and am trying to achieve DAG with creating taxonomies using some extra plugins like Dataview and Breadcrumbs. It's basically `markdown notes connected`, which allows lots of freedom in creating such taxonomies. It is still not easy to visualize it all the way I imagine it. I would really like to have it visualized after all, think seeing it all visualized (and even being able to work directly with it) helps a lot.
For me it is a big step from not-so-useful lists of tasks... simple lists of tasks are simply useless for me.
Earlier quoted context omitted.
Can you elaborate a bit on what it means to establish a DAG? I know what DAG is, just not sure what is the application here.
Rather than just a pile of tasks, the ability to establish dependencies. This task must be done before that one. Ideally then, given all these tasks and their dependencies, what should I work on next?
When one subtask is done, you check it off.
"Ideally then, given all these tasks and their dependencies, what should I work on next?"
I doubt a system can automatically propose the ideal task to work on anyway. There will be many tasks equally important and which are blocking another main task. So you would anyway have to select something by hand.
And if you would be presented with only one task to do right now, it might not be a suitable task for other practical reasons which cannot be specified using dependencies, priorities, schedules etc.
If the system gets too advanced it gets in the way more than helps. Personally I think it's better to regularly and manually walk through the list and update priorities, texts, task states, dates etc as things progresses and changes. And then you get a good overview picture of your project in the back of your head.
I'm biased. I'm making a tool that's kind of like this one. Please keep that in mind, because I'm about to give a whole bunch of criticism here. First things first, the UX and UI is really neat and there's lots of really good design and thought put into how fast the app is and how well it is handling a whole bunch of users. I was sitting in there with everyone in hacker news creating tasks and it was keeping up amazi…
I love vikunja. I set it up on my raspberry pi and been using it daily
That sounds like an excellent idea. Thanks for pointing me that way. I might repurpose the pi-hole for this and run these side by side. Not an expert here so in case you have some guidance or blogs to direct me to, please do.
First things first, I will probably not be using it (have a working solution for the time being). I just wanted to check if AND works on labels (AKA tags), which is a pet peeve of mine. Unfortunately, labels are not working for me at all (I cant figure out how to access a single label to get list of tasks with this label, not to mention doing filtering with `label1` AND `label2`).
Funny. I just stumbled upon this yesterday. The only thing that I wish to see improved is having the backend serve the frontend from the same docker container. It's a bit of a hassle to use nginx as a proxy in the docker compose setup (or in fact set all of that up on my Synology NAS).
Initially I was also interested in this. There is the staticpath option in the backend config. You can point it to the directory of the frontend files. Theoretically, both the backend and the frontend could be served by the builtin webserver. Unfortunately, for this to work most frontend URLs must get rewritten/rerouted to /index.html and this does not seem to be implemented. Shouldn't be too complicated though.
Somewhat related to to-do apps, there was an application back in the classic Mac OS days that I remember (although I don't remember the name) which worked in a way I don't think I've seen since, but seems like a pretty reasonable approach to recurring to-do tasks. Some repeating tasks have to happen on a fixed schedule, e.g. put the trash out every Tuesday night. But many (most?) of my repeating tasks a) have quite a…
[0]: https://community.vikunja.io/t/repeatable-tasks-appear-to-ju...