Open FelipeDefensor opened 4 months ago
@azfoo
Implementing this on the web app we is proving to be easier that I thought. Thanks for suggesting we do that now.
We need to de3cid if we will store the component times as differences from the absolute start or the relative start. I'm leaning towards the first option, because they will remains invariant if the user decides to change the relative start. The downside is that conversion will be needed to display those properties to the user, as seeing the relative times is probably what the user wants.
That sounds sensible. Perhaps we could have a global converter for displaying timestamps the user will see? The other issue is imported timestamps from .csv files - maybe a flag somewhere that states if it is absolute or relative?
That sounds sensible. Perhaps we could have a global converter for displaying timestamps the user will see?
Agreed.
The other issue is imported timestamps from .csv files - maybe a flag somewhere that states if it is absolute or relative?
I prefer to expose the absolute time only when the user needs to set the effective boundaries. Besides that, I say the user always interact with the relative time, as I can't see a use case where the absolute time would be needed. After all, the components must all be inside the effective boundaries.
That reminds me that we need to add a command in the CLI to set the effective boundaries.
That's fair. I'll start work on this.
@azfoo I have finished implementing this on the web app. Can I help you with the desktop implementation?
Edit: Actually, I forgot there are other important tasks that need adressing in the web app. I will let you know when I'm done with them.
First, some terminology: let "absolute start" be the start of the media file and "relative start" be the start point the user chooses. Analogously for "absolute end" and "relative end".