-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In any case, I think that this is only part of the problem and in most cases it's not a Google problem, but our own problem.
If in your case it makes sense to just grow the drummer up, in my case I have some fact sheets, related to the same item, that are shown one per screen with a tab widget. If I think of an iPad-sized tabled, it doesn't make sense to just scale up the font sizes etc... It would make more sense to group together some fact sheets so the user can see many fact sheets at the same glance. For the Galaxy pad size, I don't know since it's mid-way. In any case, I think that for many apps it will make sense to provide alternate layouts for large screens. I think it's also difficult to say in advance which the better solution is: I can't figure out how a pad could be used by only having the emulator. I need to grab a real device and play as a real user, and then find out which is the best way to use my app with it. - -- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." java.net/blog/fabriziogiudici - www.tidalwave.it/people [email protected] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyPzYcACgkQeDweFqgUGxdZpgCfWUDEqEZ3vaPPBaedJwygrgSL 8lwAn2ETUcChxwsjlyapYFUZvJfoc69K =u6Vm -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
