Channels
administrivia
announcements
bot-dark-forest
devlog-together
in-alberta
in-boston
in-germany
in-israel
in-london
in-nyc
in-ontario
in-seattle
in-sf
in-socal
introduce-yourself
linking-together
of-ai
of-end-user-programming
of-functional-programming
of-graphics
of-logic-programming
of-music
present-company
random-encounters
reading-together
share-your-work
thinking-together
two-minute-week
wormholes
Title
a
alltom
07/31/2019, 5:09 AM@stevekrouse (or anyone more well read on this than me), I enjoyed https://futureofcoding.org/essays/dctp.html but I got tripped up on the part I snipped below. Is there any reason why you chose to sequence the buttons instead of expanding the domain of
buttonLike, if the buttons were presented on something like a graphic then it might be
clicks1 = button(rect1); clicks2 = button(rect2)clicks1, clicks2 = stacked((a, b) → (button(a), button(b)))💡 1
s
stevekrouse
07/31/2019, 5:59 AMThose solutions seem like a potentially better way to do it. I am copying the sequencing idea from two FRP lobraries for HTML: Reflex and Turbine.
So the main answer is that HTML is an ordered tree, that's why
a
alltom
08/01/2019, 12:39 AMThat makes sense. Thanks!