[url=http://unity-vanlines.com][b]Movers[/b][/url]

Okay, so why 6 files? Let me start here:

Divide by 2 for header/implementations. That’s 3, not 6.

There are two tasks: (1) establishing permissions and (2) doing actual work.

Both require using the FB API via the FBRequest message. Any FBRequest call results in a callback to request:didLoad — make two requests in the same class (e.g., get permissions, post a status update) and the same method is called back twice. So now you have to keep state somewhere. I wrote to Joe about this and he suggested I either use an instance variable or a tag and put an “if” into request:didLoad. Blech. So, one class for each task.

I anticipate/anticipated links and photos to the lib myself. Wanted to let people just use a single class to do all their work, and to simplify things by using properties (e.g., fbHelper.status = @”irritated at being called an architecture astronaut”). So you need a that third pair of files. That accounts for all the files.

Now, delegates:

First of all, everything’s optional from the end user perspective. But, if you want to know whether something happened successfully then you need them. Those things that you’re interested in happen in those aforementioned files and get sent back to the main helper class that dutifully just passes them on.