1,234
edits
Changes
no edit summary
== Implementing a content provider ==
Some overwhelming documentation [http://developer.android.com/intl/ja/guide/topics/providers/content-provider-creating.html here].
A content provider looks very much like an SQLiteOpenHelper we've used in our SQLite lecture/lab. It's so similar it's easy to confuse the two.
== Implementing a content resolver ==
Some overwhelming documentation [http://developer.android.com/intl/ja/guide/topics/providers/content-provider-basics.html here]. Creating a Uri with[http://developer.android.com/intl/ja/reference/android/net/Uri.html#parse%28java.lang.String%29 Uri.parse].
A content resolver is just the client for the content provider. To demonstrate how this system is supposed to work we'll have the content resolver in a different appliction.