require "twitter.lib.php";

$username = "trembl";
$password = "••••••••";

$twitter = new Twitter($username, $password);

$options = array(
    "profile_background_color" => "fff",
    "profile_text_color" => "fff",
    "profile_link_color" => "fff",
    "profile_sidebar_fill_color" => "fff",
    "profile_sidebar_border_color" => "fff"
);

$update_response = $twitter->updateProfileColors($options);
print_r($update_response);

Nice, isn't it?

OK, I've decided to do it. To leave the elegance of Objective-C and have a closer look at C++. After all, isn't everyone doing oF these days?

Here a recapitulation of usesful C and some quick notes on C++ peculiarities - sorry - features: (That might be a good place to start.)

Initialisation int a = 1; // standard c way int b(1); // same

Defined constants

define PI 3.1415927 // faster than var

Declared constants const int c = 100 // immutable

Assignment = can also be used as rvalue a = 1 + (b = 2);

same as: b = 2; a = 1 + b;

Comma operator a = (b=3, b+2); // a = 5

When the set of expressions has to be evaluated for a value, only the rightmost expression is considered

Type casting int i, j; float f = 1.234; i = (int) f; j = int (f);

sizeof() One parameter, either a type or a variable and returns the size in bytes.

a = sizeof (char);

Will become important with arrays.

printf ("floats: %4.2f %+.0e %E \n", 3.1416, 3.1416, 3.1416); floats: 3.14 +3e+000 3.141600E+000

Very funny and strange case of rejection. I made a method called 'singleTap', that is - as the name suggests - receiving events after a single tap occurs. During the development process the function was not used and commented out, but an oversight let to the notification being left it. And then the message from Apple:

"3.3.1 Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs." The following non-public API is included in your application: singleTap:

Hmm. Clearly I did not use a private API, apparently I just happened to call a function the same name as a private API function... Wondering if there is a list of reserved function names, which is triggered a rejection?

Solution? I commented out the superflicial notification AND renamed the function to 'oneTap'. Just in case.

I am starting to believe the stories about the Apple store.

Creating and Posting a Keyboard Event:

CGEventRef sDown, sUp;
sDown = CGEventCreateKeyboardEvent (
            NULL,
            (CGKeyCode)1,
            true
);
CGEventSetFlags(sDown, kCGEventFlagMaskShift);  

// setting flags with special function. 
// Setting it via CGCreateKeyboardEvent
// would work only for the first time it's run

CGEventPost(kCGHIDEventTap, sDown);

sUp = CGEventCreateKeyboardEvent (
            NULL,
            (CGKeyCode)1,
            false
);
CGEventPost(kCGHIDEventTap, sUp);

CFRelease(sDown);
CFRelease(sUp);

That leaves the door open for applying the same to mouse events:

CGEventRef mouseEvent;
mouseEvent = CGEventCreateMouseEvent (
            NULL,
            kCGEventMouseMoved,
            CGPointMake(100, 100),
            kCGMouseButtonLeft
);
CGEventPost(kCGHIDEventTap, mouseEvent );

Magical. Isn't it.

Of course, in pre-10.6 days it would have looked like that:

CGPostKeyboardEvent (0,5,true);
CGPostKeyboardEvent (0,5,false);

Looking Projectwide for NSLog's:

Shift-Apple-F: [^//]NSLog

All the NSLogs, which don't have // infront of them.

Update: This might be a more elegant way to get rid of the NSLogs. 447

Saving Images to the Shared User Photo Album using the UIKIT UIImageWriteToSavedPhotosAlbum() function:

void UIImageWriteToSavedPhotosAlbum (
    UIImage *image,
    id completionTarget,
    SEL completionSelector,
    void *contextInfo);

Usage:

UIImageWriteToSavedPhotosAlbum(
    [theImage retain], 
    self, 
    @selector(image:didFinishSavingWithError:contextInfo:), 
    nil);

// callback when saving is done...
- (void)image:(UIImage *)image didFinishSavingWithError:(NSError *)error contextInfo:(void *)contextInfo {
    NSLog(@"finished saving");
    [image retain];
}

No 100% sure if the image has to be retained. It also seems to work without retaining and releasing it...

It takes about 3 seconds to save a 480x320 image on an iPhone 3GS. Feels a bit long...

- (BOOL)webView:(UIWebView )webView shouldStartLoadWithRequest:(NSURLRequest )request navigationType:(UIWebViewNavigationType)navigationType {

// intercepting web click in the webView
NSLog(@"%@,  %i", [request.URL absoluteString], navigationType);

}

Don't forget to set <UIWebViewDelegate>

A quick reminder on how caching works in Objective-C.

Initially there is one cache, NSURLCache administrates it.

Get the object:

NSURLCache *cache = [NSURLCache sharedURLCache]

[cache memoryCapacity];
[cache setMemoryCapacity: 1024*1024*1]; // in byte
[cache currentMemoryUsage];

Don't worry about the disk aka the flash memory in iPhone, it's not accessible.

A bit of strange behaviour, either a bug in the software or in my brain: When changing ViewControllers the memoryCapacity seems to reset itself to 0, although previous caches remain intact. Re-setting the memoryCapacity back to the original level seems to solve this. (The cache is not overwritten.)

Using the Cache The whole point of using the cache is to not download online material over again. The following steps make for a happy cache:

//URLRequest
NSURLRequest *request = [NSURLRequest requestWithURL:theURL
cachePolicy:NSURLRequestUseProtocolCachePolicy timeoutInterval:10.0f];

The delegate response would allow you to alter the about-to-be-cached-data, leaving it in is not necessary:

- (NSCachedURLResponse *)connection:(NSURLConnection *)c
willCacheResponse:(NSCachedURLResponse *)response {
    NSLog(@"willCacheResponse");
    return response;
}

All in all, not that much to take it. Finding out, that the memoryCapacity gets reset was the most time-consuming bit. For another example, of how to roll your own cache, look at URLCache example.

PHP explode(", " , "One, Two, Three");

Objective-C NSArray *listItems = [@"One, Two, Three" componentsSeparatedByString:@", "];