@James
Freeway’s “Retina” checkbox was never intended to “create” retina images, it’s more likely there to indicate Freeway to use an image twice the pixel-width (dimension) within your artwork.
####Lingo
The standard screen definition for images in web is 72 dots per inch.
####Retina
It is still 72 dots per inch, but twice the dimension of your image.
####In Freeway
Assumed your dog.jpg shall be the hero-image of your page. It’s 960px wide and has 72dpi. Your page-width in Freeway is as well max-width: 960px.
As standard you’d place it and good.
For retina, you’d now have to double its dimensions, using whatever application.
You end up in a (pretty blurry) 1920px wide - but still 72dpi - image. Save it as dog-large.jpg.
Now draw your HTML item and pass-through your dog-large.jpg. Initially, the html-frame will explode the dimensions of your page-width, right? Now check the retina check-thing and it will shrink down to the expected 960px.
Set the width to 100% (height auto) and you’re even responsive.
####Conclusion
Preferably leave everything on 72dpi. Figure out the pixel-width and argue:
Twice (1.5, 3x whatever) of the given pixels!
####If your reaction is now:
“These look great. I’d wish it would be a bit more complicated”, you’re in luck.
Because the challenge for now is to ask yourself: Wouldn’t it be better to serve different varieties of this image and let the browser decide which one to take? And that’s what Duncan is referring to and Sparkle manages for you - and Freeway never did. We had more the “either … or” approach.
To me it’s an authors responsibility - and not a machine’s. But that’s another chapter of the book. And yes - with Sparkle you’d be in a safer space.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at: