thenounproject / collectionview Goto Github PK

The results controller protocol enforces some methods that are useful in some cases but because the existing types of controllers have different requirements, this protocol doesn't provide much.

Furthermore, with the controllers being generics, they must have alternatives to the protocol methods (currently _object(at:)) to make use of those generic types.

Possible solutions:

• Dont't have a shared protocol (it does help consolidate the delegate, but doesn't provide much)
• Simplify the protocol to the core functions (i.e. numberOfSections, numberOfObjects(in:))

The other goal here is to break out the different controller processing aspects to make them easily reused by different types of controllers. For example, something similar to the ManagedResultsController could serve well as a base for the others to build upon.

Right now the CollectionViewDelegate functions related to item selection all report a single indexPath. If you select multiple it will report one (usually the last) indexPath that was selected or deselected.

The alternative would be to report all of the index paths in a set (or array) to give you greater control over how to react to the change.

@objc optional func collectionView(_ collectionView: CollectionView, didSelectItemAt indexPath: IndexPath)
Would become
@objc optional func collectionView(_ collectionView: CollectionView, didSelectItemsAt indexPath: Set<IndexPath>)

Why not make it a Cocoapods library.

This is definitely cause by a flaw in the moving logic.

The cell manipulation logic and editing sessions could certainly be improved. It started for a simple use case but was then extended without implementing the proper algorithms (also, not sure what the proper ones are but I'm assuming they exist).

Here is an example form Lingo.

https://developer.apple.com/documentation/appkit/nscollectionviewprefetching
It's useful for load data like large images.

Does CollectionView support multi select by mouse ?