org-day-planner
*I'd like to make something like Goalist, but that uses org-mode as a backend.
I find the Goalist interface excellent for a really fine-grained day plan. But it's not libre software, and the file format is not easily shareable.
It would be a fun project to recreate some of its functionality using org-mode as the underlying system.
It'd probably make sense to build it as a native Android ap, but If I did it myself, I'd probably use vue.js as a means to learning that.
1. TODO
[X]Add in current time marker[X]Start intervals from time of first TODO[ ]Display DONE items in separate calendar with visibility toggle[ ]Parsing nested TODOs[ ]Error handling[ ]Writing back to file[ ]Colour based on category of item[ ]Show items only for current day[ ]Allow arbitrary positioning of items in the todo file - so you can split it into sections
2. Log
2.1.
Wow, this for obsidian looks nice. https://github.com/lynchjames/obsidian-day-planner
2.2.
Separate file of active timestamps. Increase decrease time. Move up and down. Set which files to include.
It's kind of a fancy agenda view, I guess.
2.3.
OK, so Quasar would be a decent option it seems. Plenty useful components out of the box. It has QCalendar too, which I might be able to crib something from.
I saw a bunch of handy looking Vue calendar components at Made with Vue Calendars page. I wonder, can you use non-Quasar Vue components easily enough in Quasar? To be seen.
2.4.
Made good progress on this today. Got basic parsing set up with orga, and basic rendering of items with Quasar and QCalendar.
Still plenty plenty needs doing though. Not a small project by any means. A good learning one. I'd just like to get it to the point where I can use it on single files that I probably create elsewhere, increase/decrease the time on the items, and then save back.
First, just be able to read a single file and display it usefully. It would be read-only and I would edit it probably in orgzly for now.
I wonder if that requires use of a store?
2.5.
Really good progress. Picking up some Vue bits and pieces which is great. Added a store via Vuex today, and learning some of the details of how getters, mutations and actions work with that. Quasar makes it super simple to add these bits of plumbing in.
2.6.
Good work on it today. Refactoring some of the way active tasks are set, using the store and an array of tasks in there. Vue is very very nice for handling state updates and that just ripping through to all of the display. Quasar is really nice for giving a bunch of UI components to work with.
So where have I got? Some basic parsing of org files. Basic display of the info in there and a bit of interaction for clicking and seeing more details. It's still all read-only. The next big step would be allowing for making changes to the times of tasks, and then writing that back to file. That'll be a tough nut to crack I think.
3. Elsewhere
3.1. In my garden
Notes that link to this note (AKA backlinks).