Live data from Hacker News

Self-updating screenshots

interblah.net

61–70 of 80 posts

Re: Self-updating screenshots

#61
post #56

Speaking of screenshots. Can we please agree that the OS should not send any event to applications while a screenshot is being made? It is very annoying if you press a screenshot button and suddenly menus disappear. Or much worse, the application sends a "screenshot taken" message back to the social media platform.

I also can't stand Android preventing me from taking a screenshot. It's on my screen, I have the right to take a screenshot.

I understand the technical limit of taking screenshots of DRM-protected content (e.g. Netflix), but why would my bank app be allowed to stop me from taking screenshots?

Re: Self-updating screenshots

#62
post #61
post #56

Speaking of screenshots. Can we please agree that the OS should not send any event to applications while a screenshot is being made? It is very annoying if you press a screenshot button and suddenly menus disappear. Or much worse, the application sends a "screenshot taken" message back to the social media platform.

I also can't stand Android preventing me from taking a screenshot. It's on my screen, I have the right to take a screenshot. I understand the technical limit of taking screenshots of DRM-protected content (e.g. Netflix), but why would my bank app be allowed to stop me from taking screenshots?

Solution: don't use mobile bank apps.

Re: Self-updating screenshots

#63
post #54
post #48

Earlier quoted context omitted.

Of course it is, he managed to avoid this pitfall, I "press F to pay respect"

"F" usually means somebody did something wrong and you are paying respect to their memory. You don't say it as a form of congratulations.

> did something wrong

Nah it's for those who sacrificed their own life, those who succumbed to the call of duty (or to the imperium of perfection) and put their teammates first.

Re: Self-updating screenshots

#65
post #26

Very cool. For 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…

> It takes no time to include all this In some cases it does. Which engine?

I don't use an engine for vibing, they tend to be built around managing content and using their editors. You can drive engines from code but they are more built for invoking code from content usually. So I just use frameworks like SDL, Raylib C# and ebitengine. Most stuff I've done recently was ebitengine because I felt golang was the best thing to have LLMs writing when I started them.

Right now I have my own framework which has a host written in Rust but game code is written in AssemblyScript - too early to tell how well this will work out but it is very promising to me right now.

If I were just getting started I would probably pick some framework in Rust, or maybe Bevy which I believe is considered an engine but is code-centered.

Re: Self-updating screenshots

#66
Very nice. I did something in a similar spirit eons ago for capturing CLI tool output directly into my docbook-based documentation. In my case it was also part of a build, generating intermediate .xml prior to running the docbook build.

Ancient historical reference: https://martiansoftware.com/lab/rundoc

Re: Self-updating screenshots

#67
post #61
post #56

Speaking of screenshots. Can we please agree that the OS should not send any event to applications while a screenshot is being made? It is very annoying if you press a screenshot button and suddenly menus disappear. Or much worse, the application sends a "screenshot taken" message back to the social media platform.

I also can't stand Android preventing me from taking a screenshot. It's on my screen, I have the right to take a screenshot. I understand the technical limit of taking screenshots of DRM-protected content (e.g. Netflix), but why would my bank app be allowed to stop me from taking screenshots?

Ask them?

Re: Self-updating screenshots

#68
This reminds me of an small app I wrote and didn't do anything with-- You would choose an API / endpoint to grab data from, then choose how to display that text on a prebuilt or custom uploaded picture. On the ping it would rebuild the image and put the updated text from the api on it so you could have images with more current information (every 5/10/30 mins, etc.) Updating readmes with new screenshots on push is probably a much less cpu and better way to do dynamic image generation, for this use case.

I never ended up using the idea the way I wanted, but this makes me think there's potential in this dynamic image domain yet!

Re: Self-updating screenshots

#69
post #16

Very cool. For 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…

Would you mind sharing a link to some of these casual games? I ask cuz I'm also interested in how vibe coding can make game development easier. We had such a vibrant indie game scene when Adobe flash was about and since then nothing's really touched that level of ease of development. I think vibe coding is the first tool that actually exceeds it.

Unfortunately I can't right now, I'm going to release a few things simultaneously but they aren't public yet. They will eventually show up on https://kellydornhaus.com

Re: Self-updating screenshots

#70
post #61

Earlier quoted context omitted.

I also can't stand Android preventing me from taking a screenshot. It's on my screen, I have the right to take a screenshot. I understand the technical limit of taking screenshots of DRM-protected content (e.g. Netflix), but why would my bank app be allowed to stop me from taking screenshots?

Solution: don't use mobile bank apps.

I'm forced to use a bank app in order to authenticate, even if I want to login on the desktop website. I think it's because of an EU regulation for strong authentication.
Post reply on HN