Commit Graph

146 Commits

Author SHA1 Message Date
mattbryan9
001c1c9f2c fix(app): corrected paths to theme from app.scss 2016-09-19 08:27:24 -05:00
Adam Bradley
7c05d0c0ba fix(di): update dependency injection and default configs 2016-09-16 00:49:09 -05:00
Adam Bradley
f368abee26 test(ion): fix ion tests 2016-09-13 22:16:26 -05:00
Brandy Carney
750cde38e2 refactor(css): scope component css to mode 2016-09-13 16:52:47 -05:00
Adam Bradley
78122c551d refactor(sass): restructure for sass theme updates 2016-09-13 15:54:23 -05:00
Adam Bradley
bf2b6abac5 refactor(export): update component/provider exports 2016-09-13 15:48:25 -05:00
Adam Bradley
d7be8a80c0 test(ngmodule): update to ngmodule 2016-09-13 15:44:02 -05:00
Brandy Carney
55a0257dbc refactor(colors): color should be added as an input instead of directly adding the color to the component
BREAKING CHANGES:

Colors should be passed in the `color` input on components, not added
individually as an attribute on the component.

For example:

```
<ion-tabs primary>
```

Becomes

```
<ion-tabs color=”primary”>
```

Or to bind an expression to color:

```
<ion-navbar [color]="barColor">
   ...
</ion-navbar>
```

```ts
@Component({
  templateUrl: 'build/pages/about/about.html'
})
export class AboutPage {
  barColor: string;

  constructor(private nav: NavController, platform: Platform) {
    this.barColor = platform.is('android') ? 'primary' : 'light';
  }
}
```

Reason for this change:
It was difficult to dynamically add colors to components, especially if
the name of the color attribute was unknown in the template.
This change keeps the css flat since we aren’t chaining color
attributes on components and instead we assign a class to the component
which includes the color’s name.
This allows you to easily toggle a component between multiple colors.
Speeds up performance because we are no longer reading through all of
the attributes to grab the color ones.

references #7467
closes #7087 closes #7401 closes #7523
2016-08-23 17:16:55 -04:00
Brandy Carney
938864e8d0 refactor(button): add ion-button attribute and icon attributes to style buttons
BREAKING CHANGES:

- `<button>` becomes `<button ion-button>`
- `<a button>` becomes `<a ion-button>`
- `<button ion-item>` does not get the `ion-button` attribute
- Buttons inside of `<ion-item-options>` do get the `ion-button`
attribute
- Removed the `category` attribute, this should be passed in
`ion-button` instead.
- Button attributes added for icons in buttons: `icon-only`,
`icon-left`, and `icon-right`

closes #7466
2016-08-16 17:11:02 -04:00
Dan Bucholtz
e244d09eaa docs(app): documented setEnabled, setScrollDisabled methods
documented setEnabled, setScrollDisabled methods
2016-08-10 09:38:08 -05:00
mhartington
4cfb5a48ee doc(): update private 2016-08-06 12:26:06 -04:00
Adam Bradley
3c493652b2 test(): update to public navCtrl convention 2016-08-04 13:50:15 -05:00
Adam Bradley
ff3daeed6c chore(): remove css-scrollbar styles 2016-08-04 12:58:50 -05:00
Brandy Carney
087e2f2480 revert(tabs): undo commit that removes tab sub pages
Fix advanced tabs test

This reverts
https://github.com/driftyco/ionic/commit/743de19ae898e83375b51ef9c376225
c8e63f0ef
2016-07-28 15:28:55 -05:00
Manu Mtz.-Almeida
44ab527f74 fix(backdrop): flicker in UIWebView 2016-07-19 13:33:44 -07:00
Manu Mtz.-Almeida
ac8e4dce06 style(all): tslinter warnings 2016-07-19 13:31:46 -07:00
perry
4f52135c13 Revert "Revert "Merge branch 'master' of https://github.com/driftyco/ionic""
This reverts commit 4a6086c1f8.
2016-07-18 19:40:03 -05:00
perry
4a6086c1f8 Revert "Merge branch 'master' of https://github.com/driftyco/ionic"
This reverts commit 8945bf906d, reversing
changes made to f4fac225fa.
2016-07-18 19:24:56 -05:00
Manu Mtz.-Almeida
cac378f35b fix(menu): only one menu can be opened at a time
fixes #6826
2016-07-17 20:42:29 -05:00
Adam Bradley
0a7d865975 refactor(nav): create NavControllerBase and public abstract class
Use NavController as the public API, and NavControllerBase as the
internal API. Refactored all app/nav/tabs unit tests and created
centralized mocking functions.
2016-07-15 15:54:56 -05:00
Manu Mtz.-Almeida
5909fa4ba5 refactor(gestures): no longer use hammer for drag gestures 2016-07-15 11:23:36 -05:00
Manu Mtz.-Almeida
72c24bc927 feat(gesture-controller): disable/enable scrolling 2016-07-14 00:52:43 +02:00
Adam Bradley
1ae6619367 Merge pull request #7212 from manucorporat/gesture-controller
New Gesture controller
2016-07-13 15:24:12 -05:00
Manu Mtz.-Almeida
9f19023cb9 feat(gesture): Introducing new gesture controller 2016-07-13 22:11:38 +02:00
Adam Bradley
743de19ae8 refactor(tabs): remove tabSubPages UI
The Material Design spec has added “Bottom Navigation”, which is what
Ionic calls “Tabs”. Ionic’s MD mode now follows the updated Material
Design spec with the tabbar placed on the bottom. Additionally, any tab
sub pages do not automatically cover up the tabbar. Covering up the
tabbar is still possible by using a modal, however, it is no longer a
default feature for MD mode.
2016-07-12 20:28:40 -05:00
Adam Bradley
cca3309f4c chore(nav): create nav-interfaces file 2016-07-11 23:24:25 -05:00
Brandy Carney
0d33adafe4 chore(sass): fix linter error 2016-07-07 13:09:52 -04:00
Brandy Carney
41064bf2be refactor(tabs): rename tab input/config options to be more clear/consistent
BREAKING CHANGES:

Tab input/config options have been renamed. The following options were
renamed:

- `tabbarHighlight` -> `tabsHighlight`
- `tabbarLayout` -> `tabsLayout`
- `tabSubPages` -> `tabsHideOnSubPages`
- `tabbarPlacement` -> `tabsPlacement`

The previous names have been deprecated. They will still work in the
current release but will be removed in the future so please update to
the new names.

references #7143
2016-07-07 13:09:00 -04:00
Adam Bradley
f1433c6314 refactor(backdrop): place disable-scroll class on ion-app 2016-07-01 21:44:53 -05:00
Adam Bradley
e4bbcc667a fix(scroll): fix scrolling after switching tabs
Closes #7154
2016-07-01 20:13:49 -05:00
Adam Bradley
d8782df933 chore(): remove old deprecated warnings 2016-07-01 01:11:45 -05:00
Adam Bradley
4d56219a4c refactor(forms): upgrade to @angular/forms 2016-06-30 21:54:48 -05:00
Adam Bradley
845a516375 fix(activator): do not activate elements while scrolling
Closes #7141
2016-06-30 10:36:03 -05:00
Adam Bradley
55a5e83020 fix(nav): fix menuCtrl reference in swipe back 2016-06-29 21:12:22 -05:00
Adam Bradley
3cd31c3d17 fix(menu): fix content going under header
Closes #7084
2016-06-28 16:22:39 -05:00
Adam Bradley
4980659bd6 test(overlay): use injectable overlay controllers 2016-06-28 15:20:42 -05:00
Adam Bradley
215c6d846c refactor(overlays): inject overlay providers
BREAKING CHANGES:

- Overlay components, such as Alert or Modals, should now be created
using its injected provider.
- Overlays now have the `present()` method on the overlay’s instance,
rather than using `nav.present(overlayInstance)`.
- All overlays now present on top of all app content, to include menus.
- Below is an example of the change to `Alert`, but the pattern is the
same for all overlays: ActionSheet, Loading, Modal, Picker, Popover,
Toast

WAS:

```
import { NavController, Alert } from ‘ionic-angular’;

constructor(private nav: NavController) {
}

doAlert() {
  let alert = Alert.create({
    title: 'Alert',
  });
  this.nav.present(alert);
}
```

NOW:

```
import { AlertController } from ‘ionic-angular’;

constructor(private alertCtrl: AlertController) {
}

doAlert() {
  let alert = this.alertCtrl.create({
    title: 'Alert'
  });
  alert.present();
}
```
2016-06-28 15:18:09 -05:00
Brandy Carney
3db67f90fb fix(content): set footer height to 0 so it won't be undefined 2016-06-24 15:29:08 -04:00
Adam Bradley
7842991c1a fix(nav): auto set iOS black transition bg via css 2016-06-20 14:12:13 -05:00
Adam Bradley
3a7addf7b0 feat(toolbar): control toolbar borders on top/bottom
Toolbars can be stacked up vertically in `<ion-header>`,
`<ion-content>`, and `<ion-footer>` elements. However, toolbars also
come with borders on both the top and bottom of the toolbar. To give
developers full control of the design, Ionic also includes the
`no-border-bottom` and `no-border-top` attributes. For example,
sometimes two vertically stacked toolbars may have different background
colors, in this case it might be best to leave a border between them.
However, if they have the same background color, the app may look best
without a border between them. The main point here is, it's entirely up
to the app's design to decide when and when not to show borders between
toolbars, and to do so then each toolbar can individually set
`no-border-bottom` and `no-border-top` attributes.
2016-06-20 12:01:21 -05:00
Adam Bradley
2d680896e7 fix(tabs): hide tab's navbar when a page comes without a navbar
Closes #5556
2016-06-18 00:20:08 -05:00
Adam Bradley
cdb1f8503c chore(sass): move z-index vars to separate file, remove unused vars 2016-06-17 23:21:15 -05:00
Brandy Carney
1d8ba4a5e7 fix(toolbar): position toolbar relative and add z-index 2016-06-17 16:15:31 -04:00
Adam Bradley
1a8f6d745d test(header): update header markup 2016-06-17 11:43:30 -05:00
Adam Bradley
d13fa4e2cf refactor(structure): allow content to scroll under headers/footers 2016-06-16 11:28:02 -05:00
Dan Bucholtz
3e451cce67 style(tslint): fixed linting error for new check-else rule
fixed linting error for new check-else rule
2016-06-14 22:34:53 -05:00
Adam Bradley
9f293e8549 feat(navPop): add nav pop method on the app instance 2016-06-08 10:42:19 -05:00
Dan Bucholtz
9b78aeba77 fix(click-block): fix for the click block logic
fix for the click block logic
2016-06-08 10:27:56 -05:00
Brandy Carney
c74b3f7422 fix(config): pass custom providers in the bootstrap of the app
references #6685
2016-06-01 17:15:39 -04:00
Adam Bradley
03f4511635 chore(tslint): fix noImplicitAny errors 2016-05-31 18:40:29 -05:00