Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TimeRanges object abstraction #5

Closed
colthreepv opened this issue Oct 2, 2013 · 1 comment
Closed

TimeRanges object abstraction #5

colthreepv opened this issue Oct 2, 2013 · 1 comment
Labels

Comments

@colthreepv
Copy link
Owner

I thinked awhile about how expose TimeRanges structures, they are particular arrays explaining how much has been played, how much is seekable, and buffered.

The specific properties are:

  • buffered
  • played
  • seekable

The abstraction i had in mind is to put all those 3 arrays to an array of hashes like this:

playerControl.seekable: [
  { start: 0, end: 25 },
  { start: 51, end: 55 },
  { start: 99, end: 100 }
];

They are percentage-based and would couple well with an <input type="range"> element.
It's still under debate if it's worth to, or if there is a more clever/handy way to expose those informations

Comments are welcome

@colthreepv
Copy link
Owner Author

After consideration, this functionality seems to not add value, people using those structures will be usually experts that have read the MDN estensively so can convert the values to percentage by themselves.

As another point, make the library convert the values to percentages will put a considerable overhead, because those structures have to be manipulated every time a progress/timeupdate event gets generated.

Is already possible and will be possible to access the raw structures from your angular application, without Scope automagic binding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant