notesutils VS frame

I should write this stuff up, but I haven't.

I do have some brief notes on the "Notes.app" format here:

https://github.com/dunhamsteve/notesutils/blob/master/notes....

But I didn't discuss my methodology -- Generic decoding of protobuf, building up a schema as you go -- the tricky part there is that a byte array and a substructure look the same, so you have to try to decode it, and if successful, try that schema on the next example.

Here is another fun technique - scanning through a disassembly of an Apple framework looking for assembly patterns that match the protobuf compiler output (this was dependent on which language was targeted by protobuf):

https://gist.github.com/dunhamsteve/224e26a7f56689c33cea4f0f...

So you find the serializer / deserializer code and figure out what the original protbuf spec looked like.

> Hey, I've realized the same thing (that my workflows are stack-based) awhile ago, but didn't get to the point of writing a tool yet. Dare to share?

Sure, but because I'm only using it for myself, you're going to have to compile it yourself if you want (for now, anyway).

Originally designed to be CLI app, I find I only use the GUI these days (also in the repo).

Start here in case this is not for you: https://github.com/lelanthran/frame/blob/master/docs/FrameIn...

> Also, which approach you use to efficiently store and re-store relevant context information? I often find that intricate but important details are lost during context switch.

Everything is stored in a hierarchical DB, AKA the filesystem :-)

Each 'frame' is a directory with a specific set of files, and the directory name serves as the name of the frame. At any given time, a metainfo file in the root points to the currently active frame.

I think he might mean:

1. Push items onto a stack.

2. Create new stacks (words) for categories of items.

FWIW, I do the same, and use a tool (now using almost exclusively the GUI tool I include in the github repo) to do it.

This is the explanation of the tree-of-stacks method that I am using: https://github.com/lelanthran/frame/blob/master/docs/FrameIn...

(yes yes, it's a slideshow, but until I can make a video, this is a better medium for visualising how it works).

Always on top is a good idea, my to-do app (we all wrote one at some point) is designed to be integrated into the PS1 variable so it's always on top.

Shameless plug https://github.com/lelanthran/frame/blob/master/docs/FrameIn...

I did the same - a tree of tasks:

https://github.com/lelanthran/frame/blob/release/v0.1.4/docs...

I made it integrate with my PS1 variable so that it's useful from the terminal; my terminal prompt includes the current task, the same way it includes the git branch.

(There's a GUI I'm working on too, at the moment).

I made a tool to help me do exactly this! I even made a HN post about it, after making some HN comments about how well it is working for me.

(It's https://github.com/lelanthran/frame/blob/master/docs/FrameIn... in case anyone is interested).