Reinhard Langner

I found the example here: https://codesandbox.io/s/github/jxnblk/mdx-deck/tree/master/examples/multiple referenced in the mdx-deck README.md / Usage Examples / Multiple Decks.

Yes, the ability to add additional features to the core application opens a lot of user-specific use-cases. The user should define with plugin(s) he/she want's to use. But what do...

> Yeah, I've wanted such API that I can plugin [excalidraw-animate](https://github.com/dai-shi/excalidraw-animate) and [excalidraw-claymate](https://github.com/dai-shi/excalidraw-claymate). What "kind" of API would you need for it ? May be starting with a real usecase...

 I've made some tries. The plugin is a react-app. It will be rendered in an iframe inside the excalidraw-app. Data is exchanged via message passing. plugin -> core: window.parent.postMessage(...)...

```` wrapper.find("form").simulate("submit"); ```` works fine. But it would be nicer if I could simply send a keyDown event to the input-element inside the form. ```` wrapper.find("input").simulate("keydown", { keyCode: 13, which:...

uh, that sounds awesome. Tools, that have the possibility to extend the features with plugins would grow to usages that are not expectable at the begining. starting with a simple...

using the react-testing-library (https://testing-library.com/) I get rid of that warning with: import Modal from "react-modal"; const { container } = render(); Modal.setAppElement(container); .... // to the testing, use Modal or,...

inline editing ? I would say: yes.

I think the aspect ratio should be stayed fixed.

That is a brilliant idea. Thank you. I just checked how notion.so works - it`s exactly how you described it.