Comments (1)
Unless you do a bespoke UI, it would be hard to have "one setting pane to rule them all", and the user getting any kind of support. on jupyterlab-lsp
, we went with each feature getting its own settings schema, and even there, given the composite nature of many of the, it's very limiting. this has lead other tools (e.g. vscode) to adopt crazy-pants notation like "some.deep.path": ["value"]
which make any sort of external assessment of it (e.g. JSON pointer) of these structures all but impossible.
anyhow: i think it's entirely reasonable, given that each plugin is in fact a full jupyterlab plugin, for them to have their own settings, and be able to handle them however the heck they want. the settings need to actually be fetched with an individual REST call, so it could be, much like with jupyter-widgets, that the the register
pattern should accept a Promise<MarkupExtension>
(or whatever the heck we built).
But again... much like with extensible markup (that doesn't have a dedicated way to self-document even what plugins are in use) in the first place, if the configuration of tiny pieces of markup is entirely controlled by the user, the chances of it reproducing close to faithfully anywhere other than where it was written else start going down pretty fast.
from jupyterlab-markup.
Related Issues (20)
- Binder url not working HOT 2
- Sync scrolling in markdown preview? HOT 4
- Add `[[wiki]]` style link support HOT 1
- Synchronise checkboxes with source
- Separate existing plugins into sub-packages HOT 4
- How do you add plugins? HOT 5
- Feat: support settings reloading
- Support for PlantUML HOT 1
- Broken yaml code block syntax highlighting HOT 2
- Import error during development install HOT 1
- Accessing notebook cell metadata via a BUILTIN plugin HOT 7
- svgbob Code Fence Label inconsistent with sphinx-contrib/svgbob HOT 5
- Support new `IMarkdownParser` interface
- Update to markdown-it 13.x
- Add docs/demo with ReadTheDocs HOT 3
- Document-level rendering? HOT 2
- Explain why I would want this extension
- Support for pythonic preprocessing HOT 1
- Update mermaidjs to support Class diagram HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jupyterlab-markup.