SproutCore

SproutCore aims making building web apps simple and fun.

SproutCore was written following the MVC architecture principles.

Even if it is a JS library, SproutCore has more in common with Cocoa or .NET than jQuery or MooTools.

Sproutcore 2.x has been discontinued, development continues as Ember.

Features:

• MVC architecture
• Concentrates on speed
• HTML 5 ready
• Mobile friendly
• Scalable
• Easy to customize via themes
• Community developed
• Documentation

What is new in this release:

• 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).
• SC.Gesturable & SC.Gesture (SC.TapGesture, SC.PinchGesture, SC.SwipeGesture)
• 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.

What is new in version 1.10.2:

• Added a Developer Error when attempting to add records without id's to relationships.
• Added a debug-mode only developer error to prevent double calls to materializeRecord from within materializeRecord. The result is duplicated objects that appear to be the same record instance but are in fact not, which can be very time-consuming to debug. Hopefully this saves developers a lot of grief.
• Added several *debug-mode only* `toString` methods for easy debugging.
• Added a tiny bit of debug mode only developer support. If manually connecting/disconnecting bindings it's possible to accidentally try to bind to a missing object. The normal stack trace this would produce is hard to follow so we present a more traceable error message with the stack.

What is new in version 1.10.0:

• Allows adjust to be called after animate in the same run loop. Adjust can occur cleanly, which won't affect the animation or it can clash, in which case it will override the animation.
• Improves internal code structure to support optimization by JS engines.
• Makes the conditional that attempts to lock all textfields from receiving focus behind a modal pane, fail more quickly (this also prevents getting the pane on views that may not yet have a pane).

What is new in version 1.9.2:

• Softens the build tools dependency requirements from being ultra-pessimistic (i.e. within a minor version) to being pessimistic (i.e. within a major version).
• Fixes 'repeat' slice for @2x version. It was incorrectly appending @2x to the end of the whole path (ex. /resources/images/image-sliced-from.png@2x instead of /resources/images/image-sliced-from@2x.png).
• Fixes incorrectly named "responder" generator to "state" generator for generating SC.State subclasses.
• Fixes the snake case generator for "sproutcore gen", so that names like 'SCProject' get properly transformed to 'sc_project' and not 's_c_project'.
• Added support for background-size property in Buildtools spriting, this is required for spriting to work properly in retina firefox.
• Fixes inconsistencies and improper syntax in several templates created with "sproutcore gen".
• Fixes missing stylesheet warnings on a clean app generated with "sproutcore gen app" or "sproutcore gen statechart_app" by adding a default stylesheet to the app. Also adds a default stylesheet to a design, when using "sproutcore gen design" (i.e. an SC.Page resource)
• Fixes improper binary search used by SC.ManyArray addInverseRecord that resulted in an infinite loop.
• Fixes bug that allowed the context menu to appear regardless of overriding contextMenu in a view or setting SC.CONTEXT_MENU_ENABLED or isContextMenuEnabled to false. This makes the context menu event handling behave the same as the key, mouse, etc. event handling.
• Fixes actions: deleteForward, deleteBackward, moveLeft, moveRight, selectAll, moveUp and moveDown to be always handled by the TextFieldView element when it has focus.
• Fixes SC.TextFieldView to insert a new line when the enter key is pressed on a text area.
• Fixes the hint value for SC.LabelView so that it will appear when the label has no value and isEditable is true. Includes unit test.
• No longer modifies the underlying items given to an SC.SegmentedView with an overflow menu directly so that we don't invariably dirty the original object.

What is new in version 1.9.1:

• Fixes improper implementation of SC.SelectionSet:constrain.
• Fixes implicit globals in SC.MenuPane, creating a possible memory leak.
• Fixes memory leak with child views of SC.View. The 'owner' property prevented views from being able to be garbage collected when they are destroyed.
• Fixes SC.stringFromLayout() to include all the layout properties.

What is new in version 1.9.0:

• Improves and adds much documentation.
• Adds the Showcase app used on http://showcase.sproutcore.com. This app contains an up-to-date implementation of all of SproutCore's Views and Controls, including code snippets for the many options of each. The app also links into the SproutCore demos, which are being recovered and re-implemented.
• Introduces SC.Color.
• Fixes and enhances the media framework.
• Adds indeterminate SC.ProgressView support.
• Adds `useUnixTime` attribute to SC.DateTime record attribute handlers.
• Adds XHR2 event notification support.

What is new in version 1.8.2:

• Fixed syntax error in Datastore unit test.
• SC.SplitView can now mixin SC.SplitChild.
• Thinned picker pane border divs so that they don't overlap the content view.
• Prevents target property conflict when configuring button targets with SC.AlertPane.
• Changed the aria-orientation of horizontal SC.ScrollView to ‘horizontal' from ‘vertical'.
• Allows SC.CollectionFastPath to work with sparse content by always returning an item view even when content isn't yet available.
• Prevents SC.GridView from iterating over its content array in order to work with sparse content.
• The ‘mobile-safari' body class name is no longer being added in all browsers.
• Enables pasting in SC.TextFieldView to notify that the value changed.

What is new in version 1.8.1:

• Adds missing CSS for SC.PickerPane left and right pointer.
• Tidies up index.rhtml template.
• Adds `useUnixTime` attribute to SC.DateTime record attribute handlers.
• Introduces fixes and enhancements to the media framework.
• Documentation fixes.

What is new in version 1.8:

• A brand new exceptionally detailed three part introduction to SproutCore.
• A new reference guide on the build tools.
• Many many bug fixes. See the CHANGELOG for a complete breakdown.
• The beginnings of a major clean up initiative includes several deprecations. Look for console warnings to indicate deprecated functions and check the CHANGELOG for the full list of deprecations.
• The Desktop framework has been thoroughly updated to include correct WAI-ARIA attributes for improved compatibility with assistive technologies.
• Get a basic statechart structure in new projects using the -statechart switch with sproutcore init or sproutcore gen app.
• Statechart States can be made to represent a route (by default SC.routes routes) and if assigned, the state will be notified any time the app's location changes to match the state's assigned route.

What is new in version 1.7.1 beta:

• New string measurement functions to optimize for string wrapping.
• Added support for autoCorrect and autoCapitalize in TextFields.
• Added back object types previously removed by the refactored SC.Object
• Refactored observer paths code for a more robust handling.
• Rewrite SC.LOG_RUNLOOP_INVOCATIONS - now renamed to SC.LOG_DEFERRED_CALLS - to work with the new runloop implementation.
• Added this SC.RunLoop.kill to terminate cleanly a run loop in case of an error.
• Added the ability to dynamically add substates to a statechart via a state's addSubstate method.
• Updated the statechart tracing logic.
• Updated SC.State. getSubstate now accepts a callback; added getState method; gotoState and gotoHistoryState now use getState
• Updated state's gotoState and gotoHistoryState to allow for a more expressive state arg that now allows for the use of 'parentState'
• Updated SC.State's getSubstate method to allow for path expressions. Also refacted the findFirstRelativeCurrentState method.
• New SC globals to provide information like build mode, build number and locale.

What is new in version 2.0 Beta 3:

• New Ancestor Helpers
• Contexts in Handlebars
• Two-Way Transforms
• SC.Run, Observers & Additional Parameters
• Template Debugging
• Assert Statements
• Fix for unknownProperty

What is new in version 2.0 Beta 2:

• This version eliminates a number of bugs and significantly improves usability issues, as well as fixing compatibility with Internet Explorer 6+ and Opera.

What is new in version 1.6.0:

• SproutCore 1.6 is largely a bug fix release aiming to help provide a more stable experience.

What is new in version 2.0 DP:

• SproutCore 2.0 is a developer preview installation and is still under heavy development and APIs are likely to change.

What is new in version 1.6 Beta:

• Bugfixes to synchronization between SproutCore RecordArray/ManyArray/ChildArray and TemplateCollectionView
• Moved forms to experimental framework
• Moved routing into its own framework
• Improved ability to use table elements in Handlebars templates
• CSS and cross-browser fixes for built-in controls
• Significantly cleaned up in-line documentation

What is new in version 1.5.0:

• WAI-ARIA Support
• SCSS and Data URIs
• Template View
• Modular Loading

What is new in version 1.5.0 RC2:

• Bug Fixes:
• A ton of bugfixes to TemplateView
• TemplateCollectionView now works with RecordArrays
• TemplateCollectionView is now much more efficient when the array it is representing changes
• Fixes a bug in the {{#each}} helper where the content was not updating after it changed
• Fixes a bug where {{bindAttr}} was not working when provided with a class attribute
• Explicitly documented the existence of the itemViewTemplate property in TemplateCollectionView
• Fixes a bug where computed properties were not being invalidated when the first property in the path of their dependent key changed
• Removed some trailing commas that were causing errors in Internet Explorer 7
• Fixes a bug where unit tests were failing on Internet Explorer 7
• Resolves an issue where text fields were not able to be activated on Android devices
• Removed an invalid warning when bindings were connected
• Features:
• Bindings now fire automatically when a property is changed via the debug console
• Substantial improvements to the inline documentation
• Updated QUnit to latest version

Requirements:

• JavaScript enabled on client side