sproutcore 1.11.0.rc3 → 1.11.0

checksums.yaml

@@ -1,15 +1,7 @@
 ---
-!binary "U0hBMQ==":
-  metadata.gz: !binary |-
-    MzljNWViZTUxOTllNmJmYjllOWU4MmMyMTk4Mzk5YjhiM2MyM2JjYw==
-  data.tar.gz: !binary |-
-    OWM0MmI4YmIwMGQ4ZTM2NmFhOTk1NTRmZWQ2ZjFmYzJmZWY3NTk0Yw==
-!binary "U0hBNTEy":
-  metadata.gz: !binary |-
-    ZDlkNzk0OWMyZTNjYzk2NjdlZmZmYjdkMmZjNjQ2ZGI4N2NhOWEzZmNhZTg5
-    YjA2OTQxMjVjNTc2OWYxOGI2ZWEyN2U1OTIwMmU5NDkwNWMzYWRlMTVkODcx
-    ZTgxNzI0MWIxMTU2NmRjYzIwMjJjOTEzMjI2OTMzNjNkNmQ2YzQ=
-  data.tar.gz: !binary |-
-    NDQyZGYxMTMxMTQ1YmJjZjZlMGZmZDNjNGQyZDE4MGYyMzhiZWViNWE5Mjdi
-    MjhjODE1N2M0ZDE1NTY1NGI4YTc4MTVkNTljMmNmOTIxZTVlMzIwODNkMjYy
-    N2Q2M2ZhZTM5ZGNkMTVlMzcyNTc1NGM4NGE2NGI4YzlhMDBiZmI=
+SHA1:
+  metadata.gz: e3a3babfc3cb453226d572bfd3ad71707cc3daa4
+  data.tar.gz: 907d56b7c9861cb71890ccd201e2f1378e4118b6
+SHA512:
+  metadata.gz: 598115c0544161273f6241184b39a551100581af3e322bafed769fce30d54d9825bc3405fcfd3fdd7e38625599dcb129148230ffbc9f346ca485dc37328c5916
+  data.tar.gz: 213a9c81419f4d7e46638a4d8aa4d186da5e996b4cb948bdac8c9bf2741093381c55598a92390b222e99ac0d382a986e1af3ba2997c747a2ab775d5b0921c1a1

data/CHANGELOG

@@ -1,3 +1,8 @@
+SproutCore 1.11.0
+-----------------
+
+* Updated HAML code to work with HAML 4.x.
+
 SproutCore 1.11.0.rc3
 -----------------
 

data/VERSION.yml

@@ -1,4 +1,4 @@
 ---
 :major: 1
 :minor: 11
-:patch: 0.rc3
+:patch: 0

data/lib/frameworks/sproutcore/Buildfile

@@ -39,7 +39,8 @@ config :routing,         :required => [:core_foundation]
 config :foundation,      :required => [:routing, :core_foundation, :datetime, :'datetime/localized', :ajax]
 config :datastore,       :required => [:runtime, :datetime]
 config :formatters,      :required => [:runtime, :foundation]
-config :desktop,         :required => [:foundation]
+config :desktop,         :required => [:foundation], :test_required => [:legacy]
+config :legacy,          :required => [:desktop]
 config :media,           :required => [:desktop]
 config :statechart,      :required => [:core_foundation], :test_required => [:core_foundation, :desktop, :routing]
 config :ajax,            :required => [:core_foundation]
@@ -50,7 +51,7 @@ config :"experimental/split_view", :test_required => [:desktop]
 
 # WRAPPER FRAMEWORKS
 config :sproutcore,
-  :required => [:desktop, :datastore, :statechart],
+  :required => [:legacy, :datastore, :statechart],
   :exclude => ['phantomjs']
 
 config :qunit, :required => []

data/lib/frameworks/sproutcore/CHANGELOG.md

@@ -9,18 +9,62 @@ Edge
 ### DEPRECATIONS & REMOVALS
 ### BUG FIXES
 
+1.11.0
+-----------
+
+### NEW FEATURES
+
+#### General
+
+* The `hasObserverFor` method of `SC.Observable` has been improved to also be able to optionally check against a specific target and method. This allows the developer to properly check for the existence of a specific handler before adding it rather than only being able to check for the existence of any handler (without knowing which handler it is).
+
+### CHANGES & IMPROVEMENTS
+
+#### SC.Gesturable & SC.Gesture (SC.TapGesture, SC.PinchGesture, SC.SwipeGesture)
+
+After some investigation, it was found that there were a number of issues with the built-in gesture support. For example, two touch taps would throw an exception, pinches would fail to register and in particular, supporting multiple gestures failed in a number of scenarios. In order to fix these problems, the gesture code has been rewritten from the top-down.
+
+It is now possible to mixin SC.Gesturable to a view and use events to react to multiple gestures concurrently. Examples of the advanced type of behavior that the gesture code allows include:
+
+* Responding to single finger, two finger or any other number of touch taps, pinches (2+ touches) or swipes individually or as a group. For example, your code may want to perform different actions when a single finger taps vs. when there is a two finger tap.
+* A touch session, the time between when the first touch begins and the last touch ends, may contain more than one gesture. For example, it's possible for the user to perform a pinch, then use a third finger to tap, then swipe the remaining fingers. For example, imagine using pinch to scale an image, tap to save the change and then swipe to move it aside all without lifting the fingers. At the least, the ability to perform gestures in a single touch session multiple times, makes the gesture recognition more robust against stray accidental touches.
+* Swipe gestures can now be configured to match against any arbitrary angles, not just left, right, up & down.
+* Swipe gestures no longer trigger by simply moving far enough in one direction. They must also move quickly (configurable) and end immediately.
+
+*How does this affect your code?*  
+
+For the most part, this should have no effect on existing implementors of SC.Gesturable. The three built-in gestures: SC.TapGesture, SC.PinchGesture, and SC.SwipeGesture are still defined and they work much better than before. However if you have defined a custom SC.Gesture subclass, it will unfortunately not work correctly with this update. Because we felt the previous version of SC.Gesture's API was too complex and incompatible with the behavior we needed to achieve, we decided it was better to rewrite it in a simpler form. We're very sorry for this backwards incompatibility, but because of the previous issues with gestures, we believe no one was able to use them anyway.
+
+#### Legacy Framework
+
+There is now a sub-framework within SproutCore, `:'sproutcore/legacy'`, which is meant to contain all code providing support for older browsers. This includes the existing polyfill for `window.requestAnimationFrame` and a brand new polyfill for `Object.keys`. The legacy framework is included by default by requiring `:sproutcore` in a project's or an app's Buildfile. The legacy framework itself requires the `:sproutcore/desktop` framework, which allows for any legacy code in the SproutCore controls to be separated out.  
+
+Therefore, to build an app that will only work with the newest browsers (probably not a great idea —), you may change your Buildfile requirements to include only the specific SproutCore sub-frameworks you need. For example,
+
+    config :my_app, :required => [:"sproutcore/desktop", :"sproutcore/datastore"]
+
+### DEPRECATIONS & REMOVALS
+
+* The `owner` property of SC.View has been deprecated for general use. This property is identical to the existing `parentView` property on all views. It existed in order for some ancestor view to claim ownership of a descendent view, so that the descendent could reference the ancestor directly as `owner` rather than using some chain like `parentView.parentView...`. However, this type of connection can still be achieved by the an ancestor simply assigning `owner`, or whichever property they want to use, none-the-less and there's no need for every single SC.View to have it assigned.
+
+Note: This deprecation will show a console warning in debug (i.e. non-production) mode.
+
+### BUG FIXES
+
+* Fixed several regressions from previous release candidates.
+
 1.11.0.rc3
 -----------
 
 ### NEW FEATURES
 
-* *SC.NestedStore*  
+#### SC.NestedStore
 
 `SC.NestedStore` has a new property, `conflictedStoreKeys`, which is an array of all store keys that currently have conflicts with the nested store's parent. A conflict in a nested store can occur when the data in the parent store changes *after* the nested store has accessed and modified it.  
 
 For instance, in a multi-user system where records can be edited by multiple people at the same time, the client may use polling or websockets to update the records in the main store asynchronously in the background. With such a scenario it would be possible for the current user to be editing a record that someone else has changed in the meantime. If the client attempted to commit the changes from the nested store it would get an exception because of the conflict. Instead, the developer can now check the value of `conflictedStoreKeys` and if it is `null`, then commit the changes and if it is an array of store keys, then they know which records have conflicts and can deal with them directly.
 
-* *SC.Binding*  
+#### SC.Binding
 
 There are two new binding transforms, `string` and `integer`, that ensure the value is *always* a `String` or an integer `Number`. Examples include returning an empty `String` for `null` or `undefined` values when using the `string` transform and returning a 0 for these same values when using the `integer` transform. Furthermore, if the `integer` transform is given a String, it will be parsed to an integer `Number` according to the extra argument `radix` (which is 10 by default).
 
@@ -50,27 +94,31 @@ For example, to create a mix binding that concatenates two external properties i
 
     })
 
+#### General
+
 * *Updated Description* Scale is now a first-class layout property, correctly impacting `frame` and `clippingFrame`. If a view is scaled, the width & height of the frame will be correct as the view appears. For example, a view with layout equal to `{ width: 100, height: 100, scale: 2 }` will report a frame of `{ x: 0, y: 0, width: 200, height: 200, scale: 2 }`. The scale also takes a scaling origin into account as well and as part of this change, there are two new layout properties: `transformOriginX` and `transformOriginY`, which define the percentage (between 0.0 and 1.0) on the respective axis about which the scale transform is applied. These properties affect all transform styles and so can be used to also change the origin of a rotate style.  
 
 ### CHANGES & IMPROVEMENTS
 
-* Documentation  
+#### Documentation  
 
-** Added lots of documentation to `SC.Request` (examples), `SC.Query` (local vs. remote) and `SC.DateTime` (`adjust` and `advance`). 
-** Cleaned up documentation of all protocols, including a warning not to mix in protocols and fixed some problems that prevented some protocols from being properly generated on docs.sproutcore.com.
-** Added `SC.ObjectMixinProtocol` with documentation on using mixins with `SC.Object` as well as the methods `initMixin` and  `destroyMixin` that are supported.
-** Added documentation on touch event handling to `SC.ResponderProtocol` (i.e. the protocol that may be implemented by `SC.Responder` subclasses like `SC.View`).
-** Added/improved documentation on `SC.Gesturable` mixin.
+- Added lots of documentation to `SC.Request` (examples), `SC.Query` (local vs. remote) and `SC.DateTime` (`adjust` and `advance`).   
+- Cleaned up documentation of all protocols, including a warning not to mix in protocols and fixed some problems that prevented some protocols from being properly generated on docs.sproutcore.com.  
+- Added `SC.ObjectMixinProtocol` with documentation on using mixins with `SC.Object` as well as the methods `initMixin` and  `destroyMixin` that are supported.  
+- Added documentation on touch event handling to `SC.ResponderProtocol` (i.e. the protocol that may be implemented by `SC.Responder` subclasses like `SC.View`).  
+- Added/improved documentation on `SC.Gesturable` mixin.  
 
-* SC.PickerPane  
+#### SC.PickerPane  
 
 This view has been given special behavior when used with SC.View's `transitionIn` plugin support. If the plugin defines `layoutProperties` of either `scale` or `rotate`, then the picker will adjust its transform origin X & Y position to appear to scale or rotate out of the anchor. The result is a very nice effect that picker panes appear to pop out of their anchors.  
 To see it in effect, simply set the `transitionIn` property of the pane to one of `SC.View.SCALE_IN` or `SC.View.POP_IN`.
 
-* SC.SegmentedView  
+#### SC.SegmentedView  
 
 This view was refactored slightly to remove the special overflow view if `shouldHandleOverflow` is `false` (default). Previously the overflow view was always created and appended even if it was not to be used.  
 
+#### General
+
 * The automatically adjusted size component of the layouts of `SC.ListView` and `SC.GridView` have changed to set `height` and `width` instead of `minHeight` and `minWidth` (as it applies). The reason for this change is so that the entire list of items can be GPU accelerated by setting `wantsAcceleratedLayer: true` on the view. GPU accelerated positioning using the `translateX` and `translateY` transforms requires that the view have a fixed position (top & left) and a fixed size (height & width). These views already have a fixed position by default and now by having them adjust their `height` or `width` (depending on the direction), it is possible to accelerate these views by also fixing the other size component (i.e. if the list scrolls vertically, the list will set its height, so the developer needs to set the lists width to a fixed value and then add `wantsAcceleratedLayer: true`).  
 
 Test Results:
@@ -87,6 +135,7 @@ Test Results:
       Paint x 8:         ~6.0ms
 
 *How does this affect your code?*  
+
 Because lists and grids have an implied layout of `{ top: 0, bottom: 0, left: 0, right: 0 }`, they used to always stretch to fill their parent containing view. This is no longer the case and so a collection with too few items to fill the containing view will only be as tall or as wide as its items warrant. This will affect any background styles that were applied to the collection (such as the Ace theme did), which previously would have covered the whole containing view's background. Unfortunately, those background styles need to be moved to the style of the containing view in order to prevent any styling regressions after updating to this new version.  
 
 Therefore, to go along with this change the `background: white` style in the Ace theme that was applied to `$theme.collection` has been moved to `$theme.sc-scroll-view`. It has also been changed to `background-color: white`, which is less likely to conflict with other background styles.  

data/lib/frameworks/sproutcore/apps/showcase/resources/main_page.js

@@ -41,6 +41,7 @@ Showcase.mainPage = SC.Page.design({
       }),
 
       detailView: SC.ContainerView.design({
+        classNames: ['main-detail-view'],
         nowShowing: 'Showcase.mainPage.welcomeView',
         nowShowingBinding: SC.Binding.notEmpty('Showcase.sourceController.view', 'Showcase.mainPage.welcomeView')
       })

data/lib/frameworks/sproutcore/apps/showcase/resources/stylesheet.css

@@ -10,14 +10,20 @@ $theme.sc-source-list.main-source-list {
   }
 }
 
-$theme.views-list-view {
+$theme.main-detail-view {
   @include background-image(linear-gradient(rgba(255,255,255,0.0), rgba(0,0,0,0.2)));
   background-color: #a1a1a1;
+
+  .sc-scroll-view {
+    @include slice('images/pixels.png', $repeat: repeat);
+    background-color: #8fc4f8;
+  }
+}
+
+$theme.views-list-view {
 }
 
 $theme.views-item-view {
-  @include slice('images/pixels.png', $repeat: repeat);
-  background-color: #8fc4f8;
   border-bottom: 1px solid #5d88b6;
   border-top: 1px solid #a5d1ff;
 
@@ -211,7 +217,6 @@ $theme.sc-list-view.my-list-view {
 
 
 $theme.sc-scroll-view.my-scroll-view {
-  background-color: #ececec;
   border: 1px solid #7f7f7f;
 }
 

data/lib/frameworks/sproutcore/frameworks/core_foundation/panes/manipulation.js

@@ -31,6 +31,6 @@ SC.Pane.reopen(
     @returns {void}
   */
   removeFromParent: function() {
-    throw SC.Error.desc("SC.Pane cannot be removed from its parent, since it's the root. Did you mean remove()?");
+    SC.throw("SC.Pane cannot be removed from its parent, since it's the root. Did you mean remove()?");
   }
 });

data/lib/frameworks/sproutcore/frameworks/core_foundation/system/event.js

@@ -253,16 +253,6 @@ SC.mixin(SC.Event, /** @scope SC.Event */ {
     // don't do events on text and comment nodes
     if ( elem.nodeType === 3 || elem.nodeType === 8 ) return SC.Event;
 
-    /*
-      commenting out this block because
-      1. this issue is no longer reproducible in IE7, 8 or 9
-      2. this causes undesired behavior if one tries to remove an event from
-         an iframe because elem.setInterval is true there.
-    */
-    // // For whatever reason, IE has trouble passing the window object
-    // // around, causing it to be cloned in the process
-    // if (SC.browser.name === SC.BROWSER.ie && elem.setInterval) elem = window;
-
     var handlers, key, events = SC.data(elem, "sc_events") ;
     if (!events) return this ; // nothing to do if no events are registered
 

data/lib/frameworks/sproutcore/frameworks/core_foundation/system/locale.js

@@ -75,7 +75,7 @@ SC.Locale = SC.Object.extend({
   /**
     The inflection constants for this locale.
   */
-  inflectionConstants: {},
+  inflectionConstants: null,
 
   /**
     The method used to compute the ordinal of a number for this locale.

data/lib/frameworks/sproutcore/frameworks/core_foundation/system/root_responder.js

@@ -1094,10 +1094,9 @@ SC.RootResponder = SC.Object.extend(
       averaged.d = 0;
       averaged.velocityX = 0;
       averaged.velocityY = 0;
-      averaged.touchCount = 0;
-    }
+
     // Otherwise, average the touches.
-    else {
+    } else {
       // Cache the array object used by this method. (Cleared at the end to prevent memory leaks.)
       var touches = this._averagedTouches_touches || (this._averagedTouches_touches = []);
 
@@ -1114,47 +1113,8 @@ SC.RootResponder = SC.Object.extend(
       // Add additionalTouch if present and not duplicated.
       if (additionalTouch && !additionalTouchIsDuplicate) touches.push(additionalTouch);
 
-      // prepare variables for looping
-      var idx, touch,
-          ax = 0, ay = 0, dx, dy, ad = 0, avx = 0, avy = 0;
-      len = touches.length;
-
-      // first, add
-      for (idx = 0; idx < len; idx++) {
-        touch = touches[idx];
-        ax += touch.pageX;
-        ay += touch.pageY;
-        avx += touch.velocityX;
-        avy += touch.velocityY;
-      }
-
-      // now, average
-      ax /= len;
-      ay /= len;
-      avx /= len;
-      avy /= len;
-
-      // distance
-      for (idx = 0; idx < len; idx++) {
-        touch = touches[idx];
-
-        // get distance from average
-        dx = Math.abs(touch.pageX - ax);
-        dy = Math.abs(touch.pageY - ay);
-
-        // Pythagoras was clever...
-        ad += Math.pow(dx * dx + dy * dy, 0.5);
-      }
-
-      // average
-      ad /= len;
-
-      averaged.x = ax;
-      averaged.y = ay;
-      averaged.velocityX = avx;
-      averaged.velocityY = avy;
-      averaged.d = ad;
-      averaged.touchCount = len;
+      // Calculate the average.
+      SC.Touch.averagedTouch(touches, averaged);
 
       // Clear the touches array to prevent touch object leaks.
       touches.length = 0;
@@ -2159,7 +2119,6 @@ SC.RootResponder = SC.Object.extend(
         dragView.tryToPerform('mouseUp', evt);
       });
     } else {
-
       var view = this._mouseDownView,
         targetView = this.targetViewForEvent(evt);
 
@@ -2342,6 +2301,7 @@ SC.RootResponder = SC.Object.extend(
   dragenter: function(evt) {
     SC.run(function() { this._dragenter(evt); }, this);
   },
+
   /** @private */
   _dragenter: function(evt) {
     if (!this._dragCounter) {
@@ -2350,10 +2310,12 @@ SC.RootResponder = SC.Object.extend(
     else this._dragCounter++;
     return this._dragover(evt);
   },
+
   /** @private The dragleave event comes from the browser when a data-ful drag leaves any element. */
   dragleave: function(evt) {
     SC.run(function() { this._dragleave(evt); }, this);
   },
+
   /** @private */
   _dragleave: function(evt) {
     this._dragCounter--;
@@ -2373,10 +2335,12 @@ SC.RootResponder = SC.Object.extend(
       this._dragover(evt);
     });
   },
+
   /** @private This event fires continuously while the dataful drag is over the document. */
   dragover: function(evt) {
     SC.run(function() { this._dragover(evt); }, this);
   },
+
   /** @private */
   _dragover: function(evt) {
     // If it's a file being dragged, prevent the default (leaving the app and opening the file).
@@ -2447,6 +2411,7 @@ SC.RootResponder = SC.Object.extend(
   drop: function(evt) {
     SC.run(function() { this._drop(evt); }, this);
   },
+
   /** @private */
   _drop: function(evt) {
     // If it's a file being dragged, prevent the default (leaving the app and opening the file).

data/lib/frameworks/sproutcore/frameworks/core_foundation/system/selection_set.js

@@ -158,7 +158,7 @@ SC.SelectionSet = SC.Object.extend(SC.Enumerable, SC.Freezable, SC.Copyable,
   */
   add: function(source, start, length) {
 
-    if (this.isFrozen) throw SC.FROZEN_ERROR ;
+    if (this.isFrozen) throw new Error(SC.FROZEN_ERROR);
 
     var sets, len, idx, set, oldlen, newlen, setlen, objects;
 
@@ -218,7 +218,7 @@ SC.SelectionSet = SC.Object.extend(SC.Enumerable, SC.Freezable, SC.Copyable,
   */
   remove: function(source, start, length) {
 
-    if (this.isFrozen) throw SC.FROZEN_ERROR ;
+    if (this.isFrozen) throw new Error(SC.FROZEN_ERROR);
 
     var sets, len, idx, i, set, oldlen, newlen, setlen, objects, object;
 
@@ -536,7 +536,7 @@ SC.SelectionSet = SC.Object.extend(SC.Enumerable, SC.Freezable, SC.Copyable,
     @returns {SC.SelectionSet}
   */
   clear: function() {
-    if (this.isFrozen) throw SC.FROZEN_ERROR;
+    if (this.isFrozen) throw new Error(SC.FROZEN_ERROR);
     if (this._sets) this._sets.length = 0 ; // truncate
     if (this._objects) this._objects = null;
 

data/lib/frameworks/sproutcore/frameworks/core_foundation/system/touch.js

@@ -143,6 +143,13 @@ SC.Touch = function(touch, touchContext) {
 };
 
 SC.Touch.prototype = {
+  //@if(debug)
+  // Debug-mode only.
+  toString: function () {
+    return "SC.Touch (%@)".fmt(this.identifier);
+  },
+  //@endif
+
   /**@scope SC.Touch.prototype*/
 
   /** @private
@@ -532,7 +539,76 @@ SC.Touch.prototype = {
 };
 
 SC.mixin(SC.Touch, {
+
   create: function(touch, touchContext) {
     return new SC.Touch(touch, touchContext);
+  },
+
+  /**
+    Returns the averaged touch for an array of given touches. The averaged touch includes the
+    average position of all the touches (i.e. the center point), the averaged distance of all
+    the touches (i.e. the average of each touch's distance to the center) and the average velocity
+    of each touch.
+
+    The returned Object has a signature like,
+
+        {
+          x: ...,
+          y: ...,
+          velocityX: ...,
+          velocityY: ...,
+          d: ...
+        }
+
+    @param {Array} touches An array of touches to average.
+    @param {Object} objectRef An Object to assign the values to rather than creating a new Object. If you pass an Object to this method, that same Object will be returned with the values assigned to it. This is useful in order to only alloc memory once and hold it in order to avoid garbage collection. The trade-off is that more memory remains in use indefinitely.
+    @returns {Object} The averaged touch.
+  */
+  averagedTouch: function (touches, objectRef) {
+    var len = touches.length,
+        ax = 0, ay = 0, avx = 0, avy = 0,
+        idx, touch;
+
+    // If no holder object is given, create a new one.
+    if (objectRef === undefined) { objectRef = {}; }
+
+    // Sum the positions and velocities of each touch.
+    for (idx = 0; idx < len; idx++) {
+      touch = touches[idx];
+      ax += touch.pageX;
+      ay += touch.pageY;
+      avx += touch.velocityX;
+      avy += touch.velocityY;
+    }
+
+    // Average each value.
+    ax /= len;
+    ay /= len;
+    avx /= len;
+    avy /= len;
+
+    // Calculate average distance.
+    var ad = 0;
+    for (idx = 0; idx < len; idx++) {
+      touch = touches[idx];
+
+      // Get distance for each from average position.
+      var dx = Math.abs(touch.pageX - ax);
+      var dy = Math.abs(touch.pageY - ay);
+
+      // Pythagoras was clever...
+      ad += Math.pow(dx * dx + dy * dy, 0.5);
+    }
+
+    // Average value.
+    ad /= len;
+
+    objectRef.x = ax;
+    objectRef.y = ay;
+    objectRef.velocityX = avx;
+    objectRef.velocityY = avy;
+    objectRef.d = ad;
+
+    return objectRef;
   }
 });