I don't want to get a scripting language involved, because that creates a lot of extra complexity. First we would have to create a sandboxed scripting environment, then try to break the boundaries of the sandbox in as many ways as possible. Every time we want to add features to scripting we'll have to rebuild the engine, and a scripted engine tends to have builds distributed by an official source... me.
So instead, lets pull off the bandaid, and make rebuilding the engine a standard process of developing in 3gw. To make this easy, I would like to create standalone installers that equip users with gcc, make, and raylib. To start, I could put together a simplified set of instructions from the raylib project--those instructions show many different ways to build on each platform. In my instructions, I'll just show the way that I feel is easiest--and I personally don't use cmake.
Completing this issue represents a mental shift for 3gw. No longer will be it be reasonable for engine code and game code to all sit in the same place. I'll want to make a directory structure that allows the user to populate some folder with "behavior"-style C programs and possibly employ some variation of Entity-Component, like Unity (or look up a video about how Valve architected scripting in Source).
I don't want to get a scripting language involved, because that creates a lot of extra complexity. First we would have to create a sandboxed scripting environment, then try to break the boundaries of the sandbox in as many ways as possible. Every time we want to add features to scripting we'll have to rebuild the engine, and a scripted engine tends to have builds distributed by an official source... me.
So instead, lets pull off the bandaid, and make rebuilding the engine a standard process of developing in 3gw. To make this easy, I would like to create standalone installers that equip users with gcc, make, and raylib. To start, I could put together a simplified set of instructions from the raylib project--those instructions show many different ways to build on each platform. In my instructions, I'll just show the way that I feel is easiest--and I personally don't use cmake.
Completing this issue represents a mental shift for 3gw. No longer will be it be reasonable for engine code and game code to all sit in the same place. I'll want to make a directory structure that allows the user to populate some folder with "behavior"-style C programs and possibly employ some variation of Entity-Component, like Unity (or look up a video about how Valve architected scripting in Source).