o3de / o3de-extras

Other
61 stars 63 forks source link

Improve onbording experience with Ros2ProjectTemplate #246

Closed michalpelka closed 1 year ago

michalpelka commented 1 year ago
adamdbrw commented 1 year ago

Not only with this template: Please include generated code for Editor components / targets / module. Currently, if the user would like to add any Editor Component, their experience is quite difficult as they need to add cmake targets, define editor module, refactor out the components descriptors creation into module interface etc.

Please also make note of distinguishing project folder from project name. The latter is used to generate class names etc, it is best to make it CamelCase. See this part of instructions.

rainbj commented 1 year ago

Thanks, Joshua - Sig-UI-UX chair O3DE

michalpelka commented 1 year ago

@rainbj , Version is not a best word, better is variant e.g.:

""Add build dependencies and include them to ROS2 Gem." Does this have any UX with it?" We claim that Users can easily extend simulation with their ROS2 C++ code (our target here is robotics, system developers). Without those dependencies, this task is not that straightforward. You are right, for the end-user of simulation, it makes no difference.

michalpelka commented 1 year ago

All bullet points are checked. Closing issue. Good job.