Karakara | Karetro
New member
Hello!
In some of the help threads, occasionally I come across someone saying how it is very possible, and easy, but it is hard to expose the front end of NesMaker.
To allow more flexibility, I would recommend giving the majority of menus XML support, In addition to some form of way to edit things adding more special screens, choosing how the background ppu is used on certain levels ECT.
By implementing XML, users could easily add in new functionality to NesMaker with little modification to the source code.
For example, if they wanted to add the ability to change the acceleration for an entity when they are in a given action, you could add that as something that is checked in the entity handling code, and then add in a slider for it with XML.
I have seen a good amount of tools use this technique to make their tool more modular.
Of course, this definitely does not have to be a priority, it just is a good insight.
In some of the help threads, occasionally I come across someone saying how it is very possible, and easy, but it is hard to expose the front end of NesMaker.
To allow more flexibility, I would recommend giving the majority of menus XML support, In addition to some form of way to edit things adding more special screens, choosing how the background ppu is used on certain levels ECT.
By implementing XML, users could easily add in new functionality to NesMaker with little modification to the source code.
For example, if they wanted to add the ability to change the acceleration for an entity when they are in a given action, you could add that as something that is checked in the entity handling code, and then add in a slider for it with XML.
I have seen a good amount of tools use this technique to make their tool more modular.
Of course, this definitely does not have to be a priority, it just is a good insight.