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