title: SimpleCursorAdapter's old constructor deprecated.. really?
body: <p><a href="http://developer.android.com/reference/android/widget/SimpleCursorAdapter.html#SimpleCursorAdapter%28android.content.Context,%20int,%20android.database.Cursor,%20java.lang.String%5B%5D,%20int%5B%5D%29" rel="noreferrer">Here</a> it says that <code>SimpleCursorAdapter</code>'s API level 1 constructor is deprecated and the use of <code>LoaderManager</code> and <code>CursorLoader</code> is recommended.</p>
  
  <p>But delving into the <code>LoaderManager</code> and <code>CursorLoader</code>'s use I found <a href="http://developer.android.com/resources/samples/Support4Demos/src/com/example/android/supportv4/app/LoaderCursorSupport.html" rel="noreferrer">this</a> example where inside an inner class that extends a <code>ListFragment</code> (an extension of Fragment itself I suppose) we create a <code>CursorLoader</code>. Everything seems ok, except for the fact that <code>CursorLoader</code> takes a <code>Uri</code> as an argument. So this implies that I need to create a <code>ContentProvider</code> to get access to my database.</p>
  
  <p>I must confess it looks like an overkill to have to go through all of this just to create a simple <code>ListView</code> with items coming from a database. Specially if I have no intention of making my database data available to other apps, and the main purpose of a content provider is to do that.</p>
  
  <p>So is it really worth it? </p>
  
  <p>Especially in cases like mine where the content to be fetched is likely going to be small. I'm seriously considering doing it the old way, what do you say?</p>