Frequented Links
Stand To Reason
Scripting News
ThoughtsOnFaith
Scobleizer
Joshua Allen
Steven Vore
Evan Williams
Bill Lazar
Steve Pilgrim
Joe Jenett
Ned Batchelder
J.D. Roth
Arnab Nandi
David Rogers
Matt Kennedy
Brian Cantoni
Mike Sax
Michael Geary
Nick Bradbury
Nick Hodges
Tommy Williams
Justin King
MooseNews
Greg Franklin
Family
Kim Fahrni
Jerry 'Jay' Fahrni
Lori Fahrni
Friends
Dan Albertson
Rick Wolf
David P. Cole
David M. Cole
Chris Roth
Richard Caetano
Steve Mitchell
Stuart Rawling
Tom Distler
Fat Penguin
Will Shattuck
Daved Kuns
Cass McNutt
Kevin Medeiros
Chris Edwards
Jon Davis
James Snell
Troy Sandal
S. Douglass Gilman
Tim Torian
Justin Stolle
Jim Hainline
Chris Hopkins
Ben Padilla
Robert A. Dodd
Misc. links
Heart of the Valley
The Great Valley
Downtown Visalia
City of Visalia
Kaweah Oaks Preserve
Movie Times
State of California
ThinkGeek Wish List
Upheaval
Web Dev Stuff
The Web Standards Project
Zeldman
Eric Costello
HTML Validator
CSS Validator
Development Stuff
Central Cal Developer's
Visio on MSDN
MSDN
C/C++ Users Journal
Got Dot Net?
Scripting News
FatBrain
CheezyPing
What I do
Pelco, Endura
I work at Pelco. The opinions expressed here are my own, and neither Pelco nor any other party necessarily agrees with them.
The Unofficial Apple Weblog: "Over at Theocacao Scott Stevenson has posted the video of his Introduction to Cocoa talk (entitled "Best of Both Worlds") aimed at those who want to learn a bit about Apple's preferred API for building OS X applications." - For later.
Labels: Apple, Cocoa, Development, Mac, Objective-C
comment
Cocoa Is My Girlfriend: "...in this post I am going to demonstrate a few things that can be done with NSError objects that have been received. Specifically, how to add options to an NSError and how to (hopefully) recover from one."
Theocacao: "The third edition of Aaron Hillegass's Cocoa Programming for Mac OS X is now shipping. I talked about it in some detail previously, but the summary is that this is one book I can easily recommend to new Mac programmers."
Both via Brent Simmons.
Labels: Cocoa, Development, Mac, Objective-C
comment
Cocoa Is My Girlfriend: "...in this post I am going to demonstrate a few things that can be done with NSError objects that have been received. Specifically, how to add options to an NSError and how to (hopefully) recover from one." Labels: Cocoa, Development, Mac, Objective-C
Theocacao: "The third edition of Aaron Hillegass's Cocoa Programming for Mac OS X is now shipping. I talked about it in some detail previously, but the summary is that this is one book I can easily recommend to new Mac programmers."
Both via Brent Simmons.
comment
Cocoa Is My Girlfriend: "...in this post I am going to demonstrate a few things that can be done with NSError objects that have been received. Specifically, how to add options to an NSError and how to (hopefully) recover from one." Labels: Cocoa, Development, Mac, Objective-C
Theocacao: "The third edition of Aaron Hillegass's Cocoa Programming for Mac OS X is now shipping. I talked about it in some detail previously, but the summary is that this is one book I can easily recommend to new Mac programmers."
Both via Brent Simmons.
comment
I've been exploring the iPhone SDK lately, it's been fun. I've finally figured some stuff out so it's really starting to get exciting. My "big" hurdle had been understanding how to take advantage of Interface Builder. I finally figured out how to hookup events now that seems pretty obvious, I knew that would happen, light bulb on, bing!
Here's a question for any Mac developers. Do people actually use the Interface Builder to design visually and hookup events, or do they draw the interface and hookup events in code, or do they build the UI all in code? I know, it's a strange question, and I'm sure I'll get a strange mix of answers, if any at all, but I had to ask. I'd love for Daniel Jalkut, or Brent Simmons to chime in.
Doing Windows C/C++ stuff for years had led to a certain expectation with Mac tools. In Windows I only used the graphical tools to create dialogs (at Visio we didn't even do that), then I'd go hook up event handlers in code. It was very straight forward and after using Interface Builder once I can see how easy it would be to hookup events in code instead of letting Interface Builder generate code for me.
I was very happy to discover a hunk of old C++ code compiled and worked like a charm when mixed with Objective-C. It was a pharmacokinetics library my brother and I created a long time back, and it just built and worked. That is a HUGE leg up for me. I can use my bad habit of writing C++ and slowly move into Objective-C. Very nice.
Next hurdle, gaining a better understanding of Objective-C.
It sure would be nice to build a Cocoa version of the Endura WS5000 software, hint, hint.
Labels: Apple, C++, Cocoa, Development, iPhone, Mac, Objective-C
comment
ars technica: "This is the second part of a three-part series describing how one developer became disillusioned with the Windows platform and was reinvigorated by the bright lights of Mac OS X." - Stash for later, I'm having a bear of a time getting used to "The Cocoa Way." Anything that'll help make that transition, I'm all for it. Currently my biggest problem is figuring out how to use Interface Builder and hooking up events so my code actually receives them. This is the most difficult platform change I've ever made. I've worked with a bunch of different platforms and frameworks and I've never struggled this much. Eventually the light bulb will go on and I'll be fine, for now I'm very frustrated with the entire exercise. Objective-C is pretty interesting and I'm sure will pose some problems for me, but I can only burn one bridge at a time, and that bridge is the Interface Builder bridge. More to come.
Labels: Apple, Cocoa, Mac, Objective-C
comment
Apple.com: "The groundbreaking innovations of Mac OS X Leopard and iPhone OS offer two revolutionary development platforms for developers and IT professionals. The Apple Worldwide Developers Conference (WWDC) is the only place you can receive technical information on these sophisticated platforms from the engineers who created them. Bring your code to the labs and work one-to-one with Apple engineers, applying development methods and best-practices you gain from sessions to enhance your application."
Labels: Apple, Cocoa, Development, iPhone, Mac, Objective-C
comment
Copyright © 2001-2008 Rob Fahrni
