The fill functions accept CGFloat or Insets values, and another version should be added that accepts a UIEdgeInsets - especially since it is directly convertible to Insets.

Problem When I have a CGSize, I have to access the width & height to pass into the size() method:

func setupConstraints(with size: CGSize) {
  label.layout.size(size.width, size.height)
}

Solution I would like to just pass a CGSize to the size() method, like:

func setupConstraints(with size: CGSize) {
  label.layout.size(size)
}

We bumped into a weird (hopefully) edge case where we were adding a UIView directly to a UIWindow, and then using the automatic size class activation on some subviews within that UIView.

A problem came up where the LayoutView instance used to listen for traitCollectionDidChange notifications was being created as a direct child of the UIWindow. WWLayout relies on the LayoutView instance to be released as the primary containing view is released. This naturally fits with using UIViewControllers - but breaks when adding directly to a UIWindow.

The fix is to prevent LayoutView instances from being added directly to a UIWindow. I also wrapped all references to the auto-switching constrains held by the LayoutView in a WeakBox, as a defensive measure against any other oddball situations that might also cause problems.

• Update SwiftLint config
• Fix annoying "comment spacing" SwiftLint warnings
• Update xcodeproj "last check version"
• Add new file tempkate to the appleTV example

Addresses: #28

This PR adds versions of all the fill functions, that uses UIEdgeInsets for the inset parameter value type. This will allow for using a variable for the insets, like this:

let insets = UIEdgeInsets(top: 20, left: 20, bottom: 20, right: 20)
view.layout.fill(.superview, inset: insets)

Updating the project files & adding a CircleCI job for Swift 5.3.

Removed slather from the Gemfile since it isn't used, and including it is currently causing build errors in Circle (The Xcode 12 beta image doesn't have the dev tools installed yet - using Ruby 2.7 might fix it). Since we aren't reporting (or checking) code coverage yet in CircleCI this should be ok for now.

Bumps nokogiri from 1.10.4 to 1.10.8.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Add support for SwiftPM. Included CircleCI job is build only - unit tests are run for all the other jobs.

Added a sample project that targets Apple TV - this one uses SwiftPM. The existing sample app still uses the embedded WWLayout sub-project for easier development.

Note: will need to change example app's reference to the package once merged into develop (currently points to the feature/swiftpm feature branch).

Release 0.6.0

• Added support for tagging constraints, https://github.com/ww-tech/wwlayout/issues/2
• Added support for size classes, https://github.com/ww-tech/wwlayout/issues/6

Release version 0.5.7.

• add version of fill functions that accept a CGFloat (@g-mark)
• add version of size function that accepts a CGSize (@gradyjenkins)

Addresses: https://github.com/ww-tech/wwlayout/issues/1

This PR adds versions of all the fill functions, that uses CGFloat for the inset parameter value type. This will allow for using a variable for the insets, like this:

let padding: CGFloat = 4
view.layout.fill(.superview, inset: padding)

in addition to int/float literals like this:

view.layout.fill(.superview, inset: 42)

There is currently no code coverage reporting in CircleCI, and needs to be added - preferably with a coverage threshold.

Additionally, a code coverage badge needs to be added to the main Read Me file.

SwithLint is currently only run locally in Xcode, and only if a user has it installed - not to mention having the latest version.

SwiftLint should be run as a part of every build-test workflow in CircleCI, and further configured to prevent merging PRs that introduce any new warnings.

Is your feature request related to a problem? Please describe. Add WWLayout support for UILayoutGuide.

Describe the solution you'd like Being able to use WWLayout to add constraints to UILayoutGuide just like UIView.

Seems that a common task is for a bunch of child views to horizontally fill their parent, with possibly different insets. It would be interesting to explore this kind of convenience:

.arrangeViews(.fillX, view1 - 40, view2 - 40, view3 - 15, view4 - 32)

• options could be: centerX, fillX, leftAlign, rightAlign, plus same for vertical
• maybe have a param for an at: offset, like (.leftAlign, at: leftEdge + 20, ...)

Or, something like:

   align(.top/.left/.right/.bottom, views: Anchorable...)
   
   distribute(.horizontally/.vertically, views: Anchorable...)