mrtrizer / flappyengine Goto Github PK

Now z-sort is call every render. To avoid this, I can keep Views in order until they are changed.

You can subscribe to Connected/Disconnected and Update methods in constructor of Component.

Such component will simplify code of emiting event from View to Controller.

• Window name and size for GLUTMgr
• Define list for all targets

Take a look at SpriteComponent and other view components.

It's useful field for engine tests.

For example:
config.json

"name":"Flappy",
"defines":["RELEASE"]

config_debug.json

"defines":["DEBUG"]

Than command flappy prebuild cmake debug will give you next result:

"name":"Flappy",
"defines":["DEBUG"]

Consider this

Grayscale
GrayscaleAlpha
RGB24
RGB32

This should solve problems with object transport. Entities become untied of EntityManager.
When entity is added to EntityManager hierarchy and get access to ManagerList, we should send a Connected event to connected subtree. Optionally we can also pass managerList in this event. When subtree is disconnected, all children get Disconnected event. Presenter components use this events to create/remove renders.

SomeComponent::SomeComponent() {
   on([this](Connected e) {
       ...
   });
   on([this](Disconnected e) {
   });
   on([this](Update e) {
   });
}

(I realised that such code can't work, because all components of entity will get this events at same time. Thus I can't call Connected event on component creation.)

Also this code can be placed in Component base class and usual virtual connected()/disconnected()/init() methods could be called.
Finally, this approach can help us to simplify entity-component tree.

To provide necessary methods for entity manipulation, we can create common parent class for EntityManager and Entity.

About memory safety. We can create temporary entity for component in Component constructor. So we can use entity() method in component constructor without crashes. This temporary entity will be removed when component is added to another entity. If programmer added some components to temprorary entity they also will be removed.

Would be cool to create TypeId class, containing base class id apart of id itself in order check it on assigning and in TypeMap.

May be even move IResFactory class to a separate file

New name better describes purpose of the class. It contains sprite rect in atlas and sprite size.

Something simple and flexible. Remember how it's hard to debug box2d raycasting.

Kinda of: {!name|DefaultName!}

Idea for names:

1. Utils
2. UnitTests
3. EventBus
4. Core
5. GraphicsRes
6. OggRes
7. JsonRes
8. BasicComponents
9. PosixCore
10. GUI
11. OpenGL
12. OpenAL
13. Sdl2
14. Box2D
15. RenderManagment
16. ResManagment
17. Text

It's useful for internal engine tests.

May be even use abstraction to support future physics engines.

Check complex dependency cases.
Check component dependency.

After little exploration I found a solution. For compilation to HLSL and MSL I could use glslang + SPIRV-Cross. So, seems, I need not worry about this currently and just continue work with GLSL.

1. Install glslang https://github.com/KhronosGroup/glslang
2. Build https://github.com/KhronosGroup/SPIRV-Cross
3. Compile GLSL to SPIR-V binary representation with glslang.
4. Map SPIR-V to HLSL or MSL

Fragment shader compilation from GLSL to GLSL ES and HLSL:

glslangValidator -H -V -o test.spv shaders-hlsl/frag/basic.frag
./spirv-cross --hlsl-enable-compat --hlsl --shader-model 51 --entry main test.spv
./spirv-cross --version 310 --es test.spv

Could be useful to use in exception throwing.

This will solve problems with object depending.

Also rename View to Render

Camera should be able to render into a framebuffer. Framebuffer should be accessible as a texture.