Configure bar-buttons declaratively

[adamdbradley]

<div nav-bar-button="left" class="button" my-super-custom-attribute>
  Content! {{moreContent}}
</div>

nav-bar-button would look for the nearest parent or sibling header-bar and add the button - then when the <div nav-bar-button> element is destroyed (through say an ng-if, or through just a view getting taken out), the button would be removed.

[mlynch]

Is this a replacement for leftButtons and rightButtons?

[ajoslin]

Yeah, a replacement. Mainly to give the dev much more power.

Syntax I think I've settled on. Thoughts?

Shows the power of this syntax with a simple ng-if.

          <ion-nav-buttons side="left" ng-if="shouldHaveLeftButtons">
            <button ng-repeat="i in items" class="button">
              Button {{i}}
            </button>
          </ion-nav-buttons>
          <ion-nav-buttons side="right">
            <button ng-repeat="i in items" class="button">
              Button {{i}}
            </button>
          </ion-nav-buttons>

[mlynch]

I dig it. What happens to the old style?

[ajoslin]

It dies! We could technically deprecate it and use it with this for a version, but since we're bumping a major version up to 1.0 it should be fine.

[somethingnew2-0]

[ajoslin]

Implemented via bfcfae3

[rvanbaalen]

A little explanation on how to transition from the old style to this would be nice.