Create an account

Very important

  • To access the important data of the forums, you must be active in each forum and especially in the leaks and database leaks section, send data and after sending the data and activity, data and important content will be opened and visible for you.
  • You will only see chat messages from people who are at or below your level.
  • More than 500,000 database leaks and millions of account leaks are waiting for you, so access and view with more activity.
  • Many important data are inactive and inaccessible for you, so open them with activity. (This will be done automatically)


Thread Rating:
  • 308 Vote(s) - 3.43 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Swift class vs Cocoa Touch Class in Xcode6

#1
I am new to iOS development and have started directly with Swift.

When I want to add a new file to a project, the IDE presents me with two files which seem to be used interchangeably in the tutorials that I have seen so far.
They are "Cocoa Touch Class" and "Swift Class".

When I create a new Cocoa Touch Class, this is what I get(depending on the class inherited)

import UIKit

class CtTest: NSObject {

}

and when I create a new Swift file, I get this:-

import Foundation

The extension for both of these classes is .swift

If I add the class definition to the Swift file and modify it as follows:-

import UIKit
import Foundation

class SwTest:NSObject
{
}

is there any difference that remains between the two files.

If so, which classes are preferred in what scenarios eg. View Controllers, Models etc.

Thank You
Reply

#2
There is no difference between the two different templates other than the code they put into the file by default. Like you noticed, they both have the same extension and they are both plain text files – the compiler does not treat them any differently.

The general rule of thumb is to only import a module if you need it in that file – basically you get a compile error otherwise. You will get a compiler error because of missing imports if you try to use types from them.

# Foundation

Foundation is basically the Apple development standard library, implemented in Objective-C. It includes data types like NSArray, NSString, and NSDictionary. However, Swift provides replacements for these data types: Array, String, and Dictionary. You should only need to `import Foundation` in files that try to interact with Objective-C APIs. However, since all existing APIs are written in Objective-C (since Swift is so new), you will have to import Foundation in almost all files except for basic domain objects.

# UIKit

UIKit actually includes Foundation. If you import UIKit, you do not need to also import Foundation. UIKit is a collection of standard APIs specific to the iOS interface. It includes views like UITableView and controllers like UIViewController. You will need to import this whenever working on the UI of iOS apps.

# Cocoa Touch Class

This template is useful for subclassing classes from UIKit and potentially having Xcode generate interface builder files for you. If you don't need either of those things, you should just use the Swift Class template. Only have your object inherit from NSObject if you really have to (if you need to be able to use your Swift class from Objective-C). If you don't inherit from NSObject, there are extra optimizations that the compiler can make and it avoids some of the slower parts of the Objective-C runtime.
Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

©0Day  2016 - 2023 | All Rights Reserved.  Made with    for the community. Connected through