1.json json编码解码
2.GTMBase64 base64编码解码
3.TouchXML xml解析
4.SFHFKeychainUtils 安全保存用户密码到keychain中
5.MBProgressHUD 很棒的一个加载等待特效框架
6.ASIHTTPRequest http等相关协议封装
7.EGORefreshTableHeaderView 下拉刷新代码
8.AsyncImageView 异步加载图片并缓存代码
9.类似setting的竖立也分栏程序

AppStore软件排名相关,工欲善其事，必先利其器。

1.下载排名相关:appannie
2.用户行为分析:flurry
3.majicrank-各国排名查询工具
4.AppViz-App销售统计软件
5.PodViz-用户评论等查看工具
6.appfigures-报表统计分析工具
7.我成立的一个帮助开发者推广app的评测站:苹果I派党

Zynga刚刚收购了HTML5游戏引擎公司Dextrose AG ,可以预计明年的HTML5应用将飞速增加
开发者使用HTML5的优势是可以将游戏编码移植到多个平台

对个人开发者而言:
短期做iphone赚钱,赚了钱再投入到Android或html5上面去.

再接再励吧,希望英文app卖的好才是王道.

附带一奶瓶,由此可见主人也不是很残忍,那为什么要遗弃呢?

很棒的一篇关于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

    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

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

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>UIInterfaceOrientation</key>    <string>UIInterfaceOrientationPortrait</string>    <key>UIInterfaceOrientation~ipad</key>    <string>UIInterfaceOrientationLandscapeLeft</string>    ...

Programmatically Determining Device

    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!

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:

效果：

相关讨论：

http://www.cocoachina.com/bbs/read.php?tid-25636-page-1.html

这个讨论内容可能用的上(右边多个控制器相关)：

http://www.cocoachina.com/bbs/read.php?tid-24466.html

源码demo：
下载

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

程序先把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

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

[[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—