alexdrone / buffer Goto Github PK

There is an absolute reference to the Buffer.framework containing alexusbergo.

Perhaps change it to "relative to project" or to "relative to build products"

HI, I'm looking into Redux flow for iOS recently, it does help me to normalize some questions,
but I'm confusing with dealing big collection property in state, or multi properties in state

for properties modified, I can detect and handle in didSet block, but I have no clue what's the best way to handle a big collection inserted/deleted/modified when new state is called, I want to do accuracy operation instead just call reloadData, especially I'm using AsyncDisplayKit, reload whole collectionView/tableView will cause some UI flash issue.

Depends on a growing social app, properties might scale,
Is Buffer the solution what I seeking ?
How is the performance between Buffer with other diff frameworks ? ex: Dwifft

Also Do you think ReSwift + Buffer + AsyncDisplayKit make sense ?
I'm kind tired of MVC, lol

Environment: Xcode 10, Swift 4.2
After deleting the info.plist from [build phase] -> [Copy Bundle Resources] , the problem is resolved.
Below is the build error:
Multiple commands produce '/Users/crewbuild/myagent/_work/6/output/iphoneos/Test-Release/build.sym/Test-Release-iphoneos/Buffer/Buffer.framework/Info.plist':
2018-10-17T18:19:48.9660210Z 1) Target 'Buffer' (project 'Pods') has copy command from '/Users/crewbuild/myagent/_work/6/s/Pods/Buffer/src/Info.plist' to '/Users/crewbuild/myagent/_work/6/output/iphoneos/Test-Release/build.sym/Test-Release-iphoneos/Buffer/Buffer.framework/Info.plist'
2018-10-17T18:19:48.9689440Z 2) Target 'Buffer' (project 'Pods') has process command with output '/Users/crewbuild/myagent/_work/6/output/iphoneos/Test-Release/build.sym/Test-Release-iphoneos/Buffer/Buffer.framework/Info.plist'

Installing via Carthage fails when building because the framework does not have any shared Xcode scheme.

There are quite a few checks like NSThread.isMainThread() in the code. Maybe this should be changed to checking for the main queue instead?

Here's sample code to check for the queue instead, based on http://blog.benjamin-encz.de/post/main-queue-vs-main-thread/, where the difference is explained, too:

private let mainQueueKey = UnsafeMutablePointer<Void>.alloc(1)
private let mainQueueValue = UnsafeMutablePointer<Void>.alloc(1)

// Associate a key-value pair with the main queue
dispatch_queue_set_specific(
    dispatch_get_main_queue(), 
    mainQueueKey, 
    mainQueueValue, 
    nil
)

func dispatch_ensure_main_queue(block: dispatch_block_t) {

    // Check for presence of key-value pair on current queue
    if (dispatch_get_specific(mainQueueKey) == mainQueueValue) {
        // if we found right value for key, execute immediately
        print("main queue")
        block()
    } else {
        // otherwise dispatch on main queue now
        // /!\ Use dispatch_sync cautiously
        // it can cause deadlocks!
        dispatch_sync(dispatch_get_main_queue()) {
            print("not main queue")
            block()
        }
    }

    return image
}

Do you have any thoughts / plans around section support in tables and collections?