I’m wondering if it’s possible to do so. If that’s possible, I can make Bike my only markdown editor instead of having to use one for that sole purpose.
Code block is somewhat possible now. Use code rows. But there is no syntax highlighting. Maybe someday. That would fit within design, just requires programming work.
Embedding mermaid rendering, etc would not fit with design. In theory possible to implement, but in practice the editor would suffer, become slower and more complicated to use.
Instead I think the extension system can offer a similar function, with different tradeoffs. The extension system allows you to build/maintain HTLM views, built off outline data. The calendar in the inspector bar is one example, but there are many other possibilities.
The d3 example is an unpolished example of what I mean. You can find it in the example extensions repo. Here’s a quick screenshot.
This is a pretty strait forward example, just projecting the entire outline as a radial tree. And it’s a bit limiting because this is an early test extension, and it should really be using the panel API, so you can work on your outline in one window and have radial view update in another view.
You could have less direct mappings too. Such as rows and attributes to a table editor. Etc.
The important point is your outline stays clean outline. You can have complex views, but they live in own UI. The calendar in the inspector is another example of this idea.
2 Likes
What about markdown tables? I mean those multi-line elements should behave similarly right:
- in block mode: rendered view
- in text mode: editable raw text
Could you suggest a workaround to display rendered markdown tables linked to different rows in the editor?