Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can go ahead and open your app in Xcode 4.2 and it should still work. I've been working on a particular app since Xcode 3.x days and I'm nearly done, chugging along in Xcode 4.2 right now. It shouldn't be a problem. If you want to work with Xcode 4.1 you will be fine, but you won't be ale to use new features introduced in iOS 5. </p> <p>There are several aspects of "cross-version" development to note.</p> <ol> <li><p><strong>Testing:</strong> You can only test on version of iOS that are included with your SDK, or that are installed on physical devices that you may have. The SDK generally comes only with the latest iOS, sometimes the previous one is included as well, but since Xcode 4 was released, the older SDKs have been progressively deprecated with each release. This is not to say that your app which is linked against the iOS 5 SDK won't run on older versions of iOS. It just depends on how you implement new features.</p></li> <li><p><strong>Features:</strong> In order to support older versions of iOS properly, you want to make sure that you don't implement new features without <a href="https://stackoverflow.com/questions/3056016/alternatives-to-weak-linking-in-iphone-sdk">properly checking for the existence of classes, methods, and properties that were introduced in the newer versions of the OS</a>. Unlike Android, you don't have to worry about a million hardware configurations. ;-)</p></li> <li><p><strong>Weak Linking:</strong> To support a new feature and still be compatible with older versions of iOS, you need to weak link against frameworks that you are using to implement new features. You can read more about that in the <a href="http://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPFrameworks/Concepts/WeakLinking.html" rel="nofollow noreferrer">Apple Documentation on Weak Linking</a>.</p></li> <li><p><strong>Deployment Target:</strong> The setting that prevents the app from loading on older devices is called the "Deployment Target". If you set this to 3.1.3, then your app will run on iOS 3.1.3 and higher. Remember that if you don't code the the proper version checking, your app may break.</p></li> <li><p><strong>ARC:</strong> You can choose to enable or disable Automatic Reference Counting when you create the project. ARC scans your program at compile time only, not at runtime, it doesn't break the app on older versions of the OS.</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POHow can I support both iOS 4.X SDK and iOS 5 SDK in my iPhone app?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USMoshe
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can I support both iOS 4.X SDK and iOS 5 SDK in my iPhone app?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload