> I could go on and show a few more missed optimization opportunities in Chez Scheme I assume the Chez core devs are now aware of this post? Looks like there are a few low-hanging fruits

good evening folks. I’m doing a DrRacket color scheme here but I’m experiencing a lot of friction in updating the colors during development. Every time I change the values, I’m removing the package and then installing it again. Is there an easier way to develop colorschemes?

Something I can run in DrScheme once I change the values that makes it reload the package and update…

Or, a way to export the colorscheme from setting all the colors I want using the preferences GUI

Maybe using preferences:get ? I’ve not done this but retrieving preferences was mentioned in #drracket recently

thanks! I’ll check it out.

Is it possible to use racket/gui with big-bang/react-y approach?

By that, I mean callbacks would update states rather than the actual widget. Then, there’s a to-draw which constructs widgets from the states. The framework then re-render (efficiently) whenever states change.

What’s the benefit? Would this be the same as having a “state” object that queried the widgets for their values when it was asked for them?

frtime (https://docs.racket-lang.org/frtime/index.html\|docs)? I learned about something really cool… the demos rotation tile-game piston mirror-lens (!) involve basic controls. Not what you’re looking for I guess, but WOW to me.

Functional Reactive Programming is pretty neat :+1::skin-tone–2: