Classes

A helper for adding top and bottom shadows into any UIScrollView-based class. You create an instance in your subclass and forward calls from layoutSubviews.

Holds configuration for MMMScrollViewShadows that can be set only on initialization time.

A view that’s used internally to render shadows in MMMAutoLayoutScrollView. Open for reuse in cases we want to display compatible shadows but differntly controlled. Note that this does not support Auto Layout, you have to manage its frame.

Web view supporting top & bottom shadows.

A base for table view cells redeclareing the designated initializer into the one we typically use, so subclasses do not have to.

A simple table view cell wrapping the given view.

This is handy when you have a view already and just want to show it as one more cell.

The view being wrapped should support Auto Layout and inflate its height properly. The cell has its selectionStyle set to UITableViewCellSelectionStyleNone as these kind of cells typically do not appear selected.

Opening a deep link can involve following through one or more steps, for example:

1) make sure the main screen is visible and can switch between the pages; 2) move to the recipes page; 3) open recipe with ID N; 4) scroll to ingredients, etc.

This is a single step in such a chain.

A navigation path is just a collection of one or more “hops”.

Manages switching between different sections of the app (kind of internal URL router). It’s like a central hub accepting navigation requests and then passing them to the entities that able to perform them. (The entities that are able to open requests should register themselves as handlers.)

Info about a navigation request that is passed to handlers.

This is to be used during development to stub not ready yet parts of the app.

A limited replacement for UIImageView fixing its inability to properly work with images having non-zero alignmentRectInsets when scaled.

Note that this view is already constrained to the aspect ratio of the image’s alignment rect, so you should not use hard (equal) pins against both width and height or against all edges.

A vertical scroll view with a content view and preconfigured constraints, so there is no need in creating a scroll view / content view sandwitch manually every time.

It also supports top and bottom shadows that are displayed only when the content is clipped. The shadows can be enabled individually and they can sit either flush with the edges of the scroll view or can be inset according to adjustedContentInset, which can be handy when vertical safeAreaInsets need to be taken into account. (Note that contentInsetAdjustmentBehavior has to be either None or Always on this view since “automatic” options can lead to cyclic calculations.) Also note that scroll indicators are disabled here by default.

Begin by adding your controls and constraints into the contentView ensuring that its size can be derived from your constraints alone. Avoid constraints to the scroll view itself or outside views unless you are prepared to deal with the consequences.

Note that the width of the contentView will be constrainted hard to be equal to the width of the scroll view and its height will be constrained with prio 251 to be at least as large as the height of the scroll view.

A subview of MMMAutoLayoutScrollView where all the subviews should be added.

• (It’s not different from UIView, but making it of its own class helps when browsing view hierarchies.)

To be used during development as a placeholder for not yet implemented views. It inherits a vertical scroll view so it’s possible to see that gesture recognizers of the container do not interfere with a typical scrolling.

This is to track the navigation state of the app and have the possibility to programmatically return to registered points of the navigation path. The actual navigation entities of the app (usually view controllers) must cooperate in order to achieve this.

The possibility to go back is needed to properly handle in-app links. We have a basic mechanism for this (MMMNavigation) which allows to “open” a part of a link and forward the remaining parts to the corresponding handler down the navigation tree. The handlers thus need to be able to “close” current navigation path before opening something new.

Although navigation in the app is better represented by a tree, we assume here that at least the current path in this tree can be represented as a stack. Each element of the stack can correspond to a modal view controller or alert view, for example, but it can also correspond to a special state of the app or a screen.

A table view supporting top and bottom shadows.

Holds configuration for MMMShadowView.

Helper view for adding custom layer shadows, while taking the the shadow sizes in conserderation for its final frame.

Auto Layout does not support constraints against groups of items, so this is for the cases a normal UIView is typically used as a container for such a group. Unlike UIView we have translatesAutoresizingMaskIntoConstraints set to NO already. Also MMMContainerView does not intercept touches but subviews still do.

This is to group a few simple layout helpers.

A little helper for velocity/acceleration calculations: you feed it values with timestamps and can get the most recent acceleration/velocity values.

Minimalistic animation helpers.

Terminology:

• Normalized time — time value from the [0; 1] range.
• Curved time — normalized time transformed using one of the predefined animation curves.

Minimalistic animator object in the spirit of helpers defined in MMMAnimation.

You add animation items, which are basically a set of blocks that will be called every frame on the main run loop and when it’s done or cancelled.

It’s not for every case, it’s for those moments when you know the duration in advance and just need to animate a simple custom property and don’t want to subclass CALayer or mess with its multithreaded delegates.

The animator object does not take care of interpolation of values nor time curves, the normalized time passed into update blocks can be transformed and values can be interpolated using simple helpers in MMMAnimation.

Sort of a handle returned by MMMAnimator when a new animation is scheduled. Keep it around, otherwise the animation will be cancelled.

Collection view supporting top & bottom shadows.

Auto Layout does not support relationships between empty spaces, so we need to use spacer views and set such constraints between them. This one is a transparent and by default hidden view which can be used as such a spacer. It has no intrinsic size and low content hugging and compression resistance priorities. Unlike UIView we have translatesAutoresizingMaskIntoConstraints set to NO already.

A container which lays out its subviews in certain direction one after another using fixed spacing between them. It also aligns all the items along the layout line according to the given alignment settings. Note that you must use setSubviews: method instead of feeding them one by one via addSubview:. This is kind of a UIStackView that we understand the internals of.

Vertical version of MMMStackContainer.

Horizontal version of MMMStackContainer.

Wraps a view that uses Auto Layout into a manual layout view providing sizeThatFits: for the outside world. Can be handy with old APIs that do not fully support Auto Layout.

Wraps a view padding it from all the sides.

A view displaying a gradient from top to bottom. The linearity of the gradient can be controlled. Can be handy for shadow overlays, etc.

A base for app-specific stylesheets: commonly used paddings, colors, fonts, etc in a single place.

Dimension converter that uses a table of scales.