Keep the good work!
edit - some remarks to "get there": it must be/feel fast like native Excel, Sublime Text or at least VS code. In another phase, to be a real "programming editor" it would be great if you could use any programming language you want, not just JS. Clojurescript or Elm/Purescript could be a good start.
edit2 > ways to compress more functionality into the 'boilerplate' included with each sheet. I think the boilerplate should be somehow hidden from the end user.
As someone who is working on an Excel compiler, I can tell you it's challenging to make it very fast.
The sheets I'm working with have around a million expressions, and there are large sparse regions, so the data structures have to be a bit compact.
I would like to do a write-up about it at some point though, if for no other reason but to show the Open Document or LibreOffice people what could be improved about the formats.
Not every programming language is suitable but ClojureScript would probably work (no plans to support it right now though, gotta finish this one first!).
Considering hiding the boilerplate in the text pane.
Aside from the SQL support you mentioned wanting to add, and the various todo-items, are you planning on going beyond the spreadsheet concept? For example with some type of node-based interface, like Unreal Engine 4 Blueprints [1], or like the materials editor in Blender [2]? I realize that might be a vague question, heh.
[1]: https://docs.unrealengine.com/en-US/Engine/Blueprints/index....
[2]: https://docs.blender.org/manual/en/latest/editors/shader_edi...
I'd like to stick to a grid for writing 'functional core' logic, but there's potential to use a node interface at the surface of the 'imperative shell', to link up sheets or data feeds (push/pull). I was really impressed by Nodes [2] and I need to spend some time digging into Node-RED [3].
Furthermore, maybe the data could be in CSV at the top of the file, in an HTML comment, and the editor could be in HTML at the bottom of the file, in a CSV comment, so the file could be opened in either a browser or Excel? Haha
If you were thinking about WebSQL, then sticking to IE11 has skipped you over an obstacle course in web standards, because WebSQL was abandoned by the browsers (for good reasons, led by Mozilla and Microsoft trying not to let SQLite bugs define the web platform for decades) and won't be supported again soon, in lieu of the much simpler key-value store called IndexedDB.
> JavaScript's lack of a built-in parser is a real bummer
eval() wasn't sufficient for your needs?
Mesh is still very much an alpha. Since the last public commit I have been experimenting with:
- different text representations of the sheet (to make diffs as readable as possible)
- ways to compress more functionality into the 'boilerplate' included with each sheet.
On the to-do list are:
- persistence (including fixing "save sheet as URL" and local load/save)
- selecting input cells with a keyboard while editing a formula
- a way to include 'standard' spreadsheet formulas such as 'SUM' on-demand in the sheet file
- case-insensitive cell references
- much more polish...
JavaScript's lack of a built-in parser is a real bummer, and it means that while Mesh's backend logic can be written as a spreadsheet, in Mesh [1], the file has to include a third-party JS parser, which significantly slows down the editing process. I'd also like a proper SQL and first-class table support, but we work with what is supported by Internet Explorer 11.
I remain confident that we can substantially improve the status quo of spreadsheets and, by extension, programming.
[1] https://twitter.com/MeshSpreadsheet/status/10195553103635046...