Self-updating screenshots
interblah.net
Self-updating screenshots
1–10 of 80 posts
Re: Self-updating screenshots
#2Re: Self-updating screenshots
#3https://github.com/ericfortis/mockaton/tree/main/pixaton-tes...
Re: Self-updating screenshots
#4Re: Self-updating screenshots
#5Re: Self-updating screenshots
#6For the small casual games I've been vibe coding, I always start from a place where the application has a CLI where it can run headless, rendering to offscreen texture, with a a screenshot command as well as performance instrumentation. It takes no time to include all this, and gives the agent a way to automate the ui and inspect important things. It also lets me trivially have the agent update screenshots.
Not as neat as being part of the build process, but I will now add that.
Re: Self-updating screenshots
#7Re: Self-updating screenshots
#8Bonus: since you're generating screenshots programmatically anyway, you can generate a pair of each with your app's light/dark theme, and swap them in/out depending on prefers-color-scheme: dark. elements work in GitHub READMEs, too: https://github.com/CyberShadow/CyDo#readme
Re: Self-updating screenshots
#9Re: Self-updating screenshots
#10Worked well. Not quite the same as this, but that’s what this reminds me of.