Re: Why?
Re: Why?
- Subject: Re: Why?
- From: dave dowling <email@hidden>
- Date: Thu, 16 May 2002 12:33:56 -0400
i think you would do well to take the flaming offline. feel free
to email your personal grievances directly to me, where i'll choose
to address them if i feel they have merit. at least show the
courtesy of saving the rest of the listers from having to, as i
recall the expression in another RTFM post of yours, "scroll past
such messages in this list."
On Thursday, May 16, 2002, at 11:54 AM, Erik J. Barzeski wrote:
David,
free at last! how i found peace with God:
http://www.davedowling.com/steps.html
To further illustrate my point, it strikes me that I could not ask
you this
question and get a reasonable response:
"Why do you feel the need to include in your sig file a religious
item such
as this? What's the point?"
There are many good answers, of course, and I've heard many in my
discussions with my friends (primary among them being Seth Ellsworth
(www.sethellsworth.com), a musician and my best friend, and a devout
religious kinda guy), but I think you'd probably be reactionary,
accuse me
of being mad, or at least trying to "bait" you into some kind of
"argument,"
and run away, when really I would simply be trying to determine
what made
you do that (put it in your sig), as we are all on the quest for
truth, and
it's my current belief that neither I nor you have it, but some may be
closer than others.
That's a long sentence... Anyway, I would ask you, but your (in my
opinion)
childish response this morning has prompted this email instead. Don't
presume to tell me when I'm mad. I'm an intelligent guy, and if
others can't
or don't want to keep up with an actual intellectual conversation,
then they
need not. I had you pegged as someone who might. Guess I'll never
see you on
Crossfire or the O'Reilly Factor, then.*
* This one could be a bit incendiary, but I assure you, my blood
pressure,
heart rate, eye dilation, and body temperature are all normal (or
sub-normal, given that I have not yet had my normal
2-Cokes-by-noon), and my
intent is simply to continue to be honest and direct, "politness"
aside. If
everyone in the world was polite all the time, nobody would be able to
improve themselves. Criticism and insight are important. Of course
please
don't read that to mean I feel I'm being critical of you right now.
All of the above having been said, I really think no better or
worse of you.
I thank you for your help in solving the AppleScript issues
yesterday, and
though I doubt that you'll take me up on it, I'm always around to
chat or
answer questions. The point there being if I feel it's a waste of
time, I
can tell you that :) But most likely I'll have an example, and
think in the
back of my head "perhaps Cocoa Dev Central's search engine needs
improvement". So again, I think no better or worse of you, though
I have
checked off the "does not like to have discussions involving any
kind of
disagreement" checkbox in my mental profile of you, as fair or
unfair as
that may be. Hey, I had you pegged differently. I was wrong.
P.S. Cocoa Applications, the book that just came out, I recommend
to you as
a follow-up to Aaron's book. Just be sure to skip the first 200
pages :) I'm
pretty sure you know how to use the Finder... After that it gets
better.
BTW, the below is a great example (in my opinion, of course) of a
"newbie"
asking a question but demonstrating that he did some level of
thinking or
research on his own:
From: email@hidden
Date: Wed, 15 May 2002 23:58:47 EDT
To: email@hidden
Subject: 2 Cocoa Method Questions
This is from an experienced Mac developer, who is a newbie to Cocoa...
1) When creating non-document Edit/preference style window, what
is the best
method of handling the User Interface vs Content?
At WWDC, one apple engineer explicitly said that you should load
the User
interface when you need them (ie. opening window), and get rid of
it when the
window closes. Each window would have it's own Nib file. This
makes sense,
until you look at the Apple provided programming examples.
Several of the
programming examples load the UI in at startup (window in the
mainmenu.nib
file) with the window invisible, and use the controls on the window as
storage for the important data (ex. user defaults). This method
keeps the
window around (invisible), and uses the TextField, Sliders and such as
storage for the strings, integers and flags. Opening and closing
the window
is really a show and hide window function. The disadvantage to
this is the
memory that is being used up for invisible windows.
The alternative to this is loading the windows on the fly (and
disposed
when done), but keeping a copy of the important data in separate
NSString,
NSNumber, etc. When the window is opened, the current values
would be loaded
into the appropriate Controls. When the Controls change, their
values would
be handed off to the above mentioned NSString, NSNumber, etc. You
can see
this method is more complex (making sure the Controls & NSObjects
are in
sync) as well as taking more memory WHEN the Window is open.
Which method would you use?
I am using the example of User Defaults/Preferences for this
method, but it
really is talking about any non-document Window that sometimes is
open,
sometimes closed, and contains editable application data.
2) When creating new User Interfaces, and controller objects,
should you use
Project Builder to write the template of the controller you are
creating
(usually subclass of NSObject)? You would then run Interface
Builder, and
Read the .h file so that new class is available for Interface
Builder to c
reate an Instance of. When you want to add actions and outlets,
you add them
by hand to the .h file, and have Interface Builder re-read the file.
OR
Do you use Interface Builder to create a new subclass, add the
needed outlets
and actions using the Interface Builder UI, and then create the
.h & .m file
needed for this new object? You then load and compiled these new
files using
Project Builder.
As you can see, one example using Project Builder to create the
.h & .m file,
while the other method uses Interface Builder. The Interface
builder method
is better UI, and easier, but you cannot go back to add more
outlets/actions,
and keep any changes/additions you have added to code. Using the
Project
Builder method also seems to have some problems with setting up
.h & .m file
so Project Builder understand them (especially the new features
of not using
outlet & id classes, and being able to said a slider outlet is a
NSSlider
object).
The books and examples (and tutorials I seen) use both method,
but I am not
sure if it is just because some were written 2 years ago, vs.
recently.
Any comments?
Thanks!
Steve Sheets
--
Kindest regards,
Erik J. Barzeski
"Adults are obsolete children." - Dr. Seuss (1904-1991)
*******************************************************************
Email: erik@(anything below)
AIM: iacas ICQ: 8186546
http://barzeski.com/ http://weims.net/
http://techstra.net/ http://cocoadevcentral.com/
http://soundsetcentral.com/ http://applescriptcentral.com/
*******************************************************************
thanks.
dave dowling
free at last! how i found peace with God:
http://www.davedowling.com/steps.html
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.