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
Untitled #27
Untitled #27
Conversation
…so we can change the cache and it will still work fine.
Still not sure if a slick object that is being returned by Slick.parse should not be modifiable. I believe, in terms of API, getting an object from one function (Slick.parse), modifying it and automatically and unintentionally changing the behavior of another (Slick.find) method should be strictly verboten (Solely talking Slick, not MooTools). |
I don't wanna include a cloneObject method inside slick and ignore the parser cache... it's one of the great features it can have for being separate from the finder! |
I'm waiting for input from others. I understand the issue regarding the Slick separation, however mutating function results like that should not be possible. |
…nitialize method of Swiff, Swiff uses String.uniqueID for its instance name now
…Specs are included into moo-specs.
…mplementation is broken.
…Specs are included into moo-specs.
…current frame based on the current time (turned ON by default). - forgot to add () to the isRunning call inside stop. Whops!
done. |
Fixes the cache problem on slick and clones the parsed object so we can change it later on the injectCombinator function