On May 23, 6:30 am, MarcoAndroid <[email protected]> wrote: > Here's the most recent official platform versions distribution: > http://developer.android.com/resources/dashboard/platform-versions.html
That's the "newer" one that I referred to (at least, I think I did). I printed it out last week, along with a page showing the screen densities (unfortunately, the values were given only as "Hig", "Medium", and "Low"). I found another reference, though, that actually gave useful information on the screen sizes and resolutions. And yes, before anyone asks, I do know the difference. :-) > 1.5 + 1.6 = 5.3% so not that much anymore these days. If your > app is quite basic (not using any fancy 1.6+ SDK > functionality), you might as well still support 1.5 and higher, > because it should not cost you much in time & effort (that is: > build for 1.5, Android takes care of scaling etc). Ok, so I will just leave it at 1.5, then. At least, for my photography app. I want the UI to be clean and simple, and not distract from the photography it contains. When I get it all figured out, I hope to have simple transitions between images: either just changing (as it is now) or perhaps, a simple fade out/fade in...nothing too flashy. This is something I more or less already knew, which was emphasized for one particular photo, at our local professional photo lab, regarding the wooden frame I'd chosen...simple, non-obtrusive, and put the emphasis on the photo, not the frame. They said I'd picked the perfect frame for that very reason. :-) I'm applying that same concept with my UI, treating it as the "frame". > images might get blurry at a certain point device size. In that > case you indeed can put higher resolution images in the HDPI > folder. That's something I've been concerned with: how this will look on the new tablets.... But at 3 MB already...do I REALLY want to more or less triple the size of the app for a relative minority? Particularly when you consider that this is the first of several (this one is Scenic/Nature; I'll be at least adding one with my lightning photography, a waterspout I caught with my Nikon digital when I was living on the island, and other weather related imagery. I will probably also do two (to keep the app size reasonable) covering the Eglin AFB Armament Museum (also commonly referred to as the Eglin Air Park). Lots of static displays of everything from the old AC-47 Spooky, the AC-130A Spectre, etc., to the SR-71, and lots of bombs, missles, etc., too. Then, possibly another, focusing on the beaches we have here (which, if you don't know better, could easily be mistaken for fresh snow---pure white). > Of course you know about this page that explains a > lot:http://developer.android.com/guide/practices/screens_support.html If that's the one I'm thinking of, it's the one I mentioned above as having actual useful information on screen sizes and resolutions. :-) > Re: the icons: I guess you can find them in the Android source > code. I probably won't use more than the ones in the page showing the specs (at least, not anytime soon), so I'll probably just grab those for now. > And yes it is still recommended practice to get a copy of them > into your app, in case they might get removed in some new > Android version. Just my opinion here, obviously, but shouldn't the SDK sample code be using icons from disk, then, instead of using the ones in android.R.drawable.....? As is, they teach the wrong concept in that regard. Later, --jim -- 73 DE N5IAL (/4) < Running FreeBSD 7.0 > ICBM / Hurricane: 30.44406N 86.59909W "No, try "rm -rf /" "As your life flashes before your eyes, in the unit of time known as an ohnosecond...." (alt.sysadmin.recovery) -- 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
