Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Project Context #121

Open
wants to merge 16 commits into
base: develop
Choose a base branch
from

Conversation

fourplusone
Copy link
Collaborator

@fourplusone fourplusone commented Aug 27, 2019

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

@monkeydom
Copy link
Contributor

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 toml format for stuff like this, as it is very well defined, simple, human read and editable.

# Conflicts:
#	SubEthaEdit-Mac/Source/PlainTextDocument.h
#	SubEthaEdit-Mac/Source/PlainTextDocument.m
#	SubEthaEdit-Mac/Source/PlainTextWindowController.m
@fourplusone
Copy link
Collaborator Author

fourplusone commented Nov 12, 2019

@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

@marcofeltmann
Copy link

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 \project <>) should list all used products (ConTeXt content beginning with \startproduct) which themselves list chapters and so on…
So the language I want a mode for (guess I'll provide one by myself) provides a somewhat streamline project infrastructure and it would be perfect to get this reflected into project context even if only one underlying file is opened.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants