On Thu, Aug 18, 2011 at 8:51 PM, Ian <ian.d...@gmail.com> wrote: > > Has anyone adapted the existing Android data provider system to return data > Objects based on the data in a cursor and then keep those objects up to date > when the backing data store changes? Me naive approach would be to store > serialized versions of these objects in a BLOB column in a sqlite table and > wrap the cursor with an iterable deserializer mechanism, but I would rather > not deserialize the objects into memory until I absolutely had to. > > I'm working on a library which is meant to facilitate writing code in that style. It's written in Scala, which may be a plus or a minus, depending on taste. (Having first-class functions certainly makes it easier to deal with callbacks.)
Source code here: https://github.com/rst/positronic_net and here are a couple of sample apps: https://github.com/rst/shopping_assistant https://github.com/rst/UmbrellaToday FWIW, I'm still working on it, trying to automate more boilerplate programming tasks, and it's possible that some of the existing API will wind up changing in minor ways to accommodate that. (I'm bumping the version number on incompatible changes, of course.) If you'd like to follow along, the current action is on the development branches in the positronic_net repo. Hope this is of interest; I'd also like to see if anyone else has done something similar... rst -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en