Hi, For the the APIs with known bugs (like the Reverse GeoCoding> getFromLocation() returns null) you could use any of -- dummy data/demos/workarounds. Just make sure to clearly mentionthe bug and the workaround that you used in your README file and the judges will accept it.
Thanks, Megha On Sun, Mar 23, 2008 at 10:28 PM, kelvin <[EMAIL PROTECTED]> wrote: > > From what I can gather (from my own experimentation and from this > thread > > http://groups.google.com/group/android-developers/browse_thread/thread/c14fa89fa1d3ffa1 > ), > the reverse geocoder functionality is currently mocked up, with a > handful of hard-coded addresses. > > I understand that this is probably be worked on, but I'm curious as to > how this is going to be treated as far as judging the ADC. With my > group's submission this functionality plays a fairly large role, and > we are concerned that with the crippled state of the geocoder, our > application may not be viewed in the proper light. Obviously the > judges would understand the limitations, but we can't help but fear > that without such a large chunk of the functionality present, our > entry just won't stand on its own. > > Can someone with inside knowledge on the process recommend a course of > action for us? Will the geocoding functionality be complete in time > for the judging? Should we be looking into using a third-party > geocoder? Or should we simulate all the data so that we essentially > have a demo running on rails? > > Thanks in advance. > > -kelvin > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
