The GUI requires a valid EDS python library to be present in order to run which is fine during a typical developer workflow. However, it can be an issue for the educational project workflows if the user makes a mistake.
For example, if the user selects an incorrect project component (e.g., the wrong library), the build will fail. If they have shut down the GUI then they can't restart it to fix the problem. If the project workflow is the typical situation when this occurs, then this could be made more robust. Some ideas...
Project packages could be defined that automate the project creation process.
Restarting the GUI could be prevented if a valid EDS python library is not present
The current EDS library could be saved prior to creating a project cFS target
The GUI requires a valid EDS python library to be present in order to run which is fine during a typical developer workflow. However, it can be an issue for the educational project workflows if the user makes a mistake.
For example, if the user selects an incorrect project component (e.g., the wrong library), the build will fail. If they have shut down the GUI then they can't restart it to fix the problem. If the project workflow is the typical situation when this occurs, then this could be made more robust. Some ideas...
This issue is related to Issue 12