Since different artists collaborating on a project will likely need several starting points (or the same artist might need them as well when working on different parts of the project), having support for that would be helpful.
To minimize effort for the artist when working with them, I suggest that a dropdown menu be added near the "Run Project" button, which enumerates available entry points, and persists the chosen point during Blender restarts / recoveries.
For the implementation I suggest mimicking pytest. Entry points shall be functions in main.py with names that start with entry_, so that they can automatically be recognized and listed in the dropdown menu. Alternatively, methods of the GameApp class, likewise starting with entry_ could be used instead. On running the project, the chosen name can be passed as a command line argument, and the method, if specified, be called at the end of GameApp.__init__().
Since different artists collaborating on a project will likely need several starting points (or the same artist might need them as well when working on different parts of the project), having support for that would be helpful. To minimize effort for the artist when working with them, I suggest that a dropdown menu be added near the "Run Project" button, which enumerates available entry points, and persists the chosen point during Blender restarts / recoveries. For the implementation I suggest mimicking pytest. Entry points shall be functions in
main.py
with names that start withentry_
, so that they can automatically be recognized and listed in the dropdown menu. Alternatively, methods of the GameApp class, likewise starting withentry_
could be used instead. On running the project, the chosen name can be passed as a command line argument, and the method, if specified, be called at the end ofGameApp.__init__()
.