Stuff I got done:
- Custom editor provider for todo.md.
This means that the Kanban board updates in real time when I make changes to todo.md, as well as a toggle that lets me convert between markdown and kanban board. - Had to refactor ~30% of my code to make that change.
Stuff I got done:
- Added styling for board, card, and column
- Now tasks render horizontally! (using flex)
Stuff I got done:
- Built JS algorithm to convert markdown string to card interface.
- Styling changes in style.css to make the cards look like cards.
- Remove hardcoded ‘todo’, ‘doing’, ‘done’ divs in HTML.
Since I want my kanban board to integrate with a todo.md file, I need to switch from just using the webview into using a custom editor and building a KanbanEditorProvider. That means I need to rewrite around 30% of my code, but it’s all goody.
I should probably create a GitHub branch instead of committing everything to main, but that’s too much of a hassle.
Recently I’ve noticed that my eyes have been feeling really dry and weak, apparently looking outside every 30 minutes helps with that? Now I’m looking outside my window every 30 minutes with the hopes that my eyes feel better, and they already do. I’ve also been getting less headaches, which is nice.
I already feel like an old man 🧓
Here’s what I did!
- Added symlinks for style.css and script.js
- Cleaned up JSX –> using the filesystem API
- used some javascript to build the rendercards function (also, learned javascript, bools)
Why am I building this?
I’m building this because I keep getting tool fatigue, I keep switching from todoist to notion to pen and paper, but nothing works! I’d rather just have a tool built into my environment so that I don’t have to worry about tracking my tasks, bonus points for if/when it’s satisfying!
I did a few lil things:
- I initialised the Git repo.
- I looked up how to make VSCode extensions (I have no idea how to build a VSCode extension).
- I initialised the WebView
I learned:
- How to init a GitHub repo using the CLI (git init, add, push, upstream, ect)
- You can make a VSCode extension using the “yo code” command, that gives you boilerplate.
- Using “esbuild” for the bundler gives me the fastest build times.
- Using npm cause less potential debugging. (since pnpm symlinks)
- For my typescript edits to keep working, I need a terminal running “npm run watch” so that it compiles to js.
- Learned about VSCode UX patterns for extensions.
- Understood a little more about what we’re doing, we’re going to be using “webview” to make our extension.
- Learned a lil HTML!
🥱🥱🥱
