## [Dev Diaries] Force Directed Layout

Sometimes, the worlds of computer graphics and physics collide in the most beautiful ways.

Everybody loves UICollectionViews, but after a while, those grids tend to be a bit restrictive. The "flow" layout is fine and all, but what if we wanted to have the cells arranged in an "organic" manner?

##### Let's talk about forces

In nature, almost everything is about forces. Gravity is probably the one everyone is the most familiar with, and it goes straight down at roughly 9.8 m/s/s. What that means is that at the beginning, your object goes at 0 m/s, then after a second it goes at 9.8 m/s, then after another second, it goes at 19.6 m/s, etc. When an object is on the ground, the gravity *still applies*, but it's compensated by the floor pushing up with a force equal to the gravity.

Good ole Newton says that what matters is the **sum** of all the forces that apply to an object. From that you can deduce the acceleration the object is subjected to (in m/s/s), and by derivation, the speed of an object at a given time. Speed is the distance moved by unit of time, so from the speed, we can determine the position of an object on which the force applies.

For the rest of this post, we will assume everything has a mass of 1, because it simplifies a bit the operations.

In terms of code, I decided to have a `struct`

representing forces in a way that will give me the operations I will need later:

- adding two forces together
- getting the angle of the force in a plane
- getting the magnitude (length of the vector)

```
struct Force {
let dx: CGFloat
let dy: CGFloat
static func +(lhs: Force, rhs: Force) -> Force {
return Force(lhs.dx+rhs.dx,lhs.dy+rhs.dy)
}
static func /(lhs: Force, rhs: CGFloat) -> Force {
return Force(lhs.dx/rhs, lhs.dy/rhs)
}
init(_ x: CGFloat, _ y: CGFloat) {
dx = x
dy = y
}
var angle : CGFloat {
return CGFloat(atan2(Double(dy), Double(dx)))
}
var magnitude : CGFloat {
return sqrt(dx*dx+dy*dy)
}
}
```

##### Attraction

We'll need our cells to be attracted to a certain point in the plane. Ideally, if there's only one cell, it'll sit at that point, and if there are two, they will be as close as possible to there, while not overlapping (more on that later).

Gravity has flair, but its exponential nature is a bit *too* powerful. For force directed graphs (like the ones dot produces), we tend to go with its linear cousin: the spring. It also is easier to wrap your head around: you attach all the cells to the center with a spring, and they will try to get back there.

Spring force is expressed with Hooke's law

*k*is the stiffness of the spring- ∂ is how far we are from the "ideal" distance to the other end of the spring

You can see that compressing a spring produces an "extension" force (it pushes the two ends away because ∂ is negative), and the opposite "attraction" force (when ∂ is positive).

##### Repulsion

We *could* use the spring for repulsion as well, but it'd mean "wiring" all the cells with their nearest neighbours and always keeping track of which cells are attached to which other cells. It's too complex to manage, but fortunately, we have another physics law that repulses and looks quite natural: magnets.

Magnets attract obviously, but they also repulse quite heavily. And because we want that repulsion to be extremely high when the objects are super close and negligible when they are far away from each other, *this time* we kind of need an inverse square law. Coulomb's law to the rescue!

*k*isn't that important for us, but its value is`9×10`

^{9}N⋅m^{2}⋅C^{−2}- The two
`Q`

s are the electric charges of the objects *r*is the distance between them

You can see that objects with the same electric charge repulse each other, while objects with opposite charges attract each other.

So why didn't we use this for our attraction law? The *big* problem with using that kind of force is that it's very computationally expensive: every cell will affect *every other cell*. Calculating the resulting force is proportional to the *square* of the number of cells. Simple spring mechanics is a lot simpler to manage for attraction, but we won't escape the complexity of repulsion.

Sidenote: what's up with thatkvalue? 😳

That's physics for you, I'm afraid. We need to match the formula to the real world, and that's the number that fits what we see.

For our purposes, we have made-up identical "charges" on our cells anyways, so we will have k(Q²/r²). Might as well ignore k altogether and go with Q³/r²

Of course, that value of Q has no "physical" value, it's just convenient.

##### Let's create a universe

So, we have decided on our forces, now we need something to apply them to. Meet `Node`

, the structure which will handle the physics side of our layout. It needs to hold 3 informations:

- the position the cell is at : x and y
- some way to differentiate it from other cells (because of the repulsion bit) : a uuid
- a way to link it to the data source of the
`UICollectionView`

: an IndexPath

Here's the boring first part:

```
struct Node : Equatable, Hashable {
var x : CGFloat = 0
var y : CGFloat = 0
let uuid = UUID() // for identification purposes
var indexPath : IndexPath
init(x px: CGFloat = 0, y py: CGFloat = 0, for idx: IndexPath) {
x = px
y = py
indexPath = idx
}
static func == (lhs: Node, rhs: Node) -> Bool {
return lhs.uuid == rhs.uuid
}
// ...
}
```

The first interesting bit is the attraction function. It is extremely verbose for education purposes, you can compactify and optimize it quite a bit.

```
func attraction(center: CGPoint, stiffness: CGFloat) -> Force {
// Hooke's Law: F = -k•∂ (∂ being the "ideal" distance minus the actual distance)
let dx = x - center.x
let dy = y - center.y
let angle = CGFloat(atan2(Double(dy), Double(dx)))
let delta = sqrt(dx*dx+dy*dy)
let intensity = stiffness * delta
let ix = abs(intensity * cos(angle))
let fx : CGFloat
if center.x > x { // positive force to the right
fx = ix
} else {
fx = -ix
}
let iy = abs(intensity * sin(angle))
let fy : CGFloat
if center.y > y { // positive force to the bottom
fy = iy
} else {
fy = -iy
}
return Force(fx,fy)
}
```

The really big one, although not that complicated from the code point of view, is the repulsion force. It has to take into account every single other node. As with the attraction, it is verbose for the sake of clarity, and can obviously be optimized. One such optimization is to return early with a `0`

if the distance is "too great", but that's beyond the scope of what we are trying to do here.

```
func repulsion(others: [Node], charge: CGFloat) -> Force {
var totalForce = Force(0,0)
for n in others.filter({ (on) -> Bool in
on.uuid != self.uuid // just in case
}) {
// Coulomb’s Law; F = k(Q1•Q2/r²)
// Since we're dealing with arbitrary "charges" here, we'll simplify to F = C³/r²
// We want repulsion (Q1=Q2) and not deal with big numbers, so that works
var dx = x - n.x
var dy = y - n.y
if dx == 0 && dy == 0 { // wiggle a bit
let room : CGFloat = 0.05
dx += CGFloat.random(in: -room...room)
dy += CGFloat.random(in: -room...room)
}
let angle = CGFloat(atan2(Double(dy), Double(dx)))
let delta = max(0.000001,sqrt(dx*dx+dy*dy)) // do NOT divide by zero you fool
let intensity = pow(charge,3)/(delta*delta)
let ix = abs(intensity * cos(angle))
let fx : CGFloat
if n.x > x { // positive force to the left
fx = -ix
} else {
fx = ix
}
let fy : CGFloat
let iy = abs(intensity * sin(angle))
if n.y > y { // positive force to the bottom
fy = -iy
} else {
fy = iy
}
totalForce = totalForce + Force(fx,fy)
}
return totalForce
}
```

Note the check for divide-by-zero shenanigans (in case two cells overlap), that is covered in two different ways: we wriggle the cells a bit to avoid being exactly on top of each other *and* we don't divide by zero if the wriggling failed. The resulting force is the *sum* of being repulsed by every other cell.

Putting it all together, we'll just need to sum attraction and repulsion. For some reason, I have also included the possibility of adding a force to a node.

```
func globalForce(center: CGPoint, otherNodes: [Node], stiffness: CGFloat, charge: CGFloat) -> Force {
let a = attraction(center: center, stiffness: stiffness)
let r = repulsion(others: otherNodes, charge: charge)
return a + r
}
static func +(lhs: Node, rhs: Force) -> Node {
return Node(x: lhs.x+rhs.dx, y: lhs.y+rhs.dy, for: lhs.indexPath)
}
```

Because we have to compute the global force (which depends on every node) for every node, we end up with a square order complexity. But since the force calculation is independant for every node, we can spread the calculations of as many threads as we can to claw a bit of performance back. Thankfully I have a Task system handy.

Here is the function that takes all nodes, and computes where they should go next. `springStiffness`

and `electricCharge`

are instance variables of the layout. Its output is the pair composed of the new node positions and the total movement of all the nodes, for a reason that will become clear later.

```
func computeNewPositions(center: CGPoint, nodes: [Node]) -> (nodes: [Node], movement: CGFloat) {
// if the total movement is less than threshold, will return nil
var totalMovement : CGFloat = 0
var newNodes : [Node] = []
var computeTasks : [Task] = []
let lock = NSLock()
for n in nodes {
let t = Task() {
let f = n.globalForce(center: center, otherNodes: nodes, stiffness: self.springStiffness, charge: self.electricCharge)
let nn = n + f
lock.lock()
newNodes.append(nn)
totalMovement += f.magnitude
lock.unlock()
}
computeTasks.append(t)
}
let waitSem = DispatchSemaphore(value: 0)
let compute = Task.group(computeTasks)
compute.perform { (outcome) in
waitSem.signal()
}
waitSem.wait()
return (newNodes, totalMovement)
}
```

Now's the time to implement a few of the overrides for our custom layout. Let's start with the obvious ones:

```
protocol ForceDirectedLayoutDelegate {
func layoutDidFinish()
}
class ForceDirectedLayout : UICollectionViewLayout {
// in case you want to know
var delegate : ForceDirectedLayoutDelegate? = nil
// maths
var springStiffness : CGFloat = 0.02 // max(width,height)/1000 seems ok
var electricCharge : CGFloat = 10 // max(width,height)/2 seems ok
var cellSize : CGSize = CGSize(width: 20,height: 20) // obviously too small for real use
// ...
override func shouldInvalidateLayout(forBoundsChange newBounds: CGRect) -> Bool {
return true // because the center changes...
}
override var collectionViewContentSize: CGSize {
var totalRect = CGRect(origin: CGPoint.zero, size: self.collectionView?.frame.size ?? CGSize.zero)
for cachedA in cachedAttributes.values {
totalRect = totalRect.union(
CGRect(x: cachedA.center.x-cachedA.size.width*0.5,
y: cachedA.center.y-cachedA.size.height*0.5,
width: cachedA.size.width, height: cachedA.size.height))
}
return totalRect.size
}
}
```

The eagle eyed among you will have noticed a `cachedAttributes`

instance variable. For some reason, `UICollectionView`

itself doesn't cache the current position and size of a cell. If you call `collectionView.layoutAttributesForItem(at: idx)`

it gives you a `nil`

value, forcing you to regenerate the attributes at every stage (and there are many). I have decided to cache the cell attributes internally as a backup, and if Apple decides at some point to return a non-nil value, I will use it. But what it forces me to do is to make sure I detect cell deletion. If a cell is removed, I need to remove its cached attributes. You can skip that deletion part if you want, or code it more efficiently, it's just for completeness' sake.

```
/// Unfortunately, collectionView.layoutAttributesForItem doesn't seem to be caching the previous attributes
/// We do it ourselves as a backup
fileprivate var cachedAttributes = [IndexPath:UICollectionViewLayoutAttributes]()
/// Since we cache the data ourselves, we need to cleanup if elements are removed
override func prepare() {
super.prepare()
guard let collection = self.collectionView else {
cachedAttributes.removeAll()
return
}
let sectionCount = collection.dataSource?.numberOfSections?(in: collection) ?? 1
var rowCounts = [Int:Int]()
for s in 0..<sectionCount {
rowCounts[s] = collection.dataSource?.collectionView(collection, numberOfItemsInSection: s) ?? 0
}
for removed in cachedAttributes.keys.filter({ (idx) -> Bool in
return idx.section >= sectionCount || idx.row >= (rowCounts[idx.section] ?? 0) // hence the dictionary, no index out of bounds
}) {
cachedAttributes.removeValue(forKey: removed)
}
}
```

And finally, the override that makes everything work: the layout function itself. Unfortunately, if *a* node changes position, it affects every other node, potentially, so we can't update only a partial list. We need to do them all every single time.

But wait. We have been talking about forces for 2000+ words here. Forces can help you figure out positions but they aren't positions themselves. Yep, that's right, we have an *animated* layout: from the current position of the cells, you calculate where the cells should go *next*. So... when does the animation *end*?

That's where the `movement`

output of the computation function comes in. When we reach an equilibrium (like the floor force and the gravity exactly compensating each other), the movement drops to zero. Of course, in the real world, it's a neverending process but we can just decide that the layout stops animating as soon as the total movement of every cell falls below a certain threshold. I have decided arbitrarily that a third of a pixel is imperceptible enough, even on a 3x retina screen but if you want to stop the animation sooner, feel free to raise that a bit.

So, the mechanics will be as follows:

- we take the current positions of all the cells
- we compute their new positions
- if they didn't move much, we stop
- if they still are moving quite a bit, we instruct the collection view to keep going by invalidating the layout again

```
// unfortunately, every node affects every other node, so we can't do partial updates
override func layoutAttributesForElements(in rect: CGRect) -> [UICollectionViewLayoutAttributes]? {
var attributes : [UICollectionViewLayoutAttributes] = []
var nodes = [Node]()
if let collectionView = self.collectionView {
for i in 0..<(collectionView.dataSource?.collectionView(collectionView, numberOfItemsInSection: 0) ?? 0) {
let idx = IndexPath(row: i, section: 0)
let currentAttributes : UICollectionViewLayoutAttributes
if let ca = (collectionView.layoutAttributesForItem(at: idx) ?? cachedAttributes[idx]) {
currentAttributes = ca
} else {
// randomize start positions, just for funsies
currentAttributes = UICollectionViewLayoutAttributes(forCellWith: idx)
currentAttributes.center = CGPoint(
x: CGFloat.random(in: 0...self.collectionViewContentSize.width),
y: CGFloat.random(in: 0...self.collectionViewContentSize.height)
)
currentAttributes.size = cellSize
cachedAttributes[idx] = currentAttributes
}
attributes.append(currentAttributes)
nodes.append(Node(x: currentAttributes.center.x, y: currentAttributes.center.y, for: idx))
}
let center = self.collectionView?.absoluteCenter ?? CGPoint.zero
let nextIteration : (nodes: [Node], movement: CGFloat)
nextIteration = computeNewPositions(
center: center,
nodes: nodes)
for n in nextIteration.nodes {
if let attrsIdx = attributes.firstIndex(where: { $0.indexPath == n.indexPath }) {
let attrs = attributes[attrsIdx]
attrs.center = CGPoint(x: n.x, y: n.y)
attributes[attrsIdx] = attrs
}
}
// if it's still moving, keep going
if nextIteration.movement > 0.3 { // subpixel animation
DispatchQueue.main.asyncAfter(deadline: DispatchTime.now() + 0.05) {
self.invalidateLayout()
}
} else {
DispatchQueue.main.async {
self.delegate?.layoutDidFinish()
}
}
}
return attributes
}
```

Please note that I position new cells randomly. They *could* appear in the middle of the other cells. Depending on the effect you want to go for, you can have they come from a specific point, or randomly from the borders, etc.

And that's it! I have made a quick example that adds round cells progressively to a collection view, and here's the result:

You can obviously get the whole thing on GitHub, prepared for use as a swift package for the future Xcode version.