Re: Mild Rant (was: make that dataSource...)
Re: Mild Rant (was: make that dataSource...)
- Subject: Re: Mild Rant (was: make that dataSource...)
- From: Lloyd Sargent <email@hidden>
- Date: Wed, 12 Sep 2001 22:24:30 -0500
<mild rant>
Trying to introduce people to Cocoa, this is a big problem I see:
NEXTSTEP/Openstep/Cocoa was/is the
best GUI application framework I've ever seen; arguably it's the best
one ever written.
I think you will get few arguments on that! <grin>
The major
impediment to an explosion of amazing apps is that you have to be very
smart,
Mmmm... I disagree, you don't have to be that smart. Even I managed to
figure a few things out on my own (threads were a piece of cake - now
distributed objects, that was another thing all together, but way cool!).
and have access to
other smart people
THAT helps for us "not so smart" folks <grin>. I'm thinking of changing
my middle name to RTFM.
and ask them the right questions in the right order to get up the hill
such that
you're able to really leverage just how powerful and well designed
Cocoa is.
Or have enough time to do it the wrong way to figure it out. But, for
the most part I will agree with you to the need for access. Love this
list.
I was there with
NEXTSTEP, I sat out the Openstep stuff, but I'd like to get back in
there for Cocoa, and am
interested in figuring out how to get more people to come along with me.
We are, we are, we just need more books (and complete docs) with
examples so we don't keep bugging folks like Ondra (who seems to respond
to every e-mail one HAS to wonder when he gets any work done). I think
right now THAT is the biggest thing that is hurting Cocoa.
One of the points of putting classes on IB palettes is so that people
can use them with a minimum of
understanding - they should be able to drag an instance off a palette
and immediately use it - not
have to read header files, not have to read README files, not have to
be a terribly sophisticated IB
user.
A noble goal, but unless I can read your mind, how do I use the object?
Unless you are duplicating functionality of something else (only
different <grin>), I do not see the ability to "intuitively" use an
object. But perhaps I misunderstand what you mean...
Ideally, though, once they do become more sophisticated, and read the
README (or eventually
the header file :-)) they shouldn't have to switch over to a whole new
set of objects to utilize
these ideas - they should ramp smoothly up to the next level.
</mild rant>