On 22.05.2008, at 00:58, Rua Haszard Morris wrote:
1 Apple's docs, particularly in relation to Objective-C & Cocoa,
have some room for improvement:
- e.g. navigation (can't go back to list of methods after clicking
a method name hyperlink for example)
- lack of and generally un-useful sample code
Well, there are tons of samples. However they are scattered and if you
don't need you need MagicFoo, you cannot use google to locate MagicFoo.
And some people work on the road, sometimes without constant google
access. I prefer for conceptual work to move to a 16th century
monastry and sometimes can not prototype my ideas because some
required samples that take conceptual doc role didn't make it yet to
my harddisk...
2 Cocoa requires you when learning to implement things by clicking
and dragging, which makes learning harder for some people (this is a
real annoyance to me, why can we not see/edit these connections in a
text file? why is there so much other crap in the nib xml? etc).
That's only part of the issue. The sample code - the part one can read
up - is only part of the equation.
The setup, implicit code graph etc. is hidden in the nib and usually
completely undocumented.
There is the outline view depicting in Interface Builder the object
interconnection.
However, Interface Builder bottom line fails to provide an good
overview of the NIB innards to navigate to points of interest:
- an overview for bindings
- small badges a view has associated bindings, core animation
properties and IB connections.
Regards,
Tom_E
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
