frames

new: hop tags, tag a line in your frames.sh script for easy reference when using switch/hop. i use switch/hop instead of if conditions - less clutter, no nesting required. switch - if there's a condition that needs to be met for a hop to occur, hop - quickly hop to line of code.

to provide context: when building frames with frames.sh, instead of deploying your own server written in js/ts, your frame logic is  accommodated and taken care of within the platform by the use of a script i called flex. this script is then used on runtime to perform functionalities for your frame. your script is deployed by pressing "publish" in the frame editor.
https://docs.frames.sh/flex-code/keywords-and-methods

how do you feel about building your frames/actions logic like this? this is a compact script for a simple 4-pager tx frame. compact because instead of using the no-code components im using code instead (quicker for me). the goal is to keep the syntax good enough to make things workable and not too complex the user might as well build the logic in native lang.

how do you feel about building your frames/actions logic like this? this is a compact script for a simple 4-pager tx frame. compact because instead of using the no-code components im using code instead (quicker for me). the goal is to keep the syntax good enough to make things workable and not too complex the user might as well build the logic in native lang. 

https://warpcast.com/king/0xb1e77fca

Looks really cool. I wonder how do you pass context / output between the nodes?

Engineering @neynar. Amusement, wonder, and uncertainty ✴︎ libred.org

the diagram is only visual representation of the entire script for easy organization but really it's one whole script combined/parsed.

Ah, make sense. I thought the graph is serialized and then executed with a some op-based state machine

yea it's serialized on publishing then sent to the back with the state machine 🙂

i suppose there's 2 different parts to the editor: the template editor and the logic editor, the template simply modifies the frame front and the logic then lives on the platform's backend ready to take requests.

frame.town

Very interested to see how it feels to navigate both graph-based and code-based editors at the same time. I implemented a PoC for extended version of /frametown and it was quite a challenge to use. Context-switching tax was high for my brain.

Your implementation looks much more integrated than mine. Pretty sure it works better!