Re: "Tricks" of the "Trade"
Re: "Tricks" of the "Trade"
- Subject: Re: "Tricks" of the "Trade"
- From: Erik Thorteran <email@hidden>
- Date: Thu, 7 Jun 2001 21:13:04 -0700
Erik,
I don't think the problem is so much one of "bad habits" (though I
could
be wrong---I've heard that a habit only takes about 30 days to
develop). I
suspect the issue is one of mind-set, or, rather, programming/design
paradigm.
What exposure have you had to Object Oriented programming/design?
Have
you had experience with other languages that, at least, claim to be
Object
Oriented (or Object-like, or object-something)? Have you read
"Object-Oriented Programming and the Objective-C Language" (at
<http://Developer.Apple.com/techpubs/macosx/Cocoa/ObjectiveC/index.html>
[HTML] and
<http://Developer.Apple.com/techpubs/macosx/Cocoa/ObjectiveC/ObjC.pdf>
[PDF])? If so, do you feel you understand the concepts of Objects and
Object
Oriented used therein?
I must admit, I did have a passing acquaintance with SmallTalk
before
learning Objective-C, but that was really nothing more than reading the
SmallTalk 80 article in Byte magazine oh so many years ago. (It was
after I
knew Objective-C that I learned that there is oh so much more power
available
in SmallTalk, but I wont go into that now, or the fact that I have more
recently learned about the even greater power of TOM [either of which
would
be great replacements for, or supplements to, Objective-C {only loosing
the C
compatibility}].)
I think we can help, especially if you have read the above
reference, but
be prepared, it is a different way of thinking about programs (and,
hopefully, as you continue to learn about programming during your life,
you
will learn that there are /many/ different ways to think about
programming---many different, and valid, paradigms---don't ever get
stuck
into thinking that any one way is the only /true/ way).
David email@hidden
P.S. Feel free to present the difficulties you've been having with
making
classes work. Maybe having a more concrete case to work with will be
more
helpful to you. Everyone learns new things in different ways. Some can
"grock" the abstract and theoretical. Others need things to be more
concrete
and actual.
Really the trouble I have is interfacing with the UI, I can make classes
that do one simple thing (like a boolean wrapper or class for use in
another thread) but the trouble comes really when I try to use multiple
nibs and classes to interface with the user. They just cannot seem to
connect to each other if they are in another class. My biggest project
has one mega-class with 10-odd categories, and a workhorse thread
class. Really It is just putting the knowledge to use that is the
problem. Also, it does not make sense to me to subdivide this
mega-class because it is so tightly-woven, and between class method
calling is hard if they don't know about each other.
Erik