[issue:#111] Autosarzs Asset Generator

[mohamedashraf-eng]

Issue ID: #111

---

The Change is adding a tool utility called AssetsGenerator 2.0 for generating a file templates for the autosarzs developing and could be like custom autosar generator for the future.

[autosarzs]

There is 1000k plus files added to the PR, including python caches and other output files, can you please remove any generated files from the tool ?

And also i added a remark in the ticket #111 to explain more what exactly is the tool and a use case for it.

[autosarzs]

Code Review Remarks

1. Please remove any .pyc file in the branch
2. Please remove out folder
3. Please Remove dist folder
4. Please remove venv folder including pre-installed libs and and scripts

Notes:

• I see that it takes a lot of time equals to the same time for configuration the json file to include the interfaces for generating.
• The one config file will be huge if we decided to add other components to it
• The tool export the output into the same workspace of the tool
• The tool is having a lot of startup steps, user will consume a lot of time to configure a tool that might be more than the time needed to actually write the files.
• we are using devcontainers and makefiles, everything should be having one entry point to use any thing in the project

Summary

- This tool has a great potential but its not usable in its current state its missing the following

• CMake build system files generation as well as .c and .h files for the component
• easier way to configure the tool to generate the functions and parameters other than modifying the json file
• easier integration of the tool by setting one entry main target for executing everything.
• maybe we should think about generating executable for the tool if its require a lot of dependencies
• the tool should adhere to the current folder structure to add the component and also do the necessary steps for a complete component registration in the build system
• due to a lot of configuration and manual commands needed we might wait for a UI.

Recommendation and Refined DoD for the tool

• Input Run the tool with one command, add necessary info in the GUI in a fast convenient way
• Output Component is registered into the build system with necessary build files, building, and linked to the application

In that case, it would be great addition to also preserve one unifying style for everything and to avoid tweaks and different styles needed for different components

Thank you for taking time to present this awesome tool