Currently SizeLayout allows layouts to have a specific length along one or both dimensions.

It would be useful to be able to specify maximum width/height and minimum width/height for a nested layout.

One option would be to create a MinSizeLayout and a MaxSizeLayout. Unsure if it would make sense to combine these into one layout (e.,g. SizeRangeLayout), or even combine them with SizeLayout.

If we stick with separate layouts, then we might also want to rename SizeLayout to ExactSizeLayout

Hey there
Is there something equivalent to LabelLayout for views such as UIButton (or any other view that define an intrinsicContentSize)?

Right now I am using a SizeLayout but I am forced to define the size of my button

SizeLayout<UIButton>(
  width: 100, height: 50,
  alignment: .centerTrailing,
  flexibility: .flexible,
  config: { button in
    button.backgroundColor = UIColor.blue
    button.setTitle("Button", for: .normal)
    button.setTitleColor(.black, for: .normal)
  }
)

Hi,

first of all thanks for open sourcing LayoutKit!

While experimenting with the Framework a bit I was wondering what'd be the best approach to handle orientation changes.

Suppose we have the following layout and we want to adapt it to landscape mode on tilting the device.

Right now I handle this by creating the layout again from scratch if an orientation change occurs.

    override func viewDidLoad() {
        super.viewDidLoad()

        title = "Layout Kit"

        let leftLayout = LabelLayout(text: "Left", alignment: LayoutKit.Alignment.topLeading) {label in
            label.backgroundColor = UIColor.purpleColor()
        }

        let rightLayout = LabelLayout(text: "Right", alignment: LayoutKit.Alignment.topTrailing ) { label in
            label.backgroundColor = UIColor.cyanColor()
        }

        let stackLayout = StackLayout(axis: .horizontal, spacing: 8, sublayouts: [leftLayout, rightLayout]) { (view) in
            view.backgroundColor = UIColor.blueColor()
        }

        insetLayout = InsetLayout(inset: 8, sublayout: stackLayout, config: nil)

        guard let insetLayout = insetLayout else { return }
        insetLayout.arrangement(width: view.bounds.size.width).makeViews(inView: containerView)
    }

    override func viewWillTransitionToSize(size: CGSize, withTransitionCoordinator coordinator: UIViewControllerTransitionCoordinator) {
        super.viewWillTransitionToSize(size, withTransitionCoordinator: coordinator)

        coordinator.animateAlongsideTransition({ (context) -> Void in
            guard let insetLayout = self.insetLayout else { return }
            insetLayout.arrangement(width: self.view.bounds.size.width).makeViews(inView: self.containerView)
        }) { (context) -> Void in }
    }

However I am wondering if there might be a better approach to this issue.

Any help would be highly appreciated.

Cheers,
Riko

Currently ViewRecycler only reuses views that have a viewReuseId. It could cache views that don't have a viewReuseId by their type and reuse them when creating views.

LayoutArrangementTests should be run for the LayoutKit-macOS target but they aren't.

Need to re-enable and get tests to pass.

Need to figure out how to customize template with mkdocs

How would I reload some rows of my table?

It seems very nature if there is updatedItems/Sections in BatchUpdates.
What did I missed?

Thanks

As reported by @pgherveou in #56:

If I run twice the same layout with reuseIds set on some of my views, the order of the views changes

== test 2 ==

Unmanaged<AnyObject>(_value: <UIView: 0x7f92a56022c0; frame = (0 0; 350 250); layer = <CALayer: 0x610000033a20>>
   | <UIImageView: 0x7f92a5503e70; frame = (4 4; 50 50); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x618000234ee0>>
   | <UILabel: 0x7f92a7104440; frame = (61 4; 36.5 20.5); text = 'hello'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x60000009edc0>>
   | <UILabel: 0x7f92a5406770; frame = (58 29; 42.5 20.5); text = 'world'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x60000009dd80>>)

== test 3x ==

Unmanaged<AnyObject>(_value: <UIView: 0x7f92a56022c0; frame = (0 0; 350 250); layer = <CALayer: 0x610000033a20>>
   | <UILabel: 0x7f92a7104440; frame = (61 4; 36.5 20.5); text = 'hello'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x60000009edc0>>
   | <UILabel: 0x7f92a5406770; frame = (58 29; 42.5 20.5); text = 'world'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x60000009dd80>>
   | <UIImageView: 0x7f92a560b770; frame = (4 4; 50 50); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x610000036180>>)

This could have unexpected consequences for layering and tap handling if views overlap so LayoutKit should make sure views are in a deterministic order.

I started using this framework in a sample project. Great work and thanks for sharing.
I spent some time myself working on something similar, as a side project, and i'm considering to switch to LayoutKit cause it is far head on what I have.

Things that I'd like to add:

• Label baseline alignment: Be able to align labels by baseline in an horizontal layout
• Center on a specific element of the stack: Let's say a stack contains two layouts [A][B], if I set .center as aligment for the stack, than the stack's container will set the stack position based on the mid point of it's size. There are cases where I want to center the stack on a specifc element.

For example in this Stack I have to elements the dot and the text. That text should be centered.

A solution to this specific example could be to create an empty SizeLayout as third element of the stack with the same width than the first one. But this could be more complicated with dynamic elements and it should be possible without have to create more layout elements than necessary.

• Action support: Now I can add a button as part of the layout and than regenerate the Layout in response to an user action. Could be useful to have a native support for states (Normal, Highlighted) in a way that the view could automatically update to reflect a given state. i.e. having a state parameter in the view config block
• Traslation: Ability to apply a traslation to a view position after the layout phase by absolute value or by percentage on the container size.
• Max/Min size constraints: Ability to apply a max/min size to a Layout, so that it can still adapt it's size to the size of it's content and at the same time allows to specify min/max constraints.

Please let me know if those features are on you list and if you think if they make sense or not.
From your architecture I see that I can develop those things has private layouts but I'd like to know your feedbacks, if you have similar things on your todo list and eventually share my changes if they can be useful.

Documentation:
https://swift.org/package-manager/

• Create Package.swift

import PackageDescription

let package = Package(
  name: "LayoutKit"
)

• Move Library code to a Sources/ folder?
• Anything else?
• Test Unit Tests
• Test Swift Package Manager by a sample project
• Test Cocoapods
• Test Carthage
• Update Readme.md

Ability to apply a traslation to a view position after the layout phase by absolute value or by percentage on the container size.

This could be handy in cases where we need to tweak the position of a element in a complex layout without have to create a custom Layout.

When I use the Safari browser to visit the layoutkit.org site with an 85% page zoom, the layout breaks. Many websites have this problem, but it's ironic that Layout Kit doesn't get this right. Let me know if you need details on my configuration. The page zoom is configurable in Safari's Advanced preference panel.

I tried pod 'LayoutKit'
The version is 0.2.1 and the project created by Florian Krüger
I think it is not the correct kit.
Any idea what should I do to get the updated LayoutKit?

Rename
public func position(size size: CGSize, inRect rect: CGRect) -> CGRect
to
public func position(size size: CGSize, in rect: CGRect) -> CGRect

Hello,

I've created a layout to list a person's name and title like so:

class TeamMemberLayout: InsetLayout<View> {
    public init(person: Person) {        
        let nameLayout = LabelLayout(
            text: "Person Name",
            font: .boldSystemFont(ofSize: 16),
            alignment: .center
        )
        
        let titleLayout = LabelLayout(
            text: "Chief Executive Officer and Vice President",
            font: .systemFont(ofSize: 12),
            alignment: .center,
            config: { label in
                label.numberOfLines = 1
            }
        )
        
        super.init(
            insets: UIEdgeInsets(top: 12, left: 12, bottom: 12, right: 12),
            sublayout: StackLayout(
                axis: .vertical,
                spacing: 6,
                alignment: .topFill,
                viewReuseId: "teammemberlayout",
                sublayouts: [nameLayout, titleLayout]
            ),
            config: nil
        )
    }
}

As you can see, I am limiting the number of lines for the title label to be one, and for the alignment to be .center. However, my layout renders like so:

Any idea what I'm doing wrong? Thanks!

The link to the blog post is broken.
https://engineering.linkedin.com/blog/2016/06/open-sourcing-layoutkit--a-fast-view-layout-library-for-ios-appl

My team and I are trying out this library for a feed we are incorporating into our app and we really like LayoutKit so far. We would like to thank you for open sourcing this and we find that it's a really great way to build performant user interfaces. However, we are really missing interactivity on layouts that are not ButtonLayouts. We want to be able to control the highlighted state of any layout.

Here's an example use case we stumbled upon that caused our desire for this feature:

We have a feed with cells laid out vertically stacked. These cells have different layouts, one of which contains an ImageLayout as a sublayout. We are able to feign the highlighted state on the rest of the layout by making it transparent and making the views in a class extending UICollectionViewCell that has a highlighted state. Of course this does not pertain to the layout containing an image and it's a bit of a hack.

Is there a recommended practice for how to achieve this already using LayoutKit? We are able to identify the sublayouts of a given layout but the views they wrap are inaccessible to us.

Should there not be a recommended practice to achieve this kind of behavior we propose introducing two new protocols to LayoutKit, Actionable and Highlightable.

Actionable would allow the layout to respond to presses with an action and during the press highlight all children conforming to Highlightable until a descendant conforms to Actionable.

Highlightable allows a view/layout to assume a highlighted state, altering it's appearance without changing the layout, when passed an action from the closest parent conforming to Actionable. The properties of this highlighted state would preferably be specified in the config closure.

I should also add that we are willing to contribute to this project should you accept this proposal.

FeedTableView in sample app with the following FeedItemLayout causes red boxes around images as well as high latency alert from DWURecyclingAlert. Any thoughts on how I can optimize image loading and layout?

https://github.com/diwu/DWURecyclingAlert/blob/master/RecyclingAlert/DWURecyclingAlert/DWURecyclingAlert.m

` let actorCommentLayout = StackLayout(axis: .horizontal, sublayouts: [
SizeLayout(width: 50, height: 50, config: { imageView in

            imageView.image = UIImage(named: "Avatar\(imageIndex.instance.value)")
        }),
        LabelLayout(text: actorComment, alignment: .centerLeading)
    ])`

Let's say a stack contains two layouts [A][B], if I set .center as aligment for the stack, than the stack's container will set the stack position based on the mid point of it's size. There are cases where I want to center the stack on a specifc element.

For example in this Stack I have to elements the dot and the text. That text should be centered.

A solution to this specific example could be to create an empty SizeLayout as third element of the stack with the same width than the first one. But this could be more complicated with dynamic elements and it should be possible without have to create more layout elements than necessary.

I have built a horizontally scrolling control that uses a fixed number of fixed-size cells using LayoutKit. When the user taps a cell, I'd like to reload the previously selected cell and the newly selected cell in order to move the selection indicator. I attempted to do this by using BatchUpdates and setting the reloadItems property, but the performance is very slow.

Once I build BatchUpdates, I call layoutAdapter.reload() with a fixed width and height, passing in the BatchUpdates I just built, and returning a cached array of Layout items to the layoutProvider (with the 2 indexPaths already rebuilt and updated in the cache).

To work around this, I've instead just fetched each cell manually (cellForItemAtIndexPath), built the new layout, and arranged/made in the cell.contentView. This shows much faster performance. What's the intended use of BatchUpdates, and is there a way to get better performance out of it?

I'd like to be able to align labels inside a horizontal stack based on their baseline.

We could Add a new Alignment properties: (Vertical.baseline). If the contained object doesn't have a baseline (not text) than it behaves like .center

Here is why I want this:

I need add time accessory view and using pan gesture to reveal it(imaging iMessage)

So, what I did for this:
register and dequeue custom cell which have a method to receive offset, and the Revealer will handle pan gesture and send the offset to visible cells.

If you guys think this will be helpful like I do, I would like to send a PR

https://github.com/linkedin/LayoutKit/LayoutKit/Layouts/LabelLayout.swift

https://github.com/linkedin/LayoutKit/LayoutKit/Layouts/SizeLayout.swift

https://github.com/linkedin/LayoutKit/LayoutKit/Layouts/InsetLayout.swift

https://github.com/linkedin/LayoutKit/LayoutKit/Layouts/StackLayout.swift

https://github.com/linkedin/LayoutKit/LayoutKitExampleLayouts/MiniProfileLayout.swift

https://github.com/linkedin/LayoutKit/LayoutKitExampleLayouts

and many more...

Current sample app is manually setup.

• iOS
• tvOS
• macOS

labellayout textAlignment is not work!
my code like this

let authorLayout = LabelLayout(
            text: author,
            font: UIFont.systemFontOfSize(20),
            config: { label in
                label.textAlignment = .Right
            }
        )

Hi, just curious on how the benchmark was performed http://layoutkit.org/benchmarks/ ? I assume that layout time is the time from before to after reloadData?

Would be nice to have

Though animation works nicely for reused views, newly-added or removed views don't get any good visual effects since their frames are either miscalculated (when added) or not even calculated (when removed).

It would be nice to have some effects for them e.g. fade in/out, and also delaying purgeViews so that animation don't get interrupted.

This line is not compatible with today extension. https://github.com/linkedin/LayoutKit/blob/master/LayoutKit/LayoutArrangement.swift#L105

Could this get checked like http://stackoverflow.com/questions/29246656/ios-sharedapplication-is-unavailable-in-today-extension to add support for extensions as well?

Any idea when Swift3 support would be added, in particular for the latest Xcode 8 beta 6, which I am trying to build a project with (unsuccessfully)?

How can I use tableView:didSelectRowAtIndexPath: or deselectRowAtIndexPath:animated: delegate methods for managing cell selection when I use ReloadableViewLayoutAdapter to create tableView (like in LayoutKitSampleApp)?

Current sample app is manually setup.

ViewRecycler currently instantiates views with a no-argument constructor. This means that if you want to use a view that requires an initializer with an argument (e.g. UIButton), you need to create a subclass with a no-argument initializer.

ViewRecycler should use a view factory method provided by the layout to initialize new views. This will allow layouts to use initializers with arguments based on information in the layout.

See @pgherveou's comment below.

For instance: https://github.com/linkedin/LayoutKit/blob/master/LayoutKit/Layouts/LabelLayout.swift#L129-L137

Sometimes I want to change some property when configuration, it will be override by the initial setup.

Should the config block execute after initial setup will be better?

Creating this issue to document @staguer 's idea to improve the interface w.r.t. animation support.

With the new ViewRecycler introduced in #12, the actual creation of the view no longer needs to happen inside of makeView() -> UIView?. It would be better if LayoutKit could instantiate the view automatically (reusing if necessary) and then the layout could just configure it.

@staguer Here is the prototype that you created

// Layout can't have a generic parameter so we can create arrays of Layouts.
protocol Layout {
    func generalConfigure(view view: UIView)
    var viewType: UIView.Type? { get }
    func makeView() -> UIView?
}

extension Layout {
    func makeView() -> UIView? {
        if let viewType = viewType {
            // Layouts that use views which don't have an appropriate default initializer
            // will need to override this implementation of makeView().
            return viewType.init()
        } else {
            return nil
        }
    }
}

// Layouts will extend this instead of Layout.
protocol ConfigurableLayout: Layout {
    associatedtype V: UIView
    func configure(view view: V)
}

extension ConfigurableLayout {
    func generalConfigure(view view: UIView) {
        guard let view = view as? V else {
            return
        }
        configure(view: view)
    }
    var viewType: UIView.Type? { return V.self }
}

// Example
class LabelLayout: ConfigurableLayout {
    func configure(view: UILabel) {
        // set the text and stuff
        view.text = "hi"
    }
}

Hey sorry for the avalanche of questions
I played with the example Feed Collection view and put a breakpoint here, to test whether cell subviews were recycled or not. It gave me the results below.

Each cell subviews are recreated each time collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) is called.

The only way to recycle the views is to use a viewReuseId for each layout/sub-layouts right?
Do you have any recommendation for using Layoutkit to render reusable CollectionView Cells?

// before makeView
(lldb) po cell.contentView.subviews[0].subviews
▿ 16 elements
  - 0 : <UILabel: 0x7f9dc947a5f0; frame = (8 8; 258 20.5); text = 'Sergei Tauger commented o...'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286590>>
  - 1 : <UILabel: 0x7f9dc947a870; frame = (298 8; 14 20.5); text = '...'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286630>>
  - 2 : <UIImageView: 0x7f9dc947aaf0; frame = (8 40.25; 50 50); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x61000022a820>>
  - 3 : <UILabel: 0x7f9dc947aef0; frame = (62 32.5; 92 20.5); text = 'Nick Snyder'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286860>>
  - 4 : <UILabel: 0x7f9dc947b170; frame = (158 32.5; 22 20.5); text = '1st'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286900>>
  - 5 : <UILabel: 0x7f9dc947b3f0; frame = (62 55; 228 20.5); text = 'Software Engineer at Link...'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x6100002867c0>>
  - 6 : <UILabel: 0x7f9dc947b670; frame = (62 77.5; 108.5 20.5); text = '5 minutes ago'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x6100002869a0>>
  - 7 : <UILabel: 0x7f9dc947b8f0; frame = (8 102; 92.5 20.5); text = 'Check it out'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286720>>
  - 8 : <UIImageView: 0x7f9dc947acd0; frame = (8 126.5; 304 200); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x61000022ae20>>
  - 9 : <UILabel: 0x7f9dc947bb70; frame = (8 326.5; 100.5 20.5); text = 'Chuck Norris'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286a90>>
  - 10 : <UILabel: 0x7f9dc947bdf0; frame = (8 347; 128 20.5); text = 'chucknorris.com'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286b30>>
  - 11 : <UILabel: 0x7f9dc947c070; frame = (8 371.5; 31 20.5); text = 'Like'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286bd0>>
  - 12 : <UILabel: 0x7f9dc947c2f0; frame = (122.5 371.5; 75 20.5); text = 'Comment'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286c70>>
  - 13 : <UILabel: 0x7f9dc947c570; frame = (267.5 371.5; 44.5 20.5); text = 'Share'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286d10>>
  - 14 : <UIImageView: 0x7f9dc947c7f0; frame = (8 396; 50 50); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x61000022aca0>>
  - 15 : <UILabel: 0x7f9dc947c9d0; frame = (58 410.75; 78.5 20.5); text = 'Awesome!'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286e00>>

// after makeView
2016-10-16 11:32:11.432017 LayoutKitSampleApp[55714:4857519] subsystem: com.apple.coreanimation, category: CADebug, enable_level: 2, persist_level: 1, default_ttl: 0, info_ttl: 0, debug_ttl: 0, generate_symptoms: 0, enable_oversize: 1, privacy_setting: 0, enable_private_data: 0
(lldb) po cell.contentView.subviews[0].subviews
▿ 16 elements
  - 0 : <UILabel: 0x7f9dc9726500; frame = (8 8; 258 20.5); text = 'Sergei Tauger commented o...'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x6080002852d0>>
  - 1 : <UILabel: 0x7f9dc9726780; frame = (298 8; 14 20.5); text = '...'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x608000284bf0>>
  - 2 : <UIImageView: 0x7f9dc9726a00; frame = (8 40.25; 50 50); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x60800002c760>>
  - 3 : <UILabel: 0x7f9dc947aef0; frame = (62 32.5; 92 20.5); text = 'Nick Snyder'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x610000286860>>
  - 4 : <UILabel: 0x7f9dc9726be0; frame = (158 32.5; 22 20.5); text = '1st'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x608000280000>>
  - 5 : <UILabel: 0x7f9dc9726e60; frame = (62 55; 228 20.5); text = 'Software Engineer at Link...'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x6080002808c0>>
  - 6 : <UILabel: 0x7f9dcb800480; frame = (62 77.5; 108.5 20.5); text = '5 minutes ago'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x600000284600>>
  - 7 : <UILabel: 0x7f9dc97a8fb0; frame = (8 102; 92.5 20.5); text = 'Check it out'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x608000284010>>
  - 8 : <UIImageView: 0x7f9dcbd02ee0; frame = (8 126.5; 304 200); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x61800002c2c0>>
  - 9 : <UILabel: 0x7f9dc9665b90; frame = (8 326.5; 100.5 20.5); text = 'Chuck Norris'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x6000002843d0>>
  - 10 : <UILabel: 0x7f9dc9597ba0; frame = (8 347; 128 20.5); text = 'chucknorris.com'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x618000284380>>
  - 11 : <UILabel: 0x7f9dc9597e20; frame = (8 371.5; 31 20.5); text = 'Like'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x618000284d30>>
  - 12 : <UILabel: 0x7f9dc95980a0; frame = (122.5 371.5; 75 20.5); text = 'Comment'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x618000284c90>>
  - 13 : <UILabel: 0x7f9dc9598320; frame = (267.5 371.5; 44.5 20.5); text = 'Share'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x6180002850a0>>
  - 14 : <UIImageView: 0x7f9dc9521210; frame = (8 396; 50 50); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x61800002a380>>
  - 15 : <UILabel: 0x7f9dc95985a0; frame = (58 410.75; 78.5 20.5); text = 'Awesome!'; userInteractionEnabled = NO; layer = <_UILabelLayer: 0x618000284fb0>>

It would be great that Xamarin.iOS developer can use this lib!

See comment in build.sh.

Tests work locally but codesign appears to fail on travis.

Now I can add a button as part of the layout and than regenerate the Layout in response to an user action. Could be useful to have a native support for states (Normal, Highlighted) in a way that the view could automatically update to reflect a given state. i.e. having a state parameter in the view config block

Im getting "Extra argument synchronous in Call"

reloadableViewLayoutAdapter.reload(width: width, synchronous: synchronous, layoutProvider: { [weak self] in
            return [Section(header: nil, items: self?.getFeedItems() ?? [], footer: nil)]
            })

Hey guys, found out about LayoutKit from Realm today, looks incredible. We've been having serious issues with auto layout performance and also use a lot of corner radius's in our views, can you provide a link to something more performant?

Re: http://layoutkit.org/building-ui/#defining-composite-layouts

https://github.com/Carthage/Carthage

Hey guys, just started using the library today and have enjoyed working with it. I'm a little stuck and was hoping you could shed some light. I've got my layouts created using a UICollectionView with the ReloadableViewLayoutAdapter. The behavior I'm looking for is to load an initial dataset and render the layouts, then be able to insert, delete, move or update items using the collectionview animations. I can't find anything in the docs that describes animating data, and when I try to it winds up doing a reload instead. When the update function is called within the adapter the incremental value is always true, so it calls reloadDataSync on the collectionview instead of proceeding to call insert.

After doing the initial load how should I proceed to insert more items?

Is this behavior possible to split the layout width to all sublayouts. So that all sublayout has the same width?

To support custom collectionview or tableview delegates the currentArrangement array has to be public. An example for custom delegates is https://github.com/ecerney/CollectionViewWaterfallLayout .

Hi,

I'm not able to install layoutkit using carthage.

Xcode Version : 7.3.1
Swift Version : Apple Swift version 2.2 (swiftlang-703.0.18.5 clang-703.0.31)
Target: x86_64-apple-macosx10.9
cartfile : github "linkedin/LayoutKit"

carthage update --platform iOS
** BUILD FAILED **

The following build commands failed:
CompileSwift normal arm64
CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler
(2 failures)
A shell task (/usr/bin/xcrun xcodebuild -project "/Volumes/Workspace/Personal Projects/FrameworkPractices/Carthage/Checkouts/LayoutKit/LayoutKit.xcodeproj" -scheme LayoutKitExampleLayouts -configuration Release -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build) failed with exit code 65:
** BUILD FAILED **