[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
ok, I thought all the source was there. I used jad to decompile android.jar in the SDK directory. But there's more code in there than one could read in a career. If you need a few individual files, I can email them to you. thanks, Anil On Apr 7, 11:00 pm, acopernicus <[EMAIL PROTECTED]> wrote: > Thanks Anil. > > I was hoping to get the Java source code for classes like the > MediaPlayer, LinearLayout, & such. > > Much appreciate the pointer to the Emulator code though. > > Anthony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
Thanks Anil. I was hoping to get the Java source code for classes like the MediaPlayer, LinearLayout, & such. Much appreciate the pointer to the Emulator code though. Anthony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
On Apr 5, 12:23 pm, acopernicus <[EMAIL PROTECTED]> wrote: > Sadly the source isn't located at that page, but if someone has access > to the source code, then please send me the link to it. > ... but until then, we need to > discover it ourselves by reading through the code. > > Anthony Here it is: *reading through the code.* LOL happy reading :D http://code.google.com/p/android/downloads/list --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
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 android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
@Dan U. "There always seems to be a stack trace in LogCat, although sometimes something odd happens and the LogCat output doesn't show up in Eclipse. " I've also seem this problem, LogCat sometis stops being updated. I think this is a bug. I'm too lazy to report it though. On Apr 5, 3:46 pm, "Dan U." <[EMAIL PROTECTED]> wrote: > Interesting. I don't have the apk with m5-RC14, but api demos were on > the emulator the first time I started it up. No need to install. There > was a post about RC15 not having them, but I don't recall if that was > the real issue. > > Back on topic... > > > I can handle instability but operating in the dark because of vague > > errors that simply say "null" or nothing at all is simply amateur > > programming. > > Yeah, some of the error handling is a bit bad. To get a null pointer > where the problem is in android code itself isn't so great. I don't > recall running into any place where you just get "null" or nothing at > all though. There always seems to be a stack trace in LogCat, although > sometimes something odd happens and the LogCat output doesn't show up > in Eclipse. > > On Apr 5, 10:38 am, acopernicus <[EMAIL PROTECTED]> wrote: > > > > > Hi ank, > > > Good question. My m5-RC14 version of the SDK doesn't include an > > APIDemos.apk file so you may need to create it using Eclipse and then > > push it using the info outlined here. > > > On the other hand, I did accidentally delete my APIDemos from the > > Emulator and simply deleted my Android folder and started over again. > > To fully delete the Android install, you'll need to delete one of the > > other directories it creates outside the install folder. See this > > thread: > > >http://groups.google.com/group/android-beginners/browse_thread/thread... > > > Lastly, if you have found the apiDemos.apk and simply want to push it > > to the Emulator, then do this: > > 1) Quit out of any running app by clicking the home button. > > > 2) run this command: adb install /apiDemos.apk > > > 3) Note: Seeing the new applications sometimes requires restarting > > the Emulator as app manager sometimes only reads manifests on start. > > > Best, > > Anthony- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
Interesting. I don't have the apk with m5-RC14, but api demos were on the emulator the first time I started it up. No need to install. There was a post about RC15 not having them, but I don't recall if that was the real issue. Back on topic... > I can handle instability but operating in the dark because of vague > errors that simply say "null" or nothing at all is simply amateur > programming. Yeah, some of the error handling is a bit bad. To get a null pointer where the problem is in android code itself isn't so great. I don't recall running into any place where you just get "null" or nothing at all though. There always seems to be a stack trace in LogCat, although sometimes something odd happens and the LogCat output doesn't show up in Eclipse. On Apr 5, 10:38 am, acopernicus <[EMAIL PROTECTED]> wrote: > Hi ank, > > Good question. My m5-RC14 version of the SDK doesn't include an > APIDemos.apk file so you may need to create it using Eclipse and then > push it using the info outlined here. > > On the other hand, I did accidentally delete my APIDemos from the > Emulator and simply deleted my Android folder and started over again. > To fully delete the Android install, you'll need to delete one of the > other directories it creates outside the install folder. See this > thread: > > http://groups.google.com/group/android-beginners/browse_thread/thread... > > Lastly, if you have found the apiDemos.apk and simply want to push it > to the Emulator, then do this: > 1) Quit out of any running app by clicking the home button. > > 2) run this command: adb install /apiDemos.apk > > 3) Note: Seeing the new applications sometimes requires restarting > the Emulator as app manager sometimes only reads manifests on start. > > Best, > Anthony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
Hi ank, Good question. My m5-RC14 version of the SDK doesn't include an APIDemos.apk file so you may need to create it using Eclipse and then push it using the info outlined here. On the other hand, I did accidentally delete my APIDemos from the Emulator and simply deleted my Android folder and started over again. To fully delete the Android install, you'll need to delete one of the other directories it creates outside the install folder. See this thread: http://groups.google.com/group/android-beginners/browse_thread/thread/f846f460bf26c983/a3d0cea219a298d8?lnk=st&q=appdata+local+android#a3d0cea219a298d8 Lastly, if you have found the apiDemos.apk and simply want to push it to the Emulator, then do this: 1) Quit out of any running app by clicking the home button. 2) run this command: adb install /apiDemos.apk 3) Note: Seeing the new applications sometimes requires restarting the Emulator as app manager sometimes only reads manifests on start. Best, Anthony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
Sadly the source isn't located at that page, but if someone has access to the source code, then please send me the link to it. We won't have to worry about poor error messaging if we can go directly into the Android source code to track down the root of the problem. The best way for us to learn how to better program in Android will be having access to the design philosophy & coding logic that the Android team is following. Of course, someday we'll have a library of books written on Android's design philosophy, but until then, we need to discover it ourselves by reading through the code. Anthony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
I think perhaps the source is available at http:/code/google.com/p/ android click on the source tab. But I don't think Source Code is the answer at this stage. On Apr 5, 1:44 am, acopernicus <[EMAIL PROTECTED]> wrote: > Thanks for the reply Andrex...but happily Android's poor error > messaging is definitely not an issue with the Java language. It's a > matter of proper programming and understanding that others must be > able to develop off your code base. > > I can handle instability but operating in the dark because of vague > errors that simply say "null" or nothing at all is simply amateur > programming. > > I've been on both sides, and as I admitted, Android is in a pre-alpha > release state. But in order to compete with the bigger players out > their (iPhone and Windows Mobile), the Android code base will > definitely need to improve it's error messaging feedback > substantially. > > In lieue of better messaging, I would simply accept getting the source > code ASAP even knowing that it will change. I can guarantee that we > would all MUCH rather recode our applications as the source changes > rather than try to program to a black box like we are now. > > So perhaps I should re-title this post to "Please Release the Android > Source Code ASAP". > > Best, > Anthony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
Hi frd, I tried new Android Release but when i started emulator then there is no Folder for API Demo so ccan u suggest me tht where the problem lies. I am not able to find exact probGuide Me. Thanks in advance.. On Apr 5, 11:44 am, acopernicus <[EMAIL PROTECTED]> wrote: > Thanks for the reply Andrex...but happily Android's poor error > messaging is definitely not an issue with the Java language. It's a > matter of proper programming and understanding that others must be > able to develop off your code base. > > I can handle instability but operating in the dark because of vague > errors that simply say "null" or nothing at all is simply amateur > programming. > > I've been on both sides, and as I admitted, Android is in a pre-alpha > release state. But in order to compete with the bigger players out > their (iPhone and Windows Mobile), the Android code base will > definitely need to improve it's error messaging feedback > substantially. > > In lieue of better messaging, I would simply accept getting the source > code ASAP even knowing that it will change. I can guarantee that we > would all MUCH rather recode our applications as the source changes > rather than try to program to a black box like we are now. > > So perhaps I should re-title this post to "Please Release the Android > Source Code ASAP". > > Best, > Anthony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
Thanks for the reply Andrex...but happily Android's poor error messaging is definitely not an issue with the Java language. It's a matter of proper programming and understanding that others must be able to develop off your code base. I can handle instability but operating in the dark because of vague errors that simply say "null" or nothing at all is simply amateur programming. I've been on both sides, and as I admitted, Android is in a pre-alpha release state. But in order to compete with the bigger players out their (iPhone and Windows Mobile), the Android code base will definitely need to improve it's error messaging feedback substantially. In lieue of better messaging, I would simply accept getting the source code ASAP even knowing that it will change. I can guarantee that we would all MUCH rather recode our applications as the source changes rather than try to program to a black box like we are now. So perhaps I should re-title this post to "Please Release the Android Source Code ASAP". Best, Anthony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Call out to the community about the poor quality of Android's error messaging
Well that's what you get when you program in the Java language... Although I agree, some errors are seemingly random. It'd be nice to have some sort of stability, but I'll make do because of how great Android is now already. On Apr 5, 12: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 android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
