motion-yapper 0.0.3 → 0.1.0

data/vendor/Pods/Headers/YapDatabase/YapDatabaseViewOptions.h

@@ -1,63 +0,0 @@
-#import <Foundation/Foundation.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
-**/
-
-@interface YapDatabaseViewOptions : NSObject <NSCopying>
-
-/**
- * A view can either be persistent (saved to sqlite), or non-persistent (kept in memory only).
- *
- * A persistent view saves its content to sqlite database tables.
- * Thus a persistent view can be restored on subsequent app launches with re-population.
- *
- * A non-persistent view is stored in memory.
- * From the outside, it works exactly like a persistent view in every way.
- * You won't be able to tell the difference unless you look at the sqlite database.
- *
- * It's recommended that you use a persistent view for any views that your app needs on a regular basis.
- * For example, if your app's main screen has a tableView powered by a view, that should likely be persistent.
- *
- * Non-persistent views are recommended for those situations where you need a view only temporarily.
- * Or where the configuration of the view is highly dependent upon parameters that change regularly.
- * In general, situations where it doesn't really make sense to persist the view.
- *
- * The default value is YES.
-**/
-@property (nonatomic, assign, readwrite) BOOL isPersistent;
-
-/**
- * You can configure the view to pre-filter all but a subset of collections.
- * 
- * The primary motivation for this is to reduce the overhead when first populating the view.
- * For example, if you're creating a view which only includes objects from a single collection,
- * then you could specify that collection here. So when the view first populates itself,
- * it will enumerate over just the allowedCollections, as opposed to enumerating over all collections.
- * And enumerating a small subset of the entire database during view population can improve speed,
- * especially with larger databases.
- * 
- * In addition to reducing the overhead when first populating the view,
- * the allowedCollections will pre-filter while you're making changes to the database.
- * So if you add a new object to the database, and the associated collection isn't in allowedCollections,
- * then the groupingBlock will never be invoked, and the view will act as if the groupingBlock returned nil.
- * 
- * For all rows whose collection is in the allowedCollections, the view acts normally.
- * So the groupingBlock would still be invoked as normal.
- *
- * The default value is nil.
-**/
-@property (nonatomic, copy, readwrite) NSSet *allowedCollections;
-
-@end

data/vendor/Pods/Headers/YapDatabase/YapDatabaseViewRangeOptions.h

@@ -1,330 +0,0 @@
-#import <Foundation/Foundation.h>
-
-
-/**
- * Range offsets are specified from either the beginning or end.
- *
- * @see fixedRangeWithLength:offset:from:
- * @see flexibleRangeWithStartingLength:startingOffset:from:
-**/
-typedef enum {
-	YapDatabaseViewBeginning = 0, // index == 0
-	YapDatabaseViewEnd       = 1, // index == last
-	
-} YapDatabaseViewPin;
-
-/**
- * Grow options allow you to specify in which direction flexible ranges can grow.
- *
- * @see growOptions
-**/
-typedef enum {
-	YapDatabaseViewGrowPinSide    = 1 << 0,
-	YapDatabaseViewGrowNonPinSide = 1 << 1,
-	
-	YapDatabaseViewGrowInRangeOnly = 0,
-	YapDatabaseViewGrowOnBothSides = (YapDatabaseViewGrowPinSide | YapDatabaseViewGrowNonPinSide)
-	
-} YapDatabaseViewGrowOptions;
-
-/**
- * Range options allow you to specify a particular range of a group.
- *
- * For example, if a group contains thousands of items,
- * but you only want to display the most recent 50 items in your tableView,
- * then you can easily use range options to accomplish this.
- * 
- * YapDatabaseViewRangeOptions are plugged into YapDatabaseViewMappings.
- *
- * @see YapDatabaseViewMappings setRangeOptions:forGroup:
-**/
-@interface YapDatabaseViewRangeOptions : NSObject <NSCopying>
-
-/**
- * There are 2 types of supported ranges: Fixed & Flexible
- * 
- * A fixed range is similar to using a LIMIT & OFFSET in a SQL query.
- * That is, it represents a designated range that doesn't change.
- * 
- * You create a fixed range by specifying a desired length
- * and an offset from either the beginning or end.
- * 
- * @param length
- *   The desired length of the range.
- *   The length doesn't need to be valid at this point in time.
- *   For example, if the group only has 4 items, you can still specify a length of 20 if that is the desired length.
- *   The mappings will automatically use a length of 4 to start, and automatically expand up to 20.
- * 
- * @param offset
- *   The offset from one either the beginning or end of the group.
- *   
- * @param beginningOrEnd
- *   Either YapDatabaseViewBeginning or YapDatabaseViewEnd.
- * 
- * Using YapDatabaseViewMappings along with a fixed range provides some unique features:
- *
- * - If you specify an offset from the end of the group (YapDatabaseViewEnd),
- *   you are essentially "pinning" the range to the end, and it will stay pinned that way regardless of
- *   inserted or deleted items elsewhere in the group.
- *   
- *   For example: If you pin the range to the end, with an offset of zero, and a length of 20,
- *   then the range will always specify the last 20 items in the group,
- *   even as the group length (as a whole) increases or decreases.
- * 
- * - The changeset processing will automatically create the proper row changes to match what you want.
- *   
- *   For example: You have a fixed range with length 20, pinned to the beginning with an offset of 0,
- *   and a new item is inserted at index 0. The changeset processing will automatically give you a row
- *   insert at index 0, and a row delete at the end of your range to properly account for the row
- *   that got pushed outside your range.
- * 
- *   Thus you get row animations for free, even when only displaying a subset.
- *   And all the math is already done for you.
-**/
-+ (YapDatabaseViewRangeOptions *)fixedRangeWithLength:(NSUInteger)length
-                                               offset:(NSUInteger)offset
-                                                 from:(YapDatabaseViewPin)beginningOrEnd;
-
-/**
- * There are 2 types of supported ranges: Fixed & Flexible
- * 
- * A flexible range is designed to grow and shrink.
- * To explain this concept, consider Apple's SMS Messages app:
- *   
- *   When you go into a conversation (tap on a persons name),
- *   the messages app starts by displaying the most recent 50 messages (with the most recent at bottom).
- *   Although there might be thousands of old messages between you and the other person,
- *   only 50 are in the view to begin with.
- *   As you send and/or receive messages within the view, the length will grow.
- *   And similarly, if you manually delete messages, the length will shrink.
- * 
- * Flexible ranges are designed to handle these types of user interfaces.
- * They're also quite customizeable to handle a number of different situations.
- * 
- * You create a flexible range by specifying an starting length
- * and an offset from either the beginning or end.
- *
- * @param length
- *   The desired starting length of the range.
- *   The length doesn't need to be valid at this point in time.
- *   For example, if the group only has 4 items, you can still specify a length of 20.
- *   The mappings will automatically correct the length as appropriate.
- *
- * @param offset
- *   The offset from one either the beginning or end of the group.
- *
- * @param beginningOrEnd
- *   Either YapDatabaseViewBeginning or YapDatabaseViewEnd.
- * 
- * Using YapDatabaseViewMappings along with a flexible range provides some unique features:
- *
- * - If you specify an offset from the end of the group (YapDatabaseViewEnd),
- *   you are essentially "pinning" the range to the end, and it will stay pinned that way regardless of
- *   inserted or deleted items elsewhere in the group.
- *
- *   For example: If you pin the range to the end, with an offset of zero,
- *   then the range length will grow as items are added to the end.
- *
- * - The changeset processing will automatically create the proper row changes to match what you want.
- *
- *   Thus you get row animations for free, even when only displaying a subset.
- *   And all the math is already done for you.
-**/
-+ (YapDatabaseViewRangeOptions *)flexibleRangeWithLength:(NSUInteger)length
-                                                  offset:(NSUInteger)offset
-                                                    from:(YapDatabaseViewPin)beginningOrEnd;
-
-/**
- * The current length of the range.
- *
- * When rangeOptions get plugged into mappings, the length is automatically updated to reflect the available length.
- * 
- * For a fixed range, the length will always be less than or equal to the original length.
- * For a flexible range, the length will grow and shrink as items get inserted and removed from the original range.
-**/
-@property (nonatomic, assign, readonly) NSUInteger length;
-
-/**
- * The current offset of the range, relative to the pin (beginning or end of the group).
- * 
- * For a fixed range, the offset never changes.
- * For a flexible range, the offset will grow and shrink as items get inserted and removed between the range and pin.
-**/
-@property (nonatomic, assign, readonly) NSUInteger offset;
-
-/**
- * The pin value represents the end from which the offset is calculated.
- * For example, assume a group contains 50 items and:
- * 
- * - length=10, offset=10, pin=YapDatabaseViewBeginning => the range is [10-19](inclusive) (10 back from 0)
- *
- * - length=10, offset=10, pin=YapDatabaseViewEnd => the range is [30-39](inclusive) (10 back from 49)
-**/
-@property (nonatomic, assign, readonly) YapDatabaseViewPin pin;
-
-/**
- * There are 2 types of supported ranges: Fixed & Flexible
-**/
-@property (nonatomic, readonly) BOOL isFixedRange;
-@property (nonatomic, readonly) BOOL isFlexibleRange;
-
-/**
- * For FIXED ranges:
- * - the maxLength is readonly.
- * - it will always equal the length originally specified.
- *
- * For FLEXIBLE ranges:
- * - the maxLength allows you to specify a maximum length in which the range can grow.
- * 
- * In particular, if the range overflows the maxLength, then the changeset processing will automatically
- * trim items from the range (on the non-pin-side) to keep the range length within this maxLength.
- * 
- * For example, imagine you're displaying log entries in a tableView.
- * The range is pinned to the end, so as new log entries get appended to the database, they automatically get
- * inserted into the tableView. This allows the tableView to grow as the log grows. However, you don't want the
- * tableView growing too big, so you can set the maxLength in order to prevent this. That way, your tableView
- * grows as the logs come in (as expected). But if your tableView starts to get too big,
- * then the oldest log entries in the tableView start to fall off as new entries arrive.
- * This is eqivalent to switching from a flexible range to a fixed range,
- * but happens automatically without you having to write extra code to handle the edge case.
- * 
- * By default there is no maxLength, and thus the default maxLength is NSUIntegerMax.
-**/
-@property (nonatomic, readwrite) NSUInteger maxLength;
-
-/**
- * For FIXED ranges:
- * - the minLength is readonly.
- * - it will always equal zero.
- *
- * For FLEXIBLE ranges:
- * - the minLength allows you to specify a minimum length that the range should keep (if possible).
- *
- * In particular, if the range underflows the minLength, then the changeset processing will automatically
- * adjust the offset or expand the range in order to keep entries in the view.
- * 
- * This is sometimes useful if items can get deleted from your range.
- * 
- * By default there is no minLength, and thus the default minLength is zero.
-**/
-@property (nonatomic, readwrite) NSUInteger minLength;
-
-/**
- * GrowOptions ONLY apply to FLEXIBLE ranges.
- * 
- * The growOptions allow you to specify in which direction(s) the range may grow.
- * Let's look at a few concrete examples.
- * 
- * Example #1
- * 
- *   We're using a flexible range, with an offset of zero, pinned to the beginning.
- *   We're displaying news items, and the most recent items get inserted at index 0.
- *   The group currently contains thousands of items, and our range has a starting length of 50.
- *   If a new item gets inserted (at the beginning), we want it to get added to our range.
- *   So we would set our growOptions to be YapDatabaseViewGrowPinSide (this is the default value).
- * 
- * Example #2
- * 
- *   We're using a flexible range, with an offset of zero, pinned to the end.
- *   We're displaying log entries, with the most recent items getting appended to the end.
- *   The group currently contains thousands of items, and our range has a starting length of 50.
- *   If a new log item gets inserted (at the end), we want it to get added to our range.
- *   So we would set our growOptions to be YapDatabaseViewGrowPinSide (this is the default value).
- * 
- * Example #3
- * 
- *   We're making a UI that is somewhat akin to Facebook's news feed.
- *   That is, the most recent items come in at the top,
- *   but if you scroll to the bottom we automatically download older posts.
- *   However, we don't want to limit how far the user can scroll down.
- *   That is, if the user is bored, we're going to allow them to scroll down for
- *   however long we can fetch old items from the server.
- *   But obviously we can't allow the length of our tableView to grow infinitely long.
- *   So to accomplish this, we're going to use flexible ranges,
- *   and we're going to shift the length as the user scrolls down.
- *   To start with, we only have the 30 most recent posts in the database.
- *   And we set our flexible range as: length=30, offset=0, pin=YapDatabaseViewBeginning.
- *   Additionally we set our growOptions to: YapDatabaseViewGrowOnBothSides.
- *   Thus if we download new items, they'll get included in the range.
- *   And if we fetch older items, they'll also get included in the range.
- *   Now as the the user scrolls down, and we fetch more and more old items,
- *   we eventually get to the point were we shift the range.
- *   So when the range length gets to some max length that we want to support, we shift to a new flexible range:
- *   length=max, offset=0, pin=YapDatabaseViewEnd, growOptions=YapDatabaseViewGrowPinSide, maxLength=max
- *   This new range will keep the tableView length capped at max, and continually load older content as it gets fetched.
- *   To allow the user to scroll back up, we just increment the offset as the go.
- *   When they eventually get back up to the top, we reset the flexible range to its original value.
- * 
- *
- * To explain the different options, consider the following picture:
- * 
- *  - - - - -
- * | |x|x|x| |  <-- x marks the range
- *  - - - - -
- *  0 1 2 3 4
- *
- * groupCount = 5
- * flexibleRange: length=3, offset=1, pin=YapDatabaseViewBeginning, growOptions=YapDatabaseViewGrowPinSide
- * 
- * Now an item gets inserted at index 1 as follows:
- * 
- *  - - - - - -
- * | |?|x|x|x| |  <-- is ? added to the flexible range?
- *  - - - - - -
- *  0 1 2 3 4 5
- *
- * Does the item get added to the flexible range (with the given config options)?
- * The answer is YES.
- * 
- *  - - - - - -
- * | |x|x|x|x| |  <-- YES (based on pin & growOptions)
- *  - - - - - -
- *  0 1 2 3 4 5
- *
- * Because the flexible range is pinned to the beginning, and grows pin side.
- * So if anything gets inserted between what was originally at index 0, and what was originally at index 1,
- * then those items get added to the flexible range.
- * 
- * Notice that after the insert, the offset remains set at 1.
- * Notice that the answer would be NO if the flexible range was pinned to the end (with the same growOptions).
- * 
- * Now let's see what happens if something gets inserted at the end:
- * 
- *  - - - - - - -
- * | |x|x|x|x|?| |  <-- is ? added to the flexible range?
- *  - - - - - - -
- *  0 1 2 3 4 5 6
- * 
- * Does the item get added to the flexible range (with the given config options)?
- * The answer is NO.
- * 
- *  - - - - - - -
- * | |x|x|x|x| | |  <-- NO (based on pin & growOptions)
- *  - - - - - - -
- *  0 1 2 3 4 5 6
- * 
- * Because the flexible range is pinned to the beginning, and grows pin side.
- * 
- * Notice that after the insert, the offset remains set at 1.
- * Notice that the answer would be YES if the flexible range was pinned to the end (with the same growOptions).
- * 
- *  - - - - - - - -                 - - - - - - - -
- * |?| |x|x|x|x| | |  => NEVER =>  | | |x|x|x|x| | |
- *  - - - - - - - -                 - - - - - - - -
- *  0 1 2 3 4 5 6 7                 0 1 2 3 4 5 6 7
- * 
- *  - - - - - - - - -                  - - - - - - - - -
- * | | |x|?|x|x|x| | |  => ALWAYS =>  | | |x|x|x|x|x| | |
- *  - - - - - - - - -                  - - - - - - - - -
- *  0 1 2 3 4 5 6 7 8                  0 1 2 3 4 5 6 7 8
-**/
-@property (nonatomic, readwrite) YapDatabaseViewGrowOptions growOptions;
-
-/**
- * Various copy options.
-**/
-- (id)copyWithNewLength:(NSUInteger)newLength;
-- (id)copyWithNewOffset:(NSUInteger)newOffset;
-- (id)copyWithNewLength:(NSUInteger)newLength newOffset:(NSUInteger)newOffset;
-
-@end

data/vendor/Pods/Headers/YapDatabase/YapDatabaseViewTransaction.h

@@ -1,498 +0,0 @@
-#import <Foundation/Foundation.h>
-
-#import "YapDatabaseExtensionTransaction.h"
-#import "YapDatabaseViewTypes.h"
-#import "YapDatabaseViewMappings.h"
-
-/**
- * Welcome to YapDatabase!
- *
- * The project page has a wealth of documentation if you have any questions.
- * https://github.com/yaptv/YapDatabase
- *
- * If you're new to the project you may want to check out the wiki
- * 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 more information, please see the wiki article about Views:
- * https://github.com/yaptv/YapDatabase/wiki/Views
- *
- * You may also wish to consult the documentation in YapDatabaseView.h for information on setting up a view.
- *
- * You access this class within a regular transaction.
- * For example:
- *
- * [databaseConnection readWithBlock:^(YapDatabaseReadTransaction *transaction){
- *
- *     topUsaSale = [[transaction ext:@"myView"] objectAtIndex:0 inGroup:@"usa"]
- * }];
- *
- * Keep in mind that the YapDatabaseViewTransaction object is linked to the YapDatabaseReadTransaction object.
- * So don't try to use it outside the transaction block (cause it won't work).
-**/
-@interface YapDatabaseViewTransaction : YapDatabaseExtensionTransaction
-
-#pragma mark Groups
-
-/**
- * Returns the number of groups the view manages.
- * Each group has one or more keys in it.
-**/
-- (NSUInteger)numberOfGroups;
-
-/**
- * Returns the names of all groups in an unsorted array.
- * Each group has one or more keys in it.
- *
- * @see YapDatabaseView - groupingBlock
-**/
-- (NSArray *)allGroups;
-
-/**
- * Returns YES if there are any keys in the given group.
- * This is equivalent to ([viewTransaction numberOfKeysInGroup:group] > 0)
-**/
-- (BOOL)hasGroup:(NSString *)group;
-
-/**
- * Returns the total number of keys in the given group.
- * If the group doesn't exist, returns zero.
-**/
-- (NSUInteger)numberOfKeysInGroup:(NSString *)group;
-
-/**
- * Returns the total number of keys in every single group.
-**/
-- (NSUInteger)numberOfKeysInAllGroups;
-
-#pragma mark Fetching
-
-/**
- * Returns the key & collection at the given index within the given group.
- * Returns nil if the group doesn't exist, or if the index is out of bounds.
-**/
-- (BOOL)getKey:(NSString **)keyPtr
-    collection:(NSString **)collectionPtr
-       atIndex:(NSUInteger)index
-       inGroup:(NSString *)group;
-
-/**
- * Shortcut for: [view getKey:&key collection:&collection atIndex:0 inGroup:group]
-**/
-- (BOOL)getFirstKey:(NSString **)keyPtr collection:(NSString **)collectionPtr inGroup:(NSString *)group;
-
-/**
- * Shortcut for: [view getKey:&key collection:&collection atIndex:(numberOfKeysInGroup-1) inGroup:group]
-**/
-- (BOOL)getLastKey:(NSString **)keyPtr collection:(NSString **)collectionPtr inGroup:(NSString *)group;
-
-/**
- * Shortcut for fetching just the collection at the given index.
-**/
-- (NSString *)collectionAtIndex:(NSUInteger)index inGroup:(NSString *)group;
-
-/**
- * Shortcut for fetching just the key at the given index.
- * Convenient if you already know what collection the key is in.
-**/
-- (NSString *)keyAtIndex:(NSUInteger)index inGroup:(NSString *)group;
-
-/**
- * If the given {collection, key} are included in the view, then returns the associated group.
- * If the {collection, key} isn't in the view, then returns nil.
-**/
-- (NSString *)groupForKey:(NSString *)key inCollection:(NSString *)collection;
-
-/**
- * Fetches both the group and the index within the group for the given {collection, key}.
- *
- * Returns YES if the {collection, key} is included in the view.
- * Otherwise returns NO, and sets the parameters to nil & zero.
-**/
-- (BOOL)getGroup:(NSString **)groupPtr
-           index:(NSUInteger *)indexPtr
-          forKey:(NSString *)key
-    inCollection:(NSString *)collection;
-
-#pragma mark Finding
-
-typedef id YapDatabaseViewFindBlock; // One of the YapDatabaseViewFindX types below.
-
-typedef NSComparisonResult (^YapDatabaseViewFindWithKeyBlock)      \
-                                                        (NSString *collection, NSString *key);
-typedef NSComparisonResult (^YapDatabaseViewFindWithObjectBlock)   \
-                                                        (NSString *collection, NSString *key, id object);
-typedef NSComparisonResult (^YapDatabaseViewFindWithMetadataBlock) \
-                                                        (NSString *collection, NSString *key, id metadata);
-typedef NSComparisonResult (^YapDatabaseViewFindWithRowBlock)      \
-                                                        (NSString *collection, NSString *key, id object, id metadata);
-
-/**
- * This method uses a binary search algorithm to find a range of items within the view that match the given criteria.
- * For example:
- * 
- * You have a view which sorts items by timestamp (oldest to newest)
- * You could then use this method to quickly find all items whose timestamp falls on a certain day.
- * Or, more generally, within a certain timespan.
- * 
- * NSDate *beginningOfMonday = ...   // Monday at 12:00 AM
- * NSDate *beginningOfTuesday =  ... // Tuesday at 12:00 AM
- *
- * YapDatabaseViewBlockType blockType = YapDatabaseViewBlockTypeWithObject;
- * YapDatabaseViewFindWithObjectBlock block = ^(NSString *key, id object){
- *
- *     Purchase *purchase = (Purchase *)object;
- *
- *     if ([purchase.timestamp compare:beginningOfMonday] == NSOrderedAscending) // earlier than start range
- *         return NSOrderedAscending;
- * 
- *     if ([purchase.timestamp compare:beginningOfTuesday] == NSOrderedAscending) // earlier than end range
- *         return NSOrderedSame;
- * 
- *     return NSOrderedDescending; // greater than end range (or exactly midnight on tuesday)
- * };
- * 
- * The return values from the YapDatabaseViewFindBlock have the following meaning:
- * 
- * - NSOrderedAscending : The given row (block parameters) is less than the range I'm looking for.
- *                        That is, the row would have a smaller index within the view than would the range I seek.
- * 
- * - NSOrderedDecending : The given row (block parameters) is greater than the range I'm looking for.
- *                        That is, the row would have a greater index within the view than would the range I seek.
- * 
- * - NSOrderedSame : The given row (block parameters) is within the range I'm looking for.
- * 
- * Keep in mind 2 things:
- * 
- * #1 : This method can only be used if you need to find items according to their sort order.
- *      That is, according to how the items are sorted via the view's sortingBlock.
- *      Attempting to use this method in any other manner makes no sense.
- *
- * #2 : The findBlock that you pass needs to be setup in the same manner as the view's sortingBlock.
- *      That is, the following rules must be followed, or the results will be incorrect:
- *      
- *      For example, say you have a view like this, looking for the following range of 3 items:
- *      myView = @[ A, B, C, D, E, F, G ]
- *                     ^^^^^^^
- *      sortingBlock(A, B) => NSOrderedAscending
- *      findBlock(A)       => NSOrderedAscending
- *      
- *      sortingBlock(E, D) => NSOrderedDescending
- *      findBlock(E)       => NSOrderedDescending
- * 
- *      findBlock(B) => NSOrderedSame
- *      findBlock(C) => NSOrderedSame
- *      findBlock(D) => NSOrderedSame
- * 
- * In other words, you can't sort one way in the sortingBlock, and "sort" another way in the findBlock.
- * Another way to think about it is in terms of how the Apple docs define the NSOrdered enums:
- * 
- * NSOrderedAscending  : The left operand is smaller than the right operand.
- * NSOrderedDescending : The left operand is greater than the right operand.
- * 
- * For the findBlock, the "left operand" is the row that is passed,
- * and the "right operand" is the desired range.
- * 
- * And NSOrderedSame means: "the passed row is within the range I'm looking for".
- * 
- * Implementation Note:
- * This method uses a binary search to find an item for which the block returns NSOrderedSame.
- * It then uses information from the first binary search (known min/max) to perform two subsequent binary searches.
- * One to find the start of the range, and another to find the end of the range.
- * Thus:
- * - the implementation is efficient
- * - the block won't be invoked for every item within the range
- *
- * @param group
- *     The group within the view to search.
- * 
- * @param block
- *     One of the YapDatabaseViewFindWithXBlock types.
- * 
- * @param blockType
- *     The proper YapDatabaseViewBlockTypeWithX type that matches the given block.
- * 
- * @return
- *     If found, the range that matches the items within the desired range.
- *     That is, is these items were passed to the given block, the block would return NSOrderedSame.
- *     If not found, returns NSMakeRange(NSNotFound, 0).
-**/
-- (NSRange)findRangeInGroup:(NSString *)group
-                 usingBlock:(YapDatabaseViewFindBlock)block
-                  blockType:(YapDatabaseViewBlockType)blockType;
-
-#pragma mark Enumerating
-
-/**
- * Enumerates the keys in the given group.
-**/
-- (void)enumerateKeysInGroup:(NSString *)group
-                  usingBlock:(void (^)(NSString *collection, NSString *key, NSUInteger index, BOOL *stop))block;
-
-/**
- * Enumerates the keys in the given group.
- * Reverse enumeration is supported by passing NSEnumerationReverse. (No other enumeration options are supported.)
-**/
-- (void)enumerateKeysInGroup:(NSString *)group
-                 withOptions:(NSEnumerationOptions)options
-                  usingBlock:(void (^)(NSString *collection, NSString *key, NSUInteger index, BOOL *stop))block;
-
-/**
- * Enumerates the keys in the range of the given group.
- * Reverse enumeration is supported by passing NSEnumerationReverse. (No other enumeration options are supported.)
-**/
-- (void)enumerateKeysInGroup:(NSString *)group
-                 withOptions:(NSEnumerationOptions)options
-                       range:(NSRange)range
-                  usingBlock:(void (^)(NSString *collection, NSString *key, NSUInteger index, BOOL *stop))block;
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-@interface YapDatabaseViewTransaction (ReadWrite)
-
-/**
- * "Touching" a object allows you to mark an item in the view as "updated",
- * even if the object itself wasn't directly updated.
- *
- * This is most often useful when a view is being used by a tableView,
- * but the tableView cells are also dependent upon another object in the database.
- *
- * For example:
- *
- *   You have a view which includes the departments in the company, sorted by name.
- *   But as part of the cell that's displayed for the department,
- *   you also display the number of employees in the department.
- *   The employee count comes from elsewhere.
- *   That is, the employee count isn't a property of the department object itself.
- *   Perhaps you get the count from another view,
- *   or perhaps the count is simply the number of keys in a particular collection.
- *   Either way, when you add or remove an employee, you want to ensure that the view marks the
- *   affected department as updated so that the corresponding cell will properly redraw itself.
- *
- * So the idea is to mark certain items as "updated" (in terms of this view) so that
- * the changeset for the view will properly reflect a change to the corresponding index.
- * But you don't actually need to update the item on disk.
- * This is exactly what "touch" does.
- *
- * Touching an item has very minimal overhead.
- * It doesn't cause the groupingBlock or sortingBlock to be invoked,
- * and it doesn't cause any writes to the database.
- *
- * You can touch
- * - just the object
- * - just the metadata
- * - or both object and metadata (the row)
- * 
- * If you mark just the object as changed,
- * and neither the groupingBlock nor sortingBlock depend upon the object,
- * then the view doesn't reflect any change.
- * 
- * If you mark just the metadata as changed,
- * and neither the groupingBlock nor sortingBlock depend upon the metadata,
- * then the view doesn't relect any change.
- * 
- * In all other cases, the view will properly reflect a corresponding change in the notification that's posted.
-**/
-
-- (void)touchRowForKey:(NSString *)key inCollection:(NSString *)collection;
-- (void)touchObjectForKey:(NSString *)key inCollection:(NSString *)collection;
-- (void)touchMetadataForKey:(NSString *)key inCollection:(NSString *)collection;
-
-/**
- * This method allows you to change the groupingBlock and/or sortingBlock on-the-fly.
- * 
- * Note: You must pass a different versionTag, or this method does nothing.
-**/
-- (void)setGroupingBlock:(YapDatabaseViewGroupingBlock)groupingBlock
-       groupingBlockType:(YapDatabaseViewBlockType)groupingBlockType
-            sortingBlock:(YapDatabaseViewSortingBlock)sortingBlock
-        sortingBlockType:(YapDatabaseViewBlockType)sortingBlockType
-              versionTag:(NSString *)versionTag;
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-/**
- * YapDatabaseView deals with ordered arrays of collection/key tuples.
- * So, strictly speaking, it only knows about collection/key tuples, groups, and indexes.
- * 
- * But it's really convenient to have methods that put it all together to fetch an object in a single method.
-**/
-@interface YapDatabaseViewTransaction (Convenience)
-
-/**
- * Equivalent to invoking:
- *
- * NSString *collection, *key;
- * if ([[transaction ext:@"myView"] getKey:&key collection:&collection atIndex:index inGroup:group]) {
- *     object = [transaction objectForKey:key inCollection:collection];
- * }
-**/
-- (id)objectAtIndex:(NSUInteger)keyIndex inGroup:(NSString *)group;
-
-/**
- * Equivalent to invoking:
- *
- * NSString *collection, *key;
- * if ([[transaction ext:@"myView"] getFirstKey:&key collection:&collection inGroup:group]) {
- *     object = [transaction objectForKey:key inCollection:collection];
- * }
-**/
-- (id)firstObjectInGroup:(NSString *)group;
-
-/**
- * Equivalent to invoking:
- *
- * NSString *collection, *key;
- * if ([[transaction ext:@"myView"] getLastKey:&key collection:&collection inGroup:group]) {
- *     object = [transaction objectForKey:key inCollection:collection];
- * }
-**/
-- (id)lastObjectInGroup:(NSString *)group;
-
-/**
- * The following methods are equivalent to invoking the enumerateKeysInGroup:... methods,
- * and then fetching the metadata within your own block.
-**/
-
-- (void)enumerateKeysAndMetadataInGroup:(NSString *)group
-                             usingBlock:
-                    (void (^)(NSString *collection, NSString *key, id metadata, NSUInteger index, BOOL *stop))block;
-
-- (void)enumerateKeysAndMetadataInGroup:(NSString *)group
-                            withOptions:(NSEnumerationOptions)options
-                             usingBlock:
-                    (void (^)(NSString *collection, NSString *key, id metadata, NSUInteger index, BOOL *stop))block;
-
-- (void)enumerateKeysAndMetadataInGroup:(NSString *)group
-                            withOptions:(NSEnumerationOptions)options
-                                  range:(NSRange)range
-                             usingBlock:
-                    (void (^)(NSString *collection, NSString *key, id metadata, NSUInteger index, BOOL *stop))block;
-
-/**
- * The following methods are equivalent to invoking the enumerateKeysInGroup:... methods,
- * and then fetching the object within your own block.
-**/
-
-- (void)enumerateKeysAndObjectsInGroup:(NSString *)group
-                            usingBlock:
-            (void (^)(NSString *collection, NSString *key, id object, NSUInteger index, BOOL *stop))block;
-
-- (void)enumerateKeysAndObjectsInGroup:(NSString *)group
-                           withOptions:(NSEnumerationOptions)options
-                            usingBlock:
-            (void (^)(NSString *collection, NSString *key, id object, NSUInteger index, BOOL *stop))block;
-
-- (void)enumerateKeysAndObjectsInGroup:(NSString *)group
-                           withOptions:(NSEnumerationOptions)options
-                                 range:(NSRange)range
-                            usingBlock:
-            (void (^)(NSString *collection, NSString *key, id object, NSUInteger index, BOOL *stop))block;
-
-/**
- * The following methods are equivalent to invoking the enumerateKeysInGroup:... methods,
- * and then fetching the object and metadata within your own block.
-**/
-
-- (void)enumerateRowsInGroup:(NSString *)group
-                  usingBlock:
-            (void (^)(NSString *collection, NSString *key, id object, id metadata, NSUInteger index, BOOL *stop))block;
-
-- (void)enumerateRowsInGroup:(NSString *)group
-                 withOptions:(NSEnumerationOptions)options
-                  usingBlock:
-            (void (^)(NSString *collection, NSString *key, id object, id metadata, NSUInteger index, BOOL *stop))block;
-
-- (void)enumerateRowsInGroup:(NSString *)group
-                 withOptions:(NSEnumerationOptions)options
-                       range:(NSRange)range
-                  usingBlock:
-            (void (^)(NSString *collection, NSString *key, id object, id metadata, NSUInteger index, BOOL *stop))block;
-
-@end
-
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-#pragma mark -
-////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-
-@interface YapDatabaseViewTransaction (Mappings)
-
-/**
- * Gets the key & collection at the given indexPath, assuming the given mappings are being used.
- * Returns NO if the indexPath is invalid, or the mappings aren't initialized.
- * Otherwise returns YES, and sets the key & collection ptr (both optional).
-**/
-- (BOOL)getKey:(NSString **)keyPtr
-    collection:(NSString **)collectionPtr
-   atIndexPath:(NSIndexPath *)indexPath
-  withMappings:(YapDatabaseViewMappings *)mappings;
-
-/**
- * Gets the key & collection at the given row & section, assuming the given mappings are being used.
- * Returns NO if the row or section is invalid, or the mappings aren't initialized.
- * Otherwise returns YES, and sets the key & collection ptr (both optional).
-**/
-- (BOOL)getKey:(NSString **)keyPtr
-    collection:(NSString **)collectionPtr
-        forRow:(NSUInteger)row
-     inSection:(NSUInteger)section
-  withMappings:(YapDatabaseViewMappings *)mappings;
-
-/**
- * Gets the object at the given indexPath, assuming the given mappings are being used.
- * 
- * Equivalent to invoking:
- *
- * NSString *collection, *key;
- * if ([[transaction ext:@"myView"] getKey:&key collection:&collection atIndexPath:indexPath withMappings:mappings]) {
- *     object = [transaction objectForKey:key inCollection:collection];
- * }
-**/
-- (id)objectAtIndexPath:(NSIndexPath *)indexPath withMappings:(YapDatabaseViewMappings *)mappings;
-
-/**
- * Gets the object at the given indexPath, assuming the given mappings are being used.
- *
- * Equivalent to invoking:
- *
- * NSString *collection, *key;
- * if ([[transaction ext:@"view"] getKey:&key
- *                            collection:&collection
- *                                forRow:row
- *                             inSection:section
- *                          withMappings:mappings]) {
- *     object = [transaction objectForKey:key inCollection:collection];
- * }
-**/
-- (id)objectAtRow:(NSUInteger)row inSection:(NSUInteger)section withMappings:(YapDatabaseViewMappings *)mappings;
-
-/**
- * Fetches the indexPath for the given {collection, key} tuple, assuming the given mappings are being used.
- * Returns nil if the {collection, key} tuple isn't included in the view + mappings.
-**/
-- (NSIndexPath *)indexPathForKey:(NSString *)key
-                    inCollection:(NSString *)collection
-                    withMappings:(YapDatabaseViewMappings *)mappings;
-
-/**
- * Fetches the row & section for the given {collection, key} tuple, assuming the given mappings are being used.
- * Returns NO if the {collection, key} tuple isn't included in the view + mappings.
- * Otherwise returns YES, and sets the row & section (both optional).
-**/
-- (BOOL)getRow:(NSUInteger *)rowPtr
-       section:(NSUInteger *)sectionPtr
-        forKey:(NSString *)key
-  inCollection:(NSString *)collection
-  withMappings:(YapDatabaseViewMappings *)mappings;
-
-@end