This question comes up a fair bit, and a number of users are very interested in this.
There’s the possibility of adding a property interface where getters/setters are currently used. This would change the interface from:
x = node.get_transform().get_pos().get_x() text.set_slant(text.get_slant() + 0.1) if base.win.get_gsg().get_supports_shadow_filter(): texture.set_minfilter(SamplerState.FT_shadow)
x = node.transform.pos.x text.slant += 0.1 if base.win.gsg.supports_shadow_filter: texture.minfilter = SamplerState.FT_shadow
Thoughts? I’m willing to experiment with this and add properties as an alternative way, and eventually (Panda 2.0?) even phase out the getters and setters entirely in favour of a property-only interface.
There are some important examples where we can’t eliminate a getter/setter-like interface, such as NodePath, since methods like get_pos and set_pos do much more complicated things than setting a simple attribute on the class, and we can’t reduce this functionality down to a simple property-like interface.
There’s also the question of whether we should have camelCase alternative names for properties, the same way we support both getTransform() and get_transform(). I’m tempted to just have snake_case properties so that we can more easily phase out the camelCase() methods in the future, but I’m willing to yield if there is enough clamour for camelCase properties.