Hurray! A video tutorial! And a short one! How luck you are :p

How to make a texture tilable? Well, check the video out! Tile Next Time! Later!

After I graduated in June, I have been laying low for a while, working on various projects. Recently, I started leaving my chambers more often for various reasons, including applying for a job (Finally!), attending events (BarcampKW), and meeting with clients. So? you may ask. Well, it seems most people I meet end up trying to know me through my blog. So, I have to fix my blog!

I have been thinking for a very long time on how I am suppose to provide this proper facade through my blog. So, I spent around 30 seconds thinking! (Usually, my blog posts are spontaneous, but not this one!).

Who Am I?

No, this is not a movie review, I am gonna give a brief intro about me.

Published Projects

Upcoming Projects

ss

Mukashi, Mukashi .. There lived two young kids, a boy (names KVC) and his sister (named KVO). You see, they were born twins, and the laws of mortality did not apply to them. (Plain and simple, they never aged for some reason). They lived happily in the forest, where they survived by utilizing their two main skills:

• KVC would use his awesome trap setting techniques to place traps near rabbit holes, then go rest.
• KVO would then use her keen eyes to observe the traps for any changes, and promptly alert her brother if anything happened.
• KVC would finally get the trap containing their loot, and they would enjoy a delicious meal at the end of the day.

Countless years passed, while KVC & KVO enjoyed their peaceful lives in the forest. Until one day, they had an unexpected visitor. They were baffled by his white tuxedo, his silver pocket watch and his shiny shoes. “My name is Mr. Appolous, but you could just call me Apple”, said the stranger with a gleeful smirk. The kids just stood there gazing upon Apple.

“Say”, Apple broke the silence, “Would you two like to help me by being part of a very successful programming language?” — BZZT. Wait, say what?!

Ok, enough with the silly introduction, and onto the blog post :p. I just hope this silly story somehow sticks to your mind and helps you comprehend to some extent what KVC and KVO are, until we dwell into their guts in a bit.

Before writing the blog post about KVC & KVO … Man, has it been a while!! >.< This Islamicaster project of mine has been ever so stressful with a never ending TODO list. The good news is, it’s still full of new things to learn! And thanks to that, I have completely mastered KVC & KVO! (jk, I am no where near a master of them, but I do have enough knowledge to give an overview on their awesomeness )

“KVC & KVO: Replacing Pillars with Magic” is the title, but what does it really mean? Well, keep that question in one corner of your mind till we explore what KVC & KVO are, then we shall answer this question.

First off, KVC & KVO are not always used together. Each has its own divine purpose, and can be used separately. The awesomeness comes from combining them. However, for the sake of this blog post, we shall tackle them one at a time.

KVC: Key-Value Coding

As you might have deduced from the boring tale above, KVC does two main things:

1. Sets traps values.
2. Gets values.

… OK, so what’s so cool about that? Well, the way we set and get the values is what’s cool. To put it clear and simple, “KVC allows us to get and set the variables of an object as though it was a dictionary” (That’s not 100% accurate, but leave it like this for now). Consider the following example:

@interface Foo : NSObject {
    id var1;
    id var2;
    ...
    id varN;
}

Now, with this class having all theses iVars, it would be a pain to do something like:

Foo* foo = [[Foo alloc] init];
foo.var1 = ...;
foo.var2 = ...;
...

What’s the alternative? KVC! Here is how it works:

for (int i = 1 ; i<=N ; i++) {
    NSString* varName = [NSString stringWithFormat:@"var%d", i];
    [foo setValue:[NSNumber numberWithInt:22] forKey:varName];
}

// And inorder to read the vars in a similar fashion:
int var1 = [[foo valueForKey:@"var1"] intValue];

Notice two things:

1. The instance variable we are setting is of type `int`, while we are sending and `NSNumber` object.
2. What the heck happens if the setters and getters are overriden?!
3. The value we are settings might not be so conveniently easy to determine.

Regarding the first note, it’s fine. KVC is smart enough to send the NSNumber as an int to the instance variable. The second case is similarly handled by KVC, in the sense that it will call your custom setters & getters, no worries.  However, the third case is tough. It is true that most of the time you probably don’t have such a convenient value to set.We will see about that after exploring KVO.

KVO: Key-Value Observing

Remember what was KVO’s job? Observe. Thus, it is quite simply useful to observe any changes on the instance variable that we have. This is a useful alternative for delegates in simple cases, where defining a protocol and setting up a delegate is just an overkill. Imagine a game with a gun. No, not a game holding a gun, but rather a game that contains a gun that the player can fire. Now, imagine that this gun cannot fire two simultaneous shots. Now, here are some approaches that are available:

// Polling approach. Yuck!

// Inside the gun class:
- (void)fireBullet {
    // check if bullet exited the screen
    if (bullet.ready || bullet.position.x > 400) {
        [self reloadBullet:bullet];
        [bullet fireWithAngle:zelta];
        [bullet setReady:NO];
    }
}

Some of us might started thinking, what’s wrong with that? Nice, simple and it works! Well, not exactly. What if the player fires a shot and stops? The bullet would eventually go off screen and continue moving with no reason at all!! Even more, what if we wanted to show the user whether he has a bullet reloaded? It won’t be possible without a delegate:

// Polling approach, with delegate. Gross!

// Inside bullet class:

// this method updates the bullet position each frame
// thus we see an animation of the bullet moving:
- (void)update {
    self.position.x += 1;
    if (self.position.x > 400) {
        [delegate bulletDidExitScreen:self];
    }
}

// Inside the gun class:

// handle delegate method:
- (void)bulletDidExitScreen:(Bullet *)bullet {
    [self showBulletAvailable];
    [bullet setReady:YES];
}

- (void)fireBullet {
    // No longer need to check if bullet exited the screen
    if (bullet.read) {
        [self reloadBullet:bullet];
        [bullet fireWithAngle:zelta];
        [self showBulletUnavailable];
    }
}

OK, with that crap out of the way, let’s see how KVO does it:

- (void)fireBullet {
    // check if bullet exited the screen
    if (bullet.ready) {
        [self reloadBullet:bullet];
        [bullet fireWithAngle:zelta];
        [self showBulletUnavailable];

        [bullet addObserver:self
                 forKeyPath:@"position.x"
                    options:NSKeyValueObservingOptionNew
                    context:NULL];
    }
}

- (void)observeValueForKeyPath:(NSString *)keyPath
                      ofObject:(id)object
                        change:(NSDictionary *)change
                       context:(void *)context {
    float newX = [[change objectForKey:NSKeyValueChangeNewKey] floatValue];
    // do stuff...
}

Just awesome I won’t say more.

With Our Powers Combined!

Now, let me show you how I recently used these two to end up with a pretty-darn darn-pretty design .

… I ran out of gas this time ^^; … Hopefully next time I’ll continue.

And, I have finally pushed myself to publish a video tutorial! I am not sure whether it will be useful or not but I’d be happy if just a handful of people learn a thing or two .

Now, I am going to simply rant and blabber until the video is exported and published to YouTube, then, I will add it, and stop this ranting . So, what will the ranting be about? The tutorial, of course!

I was very excited recently when I wrote a kinda modular class that provides Infinite Scrolling illusion to a UIScrollView. So, I really wanted to share what I learned to the masses. It is, however, a long journey, and requires many concepts to be explained in detail, so I can’t really make it a single short tutorial. Thus, I have prepared today the first part, which is waaay easier than the second part. Especially in these busy days, I cannot manage to publish the second part without sacrificing quality, so it will have to wait a week or two till its released. (Not yet Bob? [Bob is my rendering engine. You see, I give different parts of my computer different names. For example, my sound output is called "Wolf". My family often hear me yelling, "Shut up, Wolf!", and they would think I went nuts... Aaaanyways.]).

Wow, Bob has quiet down .. I am sure he’s done by now … Half way though, you say? Oh, he passed the job to Thomas (My network card ). Bummer, Thomas takes his time to upload .. I think I’ll go do something useful, and stop wasting time .

…

And the tutorial you have been waiting for!!

YouTube Tutorial

And the Source Code which you have been REALLY waiting for!

The Source Code

GAAAAAH!!! I just had to yell it out!

I am over with the hardest parts of my graduation project, over with the toughest finals, and most importantly, I am just furious at myself for not writing for so long! [-__-']

On with the post, the sneak peak! Today, though shalt expose parts of thy project!! (My inner literature just goes nuts when I am excited).

Without further ado .. Let us look at this project!

Islamicaster .. Inspired from all the “caster” applications out there, me and my mates in the project decided to call our project “Islamic – caster”, with the c being mutual. And please, it is pronounced ISLAMIC and not IZLAMIC.

So, what’s so super cool about this project? Number 1 coolest thing probably is that we were fortunate enough to work with a VERY talented Kuwaiti artist. Sir Ahmad Al-Refaie, whom can be found at Owaikeo.com, is currently employed at Pink Coffee & PR, and these guys were kind enough to take care of the graphics design part of the application! This made us work in full potential on the programming side of the project. Still, the graphics are simply breath taking and “outstounding”. (I just made that up, which is a mix of two words that fit that place perfectly. I leave it as an exercise for the reader to figure these two words out :p).

In my opinion, the second best thing about this project is “Portability”. Before you start throwing me with nuts for introducing computer Jargon here, let me clear it out. Thy project shalt  run consistently on iOS, Mac and Android! YES! (As much as possible). The fact is we have already finished much of the Mac app, and the mobile platforms remain. Point is, we are already on three platforms before going official! Hopefully expanding ever more as the project grows larger with more human resources :p.

I am not going to say anymore than that! If you would really like to know more about Islamicaster, please come visit us at the Engineering Exhibition!

The first day will be from 12:30pm – 10:00pm, while the second day will be from 9:00am till 8:00pm .

We really look forward to seeing you there!