On May 4, 10:09 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Joa,
>
> I don't agree.
>
> <Let's agree for a moment that this contest is not
> going well. >
>
> The contest is going better than I expected. Much of the SDK works.
> You may have to choose to use the part that works,
My apps work and I can happily report that I could take MapView and
classes associated-in-function all the way to a no-excuses user
experience. So the SDK is just fine for what I found. And as soon as
we can get location-based search back, I can port to the latest SDK,
from m3-37.
Below just a few tricks I am using to maximize usability and user
experience:
- image pre-fetching
- server-side processing and garbage collection during
MapView.animate()
- no object creation or any of the expensive operations in graphics
displaying code (subclass to Overlay), following the code optimization
guidelines (thanks guys for that part of the documentation; I've been
going there frequently)
- the above left to background threads which also fetch the server
side data without any ugly GUI hang-ups. Kind-off a high level z-
Buffer
Just like it's supposed to be in a modern GUI. This is professional
level stuff because this is what I used to do to make a living with
presentable formal education...
And now I am finding that the judges are not even concerned about
calling a single app feature. Naturally, I am little miffed.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Android Challenge" 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-challenge?hl=en
-~----------~----~----~----~------~----~------~--~---
