View Single Post
Old 09-14-2016, 02:18 AM   #3
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
For whole-screen content, I tend to use a separate HTML page and SVG. It is pretty much the only approach I'm aware of that will make things work robustly (almost) everywhere.

For smaller images, I'd normally expect them to be shown at actual size, rather than specifying size information, and I normally pick the image size to be something reasonable on an average device screen, and just let it be small on other devices. Whether that works or not for you depends on the layout.

But if you want to do something more complex than that, then yes, you'd pretty much have to have classes for each image size.

Last edited by dgatwood; 09-14-2016 at 02:22 AM.
dgatwood is offline   Reply With Quote