From 2f4ebb85cf6cc2b20fa393db3964692749c900fd Mon Sep 17 00:00:00 2001
From: Perry Govier <perrygovier@users.noreply.github.com>
Date: Fri, 2 Jan 2015 16:35:59 -0600
Subject: [PATCH] docs(navbar): getting rid of alternate use section since it's
 now an anti-pattern

---
 js/angular/directive/navBar.js | 24 ------------------------
 1 file changed, 24 deletions(-)

diff --git a/js/angular/directive/navBar.js b/js/angular/directive/navBar.js
index 636e9b2b44..89ab7893e2 100644
--- a/js/angular/directive/navBar.js
+++ b/js/angular/directive/navBar.js
@@ -43,30 +43,6 @@
  * to the top when tapped.  Set no-tap-scroll to true to disable this behavior.
  *
  * </table><br/>
- *
- * ### Alternative Usage
- *
- * Alternatively, you may put ion-nav-bar inside of each individual view's ion-view element.
- * This will allow you to have the whole navbar, not just its contents, transition every view change.
- *
- * This is similar to using a header bar inside your ion-view, except it will have all the power of a navbar.
- *
- * If you do this, simply put nav buttons inside the navbar itself; do not use `<ion-nav-buttons>`.
- *
- *
- * ```html
- * <ion-view view-title="myTitle">
- *   <ion-nav-bar class="bar-positive">
- *     <ion-nav-back-button>
- *     </ion-nav-back-button>
- *     <div class="buttons primary-buttons">
- *       <button class="button">
-            Button
- *       </button>
- *     </div>
- *   </ion-nav-bar>
- * </ion-view>
- * ```
  */
 IonicModule
 .directive('ionNavBar', function() {