This section: https://github.com/ihmcrobotics/ihmc-open-robotics-software-tutorials/wiki/Setting-Up-Your-Workspace, helps the user to setup a workspace to work with IHMC software stack directly from source, i.e. import the IHMC software directly in the workspace alongside the user's code.
The tutorials on the other hand show how to set up a workspace depending on the IHMC software stack via Jar dependencies, i.e. the IHMC software is not imported directly in the workspace, instead, Jars are added as dependencies to the user's code.
The distinction between these 2 modes isn't quite clear in the Wiki. However, the difference can be quite important, especially since depending on the IHMC software from source complexify the setup and increase computational load when compiling.
We may want to re-think the structure, because maybe it is working against us to clarify that. Maybe we'd want in the structure to have the 2 setup side-by-side which would help making it clear that they are different.
This section: https://github.com/ihmcrobotics/ihmc-open-robotics-software-tutorials/wiki/Setting-Up-Your-Workspace, helps the user to setup a workspace to work with IHMC software stack directly from source, i.e. import the IHMC software directly in the workspace alongside the user's code. The tutorials on the other hand show how to set up a workspace depending on the IHMC software stack via Jar dependencies, i.e. the IHMC software is not imported directly in the workspace, instead, Jars are added as dependencies to the user's code. The distinction between these 2 modes isn't quite clear in the Wiki. However, the difference can be quite important, especially since depending on the IHMC software from source complexify the setup and increase computational load when compiling. We may want to re-think the structure, because maybe it is working against us to clarify that. Maybe we'd want in the structure to have the 2 setup side-by-side which would help making it clear that they are different.
Let's talk about it at some point