Fast Swift Views layouting without auto layout. No magic, pure code, full control and blazing fast. Concise syntax, intuitive, readable & chainable. [iOS/macOS/tvOS/CALayer]
UIScree.main will be deprecated in a future version of iOS.
Added by Hyungyu Kim in Pull Request #275
New property pin.keyboardMargins
UIView.pin.keyboardMargins: property expose directly the value of UIKit UIView.keyboardLayoutGuide. This is really useful when layout adjustment due to the keyboard is required. iOS 15+Instead of using verbose Objective-C with all brackets ([ ]):
[[[[[[logo.pinObjc top] left] width:100] aspectRatio] marginWithTop:topLayoutGuide + 10 horizontal:10 bottom:10] layout];
It now use function chaining:
logo.pinObjc.topInsets(safeArea).leftInsets(safeArea).width(100).aspectRatio().margin(margin).layout();
autoSizeThatFits.
By calling autoSizeThatFits with the given available size and a layout closure, any layouting performed by PinLayout in that closure will be computed without affecting any subview's frame in the view hierarchy. On the other hand, any non PinLayout related code will also be executed. For that reason, it is really important to separate your layout code in it's own function to avoid any side effect during sizing, like setting the scroll view's content size in the above exemple or perhaps assigning itemSize in a collection view layout. That kind of code that depends on the layout should only be executed when layoutSubviews() is called as part of a normal layout pass.
The resulting size also takes into account the margins applied on subviews, even on the bottom and trailing sides. Automatic sizing makes it really easy to write your layout logic once and add proper sizing behavior with virtually no additional effort.
See https://github.com/layoutBox/PinLayout#automatic_sizing for more documentation. * Added by Antoine Lamy in Pull Request #216