@caasion

Devlog 2 - Refining the Day View

In the last devlog, I showed a working editable timeline where you can move blocks around to schedule them.

This time, I completed the full functionality that I want for my app to have with making schedules.

There are two things: blocks and tasks. Blocks are units that you can schedule in your day. Tasks are items that you can complete in a day.

The timeline now allows you to create, edit block name, edit block times, convert a block into a checkable block (like a task + block), and add associations.

Associations are what really makes Kairos super powerful as it allows you to connect how you spend your time (blocks) and what you do (tasks) to a particular goal or area of focus in life.

These associations are defined in separate markdown files, and they influence the color of the blocks on the page.

The app is far from done, but now I can use it to schedule blocks and define tasks for a day!

Kairos is greek for “the exact, critical, or opportune moment for action.”

Kairos is for people whose time isn’t fully their own (students, employees, or anyone juggling shifting commitments) who need to decide how they spend their time before it’s decided for them.

This applies a lot for me. When I’m in school, I feel like I’m constantly juggling with school work, clubs, and trying to have fun with friends. Sometimes it feel like I’m dropping a few balls while juggling everything.

I built this as a alternative to my other productivity plugin Holos because I realized that task-based planning is not as effective as time-based planning, where you actually have to specify when you are planning to do something.

I hope that this will be the last productivity app that I build (and that it works well for me and others!!!)

It turns out I’ve been building a retreival augmented generation system for AI all along.

I did this without even realizing it was called that!

Since last time, I’ve hooked up a text-embedding engine to turn text into vectors.

Next, I did some math to calculate cosine similarity between the vectors so I can see how similar these vectors are. I also added some helper functions to help retrieve the vectors that are similar enough and only take the top K (5) values.

I hooked this all up to the command line chat!

It still doesn’t seem to remember properly though… I’m going to spend some time to debug this.

My linear algebra test is coming up soon, and I need to study for it, but I also really wanted to build something, so I built a tool to help my peers and I study lin alg.

The visualizer helps you see what it means for a matrix to be a linear transformation and also shows you concepts like eigenvectors and eigenvalues.

I made a conversation with the AI call!

Instead of relying on AI, I’m forcing myself to read documentation to go slow (instead of having everything done for me).

The first hour was a little bit of experimenting and planning.

I made some AI calls myself and also sketched a simple architectural diagram.

Some more fixes to really get the plugin to be useable by other people!

v4.0.5

• Add ability to change track effective dates in Workbench
• Change how track effective dates work
  • Only 1 interval of active dates
  • No longer dependent on its internal project contents
• Remove old, unused settings options

Releasing and shipping something for other to use really isn’t about just pushing code.

After writing up my release, I thought I would be done, but when it actually came to test the plugin out on my vault, I ran into some issues that made the plugin really unusable, so I’ve been working towards fixing that.

Here’s what I addressed:

• Added the ability to create projects and tracks (After the redesign, I forgot to add a button to create these basic things!!)
• Removed directly style sheet injection (Obsidian doesn’t like it when I add css using javascript)
• Added the ability to define start and end date for projects with 1 phase

I still got some bugs to fix and production issues to address!

I’ve been working on the actual v4 release of the plugin. But it’s been taking a lot longer than I thought.

While testing the plugin in my test environment, the plugin runs quite smoothly. However, when testing it in my actual vault, it is a lot slower and less performant than I expected. Waiting 9 seconds just to switch a view is such a deal-breaker.

Regardless, here is what I did since the last devlog:

• Added a panel to edit tracks in the “Workbench” view (When redesigning the views, I forgot to provide a place for people to edit their tracks)
• Fixed styling of the Gantt chart view
• Attempted to optimize performance with rendering tweaks and by removing some debounce conditions

I added the capability for partial task completion. At first, I thought it would be a super simple task, but because of how tightly integrated everything is in the project, it took me a little longer than I thought it would.

Hey everyone! I’ve been building Holos, a productivity plugin that connects big-picture life planning to daily execution, all inside Obsidian.

The core idea: a three-tier system where Tracks define what you’re focusing on in a phase of life, Projects drill into specific areas, and a grid planning view turns everything into executable daily tasks. All stored in plain markdown files in your vault.

I built it because I kept overcommitting and losing the thread between my seasonal goals and what I was actually doing day to day. It’s been my daily driver for a while now.

This project has gone through many iterations, and I’ve recently started reworking the UI to make the plugin truly usable and intuitive for new users.

I would appreciate any feedback on the UI. Meanwhile, I am working on the task and rendering logic to make sure things are working as intended!

Hey everyone! I’ve been building Holos, a productivity plugin that connects big-picture life planning to daily execution, all inside Obsidian.

The core idea: a three-tier system where Tracks define what you’re focusing on in a phase of life, Projects drill into specific areas, and a grid planning view turns everything into executable daily tasks. All stored in plain markdown files in your vault.

I built it because I kept overcommitting and losing the thread between my seasonal goals and what I was actually doing day to day. It’s been my daily driver for a while now.

This project has gone through many iterations, and I’ve recently started reworking the UI to make the plugin truly usable and intuitive for new users.

I would appreciate any feedback on the UI. Meanwhile, I am working on the task and rendering logic to make sure things are working as intended!