X-Git-Url: https://gerrit.automotivelinux.org/gerrit/gitweb?a=blobdiff_plain;ds=sidebyside;f=afb-client%2Fbower_components%2Ffoundation-apps%2FCHANGELOG.md;fp=afb-client%2Fbower_components%2Ffoundation-apps%2FCHANGELOG.md;h=75f509630f56411f4ef5ebaa15e4c218ec1709e0;hb=5b1e6cc132f44262a873fa8296a2a3e1017b0278;hp=0000000000000000000000000000000000000000;hpb=f7d2f9ac4168ee5064580c666d508667a73cefc0;p=src%2Fapp-framework-demo.git diff --git a/afb-client/bower_components/foundation-apps/CHANGELOG.md b/afb-client/bower_components/foundation-apps/CHANGELOG.md new file mode 100644 index 0000000..75f5096 --- /dev/null +++ b/afb-client/bower_components/foundation-apps/CHANGELOG.md @@ -0,0 +1,301 @@ +# Version 1.1 â Weisshorn + +*March 17, 2015* + +### General + +- **The CLI has been updated to version 1.1.** It includes a streamlined install process, better error-handling, better cross-platform support, and *no Ruby dependency*. Run `npm update -g foundation-cli` to get it. +- **The documentation is way better.** We did a sweep of every docs page to fix typos, improve examples, and generally make things more clear. Enjoy! +- **Foundation for Apps is now libsass-first.** We're still testing the codebase in both Ruby Sass 3.4+ and libsass 3.1+, but our documentation and template stack now compile with libsass by default. **This means Ruby is no longer a hard dependency of the framework.** +- **Directive templates are now compiled to one file.** We're using [ng-html2js](https://github.com/yaru22/ng-html2js) to package up all of our directive templates into a single JavaScript file. This means you no longer need to include the `components` folder in a public directory! This method still works, but you can also just include the `templates.js` file and you're good to go. + - The templates file is included in the Bower and npm packages, under `dist/js/foundation-apps-templates.js`. + - A third CDN URL has been created for the template files. + - Thanks to @MikaAK for submitting the pull request that implemented this! + +### Sass Variable Changes + +These Sass variables changed. If you're upgrading an existing project, you'll need to update your `_settings.scss` file manually. + +**Added:** `$button-background-hover: scale-color($button-background, $lightness: -15%)` +**Added:** `$motion-class-showhide: (in: "ng-hide-remove", out: "ng-hide-add");` +**Added:** `$motion-class-showhide-active: (in: "ng-hide-remove-active", out: "ng-hide-add-active");` +**Added:** `$input-background-disabled: smartscale($input-background)` +**Added:** `$input-cursor-disabled: not-allowed` +**Changed:** `$button-tag-selector` is now `false` (previously `true`) +**Removed:** `$panel-animation-speed` + +**You don't need to add the new variables to your settings file,** unless you want to change their default values. + +**The old variables are still in the codebase, but aren't being used.** They'll be permanently removed in version 1.2. + +### Template Changes + +- Sass is now compiled using libsass. +- Directive templates are compiled into a `templates.js` file, instead of being referenced using hardcoded paths to HTML files. +- **If you have an existing project, you don't need to change anything to upgrade to v1.1.** + +### New Features + +- **Improved view animation!** In and out animations on views will now play simultaneously. Thanks to @AntJanus, @stryju, and @jeanieshark for all their hard work in solving this difficult problem! +- `ui-view` elements no longer need the attribute `ng-class="['ui-animation']"` to animate properly; just having `ui-view` is enough. +- Prior to v1.1, view animations only worked if the states were created using our front matter routing plugin. Now you can enable view animation in manually-defined states by adding an `animation` property to the state object. + +```js +$stateProvider + .state('home', { + url: '/', + templateUrl: 'templates/home.html', + animation: { + enter: 'slideInDown', + leave: 'fadeOut' + } + }); +``` + +- #461: Added a `$background-hover` parameter to the `button-style()` mixin. You can pass in a color, or the `auto` keyword to automatically set a color based on the `$background` parameter. +- #462: Added styles for disabled form elements. They're automatically applied to any `` element with the `disabled` or `readonly` attributes, or a `