I've described a method for using retina images here:
http://retina.teknonsys.com
On Tuesday, April 17, 2012 5:21:41 AM UTC-4, Evan Ruff wrote:
Hey guys,
So I'm designing an application to be used on tablets and phones. With the
introduction of the new iPad, my images are getting BIG. Real
David,
This is EXACTLY what I was looking for!
IMHO, this is absolutely a critical feature for webapps to have moving
forward. It would be great to move this into the trunk for 2.6.
Thanks!
E
On Wednesday, August 15, 2012 3:35:35 PM UTC-4, DCYorke wrote:
I've described a method for using
Shouldn't the image size remain constant with screen resolution? Otherwise
there would be a similar need on desktops. Are you specifying image size in
pixels? Could you use percent?
Mike
On Tuesday, April 17, 2012 2:21:41 AM UTC-7, Evan Ruff wrote:
Hey guys,
/div
So I#39;m designing
Shouldn't the image size remain constant with screen resolution?
Otherwise there would be a similar need on desktops. Are you specifying
image size in pixels? Could you use percent?
Apples HiDPI devices double every pixel so that the appearance of the web
application remains the same
Am,
This is essentially what I want to do, but with a more refined, reusable
approach.
One thing that I've found is very helpful with the Android framework, is it
has some built in failover type stuff. So if I have an hdpi asset, but no
corresponding asset in the ldpi directory, it will just
Joe,
SVG would be awesome if my sources were vectors. By the time the images
have gotten to me, they're bitmaps.
Does GWT support SVG in client bundles?
Thanks,
E
On Tuesday, April 17, 2012 10:21:31 PM UTC-4, Joseph Lust wrote:
Note quite what you're looking for, but why not use SVG for
You could wrap them up as a TextResource in your ClientBundle and inject
them into the page, but Android 1-3's Browser doesn't support SVG, nor do
IE versions prior to 9.
On Thursday, April 19, 2012 12:38:54 PM UTC-5, Evan Ruff wrote:
Joe,
SVG would be awesome if my sources were vectors. By
Colin,
This seems to be similar to Jens suggestion. I just read over the
Appearance Pattern information and it seems like it would be quite a lot of
code for every Widget in the application. Are you suggesting that the
ImageBundle itself have an appearance abstraction, or that each Widget have
I think it'd be a little too specialized for ClientBundle itself to support
such a thing - that said, a custom *ClientBundleGenerator subclass could be
used in conjunction with file naming conventions to work this out. The
basic idea would need to be that each file has one of several suffixes,
Hey guys,
So I'm designing an application to be used on tablets and phones. With the
introduction of the new iPad, my images are getting BIG. Real big. HUGE.
They're so big at this point, that it's really unwieldy to download the
ginormous ImageBundle; further, when scaled down in the browser,
What about a custom property for deferred binding in a .gwt.xml file and a
small javascript that fills its value based on window.devicePixelRatio.
Older iOS devices have a ratio of 1 while the retina devices have a ratio
of 2 because each pixel is doubled. So you could define your own ratio
It could be possible to wrap your ClientBundles in an appearance
implementation, and use replace-with declarations on that, to check for dpi
when the app starts up. Check out the notes on the appearance concept at
Note quite what you're looking for, but why not use SVG for many of these
graphics? In most cases the result will be smaller than a png and you will no
longer need to worry about resolution creep. This is what we used for our ipad
app.
Joe
--
You received this message because you are
13 matches
Mail list logo
