Try to have custom renderer with myst. #314
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Let me know if you would like to have a quick meeting next week on this? I will try to take a quick look through in the next week and give some tips. |
|
Sure I would be happy to meet, let me shoot you an email to coordinate. |
|
scipy.signal._filter_design:zpk2sos seem to contain raw directives: |
|
|
Carreau
force-pushed
the
myst
branch
2 times, most recently
from
4fb45aa to
11d8921
Compare
this will make it much more easier to make a jupyterLab extension as once we have a JS renderer, we can "just" make a JupyterLab extension that use the same components. I dont' know much about how to do that, but here is an attempt that try to do it: - it add the the "frontend" folder, if you run `npm install` (once) and then `npm run build` from within it, it will generate the a `index.<hash>.js` file in `papyri/app/js/...`. As I don't know how to not have it have a `hash`, this adds new handlers that try to guess the name of the file and serve it. This let you in a template to call `render(dom-id, json)`, and ti wil use myst to render that on the given node. The idea is to give myst the root node, but that does not work so far as some of our nodes are not the same. we can go two routes (or a mix of both): - write custom rendered for myst, - massage our nodes to look like what myst is expecting.
|
Ok, let's get that in, it's starting to be unwildy after a month of work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One thing I'd like to do is do the full rendering with myst.js,
this will make it much more easier to make a jupyterLab extension as once we have a JS renderer, we can "just" make a JupyterLab extension that use the same components.
I dont' know much about how to do that, but here is an attempt that try to do it:
npm install(once) and thennpm run buildfrom within it, it will generate the aindex.<hash>.jsfile inpapyri/app/js/....As I don't know how to not have it have a
hash, this adds new handlers that try to guess the name of the file and serve it.This let you in a template to call
render(dom-id, json), and ti wil use myst to render that on the given node.The idea is to give myst the root node, but that does not work so far as some of our nodes are not the same.
we can go two routes (or a mix of both):