Sin título

[acaserop]

Introducing ACPLogin

I just released ACPLogin, this module provide you an easy user management on top of Deployd.

https://github.com/antoniocasero/ACPLogin

For those who don't know what is Deployd, is an open source BaaS (backend as a service), so if you are looking for affordable backend you should try it.

[acaserop]

Strong vs Copy

Most of the people, when they started with objective c, were setting every property as “strong" or “weak". But those are not the only types for properties. By definition, “strong" type retains a reference of the object, and it will keep it until is set to nil. We are not copying the object, we are using the same object reference in different places, and “that" could give you a headache.

In general, we should use “copy" for any instance of a class that has a mutable subclass (NSArray, NSString..), Why? because is safer to copy the object, do whatever you want to do with it, rather than use the same reference with maybe other owners.

Lets see this with one example,

Our main array, it's gonna contain information that we want to keep in our class

@property (nonatomic, strong) NSMutableArray *myPreciousArray;

….

_myPreciousArray = [@[@"A", @"B", @"C"] mutableCopy ];

(So, now we have set up another array)

NSMutableArray * dirtyArray = [NSMutableArray new];

dirtyArray = _myPreciousArray;

….

Then, and this is the important part, if we change the dirtyArray:

dirtyArray[0] = @"U";

We are changing the value in both arrays, 

NSLog(@"%@", _myPreciousArray);

( U, B, C) <————— :( !!

  Try now with (nonatomic, copy) ...

[acaserop]

Introducing ACPButton v1.0.0

I wrote this extension of UIButton to make easy to change and customise the buttons of your project.

To install this Project, you can clone the project from github

git clone [email protected]:antoniocasero/ACPButton.git

Or you can add the pod to your project

pod ACPButton

Enjoy it!

[acaserop]

Singleton pattern, the dilemma

A singleton class is an easy way to resolve the communication between viewcontrollers, but it is good? The answer is depend... The purpose of a Singleton is to contain a resource that can only have a single instance.  

As you know singleton class will be create at the beginning of your app life cycle and will be stored in memory ALL THE TIME, it is no possible to destroy it. So in memory management terms (yes, using even ARC), maybe is not a good solution. And if you want to have a set of unit test in your project, definitely is not recommended to use it. (See this article)

So, a new concept is the  "weak singleton", allows you to have one instance, but you can destroy the object if you set it to nil.

+ (id)sharedInstance

{

    static __weak ASingletonClass *instance;

    ASingletonClass *strongInstance = instance;

    @synchronized(self) {

        if (strongInstance == nil) {

            strongInstance = [[[self class] alloc] init];

            instance = strongInstance;

        }

    }

    return strongInstance;

}

To keep this alive, you just need to keep one strong reference to this object, 

_singletonInstance = [ASingletonClass sharedInstance];

And if you want to destroy it,

_singletonInstance = nil;

This allow you to have control over your singleton class. I hope this help you :)

[acaserop]

Berlin 2013

For my part, I travel not to go anywhere, but to go. I travel for travel’s sake. The great affair is to move.

[acaserop]

Berlin

For my part, I travel not to go anywhere, but to go. I travel for travel’s sake. The great affair is to move.