Include implementation with tabs and imports

[MatthewCaseres]

I have an implementation that uses tabs and imports, https://www.actuarialopensource.org/book/welcome. I'm curious if it is possible to provide such an implementation directly in this package so that I'm not rolling my own implementation and maybe can benefit from the broader community that depends on this package.

[elilambnz]

Hi and thanks for your support! I've taken a look at your implementation of tabs. I agree that this would be a helpful addition, especially for those who have more complex examples to show off. In the meantime, do let me know if any small tweaks can be made to accomodate your current solution.

[MatthewCaseres]

My application appears to be running smoothly with no need for enhancements.

I do some stuff not mentioned in the docs though so please let me know if I am doing something bad.

I give editors uuid and track the uuid of the most recent editor (via React context) and only keep the worker alive for the most recently used editor. This should minimize the latency from lazy loading and terminating workers, while ensuring that at most one worker is loaded at a time.

[elilambnz]

@MatthewCaseres I just wanted to let you know that I haven't forgotten about your suggested improvements.

Keeping an idle worker alive is a great suggestion and something that I started a little bit of work toward in March. There is an feature branch in development that you can track here #213

In regards to showing usage of tabs, I've added an example of using multiple files here so I'll go ahead and close this issue. I believe that the UI implementation should be up to the developer, but looking at this example will be a good start for others.