The exact radius for the icon rounded corners is:

• iPhone OS 3.x(57×57) is 9 pixels
• iPhone OS 4.0(114×114) I guess it’s 18 pixels but I’m not sure of that

The exact radius for the Artwork(512×512) is 80 pixels.

1. Make the MyViewController a UIScrollViewDelegate. Do this by adding in the @interface declaration in the .h file.
2. Create a UIImageView instance variable in the @interface of MyViewController. We will need this to specify it to the Delegate which object is to be zoomed. Add the @property and @synthesize for this image in relevant places. I used scroll2ImageView as the name of the instance.
3. In the viewDidLoad Method in myViewController.m class replace the code for setting up scrollView2 with this code.

[scrollView2 setBackgroundColor:[UIColor blackColor]];
[scrollView2 setCanCancelContentTouches:NO];
scrollView2.clipsToBounds = YES; // default is NO, we want to restrict drawing within our scrollview
scrollView2.indicatorStyle = UIScrollViewIndicatorStyleWhite;
scroll2ImageView = [[UIImageView alloc] initWithImage:[UIImage imageNamed:@"image0.jpg"]];
[scrollView2 addSubview:scroll2ImageView];
[scrollView2 setContentSize:CGSizeMake(scroll2ImageView.frame.size.width, scroll2ImageView.frame.size.height)];
scrollView2.minimumZoomScale = 1;
scrollView2.maximumZoomScale = 3;
scrollView2.delegate = self;
[scrollView2 setScrollEnabled:YES];


We made three changes here. First we replaced the local instance of imageView with the class instance scroll2ImageView. We will need this in the next step. Second we added min/max zoom scale for the image. Third we assigned the scrollView2 delegate to self.

4. Last thing we need to do is tell the delegate wat all to zoom when it detects a zoom in/out pinch. We add the following method for this.

-(UIView *) viewForZoomingInScrollView:(UIScrollView *)scrollView {
return scroll2ImageView;
}


This app is a pocket catalogues of all the products that can be found in each Uterqüe store, organized by sections which is very useful for all customers, but one of the most important features of the application is the update frequency: Uterqüe’s team will update the content weekly to keep you informed about all its new products.

Now the user can use a Augmented Reality or Google maps functionalities to search his closest store.

I would like to take this post to talk about mobile marketing posibilities, there is a lot of companies around the world using mobile marketing solutions to promote their products. iPhone and large set of latest mobile devices has the multimedia capabilities to provide a very easy, clear and useful channel of communication between companies and it’s potential customers.

The fact of Uterque releasing a set of applications available in most important plattforms(iPhone, Android, Nokia, Blackberry,…) it’s just another example of how useful can be for the companies to keep his customers updated with it’s latest products through a maketing mobile application.

I didn’t knew the answer at this moment but once I got to the office I decided to look for it. After a few minutes googling I found the answer: it’s possible, and here is the source code to do it.

NSArray *topLevelObjs = nil;
topLevelObjs = [[NSBundle mainBundle] loadNibNamed:nibNameOrNil owner:self options:nil];

if (topLevelObjs == nil)
   NSLog(@”Error! Could not load nib file.\n”);


[myMailComposerVC setTitle:@"My title"]

but if you do that you don’t get anything, you still get the “NEW MESSAGE” text.
The way I found to access it is the following. Maybe there is another/better don’t know but this one definitely works:

[[[[myMailComposerVC navigationBar] items] objectAtIndex:0] setTitle:@”My title”];

Hope it helps someone as much as it helped me.

App Store Icon

• 512×512

Application Icon

• 114×114 iPhone 4
• 72×72 iPad
• 57×57 older iPhones

Spotlight Search Results and Settings Icon

• 58×58 Spotlight/Settings iPhone 4
• 50×50 Spotlight - iPad
• 29×29 Settings - iPad/older iPhones

Document Icon

• 44×58 iPhone 4
• 320×320 and 64×64 iPad
• 22×29 older iPhones

I found this usefull PSD in “Cocoia Blog”.

You might wonder if that is because there is no easy way to build an application with both HD graphical assets and nonHD graphical assests that looks great on all iPhone OS versions. But that’s not true. Recently I found out a very esy way to do that:

UIKit supports the automatic loading of high-resolution variants (@2x) of your images.

The “only” thing you have to do is generate HD graphical images of each existing image in your current project and name it the same but with an @2x in the end. i.e:

previous image name: logo.png

HD image name: logo@2x.png

once you have all the images just import to your existing project and compile it again using the same iPhone OS version you used to compile the nonHD version of the application, and submit it to the store.

Et voilà! The iOS 4 will handle it automatically to display your new HD images.


#import <CommonCrypto/CommonCryptor.h>



@implementation NSMutableData (AES256)
- (BOOL) encryptWithKey: (NSString *) key {
// 'key' should be 32 bytes for AES256, will be null-padded otherwise
char * keyPtr[kCCKeySizeAES256+1]; // room for terminator (unused)
bzero( keyPtr, sizeof(keyPtr) ); // fill with zeroes (for padding)

// fetch key data
[key getCString: keyPtr maxLength: sizeof(keyPtr) encoding: NSUTF8StringEncoding];

// encrypts in-place, since this is a mutable data object
size_t numBytesEncrypted = 0;
CCCryptorStatus result = CCCrypt( kCCEncrypt, , kCCAlgorithmAES128, kCCOptionPKCS7Padding,
keyPtr, kCCKeySizeAES256,
NULL /* initialization vector (optional) */,
[self mutableBytes], [self length], /* input */
[self mutableBytes], [self length], /* output */
&numBytesEncrypted );

return ( result == kCCSuccess );
}



- (BOOL) decryptWithKey: (NSString *) key {
// ‘key’ should be 32 bytes for AES256, will be null-padded otherwise
char * keyPtr[kCCKeySizeAES256+1]; // room for terminator (unused)
bzero( keyPtr, sizeof(keyPtr) ); // fill with zeroes (for padding)

// fetch key data
[key getCString: keyPtr maxLength: sizeof(keyPtr) encoding: NSUTF8StringEncoding];

// encrypts in-place, since this is a mutable data object
size_t numBytesEncrypted = 0;
CCCryptorStatus result = CCCrypt( kCCDecrypt, , kCCAlgorithmAES128, kCCOptionPKCS7Padding,
keyPtr, kCCKeySizeAES256,
NULL /* initialization vector (optional) */,
[self mutableBytes], [self length], /* input */
[self mutableBytes], [self length], /* output */
&numBytesEncrypted );

return ( result == kCCSuccess );
}
@end



NSData *myData;
myData = [myString dataUsingEncoding: NSUTF8StringEncoding];



NSString *myStr;
myStr = [[[NSString alloc] initWithData:myData encoding:NSUTF8StringEncoding] autorelease];


%@ Object
%d, %i signed int
%u unsigned int
%f float/double
%x, %X hexadecimal int
%o octal int
%zu size_t
%p pointer
%e float/double (in scientific notation)
%g float/double (as %f or %e, depending on value)
%s C string (bytes)
%S C string (unichar)
%.*s Pascal string (requires two arguments, pass pstr[0] as the first, pstr+1 as the second)
%c character
%C unichar
%lld long long
%llu unsigned long long
%Lf long double



UIGraphicsBeginImageContext(renderImage.size);
CGContextSetBlendMode(UIGraphicsGetCurrentContext(), kCGBlendModeCopy);
[renderImage drawInRect:CGRectMake(0, 0, renderImage.size.width, renderImage.size.height)];
CGContextSetBlendMode(UIGraphicsGetCurrentContext(), kCGBlendModeDifference);
CGContextSetFillColorWithColor(UIGraphicsGetCurrentContext(),[UIColor whiteColor].CGColor);
CGContextFillRect(UIGraphicsGetCurrentContext(), CGRectMake(0, 0, renderImage.size.width, renderImage.size.height));
renderImage = UIGraphicsGetImageFromCurrentImageContext();
UIGraphicsEndImageContext();


There are no big changes on the applications, the most important one is we removed the in app purchase service of the application, but we added we’ve added adMob advertisements. So the application is completely free right now

In this version you’ll also find:

• Some minor performance issues fixed.
• Updating bug when launching the application fixed.

• Loading time improved: now it’s much more faster.
• News quick summary: to read while waiting for the website to load.
• New share functionality: send the news links you find interesting
  to all of your friends by email.
• Interface redesign: a new set of icons added to make the
  application look more clear and fancy.
• New headlines’ styles: to quickly identify which has been read and
  which not.

We also want to announce that we are waiting for the approval of the v2.0 version of both applications which will have some minor changes. I’m sure you will be wondering why we have moved application version from 1.2 to 2.0 if there is no big changes on it.
That’s ’cause the big changes are in the way we are going to sell it.

From now and on you’ll find both applications with a 15 days FREE trial and WITHOUT any kind of SUBSCRIPTION.

Once the trial time expires you will be asked to buy the application using the InAppPurchase system, so if you liked it, don’t hesitate to buy it just for .99 $, and enjoy the application for the rest of your life.

These apps are pocket catalogues of all the products that can be found in each ZARA store, organized by sections which is very useful for all customers, but one of the most important features of the application is the update frequency: ZARA’s team will update the content weekly to keep you informed about all its new products.

I would like to take this post to talk about mobile marketing posibilities, there is a lot of companies around the world using mobile marketing solutions to promote their products. iPhone and large set of latest mobile devices has the multimedia capabilities to provide a very easy, clear and useful channel of communication between companies and it’s potential customers.

The fact of ZARA releasing a set of applications available in most important plattforms(iPhone, Android, Nokia, Blackberry,…) it’s just another example of how useful can be for the companies to keep his customers updated with it’s latest products through a maketing mobile application.

We wanted to provide the application with the best news quality we could and that’s why we work with the top spanish online press clipping company as a partner that provides us all the application news content. It has more than 2500 online sports sources in 13 languages.

For example we need to store CGPoints.


NSArray *points = [NSArray arrayWithObjects:
[NSValue valueWithCGPoint:CGPointMake(5.5, 8.3)],
[NSValue valueWithCGPoint:CGPointMake(11.9, 8.5)],
nil];


And when we need to get these points, for example the first point


NSValue *val = [points objectAtIndex:0];
CGPoint p = [val CGPointValue];


We wanted to provide the application with the best news quality we could and that’s why we work with the top spanish online press clipping company as a partner that provides us all the application news content. It has more than 2500 online sports sources in 13 languages.

The answer to question that is as simple as: “we haven’t done it before because the 90% of our works are confidential”. We thought it would be better to wait until we had at least 2 own applications or 2 non-confidential applications on the store.

We want to communicate that we are working on a serial of “Football Club News Reader” applications based on our MobileNewsApp engine. So you could expect more applications on that field before the end of the year. We are also working on 2 non-confidential projects which are going to be released soon. Because of that serial of events we are pretty sure that now is the best moment to update this website with the work section.

This kind of error is hard to debug, it happens when a message is sent to a released object, but the Xcode debugger doesn’t give any kind of information about which is the released object, because it is already released and it isn’t allocated in memory anymore, so the debugger doesn’t know it’s structure and it only has a pointer to an “empty” memory address. As the application can crash at anytime before the object is released it seems to be quite aleatory and sometimes hard to reproduce and trace.

So ’cause each EXEC_BAD_ACCESS error is different depending on your specific source code, I can’t give a generic solution, but I can explain you a way to trace it. you should know that exists an environment variable called NSZombieEnabled. If you set it to yes, Objective-C will leave in memory a dummy object for each deallocated object, then if your application send a message to the zombie object, execution will stop and you will be able to take a look at the stack and see from where the object is called. It can’t tell you the specific line of your source where the object is released, but it shows you the method where your object is called before being released and this should you get an idea of where the problem is.

So I imagine that now you are wondering hot to set up this variable, so let’s go on. To do it you have to create a new instance variable right clicking on your executable name, inside the executables group on the left side column of your Xcode’s project screen. Then choose the get info option. Then tap on the Arguments tab. You will see to white boxes, the second one is the one to set up environment variables, so press the + symbol under the white box and name the variable NSZombieEnabled with the word YES as the value. Make sure the checkbox is selected.

So you just have to run your application in debug mode, next time the EXEC_BAD_ACCESS occurs, the application will stop and you will see this kind of message in the debugger console:

2009-10-19 09:33:00.000 xxxxx[3997:20b] *** -[YourObject retain]: message sent to deallocated instance 0xXXXXXXX

Now you are able to click on the debugger and take a look at the stack. You will see some methods in bold, these are the ones you should take a look to review where your object is called after being released.

Remember that you have to uncheck the checkbox of the NSZombieEnabled variable once you fix the problem, or delete the variable if you prefer, or you will experience memory crashes, because of the zombie objects allocated and never freed.