Ionic Framework Beta Changes

Right now the library’s latest cut is 1.0.0-beta.12 “krypton-koala” (2014-09-10). Lets take a quick glance at some the new features:

Features

  • $ionicBody: service to simplify body ele interaction (2c3f1c9f)
  • $ionicConfigProvider: add $ionicConfigProvider (2643cffc)
  • $ionicScrollDelegate: expose zoomBy and zoomTo methods (029f8f33, closes #1977)
  • ionContent: add locking option (af229072, closes #2034)
  • ionScroll: add locking option (cc8f31d8, closes #2034)
  • popover: support popping from bottom or top of screen (5d06c4ae, closes #1986)
  • scroll-content: add 1px padding-top (e5b5906c)
  • splitView: expose side menu on large viewport (b69aa548)
  • templateCache: automatically cache template files to prevent flicker on page navigation and imp (944a92b0)
  • collectionRepeat: other children of ion-content element fit in (7ddb57e6, closes #1920, #1866, #1380)
  • popover: created popovers (c1215aa3)
  • tabs: Expand striped android style tab functionality. Closes 1694 (ddda809b)
  • $ionicLoading: add $ionicLoadingConfig constant for default options (26ca840d, closes #1800)
  • checkbox: add disabled and emotion styles to ion-checkbox. and #1509 (79fb1e49, closes #1683)
  • ionModalView: ion-modal-view to wrap template instead of <div class="modal"> (ed4f2288, closes #1668)
  • ionSideMenu: add edge-drag-threshold, delegate edgeDragThreshold() (ba56bb98, closes #1570)
  • ionSlideBox: add ‘auto-play’ attr to optionally disable auto-play (8f808609, closes #1552)
  • tab: options ‘hidden’ attribute for tabs., #1673 (bb6976ad, closes #1666)

Breaking Changes

  • ion-radio no longer has an isolate scope. This will break your radio only if you were relying upon the radio having an isolate scope: if you were referencing $parent.value as the ng-disabled attribute, for example.

Change your code from this:


<ion-radio ng-disabled=""></ion-radio>

To this:


<ion-radio ng-disabled=""></ion-radio>

(53c437e2)

* ion-toggle no longer has an isolate scope. This will break your toggle only if you were relying upon the toggle having an isolate scope: if you were referencing $parent.value as the ng-disabled attribute, for example.

Change your code from this:

To this:

(537b29d0) * Reordering with ion-reorder-button no longer changes the order of the items in the DOM.

This change will only break your list if you were not using the onReorder callback as described in the documentation.

Before, while reordering an element in a list Ionic would swap the elements underneath as the reordering happened. This sometimes caused errors with angular’s ngRepeat directive.

Now, reordering an element in a list does not change the order of elements in the DOM. It is expected that the end developer will use the index changes given in the onReorder callback to reorder the items in the list. This is simple to do, see the examples in the ionReorderButton documentation.

(ba1859b3)

* ion-toggle no longer has an isolate scope. This will break your toggle only if you were relying upon the toggle having an isolate scope: if you were referencing $parent.value as the ng-disabled attribute, for example.

Change your code from this:

To this:

(537b29d0) * Reordering with ion-reorder-button no longer changes the order of the items in the DOM.

This change will only break your list if you were not using the onReorder callback as described in the documentation.

Before, while reordering an element in a list Ionic would swap the elements underneath as the reordering happened. This sometimes caused errors with angular’s ngRepeat directive.

Now, reordering an element in a list does not change the order of elements in the DOM. It is expected that the end developer will use the index changes given in the onReorder callback to reorder the items in the list. This is simple to do, see the examples in the ionReorderButton documentation.

(ba1859b3)

Stay tuned!

comments powered by Disqus