- From: Wesley Hales <whales@redhat.com>
- Date: Tue, 13 Dec 2011 09:47:27 -0500
- To: Filip Maj <fil@adobe.com>
- Cc: "public-native-web-apps@w3.org" <public-native-web-apps@w3.org>, Brian LeRoux <brian.leroux@nitobi.com>
From a developer usability/maintenance standpoint, what happens when I'm trying to target 5, 6, or more resolutions? So the "recommended" filename convention might be something like: [name]_[device]_[type]_[ppi]_[orientation]_[dimensions].[png,jpg,gif] Of course, they wouldn't be required to follow any convention, so that seems like a maintenance nightmare once you try to support a lot of devices. What are you guys seeing from real world apps? At a minimum, just supporting Apple devices, you have 3+ resolutions x 2 orientations. imo, there are a few good things about having the width/height attributes: 1) developers know, up front, which screen size they are targeting -- allowing them to keep the config readable. 2) Allowing the user agent to calculate and parse the image size seems like needless overhead, since the developer might already be inputing the image dimensions in the filename. What happens when the device resolution doesn't match the provided splash images? Do we stretch the closest one or ignore it? Wesley On Dec 12, 2011, at 5:43 PM, Filip Maj wrote: > That's a good point... Not sure why we did that. Probably laziness :) > > I agree with you Marcos, the user agent should figure that stuff out. > > On 11-12-12 9:48 AM, "Marcos Caceres" <w3c@marcosc.com> wrote: > >> I'm was looking at: >> >> https://build.phonegap.com/docs/config-xml >> >> And see that Phonegap is allowing multiple splash screens so that splash >> screens can be matched up nicely to the most appropriate screen >> dimensions. >> >> We should probably do the same in our spec. >> >> Phonegap guys, are you finding that people are including multiple splash >> screens? >> >> I'll just say that the only thing I don't like about the phonegap >> solution is that the dev has to put in the width and height values (its >> really error prone)Š in W3C widgets, we make the device look those up >> (unless the format has no intrinsic width/height, as is the case with >> SVG). That way, the device can determine the best fit dynamically at >> start up (and store that on first run, for optimization sake). >> >> <splash src="splashes/ipad3_retina_omg_crazylarge_VERTICAL.png" /> >> <splash src="splashes/ipad3_retina_omg_crazylarge_HORIZONTAL.png" /> >> >> >> <splash src="splashes/ipad.png" /> >> >> >> <splash src="splashes/iphone_retina.png" /> >> >> >> <splash src="splashes/iphone_3gs.png" /> >> >> >> >> >> >> etc. >> >> >> >> -- >> Marcos Caceres >> >> > >
Received on Tuesday, 13 December 2011 16:06:34 UTC