Create a Sequences.Register() to parallel the UI Pack #94
Labels
Comments
|
Agreed. The problem is figuring out the ideal syntax; I want to make sure that the syntax I use for call creation in the UI Pack is actually universally applicable. I'll think on this in the coming days. Thank you so much, Fredrik! |
julianshapiro
changed the title
julianshapiro
changed the title
|
Should be the next big addition ;) |
julianshapiro
changed the title
|
This issue is now part of issue #136. |
julianshapiro
added a commit
that referenced
this issue
Jul 3, 2014
Transition “out” effects don’t reset opacity to 1. This is the only default behavior change that has been made to the UI pack. Shouldn’t affect the vast majority of use cases. Performance improvements due to automatically forcefeeding all reset values. Fix reset timing bug in which reset occurs after user’s complete callback fires. Closes #132. Closes #129. Turned sequence registration into externally-accessible function. Closes #94. Closes #136. Added options customizability to calls. See http://VelocityJS.org/#uiPack.
|
This took a while, @frekw, but now it's here. Check it out (see Custom Effects): http://velocityjs.org/#uiPack. |
|
Cool! Thanks so much @julianshapiro |
Rycochet
pushed a commit
that referenced
this issue
Aug 3, 2020
Transition “out” effects don’t reset opacity to 1. This is the only default behavior change that has been made to the UI pack. Shouldn’t affect the vast majority of use cases. Performance improvements due to automatically forcefeeding all reset values. Fix reset timing bug in which reset occurs after user’s complete callback fires. Closes #132. Closes #129. Turned sequence registration into externally-accessible function. Closes #94. Closes #136. Added options customizability to calls. See http://VelocityJS.org/#uiPack.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
I'm looking to add some custom effects for my web application, and like the clean syntax used to declare effects in
velocity.ui.js. However, the way its currently built forces me to either modify the library itself (which I don't want) or duplicate the code used to register the effects @ https://github.com/julianshapiro/velocity/blob/master/velocity.ui.js#L487-L527 which also seems unnecessary.Would it make sense to refactor https://github.com/julianshapiro/velocity/blob/master/velocity.ui.js#L488-L526 to
Velocity.Sequences.register(name, properties)to have an official API supporting this syntax?The text was updated successfully, but these errors were encountered: