# How a "view" is handled in an Entity-Component based model?

Coming from an MVC background, I am trying to understand Entity-Component based model. However, i can see description about the use components( data objects ) and entities ( group of different data-objects ie components), but cannot see how view is created. I can see something called "render" components though. But how would i use it ? It seems, i don't need to bother about separation of view from data in this architecture. But i doubt, if this is the case, then things would mess up.

• This question probably can't be answered in a reasonable manner, TBH. There's no point in comparing MVC and CBES, they're trying to achieve different goals using different means. Just read the T=Machine articles with a clear mind and forget about your background. Jan 27 '13 at 16:59
• I agree with @dreta. (Also, are you dreta from the Crunchbang forums?) Jan 27 '13 at 17:46
• @Yannbane No, sorry. Jan 27 '13 at 18:34

There are a broad range of component-based entity systems, each of them handling this a bit differently, but the way I decouple drawing from data is to use Systems. A system is a class that takes data from components and works with them as a group. Some examples of systems would be a CollisionDetectionSystem or an AnimationSystem or, being the point of this question, a GraphicsSystem. The GraphicsSystem would be registered with each component, and they could pass in their data to the system.