rohdesamuel / cubez Goto Github PK

This should create a global resource manager where resources can be identified by user strings or ids. The resources should be scoped to the current scene or the global scene.

In order to have a more useful GUI system, it would be helpful to have scene management. In this way, a user will be able to code different scenes with components, entities, and resources attached. This is useful for having different menus and levels.

• Rendering
• User Input
• Logging
• GUI

Example has hard-coded trigger for the logging event, it would be nice to have this in the API.

Use cases are:

• Linearly stateful functions
• Callback handling
• Background resource loading

Once an event is flushed, it stops any new events from being executed. This may or may not hamper a user's ability to write succinct code.

All programs are executed synchronously and would be more efficient to be asynchronous.

Events are currently not thread-safe for performance reasons. A new thread-safe event type called "qbChannel" should be added for inter-program communication. A work-around is to use components.