The most advanced NSFetchedResultsController reimplementation for a desktop Cocoa.

License: MIT License

Objective-C 99.67% Ruby 0.33%

coredata frc nstableview nsfetchedresultscontroller nsarraycontroller macos

kspfetchedresultscontroller's People

Contributors

Stargazers

Watchers

Forkers

proxi sudri wirelessheads wildthink anderscarling enquora priyatirounarayanane agiletortoise

kspfetchedresultscontroller's Issues

Sectioned FRC calls methods of a regular FRC's delegate

KSPSectionedFetchedResultsController fires faults during sections building

[object valueForKeyPath: self.sectionNameKeyPath];

😔

Translate the comments to English.

Right now there are many useful comments but for the most part they are in Russian.

Implement a faster LCS algorithm

[An O(ND) Difference Algorithm and Its Variations](An O%28ND%29 Difference Algorithm and Its Variations)

Don't expose a concrete table section class to FRC clients

KSPFetchedResultsController doesn't support fetch requests with a sort descriptors that specify key paths as sorting keys

Find places where we can replace -indexOfObject: with -indexOfObjectIdenticalTo:

-[NSManagedObject isEqual:] is implemented as a simple pointer comparison anyways.

FRC doesn’t respect fetchOffset and fetchLimit when a new objects are inserted into the context

Right now I have no idea how to fix this issue in an efficient way. And to be honest, I am not sure that this change is even required as long as iOS NSFetchedResultsController have the same behaviour.

Add a simple quick-start guide to the Readme.md

Installation using Cocoapods
Controller creation and initialization
Initial fetch
Becoming a delegate and getting change callbacks

Utilize NS_ASSUME_NONNULL_BEGIN ... END macro

No demo project added. Please add a demo project!

Sorting of a fetchedObjects may break when multiple objects are updated in one batch

Cover the main differences between the KSPFetchedResultsController and NSFetchedResultsController

There is an important difference in a way KSPFetchedResultsController merges the changes from the NSManagedObjectContextObjectsDidChangeNotification. The chosen way is better for NSTableView pairing, but may be a little confusing for the NSFetchedResultsController users.
KSPFetchedResultsControllerDelegate is notified not only about changes that already took place, but also about changes that are going to happen.
KSPSectionedFetchedResultsController uses NSObjects as 'names' for its sections as opposed for NSStrings used by NSFetchedResultsController.
KSPFetchedResultsController uses plain indices instead if index paths used by NSFetchedResultsController. Again, this is better for NSTableView pairing. Because of this the KSPSectionedFetchedResultsControllerDelegate method that is called on object change has completely different signature.
When reporting sections changes KSPSectionedFetchedResultsController has three possible events: section insertion, section movement and section deletion. Again, delegate method signature is a little different, and a separate enum (KSPSectionedFetchedResultsChangeType) is used to define possible sections changes.