You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's feasible to still use Kaavio-showdown and have a WYSIWYG editor. Something like StackEdit (NPM repo). This editor converts everything to Markdown which is then passed through Kaavio-showdown.
This provides one obvious benefit easier editing. You can add buttons for zoomOn, toggleHighlight, hide, show etc.
It also provides one less obvious benefit - easy state tracking. As the author adds interactive links they should build up from each other. So, if the first link specifies toggleHighlight and the second link specifies zoomOn - clicking the second link only should both toggleHighlight and zoomOn. With a WYSIWYG editor, the author wouldn't have to worry about this. The editor could automatically pass in the tracked operations into the markdown.
The text was updated successfully, but these errors were encountered:
It's feasible to still use Kaavio-showdown and have a WYSIWYG editor. Something like StackEdit (NPM repo). This editor converts everything to Markdown which is then passed through Kaavio-showdown.
This provides one obvious benefit easier editing. You can add buttons for zoomOn, toggleHighlight, hide, show etc.
It also provides one less obvious benefit - easy state tracking. As the author adds interactive links they should build up from each other. So, if the first link specifies toggleHighlight and the second link specifies zoomOn - clicking the second link only should both toggleHighlight and zoomOn. With a WYSIWYG editor, the author wouldn't have to worry about this. The editor could automatically pass in the tracked operations into the markdown.
The text was updated successfully, but these errors were encountered: