Emmanuel

[Renderers] Add ability to negotiate capabilities with the renderer

8

If the renderer is incapable of showing 3D textures, or drawing specific elements, like some colors (for example monocrome interfaces), clay should be able to take that into account, and...

[Renderers/Terminal] Add initial implementation of terminal renderer

1

This is an initial approach to the terminal renderer. Its pretty bad, it does not take into account the "real" pixel size of the terminal, just the character size. Fixes...

[Debugger] Expand warnings to include UI linting

1

A check pass should be done when in debug mode, and warn about unclickable buttons (culled out), invisible text (background is too similar to text), window elements that are too...

Add OpaqueFunction to list at docs.ros.org

3

Searching for OpaqueFunction in docs.ros.org/en/rolling/p/launch I find nothing, it should be added: https://docs.ros.org/en/rolling/p/launch/search.html?q=OpaqueFunction&check_keywords=yes&area=default

Raylib example broke

7

The raylib example is broken and doesn't scroll 

[Renderers/Raylib] TYPE_NONE not handled in the raylib renderer

5

I just got "Unhandled command type." for raylib renderer for command "CLAY__ELEMENT_CONFIG_TYPE_NONE". My layout is just a rectangle: ``` Clay_RenderCommandArray CreateLayout() { Clay_BeginLayout(); CLAY_RECTANGLE({ .color = {255,255,255,0} }); Clay_RenderCommandArray renderCommands...

[Examples] Create a standard test of functionality

3

Please create a standard test of functionality for implementing the renderer. Something that uses all features, and "proves" the renderer works. It should probably be nice looking.

Add related gazebo version to library APIs

5

Add related gazebo version to library APIs. For example, here is the sidebar for Gazebo sensors:  Tentative proposed change: 

Alert and link to newer library versions for API like ros2 docs

3

Gazebo docs doesnt link to newer versions for its API. See for example https://gazebosim.org/api/sensors/7/custom_sensors.html, which doesn't let you know that https://gazebosim.org/api/sensors/9/custom_sensors.html is the last version of the same page.

Here it uses "alwaysOn" tag: https://github.com/gazebosim/gz-sensors/blob/8aff340be1c422e2898964c1ba62864c047fccb6/test/integration/imu.cc#L46 But the correct tag is "always_on". In fact, gazebo throws a warning: ``` Warning [Utils.cc:132] [/sdf/world[@name="gnss_world"]/model[@name="model_with_sensor"]/link[@name="link"]/sensor[@name="imu_gnss"]/alwaysOn:/root/gnss_sim/imu_gnss.sdf:L242]: XML Element[alwaysOn], child of element[sensor], not defined in...