Permalink
Browse files

Fully deprecates the animation sub-framework, since it has been fully…

… implemented into SC.View:animate and significantly improved.
  • Loading branch information...
1 parent d427750 commit f310259309c5869c89365891bf990659624669af @publickeating publickeating committed Mar 14, 2013
View
@@ -49,7 +49,6 @@ config :"experimental/split_view", :test_required => [:desktop]
# WRAPPER FRAMEWORKS
config :sproutcore, :required => [:desktop, :datastore, :statechart]
-config :animation, :required => :foundation
config :qunit, :required => []
config :testing, :required => [:jquery], :test_required => [], :debug_required => []
@@ -88,7 +87,7 @@ config :ace,
# CONFIGURE APPS
config :core_tools, :required => [
- :desktop, :datastore, :animation, "sproutcore/experimental/forms",
+ :desktop, :datastore, "sproutcore/experimental/forms",
"sproutcore/ace",
# The SC apps will use the experimental version of these controls:
@@ -1,3 +0,0 @@
-# SproutCore is required for animation to work. This shouldn't be an issue,
-# but is required to force the tester to include SproutCore.
-config :all, :required=>[:sproutcore]
@@ -1,25 +0,0 @@
-Copyright (C) 2009 Alex Iskander and TPSi. All Rights Reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-3. Neither the name of Technical Programming Services, Inc. ("TPSi") nor the
-names of its contributors may be used to endorse or promote products
-derived from this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY TPSi ``AS IS'' AND ANY
-EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL TPSi OR
-CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
-PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
-PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
@@ -1,79 +0,0 @@
-SC.ANIMATABLE
-=============
-
-A simple mixin called SC.Animatable is provided. What does it do?
-It makes CSS transitions for you, and if they aren't available,
-implements them in JavaScript.
-
-Current good things:
-* Animates 300 SC.LabelViews acceptably with only JavaScript. Animates >500
- just as well (if not better) with CSS transitions.
-* Automatically detects if CSS transitions are available.
-
-Current flaws:
-* Supports only a limited subset of properties. For instance, no support for
- animating background colors.
-
-Example Usage:
-
- aView: SC.LabelView.design(SC.Animatable, {
- transitions: {
- left: .25,
- top: {duration: .25}
- width: { duration: .25, timing: SC.Animatable.TIMING_EASE_IN_OUT }, // with timing curve
- height: { duration: .5, timing: [0, 0, 0.58, 1.0] } // with custom timing curve
- }
- })
-
-
-Including in your Project
-===============================================================================
-In your project-level Buildfile, there is a line like this:
-config :all, :required => :sproutcore
-
-Add the animate framework to it by changing it to this:
-config :all, :required => [:sproutcore, 'sproutcore/animation']
-
-Now, you should be able to use it in any view, as demonstrated above!
-
-
-Reference
-===============================================================================
-The API is simple. You set up transitions in the "transitions" property, and can
-supply them with a few parameters:
-* duration: The amount of time in seconds that the animation should last.
-* timing: The timing curve to use. Defaults to SC.Animatable.defaultTimingFunction. See "Timing"
-
-
-Timing
-------
-Timing is handled using beziér curves (like in CSS transitions).
-
-The variable SC.Animatable.defaultTimingFunction can be used to globally set the timing
-curve; any transition that has "null" as its timing curve will use this default
-timing curve.
-
-For example, you could include this line in one of your JavaScript files:
-SC.Animatable.defaultTimingFunction = SC.Animatable.TRANSITION_EASE_IN_OUT;
-
-There are a few built-in timing curves (shown here with their values). The curves
-with CSS in their name are CSS-only versions; JavaScript-based animations will use
-linear. The big benefit of CSS-only timing functions is that JavaScript performance
-is not impacted; to handle timing curves, JavaScript has to do some semi-heavy calculations
-**each frame**. Using CSS-only transitions gives a graceful degradation of sorts.
-
-* SC.Animatable.TRANSITION_NONE: "linear"
-* SC.Animatable.TRANSITION_CSS_EASE: "ease"
-* SC.Animatable.TRANSITION_CSS_EASE_IN: "ease-in"
-* SC.Animatable.TRANSITION_CSS_EASE_OUT: "ease-out"
-* SC.Animatable.TRANSITION_CSS_EASE_OUT: "ease-in-out"
-* SC.Animatable.TRANSITION_EASE: [0.25, 0.1, 0.25, 1.0]
-* SC.Animatable.TRANSITION_LINEAR: [0.0, 0.0, 1.0, 1.0]
-* SC.Animatable.TRANSITION_EASE_IN: [0.42, 0.0, 1.0, 1.0]
-* SC.Animatable.TRANSITION_EASE_OUT: [0, 0, 0.58, 1.0]
-* SC.Animatable.TRANSITION_EASE_IN_OUT: [0.42, 0, 0.58, 1.0]
-
-
-**Note**: The TRANSITION_NONE value is technically a CSS-only "linear" curve; as CSS-only
-curves make JavaScript use linear, it all works out.
-
Oops, something went wrong.

0 comments on commit f310259

Please sign in to comment.