Conversation
|
Just had a quick compile and it looks promising. Won't have time to look into it any deeper until the 5.1 catalina release is finished though. So If you'd like to sketch out some behavior spec here, in #1 or in the branch in a markdown file that would be appreciated so the direction can be guided. Generally speaking I like the approach to have a separate Workspace window (although in full screen mode that should also move around and be available somehow). I'd also like the documents to be tied to the workspace somehow if they are in a subpath. If there is some persistent part to our workspace, then storage of this one also needs to be discussed/defined. Currently I'm very fond of the |
…into feature/1-project-context
e69a203 to
c7ed1b3
Compare
fd785db to
95368c4
Compare
|
@monkeydom i included a file describing the behaviour and design to the branch: https://github.com/fourplusone/SubEthaEdit/blob/feature/1-project-context/Documentation/ProjectContext.md |
|
I'd like to discuss making the project context scriptable by Modes. I found this pr and corresponding issue by looking for some SEE ConTeXt modes, and this project is an idea that sounds pretty nice in conjunction with the ConTeXt project structure: One or more project files (ConTeXt content beginning with So: I'd like that approach to be scriptable by any module since there may be a project structure that already exists and should be hooked into the project context. |
Specification & Documentation
Here's my current Work in Progress on #1 (Project Context). This PR is meant to eventually provide an MVP for Project Context and serve as a basis to discuss the architecture. Feedback is very welcome