On 24/05/2011, at 11:49 PM, Joanna Carter wrote:
> I would definitely argue that this kind of design is not really "cleaning up"
> the design but, further, polluting it :-)
>
> In the Cocoa world, the Controller is a very important part of getting the
> non-UI code to connect to the UI element
Hi Graham
> Of course I'm simplifying when discussing MVC - I have rarely found a case
> that's "pure" in the sense of just M, V and C as well, usually there are
> several layers of controller and the data model is distributed among
> different objects as well. I felt the game example might be
On 24/05/2011, at 3:05 PM, Quincey Morris wrote:
> On May 23, 2011, at 18:27, Graham Cox wrote:
>
>> Am I worrying too much? Or is there a better way to think about layers that
>> means I don't have to give up on strict MVC?
>
> I'll take a stab at this -- not pontificating, just expressing an
On May 23, 2011, at 18:27, Graham Cox wrote:
> Am I worrying too much? Or is there a better way to think about layers that
> means I don't have to give up on strict MVC?
I'll take a stab at this -- not pontificating, just expressing an opinion, and
a hesitant one at that ...
There's nothing *i
Hi all,
I haven't done anything with Core Animation so I'm belatedly trying to learn it.
As a controlled environment to do this, I've written a simple game app that
implements the old 'dots and squares' game. First I did this in a classic
manner using a custom 'static' view to draw the board, n
