I implemented a profile system in one of my apps with the help of an SQLiteDatabase (basics are explained in the notepad tutorial ). You only need one table to store profile name/id, and all of the settings you want.
I implemented a profile system in one of my apps with the help of an SQLiteDatabase (basics are explained in the notepad tutorial). You only need one table to store profile name/id, and all of the settings you want. Save each profile as a new record in your table, with an appropriate name field retrieve all records and display the list of names when you want to user to be able to select a profile (e.g. SELECT * FROM Profile) delete a profile in your system by deleting the corresponding record (e.g. DELETE FROM Profile WHERE name='john') I also saved the name/identifier of the current profile using SharedPreferences so that my system had an easy way to know which profile was currently/most recently active, outside of the context of profile loading.
The latter seems more flexible to me and e.g. Makes it easy for users to exchange profile files. – drjr Jan 12 at 9:48 My profile data was heavily linked to other areas of my system and I felt more comfortable implementing it with a SQLite db. I think SQLite would offer better support for scalability and data manipulation/querying.
For simple data storage, I think XML could be suitable here. However, it is hard to be sure that your use cases for the data will stay simple forever... Using XML for profile exchange is still a good idea. Stackoverflow.
Com/questions/201568/… – antonyt Jan 12 at 11:36.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.