Re: cocoa app from scratch
Re: cocoa app from scratch
- Subject: Re: cocoa app from scratch
- From: "Mark A. Stratman" <email@hidden>
- Date: Mon, 19 Jul 2004 03:59:15 -0500
On Jul 19, 2004, at 3:29 AM, Ihar 'Philips' Filipau wrote:
1. IB cannot update file which I already have modified - so I have to
do it manually anyway. So you cannot do it completely automatically
anyway. Switch forth and back from Xcode to IB just to add another
method to class as for overkill. I do it in couple of seconds by hands
without need to: i. switch to IB; ii. find its window; iii. switch to
classes; vi. locate class; v. right click to add method; vi, make up
parameters, vii. click to generate source code/whatever. All this
instead of in Xcode: i. type method in; ii. select it, switch to
.h/.m; iii. paste it; iv. Cmd-S. Done. So unvisual way has its
advantages too.
Bah, sounds to me like you're just not fully utilizing IB. :-p
Just have IB re-read the headers (click the classes tab, then hit
cmd+alt+r and select the files you've updated).
It will automagically recognize any IBAction methods and IBOutlets
you've added. No need for all that hassle you've described.
2. I want to see how it works - bit more academic, rather then
pragmatic approach you are argueing. But that find with me. I very
easily get lost on IB's windows, classes, properties, etc. Interface
is just not for me. And those trick that I need to go forth and back
from Xcode to IB to Xcode to IB to Xcode again is definitely doesn't
help.
I can understand hand-coding all your GUI controls for the sake of
learning. Don't let me or anyone else discourage you if that's your
goal. For any other purpose though, programmatically creating your
entire GUI is almost *always* a very bad thing to do, and a nightmare
for maintenance.
_______________________________________________
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.