2022-12-04
clawe
> TODO pomodoros backend crud clj tests
> TODO pomodoros stored on the focus backend
as a list
> TODO 'journal' clawe widget that shows in the journal workspace
> TODO focus widget cruds an arbitrary "MODE"
>> TODO remember previous modes
>> TODO include mode-switch timestamps
>> TODO perhaps combine/compose pomodoro features
i.e. pomodoros/breaks now include a mode
two potential modes: 'execute-current-task' vs 'pomodoro-break'
another: 'relaxed-sunday' vibes
> TODO prompt for a mode when returning to the machine
maybe just a notification reminding us
every five minutes: (str "CURRENT MODE: " (or mode "[WARN] no mode set"))
> TODO clawe add tag-crud to the focus widget
definitely want tag-crud, for the daily file _and_ per headline
aoc
> DONE pull and run advent-of-godot code
>> proof that this is complete
the unit test
A screenshot of the unit tests I wrote last night/this morning
captured: 2022-12-04 14:52
AOC Day 1 implementation
A screenshot of the CalorieCounting.gd script
captured: 2022-12-04 14:51
screenshot of `bb tests` output
All the GUT tests are passing!
captured: 2022-12-04 14:51
> TODO godot day 2
> TODO godot day 3
> TODO godot day 4
org-blog
> TODO clawe-based expo/publish page/widget
> TODO ->hiccup namespace needs definitive component for link protocol branches
example link: max-sixty/aot-gpt
> TODO clawe component showing current blog diff
and asking if it can be published
this is where recently edited, linked-to, unpublished notes get collected and emphasized
with fast-buttons
could also collect un-tagged headlines to ask for more tags
yodo
> TODO full yodo project review
a blog post detailing comment, theories, components, etc
what does this rotting tree trunk have to offer the community?
reminds me of: tending the mind garden
> TODO find that old yodo project file
looking for content about 'modes'
just discovered the garden's ~/todo/websites/* dir
a bunch of bookmarks from 2020, preserved forever with ugly timestampy filenames
(that used to be the org-roam default)
created when i had an org-protocol browser extension in place
it replaced my pocket flow
i ought to restore that, I bet I could really establish it now
could even pop-up a journal + paired clawe widget when capturing
capturing as a mode
My old yodo and projects notes were big on modes - it was a feature i never quite got around to.
Now I find those notes pretty unapproachable
stream format idea: _silent_ streaming - BYO Audio
This might be a better pace for coding along with someone
it puts the owness on the streamer to make the content and context visual
and allows for adding an audio track later
Tho I suppose I can already do that
why doesn't my `journal` workspace support a smarter layout
workspace-layouts might be an interesting clawe concept
it's really providing dimensions/markup to clawe-toggle targets
starting to feel close to emacs's purpose-mode or whatever that intent + buffer
coupling framework was
side note: how to just write footnotes?
I want to interject a foldable, then move on from it afterwards
the way i used to do in my journals. it's like i'm scared of writing a new file
i guess what i want is self-referencing notes - edges within files
clawe idea: workspaces as a 'layer'
see multiple workspaces at once, but keep them to their own max dimensions
i.e. calling the journal toggles in the entire journal layer
i.e. streaming means we always show our widgets layer
modes should probably be composable
max-sixty/aoc-gpt
teknql slack reference: https://teknql.slack.com/archives/C01FNGKKRA9/p1670175935552729
max-sixty/aoc-gpt
gpt scaring me a bit lately
review is basically tending the mind garden
reminds me of: tending the mind garden
so is writing!
vaguely related: writing is reporting
clawe or org-blog for publishing is about managing pipelines
what is the state of this piece of data in the system
what modes/pomodoros remain to jump into it
clawe publishing should make it easy to share updates
i.e. what's the visual for the quick hand-written blurb
maybe the backend should sync with the frontend
localstorage as a datascript layer
db listeners for pushing/syncing with the backend
might be nice with a frotend local storage
where's my git-status health check?
maybe add this to the clawe focus widget