> but that is 1) a pain, and 2) I don't want the rest of my application > to have to understand the database layout. I don't know of a > CursorAdapter that will do the transforms I am looking for, so I will > write them myself.
Please bear in mind that you are writing applications to run on mobile devices whose horsepower is reminiscent of PCs from a decade ago. Programming techniques that you might use on a current PC with tons of RAM, fast CPUs, and access to constant AC power are not necessarily recommended in a mobile device environment. > So, the question - I am thinking of simply subclassing the Polygon, to > create a DatabasePolygon, with all of the calls simply being the > correct callthru's to the Cursor. I assume Polygon is your own class, since I do not see one in the SDK. > I am thinking that this will still > preserve the usefulness of Cursors, will use very low memory because > they are wrapper classes, and will allow the rest of my application to > never know anything about the database, simply about Polygon. > > Thoughts? You are welcome to give this a try. Bear in mind that everything in the system that wants to use a Cursor (e.g., CursorAdapter) will not be able to use DatabasePolygons. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
