Remove Legacy Code about engo

[EtienneBruines]

Can I ask what's wrong with Drawable, and how it should look instead?

[paked]

@EtienneBruines It fulfils the same purpose as Renderable, although... Perhaps we should use it... Renderable is quite ugly and relies on moving state.

[EtienneBruines]

@paked Using either one of those would indeed be better; as they both sound like they're doing the same.

[paked]

@EtienneBruines I personally think Drawable is the better design (not sure why I wrote it down then...)

cc: @matiwinnetou

[matiwinnetou]

very useful info, thx. Helps me to learn the current status of the project.

[paked]

@matiwinnetou Do you have any opinions on Drawable vs Renderable?

[matiwinnetou]

@paked At the moment sadly no, as I understand still too little the difference. In general, however, from my experience I can say that one should avoid state like fire. It is not always possible though or complicates code a lot. You mentioned that Drawable has no state where as Renderable assumes state.

In our ECS app, which believe or not is actually a web application. (We created own ecs-web framework in Java 8 we have even various Worlds, like ImmutableWorld, RequestWorld (mutable world), to make this separation clear. In our design worlds form a chain, where a world can have a parent attached.

[paked]

@EtienneBruines What about you? (Drawable vs Renderable )

[EtienneBruines]

I do think the Drawable is much clearer. Since there'll be a Shader for each PriorityLevel (which people can add themselves), all we need from whatever we want to draw, is the Texture, and size/location.

I have no idea what the View() (float32, float32, float32, float32) function is supposed to do though.

But I have no idea what's best-practice for ECS. I just think about what's easier to use/implement.