Nicer transform archetype interface in python

[Wumpf]

What

• Fixes It's hard to discover how to use Transform3D archetype #3528
  • plus as discussed TranslationRotationScale3D and TranslationAndMat3x3 datatypes no longer implement the as_components interface
• Need to patch up things in Port all Python examples to new APIs #3545

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested demo.rerun.io (if applicable)

• PR Build Summary
• Docs preview
• Examples preview
• Recent benchmark results
• Wasm size tracking

[Wumpf]

@jleibs is the exception throwing there in line and will be caught automatically? I'm a bit out of the loop with what we ended up with

Edit: Oh that's still all on #3531. I'll review it on Monday

[abey79]

This makes for such a nice API!!

Two things:

1. Maybe add a test to ensure exceptions are raised with incompatible args (with @pytest.raises(ValueError): ....
2. Maybe should shouldn't completely hide (or make non-obvious) that the "concrete" types (TranslationAndMat3x3, etc.) can be used as well. That could be added to the __init__ docstring, maybe, in a transform3d_explicit.py example?

[abey79]

May be an example section here would be good, as a way to list all supported combinations. This is going to be useful for the user, to avoid solving for constraints listed in the Parameter section

[Wumpf]

we generally have examples on the type documentation. I'm hesitant to add examples now and here and only for python.
"all supported combintations" may also be way too much

[abey79]

I agree this is not the place for a full on example, but something akin to this would still provide value IMO. It's much more explicit as to what the 3 general forms are.

# use one of the concrete transform data type, e.g.
rr.Transform3D(rr.datatypes.TranslationAndMat3x3)

# using translation and/or and 3x3 matrix
rr.Transform3D(translation=[...], mat3x3=[...])

# using any or all of the elementary transform components
rr.Transform3D(translation=[...], rotation=..., scale=...)

[abey79]

It could even be a bullet list without actual code.

[Wumpf]

Maybe should shouldn't completely hide (or make non-obvious) that the "concrete" types (TranslationAndMat3x3, etc.) can be used as well. That could be added to the init docstring, maybe, in a transform3d_explicit.py example?

I mean they're not really all that hidden, are they? It's the first parameter the method takes. But that said I could manually expand the type annotation to

        Transform3D |
        datatypes.TranslationAndMat3x3 |
        datatypes.TranslationRotationScale3D

but we also never do that in any other place, so I'm a bit hesitant

[abey79]

Maybe should shouldn't completely hide (or make non-obvious) that the "concrete" types (TranslationAndMat3x3, etc.) can be used as well. That could be added to the init docstring, maybe, in a transform3d_explicit.py example?

I mean they're not really all that hidden, are they? It's the first parameter the method takes. But that said I could manually expand the type annotation to

        Transform3D |
        datatypes.TranslationAndMat3x3 |
        datatypes.TranslationRotationScale3D

but we also never do that in any other place, so I'm a bit hesitant

Yeah, I don't have a very strong feeling about this. Also, I think my comment would largely address the visibility of these datatypes.