On May 22, 11:57 pm, Zsolt Vasvari <[email protected]> wrote:
> First of all, I would think very seriously about not building a new
> app that supports 1.5 in the middle of 2011.

Honestly....I'm not so sure that I'm going to now.  I'd seen (and
asked
about this in the Android Forums/"Lounge" forum about a week ago---no
answer yet) an Android OS version distribution chart an Android OS
version distribution chart that showed 1.5 and 1.6 as each having
roughly
1/3 of the Android market, so I didn't want to limit my apps to just
the
remaining third.  Well apparently that "current" chart wasn't so
current,
after all.  :-)

Now, I'm seriously considering setting it at 2.2+.  There's another
good
reason for this, too.  My laptop meets the stated system requirements
(on the respective page on this site) for Android development, but it
doesn't meet *THE* requirements (it's only got a single 1.4 GHz CPU),
so I have to test on my Motorola Bravo (Android OS ver. 2.2.1).
Limiiting it to 2.2 and up makes more sense anyways.

Ok, so that part of the question is history...no longer matters.

But the other half is still significant:  If the SDK samples are
teaching
me to use android.R.drawable.[whatever], and the page describing the
exact dimensions, specific %grey values for shading, etc., says that's
exactly what you should NOT do, A) which do I believe, and B) if I AM
supposed to get my own copy of the icons and use them....where?  The
one set (zip file containing, or so it said, the icons for different
screen densities) only had a bunch of Photoshop documents that my
version thinks are corrupted and won't open.

And on that topic, yet ANOTHER question.  My first (and several that
may
follow it) is a bunch of my photography favorites from the Scenic/
Nature
category (more or less).  It's got 40 images (I've seen gripes about
such
apps only having 20 or so images), and is about 3 MB, which I'm told
is
huge.  All of the (reduced) images in the app are currently 72dpi,
with
the max x/y size in pixels set to 255.  Do I REALLY want to scale
those
up to 100 or more dpi, and larger image sizes?  Or, just let the phone
scale them to fit their container?  All I know, right now, is that
they
look great on my phone.

Btw, the high-resolution TIFFs are for poster-size enlargements only
(some of them have already sold some 16x20s at $75 each, but at the
time, I was in the middle of the cancer ordeal, and didn't have the
energy to really pursue that any further---but this app will allow
anyone who wants to to order poster-sized prints).  At the very least,
I'm hoping it will help me with a little extra cash each month, and if
I'm really lucky, it might even help me get out from under the whole
Social Security Disability/Medicare BS---I would *LOVE* to see it do
THAT!).

So that's the whole story, new questions and all.  Meanwhile, I'm
going
back to making improvements to the simple UI I started with---as I
learn
more, it improves, and so on.  I'm currently working on intents for
the
info screens, using the current image as wallpaper, and trying to
figure
out whether it's Gestures or something else that I need to use to be
able
to change to the next/previous image with just a swipe on the
screen....

Later,
   --jim

--
73 DE N5IAL (/4)        | Peter da Silva:  No, try "rm -rf /"
[email protected]    | Dave Aronson:    As your life flashes before
< Running FreeBSD 7.0 > |      your eyes, in the unit of time known as
an
ICBM / Hurricane:       |      ohnosecond....
(alt.sysadmin.recovery)
   30.44406N 86.59909W  |

-- 
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

Reply via email to