Get Android Application Development For Dummies, 2nd Edition now with the O’Reilly learning platform.

You first set up some parameters, ask a ContentResolver to complete a create or update, and then process the result and notify. If the mRowId is greater than 0, the user wants to edit an existing task. If the mRowId for the fragment is 0, the user wants to add a new task. There, the app responds to the user’s Save button click. When the user creates a task, it takes place in the OnClickListener of the mConfirmButton of ReminderEditFragment. Saving values from the screen to the database The next sections introduce you to the entire implementation of ReminderProvider, which outlines the CRUD operations. Update the user interface by displaying a toast and closing the edit activity.Īfter inserting your first task, you should have enough of a grasp on the ReminderProvider class interaction to perform more tasks. Store the values to the ReminderProvider database using a ContentResolver.ģ. To insert your first task into the SQLite database, build the Save button click listener to:Ģ. Inserting tasks is simple, after you get the hang of it. These user interactions cover the create, read, update, and delete(CRUD) operations needed to make the Task Reminder application work. The user can then tap a task to edit it, or long-press the task to delete it. After you have a ContentProvider, you can create a task for it: Insert a record, and then list all tasks on the ReminderListFragment.

Sqlite android app