I’m writing a screen that displays a row’s worth of information from a DB. Basically it’s a Detail Fragment that represents information pertaining to one ‘row’ in a table. I want to understand the best practice for binding data from a cursor (one unique row from a table) to a layout of textviews, checkboxes, etc.
Is AdapterView the ticket?
@JoeMalin suggested:
Then write an adapter between a cursor and an array of text views.
Which boils down my question. What’s the right way to hook a series of text views to a cursor?
If you want to do processing on some of the cursor data before you move it to the text views, then you’re going beyond the adapter pattern, which assumes that “recasting” the form of a data structure to another data structure without any intermediate processing. The virtue of an adapter is that, for two data structures A and B linked by an adapter, it’s assumed that B automatically changes whenever A changes.
Of course, you can redefine the idea of adapter to insert your own intermediate operation, such as converting dates, or you could make the conversion an aspect of the view that’s displaying the data. I am guessing that the “processing” is really formatting, which you do for display purposes. That’s an attribute of the text view, not the data; write something that extends text view and converts dates as needed. Then write an adapter between a cursor and an array of text views.