Comments on: Working without a nib, Part 5: No, 3! http://lapcatsoftware.com/blog/2007/06/10/working-without-a-nib-part-5-no-3/ Coding under the close supervision of cats Fri, 09 Jul 2010 18:22:20 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Jeff http://lapcatsoftware.com/blog/2007/06/10/working-without-a-nib-part-5-no-3/comment-page-1/#comment-2288 Jeff Sun, 17 Jun 2007 21:31:16 +0000 http://lapcatsoftware.com/blog/2007/06/10/working-without-a-nib-part-5-no-3/#comment-2288 <p>I've reconsidered my opinion and written a new <a href="http://lapcatsoftware.com/blog/2007/06/17/working-without-a-nib-part-4-setapplemenu/" title="Working without a nib, Part 4: setAppleMenu" rel="nofollow">post</a> on this issue. I don't think that I'm jumping through any more hoops by using <code>setValue:forKey:</code> instead of <code>setAppleMenu:</code>, though. The two techniques are functionally equivalent; the latter technique doesn't automatically solve the other problems I've discussed.</p> I’ve reconsidered my opinion and written a new post on this issue. I don’t think that I’m jumping through any more hoops by using setValue:forKey: instead of setAppleMenu:, though. The two techniques are functionally equivalent; the latter technique doesn’t automatically solve the other problems I’ve discussed.

]]> By: Jack Nutting http://lapcatsoftware.com/blog/2007/06/10/working-without-a-nib-part-5-no-3/comment-page-1/#comment-2276 Jack Nutting Sat, 16 Jun 2007 06:28:20 +0000 http://lapcatsoftware.com/blog/2007/06/10/working-without-a-nib-part-5-no-3/#comment-2276 It seems like you're jumping through lots of hoops that could be avoided by just calling the setAppleMenu: private method that Joar suggested in part 1. You said you'd rather not use that in production code, but does your current strategy of relying on private ivars and undocumented behavior really seem *less* fragile? That being said, I'm enjoying reading about your investigations into the nether regions of Cocoa. Be careful out there! :) It seems like you’re jumping through lots of hoops that could be avoided by just calling the setAppleMenu: private method that Joar suggested in part 1. You said you’d rather not use that in production code, but does your current strategy of relying on private ivars and undocumented behavior really seem *less* fragile?

That being said, I’m enjoying reading about your investigations into the nether regions of Cocoa. Be careful out there! :)

]]>