花太香齐的博客 » iPhone/Mac/ObjectC

[转]Converting iPhone Apps to Universal Apps

花太香齐 — Sat, 31 Jul 2010 08:53:54 +0000

很棒的一篇关于Universal程序的心得,原文地址:http://iphonedevelopment.blogspot.com/2010/04/converting-iphone-apps-to-universal.html
(需翻墙)

Well, the NDA has finally lifted, so we can start talking about iPhone SDK 3.2 and the iPad. The logical starting place seemed to be how to convert your existing applications into a “Universal App” that runs natively both on the iPad and the iPhone/iPod touch. Now, a lot of you have likely already had to figure this stuff out so you could get your updated app on the store today, but for those who didn’t go the early adopter route, let’s take a few minutes to look at the process. It’s pretty straightforward but there are a few gotchas.

Note: There are some additional things you should know, so read this post also before tackling your update.

Targeting All Devices

The first thing you have to do is identify that you want to build your existing application as a universal application. For this article, I’m using the Xcode project from OpenGL ES Particle Generator Application, but I’ll try to keep the information general. Note: the following step is not needed if you use Xcode’s Update Project Target for iPad option talked about here.

Bring up your Project Info window in Xcode by either double-clicking on your project’s root node in the Groups & Files pane or selecting Edit Project Settings from the Project menu and then navigate to the Build tab. Now, the change we’re about to make needs to be made to all configurations, so make sure that the Configuration popup menu is set to All Configurations, otherwise you’ll only make the change on one configuration.

We need to change a setting called Target Device Family, so type Target into the search bar, or just search for that entry manually (it’ll be under the Deployment heading). Right now, it should look like this:

See how it says iPhone? Yeah, you know what to do. Click on it and change it so it reads iPhone/iPad, like so:

Good! now you’re done, right? Most likely, no.

Auditing for Hardcoded Sizes

The next thing you’re going to want to do is audit your application to see if you hard-coded the screen size anywhere in your application. You shouldn’t have hardcoded those values, but let’s face it, we’ve all done it. A Project Find (⌘⇧F) for 320 and 480 and that should turn up any of those hardcoded values. In the Particle Generator code, I did it in only one place, in code that creates a UIImage of the OpenGL view. The line of code where I did it looks like this:

    CGImageRef imageRef = CGImageCreate(320, 480, bitsPerComponent, bitsPerPixel, bytesPerRow, colorSpaceRef, bitmapInfo, provider, NULL, NO, renderingIntent);

Usually, the fix for this will be obvious. Instead of hardcoding, you want to pull the width and height from the OpenGL view. The code where I did it actually exists on the GLView class, so I can fix it like so:

    CGImageRef imageRef = CGImageCreate(self.frame.size.width, self.frame.size.height, bitsPerComponent, bitsPerPixel, bytesPerRow, colorSpaceRef, bitmapInfo, provider, NULL, NO, renderingIntent);

But, what if what you’ve hardcoded is the actual size of the view? Then you need to pull the size from the main screen instead of the view. That’s easy enough to do.

    UIScreen *screen = [UIScreen mainScreen];    [myView setFrame:[screen applicationFrame]];

Dealing with Different Window Sizes

Most likely your application’s one instance of UIWindow is contained in your MainWindow.xib file that gets loaded automatically. Most likely, that Window is hardcoded to 320×480. Now, you might think that you can just go into Interface Builder and set the autosize attributes for the window and it will get resized for you at launch. You would be wrong. There is no automatic check to make sure your window is the right size.

You have to make sure that the window is the right size for the device you’re running on. There are, basically, two ways of doing that. If your application is such that you just need to resize the window and your autosize attributes will take care of making everything look nice, then you can just handle this programmatically in applicationDidFinishLaunching: by setting the window’s size to the size of the screen, less the status bar andy any other objects controlled by the iPhone OS (this is known as the Application Frame). Doing this looks almost exactly like setting the size of the view above:

    CGRect  rect = [[UIScreen mainScreen] bounds];    [window setFrame:rect];

Now, this is actually a good approach for the Particles application because it has one full-screen view. However, the iPad and the iPhone are really different devices, and there are several UI components available on the iPad that aren’t available (at least yet) on the iPhone, such as split views and pop up views. For many applications, especially complex applications using a lot of UIKit views and controls, you’re probably going to want to provide completely different NIB file based on which device on which the code is running.

Info.Plist Device-Specific Entries

The one really important nib file in every iPhone application is, of course, MainWindow.xib, and there has to be a way to tell your application to use a different MainWindow.xib for different devices. In fact, there is. For each key that Info.plist supports, such NSMainNibFile, which is used to specify the name of the application’s main nib file, you can now specify device-specific entries. If you provide a device-specific entry for the device the application is currently running on, it will use the device-specific value, otherwise it will just use the normal value.

Device-specific keys are exactly the same as the original or default key except the key name is followed by a tilde (~) and then the name of the device in all-lowercase letters. So, to tell our application to load a different nib file for the iPad, we can add a key called NSMainNibFile~ipad and then specify the name of the nib file to use when launching on an iPad. For the iPhone and iPod touch, it will continue to use the default value, MainWindow.xib, but for the iPad, it will use the nib file you’ve specified in the new, device-specific key.

You can add a new version of MainWindow.xib to your project by selecting the Resources group and choosing Add New File from the File menu. From the New File Assistant, select User Interface from under the iPhone OS, then select Application XIB, and make sure you select the right device in the Product drop-down.

Make sure you remember to connect all the outlets and actions in this new nib to the same outlets and actions you used in the other nib. Remember, only one of the application nibs will be loaded, so there’s no conflict.

For any key in the Info.plist file, you can use this same technique to override the default value with a device specific. You could, for example, have the iPhone version start in Portrait and the iPad version start in landscape, like so:

    ...    <key>UIInterfaceOrientationkey>    <string>UIInterfaceOrientationPortraitstring>    <key>UIInterfaceOrientation~ipadkey>    <string>UIInterfaceOrientationLandscapeLeftstring>    ...

Programmatically Determining Device

If you have code that needs to vary depending on whether it’s running on the iPad or iPhone/iPod touch, Apple has provided a new macro called UI_USER_INTERFACE_IDIOM() that will tell you that. There are currently two values defined, UIUserInterfaceIdiomPhone and UIUserInterfaceIdiomPad, and this macro will return the value that corresponds to the device being run. So, for example, if you needed to push a view controller onto the navigation stack, but wanted a different nib used for the iPad than the iPhone, you might do this:

    MyController *controller = nil;

    if (UI_USER_INTERFACE_IDIOM() == UIUserInterfaceIdiomPad)        controller = [[MyController alloc] initWithNibName:@"MyiPadNib" bundle:nil];    else        controller = [[MyController alloc] initWithNibName:@"MyiPodNib" bundle:nil];

    [self.navigationController pushViewController:controller animated:YES];    [controller release];

If you need finer-grain control, and need to know exactly which device, there’s no official, supported way to determine the exact device. The vast majority of the time you you think you need to know the device, you don’t actually need to know the device, you just need to know which features are supported. Even though you can find code around the web that will determine the device based on UIDevice, you really shouldn’t base your logic on that because such code can be fragile since you don’t know what future devices will exist, or what features they will have.

In cases like the Image Picker, Apple provides a way to determine which features are available on your device, such as whether there’s a camera, and whether that camera supports video. When Apple hasn’t provide a specific check or test, what you can do is use NSClassFromString(), which (as is probably obvious from the name) creates a Class instance based on the name of a class contained in a string. If this returns nil, then you know the class you’re asking about isn’t available. You can wrap your code that uses classes that aren’t available everywhere in these checks and make code that works correctly on all devices, and will continue to do so in the future (for the most part – it’s never possible to 100% future-proof code). Here’s an example of checking for the existence of the UISplitViewController, which is a new class only available on the iPad:

    Class splitViewController = NSClassFromString(@"UISplitViewController");    if (splitViewController)    {       UISplitViewController* mySplitViewController = [[splitVCClass alloc] init];       // ... configure, use, then release    }

You can do something similar with C functions by checking if the function is NULL For example, one of the frameworks added with iPhone SDK 3.2 is CoreText.framework. If we wanted to use the function CTFontCreateWithName() to create a new font using that framework, we could wrap the logic in an interface idiom check, like above, or we could just check to see if the function we want to use exists by seeing if the symbol CTFontCreateWithName is NULL at runtime, like so:

    if (CTFontCreateWithName != NULL)        CTFontFontRef myFont = CTFontCreateWithName(@"Comic Sans", 14.0, NULL);

Go, Go, Gadget iPad, Go!

Well, that pretty much covers the basics you’ll need to convert your existing iPhone apps to Universal Apps. The more complex your app, the more likely you’ll want to consider doing separate iPad and iPhone applications. I’ll show how to add another target to your Xcode project so you can generate two applications from the same project in a future post. For many apps, however, this should be enough to get you porting away, so port away!

Socket communication on the iPhone/iPad

花太香齐 — Thu, 29 Jul 2010 06:06:25 +0000

Some information on socket implementation on the iPhone, because I’ve found no information on the web and think this could be useful for others as well. Caution: More often than not you only want to get the contents of an URL, for this simply use the following:

NSString *someString = [NSString stringWithContentsOfURL:(NSURL *)url];

But if you in fact want to connect low level to a socket and read/write the bytes themselves you can get it running like this:

// This will be the read stream.
CFReadStreamRef myReadStream = NULL;

// This will be the write stream.
CFReadStreamRef myWriteStream = NULL;

// Create socket.
CFStreamCreatePairWithSocketToHost(kCFAllocatorDefault,
   (CFStringRef) yourHostAsNSString,
   yourPortAsInteger,
   &myReadStream,
   &myWriteStream);

// Open read stream.
if (myReadStream != NULL && CFReadStreamOpen(myReadStream))
{
   // Read bytes in chunks of ten bytes.
   UInt8 readBuffer[10];
   while (CFReadStreamHasBytesAvailable(stream))
   {
   // Read bytes.
   CFReadStreamRead(stream, buffer, 10);

   // Do something with your bytes ...
   }
}

// Open write stream.
if (myWriteStream != NULL && CFWriteStreamOpen(myWriteStream))
{
   // Write a byte.
   UInt8 writeBuffer[1];
   writeBuffer[0] = 42;
   CFWriteStreamWrite(stream, writeBuffer, 1);
}

// Be a good citizen.
CFReadStreamClose(myReadStream);
CFWriteStreamClose(myWriteStream);
CFRelease(myReadStream);
CFRelease(myWriteStream);

iPad类似Setting程序，竖屏SplitView小demo

花太香齐 — Thu, 29 Jul 2010 01:44:41 +0000

竖屏SplitView，类似系统的setting程序，一个demo。
看到cc很多人在问，发下。

效果：

TCP中connect加入的超时控制

花太香齐 — Wed, 28 Jul 2010 08:12:07 +0000

最近写iPad下iWebmaster中portscan用到的,备份记录下,大致核心部分如下:

在使用TCP的connect连接服务器时，在默认情况下系统使用的是阻塞式socket，如果服务器当前不可用，则connect会等待知道超时时间到达，而这个超时时间是系统内核规定的，并不能使用setSocketOpt来设置，这个函数只能设置send和recv的超时，为了能够随意控制connect的超时时间，可以使用select。大致的过程就是先将socket设置成非阻塞，使用select去轮询套接口，再根据套接口去判断连接状态。

int flag;
   flag = fcntl(sock,F_GETFL,0);
   flag |= O_NONBLOCK;
   fcntl(sock,F_SETFL,flag);//设置非阻塞
   if (type == SOCK_STREAM) {
   int ret = -1;
   connected = connect(sock, (struct sockaddr *) &address,
   sizeof(address));
   if (connected != 0 ) {//if 1
   if(errno != EINPROGRESS)
   logdown(ERROR,"connect error :%s\n",strerror(errno));
   else //esle
   {
   struct timeval tm;
   tm.tv_sec = 3;
   tm.tv_usec = 0;
   fd_set set,rset;
   FD_ZERO(&set);
   FD_ZERO(&rset);
   FD_SET(sock,&set);
   FD_SET(sock,&rset);
   socklen_t len;
   int error = -1;
   int res;
   res = select(sock+1,&rset,&set,NULL,&tm);
   if(res < 0)
   {
   logdown(WARNNING,"network error in connect\n");
   ret = -1;
   }
   else if(res == 0)
   {
   logdown(WARNNING,"connect time out\n");
   ret = -2;
   }
   else if (1 == res)
   if(FD_ISSET(sock,&set))
   {
   flag &= ~O_NONBLOCK;
   fcntl(sock,F_SETFL,flag);//设置阻塞
   return sock;
   }
   else
   {
   ret = -3;
   logdown(WARNNING,"other error when select:%s\n",strerror(errno));
   }
   return ret;
   }//else
   }//if 1
   return sock;
   }

程序先把socket设置成非阻塞，connect在非阻塞模式下会立刻返回，如果没有其他错误，返回值等于0。当connect不能立刻建立连接时，会返回一个EINPROGRESS，表示连接正在建立的过程中，这时我们可以使用select去轮询套接口，而select的轮询超时时间可以根据自己的需要去设置，最主要的是轮询的集合一定要是读和写的集合，即select的第二和第三个参数要赋值，待select返回就可以去判断返回值来确定connect的进程状态了。如果返回值小于0，说明connect的进程出现了错误，如果是等于0则说明connect超时，如果等于1，并且套接口此时的状态是可写，则说明了connect已经成功建立（关于这点大概是因为服务器接收了连接后，不会立刻想socket写数据，这是客户端就只能轮询到可写的socket，我觉得如果服务器接受连接并立刻写数据，在客户端就可能是返回2，这时学要同时判断socket的可读和可写了）；其他情况的话就算是其他错误吧，至此，我们只需要设置select的超时值就可以随心所欲地实现自己想要的connect连接超时了。

最后，别忘了把套接口设置会阻塞状态，毕竟阻塞状态加线程方便控制。

效果图:www.ieliwb.com/app/screenshot.php?s=iWebmasterHD

我会一直用心做好产品,做好服务的

花太香齐 — Fri, 16 Jul 2010 13:36:21 +0000

偶的生活查询for iPad 上线3天登上了中国区付费棒首,小小的祝贺一下.我会一直用心做好产品,做好服务的,感谢Apple,感谢AppStore,感谢所有Apple fans.

生活查询for iPad
生活查询for iPhone

不同控制器之间通信的一个好方法

花太香齐 — Thu, 15 Jul 2010 09:48:14 +0000

首页在view1的控制器初始化init方法里加上观察者模式方法:

[[NSNotificationCenter defaultCenter] addObserver:self
selector:@selector(reloadChat:)
name:@”reloadChat” object:nil];

-(void)reloadChat:(id)sender{}

在view2里的button添加用来触发view1的reloadChat方法:

[[NSNotificationCenter defaultCenter] postNotificationName:@”reloadChat” object:self];

—END—

一代二代iPhone千万别升级到iOS4.0,警惕!!!!

花太香齐 — Tue, 13 Jul 2010 14:52:48 +0000

偶二代机器就是一个活生生的例子,升级后卡的滴血.偶现在每天都运行在安全模式,正常模式放个音乐都卡的吐血……

后台运行就是个大垃圾,还没以前的插件好用…..

痛苦……
鸡肋……
鸡肋……
纠结……

有视频为证:

没有ipad,发布真机截图的几个方法

花太香齐 — Sun, 11 Jul 2010 13:05:46 +0000

1.CTRL+COMMAND+C,然后在Preview里New from clipboard(不带边框,推荐)

2.cmd＋shift＋4，这时按下空格就会出现相机窗口选择,点一下模拟器就可以(带边框)

iPhone的九宫格实现代码

花太香齐 — Sun, 11 Jul 2010 04:45:31 +0000

看到CocoaChina很多同学在问,其实很简单,我这是用图片堆砌实现的九宫格,分享如下:

效果图:

核心就这2个方法:

//Power by ieliwb.com
- (void)viewDidLoad {
   [super viewDidLoad];

   NSArray* imageNames = [NSArray arrayWithObjects:
   @"ico_mobile.png",
   @"ico_idcard.png",
   @"ico_postcode.png",
   @"ico_flight.png",
   @"ico_translate.png",
   @"ico_phone.png",
   @"ico_car.png",
   @"ico_health.png",
   @"ico_bjxm.png", nil];

   UIButton *Btn;
   for (int i=0; i<9; i++) {
   CGRect frame;
   Btn = [[UIButton buttonWithType:UIButtonTypeCustom] retain];
   [Btn setImage:[UIImage imageNamed:[imageNames objectAtIndex: i]] forState:UIControlStateNormal];//设置按钮图片

   Btn.tag = i;

   frame.size.width = 59;//设置按钮坐标及大小
   frame.size.height = 75;
   frame.origin.x = (i%3)*(59+32)+40;
   frame.origin.y = floor(i/3)*(75+24)+40;
   [Btn setFrame:frame];

   [Btn setBackgroundColor:[UIColor clearColor]];
   [Btn addTarget:self action:@selector(btnPressed:) forControlEvents:UIControlEventTouchUpInside];
   [self.view addSubview:Btn];
   [Btn release];

   }

}

//响应按钮事件
-(void)btnPressed:(id)sender{
   UIButton *Btn = (UIButton *)sender;
   int index = Btn.tag;

   switch (index) {
   case 0:
   if(mobileController==nil)
   mobileController = [[MobileController alloc]init];
   [self.navigationController pushViewController:mobileController animated:YES];
   break;
   //其他几个控制器类似
   }

}

九宫格背景修改可以这样实现:

- (void)loadView {
   UIImageView *contentView = [[UIImageView alloc] initWithFrame:[[UIScreen mainScreen] applicationFrame]];
   [contentView setImage:[UIImage imageNamed:@"subview_9_bg.png"]];
   [contentView setUserInteractionEnabled:YES];
   self.view = contentView;
   [contentView release];
}

UINavigationBar背景图片可以这样实现:

@implementation UINavigationBar (CustomImage)
- (void)drawRect:(CGRect)rect {
UIImage *image = [UIImage imageNamed: @"top_bg.png"];
[image drawInRect:CGRectMake(0, 0, self.frame.size.width, self.frame.size.height)];
}
@end

—-End—-

AppStore的Review效率……

花太香齐 — Sun, 11 Jul 2010 04:08:33 +0000

原因:

第一次:rewrite了私有api (苹果就是霸王,有些api只能自己用,还不让人改)
第二次:请提供用户名和密码测试,我日,(注册就在登录下面)
第三次:有彩票 (彩票的最好一律不要做了)
第四次:简介里有彩票 (连软件说明简介都要注意)

现在审查很慢很严格。而且，apple那里似乎也没有个不允许使用东西的列表,这应该是让我们开发者更加的注意自己的程序，不然被拒后再提交要花费很长时间.