Thanks for your info. So my understanding is, We build our own Content Provider with the help of our own data structure. These content will be persisted in the device memory (NOT in memory) and using content resolver we have to do data operations. Am I right?
Thanks Siva On Fri, Jun 17, 2011 at 4:57 PM, Sivaprakash <[email protected] > wrote: > Hi > > I am using > > ArrayList<HashMap<String, String>> mylist = new ArrayList<HashMap<String, > String>>(); > > to assign data into ListView.... So rather than doing this are you advising > that we can directly talk to GUI components and display the content? > > Thanks > Siva > > > > > On Fri, Jun 17, 2011 at 4:46 PM, jjoe64 <[email protected]> wrote: > >> hi >> you shouldn't hold munch data structure in objects because of the low >> memory on mobile devices. Instead you should use the sqlite feature and >> query, update, delete through a Content Provider. Don't work with Lists of >> Maps (List<Map<String, Object>>) or something like that for data storing. >> I'm currently refactoring my app because I did that (similar) mistake. >> >> -- >> 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 > > > > > -- > - Prakash. > -- - Prakash. -- 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
