On Sep 20, 2010, at 2:23 PM, Richard Somers wrote:
> On Sep 18, 2010, at 5:43 PM, Raleigh Ledet wrote:
>
>> Then you were not aware that if you can load a nib multiple times to create
>> multiple instances of the same view hierarchy.
>
> Correct. I did not know that you could load a nib multip
On Sep 18, 2010, at 5:43 PM, Raleigh Ledet wrote:
Then you were not aware that if you can load a nib multiple times to
create multiple instances of the same view hierarchy.
Correct. I did not know that you could load a nib multiple times.
Thanks for the info.
--Richard
__
On Sep 18, 2010, at 9:29 AM, Richard Somers wrote:
> On Sep 18, 2010, at 9:36 AM, Raleigh Ledet wrote:
>
>> Define "lots". 10 or 100? Generally, you create a nib for each view and you
>> programmatically load the nib with a view controller.
>
> Lots means 20 initially, up to 80 total later on.
On Sep 18, 2010, at 9:36 AM, Raleigh Ledet wrote:
Define "lots". 10 or 100? Generally, you create a nib for each view
and you programmatically load the nib with a view controller.
Lots means 20 initially, up to 80 total later on.
If variations are minor, then you can reduce the number of nib
On Sep 17, 2010, at 6:09 AM, Richard Somers wrote:
> The reason for the programmatic view is there are lots of similar views with
> minor variations between them. Having a programmatic view allows the objects
> in the view and the layout and configuration of those objects to be
> controlled fr
On Sep 17, 2010, at 10:25 PM, Seth Willits wrote:
It's hard to answer such general questions well, but I'll give it a
shot.
Whether the views are created programmatically or created by a nib,
the overall architecture of where controller code goes shouldn't
change, so having view controlle
On Sep 17, 2010, at 8:58 PM, Richard Somers wrote:
> My current inclination now is to change this and do all view composition,
> connecting, and binding in the controller. The root view would still be there
> but the controller would be doing most all of the work.
It's hard to answer such gene
On Sep 17, 2010, at 7:09 AM, Richard Somers wrote:
The reason for the programmatic view is there are lots of similar
views with minor variations between them. Having a programmatic view
allows the objects in the view and the layout and configuration of
those objects to be controlled from a
Consider the following architecture.
windowController
viewController
programmaticView
viewController1
programmaticView1
viewController2
programmaticView2
viewController3
programmaticView3
...
Each
