Michael Aufreiter

That won't go into core as we want to support only semantic structures out of the box. However you can implement that with custom nodes/tools/commands.

I think the most natural solution would be to add a fake-text element (e.g. paragraph) before the IN (sth that exists only in the view not in the model). Then...

And if we just prevent that from ever happening. I mean if we disable insertion of isolated nodes as first element in a container?

I didn't like the custom cursor style we had before... somewhat unnatural. But if we managed to do it with a native blinking cursor I think it would be fine.

Understand. Mhh.. native cursor also not possible if we would be ok that it's rendered at a lower height (like a text cursor) at the top-left of the IN?

We may also want to use symbols for representing node types. E.g. ```js const { CDATA } = DOMElement.NodeTypes ```

I like the proposal. And the explicit abstraction of appState. Realizing we need this in many places, e.g. remembering which card was open in the metadata panel. As for the...

appState.observe looks good. Maybe put the params first, then the handler and context (this) ?

I'm one of the original developers behind eLife Lens (which is used as the article viewer in ScienceFair). Right now we are working on a set of tools related to...

Hi @csarven! I'd love to sync up. Maybe we can find a date/time in about 2-3 weeks? Some quick thoughts: If I understand correctly, you are building on top of...