You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OTIO classes like Composition and Item can be wrapped in Java interfaces or abstract class instead of classes to make it explicit that they are not to be used directly, but through subclasses. If there's any useful logic in these base classes we can provide default implementation in the interface as shown here.
The text was updated successfully, but these errors were encountered:
KarthikRIyer
changed the title
Wrap OTIO base classes in Java interfaces instead of classes
Wrap OTIO base classes in Java interfaces or abstract class instead of classes
Sep 4, 2021
@reinecke classes like Composition and Item have functions which do not have an implementations and should be subclassed for actual use. In the python bindings why don't we make them abstract methods?
Is there any situation where someone would use Composable, Composition, Item, SerializableObject, SerializableObjectWithMetadata directly?
OTIO classes like Composition and Item can be wrapped in Java interfaces or abstract class instead of classes to make it explicit that they are not to be used directly, but through subclasses. If there's any useful logic in these base classes we can provide
default
implementation in the interface as shown here.The text was updated successfully, but these errors were encountered: