I've fought doing that myself, especially because you can't use the PreferenceActivity and have to redo your entire UI.
It would be really cool if we could plug in different "Preference" storage solutions. One could be the SharedPreferences object, but another could be a database. By having a SharedPreferences interface and being able to specify a preferences factory in the constructor or OnCreate method of the activity, we would be able to implement any solution we want and still use the preferences xml elements. Thanks, Eric On Wed, Feb 11, 2009 at 1:38 PM, JP <joachim.pfeif...@gmail.com> wrote: > > > Some more testing showed that the problem is not completely gone (in > my case). > > This is one of the last things I have on my list now... I've been > pushing this out but I suppose I'll work around all that now and drop > the preferences in a Sqlite database table. This will the master copy > now and I'll make updates to SharedPreference as changes occur. Kinda > sucks - it duplicates things - but I guess this is a case of gotta do > what you gotta do... > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
