you will probably not like what I'm going to say, but: ranting on the forum is going to have very little results here.
even if there are Android developers who read them (and a fewer that even answer certain questions) they are all very busy at the moment. what this means is that the best way to report that kind of problem (i.e. "weak error reporting") is to *use the public issue tracker*. - register an issue, and chances that the problem will be seen and reviewed by a relevant member of the development team is increased - describe your problem as precisely as possible, trying to nail it to the simplest possible code snippet or instructions. this also dramatically increases the chances of seeing the issue fixed / answered dramatically in the next SDK release of course, I'm talking about problems that you want to communicate to Android engineers. feel free to use the forum to ask other members to see if there aren't simple work-arounds / way of using the system or if they have a solution for it first. sadly, your original post didn't contain any meaningful information we can use to track exactly the error reporting weaknesses you're talking about (and I certainly don't deny they exist). On Sat, Apr 5, 2008 at 6:19 AM, acopernicus <[EMAIL PROTECTED]> wrote: > > Yeah...the Challenge deadline is growing closer, so I needed to spread > a a little feedback to the Android team about the many days I've just > spent working around issues in the API. OK...first off...some of > those issues were mine but my biggest waste of time has been tracking > down error messaging like "Null", "IOException", "...". > > The error messaging on the MediaPlayer in particular has been killing > me these last few days but the error messaging throughout the entire > API in general is AWFUL. I would like the Google team to please > realize that..while yes this is a pre-alpha release...many of us are > wasting many precious hours of our spare time on this project and do > not have the benefit of the source code that will someday be > available. SO it woudl be great if they would please update their > error messaging to give us a clearer idea of just what has happened > rather than blank messages or simple "null" statements. > > If you feel the same way, then please echo your thoughts on Android's > error messaging. > > Biosopher > > > --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
