3 ms·
I think it's intuitive and works, but tab and shift+tab in the shortcuts menu are about adding children and parents. So, adding instructions for it is enough :)
by vilkkala 4y ago
I think it's intuitive and works, but tab and shift+tab in the shortcuts menu are about adding children and parents. So, adding instructions for it is enough :)
I definitely would give the computation beta a try. My use case would be just "more visual Excel".
It's important that the nodes can also have non-formulae content, e.g.
salary["Salary<br/>`${1500}` €"]
Interested in seeing how you have implemented referencing the inputs.
Edit: You answered the last question with the video. Looks interesting, but having to add one extra node for the variable declaration feels cumbersome.
Edit 2: What if the outputs of the nodes could be named with text in the links?
- vilkkala 4y agoLike: one["Some value {100}"] two["Other value {200}"] computation["Sum is {first + second}"] one--first-->computation two--second-->computation
- escot 4y agoOk I enabled computation for a little while on prod, but you have to know this super secret keyboard shortcut to turn it on: Control-Option-E. I'll leave it on at least a few days, and if you want to try more I can put up a more permanent link to a build with it.
- escot 4y ago> having to add one extra node for the variable declaration feels cumbersome Well you don't always have to define a variable. For example `=sum()`in a node will just take all the parent values and sum them, whether they are variables or just pure values. But you're right that if you want to define a variable its takes two nodes (the expression as the parent, then the `var foo` as the child). I should probably support defining a variable completely inside a node like `var foo = 1 + 2`. I'm still a little hesitant to add any text on the arrows until I find a better way to do it via the keyboard. I find that just using the text in the nodes is usually sufficient anyways.