Skip to main content
edited tags
Source Link
user1430
user1430

I am currently working on an iOS project called Old Frank that I have been trying to follow a MVC design pattern.

The gist of it is.

GameObjects(model) <- Scene(controller) -> Sprites "SpriteKit" (View)

GameObjects(model) <- Scene(controller) -> Sprites "SpriteKit" (View)

Now if I understand MVC correctly you can't use a lot of the features that SpriteKit has to offer if you want to follow MVC. For instance any SKActionSKAction, collision detection, etc.

Isn't it up to the model where game objects are located and how they should react when touching other objects? Isn't it up to the model to determine location over time?

Are there any parts of SpriteKit that would be considered ok tookayto use as the "View" of"view" in MVC other than rendering?

I am currently working on an iOS project called Old Frank that I have been trying to follow a MVC design pattern.

The gist of it is.

GameObjects(model) <- Scene(controller) -> Sprites "SpriteKit" (View)

Now if I understand MVC correctly you can't use a lot of the features that SpriteKit has to offer if you want to follow MVC. For instance any SKAction, collision detection, etc.

Isn't it up to the model where game objects are located and how they should react when touching other objects? Isn't it up to the model to determine location over time?

Are there any parts of SpriteKit that would be considered ok to use as the "View" of MVC other than rendering?

I am currently working on an iOS project called Old Frank that I have been trying to follow a MVC design pattern.

The gist of it is.

GameObjects(model) <- Scene(controller) -> Sprites "SpriteKit" (View)

Now if I understand MVC correctly you can't use a lot of the features that SpriteKit has to offer if you want to follow MVC. For instance any SKAction, collision detection, etc.

Isn't it up to the model where game objects are located and how they should react when touching other objects? Isn't it up to the model to determine location over time?

Are there any parts of SpriteKit that would be considered okayto use as the "view" in MVC other than rendering?

Tweeted twitter.com/#!/StackGameDev/status/581719099912429568

Do features of Does SpriteKit follow the MVC pattern?

Source Link

Do features of SpriteKit follow MVC

I am currently working on an iOS project called Old Frank that I have been trying to follow a MVC design pattern.

The gist of it is.

GameObjects(model) <- Scene(controller) -> Sprites "SpriteKit" (View)

Now if I understand MVC correctly you can't use a lot of the features that SpriteKit has to offer if you want to follow MVC. For instance any SKAction, collision detection, etc.

Isn't it up to the model where game objects are located and how they should react when touching other objects? Isn't it up to the model to determine location over time?

Are there any parts of SpriteKit that would be considered ok to use as the "View" of MVC other than rendering?