RE: Swapping isa's (was Re: Hex Edit controls (resknife))
RE: Swapping isa's (was Re: Hex Edit controls (resknife))
- Subject: RE: Swapping isa's (was Re: Hex Edit controls (resknife))
- From: "M. Uli Kusterer" <email@hidden>
- Date: Wed, 1 Dec 2004 08:39:45 +0100
At 10:51 Uhr +1100 01.12.2004, Jeff Laing wrote:
You need a fairly high degree of familiarity with Interface Builders GUI
before you can be really productive, irrespective of what most people seem
to think. Yes, you can lay panels out without knowing what you are doing,
but thats not where you introduce bugs, its the inter-connectivity of GUI
objects (not to mention creating "instances") that are the hard details to
get exactly right. Accidentally break a connection (because you delete and
recreate a gui control) and your clue is a little yellow icon, which you are
ignoring anyway because thats actually going to be a reference to another
nib.
I've made up my mind not to sing my praises of Aaron Hillegass' book
here. Okay, IIRC he doesn't actually mention the list view widget
(and BTW -- I've filed a bug with Apple asking them to make it a
segmented control a la Finder, maybe you'll want to, too), but he
does mention how and why outlets work and also points out the
exclamation mark.
I'm not saying "I want to do it with code". I'm saying "I want it to be
verifiable by eye", by code inspection. Because Interface Builder is seeing
some sort of corruption in the file and just giving up - I believe I could
see the same corruption and stand a chance of excising it with a careful
knife (vi), which I've managed to do with Visual Studio.
YOu're aware that you can switch a NIB file to use XML as of 10.2,
right? I think it's named a little misleadingly, and can be set in
one of the tabs of the main window of any NIB file.
Switching from rant back to (hopefully) productive discussion, one thing I
noticed in the ResKnife code was that they chose to have a
HexWindowController, a HexWindowDelegate and three HexTextView entities. In
all the stuff I've done so far, I haven't seen a good reason to seperate the
controller from the delegate - can anyone give one, other than some
theoretical "it conforms to this pattern" ? One of the serious warts in the
ResKnife stuff to my eye is that there is still a lot of cross-talk between
the controller and the delegate, which seems to defeat the purpose of the
seperation.
Well, most of this is Nick's baby, and when I wrote my part of the
app, I was still starting out with Cocoa, so sadly I can probably
hardly do more than cringe at and apologize for some of the design
decisions I made, and defer to Nick regarding the rest. :-S
E.g. if I were to redo the template editor today, I'd probably use
NIBs, etc. Then again, I'm surprised how well it turned out back then.
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden