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.

Sign up for GitHub

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

Jump to bottom

Support for multiple .literate document projects #7

Open
jesterKing opened this issue Dec 7, 2021 · 1 comment
Open

Support for multiple .literate document projects #7

jesterKing opened this issue Dec 7, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@jesterKing
Copy link
Owner

Design and implement a good mechanism to support multiple .literate document projects.

Whilst this is with multiple .literate document projects in mind the feature should work equally well for single .literate document projects.

  • TOC
    • TOC per book
    • TOC per chapter
  • Cross-referencing
  • Inlining of code for fragments in generated .html
@jesterKing jesterKing added the enhancement New feature or request label Dec 7, 2021
@jesterKing
Copy link
Owner Author

Since v0.2.1 the extension manages multi-root workspaces better. This doesn't mean multiple literate projects with cross-referencing, but rather that projects in different folders can be added to the same workspace without these interfering with each other.

Still, good cross-referencing between projects would be an interesting excercise.

jesterKing added a commit that referenced this issue Jan 7, 2022
@jesterKing
* Overhauling literate file processing. There is now one class respon…
a4e3af1 
…sible for

  handling the parsing and rendering of literate files and for creation of
  fragment maps. Different parts use the new central fragment repository. This
  has been done with future enhancements in mind.
* Literate program split up into several documents. TOC, chapter linking and
  similar features have become important, but for now accept that browsing the
  literate program isn't the easiest. Something to be address better through #7,
  #10 and #11.
* Diagnostics don't repeat unnecessarily.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jesterKing