RFC: Feature Request: External Template Directory and Post-Build Script Support

[sidcha]

1. External Template Directory
Currently, the code template is stored within the EEZ Studio project file. I would prefer having the option to store this template in my source directory instead.

When configuring a project, in addition to specifying the output directory (where generated code is placed), users should be able to specify a template directory.

• On initial configuration, EEZ Studio would copy the default template code into this directory.
• After that, EEZ Studio should use the template files from this directory to generate the output code.

This setup allows users to:

• Check in the template directory to version control while ignoring the generated output.
• Track and manage custom modifications to the template more easily.

2. Post-Build Script Hook
It would also be helpful to support an optional post-build script that runs automatically after each build. This can be used to perform fixups or apply additional transformations to the generated code.

For example, I currently run a manual script to adjust display settings for a monochrome display:

sed -i 's/lv_theme_default_init(dispp, lv_palette_main(LV_PALETTE_BLUE), lv_palette_main(LV_PALETTE_RED), false, LV_FONT_DEFAULT)/lv_theme_mono_init(dispp, false, LV_FONT_DEFAULT)/g' screens.c

Having this automation built into the build process would greatly improve workflow efficiency and maintainability.