usnul/meep

Entity Component System game engine

meep's Issues

Suggestions for making the code more accessible to new users

I'm taking a look through the code now, and it looks very clean and usable.

Two things that would make it even more accessible:

• seperate demo and engine code. That is, put demo code in /demo/src and engine code in engine/src
• In the absence of documentation, one or two line comments at the start of each file (or at least most important files). For example, ViewGroup - I'm guessing this is for organising visible objects into groups? It would be great if the purpose of this file was clearly stated at the top of the file. That would reduce the cognitive load of new users a lot as they get to grips with the engine.

For sure, if I spend even a day working with this engine these things will probably be obvious to me. But these changes would make me much more likely to consider using the code in the first place.

Meep engine need more examples?

hi usnul:
i follow you passerword on threejs.org i find that:
http://server1.lazy-kitty.com/tests
but we still no know how to use engine like test.
does that tests open source? maybe it more helper for newer to learn the engine meep .
^_^.

How to use Editor?

Hello, how to use editor?
I run npm run "start:dev" and just see a terrain demo, no any UI.

BVH creation time?

How long does it take to construct the BVH? Would it be usable for many meshes with ~100k vertices (constructed in a worker and allocated using SharedArrayBuffer if available)?

Its super cool that you implemented all this. It looks like a ton of work.

Status of this engine?

Any active development work goin on? It seemed to have a lot of promise but now seems to have stopped…