Open
Description
Desired behavior
We should complete our Ruby scripting support for all classes. Now that we have SWIG -based Python interfaces for all classes, it should be quick to migrate them to Ruby.
We should also add tests for all classes.
Alternatives considered
Abandoning Ruby in favor of Python?
Implementation suggestion
It should be quick to port the existing SWIG files to Ruby. Adding tests will take longer.
The files live here: https://github.com/ignitionrobotics/ign-math/tree/ign-math6/src/ruby
Here's the status:
- AngleAxisAlignedBoxBoxColorCylinderDiffDriveOdometryFilterFrustumGaussMarkovProcessgraph/Edgegraph/GraphAlgorithmsgraph/Graphgraph/VertexHelpersInertialKmeansLine2Line3MassMatrix3MaterialMaterialTypeMatrix3Matrix4MovingWindowFilterOrientedBoxPIDPlanePose3QuaternionRandRollingMeanRotationSplineSemanticVersionSignalStatsSphereSphericalCoordiantesSplineStopwatchTemperatureTriangle3TriangleVector2Vector3Vector3StatsVector4
Additional context
This was broken off #101.
Activity
chapulina commentedon Dec 30, 2021
We're moving all the SWIG files that we had working for Python to the Ruby directory in #354, but we're not enabling them.
Now the work on this issue should consist of:
Adding each file to:
https://github.com/ignitionrobotics/ign-math/blob/5fa6f7858a873448c9fa09be23dafc99f0f8863d/src/ruby/CMakeLists.txt#L16-L23
Porting the existing test from C++ / Python to Ruby
Making any necessary adjustments to the SWIG file
azeey commentedon Feb 22, 2024
I would be in favor of abandoning Ruby in favor of Python.