6 list persistance

[tycebrown]

Here is a design overview:

• Instead of directly storing a List, I've abstracted that into a class called ListModel, which can be directly put into an isar database.
• Isar database work is abstracted into a static class called ListsDatabaseManager.

Some design questions/concerns:

• At the current moment, the list model (and its items) are loaded "eagerly", so all the lists and their items are loaded at the start. Should the items and list model's metadata (such as the name of the list model) be loaded separately? Do you think an "eager" loading would seriously slow down the app?
• All updates are eager (I couldn't find any way to schedule updates to happen at the termination of the app), so a slight change leads to the whole list model being re-put into the database. Would this slow down the app noticeably?
• Are there any sloppy names that need to be fixed (like ListsDatabaseManager)?

[Pertempto]

Here is a design overview:

• Instead of directly storing a List, I've abstracted that into a class called ListModel, which can be directly put into an isar database.
• Isar database work is abstracted into a static class called ListsDatabaseManager.

Some design questions/concerns:

• At the current moment, the list model (and its items) are loaded "eagerly", so all the lists and their items are loaded at the start. Should the items and list model's metadata (such as the name of the list model) be loaded separately? Do you think an "eager" loading would seriously slow down the app?
• All updates are eager (I couldn't find any way to schedule updates to happen at the termination of the app), so a slight change leads to the whole list model being re-put into the database. Would this slow down the app noticeably?
• Are there any sloppy names that need to be fixed (like ListsDatabaseManager)?

I think the current "eager" system should be fine for now. We can optimize later if we need. For ListsDatabaseManager, why not call it just DatabaseManager or DbManager?

[Pertempto]

Functionality is still working great! Just a few code-cleanup things I saw.

[Pertempto]

The code looks good!