Quote:
Originally Posted by exorcyze
I'm not sure I have a solution that I'm 100% happy with yet, but I had gotten tired of having to keep adding things to track to the app delegate. I also try to not overuse singletons, and since there is already one handy ( thanks to the AppDelegate ), I simply made a DataManager class that would handle the application data.
In many other languages you'll see a class like that being a singleton so it can be used to access / manage data from anywhere. But since we already have our singleton, I simply made an instance of that as a property of the AppDelegate - then referenced data properties and methods from within there.
Coupling that with FMDB for database access simplified my code and consolodated it to one handy place without making my delegate all cloudy.
Would love to hear any better approaches though. =)
|
Anything you can share? We all seem to be looking for a packageable/reuseable prototype.
TIA
Dick