In the video he describes the usecase that a user can "flip" between Markdown notes and Excalidraw notes in the same file and use both. This is achieved by writing a normal markdown note and then adding the excalidraw-plugin: parsed property.
By adding what I'll be refering to as the "Excalidraw-Data" section (basically JSON) you can can convert the file with the command "Toggle between Excalidraw and Markdown mode" between Markdown and Excalidraw.
The Problem
The issue arises in Live Preview Mode when one wants to write in Markdown and draw in Excalidraw while also having a clutter-free markdown experience: Yes you have the ability to add comments (%%) before and after the "Excalidraw-Data" section to hide it in Reading Mode but this doesn't hide the section in Live Preview Mode at all.
In Live Preview Mode the section expands more and more when you add new items to the visual Excalidraw note. This is annoying because lets say I have text stored at the bottom of a markdown file that I need to edit. It would take a lot of time for me to scroll all the way down just to edit some text. You also aren't able to see what text is below the "Excalidraw-Data" section and would have to switch to Reading Mode first.
Possible Solution
Add the option to use an obsidian callout box specifically for use with the Excalidraw-Plugin. The callout can be named with a title like "excalidraw-plugin" or "excalidraw-parse". The contents of the callout should embed the whole "Excalidraw-Data" section and should only be parsed by the plugin.
This would give the user the ability to "stash away" the content of the Excalidraw section in the callout and would keep the note clutter-free in Live Preview Mode (see picture).
Example Callout
>[!excalidraw-parse]-
> # Excalidraw Data
> ## Text Elements
> ## Drawing
> ```json
>....
>```
The Visual difference
On the left: Markdown note with normal Excalidraw section
On the right: Markdown note with Excalidraw section stashed away in callout box
Context
My Issue is referencing the problem that came up in one of Zsolt's videos: Start using the flipside of your markdown notes.
In the video he describes the usecase that a user can "flip" between Markdown notes and Excalidraw notes in the same file and use both. This is achieved by writing a normal markdown note and then adding the
excalidraw-plugin: parsedproperty.By adding what I'll be refering to as the "Excalidraw-Data" section (basically JSON) you can can convert the file with the command "Toggle between Excalidraw and Markdown mode" between Markdown and Excalidraw.
The Problem
The issue arises in
Live Preview Modewhen one wants to write in Markdown and draw in Excalidraw while also having a clutter-free markdown experience: Yes you have the ability to add comments (%%) before and after the "Excalidraw-Data" section to hide it inReading Modebut this doesn't hide the section inLive Preview Modeat all.In
Live Preview Modethe section expands more and more when you add new items to the visual Excalidraw note. This is annoying because lets say I have text stored at the bottom of a markdown file that I need to edit. It would take a lot of time for me to scroll all the way down just to edit some text. You also aren't able to see what text is below the "Excalidraw-Data" section and would have to switch toReading Modefirst.Possible Solution
Add the option to use an obsidian callout box specifically for use with the Excalidraw-Plugin. The callout can be named with a title like "excalidraw-plugin" or "excalidraw-parse". The contents of the callout should embed the whole "Excalidraw-Data" section and should only be parsed by the plugin.
This would give the user the ability to "stash away" the content of the Excalidraw section in the callout and would keep the note clutter-free in Live Preview Mode (see picture).
Example Callout
>[!excalidraw-parse]- > # Excalidraw Data > ## Text Elements > ## Drawing > ```json >.... >```
The Visual difference