sproutcore 1.11.0.rc1 → 1.11.0.rc2

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    YWNkNmQyY2I1Zjk5MDE3ZDA2NDYxMmZhNjdlNDhhYzRhODFmMjdmYw==
+    ZDA3N2VhZDM4N2JjNjQyMzFiMzM5MWQ5OTc1MDkyZWJmNjU2OWRkMg==
   data.tar.gz: !binary |-
-    MmYzZjBiYjExZDkyNzQ2OTVlNjk4MzljMmI5ZTUxNTkwODhjMzY2ZA==
+    Y2EzNWNiN2M0NzI2OTYyM2UzN2M4MDQ0ZTMyNzQ2Mzc2Y2U1OTY4Yg==
 !binary "U0hBNTEy":
   metadata.gz: !binary |-
-    OWU0OTljNTEyNDc3YWNiNzA0NzNlYWYzNWIyZTZiYTcyZWI0YjU1NmVkOGI0
-    MGJkNjhlYzgzMGNkMTkxNDM4MDkxNDAyMGQ2YjBkYzcwNDE2NTYzN2I2MmVj
-    MzY4YjM0YTE2ZTBkZTU4NWYwNDBjMGQ4ZTczMjM1Y2RmMmE2MzE=
+    YTRjNzY4ZjRkYjZiYjBiZjU0MjI2NGI4ZmE4ZTYzMzE3MDNiNjJhYzk0OWE0
+    NzhhN2MxNWQ5NzAwNzU3OTlhOGM1YjFlZTY0ODg2ZTE0ZTI0MTczMWQyZWVh
+    MThmNjc5MjMxYzBmYzVkZTE5OWZmZjNiMzhkNGZjM2UyZjQ4OWM=
   data.tar.gz: !binary |-
-    NWI0ZmFlYjYxM2VjMmIxZDI0ZmQwZTU1OTIzZWE5NzdkZjhjMTdlNTM3MzBi
-    NTA4NmRiMzUyNzVhZDZjODAyYWNlOWI0MjVmODZkOTRlYWMzY2RmYjlhOTJh
-    ZGUwM2IwZDJhNjE5MTcxZjkzODg0YjM0ODRiODdhZmMwYzA3MmI=
+    MDc1MGQzMWM1YzljMDJhNTcyZGFlMjQwNDQxZDI5ZGMzZjg3M2FmN2UyNzZm
+    YjZmZGQ4YjA0NjU0OGYxMjZkOGI3ZDZjOGVhZmU5NDFmMjczMzdmOWZmNmNi
+    MDAwMzQ0NjJjNDEyMGNhYjc5NDhmNDIxYTBmMDhkYTBlZjMzZDE=

data/VERSION.yml

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

data/lib/frameworks/sproutcore/CHANGELOG.md

@@ -1,24 +1,53 @@
 CHANGE LOG
 ==========
 
-1.11.0
+1.11.0.rc2
 -----------
 
-### NEW FEATURES
+### CHANGES & IMPROVEMENTS
+
+* SC.ScrollView alignment handling has been improved for container (i.e. the scroll view) or content size changes. This change partially addresses a regression that allowed the content to appear offset incorrectly when it or the scroll view's size changed. But after some investigation, the behavior has also been improved to support the following scenarios:  
+
+1. The scroll view is left (or top) aligned, scrolled to the maximum right (or bottom) edge and container or content changes size: the content should stick to the right (or bottom) side
+2. The scroll view is left (or top) aligned, scrolled to the minimum left (or top) edge and container or content changes size: the content should stick to the left (or top) side
+3. The scroll view is right (or bottom) aligned, scrolled to the maximum right (or bottom) edge and container or content changes size: the content should stick to the right (or bottom) side
+4. The scroll view is right (or bottom) aligned, scrolled to the minimum left (or top) edge and container or content changes size: the content should stick to the left (or top) side
+5. The scroll view is center (or middle) aligned, scrolled to the center (or middle) and container or content changes size: the content should stick to the center (or middle)
+
+* Refactored SC.Event slightly. Most importantly, SC.Event instances are now cached per event type in order to avoid constant memory re-allocation. Previously, every DOM event was normalized into a new SC.Event object, which was later freed. In order to reduce the amount of memory churn, one SC.Event instance is cached per type of event and updated with the new DOM event as it comes in.
+* Removed long deprecated method, `SC.browser.compareVersion`. This method was deprecated in version 1.7 and is not used anywhere within the framework. As the deprecation warning noted, developers should use the `SC.browser.compare` method for doing a proper comparison between version strings.
+* The core methods used in SC.View layout have been slightly optimized to avoid memory re-allocation. Since SC.View layout code may run repeatedly in short order (e.g. re-positioning during scrolling), we need to ensure that no new objects are created each time. The reason for this is so that we're not quickly adding hundreds of small objects to the garbage heap that will need to be collected. Since we have no control over when garbage collection occurs, the best we can do is try to avoid it and to ensure that it completes as quickly as possible.
+* The argument for the SC.ActionSupport mixin's main method `fireAction` has been changed from `action` to `context`. This allows calling-time specific information to be passed to the action + target on each call. To specify the `action` for `fireAction` to use, the existing `action` property should still be set. As part of this change, the documentation for SC.ActionSupport has been greatly extended and includes tips on supporting multiple actions or targets and for implementing actions on targets.
+  
+Along with this change, the `actionContext` property has also now been deprecated and will be removed in a future version of SproutCore.
+
+Note: this is a backwards-compatible change. If a String is passed to `fireAction` *and* no `action` property exists, the argument will be used as the `action` (i.e. no context will be sent). When this occurs, a Developer Warning will appear in the console. Likewise, a Developer Warning will appear if `actionContext` is set prior to a view being initialized.
+* SC.ButtonView and SC.CollectionView have both been altered slightly to use SC.ActionSupport. This has no affect on the use of action & target in these views.
+* Moved tracing code of SC.ResponderContext and SC.Module to debug-only. This prevents the debugging code from being included in production builds, thus reducing the overall deployed file size slightly.
+* Optimized use of the `arguments` object in several locations in order to avoid its instantiation. There were several occurrences of code copying the `arguments` object into an Array using `slice`; this is very costly for performance as it causes the browser to instantiate the `arguments` object in order to do the slice. Instead, these occurrences were converted to either access the arguments by index without a copy or to do a fast copy without instantiation. See http://jsperf.com/closure-with-arguments for an example of the performance difference this can make. Using slice is anywhere from ~50% to ~90% slower depending on the browser.  
+  
+Affected: SC.Request, SC.WebSocket, SC.DelegateSupport, SC.Color, SC.Event, SC.Store, SC.Module, SC.Object, SC.Function, SC.State, SC.Statechart
+* Named two anonymous functions: send_event & handle_event in order to aid in debugging and profiling of the core framework.
+
+### BUG FIXES
 
-* Added polymorphic record support to SC.Record. This experimental framework has been in use in a few projects and has recently been vastly improved to fix bugs and improve its performance. Includes unit tests and examples
-* Added new properties to SC.Request instances: allowCredentials (default true, which will indicate that credentials be included for cross-domain requests (e.g. xhr.withCredentials = true) and isSameDomain (readonly computed property, true if the protocol, domain and port match exactly).
+* Fixed a very slow memory leak in SC.browser. Caching of the experimental style names for the current browser would fail intermittently since the cache key was being kept on the CSSStyleDeclaration which the browser (seen in Chrome) would occasionally drop. Caching is now done per experimental style name, which is more correct and has the added benefit of being marginally faster than using SC.guidFor.
+* Fixed a deficiency in SC.RootResponder.prototype.sendAction. It failed to pass the given context argument along to the target unless the target was a ResponderContext object (i.e. SC.Pane or SC.Application).
+* Fixed a memory leak in SC.WebSocket due to a set on an undeclared (i.e. global) variable.
+* Fixed an issue with SC.SegmentedView that meant its frame property failed to update when its layout was changed.
+
+1.11.0.rc1
+-----------
+
+### NEW FEATURES
 
-These new properties can be used by an SC.Response subclass to include allowing credentials for cross domain requests.
-* Added dragDidSucceed, dragDidCancel, source.dragSlideBackDidEnd callbacks to SC.Drag.
+* Added polymorphic record support to `SC.Record`. This experimental framework has been in use in a few projects and has recently been vastly improved to fix bugs and improve its performance. Includes unit tests and examples
+* Added new properties to `SC.Request` instances: `allowCredentials` (default true, which will indicate that credentials be included for cross-domain requests (e.g. xhr.withCredentials = true) and `isSameDomain` (readonly computed property, true if the protocol, domain and port match exactly).  
+These new properties can be used by an `SC.Response` subclass to include allowing credentials for cross domain requests.
+* Added `dragDidSucceed`, `dragDidCancel`, `source.dragSlideBackDidEnd` callbacks to `SC.Drag`.
 * `SC.View.VERTICAL_STACK` & `SC.View.HORIZONTAL_STACK` have been improved to allow child views in the stack to resize to fill available space. Previously, every child view needed to have a height or width specified with the exception of the last child view which could be resized to fit the remaining space of the parent view. This option was enabled by setting `resizeToFit` to `false` in the `childViewLayoutOptions` hash. In 1.11, we can now set `resizeToFit` to `false` and have all child views without an explicit width or height respectively, resize to fill the available space. By default the available space will be shared evenly by all of these child views, but a more specific per child view weighting can be applied by specifing a `fillRatio` on the child views. For instance, to split the available space between two flexible child views as 1/3 and 2/3, the first view would have a `fillRatio` of 1 and the second view would have a `fillRatio` of 2.
-* Updates SC.SceneView to support the new SC.ContainerView hardware-accelerable transitions.
-* Adds new SC.WebSocket wrapper class with proper run loop behavior.
-* The last item view in a CollectionView now gets an isLast property.
-* In the test runner app, adds links to individual test URLs for easier access.
-* Adds SC.ListItemView's right icon as a click-action zone to accompany the existing left icon action support.
-* Many developer warnings and errors that would previously appear in production have been restricted to dev-mode only.
-* Binding helper methods SC.Binding.and & SC.Binding.or are now fully armed and operational, including supporting local properties.
+* Adds new `SC.WebSocket` wrapper class with proper run loop behavior.
+* Adds `SC.ListItemView`'s right icon as a click-action zone to accompany the existing left icon action support.
 * SC.TextFieldView now supports browser autocompletion via its boolean autoComplete property.
 * SC.ContainerView transition plugins can now specify reversable transitions.
 * The developer warnings that are logged when you try to bind to a non-bindable object (or forget a leadoff period on a local property) has been improved and clarified substantially.
@@ -31,75 +60,68 @@ These new properties can be used by an SC.Response subclass to include allowing
 * SC.Drag#slideBack now works as advertised!
 * SC.UndoManager has been refactored to allow easier undo action grouping; see documentation for details. SC.UndoManager#registerUndo has been replaced with the cleaner SC.UndoManager#registerUndoAction API, which provides support for the standard target/action pattern.
 * SC.DateFieldView now supports freeform keyboard number entry.
-* iOS-style Overlaid scroller bars now fade out when not in use.
-* SC.Color#cssText is now read/write, allowing you to bind it to a user-enterable text field. SC.Color now implements SC.Error and enters an error state when given bad input.
 * SC.MenuPane now has an escapeHTML property which it proxies to its items.
-* SC.Request.manager has two new methods: isPending and isInFlight.
-* Adds long-overdue SC.Binding.equalTo.
+* `SC.Request.manager` has two new methods: `isPending` and `isInFlight`.
+* Adds `SC.Binding.equalTo`.
 * Adds boolean shouldAutoResize property to SC.SegmentedView.
-* Added documentation and constants will make SC.PickerPane positioning and customization much easier.
-* Now includes "minimal-ui" viewport meta tag for awesomer Mobile Safari apps.
+* Now includes "minimal-ui" viewport meta tag for Mobile Safari apps.
 * Adds stackNextTouchResponder and stackCandidateTouchResponder methods to SC.Touch to make it easier to pass touch respondership between views.
-* SC.ListView can now be horizontal as well as vertical with new layoutDirection property. Renames all rowHeight properties to rowSize.
-* Adds new opt-in API (SC.Store#chainAutonomousStore) for nested stores which can interact with the data source. This allows you to commit nested store changes to the server before committing successful updates to the parent store with SC.NestedStore#commitSuccessfulChanges.
-* Setting SC.ScrollView#delaysContentTouches will now give your content views full control over touch events in question. As a side effect, native touch handling is now possible inside scroll views.
-* SC.ScrollView#scale now works as advertised!
-* Scale is now a first-class layout function, correctly impacting frame and clippingFrame. As a result, scaled content within a CollectionView will now correctly calculate which item views should be currently visible.
-* Adds official SC.Scalable protocol.
-* SC.SliderView has a new markSteps property, which draws a mark element for each step. It also gains an updateOnScroll property, which allows you to prevent it from handling mouseWheel events (in a scroll view for example).
-* The improved documentation for SC.Object's stupendously useful didChangeFor method will hopefully encourage its use.
-* Use SC.ScrollView's horizontalAlign and verticalAlign properties to align fixed-width or -height content.
-* Adds support for calculated properties to String.fmt.
-* Adds toolTip to SC.MenuItemView, and the corresponding itemToolTipKey to SC.MenuView.
+* Adds horizontal layout for `SC.ListView` using `layoutDirection` property.
+* Adds new opt-in API (`SC.Store.prototype.chainAutonomousStore`) for nested stores which can interact with the data source. This allows you to commit nested store changes to the server before committing successful updates to the parent store with `SC.NestedStore.prototype.commitSuccessfulChanges`.
+* Setting `SC.ScrollView.prototype.delaysContentTouches` will now give your content views full control over touch events in question. As a side effect, native touch handling is now possible inside scroll views.
+* `SC.SliderView` has a new `markSteps` property, which draws a mark element for each step. It also gains an `updateOnScroll` property, which allows you to prevent it from handling `mouseWheel` events (in a scroll view for example).
+* Adds support for calculated properties to `String.fmt`.
+* Adds `toolTip` property to `SC.MenuItemView`, and the corresponding `itemToolTipKey` to `SC.MenuView`.
 
 ### CHANGES & IMPROVEMENTS
 
+* Scale is now a first-class layout function, correctly impacting frame and clippingFrame. As a result, scaled content within a CollectionView will now correctly calculate which item views should be currently visible.
 * SC.ScrollView complete refactor:
-
-** Ensures that scaling the view maintains the visual center.
-** Improves touch support significantly. Including centered zooming for pinch gestures, smoother bounce-back overdrag past the boundaries.
-** Improves gesture animation performance and feel with requestAnimationFrame.
-** Supports flexible sized GPU accelerated content. When the content of the view has an undefined width or height, SC.ScrollView will fix the size of the content to fit the container so that it may be positioned using translateX & translateY.
-** Uses shared objects for adjusting the content & container views of SC.ScrollView. This prevents repeated memory allocs while scrolling, which must eventually be garbage collected (a painful occurrence in JavaScript).
-
+  * If `horizontalOverlay` or `verticalOverlay` is true, it will use `SC.OverlayScrollerView` by default. It's no longer necessary to also set `horizontalScrollerView: SC.OverlayScrollerView` in order to get overlaid scrollers.
+  * Use SC.ScrollView's horizontalAlign and verticalAlign properties to align fixed-width or -height content.
+  * SC.ScrollView#scale now works as advertised!
+  * iOS-style Overlaid scroller bars now fade out when not in use.
+  * Ensures that scaling the view maintains the visual center.
+  * Improves touch support significantly. Including centered zooming for pinch gestures, smoother bounce-back overdrag past the boundaries.
+  * Improves gesture animation performance and feel with requestAnimationFrame.
+  * Supports flexible sized GPU accelerated content. When the content of the view has an undefined width or height in its layout and has `wantsAcceleratedLayer` set to `true`, `SC.ScrollView` will fix the undefined size (width or height) of the content to *fit* the container so that the content may be scrolled using `translateX` & `translateY`.
+  * Uses shared objects for adjusting the content & container views of SC.ScrollView. This prevents repeated memory allocs while scrolling, which must eventually be garbage collected (a painful occurrence in JavaScript).
 * Improves SC.Touch documentation.
+* The improved documentation for SC.Object's didChangeFor method will hopefully encourage its use.
+* The last item view in a CollectionView now gets an isLast property.
 * Removes an extra Object instantiation in `SC.View.prototype.computeParentDimensions` (if frame wasn't given, an empty Object was instantiated for no real use). Also removes pre-obfuscation of variables.
 * Speeds up and slims down the `SC.View.prototype.adjust` method. When a single key is passed to `adjust()` it no longer creates an Object just to iterate the single key. Likewise, the resulting call to `_checkForResize()` on layout changes is improved by removing the creation of two Objects used for testing and by removing the over achieving test (the test covered the case of concurrent effective border and size changes, which are very rare and not critical to fail the test).
 * Cleaned up the SC.Pane unit tests (were leaving panes attached, missing run loops, etc.) and fixed the situation where calling destroy on a building out view would fail to remove the view's layer immediately.
 * Improves the SC.View cancel animation method to work with centerX/centerY animations. Disabled the rotation decompositions on X & Y axes, since they don't work in all cases.
 * Changed SC.GridView to provide its own height rather than minHeight. Note: We use height, because this allows the list view to be positioned with translateX, translateY.
 * Refactored SC.MenuScrollView.
-
-** Reduced code by removing duplicate properties from its superclass SC.ScrollView.
-** Renamed verticalScrollerView & verticalScrollerView2 to topScrollerView & bottomScrollerView respectively to make it clearer which they are and to avoid confusion with the verticalScrollerView property of SC.ScrollView.
-** Removed four (!) extra observers (one which was totally useless on the non-existant horizontal scroller visibility).
-** Tidied up the createChildViews code to be more readable and not make excess calls to reposition the scrollers.
-** Improved the appearance/disappearance of the scrollers. It now shifts the content view at the same time that the container view adjusts to show/hide scrollers so that the content view never appears to jump, which also ensures that there is no extra space at the bottom of the container view.
-
+  * Reduced code by removing duplicate properties from its superclass SC.ScrollView.
+  * Renamed verticalScrollerView & verticalScrollerView2 to topScrollerView & bottomScrollerView respectively to make it clearer which they are and to avoid confusion with the verticalScrollerView property of SC.ScrollView.
+  * Removed four (!) extra observers (one which was totally useless on the non-existant horizontal scroller visibility).
+  * Tidied up the createChildViews code to be more readable and not make excess calls to reposition the scrollers.
+  * Improved the appearance/disappearance of the scrollers. It now shifts the content view at the same time that the container view adjusts to show/hide scrollers so that the content view never appears to jump, which also ensures that there is no extra space at the bottom of the container view.
 * Pulled SC.MenuScrollerView into its own file and refactors it slightly.
-
-** Reduced the amount of code by removing duplicate properties from its superclass SC.ScrollerView.
-** Removed unused code (ownerScrollValueKey computed property & _sc_scroller_valueDidChange observer(!)).
-** Improved the readability of the _scrollMenu method.
-
+  * Reduced the amount of code by removing duplicate properties from its superclass SC.ScrollerView.
+  * Removed unused code (ownerScrollValueKey computed property & _sc_scroller_valueDidChange observer(!)).
+  * Improved the readability of the _scrollMenu method.
 * Refactored SC.MenuPane slightly:
-
-** Fixed a problem where the items array was not observed for content changes when it was set on create (includes unit test).
-** Removed an unnecessary layout change in createChildViews, which also meant that creating a menu pane as a singleton (i.e. with no run loop) would throw warnings.
-** Slightly simplified the code by removing duplicated properties from the superclass SC.PickerPane and reusing the items observer code for initialization.
+  * Fixed a problem where the items array was not observed for content changes when it was set on create (includes unit test).
+  * Removed an unnecessary layout change in createChildViews, which also meant that creating a menu pane as a singleton (i.e. with no run loop) would throw warnings.
+  * Slightly simplified the code by removing duplicated properties from the superclass SC.PickerPane and reusing the items observer code for initialization.
 * Changed the default maximum of SC.ScrollerView to be 0. It was 100 previously, which is arbitrary and incorrect.
 * Removed an extra call to SC.RootResponder's computeWindowSize() each time that a pane is appended. This is unnecessary, since the root responder recomputes its window size property whenever the window actually resizes.
 * Changed SC.MenuItemView's handling of submenus. Previously if the item's submenu was visible and the mouse exited back onto the menu item view, it tried to re-append the same submenu. Instead, it now checks to see if its submenu is already attached before attempting to enter it again.
 * Allows for optimization of SC.RenderContext's setStyle method (Removes V8 "ForIn is not fast case" warning, see http://commondatastorage.googleapis.com/io-2013/presentations/223.pdf).
-* Improved performance of core SC methods: SC.mixin, SC.supplement as well as SC.Function.enhance. SC.mixin and SC.supplement iterated the arguments object to insert a boolean flag to pass to a private function that then iterated its arguments in order to ignore the flag argument, which is totally unnecessary. Instead, SC.mixin and SC.supplement iterate the arguments once and pass the new Array to the private function as a second argument, removing the need for a second iteration.
-
-As well, these three areas all accessed the arguments object to copy it, which requires the browser to instantiate it, which is costly. Instead, we now do a fast copy (similar to this: http://jsperf.com/closure-with-arguments) without instantiating the arguments object.
-
-Finally, by doing a fast copy of arguments these functions are now optimizable by V8, whereas they weren't previously.
-
-Benchmark: SC.mixin & SC.supplement ~ 58% faster
-* Calls adjustLayout on initialization of SC.CollectionView.
-
+* Many developer warnings and errors that would previously appear in production have been restricted to dev-mode only.
+* Improved performance of core SC methods: SC.mixin, SC.supplement as well as SC.Function.enhance. SC.mixin and SC.supplement iterated the arguments object to insert a boolean flag to pass to a private function that then iterated its arguments in order to ignore the flag argument, which is totally unnecessary. Instead, SC.mixin and SC.supplement iterate the arguments once and pass the new Array to the private function as a second argument, removing the need for a second iteration.  
+  
+As well, these three areas all accessed the arguments object to copy it, which requires the browser to instantiate it, which is costly. Instead, we now do a fast copy (similar to this: http://jsperf.com/closure-with-arguments) without instantiating the arguments object.  
+  
+Finally, by doing a fast copy of arguments these functions are now optimizable by V8, whereas they weren't previously.  
+  
+Benchmark: `SC.mixin` & `SC.supplement` ~ 58% faster
+* Calls adjustLayout on initialization of SC.CollectionView.  
+  
 Certain containing views, transitions and specialized layout engines need to know what type of layout their child views will have in order to make the proper adjustments. SC.CollectionView subclasses typically set a width or a height themselves, but when this happens late, the actual layout style of the collection is misunderstood at initialization to be something different.
 * Improved the management of the content view for SC.ContainerView.
 * Improved the default styling of overlay scroller views. Making them look more like natural overlay scrollers in OS X/iOS and making them visible on dark backgrounds.
@@ -109,15 +131,19 @@ Certain containing views, transitions and specialized layout engines need to kno
 
 SC.State had two `observes` helper functions used to be notified when its `enteredSubstates` and `currentSubstates` arrays change. Since these arrays are modified by the owner statechart, the observers needed to be chained enumerable observers. However, this resulted in slower object initialization for each state object and excess observer firing as the entered and current substates change. Instead, we simply notify the target state directly each time that the statechart makes a change to its `enteredSubstates` and `currentSubstates`.
 * Improved SC.ScrollView performance a tiny bit by removing the unnecessary chained binding back from the scrollers to their owner. Scrollers are created automatically by the SC.ScrollView and are not moved between different owners.
+* Added documentation and constants will make SC.PickerPane positioning and customization much easier.
 * Significantly improved performance of SC.PickerPanes attached to element's within an SC.ScrollView.
 
 There were a couple of issues hampering performance for SC.PickerPanes within SC.ScrollViews. The first was that the scroll view observers were too greedy observing (the unfortunately noisy) horizontalScrollOffset and verticalScrollOffset of the scroll view for changes and repositioning on each change. What this meant was that an SC.PickerPane could reposition itself up to 6 times in a single run loop as the content of the scroll view changed even thought the scroll offsets may not have changed at all. Instead, the proper pattern for observing multiple properties (or noisy properties) is to filter the input through an invokeX (i.e. so even though 6 calls to the observer function occur, we only call positionPane once, via invokeOnce). Additionally, we no longer observe the offsets if the scroll view can't even scroll (in either direction). And finally, to ensure that the anchor element is in its new position before we re-position, we actually use invokeNext as our input filter.
 * Fixed several inconsistencies in property referencing within SC.PickerPane. There were multiple places where '.' notation was used instead of get/set. Also tidies up some unclear code.
 * Removed the enabling of run loop logging when SC.LOG_BINDINGS is set. The run loop logs are very noisy and make it harder to follow the binding changes. Also forced some of the logging code into debug builds only.
 * Cancels active transitions of SC.ContainerView when transitionSwap is altered mid-transition. This includes a developer warning.
+* Renamed all `rowHeight` properties to `rowSize` for `SC.CollectionRowDelegate`.
 * Added retina version images for SC.SliderView in Ace.
 * Removed several lines of debugging code from production builds of SC.Observable using @if(debug).
 * Updates to jQuery 1.11.1. Notably, there was a serious memory leak in jQuery 1.8 where the tokenCache grew continuously (because keys in the cache have a " " appended to them and the code tried to delete keys without taking the " " into account).
+* Updates SC.SceneView to support the new SC.ContainerView hardware-accelerable transitions.
+* SC.Color#cssText is now read/write, allowing you to bind it to a user-enterable text field. SC.Color now implements SC.Error and enters an error state when given bad input.
 * Fixed memory leaks in SC.ListView and SC.CollectionView. Since these views add observers to their related objects, they need to also properly remove those observers again when the views themselves are destroyed. Otherwise, when collection views are removed, the observers on the related objects become stranded.
 * SC.Query's internal token tree is now a proper SC.Error when in an error state.
 * Removed all uses of `enhance` within the SC.View `reopen`s in core_foundation. The `_enhance` function is inordinately slow in Firefox (version 31 on OS X). Benchmarks of creating 100 views in a loop takes ~1800ms with the enhance's and only ~38ms without any in Firefox on OS X. In Chrome and Safari on OS X, the difference is negligible.
@@ -147,13 +173,13 @@ cross-platform compatible.
 * Fixes up some bad overrides of interpretKeyEvents. Make sure to use, rather than override, this method in your own code.
 * SC.TextFieldView now supports selection direction when the browser allows.
 * Many webkit-specific properties under the hood – for example, transform CSS – have been replaced with correctly browser-detected versions.
-* VERTICAL_STACK and HORIZONTAL_STACK child layout plugins now support the use of minHeight and minWidth.
+* `SC.View.VERTICAL_STACK` and `SC.View.HORIZONTAL_STACK` child layout plugins now support the use of `minHeight` and `minWidth`.
 * CoreTest, our QUnit like testing suite, now includes a "warn" method to explicitly create a warning.
 * SC.MenuPane will ignore the first item if it is a separator.
 * A number of improvements and backwards-compatibility fixes have been made to the SC.SelectView replacement class found in the experimental frameworks.
 * You can now customize your SC.AlertPane's buttons' isDefault, isCancel, tooltips, layerId and localize properties.
-* Adds developer warning when calling SC.PickerPane#append. You should use SC.PickerPane#popup instead.
-* Adds a layout orientation class to SC.SplitDividerView.
+* Adds developer warning when calling `SC.PickerPane.prototype.append`. A developer should always use `SC.PickerPane.prototype.popup` to display a picker pane.
+* Adds a layout orientation class to `SC.SplitDividerView`.
 * Adds SC.String#escapeCssIdForSelector method to handle '.' and ':' characters, which are valid in CSS IDs but which must be escaped for use in jQuery selectors.
 * In development mode, SC.ChildArray (nested toMany attribute) now has a helpfully verbose toString method.
 * runtime framework no longer requires jQuery. jQuery requirement moved to core_foundation.
@@ -173,6 +199,8 @@ cross-platform compatible.
 * Adds a Developer Error when setting up a nested record attribute with an inverse property (via toOne or toMany).
 * SC.TextFieldView's maxLength property can now be updated live.
 * SC.ContainerView can now take local property paths (e.g. '.localPage.view') as nowShowing.
+* Binding helper methods `SC.Binding.and` and `SC.Binding.or` are now fully operational, including supporting local properties.
+* In the test runner app, adds links to individual test URLs for easier access.
 
 ### DEPRECATIONS & REMOVALS
 

data/lib/frameworks/sproutcore/apps/showcase/controllers/source_tree_controller.js

@@ -28,24 +28,34 @@ Showcase.sources = SC.Object.create(SC.CollectionContent, SC.TreeItemContent, {
           name: "Automatic Image Scaling",
           view: 'Showcase.mainPage.demoView'
         }),
+        SC.Object.create({
+          appPath: 'http://demos.sproutcore.com/big_data_demo',
+          name: "Big Data Lists",
+          view: 'Showcase.mainPage.demoView'
+        }),
         SC.Object.create({
           appPath: 'http://demos.sproutcore.com/child_view_layout_demo',
-          name: "Child View Layouts",
+          name: "Child View Layout Plugins",
           view: 'Showcase.mainPage.demoView'
         }),
         SC.Object.create({
-          appPath: 'http://demos.sproutcore.com/big_data_demo',
-          name: "Displaying Big Data",
+          appPath: 'http://demos.sproutcore.com/data_drag_demo',
+          name: "Dragging Things In",
           view: 'Showcase.mainPage.demoView'
         }),
         SC.Object.create({
           appPath: 'http://demos.sproutcore.com/flot_demo',
-          name: "Flot (or other) Integration",
+          name: "Flot (or other 3rd Party) Integration",
+          view: 'Showcase.mainPage.demoView'
+        }),
+        SC.Object.create({
+          appPath: 'http://demos.sproutcore.com/design_mode_demo',
+          name: "Responsive Design",
           view: 'Showcase.mainPage.demoView'
         }),
         SC.Object.create({
           appPath: 'http://demos.sproutcore.com/lively_view_demo',
-          name: "Transition Plugins",
+          name: "Transition Animation Plugins",
           view: 'Showcase.mainPage.demoView'
         }),
         SC.Object.create({
@@ -207,7 +217,7 @@ Showcase.sourceTreeController = SC.TreeController.create({
   allowsEmptySelection: YES,
 
   /** Update the URL to match the selection. */
-  selectionDidChange: function() {
+  selectionDidChange: function () {
     var content = this.get('content'),
       selection = this.get('selection');
 
@@ -216,7 +226,7 @@ Showcase.sourceTreeController = SC.TreeController.create({
         section;
 
       // Determine which group the selection belongs to.
-      content.get('treeItemChildren').forEach(function(group) {
+      content.get('treeItemChildren').forEach(function (group) {
         if (group.get('treeItemChildren').indexOf(object) >= 0) {
           section = group;
         }

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

@@ -18,7 +18,7 @@ Showcase.mainPage = SC.Page.design({
     header: SC.View.design({
       layout: { borderBottom: 1, height: 50, zIndex: 999 },
       tagName: 'header',
-      render: function(context, firstTime) {
+      render: function (context, firstTime) {
         context.setAttr('role', 'banner');
         context.push('<div class="container"><h1 id="logo"><a href="http://www.sproutcore.com"><img src="' + sc_static('images/logo.png') + '" alt="SproutCore"></a></h1><nav role="navigation"><ul><li><a href="http://www.sproutcore.com/about/">About</a></li><li class="active"><a href="/">Showcase</a></li><li><a href="http://guides.sproutcore.com">Guides</a></li><li><a href="http://docs.sproutcore.com">Docs</a></li><li><a href="http://www.sproutcore.com/community/">Community</a></li><li><a href="http://blog.sproutcore.com">Blog</a></li></ul></nav></div>');
       }
@@ -59,7 +59,27 @@ Showcase.mainPage = SC.Page.design({
   }),
 
   demoView: SC.WebView.design({
-    valueBinding: SC.Binding.oneWay('Showcase.sourceController.appPath')
+    classNames: ['demo-view'],
+    valueBinding: SC.Binding.oneWay('Showcase.sourceController.appPath'),
+    childViews: ['loading'],
+
+    iframeDidLoad: function () {
+      sc_super();
+
+      this.set('isLoading', false);
+    },
+
+    valueDidChange: function () {
+      this.set('isLoading', true);
+    }.observes('value'),
+
+    loading: SC.LabelView.extend({
+      classNames: ['loading-label'],
+      layout: { centerX: 0, centerY: 0, height: 150, width: 250 },
+      escapeHTML: false,
+      isVisibleBinding: SC.Binding.oneWay('.parentView.isLoading'),
+      value: "Loading Demo Application&hellip;"
+    })
   })
 
 });

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

@@ -71,6 +71,20 @@ $theme.views-item-view {
   }
 }
 
+$theme.demo-view {
+  @include background-image(sc_static('cross.png'), sc_static('pixels.png'), linear-gradient(top, rgba(255,255,255,0), rgba(255,255,255,0.5)));
+  background-color: #3a9bee;
+
+  .sc-label-view {
+    &.loading-label {
+      color: white;
+      text-shadow: rgba(0,0,0,0.5) 0 1px 2px;
+      line-height: 45px;
+      font-size: 38px;
+      text-align: center;
+    }
+  }
+}
 
 $theme.welcome-view {
   @include slice('images/pixels.png', $repeat: repeat);

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

@@ -145,12 +145,12 @@ Showcase.viewsPage = SC.Page.create({
       content: [
         Showcase.ViewsItemContent.create({
           title: 'Regular',
-          example: "SC.GridView.extend({  columnWidth: 120,  rowHeight: 58,  contentBinding: SC.Binding.oneWay('Showcase.collectionItems'),  layout: { left: 20, right: 20, top: 20, bottom: 20 },  exampleView: SC.View.extend(SC.Control, {  classNames: ['grid-example-view'],  childViews: ['image', 'title'],  image: SC.ImageView.extend({  layout: { centerX: 0, centerY: 0, height: 24, width: 24 },  valueBinding: SC.Binding.oneWay('.parentView.content.icon')  }),  title: SC.LabelView.extend({  layout: { centerX: 0, bottom: 0, height: 18, width: 120 },  valueBinding: SC.Binding.oneWay('.parentView.content.title')  })  })  })"
+          example: "SC.GridView.extend({  columnWidth: 120,  rowHeight: 58,  contentBinding: SC.Binding.oneWay('Showcase.collectionItems'),  layout: { left: 20, right: 20, top: 20, bottom: 20 },  exampleView: SC.View.extend(SC.Control, {  classNames: ['grid-example-view'],  childViews: ['image', 'title'],  image: SC.ImageView.extend({  layout: { centerX: 0, centerY: 0, height: 24, width: 24 },  valueBinding: SC.Binding.oneWay('.parentView*content.icon')  }),  title: SC.LabelView.extend({  layout: { centerX: 0, bottom: 0, height: 18, width: 120 },  valueBinding: SC.Binding.oneWay('.parentView*content.title')  })  })  })"
         }),
 
         Showcase.ViewsItemContent.create({
           title: 'Scrollable with Minimum Width',
-          example: "SC.ScrollView.extend({ layout: { left: 20, right: 20, top: 20, bottom: 20 },  contentView: SC.GridView.extend({  columnWidth: 200,  rowHeight: 200,  layout: { minWidth: 600 },  contentBinding: SC.Binding.oneWay('Showcase.collectionItems'),  exampleView: SC.View.extend(SC.Control, {  classNames: ['grid-example-view'],  childViews: ['image', 'title'],  image: SC.ImageView.extend({  layout: { centerX: 0, centerY: 0, height: 24, width: 24 },  valueBinding: SC.Binding.oneWay('.parentView.content.icon')  }),  title: SC.LabelView.extend({  layout: { centerX: 0, bottom: 0, height: 18, width: 120 },  valueBinding: SC.Binding.oneWay('.parentView.content.title')  })  })  })  })"
+          example: "SC.ScrollView.extend({ layout: { left: 20, right: 20, top: 20, bottom: 20 },  contentView: SC.GridView.extend({  columnWidth: 200,  rowHeight: 200,  layout: { minWidth: 600 },  contentBinding: SC.Binding.oneWay('Showcase.collectionItems'),  exampleView: SC.View.extend(SC.Control, {  classNames: ['grid-example-view'],  childViews: ['image', 'title'],  image: SC.ImageView.extend({  layout: { centerX: 0, centerY: 0, height: 24, width: 24 },  valueBinding: SC.Binding.oneWay('.parentView*content.icon')  }),  title: SC.LabelView.extend({  layout: { centerX: 0, bottom: 0, height: 18, width: 120 },  valueBinding: SC.Binding.oneWay('.parentView*content.title')  })  })  })  })"
         })
       ],
       exampleHeight: 360

data/lib/frameworks/sproutcore/frameworks/ajax/system/request.js

@@ -115,7 +115,7 @@ SC.Request = SC.Object.extend(SC.Copyable, SC.Freezable,
 
       // This pattern matching strategy was taken from jQuery.
       parts = urlRegex.exec( address.toLowerCase()  );
-      originParts = urlRegex.exec( window.location.href.toLowerCase() );
+      originParts = urlRegex.exec( location.href.toLowerCase() );
 
       return SC.none(parts) ||
         (parts[1] === originParts[1] &&  // protocol
@@ -174,7 +174,7 @@ SC.Request = SC.Object.extend(SC.Copyable, SC.Freezable,
   timeout: null,
 
   /**
-    The body of the request.  May be an object is isJSON or isXML is set,
+    The body of the request.  May be an object if isJSON or isXML is set,
     otherwise should be a string.
 
     @type Object|String
@@ -270,7 +270,7 @@ SC.Request = SC.Object.extend(SC.Copyable, SC.Freezable,
     var ret = {},
         keys = this.COPY_KEYS,
         loc = keys.length,
-        key, listeners, headers;
+        key;
 
     while(--loc >= 0) {
       key = keys[loc];
@@ -524,7 +524,8 @@ SC.Request = SC.Object.extend(SC.Copyable, SC.Freezable,
     @returns {SC.Request} The SC.Request object.
   */
   notify: function(statusOrEvent, target, action) {
-    var args;
+    var args,
+      i, len;
 
     //@if (debug)
     if (statusOrEvent === 'loadend' && SC.Request.WARN_ON_LOADEND) {
@@ -535,7 +536,11 @@ SC.Request = SC.Object.extend(SC.Copyable, SC.Freezable,
     // Normalize arguments
     if (SC.typeOf(statusOrEvent) !== SC.T_NUMBER && SC.typeOf(statusOrEvent) !== SC.T_STRING) {
       // Accept multiple additional arguments (Do so before shifting the arguments!)
-      args = SC.A(arguments).slice(2);
+
+      // Fast arguments access.
+      // Accessing `arguments.length` is just a Number and doesn't materialize the `arguments` object, which is costly.
+      args = new Array(arguments.length - 2); //  SC.A(arguments).slice(2)
+      for (i = 0, len = args.length; i < len; i++) { args[i] = arguments[i + 2]; }
 
       // Shift the arguments
       action = target;
@@ -543,7 +548,15 @@ SC.Request = SC.Object.extend(SC.Copyable, SC.Freezable,
       statusOrEvent = 0;
     } else {
       // Accept multiple additional arguments.
-      args = SC.A(arguments).slice(3);
+
+      if (arguments.length > 3) {
+        // Fast arguments access.
+        // Accessing `arguments.length` is just a Number and doesn't materialize the `arguments` object, which is costly.
+        args = new Array(arguments.length - 3); //  SC.A(arguments).slice(3)
+        for (i = 0, len = args.length; i < len; i++) { args[i] = arguments[i + 3]; }
+      } else {
+        args = [];
+      }
     }
 
     // Prepare listeners for this object and notification target.
@@ -699,8 +712,7 @@ SC.Request.manager = SC.Object.create(
   */
   cancel: function(response) {
     var pending = this.get('pending'),
-        inflight = this.get('inflight'),
-        idx;
+        inflight = this.get('inflight');
 
     if (pending.indexOf(response) >= 0) {
       this.propertyWillChange('pending');