Weird how the Maps API docs mention installing several places only to immediately mention it is already installed for you: http://code.google.com/android/add-ons/google-apis/maps-overview.html
Cleaning that up could be one specific documentation improvement. The docs seem pretty straight forward otherwise, though. I got there by following links from the "Location and Maps" section of the Dev Guide. Some of the links out go to the Japanese version of pages, but that could be my OS/browser settings messing things up. The "cannot be resolved" error in Eclipse when trying to use the Maps API in an Android project with the wrong build target seems like it might be causing trouble. It's natural for a Java developer to go hunting for a JAR library to include when they see that error. In this case, however, the solution is to fix the build target. Anything dealing with the JAR is handled automatically by that. I wonder if the Android plugin for Eclipse could intercept this error message and put a better one in its place somehow. On Oct 8, 9:23 am, ian <[email protected]> wrote: > I;ve had no end of build path problems and I am still having them. One > problem I had was that I selected 1.5 instead of Google apis in my > build target and it would not recognize maps.jar on the path. > > Last night I scrambled up my build path and am unsure how to restore > it properly. I had one app running properly but while trying to fix > another, messed up everything in the workspace. Now none will compile. > > On Oct 8, 1:14 am, Lance Nanek <[email protected]> wrote: > > > What problems did you run into re the build path? I just recently > > published something on the market and can only recall even seeing the > > build path on an Android project once. A partner wanted to use > > Subversion instead of Git for source control, so I had to open the > > build path dialog in Eclipse and ignore .svn directories. Even that > > probably would have been handled automatically if I'd had a Subversion > > plugin installed. > > > On Oct 7, 10:08 pm, ian <[email protected]> wr soote: > > > > Well maybe it's juist me, but my Android development problems often > > > stem from build path errors. > > > > On this subject, he Android online instructions are vague and > > > sometimes unclear. The error messages are weak for this kind of error > > > and there is little in the area of mend utilities. > > > > To the novice, these arcane issues seem almost unsolvable. I'm sure > > > these sort of problems have caused some developers to abandon the > > > platform entirely and work on iPhone apps instead. > > > > Getting the maps-api key is also confusing for some beginners. > > > > Android is a big project that could benefit from better online info > > > and support. If they are really serious about Android, Google should > > > do more for the developers. > > > > As things stand now, Android developers have to rely that Google won't > > > abandon the project,and that the slow to be released phones will soon > > > gain viable market share. > > > > Honestly in Canada, I've never seen an Android phone. They are > > > available only on an unattractive three year package and nobody is > > > choosing them over similarly priced Pre or iPhones. > > > > You gotta have faith to be an Android developer. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
