#fructure 搜尋結果
#fructure is now 20% closer to the fluid editing experience I originally envisaged! If you want, you can just type more-or-less normally for entry purposes. Check out the character history displayed above: parentheses are often unnecessary, some significant gotchas.
still not the fluid editing experience i envisaged but coming along. as of the next bit of work i'm doing, entry should be (optionally) indistinguishable from standard text entry. the fact that this is happening should probably be a hint, but i am thus far evading it #fructure
For our program synthesis class w/ @xwangsd, @disconcision @dedbox and I built a #fructure-like interface for Smyth in Hazel. Here it is in action synthesizing add on inductive nats. h/t @jplubin for helpful discussions.
Don't know what possessed me but I actually wrote a semantically correct program in #fructure tonight instead of my usual gibberish. Above is the sequence of keystrokes which evoked it.
putting in my monthly attempt to fix a long-standing bug with curved backdrop rendering in #fructure. i... did not follow good practices writing this routine, which makes it extremely awkward but sometimes spectacular to debug
フリップ卿が三角の薄いべっ甲ピック使ってたって聞いて、どの厚さが #Fructure 弾きやすいかトライしてみる。結果どのピックでもちゃんとは弾けない。。😭😭😭 #KingCrimsonが好き #ギターピック #プログレ好き
here fructure-editor.tumblr.com/archive you can see a chronology from my first abortive attempts in summer 2017 (purple era), to the mockups i did this summer (white era), to the current version i've been working on since the fall (grey->cyan era) #fructure
フリップ卿が三角の薄いべっ甲ピック使ってたって聞いて、どの厚さが #Fructure 弾きやすいかトライしてみる。結果どのピックでもちゃんとは弾けない。。😭😭😭 #KingCrimsonが好き #ギターピック #プログレ好き
For our program synthesis class w/ @xwangsd, @disconcision @dedbox and I built a #fructure-like interface for Smyth in Hazel. Here it is in action synthesizing add on inductive nats. h/t @jplubin for helpful discussions.
Offo 🤔 @idevadhikari who advised U to take bloody Rest? Actually, not needed ♿ Jus Njoy D (3sum ) #Fructure 🙄🙄 as U toh d Realistic👊Wrestler..
And the after-effects of #Golondaaj 1st schedules continues.....🤔 instagram.com/p/B9DzqQHHe_8/…
My RacketCon 2019 talk on #fructure. This is the same as last week's link except it's been pried free from the rich vein of the livestream and pinned, twitching, to museum bristol board - much like a mixed metaphor on a strained simile: youtube.com/watch?v=CnbVCN…
youtube.com
YouTube
(ninth RacketCon): Andrew Blinn – Fructure: A Structured Editing...
there are a few examples here. maybe the most directly relevant is isomorf: isomorf.io/#!/syntax-pick…; the projective side seems solid but entry isn't there yet. this is something i'm working towards with #fructure though it's current pretty far back on the roadmap
My #racketcon talk on structured editing with #fructure! Starts around 7:07 if the offset link doesn't work: youtu.be/xSjk2PdQm5k?t=…
youtube.com
YouTube
RacketCon 2019
#fructure is now 20% closer to the fluid editing experience I originally envisaged! If you want, you can just type more-or-less normally for entry purposes. Check out the character history displayed above: parentheses are often unnecessary, some significant gotchas.
putting in my monthly attempt to fix a long-standing bug with curved backdrop rendering in #fructure. i... did not follow good practices writing this routine, which makes it extremely awkward but sometimes spectacular to debug
Don't know what possessed me but I actually wrote a semantically correct program in #fructure tonight instead of my usual gibberish. Above is the sequence of keystrokes which evoked it.
Again, we run straight-on into interop :(. Dr. Racket supports inline vector images; I was using them to document #fructure layout functions - as well as inline in tests! - but I stopped as the format was making diffs useless.
フリップ卿が三角の薄いべっ甲ピック使ってたって聞いて、どの厚さが #Fructure 弾きやすいかトライしてみる。結果どのピックでもちゃんとは弾けない。。😭😭😭 #KingCrimsonが好き #ギターピック #プログレ好き
basic editing is starting to look okay. getting a good dr. racket <-> photoshop iterative flow down for style tweaking. #fructure
Don't know what possessed me but I actually wrote a semantically correct program in #fructure tonight instead of my usual gibberish. Above is the sequence of keystrokes which evoked it.
#fructure is now 20% closer to the fluid editing experience I originally envisaged! If you want, you can just type more-or-less normally for entry purposes. Check out the character history displayed above: parentheses are often unnecessary, some significant gotchas.
putting in my monthly attempt to fix a long-standing bug with curved backdrop rendering in #fructure. i... did not follow good practices writing this routine, which makes it extremely awkward but sometimes spectacular to debug
still not the fluid editing experience i envisaged but coming along. as of the next bit of work i'm doing, entry should be (optionally) indistinguishable from standard text entry. the fact that this is happening should probably be a hint, but i am thus far evading it #fructure
Something went wrong.
Something went wrong.
United States Trends
- 1. Eagles 173K posts
- 2. Goff 18.9K posts
- 3. Lions 80.7K posts
- 4. Dan Campbell 9,517 posts
- 5. Jalen 32.5K posts
- 6. Chiefs 92.9K posts
- 7. Gibbs 7,496 posts
- 8. Nakobe Dean 2,108 posts
- 9. #ITWelcomeToDerry 8,480 posts
- 10. Kevin Patullo 5,851 posts
- 11. Collinsworth 2,878 posts
- 12. #OnePride 5,185 posts
- 13. GM CT 20.7K posts
- 14. Vic Fangio 3,082 posts
- 15. AJ Brown 8,030 posts
- 16. Shedeur 56.4K posts
- 17. #BaddiesUSA 11.2K posts
- 18. Jamo 4,735 posts
- 19. Gabriel 66.2K posts
- 20. House Republicans 27.3K posts