add  tag to posts

Rafael Machado · Mateusz Matoszko · commit 7c2781d7f134 · 2015-11-06T14:21:23.000+01:00
add social buttons on front page
diff --git a/.themes/nshint/sass/custom/_styles.scss b/.themes/nshint/sass/custom/_styles.scss
@@ -28,6 +28,13 @@ body {
 		background: #FFFFFF;
 	}
 
+	.social {
+		padding-top: 30px;
+		img {
+			padding-right: 20px;
+		}
+	}
+
 	> header {
 		background: #ffffff;
 		padding-top: 3em;
@@ -200,8 +207,6 @@ article {
 
 	.blog-index {
 		article {
-			padding-top: 4em;
-
 			header {
 				padding-top: 2em;
 				padding-left: 0;
diff --git a/.themes/nshint/sass/partials/_blog.scss b/.themes/nshint/sass/partials/_blog.scss
@@ -3,7 +3,6 @@ article {
   a { @extend .force-wrap; }
   header {
     position: relative;
-    padding-top: 2em;
     margin-bottom: 1em;
     h1 {
       margin: 0;
diff --git a/.themes/nshint/sass/partials/_navigation.scss b/.themes/nshint/sass/partials/_navigation.scss
@@ -40,7 +40,6 @@ body > nav {
     ul {
       @include horizontal-list(0);
       display: inline-block;
-      padding-top: .15em;
     }
     ul.subscription {
       margin-left: .8em;
diff --git a/.themes/nshint/source/_includes/article.html b/.themes/nshint/source/_includes/article.html
@@ -28,9 +28,9 @@ <h1 class="entry-title">{% if site.titlecase %}{{ page.title | titlecase }}{% el
   {% capture excerpted %}{{ content | has_excerpt }}{% endcapture %}
   {% if excerpted == 'true' %}
     <footer>
-      <a rel="full-article" href="{{ root_url }}{{ post.url }}">{{ site.excerpt_link }}</a>
+      <a rel="full-article" href="{{ root_url }}{{ post.url }}">{{ site.excerpt_link }}</a> 
     </footer>
   {% endif %}
 {% else %}
 <div class="entry-content">{{ content }}</div>
-{% endif %}
+{% endif %}
diff --git a/.themes/nshint/source/_includes/custom/header.html b/.themes/nshint/source/_includes/custom/header.html
@@ -1,4 +1,9 @@
 {% if site.title %}
-	<!-- <div class="header-title"><a href="{{ root_url }}/">{{ site.title }}</a></div> -->
 	<a href="{{ root_url }}/"><img src="{{ root_url }}/images/nshint_logo.png" /></a>
+	<br/>
+	<div class="social">
+		<a href="{{ site.social.twitter }}"><img src="{{ root_url }}/images/twitter.png" /></a>
+		<a href="{{ site.social.github }}"><img src="{{ root_url }}/images/github.png" /></a>
+		<a href="{{ site.social.rss }}"><img src="{{ root_url }}/images/rss.png" /></a>
+	</div>
 {% endif %}
diff --git a/_config.yml b/_config.yml
@@ -44,7 +44,7 @@ highlighter: pygments # default python pygments have been replaced by pygments.r
 paginate: 10          # Posts per page on the blog index
 paginate_path: "posts/:num"  # Directory base for pagination URLs eg. /posts/2/
 recent_posts: 5       # Posts in the sidebar Recent Posts section
-excerpt_link: "Read on &rarr;"  # "Continue reading" link text at the bottom of excerpted articles
+excerpt_link: "Read on"  # "Continue reading" link text at the bottom of excerpted articles
 excerpt_separator: "<!--more-->"
 
 titlecase: true       # Converts page and post titles to titlecase
@@ -100,6 +100,11 @@ google_analytics_tracking_id: UA-66445219-1
 # Facebook Like
 facebook_like: false
 
+social:
+  twitter: https://twitter.com/nshintio
+  github: https://github.com/nshintio/
+  rss: http://nshint.io/atom.xml
+
 author_ids: [matt, woj, rafa, marcin, kondrat]
 authors: 
    matt:
diff --git a/sass/custom/_styles.scss b/sass/custom/_styles.scss
@@ -28,6 +28,13 @@ body {
 		background: #FFFFFF;
 	}
 
+	.social {
+		padding-top: 30px;
+		img {
+			padding-right: 20px;
+		}
+	}
+
 	> header {
 		background: #ffffff;
 		padding-top: 3em;
@@ -200,8 +207,6 @@ article {
 
 	.blog-index {
 		article {
-			padding-top: 4em;
-
 			header {
 				padding-top: 2em;
 				padding-left: 0;
diff --git a/sass/partials/_blog.scss b/sass/partials/_blog.scss
@@ -3,7 +3,6 @@ article {
   a { @extend .force-wrap; }
   header {
     position: relative;
-    padding-top: 2em;
     margin-bottom: 1em;
     h1 {
       margin: 0;
diff --git a/sass/partials/_navigation.scss b/sass/partials/_navigation.scss
@@ -40,7 +40,6 @@ body > nav {
     ul {
       @include horizontal-list(0);
       display: inline-block;
-      padding-top: .15em;
     }
     ul.subscription {
       margin-left: .8em;
diff --git a/source/_includes/article.html b/source/_includes/article.html
@@ -28,9 +28,9 @@ <h1 class="entry-title">{% if site.titlecase %}{{ page.title | titlecase }}{% el
   {% capture excerpted %}{{ content | has_excerpt }}{% endcapture %}
   {% if excerpted == 'true' %}
     <footer>
-      <a rel="full-article" href="{{ root_url }}{{ post.url }}">{{ site.excerpt_link }}</a>
+      <a rel="full-article" href="{{ root_url }}{{ post.url }}">{{ site.excerpt_link }}</a> 
     </footer>
   {% endif %}
 {% else %}
 <div class="entry-content">{{ content }}</div>
-{% endif %}
+{% endif %}
diff --git a/source/_includes/custom/header.html b/source/_includes/custom/header.html
@@ -1,4 +1,9 @@
 {% if site.title %}
-	<!-- <div class="header-title"><a href="{{ root_url }}/">{{ site.title }}</a></div> -->
-	<a href="{{ root_url }}/"><img src="{{ root_url }}/images/nshint_logo.png" height="120px" /></a>
+	<a href="{{ root_url }}/"><img src="{{ root_url }}/images/nshint_logo.png" /></a>
+	<br/>
+	<div class="social">
+		<a href="{{ site.social.twitter }}"><img src="{{ root_url }}/images/twitter.png" /></a>
+		<a href="{{ site.social.github }}"><img src="{{ root_url }}/images/github.png" /></a>
+		<a href="{{ site.social.rss }}"><img src="{{ root_url }}/images/rss.png" /></a>
+	</div>
 {% endif %}
diff --git a/source/_posts/2015-06-23-toggle-slow-animations.markdown b/source/_posts/2015-06-23-toggle-slow-animations.markdown
@@ -10,7 +10,7 @@ categories:
 iOS Simulator has a feature that slows animations, you can toggle it either by pressing `⌘T` or choosing `Debug > Toggle Slow Animations in Frontmost App`. It's very useful, but what if we want to do the same on device? It's easy, fast and simple.
 
 `CALayer` has a property called `speed`, which is a time multiplier. This means that if we have an animation with a duration of 1 second, and set the layer's speed to 2, it'll take just 0.5 seconds to finish. The best thing about it is that it's related to the parent layer. So when we change the speed of a particular `CALayer`, every child layer will be affected. So, if we change `UIWindow` layer speed, every `CALayer` in our application will perform animations with that custom speed value. That leaves us with this two extensions:
-
+<!--more-->
 ``` swift
 extension UIWindow {
 
diff --git a/source/_posts/2015-06-25-storyboard-localization.markdown b/source/_posts/2015-06-25-storyboard-localization.markdown
@@ -10,7 +10,7 @@ categories:
 Internationalizing the users interface in Xcode is [really easy](https://developer.apple.com/library/ios/documentation/MacOSX/Conceptual/BPInternational/InternationalizingYourUserInterface/InternationalizingYourUserInterface.html). Xcode separates all the texts from your views in a dictionary. However, we can make it better, using `extensions` and `@IBDesignables`. How handy would it be, if setting localized strings were as easy as the following?<br/><br/>
 {% img center /images/storyboard-localization/1.png %}
 <br/>
-
+<!--more-->
 Easier than that, are the `extensions` to unleash this fancy feature.
 
 ```swift
diff --git a/source/_posts/2015-06-27-tracking-drawing-errors.markdown b/source/_posts/2015-06-27-tracking-drawing-errors.markdown
@@ -17,7 +17,7 @@ Do you sometimes see this in your code while performing custom drawing using <co
 <Error>: CGContextDrawImage: invalid context 0x0
 <Error>: CGContextRestoreGState: invalid context 0x0
 ```
-
+<!--more-->
 And as always is very hard to track, because you cannot exactly say which draw command actually cause this or where does it comes from.
 But there is a simple solution to this:
 
diff --git a/source/_posts/2015-07-02-fixing-uicatalog-invalid-asset-error.markdown b/source/_posts/2015-07-02-fixing-uicatalog-invalid-asset-error.markdown
@@ -11,7 +11,7 @@ categories:
 CUICatalog: Invalid asset name supplied: (null), or invalid scale factor: 2.000000
 ```
 This error may happen when you try to load `UIImage` and your asset string is `nil`. For now this will not crash your app but may case some future problems. This may also lead to some UI inconsistency. To track down issue like this we need to set symbolic breakpoint:
-
+<!--more-->
 {% img center /images/uicatalog_invalid_asset/null_asset.png %}  
 
 Add `$arg3 == nil` condition (on Simulator) or `$r0 == nil` condition on iPhone device. This will stop executing your app exactly in the line where you try to load broken image.
diff --git a/source/_posts/2015-07-04-how-to-animate-uilabel-properties.markdown b/source/_posts/2015-07-04-how-to-animate-uilabel-properties.markdown
@@ -18,7 +18,7 @@ self.someLabel.textColor = [UIColor blueColor];
 				  		self.someLabel.textColor = [UIColor redColor];
 				  	}];
 ```
-
+<!--more-->
 But there is a simple solution. Instead of animating property we will perform transition on object itself.
 
 Using `transitionWithView` should solve our problem:
diff --git a/source/_posts/2015-07-05-working-with-coretelephony-framework.markdown b/source/_posts/2015-07-05-working-with-coretelephony-framework.markdown
@@ -9,7 +9,7 @@ categories:
 Have you ever encountered a situation where you want to build some record or music app ? But you need to somehow react on a phone call which in many cases break recording or playing in more advanced app (mostly when it comes to `CoreAudio`) or switch UI in case of call? `CoreTelephony` is a great library which will help in most of the situations.  
 
 To detect phone call on your iPhone or iPad app (this may be the case now when we use continuity) simply use this piece of code:  
-
+<!--more-->
 ```objc
 #import <CoreTelephony/CTCall.h>
 #import <CoreTelephony/CTCallCenter.h>
diff --git a/source/_posts/2015-07-12-shared-breakpoints.markdown b/source/_posts/2015-07-12-shared-breakpoints.markdown
@@ -9,7 +9,7 @@ categories:
 Developing multithreaded application is not something new and it's become more and more popular with multicore processors. One thing it's for sure, debugging multithread applications is tough.
 
 iOS has some gotchas regarding multithread, things that if you don't respect, may cause your application to crash or hang the users interface, for example:
-
+<!--more-->
 - Animations outside the main thread, may crash the application.<br/>
 - Performing network requests on the main thread, will hang the users interface.<br/>
 
diff --git a/source/_posts/2015-07-16-uicollectionviews-now-have-easy-reordering.markdown b/source/_posts/2015-07-16-uicollectionviews-now-have-easy-reordering.markdown
@@ -8,7 +8,7 @@ categories:
 ---
 
 I'm a huge fan of `UICollectionView`. It's way more customizable than his older brother `UITableView`. Nowadays I use collection view even more often than table view. With iOS 9 it supports easy reordering. Before it wasn't possible out of the box, and to do so means painful work. Let's have look at the API. You can find the accompanying Xcode project [on GitHub](https://github.com/nshintio/uicollectionview-reordering).
-
+<!--more-->
 The easiest way to add easy reordering is to use `UICollectionViewController`. It now has a new property called `installsStandardGestureForInteractiveMovement` which adds standard gestures to reorder cells. This property is `true` by default, which means that there's only one method we should to override to get things working.
 
 ``` swift
diff --git a/source/_posts/2015-07-23-run-script-phase-reporting.markdown b/source/_posts/2015-07-23-run-script-phase-reporting.markdown
@@ -8,7 +8,7 @@ categories:
 ---
 Bash scripts are commonly used in Mac/iOS development to make repetitive operations hands-free. However sometimes things go wrong and in a perfect world I’d like to be properly informed about the errors.
 Here comes view called „Report Navigator”, which displays any type of errors, warnings at compile time of Objective-C/Swift, or even while typing new lines of code. Let me show how to use the Report Navigator.
-
+<!--more-->
 As usual create new `Run Script Phase` and insert your Bash script:
 
 {% img center /images/bash-scripts-marks/bash-scripts-new-script-phase.png %}  
diff --git a/source/_posts/2015-08-03-law-of-demeter.markdown b/source/_posts/2015-08-03-law-of-demeter.markdown
@@ -7,7 +7,7 @@ author: rafa
 categories:
 ---
 You may haven't heard about this law or if you have, you may have wondered [who's this Demeter guy](http://homepages.cwi.nl/~storm/teaching/reader/LieberherrHolland89.pdf). Regardless of it, the Law Of Demeter (LoD) is a foundation concept that's used among several design patterns, to wit: Delegate, Proxy, Façade, Adapter and Decorator. Therefore, you probably are already taking advantage of this Law, knowing it or not.
-
+<!--more-->
 There's a particular situation that occurs with iOS, that's perfect for applying the LoD. Sometimes it's needed to call method in our `UIApplicationDelegate`. The common way of doing that is the following:
 
 ```swift
diff --git a/source/_posts/2015-08-04-using-sql-as-date-formatter.markdown b/source/_posts/2015-08-04-using-sql-as-date-formatter.markdown
@@ -8,7 +8,7 @@ categories:
 ---
 
 This post is a quick update to [Vombat's blog post](http://vombat.tumblr.com/post/60530544401/date-parsing-performance-on-ios-nsdateformatter) about using SQL instead of `NSDateFormatter` when it comes to parsing dates in your project. If you don't read it yet, I will highly recommend to do it now. This time we will use Swift to make same measurements.
-
+<!--more-->
 TL;DR:
 
 You can use sql database function `strftime` to get UNIX time from e.g.: ISO8061 date string.
diff --git a/source/_posts/2015-08-09-nsprogressreporting.markdown b/source/_posts/2015-08-09-nsprogressreporting.markdown
@@ -11,7 +11,7 @@ In iOS7 and OS X 10.9 Apple released NSProgess. Its a nice, helpful piece of cod
 If you finally [find a proper way to use it](http://oleb.net/blog/2014/03/nsprogress/) it can be very beneficial.
 
 Besides of helpfull UserInfo object keys which give us comprehensive text information about progress of our tasks in proper language, NSProgress was supposed to provide us way of compositioning objects into trees. However, first version of class allowed this in an implicit way which does not look very clear first time you learn it.
-
+<!--more-->
 I will try to present it to you in a short way:
 ```swift
 let parentProgress = NSProgress()
diff --git a/source/_posts/2015-08-17-autolayout-breakpoints.markdown b/source/_posts/2015-08-17-autolayout-breakpoints.markdown
@@ -8,7 +8,7 @@ categories:
 ---
 
 Auto layout has become a crucial tool for iOS and OS X development. It makes creating layout for multiple screen sizes easy peasy. But sometimes it can drive you crazy, with verbose and misleading logs.
-
+<!--more-->
 ```
 Unable to simultaneously satisfy constraints.
 Probably at least one of the constraints in the following list is one you don't want.
diff --git a/source/_posts/2015-08-24-dont-forget-about-uimotioneffects.markdown b/source/_posts/2015-08-24-dont-forget-about-uimotioneffects.markdown
@@ -12,7 +12,7 @@ categories:
 Motion effects is an easy way to react to external variations on the device's orientation. To say, `UIKit` performs UI changes whenever the user tilts the device, vertically or horizontally.
 
 Let's use `UIInterpolatingMotionEffect` a subclass of `UIMotionEffects`, with `MapKit`. Notice how appealing it is.
-
+<!--more-->
 {% img center /images/dont-forget-about-motion-effects/01.gif %}
 
 Sweet, right?
diff --git a/source/_posts/2015-09-02-autolayout-and-nslocalizedstring.markdown b/source/_posts/2015-09-02-autolayout-and-nslocalizedstring.markdown
@@ -10,7 +10,7 @@ categories:
 A localized application is the one that has all of its texts, translated into the users device current language. And this, for us developers, means one thing, and one thing only. Nightmare.
 
 Every time a new translation comes, it's necessary to run the application and check for broken layouts. Take this quite simple UI.
-
+<!--more-->
 {% img center /images/autolayout-and-nslocalizedstrings/01.png 375 %}
 
 Simple, huh?
diff --git a/source/_posts/2015-09-14-logging-excessive-blocks-on-the-main-thread.md b/source/_posts/2015-09-14-logging-excessive-blocks-on-the-main-thread.md
@@ -10,7 +10,7 @@ Logging excessive blocks on the main thread
 
 Having an application running at 60 FPS is every programmers dream, and users delight.
 The worst users experience ever is a frozen and unresponsive screen. It's a dreadful crime in mobile world nowadays. Users try to interact at any moment and according to Murphy’s law they will find all your mistakes. So, you better keep the main thread slim.
-
+<!--more-->
 To keep things smoothly in the users interface, every single operation that's schedule to run into the main thread can take longer than 16 milliseconds, and there's a handy solution to get you covered. It's a little library called [Watchdog](https://github.com/wojteklukaszuk/Watchdog).
 
 Watchdog is a very simple and straightforward library that logs excessive blocking on the main thread. Let's take a look at how to use it:
diff --git a/source/_posts/2015-09-23-uitraitcollection-trick.markdown b/source/_posts/2015-09-23-uitraitcollection-trick.markdown
@@ -8,7 +8,7 @@ categories:
 ---
 
 Gone are the days where there was just one iPhone for developers as a target. Now we have to support multiple devices with different screen sizes. Fortunately, we have autolayout, which solves a part of this design equation, the other part is solved with [`UITraitCollection`](https://developer.apple.com/library/ios/documentation/UIKit/Reference/UITraitCollection_ClassReference/). Trait collection object has two size classes: horizontal and vertical. Each of these classes has three possible values: compact, regular or any. The current device+orientation can be described as a combination of the sizes.
-
+<!--more-->
 {% img center /images/uitraitcollection_trick/1.png %}  
 
 The best thing is that storyboards and nib files support these size classes. We can make layout changes directly onto them. Every view or auto-layout constraint can exist in one or several other size classes. So it is possible to support multiple devices and orientations without any code. Nevertheless there is a case, which is not covered at all. Imagine that you support only portrait mode and the designer wishes to make a difference between iPhone 5 and iPhone 6+ screen. In this case, size classes are not much helpful. However, we can leverage them in an unusual way.
diff --git a/source/_posts/2015-10-07-easy-cast-with-_ObjectiveCBridgeable.markdown b/source/_posts/2015-10-07-easy-cast-with-_ObjectiveCBridgeable.markdown
@@ -8,7 +8,7 @@ categories:
 ---
 
 Swift is out there for about a year and it's a great programming language. I think that almost every iOS/OSX developer out there has already written couple of things in Swift (if you haven't, go ahead and try, you won't regret it, I promise). Although, we have many years of libs and frameworks built using Objective-C and sooner or later a project may have both Swift and Objective-C working together.
-
+<!--more-->
 Fortunately, Apple gave us a [book](https://itunes.apple.com/us/book/using-swift-cocoa-objective/id888894773?mt=11) and a couple of WWDC session ([here](https://developer.apple.com/videos/play/wwdc2014-406/) and [here](https://developer.apple.com/videos/play/wwdc2015-401/)) with the intent to help developers on this task.
 
 For those who have some experience with this integration knows that casting plays an important role. So, todays hint will dig into an poor documented protocol called `_ObjectiveCBridgeable`.
diff --git a/source/_posts/2015-10-08-bluetooth-low-energy-the-fun-way.markdown b/source/_posts/2015-10-08-bluetooth-low-energy-the-fun-way.markdown
@@ -10,7 +10,7 @@ categories:
 Today Bluetooth Low Energy can be found in many cool applications, it can be used from simple data exchange to payment terminals and the more popular usage with iBeacons. But what if we want to build something funny with it? Like some simple game not even realtime, it may be even turn based game. Imagine you do not need to go through this long setup, waiting for server players to be ready etc.
 
 Everyone knows that building good multiplayer game is hard, multiplayer itself is hard... But here I want to show you my small proof of concept of working bluetooth low enery multiplayer game.
-
+<!--more-->
 It can be used in any kind of game! Strategy, board, rpg, race. I built§ a small demo project to show this in details but now let's focus on basics:
 
 Pros:  
diff --git a/source/_posts/2015-10-10-working-with-cfunction-pointers-in-swift.markdown b/source/_posts/2015-10-10-working-with-cfunction-pointers-in-swift.markdown
@@ -8,7 +8,7 @@ categories:
 ---
 
 Swift like objC allow us to mix it with other languages, unfotunately when it comes to Swift we can only choose between our good old friend objC or ANIS C, as there is still lack of C++ support. Basically using function pointers allows us to call C functions inside Swift. Swift will automatically convert methods included in Bridge Header into Swift equivalents:
-
+<!--more-->
 This code:  
 
 ```C
diff --git a/source/_posts/2015-10-23-noescape-attribute.markdown b/source/_posts/2015-10-23-noescape-attribute.markdown
@@ -11,7 +11,7 @@ Swift 1.2 introduced us with `@noescape` attribute. It's a very important featur
 
 While digging into [release notes](https://developer.apple.com/library/ios/releasenotes/DeveloperTools/RN-Xcode/Chapters/xc6_release_notes.html) we can see a bunch of clever words:
 > A new `@noescape` attribute may be used on closure parameters to functions. This indicates that the parameter is only ever called (or passed as an @noescape parameter in a call), which means that it cannot outlive the lifetime of the call. This enables some minor performance optimizations, but more importantly disables the `self.` requirement in closure arguments.
-
+<!--more-->
 Lets analyze those smart statements and put it into code so everyone can enjoy it: 
 
 ```swift
diff --git a/source/images/github.png b/source/images/github.png
diff --git a/source/images/rss.png b/source/images/rss.png
diff --git a/source/images/twitter.png b/source/images/twitter.png

Original file line number	Diff line number	Diff line change
`@@ -40,7 +40,6 @@ body > nav {`
`40`	`40`	`ul {`
`41`	`41`	`@include horizontal-list(0);`
`42`	`42`	`display: inline-block;`
`43`		`- padding-top: .15em;`
`44`	`43`	`}`
`45`	`44`	`ul.subscription {`
`46`	`45`	`margin-left: .8em;`