On Nov 14, 2010, at 10:40 AM, Matt Neuburg wrote:
> We all did all those steps manually for years and years, on every single
> application we wrote. Finally Apple realized they could save us some steps
> and wrote it into the template. Since the purpose of the provided instance is
> to functio
On Sat, 13 Nov 2010 19:35:45 -0600, William Squires said:
>1) Why is it, when you create a new Cocoa Application (or even some
>iOS Applications) in Xcode, does it generate AppDelegate
>(.h and .m) files, instead of calling them Controller (.h
>and .m)?
It's for your convenience. It used t
On Nov 13, 2010, at 5:35 PM, William Squires wrote:
> 1) Why is it, when you create a new Cocoa Application (or even some iOS
> Applications) in Xcode, does it generate AppDelegate (.h and .m)
> files, instead of calling them Controller (.h and .m)? Since these
> tie to the .xib - according to
1) Why is it, when you create a new Cocoa Application (or even some
iOS Applications) in Xcode, does it generate AppDelegate
(.h and .m) files, instead of calling them Controller (.h
and .m)? Since these tie to the .xib - according to MVC
paradigm - shouldn't it be a controller object for t
