Permalink
Switch branches/tags
Nothing to show
Commits on Mar 7, 2012
  1. Merge pull request #5 from mmower/master

    Fix function prototype warnings and unguarded iOS functions
    committed Mar 7, 2012
Commits on Oct 24, 2010
  1. add 'invalidateUnlocked' method to allow easy overriding

    implementation of 'invalidateUnlocked' method for IKAutoArchivingMemoryAwareFuture removes archive from the disk now
    Kentzo committed Oct 24, 2010
Commits on Oct 23, 2010
  1. fix invalidate method

    Kentzo committed Oct 23, 2010
Commits on Oct 22, 2010
Commits on Oct 21, 2010
  1. fix preprocessor flags

    fix deadlock in processMemoryWarning method
    Kentzo committed Oct 21, 2010
Commits on Sep 4, 2010
  1. use "(TARGET_IPHONE_SIMULATOR && __IPHONE_OS_VERSION_MIN_REQUIRED >= …

    …__IPHONE_3_2) || __IPHONE_OS_VERSION_MIN_REQUIRED > __IPHONE_3_2" because "__IPHONE_OS_VERSION_MIN_REQUIRED has "__IPHONE_3_2" value for simulator even if deplyenment SDK is set to iPhone OS 4.0.
    
    fix: send +class to _IKAutoArchivingMemoryAwareFuture
    Kentzo committed Sep 4, 2010
  2. instead of setting isObserving directly, use countOfUsers property to…

    … determine if future should observe memory warning notifications
    Kentzo committed Sep 4, 2010
Commits on Aug 29, 2010
  1. new marks to separate iOS futures

    use [self futureHasResolved] to check future status instead of check _resolved variable directly
    override futureValue function to return retained and autorelease object. That is neccessary because _value can be invalidated at any time.
    pass [NSThread currentThread] to the processMemoryWarning block to unlock _lock in appropriate thread.
    check future class in +initialize method. Thanks to the Mike's Friday Q&A 2010-08-27
    rename encode -> archive
    rename decode -> unarchive
    remove encodeValue and decodeValue
    add more comments for _IKMemoryAwareFuture and _IKAutoArchivingMemoryAwareFuture
    Kentzo committed Aug 29, 2010
Commits on Aug 25, 2010
  1. IKAutoArchivingMemoryAwareFuture provides automatic support for archi…

    …ving/unarchiving objects that conforms to NSCoding protocol when UIApplicationDidReceiveMemoryWarningNotification is received
    
    fix deplyment target guards
    use CFMutableDictionary instead of NSMapTable for iOS
    Kentzo committed Aug 23, 2010
  2. fix: change resolved

    Kentzo committed Aug 25, 2010
  3. minor fixes

    Kentzo committed Aug 25, 2010
  4. fix guards

    Kentzo committed Aug 25, 2010
Commits on Aug 24, 2010
  1. fix logs prefix

    Kentzo committed Aug 24, 2010
  2. fix merge conflicts

    Kentzo committed Aug 24, 2010
  3. fix: use wrong deployment target guards

    use CFMutableDictionary instead of NSMapTable for iOS
    Kentzo committed Aug 24, 2010
Commits on Aug 23, 2010
  1. IKAutoArchivingMemoryAwareFuture provides automatic support for archi…

    …ving/unarchiving objects that conforms to NSCoding protocol when UIApplicationDidReceiveMemoryWarningNotification is received
    Kentzo committed Aug 23, 2010
  2. fix: if IKMemoryAwareFutureStopObserving is called before future is a…

    …ctually resolved, future ignores this call and starts obeserving
    Kentzo committed Aug 23, 2010
Commits on Aug 21, 2010
  1. use selector-based notification observing instead of block-based

    add methods to start/stop observing low-memory warnings
    Kentzo committed Aug 21, 2010
Commits on Aug 19, 2010
  1. IKMemoryAwareFuture is a future for iPhone projects. It responds to t…

    …he memory warnings and releases it's object from the memory. IKMemoryAwareFuture keeps block even after object is allocated.
    Kentzo committed with Aug 19, 2010