Jeremy Vuillermet 2023-04-11 21:17:01
Hi everyone, here is a recording of a data-first design tool I demoed during last future of code meetup. twitter.com/jvuillermet/status/1645862317597380616
Next, I would like to explore how to improve the formula input/editor. I think there is an opportunity for more structured editing while adding playfulness and intermediate value preview. I like those 2 directions so far:
Any other idea or reference in that space?
Jeremy Vuillermet 2023-04-12 17:37:02
yes Gneiss is really nice and inspired me to have the full json and data browser on the left. In my opinion, the missing part of Gneiss is that the components are the end of the road. In my prototype or something like retool, the visual components also expose their data so we can keep building on top. An interesting and unexpected reinforcing loop
I didn’t know about project Lincoln, that’s amazing! thanks a lot. I need to spend more time on the video to better understand how it works
Jeremy Vuillermet 2023-04-13 17:25:24
perfect, thanks! that’s some material to study 😛 Anything in the structured editing like the 2 last links of the post that come to mind?
Something better than just text to edit formulas
nicolas decoster 2023-04-16 17:10:48
Very interesting demo! I like the discoverabilty, the contraints between visual elements, the way you map arrays on visuals, etc.
nicolas decoster 2023-04-16 17:14:32
The formula editing is also already nice at this stage. But, yes, maybe a more playful way to do it would be nice.
But, I'm not sure that adacraft-like (i.e. block programming) would fit? Or maybe a concatenation of blocks that transform the data (or nodes'n wires)? With displaying of intermediate results?
nicolas decoster 2023-04-16 17:22:47
Here is an example of what I've done on a similar use case (widget from a weather API) with a nodes'n wires tool prototype I've done long long time ago. The relevant aspect in it for your use case would be the fact that data flows through "simple" transformation blocks.