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

Shy preloading/activation #224

Closed
ghost opened this Issue Aug 30, 2013 · 5 comments

Comments

Projects
None yet
1 participant
@ghost

ghost commented Aug 30, 2013

If we have a lot of reel in the same page, it could help to limit to only the reel a user want to play.

Also, if the reel is a long sequence, we could only load the frames on demand to limit the number of frames loaded by turning preload off.

@pisi

This comment has been minimized.

Show comment
Hide comment
@pisi

pisi Aug 30, 2013

Owner

This kind of matches one of the next points on the site:

Explicit activation to lower the bandwidth cost when there's no action from the user.

Although on the site it says "implicit", "explicit" is the correct word ;)

I'm thinking about adding some Boolean option, which will enable "on-demand mode", in which it will begin the preloading process only after either image was clicked or an event is triggered. Does that sound good?

Owner

pisi commented Aug 30, 2013

This kind of matches one of the next points on the site:

Explicit activation to lower the bandwidth cost when there's no action from the user.

Although on the site it says "implicit", "explicit" is the correct word ;)

I'm thinking about adding some Boolean option, which will enable "on-demand mode", in which it will begin the preloading process only after either image was clicked or an event is triggered. Does that sound good?

@ghost ghost assigned pisi Aug 30, 2013

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Aug 30, 2013

This sounds pretty good! 👍

ghost commented Aug 30, 2013

This sounds pretty good! 👍

@pisi

This comment has been minimized.

Show comment
Hide comment
@pisi

pisi Aug 31, 2013

Owner

OK, so as this was fairly straight forward, is already merged into development branch.

I've added a new option shy, which by default is false and Reel initializes and preloads right away. When true on the other hand, it will just crack the surface with the initialization and won't trigger the setup chain of events thus effectively preventing the preload. It will wait for user to click on the image, which will trigger "setup" event and finish building and preloading the instance. You can of course trigger the "setup" event by yourself from wherever.

Have had a productive night :)

Owner

pisi commented Aug 31, 2013

OK, so as this was fairly straight forward, is already merged into development branch.

I've added a new option shy, which by default is false and Reel initializes and preloads right away. When true on the other hand, it will just crack the surface with the initialization and won't trigger the setup chain of events thus effectively preventing the preload. It will wait for user to click on the image, which will trigger "setup" event and finish building and preloading the instance. You can of course trigger the "setup" event by yourself from wherever.

Have had a productive night :)

@pisi

This comment has been minimized.

Show comment
Hide comment
@pisi

pisi Sep 12, 2013

Owner

Ready for release

Owner

pisi commented Sep 12, 2013

Ready for release

@pisi pisi closed this Sep 12, 2013

@pisi

This comment has been minimized.

Show comment
Hide comment
@pisi

pisi Nov 5, 2013

Owner

Released today as part of v1.3.0

Owner

pisi commented Nov 5, 2013

Released today as part of v1.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment