use-case :
When using logseq in a “single user mode” I would use “graphics” ( in general ) only when absolutely necessary. However there are times when a flow chart or other “white board”/“free flow diagrams” would be useful to organize and express relationships between things.
most wanted features :
Regardless of how a whiteboard is implemented in logseq ( maybe using mermaid - Markdownish syntax for generating flowcharts, sequence diagrams, class diagrams, gantt charts and git graphs. and or other such approaches?) I would hope that the logseq query functions would be able to find all text and maybe follow relationships ( arrows / links ) between those text “blobs” too. I think the challenge of supporting traversal of cyclic graph traversal would be a very challenging task to solve.
Maybe a good starting point would be some kind of “canvas” in logseq to make building mermaid syntax via visual toolbar/buttons/drag-n-drop paradigms would be a low code functional solution to start with? I am thinking a new kind of “diagram/whiteboard” quote block that would bring up a toolbar to add new items and link them, etc… etc…
Then focus on getting the logseq query enhancements to be able to search those diagrams done after that.
experience with whiteboards:
Visio is by far the best general purpose tool. However, it is not very easy to use due to all of the flexibility and “clicky-clicky” (modes and “hit box”/“handles” that pop-up/hide ) learning curve.
I would suggest keeping the shape set small and straight forward with optional text blobs OR links to a block elsewhere in logseq. (Maybe even support a new kind of “Template” to extend the toolbar with local template blocks too.) Text blobs, Images would be useful too. But that may also lead to wanting to “draw on the images”. (aka: image editing ) I think Image editing is best left outside of logseq.
questions / random thoughts :
Maybe an HTML5 canvas would also be an implementation option. That could leave logseq able to query/search the contents too. Though it would likely be more work than starting with mermaid syntax too.