feasibility of commands.txt generation from OpenCV API?

[drzraf]

I wished someone already did this ten years ago (or would explain why its dumb in the first place).
For me it seems quite consistent and predictable (although mapping enum/constant/indirection may be painful) and could bring hundreds of handy OpenCV operations into the UI world in a matter of minutes.

Eg: https://docs.opencv.org/4.x/d6/d6e/group__imgproc__draw.html#ga0a165a3ca093fd488ac709fdf10c05b2

type	name,
InputOutputArray	img,
Point	pt1
Point	pt2
const Scalar &	color
int	thickness = 1
int	line_type = 8
int	shift = 0
double	tipLength = 0.1

Doxygen can generate XML
... which could later be merged with (unavoidable manual customisations), in order to (re)generate commands.txt

[ArthurDelannoyazerty]

For me I don't see the point of specifying a type for a variable. All we need to know to provide the user with is the range and step of this number.
The current command.txt file is long to write (so generating it could be nice), but when it's done, then we don't need to modify it, so what is the point for this change ?