Hi Koen,
Your approach doesn't sound that wrong to me.
How about having a master controller that is more or less what you have now,
and split the functionality that handles the data stream out into a separate
class that the master controller calls on to fetch the data? Then according to
what i
On Sep 19, 2012, at 12:14 PM, Koen van der Drift
wrote:
> Thanks for the link, lots of info there. Unfortunately he doesn't
> discuss the responsibility of the MVC classes in the slides regarding
> the best location for the NSURLConnection code. I got that and the
> paring already working, but
Thanks for the link, lots of info there. Unfortunately he doesn't
discuss the responsibility of the MVC classes in the slides regarding
the best location for the NSURLConnection code. I got that and the
paring already working, but need to make it more flexible.
- Koen.
On Wed, Sep 19, 2012 at 2:0
I haven't implemented what you're describing, but you might want to look
at Marcus Zarra's talk on Flexible JSON Importing. I don't know what
you're parsing (JSON, XML, or something else). I found the slides for
Marcus' Flexible JSON Importing talk here:
http://www.mactech.com/conference/presentati
Briefly in my app (OSX), I download data from a database to be
displayed in a view. I created a Controller that takes care of the
NSURLConnection, retrieves the data, and sends it to a database model
class to parse. It also takes care of updating the UI during the
download ("Download in progress",
