Look, this is a niche market app. I don't want to spend time revising it. That would be a BAD business decision. This problem effects more developers than myself. Just give us a tool to check! Some of us had to do something clunky like you suggest when Samsung came out with the Galalxy tablet back in 2009 and contacted developers (including me). Android Developer Support was not happy about those kinds of solutions.

Another solution I've thought of but more of a test is to release a free do nothing app to Play with the element additions and see what gets filtered. Once I have the information I could delete it from Play. Probably not something Google would like developers doing.

BTW, have you actually worked with those various sw qualifiers? I used those in the page view version and particularly to get specific font sizes from dimension files. Those are broken too and it's been reported as an issue. My Galaxy Nexus phone won't use a 720p file but a 360p one instead. Some sizes work and some don't. At least these could be tested on the emulators. The emulators don't care about the elements in the manifest.

On 12/21/2012 09:48 AM, b0b wrote:
You could programatically start different activities from a proxy activity,
based on qualifiers:

if(isSw600dp()) {
   startActivity(); // 7" tablet
} else  if(isSw720dp()) {
   startActivity(); // 10" tablet
} else {
   startActivity(); // phone
}

Writing the isSwXXXdp functions is very easy.

On Friday, 21 December 2012 18:26:48 UTC+1, jtoolsdev wrote:
On 12/21/2012 05:05 AM, b0b wrote:
Why simply not have a single APK ? That way you do not have to go
through
possible <supports-screens> and <compatible-screens>
issues ?

You single APK would pick up adapted layouts / resources based on
qualifiers to display
7" and 10" UI.

That's not a solution because the GUI code is different between page and
fragment views.  The solution should be that xlarge should be ONLY
screens 10" and above and not include ANY 7" tablets or even 8.9"
tablets.  Adding xhdpi looks like it would solve it for the Nexus 10.
The Nexus 7 should get the page view version and shouldn't even be
filtered out now.  I would say the manifest elements weren't
particularly thought out all that well.  The developer console should
also let me check what devices are filtered out even before activating
an APK.  Or as I already said and others have asked for give us a tool
to check included in the SDK.



--
You received this message because you are subscribed to the Google Groups "Android 
Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/android-discuss?hl=en.

Reply via email to