Question about from the ApiDemos sample project

by hackbod » Fri, 27 Jun 2008 08:55:54 GMT

Sponsored Links

And we can continue to put comments in sample code after completing
the final code for 1.0, so it is pretty low in priority at this
time. :)


Question about from the ApiDemos sample project

by Disco Stu 010 » Sat, 28 Jun 2008 01:37:40 GMT


Thanks for your response. Certainly clarifies a few things.

The sample code has been immensely valuable in getting a better  
understanding of the Android APIs. I totally understand the 'too many  
things to do' problem, I have been guilty of that many times. However,  
I would like to respectfully submit that a very large community of  
developers is potentially relying on ApiDemos code to learn about  
Android. "Well documented code" should be a key element of the  
delivery and not simply whether the demo code works or not. There is a  
lot of power behind the few lines of code that is not apparent at all.  
Honestly, by 1.0 timeframe a large number of us might not even need to  
look at this code. Now is when the comments will be most helpful.

Thanks again,



Sponsored Links

Other Threads

1. Verify Error with HTTPMIME / MIME4J

So, in following this post....

2. Access assets from within ParcelFileDescriptor / ContentProvider

Hi together,

Since a few days we are struggling with accessing asset files. Pretty
early I found out that accessing assets is not directly possible with
the "file:///" Uri.
Now my colleague wrote a ContentProvider class.

Within the ParcelFileDescriptor from the ContentProvider we use the
openFile method to directly access a css file when the pfd is called
from within HTML with the content:// scheme.
Unfortunately, the css had no effect on the HTML and I found out with
File.exists() that this file does not exist under "file:///
android_asset/ + filename", although the file is obviously under
assets/Resources in my package exlplorer.

My presentiment is that it's all just a minor misuse of URI paths.

Thanks in Advance for any help.




3. SharedPreferences: editor.commit() always false even though it commits

4. Application installing with default pre-made database file

5. location is always latitude 0 longitude 0 altitude 10 in v0.9

6. Task Manager, or something to close apps.

7. An Android wishlist from a soon-to-be-user