GeezerVison

✅ Deploy Preview for java-processing-faf822 ready!

Name	Link
🔨 Latest commit	f667685
🔍 Latest deploy log	https://app.netlify.com/projects/java-processing-faf822/deploys/6a3c0432e92d39000776747b
😎 Deploy Preview	https://deploy-preview-695--java-processing-faf822.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Flagging for review: should check how the new links get picked up by Fathom analytics.

Thanks for calling that out! I was about to tag you @SableRaf in regards to the visual elements. But sounds like it's good. I'll check the analytics

Another thing is the info tooltip for each distribution could include an explanation so ppl can tell the difference between each build.

I was about to tag you @SableRaf in regards to the visual elements.

I've been thinking about this too. I'd suggest putting the Snap button at the top since that's the recommended install for beginners, and the other two buttons could use a secondary color. People who want the .deb or flatpak versions likely know what they need, but a beginner downloading the wrong package is likely to get stuck.

Got it, @catilac.

I think Snap isn't the one we should highlight as it serves only Ubuntu users. Flatpak is the option that is both easy and that serves the most number of distros @SableRaf.

Does Flatpak take care of MIME file association, setting up the JAVA environment variable that the VS Code extension uses to locate Processing, and configure support for the pde:// URI schema?

I know that some distributions (like Mint) choose to disable snapd by default, but you can still re-enable it.

@ogoregen @SableRaf -- would it make sense to move this discussion into another issue? it sounds less urgent than fixing these links. let's move this discussion into discord and we can distill it into a task we can assign to @ogoregen?

Came here to file an issue about this. Tool tip would be great but right now this is very confusing, I had to go into devtools to figure out which one I wanted to download.

I think it would be great to merge this fix. @SableRaf think you would have the ability to do that.

@duskvirkus This should be addressed by the new download flow in #683, however it is currently blocked by processing/processing4#1425

@catilac If the download flow is likely to take longer, it may be worth patching the buttons separately in the meantime. What do you think?

@SableRaf Yeah I think patching makes sense for now, I'm currently blocked by other tasks on the way to ars

This should be addressed by the new download flow in #683, however it is currently blocked by

I was about to comment on processing/processing4#1425, saying it would be better to fix the links on the website first but now checking the discussion here, it seems we have a circular dependency. Any chance updating the links without #683 and processing/processing4#1425 ?

I just checked the deployment preview and everything looks fine. I think this can be merged without any blockers.