Totally stoked to say that my Obj-C 2.0 screencast in online.
Looking forward to hearing about the cool iPhone apps you come up with!
Nice! I already bought your iPhone series, and they really helped me a lot.
I was waiting for this series to come out, to really dive in objective-c 2.0.
ps. Could you email me? I have a question about episode 4 of the iPhone series.
Roy van der Meij
on January 15, 2009 at 04:53 AM MST
Bought a copy hot off the (video) presses last night...
on January 15, 2009 at 04:53 AM MST
Thanks for the screencasts, hopefully this will be a nice long series =D
Any chance you will be making a series on creating games for either the iphone or mac?
on January 16, 2009 at 04:34 PM MST
Thanks! Yep I'm planning several in this series on lots of topics, any one topic you are more interested than others?
I'm not sure about doing game development stuff for iPhone, the topic is so huge. I'm thinking that the tech side (OpenGL, Core Animation) is stuff that I think makes good screen cast. Theory of games is prob out side the realm of what I'd do. Is there anything there you'd like to see?
on January 16, 2009 at 06:17 PM MST
I've just enjoyed the first two screencasts, and am eagerly awaiting the next installments :)
on January 20, 2009 at 10:33 AM MST
Thanks for the books and the screencasts. They've helped tremendously -- and the screencasts make excellent entertainment while I'm running.
Are you still planning an Obj-C 2.0 book? Or has this morphed into the iPhone book?
One thing I think your materials do better than anyone else's is to explain the why, rather than just the how, which is particularly important for people, like me, who are new to programming, in general. Watching you write code in screencasts and seeing you work through the process is invaluable.
I'd really like to see more on intermediate topics, like bindings, array controllers, the responder chain and Core Data. Interacting with AddressBook and iCal would be good, too.
I'd also like some more information on random things that seem to fall through the cracks, like naming classes and variables (do class name really need to start with a 2-3 letter custom code to avoiding conflicting with Apple? Should I be prefacing iVars with _ or iVar outlets with 'o' and methods with 'm'?), deciding on a variable's scope, how to structure a class and how to compose a custom class created by using several layers of custom classes -- architecture-type stuff.
Finally, I'd be interested in seeing whether you have any tips for hanging onto and passing instance references through view and window controllers. I think this ties in with the responder chain to some degree, but I'm trying to write an app that uses a single window and many view controllers and trying to keep track of an instance of, say, an array controller, instantiated in the NIB file gets tricky when I'm a few view controllers removed from it.
One suggestion would be a Core Data app for photos, with three different views showing the same data -- a table view, an IKImageBrowserView and a cover flow view. The views are switched by a segmented cell and whatever filtering or sorting has been applied by the user in one view applies to all three as the user switched among the views using the segmented cell. Adding menu item validation and keyboard shortcuts would be a plus.
on January 28, 2009 at 05:38 PM MST
Thanks for the great materials.
I'd like to see more on KVO/KVC, the responder chain, array controllers, dictionary controllers, outline views and bindings. Screencasts on integrating Addressbook and iCal would be great, as well.
I also posted this on the iPhone book forum. Apologies for the double post, but I wanted you (and others) to notice this.
I wrote a tool that takes the content of one project, and merges it with another project. I think this can be useful for iPhone development, because we’re not allowed to do internal frameworks, and setting up external static libraries is a mess.
The tool is on GitHub, with complete instructions for using and extending it - http://github.com/costan/zerg_xcode
With my tool, the library provider would have an Xcode project, with all the files tucked away nicely under one folder and one group. Then the consumer would download the library somewhere, then “zerg-xcode import” from the project file. The targets and files would be inserted in the consumer’s project, and the files would be copied on disk as well.
Why would you want multiple targets in a library? I have a static library with the functionality, another static library with helpers for the consumer’s automated tests, and an iPhone app with automated tests for everything above.
I'm wondering if you can help me get some visibility for the tool. I think it would be useful to people who want to share code among projects.
on February 28, 2009 at 10:59 AM MST
Have watched the Objective C 2.0 screen cast and have recently purchased the ones on iPhone topic. I was wondering if you had any plans on a screen cast for making games?
on March 20, 2011 at 06:31 PM MDT