motion-yapper 0.0.3 → 0.1.0

data/vendor/Pods/BuildHeaders/YapDatabase/YapDatabaseView.h

@@ -1,127 +0,0 @@
-#import <Foundation/Foundation.h>
-
-#import "YapDatabaseExtension.h"
-#import "YapDatabaseViewTypes.h"
-#import "YapDatabaseViewOptions.h"
-#import "YapDatabaseViewConnection.h"
-#import "YapDatabaseViewTransaction.h"
-#import "YapDatabaseViewMappings.h"
-#import "YapDatabaseViewChange.h"
-#import "YapDatabaseViewRangeOptions.h"
-
-/**
- * Welcome to YapDatabase!
- * 
- * https://github.com/yaptv/YapDatabase
- * 
- * The project wiki has a wealth of documentation if you have any questions.
- * https://github.com/yaptv/YapDatabase/wiki
- *
- * YapDatabaseView is an extension designed to work with YapDatabase.
- * It gives you a persistent sorted "view" of a configurable subset of your data.
- *
- * For the full documentation on Views, please see the related wiki article:
- * https://github.com/yaptv/YapDatabase/wiki/Views
- * 
- * Just in case you don't have Internet access,
- * see the quick overview in YapDatabaseView.h.
-**/
-@interface YapDatabaseView : YapDatabaseExtension
-
-/* Inherited from YapDatabaseExtension
- 
-@property (nonatomic, strong, readonly) NSString *registeredName;
-
-*/
-
-/**
- * See the wiki for an example of how to initialize a view:
- * https://github.com/yaptv/YapDatabase/wiki/Views#wiki-initializing_a_view
- *
- * @param groupingBlock
- * 
- *   The grouping block handles both filtering and grouping.
- *   
- *   @see YapDatabaseViewTypes.h for block type definition(s).
- * 
- * @param groupingBlockType
- * 
- *   Specify the type of groupingBlock that is being passed.
- *   
- *   @see YapDatabaseViewTypes.h for block type definition(s).
- * 
- * @param sortingBlock
- * 
- *   The sorting block handles sorting of objects within their group.
- *   
- *   @see YapDatabaseViewTypes.h for block type definition(s).
- * 
- * @param sortingBlockType
- * 
- *   Specify the type of sortingBlock that is being passed.
- *   
- *   @see YapDatabaseViewTypes.h for block type definition(s).
- *
- * @param versionTag
- *
- *   If, after creating a view, you need to change either the groupingBlock or sortingBlock,
- *   then simply use the versionTag parameter. If you pass a versionTag that is different from the last
- *   initialization of the view, then the view will automatically flush its tables, and re-populate itself.
- *
- * @param options
- *
- *   The options allow you to specify things like creating an in-memory-only view (non persistent).
-**/
-
-- (id)initWithGroupingBlock:(YapDatabaseViewGroupingBlock)groupingBlock
-          groupingBlockType:(YapDatabaseViewBlockType)groupingBlockType
-               sortingBlock:(YapDatabaseViewSortingBlock)sortingBlock
-           sortingBlockType:(YapDatabaseViewBlockType)sortingBlockType;
-
-- (id)initWithGroupingBlock:(YapDatabaseViewGroupingBlock)groupingBlock
-          groupingBlockType:(YapDatabaseViewBlockType)groupingBlockType
-               sortingBlock:(YapDatabaseViewSortingBlock)sortingBlock
-           sortingBlockType:(YapDatabaseViewBlockType)sortingBlockType
-                 versionTag:(NSString *)versionTag;
-
-- (id)initWithGroupingBlock:(YapDatabaseViewGroupingBlock)groupingBlock
-          groupingBlockType:(YapDatabaseViewBlockType)groupingBlockType
-               sortingBlock:(YapDatabaseViewSortingBlock)sortingBlock
-           sortingBlockType:(YapDatabaseViewBlockType)sortingBlockType
-                 versionTag:(NSString *)versionTag
-                    options:(YapDatabaseViewOptions *)options;
-
-@property (nonatomic, strong, readonly) YapDatabaseViewGroupingBlock groupingBlock;
-@property (nonatomic, strong, readonly) YapDatabaseViewSortingBlock sortingBlock;
-
-@property (nonatomic, assign, readonly) YapDatabaseViewBlockType groupingBlockType;
-@property (nonatomic, assign, readonly) YapDatabaseViewBlockType sortingBlockType;
-
-/**
- * The versionTag assists you in updating your blocks.
- *
- * If you need to change the groupingBlock or sortingBlock,
- * then simply pass a different versionTag during the init method, and the view will automatically update itself.
- * 
- * If you want to keep things simple, you can use something like @"1",
- * representing version 1 of my groupingBlock & sortingBlock.
- * 
- * For more advanced applications, you may also include within the versionTag string:
- * - localization information (if you're using localized sorting routines)
- * - configuration information (if your sorting routine is based on some in-app configuration)
- *
- * For example, if you're sorting strings using a localized string compare method, then embedding the localization
- * information into your versionTag means the view will automatically re-populate itself (re-sort)
- * if the user launches the app in a different language than last time.
- * 
- * NSString *localeIdentifier = [[NSLocale currentLocale] localeIdentifier];
- * NSString *versionTag = [NSString stringWithFormat:@"1-%@", localeIdentifier];
-**/
-@property (nonatomic, copy, readonly) NSString *versionTag;
-
-/**
- * The options allow you to specify things like creating an in-memory-only view (non persistent).
-**/
-@property (nonatomic, copy, readonly) YapDatabaseViewOptions *options;
-
-@end

data/vendor/Pods/BuildHeaders/YapDatabase/YapDatabaseViewChange.h

@@ -1,272 +0,0 @@
-#import <Foundation/Foundation.h>
-
-typedef enum {
-	YapDatabaseViewChangeInsert = 1,
-	YapDatabaseViewChangeDelete = 2,
-	YapDatabaseViewChangeMove   = 3,
-	YapDatabaseViewChangeUpdate = 4,
-	
-} YapDatabaseViewChangeType;
-
-typedef enum {
-	YapDatabaseViewChangedObject     = 1 << 0, // 0001
-	YapDatabaseViewChangedMetadata   = 1 << 1, // 0010
-	YapDatabaseViewChangedDependency = 1 << 2, // 0100
-	
-} YapDatabaseViewChangesBitMask;
-
-
-/**
- * YapDatabaseViewChange is designed to help facilitate animations to tableViews and collectionsViews.
- * 
- * In addition to the documentation available in the header files,
- * you may also wish to read the wiki articles online,
- * which are designed to give you an overview of the various technologies available.
- * 
- * General information about setting up and using Views:
- * https://github.com/yaptv/YapDatabase/wiki/Views
- * 
- * General information about technologies which integrate with Views:
- * https://github.com/yaptv/YapDatabase/wiki/LongLivedReadTransactions
- * https://github.com/yaptv/YapDatabase/wiki/YapDatabaseModifiedNotification
-**/
-
-@interface YapDatabaseViewSectionChange : NSObject <NSCopying>
-
-/**
- * The type will be either:
- * - YapDatabaseViewChangeInsert or
- * - YapDatabaseViewChangeDelete
- *
- * @see YapDatabaseViewChangeType
-**/
-@property (nonatomic, readonly) YapDatabaseViewChangeType type;
-
-/**
- * The section index.
- * 
- * If the type is YapDatabaseViewChangeDelete, then this represents the originalIndex of the section (pre-animation).
- * If the type is YapDatabaseViewChangeInsert, then this represents the finalIndex of the section (post-animation).
-**/
-@property (nonatomic, readonly) NSUInteger index;
-
-/**
- * The corresponding group for the section.
-**/
-@property (nonatomic, readonly) NSString *group;
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-@interface YapDatabaseViewRowChange : NSObject <NSCopying>
-
-/**
- * The type will be one of:
- * - YapDatabaseViewChangeInsert
- * - YapDatabaseViewChangeDelete
- * - YapDatabaseViewChangeMove
- * - YapDatabaseViewChangeUpdate
- * 
- * @see YapDatabaseViewChangeType
-**/
-@property (nonatomic, readonly) YapDatabaseViewChangeType type;
-
-/**
- * The changes property is a bitmask representing what changed for the corresponding row in the database.
- *
- * There are 3 types represented in the bit mask:
- * - YapDatabaseViewChangedObject
- * - YapDatabaseViewChangedMetadata
- * - YapDatabaseViewChangedDependency
- * 
- * YapDatabaseViewChangedObject means the object was changed via setObject:forKey:inCollection:.
- *
- * YapDatabaseViewChangedMetadata means the metadata was changed.
- * This might have happend implicitly if the user invoked setObject:forKey:inCollection: (implicitly setting
- * the metadata to nil). Or explicitly if the user invoked setObject:forKey:inCollection:withMetadata: or
- * replaceMetadata:forKey:inCollection:.
- * 
- * YapDatabaseViewChangedDependency means the row was flagged due to a cell drawing dependency configuration.
- * See YapDatabaseViewMappings: setCellDrawingDependencyForNeighboringCellWithOffset:forGroup:
- * 
- * Keep in mind that this is a bitmask. So, for example, all bits might be set if
- * a row was updated, and was also flagged due to an inter-cell drawing dependency.
- *
- * This may be useful for various optimizations. For example:
- * The drawing of your cell depends only on the object.
- * However, your objects are rather large, and you're using metadata to store small subsets of the object
- * that often need to be fetched. In addition, you're keeping other information in metadata such as refresh dates
- * for pulling updates from the server. The grouping and sorting block are optimized and use only the metadata.
- * However this means that the metadata may change (due to a refresh date update),
- * when in fact the object itself didn't change.
- * So you could optimize a bit here by skipping some cell updates.
- * 
- * if (change.type == YapDatabaseViewChangeUpdate)
- * {
- *     if (change.modifiedColumns & YapDatabaseViewChangedObject) {
- *         // object changed, update cell
- *     }
- *     else {
- *         // only the metadata changed, so we can skip updating the cell
- *     }
- * }
- *
- *
- * @see YapDatabaseViewChangesBitMask
-**/
-@property (nonatomic, readonly) int changes;
-
-/**
- * The indexPath & newIndexPath are available after
- * you've invoked getSectionChanges:rowChanges:forNotifications:withMappings:.
- *
- * @see YapDatabaseConnection getSectionChanges:rowChanges:forNotifications:withMappings:
- * 
- * These properties are designed to help facilitate animations to tableViews and collectionsViews.
- * 
- * Recall that a view has no concept of sections.
- * That is, a view has groups not sections.
- * A group is a string, and a section is just a number.
- * 
- * Using groups allows a view to be more dynamic.
- * Your view may contain dozens of groups,
- * but a particular tableView within your app may only display a subset of the groups.
- * 
- * For example, you may have a view for displaying products in a grocery store.
- * Each product is grouped by department (e.g. produce, deli, bakery), and sorted sorted by name.
- * Using this view you can easily bring up a table view which displays only
- * a few departments such as: liquor, wine, beer.
- * 
- * In this example:
- * - Section 0 = liquor
- * - Section 1 = wine
- * - Section 2 = beer
- *
- * NSArray *groups = @{ @"liquor":@(0), @"wine":@(1), @"beer":@(2) };
- * YapDatabaseMappings *mappings = [YapDatabaseViewMappings mappingsWithGroups:groups view:@"order"];
- *
- * The mappings are then used to "map" between the 'groups in the view' and 'items in the table'.
- * 
- * Mappings can provide a lot of additional functionality as well.
- * For example, you can configure the mappings to only display a particular range within a group.
- * This is similar to a LIMIT & OFFSET in SQL.
- * This is the tip of the iceberg. See YapDatabaseViewMappings.h for more info.
- *
- * In order to animate changes to your tableView or collectionView, you eventually do something like this:
- * 
- * NSArray *sectionChanges = nil;
- * NSArray *rowChanges = nil;
- * [databaseConnection getSectionChanges:&sectionChanges
- *                            rowChanges:&rowChanges
- *                      forNotifications:notifications
- *                          withMappings:mappings];
- * 
- * This gives you a list of changes as they affect your tableView / collectionView.
- *
- * The indexPath and newIndexPath properties are modeled after:
- * NSFetchedResultsControllerDelegate controller:didChangeObject:atIndexPath:forChangeType:newIndexPath:
- * 
- * - indexPath represents the ORIGINAL indexPath for the row.
- *   It is non-nil for the following types : Delete, Move, Update.
- *   (And nil for insert since there was no original indexPath.)
- *
- * - newIndexPath represents the FINAL indexPath for the row.
- *   It is non-nil for the following types : Insert, Move.
- *   (And nil for delete since there is no final indexPath.)
- *   (And nil for update since that's how NSFetchedResultsController works,
- *    and thus how existing code might expect it to work.)
- * 
- * Once you have the sectionChanges & rowChanges, you can animate your tableView very simply like so:
- * 
- * PS - For a FULL CODE EXAMPLE, see the wiki:
- * https://github.com/yaptv/YapDatabase/wiki/Views#wiki-animating_updates_in_tableviews_collectionviews
- *
- * if ([sectionChanges count] == 0 & [rowChanges count] == 0)
- * {
- *     // Nothing has changed that affects our tableView
- *     return;
- * }
- *
- * // Familiar with NSFetchedResultsController?
- * // Then this should look pretty familiar
- *
- * [self.tableView beginUpdates];
- *
- * for (YapDatabaseViewSectionChange *sectionChange in sectionChanges)
- * {
- *     switch (sectionChange.type)
- *     {
- *         case YapDatabaseViewChangeDelete :
- *         {
- *             [self.tableView deleteSections:[NSIndexSet indexSetWithIndex:sectionChange.index]
- *                           withRowAnimation:UITableViewRowAnimationAutomatic];
- *             break;
- *         }
- *         case YapDatabaseViewChangeInsert :
- *         {
- *             [self.tableView insertSections:[NSIndexSet indexSetWithIndex:sectionChange.index]
- *                           withRowAnimation:UITableViewRowAnimationAutomatic];
- *             break;
- *         }
- *     }
- * }
- *
- * for (YapDatabaseViewRowChange *rowChange in rowChanges)
- * {
- *     switch (rowChange.type)
- *     {
- *         case YapDatabaseViewChangeDelete :
- *         {
- *             [self.tableView deleteRowsAtIndexPaths:@[ rowChange.indexPath ]
- *                                   withRowAnimation:UITableViewRowAnimationAutomatic];
- *             break;
- *         }
- *         case YapDatabaseViewChangeInsert :
- *         {
- *             [self.tableView insertRowsAtIndexPaths:@[ rowChange.newIndexPath ]
- *                                   withRowAnimation:UITableViewRowAnimationAutomatic];
- *             break;
- *         }
- *         case YapDatabaseViewChangeMove :
- *         {
- *             [self.tableView deleteRowsAtIndexPaths:@[ rowChange.indexPath ]
- *                                   withRowAnimation:UITableViewRowAnimationAutomatic];
- *             [self.tableView insertRowsAtIndexPaths:@[ rowChange.newIndexPath ]
- *                                   withRowAnimation:UITableViewRowAnimationAutomatic];
- *             break;
- *         }
- *         case YapDatabaseViewChangeUpdate :
- *         {
- *             [self.tableView reloadRowsAtIndexPaths:@[ rowChange.indexPath ]
- *                                   withRowAnimation:UITableViewRowAnimationNone];
- *             break;
- *         }
- *     }
- * }
- *
- * [self.tableView endUpdates];
-**/
-@property (nonatomic, readonly) NSIndexPath *indexPath;
-@property (nonatomic, readonly) NSIndexPath *newIndexPath;
-
-/**
- * The "original" values represent the location of the changed item
- * at the BEGINNING of the read-write transaction(s).
- *
- * The "final" values represent the location of the changed item
- * at the END of the read-write transaction(s).
-**/
-
-@property (nonatomic, readonly) NSUInteger originalIndex;
-@property (nonatomic, readonly) NSUInteger finalIndex;
-
-@property (nonatomic, readonly) NSUInteger originalSection;
-@property (nonatomic, readonly) NSUInteger finalSection;
-
-@property (nonatomic, readonly) NSString *originalGroup;
-@property (nonatomic, readonly) NSString *finalGroup;
-
-@end

data/vendor/Pods/BuildHeaders/YapDatabase/YapDatabaseViewChangePrivate.h

@@ -1,94 +0,0 @@
-#import "YapDatabaseViewChange.h"
-#import "YapDatabaseViewMappings.h"
-
-/**
- * This header file is PRIVATE, and is only to be used by the YapDatabaseView classes.
-**/
-
-@interface YapDatabaseViewSectionChange () {
-@public
-	
-	// This header file is PRIVATE, and is only to be used by YapDatabaseView classes
-	
-	NSString *group; // immutable
-	BOOL isReset;    // immutable
-	
-	YapDatabaseViewChangeType type; // mutable during consolidation
-	
-	NSUInteger originalSection; // mutable during pre-processing
-	NSUInteger finalSection;    // mutable during pre-processing
-}
-
-+ (YapDatabaseViewSectionChange *)insertGroup:(NSString *)group;
-+ (YapDatabaseViewSectionChange *)deleteGroup:(NSString *)group;
-
-+ (YapDatabaseViewSectionChange *)resetGroup:(NSString *)group;
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-@interface YapDatabaseViewRowChange () {
-@public
-	
-	// This header file is PRIVATE, and is only to be used by YapDatabaseView classes
-	
-	id key; // immutable
-	
-	NSString *originalGroup; // immutable
-	NSString *finalGroup;    // mutable during consolidation
-	
-	YapDatabaseViewChangeType type; // mutable during consolidation
-	int changes;                    // mutable during consolidation
-	
-	NSUInteger opOriginalIndex;  // immutable
-	NSUInteger opFinalIndex;     // immutable
-	
-	NSUInteger originalIndex; // mutable during processing
-	NSUInteger finalIndex;    // mutable during processing
-	
-	NSUInteger originalSection; // mutable during pre-processing
-	NSUInteger finalSection;    // mutable during pre-processing
-}
-
-/**
- * During a transaction, there are only 3 row change types that may be recorded.
- *
- * Post-processing figures out everything else, such as if an item was moved,
- * or if multiple operations can be consolidated into one.
-**/
-
-+ (YapDatabaseViewRowChange *)insertKey:(id)key inGroup:(NSString *)group atIndex:(NSUInteger)index;
-+ (YapDatabaseViewRowChange *)deleteKey:(id)key inGroup:(NSString *)group atIndex:(NSUInteger)index;
-
-+ (YapDatabaseViewRowChange *)updateKey:(id)key changes:(int)flags inGroup:(NSString *)group atIndex:(NSUInteger)index;
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-@interface YapDatabaseViewChange : NSObject
-
-/**
- * The brains behind the post-processing logic.
- * Exposed privately to be used by the unit tests.
-**/
-+ (void)processRowChanges:(NSMutableArray *)changes;
-+ (void)consolidateRowChanges:(NSMutableArray *)changes;
-
-/**
- * This method applies the given mappings, and then invokes the post-processing method.
- * 
- * This method is ONLY to be used by YapDatabaseViewConnection.
-**/
-+ (void)getSectionChanges:(NSArray **)sectionChangesPtr
-               rowChanges:(NSArray **)rowChangesPtr
-	 withOriginalMappings:(YapDatabaseViewMappings *)originalMappings
-			finalMappings:(YapDatabaseViewMappings *)finalMappings
-			  fromChanges:(NSArray *)changes;
-
-@end