Engine property set for GUI generation

[pkomon-tgm]

Different engine implementations might support different effects with different parameters (lets call them"properties"). It would be nice, if the app implementation could generically generate a user interface (using imGUI) for a set of engine properties.

• Engine properties are specified by the engine and exposed to app (i.e. in app something like engine.getPropertyList()
• App generates imGUI elements for each property

There might be properties that are also used by the app - this would be a set of properties that the app would require every engine to supply. For now, we can ignore this tho, because we couldn't come up with a use-case for this so far. We can just add it when we actually need it.

Things to be done:

• [ ] encapsulate engine property list, expose to app
• [ ] move imGUI to app (refactoring step)
• [ ] generate imGUI elements based on the engine properties

[GeraldKimmersdorfer]

Just thinking out loud: I've used a similar property implementation in two of my projects. It also allows for the extension of animations on those properties. Don't know if relevant for this project but it's cool.

Furthermore if they are somewhat generic it should be easy to implement those in different GUIs (QML, HTML, ImGUI)

[pkomon-tgm]

Perfect, then we can start off with your existing implementation and iterate on it whenever we need something not yet supported by it. It also depends on under what license you published your projects (but I guess we are fine here ^^)

Agreed, tho I think we should stick to ImGUI for now.