> If you you want to use the 'action' concept in your model AND want to use > something that still can be called MVC , yes, in general you will need to > implement in your model entities the methods needed by action operation (the > 'action execute interface' if you want, that comprises 'do', '_step', > 'pause', 'resume', 'remove_action').
Okay, I went ahead and did this. I was surprised how easy it was. I basically just copied the do, remove_action, and step logic to a new "ActionDoer" class and set that as a base class (along with EventDispatcher) to my Entity class. It's working great so far. > In retrospect, that interface could have been defined as a subclass, to be > inherited by CocosNode and, should the developer wanted, the model objects. Given my quick work with my "custom" ActionDoer class, I'd say this would be pretty simple. You wouldn't even break backwards compatibility, since you'd just be breaking out some logic and adding a base class to CocosNode. Thanks! -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cocos-discuss?hl=en.
