Now that we do a lot of autolayout stuff programmatically, it would be great to have some basic helper managing diffs to a border.

We need to notify the delegate when a filter is removed.

• provide default implementation.

We should add the option to use a custom view for the title of the navigation bar.

We should have a bigger zone for the back click on the pseudo nav-bar.
Actually, we're going to use the full nav bar to activate the left action when it's present.

For the Flaneur iOS app, we need a system to build forms conveniently.

It includes:

• A text field with a label
• A text area with a label
• A button to select an image with a label
• The option to enable/disable a button somewhere (most likely on the navigation bar)
• The option to "jump" from field to field

• Don't use a UIViewController but a simpler UIView just like FlaneurCollectionView

So that we can set the font for UILabel.

Once #16 is completed,

• Add a selection tool using an horizontally scrolling collection view of items with different views
• Add the option to select an arbitrary number of images
• Add an optional action destructive button

It would be super convenient to attach any kind of information to a filter so that when it's removed, we can get more information about what we're supposed to do.

We need to support multiselection of cells.

To do so, we should provide a readonly access to the collection view so that the client can set allowsMultipleSelection to true and the delegate method should support deselection.

The Flaneur app is using a pseudo-nav bar that is more than 44px high.
As such, a view to factorize this behavior would be great.

Specs:

• It can have a plain title alone, left aligned or center aligned.
• It can have 1 optional left button item with configurable behavior
• It can have optional right button items with configurable behavior:
  • Either 1 text
  • Or multiple icons

It style should be configurable via UIAppearance so that configuring it once and for all is enough.

Cf. designs

IGListKit can instanciate cells in many ways, we should use an Enum to let the user decide what method he'd like to choose best.

So far, we deal only with 2 columns with a 1.0 height/width ratio, but the view could totally manage different values. Let's set them in the configure.

Add modal view to indicate progress

Section controllers are not updating cells, even when isEqual for the ListDiffable returns false.

#6 was a little extreme. Only the title should trigger the left action otherwise, the right buttons can trigger it when the tap is not precise enough.

Add controls over the right buttons of the navigation bar to:

• toggle between 2 states
• being able to select/deselect

Cell selection management is not the most convenient part of UIKit and it makes FlaneurFormSelectElementCollectionViewCell buggy as it is as when marking a cell as selected prevent it from being further deselected.

UICollectionView seems to manage some internal state that is not synchronized between cells' isSelected and UICollectionView's indexPathsForSelectedItems.

We want a convenient way to place annotations on a map.

The right buttons of a FlaneurNavigationBar should be configurable dynamically. For instance, if we want to set them asynchronously.

We need a tool to manage a collection view on 2 columns, with an optional filter mechanism.

• It should allow another component to style the cell
• It should allow to manage margins conveniently
• It should display a banner of filters, that operate under an inclusive basis (OR)

Flexible collection view displaying cells from a server.
It should deal with:

• no data
• no network
• efficiency

We'll use it as a POC with IGListKit

Sometimes cells need to display data from the network and we need a spinner to show an activity is going on but then, many outcomes can happen:

• success: the data is here
• failure: the data failed for many reasons. For instance, geolocation might have failed because there is no network, because the user does not allow to request his location (and maybe we can politely ask him to reconsider), etc.

We need something similar to what the Swift Talk guys are doing in their Swift Talk #3 - Loading View Controllers video.