Richard Lord

That sounds like a good idea. You'll want reference counting on the collections in case multiple systems use the same collection.

I added a method to clone an entity in my fork of xember. I figure it's the first step towards prefabs. Please pull it if you like it.

In the asteroids example I use a gun component to represent the gun on the spaceship. I can imagine a situation where the spaceship has two guns, pointing in different...

Despite the example I gave, I'm not convinced this feature should be included. On the face of it, it looks simple. If an entity has two Gun components, and a...

Hi Ian Based on your diagram, you don't just need two RenderingComponents on your entity, you also need the entity manager to know the difference between them because you need...

I wasn't saying that your internal mapping solution wouldn't work, but that simply allowing multiple instances of a component, which is what this thread is about, wouldn't solve the problem....

The shared components are components of both entities. They can be accessed from either component. They are the means of managing the entity-entity dependencies. Entities don't know about each other,...

Mike As you know, the architecture of your system is very different to Xember. In Xember, components are simple value objects, entites are just containers for components, and systems process...

Ian 1. Perhaps holding a collection of renderers in a component isn't the correct solution to the problem you express. I actually said in an earlier post that I think...

Hi. I've not seen this before, are you able to provide an example? The textures are made by first creating a bitmap (in the BitmapCreator class) and then combining them...