This make handling gesture more easily, with block

It works this way

• ViewController -strong-> GestureSense -strong-> Target -strong-> handler block
• UIGestureRecognizer -weak-> Target
• It won't attach the same kind of gesture twice

let sense = GestureSense()
let view = UIView()

sense.tap(view) { gr in

}

sense.pan(view) { gr in

}

sense.pan(view) { gr in

}

As @vadymmarkov brought up in (https://github.com/hyperoslo/Sugar/pull/78#issuecomment-220854098), Sugar is growing out of proportion, one can even start to call it obese.

We need to come up with a good strategy to tackle this problem. As I wrote in #78;

I think we need to adress this is a good way, maybe splitting it out in to separate repos where it makes sense and then starting to mark things as deprecated and then remove extract and remove bits and pieces from the Sugar core.

That could be one way of handling it. But we need to find a good middle ground to find what goes into Sugar and what does not. Do we see Sugar as a incubator for future pods, exposing where there could be potential for more components or is it more like the name implies, a syntax sugar for Cocoa and Cocoa Touch were we feel that Apple default implementation is falling short.

Regardless of that, the issue needs solving so, without further ado, discuss peoples!

With this PR, you can easily split up String’s into multiple parts by calling split().

"root/path/file".split("/")
// ["root", "path", "file"]

I was doing some Networking and wanted to check if the status code was in a range, did this tiny thing. You call it like this:

let OK = 200..<300
OK.contains(response.statusCode)

@hyperoslo/malibu

This PR adds some functionality to dispatch. Now you can select between all global queues by just passing an enum value;

It still defaults to .Main so the public API does not change.

# Main queue
dispatch {}

# Interactive
dispatch(queue: .Interactive) {}

# Interactive
dispatch(queue: .Initiated) {}

# Interactive
dispatch(queue: .Utility) {}

# Background
dispatch(queue: .Background) {}

You can still add your own custom queue by doing this;

# Custom
dispatch(queue: .Custom(myQueue)) {}

The only change required to support swift 2.3 is self.init(CGImage: image!.CGImage!) in the branch instead of self.init(CGImage: image.CGImage!) in the file UIImage+Extensions.swift

• Observer keyboard will show and will hide events
• Currently support handler for basic animation, custom block, scrollview insets, layout constraint
• Add new handler by conforming to KeyboardHandler protocol

I'm working with CocoaPods package in there isn't possible point to a branch, is there possible release a tagged version of Sugar package to Swift 3 users?

This is the reverse of isEmpty but it will help improve the implementation in your application.

So instead of:

if !value.isEmpty {}

You could do:

if value.isPresent {}

I have made all the necessary changes to upgrade this project to swift version 4.2. This included all API changes in actual application code as well as test code. The projects produces no warnings.

Further discussion: Sugar currently offers the computed property .length on the String type. This was added to avoid typing .character.count everytime someone wanted to access the character count of a string. Since the original implementation of Sugar, Swift has since reverted back to using .count on the string type directly which renders this property meaningless. I did not want to remove it to avoid breaking existing code, but I would like to propose removing this completely.

If you use current Sugar with Swift 3 environment and use >, <, >=, <= operators, it will lead to compile error like follows.

Ambiguous use of operator '<'

We shouldn't have these operators in Sugar anymore.