Create "@2x" high-res icon assets for Mac builds about ivy HOT 4 OPEN

Also, according to the docs, we can tell raco to set the incs rather than having us moving them inside the .app ourselves: raco exe --icns ‹.icns-path›

from ivy.

@IonoclastBrigham
Does OS X actually require using the @2x file naming scheme? I'm mostly familiar with with the use of @2x file names when applying the principles of "responsive design" to images in a web page. And in that case, I think the new HTML5 standards (the srcset attribute or the picture element) offered a better, more flexible solution. I don't like how @2x treats the lower resolution as the standard base -- even smart phones are starting to get high-density screens -- and I kind of think using @2x in the filename just looks weird.

I do like the idea of using ImageMagick (or possibly GraphicsMagick) to take care of exporting the SVG at different sizes. Adding a build requirement will be less of an issue when we add binary packages, right?

from ivy.

1.0 was just released as binary packages for windows, linux, and os x. So yeah, the build dependency is irrelevant for the average user. And anyone who can install racket and build ivy from source likely already has ImageMagick installed. This is probably okay.

To your point, Mac and iOS apps can bundle copies of their raster assets with @2x and @3x variants for higher-density screens. This is equivalent to the drawable-Xdpi directory structure, for Android apps. It's not strictly necessary, as the system will try to pick the best version available, and scale it if needed. But it could potentially look kinda janky, so if you want control over how it looks, you provide them.

Alternatively, we might be able to use a vector version directly, though it might need to be exported from svg to some intermediate format. I know a lot of iOS/OS X graphics get packaged up as PDFs, but I'm not sure you can do that kinda thing with app icons.

from ivy.

Update: read-bitmap has the optional keyword argument #:try-@2x?

from ivy.