Programming and stuff

In my current project I had to change flow of "success and error blocks" in API calls, and add "retry block" in order to be able to retry every failed connection. It turned out to be not so trivial task in current architecture, but I've managed to do it with using alert views with blocks (it's not so interesting how at the moment). At first I've used some library that supported blocks, but also changed completely alert view pattern

http://i.imgur.com/3s3eJ.png

We did like it, but client decided it's too different from default, so I needed to changed it. At first I've looked for solutions with default Alert View, but didn't find anything good enough. So I've decided to create my own UIAlertView category that supports block in about 20 lines of code:

#import <UIKit/UIKit.h> typedef void(^UIAlertViewActionBlock)(void); @interface UIAlertView (Blocks) - (void)addBlock:(UIAlertViewActionBlock)block; - (void)addBlock:(UIAlertViewActionBlock)block forButtonIndex:(NSInteger)index; @end

#import "UIAlertView+Blocks.h" #import <objc/runtime.h> @implementation UIAlertView (Blocks) static NSString *handlersDictionaryKey = @"handlersDictionaryKey"; - (void)addBlock:(UIAlertViewActionBlock)block { [self addBlock:block forButtonIndex:self.firstOtherButtonIndex]; } - (void)addBlock:(UIAlertViewActionBlock)block forButtonIndex:(NSInteger)index { NSMutableDictionary *handlersDictionary = objc_getAssociatedObject(self, (__bridge void *)handlersDictionaryKey); if (handlersDictionary == nil) { handlersDictionary = [NSMutableDictionary dictionary]; } handlersDictionary[@(index)] = block; objc_setAssociatedObject(self, (__bridge void *)handlersDictionaryKey, handlersDictionary, OBJC_ASSOCIATION_RETAIN_NONATOMIC); self.delegate = self; } #pragma mark - UIAlertViewDelegate - (void)alertView:(UIAlertView *)alertView clickedButtonAtIndex:(NSInteger)buttonIndex { NSMutableDictionary *handlersDictionary = objc_getAssociatedObject(self, (__bridge void *)handlersDictionaryKey); if (handlersDictionary) { UIAlertViewActionBlock handler = handlersDictionary[@(buttonIndex)]; if (handler) { handler(); } } } @end

After releasing HackBike I was very excited every time iTunesConnect was kind enough to update my download stats. Unfortunately those statistics are rarely updated, and I can't check my total downloads counts, or event week stats (before it's end). But today I've found nice solution. AppFigures - besides that I gave them my iTunesConnect credentials, I hope they will not delete all my apps and developers certificates. Now I can see much more stats, with nice font and colours. 

Get HackBike on the App Store. See screenshots and ratings, and read customer reviews.

I did it! I've finally finished HackBike - iPhone app created on first edition of HackWro (http://hackwro.pl/ - local hackathon). HackBike show you Nextbike stations, allows you to rent and return bikes, track time and cost. It's rather simple app, but it took me almost 10 months to finish. Why is that? Main reason is that I didn't have designer to help me with UI and I didn't want to rush like with TraceCoin (which looks so 2008). For a long time I couldn't find someone willing to work for free (just like I did). Fortunately 2013 design is flat design so even I could became UI designer :) I did it on my own, and I'm quite happy with results (see screenshots below). Another reason is rule that says "last 20% of your development will take you 80% of time" (or something like that). Working on edge cases and fixing functional and UI bugs took me another few weekend to work on. But finally I've made even i18n and submitted app to AppStore. Can't wait to see it online :)

As a "computer guy", do you remember when someone asked you "hey, could you repair my smarthone? It's not working again!". 

from: http://cocoapods.org/

Specify the libraries for your project in an easy to edit text file. Then use CocoaPods to resolve all dependencies, fetch the source, and set up your Xcode workspace.

Yep, it's all true. Finally you can manage you dependencies and use external code like static libraries. 

I like circles. They’re great and regular and trendy so why not to use them in my new design? No reason not to (especially when it comes to trendy side)!. Everyone wants to look fashionable, even my apps. Just look at those two screens and decide yourself.

I’ve decided to redesign and rewrite one of my first apps: TraceCoin.

TraceCoin is mobile and web application created to help you manage your personal expenditures between friends and co-workers. It happened that co-founder and creator of TraceCoin is friend of mine and flatmate, so he asked me to write iPhone app for him. At the time I was iOS beginner so I’ve agreed with no doubts :) Implication of my decision is robust and quite bad code and design graphic from 2008. I have this app in my CV and I even use it occasionally so I’ve decided to rewrite and redesign TraceCoin, hoping that my 1 year iOS experience will make a difference in final product.

I’m going to notify you (hello, is there anybody here?) about my progress, design decision and maybe retrospection from my old code.

Recently I use more static libraries in my iOS projects. At the beginning I had some issues with creating Archive for ad-hoc distribution. My project was building just fine for debug, but when I tried to build them for testing, XCode would throw up some „headers not found” error. Finally I’ve managed to solve this problem and written down step-by-step instruction. Feel free to use it.

For every static library set this setting: Project -> Target -> Build Settings -> Skip Install -> YES

In your main project:

Project -> Info -> Configurations -> Add new configuration (you can copy Release) and name it e.g. „Ad Hoc”.

Project -> Target -> Build Settings (all) -> Code Sigining Identity -> Ad Hoc -> Set your distributor certificate.

Project -> Target -> Build Settings (all) -> Skip Install -> Ad hoc -> NO

(VERY IMPORTANT) Project -> Target -> Build Settings (all) -> Header Search Path -> Ad Hoc -> Add paths to all static libraries (check recursive mark) -> "${SOURCE_ROOT}/static_library" - if you got following folder structure:

/static_library

/static_library_2

/Main_Project

/Main_Project.xcodeproj

Project -> Target -> Build Settings (all) -> Scan All Sources Files for Includes = YES

PS. Most important thing is to set proper headers paths in Header Search Paths.

PS 2. I’m assuming that you have project (xcodeproj) for your static library and you've added it to you main project.

I’m using „Reminder” quite often, when I need to pay a bills, make a call or go to a barber. App itself seems to be easy to use: you just have to tap empty space and type your todo thing, and it works great. 

But what if you want to be notified about some event? Nomen omen, „Reminder” should reminde you to do stuff. It turns out to be not trivial task! This task needs 4 steps to be completed!

1. Tap on your to do item.

2. Tap on „remind me” row.

3. Switch „at day” to on.

4. Tap on row with date below.

5. Success! Now I can chose my date!

It seems to me like it’s way to many steps to set reminder in „Reminder” app! I would say it’s just ridiculous.

But how to fix it? It couldn’t been simpler: in to do item detail (first step) add switch „reminde me” and when you switch it to „on” (second step) you can chose your date.

From 4 steps to 2? Seems like improvment to me. You’re welcome Apple.

It’s not very good idea to show master view in portrait mode in iPad split view application. Main reason is that it’s just not looking good - there’s not enough space for content in detail view and proportions are not preserved. So it’s common behaviour to hide your master view when application is transformed in portrait mode. But what if there’s still need for stuff (e.g. table view with articles) from master view? Well there is solution - show master view in popover menu.

Warning: this is not my solutions - I took it from Stanford Paul Hegarty iOS course lecture 7), and decieded to write this note, because I didn’t find it anywhere on Internet (maybe I didn’t search too long) and other solutions were not even closly elegant like this one.

So we’ve got our SplitViewController, MasterViewController and DetailViewController. 

First thing is to implement UISplitViewControllerDelegate Protocol in our SplitViewController class. Methods that we need to use:

https://gist.github.com/3579898

In methods no. 1 we will show our button and in 2. we will hide it.

First problem: how we’ll communicate our SplitViewController with DetailViewController? We need to add button to toolbar in DetailViewController when method willHideViewController is called. And what is the best way to communicate with two seperate object? Delegates! How we’ll do it?

Step 1. Create protocol with just one property: 

https://gist.github.com/65512c9db5221de70c73

Step 2. Implement it protocol in DetailViewController and synthesize this property.

https://gist.github.com/71050f78d8541d6193f8

Step 3. Add to SplitViewController property with our protocol type which will return our detail view from SplitViewController array of controllers.

https://gist.github.com/baca158084a9468ae1a7

Step 4. Implement SplitViewController protocol methods in way that they'll show and hide our button.

https://gist.github.com/5bc451059422a9250d03

And that should be it. If our iPad application supports different screen orientations AND will hide master view in portrait mode, then our button should work great.