❔ Inheritance or composition?
For example, blender, C4D or any 3D modelling program would have a scene with a hierarchy of objects (e.g. cube, mesh, etc). These would obviously need a position associated with them... but would it be a better idea to use composition such that you have a
Another example that really made me think of this question is premiere pro, specifically video clips. Video clips are obviously going to have some sort of manually controllable position, and also a scale value (and an origin point to assist the scale). But the way premiere pro presents that data is in the effects panel as the "Motion" effect, making me think that internally premiere pro stores all that data in an effect instead of in the clip class or struct or however they do it. If they wrote it using C structs I could understand because audio clips don't really need a position. However if it were C++, would it not be a better idea to have
TransformationInfoAnother example that really made me think of this question is premiere pro, specifically video clips. Video clips are obviously going to have some sort of manually controllable position, and also a scale value (and an origin point to assist the scale). But the way premiere pro presents that data is in the effects panel as the "Motion" effect, making me think that internally premiere pro stores all that data in an effect instead of in the clip class or struct or however they do it. If they wrote it using C structs I could understand because audio clips don't really need a position. However if it were C++, would it not be a better idea to have
VideoClipObjectClipObject