layout-tools-for-susy 0.1.2 → 0.1.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9da75cb63b3401fefbc37d62bf126c5d0da68cc0
-  data.tar.gz: 1a6772cca9a86a94e0f7a6de4457dffd6cb7bf2e
+  metadata.gz: 180cb44dc0e0823b692156346200ad968dc51c4d
+  data.tar.gz: b31858f42a0e5ad6fc619cd1f8576c2302403a23
 SHA512:
-  metadata.gz: 06835402a614d99ada02d19dcf29adb649228489f9633ab9c2729e43ab934cf8a3d652ec573e1a0065657b0f67b08a9e1727779308778b6a327b1098901d3362
-  data.tar.gz: eecd8f4d8e64274ed3e3b2325ea6955106dc7ebc95254554040b407afeebd012d5ff97727aa8558cd8526c1b57dd15faec29be2d859bbd3b2bfa3ddd0f9869be
+  metadata.gz: 8d8876013b0e5c8ac3c780ff16cb0fd7a1b07c7dec0f58d3f6f1715d316bac73ed27d11256c0d25d306b4be3ba2de7638c80c22aabce9321ff5b1bfdeecc3385
+  data.tar.gz: 22fd0900b43e0c5d2af492f495f09de332d67e7b6b3ed1f8cd74986c2c5c5b218d0c4b1e899a4ae2f55d41eb57e83f2738ff10d9c168a83f7a55dd7bf0a2933b

data/README.md

@@ -32,7 +32,7 @@ $ npm install layout-tools-for-susy --save-dev
 This installs layout tools and Susy. Include tools in your stylesheets like this:
 ```scss
 // file: src/stylesheets/styles.scss
-@import '../../node_modules/layout-tools-for-susy/node_modules/susy/sass/susy',
+@import '../../node_modules/susy/sass/susy',
         '../../node_modules/layout-tools-for-susy/stylesheets/layout-tools-for-susy';
 ```
 
@@ -139,7 +139,7 @@ $layouts: (
 @include layout-init($layouts);
 
 ```
-The root properties of the map $layouts represent the different layout contexts. Layout contexts may be layout variations depending on breakpoints or layout settings specific for e.g. a certain template. There are some important settings that will be defined by default if you don’t set them yourself. The `default` layout will be set up by—you guessed it—default with the properties `susy`—containing Susy’s default settings—and `base`—setting a `base__font-size` and `base__line-height` value. To implement your custom layouts, you have to create your settings map like shown above overriding the defaults and adding additional layout specifications. 
+The root properties of the map $layouts represent the different layout contexts. Layout contexts may be layout variations depending on breakpoints or layout settings specific for e.g. a certain template. There are some important settings that will be defined by default if you don’t set them yourself. The `default` layout will be set up by—you guessed it—default with the properties `susy`—containing Susy’s default settings—and `base`—setting a `base__font-size` and `base__line-height` value. To implement your custom layouts, you have to create your settings map like shown above overriding the defaults and adding additional layout specifications.
 
 #### Using layout contexts
 The `default` layout context is the most basic. It will be used everywhere where no other layout context is set (by using the `layout-use` mixin). All other layout contexts extend the `default` context and thus override its settings. If you want to extend a specific context, you can define it using the `extends` property within a layout context’s definition map. In the example above the layout context `L` extends `M`. That means the settings and values you will be working with in the layout context `L` are the result from first merging `M` into `default` and then `L` into the first merge’s result. So within the context of `L` the value of `base__font-size` will be 18px. This behaviour allows you create a sophisticated system of layout settings through controlled inheritance of settings and values.
@@ -224,7 +224,7 @@ $my-component: (
 
 // Use styles
 .my-component {
-  
+
   &__label {
     // Retrieve settings from current layout context
     $label__font-size: layout-get(my-component, label__font-size);
@@ -264,7 +264,7 @@ $layouts: (
       ...
     ),
     breakpoint: (
-      ( 
+      (
         min-width: 480px,
         max-width: 800px,
         min-height: 650px
@@ -308,7 +308,7 @@ As you can see, it's possible to define a single, simple breakpoint through addi
   }
 }
 ```
-That’s it. Easy, isn’t it? 
+That’s it. Easy, isn’t it?
 
 ## More handy helpers
 Layout Tools for Susy come with some more handy helpers.
@@ -343,7 +343,7 @@ body {
 }
 
 .page {
-  
+
   &__header {
     // retrieve font sizes from layout context
     $header__font-size: layout-get(page, header__font-size);
@@ -387,7 +387,7 @@ body {
         }
       }
     }
-  } 
+  }
 }
 ```
 In the example above the ```type-context``` mixin is used to set new local font sizes and line heights as ```em``` values. In contrast to ```type-base``` the base values ```$base__font-size``` and ```$base__line-height``` won’t be altered within the mixins scope. Multiple type contexts can be embedded into each other and the mixin will take track of the relative font sizes and line heights and the necessary calculations.
@@ -429,4 +429,4 @@ background-image: url(const(BG_IMG_PATH) + 'hero_bg.jpg');
 
 ### Tips and tricks
 
-### Contribute
+### Contribute

data/lib/layout-tools-for-susy.rb

@@ -12,6 +12,6 @@ else
 end
 
 module LayoutTools
-  VERSION = "0.1.2"
-  DATE = "2015-12-03"
-end
+  VERSION = "0.1.6"
+  DATE = "2016-01-02"
+end

data/stylesheets/_layout-tools-for-susy.scss

@@ -1,6 +1,3 @@
-// Dependencies
-@import 'susy';
-
 // Config
 @import 'config/constants',
         'config/layouts',

data/stylesheets/mixins/_layout-use.scss

@@ -80,9 +80,9 @@
         }
       }
     }
-  }
-  @else {
-    @content;
+    @else {
+      @content;
+    }
   }
   // restore parent layout settings
   $LAYOUT: $LAYOUT--parent !global;
@@ -91,4 +91,4 @@
   $base__line-height: $base__line-height--parent !global;
   // $local__font-size: $local__font-size--parent !global;
   // $local__line-height: $local__line-height--parent !global;
-}
+}

metadata

@@ -1,41 +1,41 @@
 --- !ruby/object:Gem::Specification
 name: layout-tools-for-susy
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.6
 platform: ruby
 authors:
 - Oliver Wehn
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-12-03 00:00:00.000000000 Z
+date: 2016-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: sass
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ~>
       - !ruby/object:Gem::Version
         version: '3.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ~>
       - !ruby/object:Gem::Version
         version: '3.0'
 - !ruby/object:Gem::Dependency
   name: susy
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ~>
       - !ruby/object:Gem::Version
         version: '2.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ~>
       - !ruby/object:Gem::Version
         version: '2.2'
 description: Organize and handle layouts over multiple breakpoints
@@ -45,8 +45,8 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- CHANGELOG.md
 - README.md
+- CHANGELOG.md
 - lib/layout-tools-for-susy.rb
 - stylesheets/_layout-tools-for-susy.scss
 - stylesheets/config/_constants.scss
@@ -84,17 +84,17 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">="
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">="
+  - - '>='
     - !ruby/object:Gem::Version
       version: 1.3.6
 requirements: []
 rubyforge_project: layout-tools-for-susy
-rubygems_version: 2.4.8
+rubygems_version: 2.0.14
 signing_key: 
 specification_version: 4
 summary: Handy mixins and functions to handle layout settings for multiple breakpoints.