3 ms·
I just want a modern spreadsheet-like interface that isn't limited to the concept of sheets. A visually-represented functional language that lets a user with no
by airstrike 7y ago
I just want a modern spreadsheet-like interface that isn't limited to the concept of sheets. A visually-represented functional language that lets a user with no programming knowledge run a pipeline of data transformation and ultimately output the data in a management/client-ready format.
I want to build it myself, but I have neither the time nor the expertise.
- thanksforfish 7y agoWhat limitations are you looking to remove? 2d to multi-dimensional? Tables that float instead of living on sheets?
- airstrike 7y agoEDIT: I think users can only really easily operate with 2D data, but to borrow someone else's acronym, a ZUI with multiple layers / levels of data could be more ergonomic than a vanilla GUI, so in a way I am indeed arguing for 3D. And yes to floating tables. Probably allowing users to also reference other sheets/tables semantically rather than just by row-column. Also creating explicitly defined (visual) pipelines of how the data is being transformed so users can audit and understand complex "spreadsheets". Auditing deeply linked calculations by following text formulas is too cumbersome for most users.
- thewebcount 7y agoI've sat through a presentation done with a ZUI (Zoomable User Interface) and it was nauseating. I literally almost threw up due to the unexpected motion every few seconds.
- airstrike 7y agoI believe you, but I think there's a difference between watching someone work and working – if you control the motions, they're not unexpected after all
- RedNifre 7y agoDo you mean like Node-RED, or something different? https://nodered.org/ https://nodered.org/
- airstrike 7y agoI'd say that certainly has some of the elements I'm thinking of, but what I'm describing is a little more spreadsheet like
- tonyedgecombe 7y agoYears ago I worked with a project called FormScape that did that. The end result was usually a printed report or PDF but there is no reason it couldn't be some other data format. The whole thing was tree based, basically you were gluing together a bunch of domain specific objects. The result was something like a visual abstract syntax tree but not quite. There were general purpose nodes on the tree that handled conditions or arithmetic and specialised ones that mapped data. The people who grasped it well would have been equally happy writing code. Unfortunately it was often sold as a tool that didn't require programmers, that wasn't the case. If you don't have the ability to decompose your requirements to their constituent parts no tool is going to help. There was often debate about whether it was programming or not however it was certainly Turing complete. I managed to write a tiny basic interpreter in it. It was very productive in its narrow niche.