EtherCalc VS slate

Somewhat random, but spreadsheets continued to evolve after VisiCalc (obviously).

Here is one by the inventor of VisiCalc, Dan Bricklin, on github: https://github.com/DanBricklin/socialcalc

Audrey Tang (who happens to currently serve as the Minister of Digital Affairs of the Republic of China (Taiwan)) created the Node.js port of SocialCalc, EtherCalc: https://github.com/audreyt/ethercalc

Audrey made a fascinating write up of SocialCalc for The Architecture of Open Source Applications https://aosabook.org/en/v1/socialcalc.html

if you need office stuff ON CLOUD then no idea there are several random ones like https://github.com/audreyt/ethercalc (demo on top right the website works fine and is multi-user collab) and there are libreoffice ones that work in cloud too, though using them in browser never really made sense to anything I've seen. I've never been to any office or consulted anywhere that multi-user actually helped anyone.

I think there's several possible solutions: * No-code/low-code database platforms (e.g., NocoDB) * Personal finance manager (e.g., Firefly III) * Spreadsheets (e.g., CryptPad for a full office suite or Ethercalc) * Task management systems (e.g., Vikunja)

Office solutions (e.g., spreadsheets): CryptPad and EtherCalc

ethercalc: supports editing by multiple clients simultaneously. Pretty easy to setup.

Try CryptPad or EtherCalc.

Ethercalc, although a bit dated, works ok on docker https://github.com/audreyt/ethercalc

- it creates a layout based on rows and cells, so it support multi-column layout - each cell can contain a different "cell-plugin", - richt-text editor based on https://github.com/ianstormtaylor/slate is built in and comes with its own plugin system. It can do weight, italic, block-types, alignment and lists and can be extended as you want (even with elements storing data and interactive components) - you can create custom cell plugins based on a schema (or custom control ui) and a component that should be rendered - it stores an object tree that represent it, not html. It therefore can contain any react component, which is great if you want to allow your editors to add interactive components or components that you already built as part of the app - i carefully optimized for SSR and bundle size, so no editor ui is rendered nor loaded. editor ui is only loaded on the client if you disable readOnly. (lazy loading) - it mainly tested with nextjs, since i used it for content-heavy pages. - its not yet tested with react-server components, but it should actually work in read-only mode

Finally there's Slate and Lexical which are super powerful in terms of customizability and extensibility. They're great options for when the editing experience plays a major role in the product.

Slate, as per its documentation, is a completely customizable framework for building rich text editors. Therefore, it doesn't offer a feature-rich text editor but instead provides tools to build one. Let's create a component called Slate and see what the Slate editor looks like.

Link to Repo

Word of warning about Slate: I love the API and the design goals, but it appears to suffer from some fundamental issues. We were experiencing issues similar to this one and a team of multiple 10+ year experienced frontend devs couildn't figure out what was going on. I had to completely rip out a feature we had built with Slate and had to reimplement a new version from scratch with Lexical. So far we have no issues other than those inherent to rich text editing.

We're trying to choose between Lexical and Slate at work. Do you have any examples that would be similar to this? https://github.com/ianstormtaylor/slate/blob/main/site/examp...

If you are going to customise a ton of functionalities and/or implement new functionality I suggest using SlateJS. If not, have a look at Sun editor.

You definitely need to give Slate (https://github.com/ianstormtaylor/slate) a try - the best editor framework I've used.

Slate: Looks very promising, but it's for React. (Someone has floated the idea of making it framework-agnostic, but the maintainers haven't committed to that goal yet.)