Guidance on Project Structure
Guidance on Project Structure
- Subject: Guidance on Project Structure
- From: Jeremy Dronfield <email@hidden>
- Date: Mon, 17 Jun 2002 11:10:25 +0100
I'm brand spanking new to Cocoa, and I'd like to know if anyone can
point me in the direction of some general guidance on structuring a
project. I've done most of the available tutorials (CocoaDev and Vermont
Recipes) and ploughed through the Developer documentation, but I still
feel bewildered about some elementary structuring principles which don't
seem to be addressed either by learning-by-doing or statements of theory.
1. What factors determine the choice of document-based or
non-document-based templates?
2. What factors influence the decision to add extra nibs to a project?
(I've looked at OmniWeb's package contents, for instance, and there are
no fewer than NINETEEN nib files in there.) And what methods can be used
to make them communicate with each other?
3. Similarly, the use of NSObject, NSWindowController (and other)
subclasses. Vermont Recipes has helped me understand how these can be
arranged and used, but I feel I'm missing a whole world of options to
suit different needs.
I've found none of these questions answered satisfactorily (or even at
all) in any of the material I've looked at, but feel there must be
something out there which guides newbies through these complexities
using theoretical explanation fleshed out with analysis of real-world
examples. If there isn't, why not? An opportunity for all you Cocoa
experts ...?
_______________________________________________
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.