Forging the Core 1/??

Hello :)

Today I will talk about what I'm currently working on, the "Core" of the engine.

Right now, to do the "base" of thing and have quickly something to test on, I was working with 2 distinct parts:

- The UI
- The RTP (RealTime-Preview)

This is good to quickly try thing, but this is it, appart for testing, this is a very bad way to do thing. So for the last days I worked, and I'm still working on, the Core of the engine.

The "Core" is the brain of the engine, it will not be seen by the user, but will manage everything, then the UI and RTP will communicate with the Core to get / set data. One of the main point of why I'm doing this is maintainability. Because before the Core, when I wanted to add something in the engine, I needed to work on it on the UI part, then adapt it to the RTP, the UI part could communicate with the RTP, but not the other way around, ...

With the Core, I will be able to work on it with the Core, then make some little change on the UI and the RTP, in fact it will be way more logical like that:
- The UI part manage only the UI
- The RTP part manage only the RealTime-Preview
- The Core part manage everything else

With that, this will allow me to more easily work on the plugin system, but this will come later on :)

For now I already adapted the loading process of asset, for now only Tilesets, but let me tell you: This is way more easy and maintainable ;)

Note: The delay of the display of the test tileset is normal, it's not due to lag / slow process, it's to allow me the time to switch to the right tab!

Have a good day, I will return to work right now,

Ward.