[seletskiy]

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?

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.

[lelanthran]

> 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.