Namespaced classes in swift

AppDelegate.swift

//
//  AppDelegate.swift
//  Namespaced
//
//  Created by Mika Jauhonen on 2014-09-18.
//  Copyright (c) 2014 Mika Jauhonen. All rights reserved.
//

import UIKit

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

	var window: UIWindow?


	func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {
		
		let testOne = Package.SubPackage.SubPackageOne.Test()
		let testTwo = Package.SubPackage.SubPackageTwo.Test()
		
		println(testOne.name)
		println(testTwo.name)
		
		return true
	}

	func applicationWillResignActive(application: UIApplication) {
		// Sent when the application is about to move from active to inactive state. This can occur for certain types of temporary interruptions (such as an incoming phone call or SMS message) or when the user quits the application and it begins the transition to the background state.
		// Use this method to pause ongoing tasks, disable timers, and throttle down OpenGL ES frame rates. Games should use this method to pause the game.
	}

	func applicationDidEnterBackground(application: UIApplication) {
		// Use this method to release shared resources, save user data, invalidate timers, and store enough application state information to restore your application to its current state in case it is terminated later.
		// If your application supports background execution, this method is called instead of applicationWillTerminate: when the user quits.
	}

	func applicationWillEnterForeground(application: UIApplication) {
		// Called as part of the transition from the background to the inactive state; here you can undo many of the changes made on entering the background.
	}

	func applicationDidBecomeActive(application: UIApplication) {
		// Restart any tasks that were paused (or not yet started) while the application was inactive. If the application was previously in the background, optionally refresh the user interface.
	}

	func applicationWillTerminate(application: UIApplication) {
		// Called when the application is about to terminate. Save data if appropriate. See also applicationDidEnterBackground:.
	}


}

Package.swift

//
//  Package.swift
//  Namespaced
//
//  Created by Mika Jauhonen on 2014-09-18.
//  Copyright (c) 2014 Mika Jauhonen. All rights reserved.
//

import Foundation

public struct Package {
	public struct SubPackage {
		public struct SubPackageOne {
		}
		public struct SubPackageTwo {
		}
	}
}

PackageOne.SubPackage.SubPackageOne.Test.swift

//
//  PackageOne.SubPackage.SubPackageOne.Test.swift
//  Namespaced
//
//  Created by Mika Jauhonen on 2014-09-18.
//  Copyright (c) 2014 Mika Jauhonen. All rights reserved.
//

import Foundation

extension Package.SubPackage.SubPackageOne {
	public class Test {
		let name = "I am Test in PackageOne.SubPackage.SubPackageOne"
	}
}

PackageOne.SubPackage.SubPackageTwo.Test.swift

//
//  PackageOne.SubPackage.SubPackageTwo.Test.swift
//  Namespaced
//
//  Created by Mika Jauhonen on 2014-09-18.
//  Copyright (c) 2014 Mika Jauhonen. All rights reserved.
//

import Foundation

extension Package.SubPackage.SubPackageTwo {
	public class Test {
		let name = "I am Test in PackageOne.SubPackage.SubPackageTwo"
	}
}

@mikajauhonen, how do you deal with storyboards? The struct/extension approach works perfectly (so far), however I cannot point to any class namespaced this way from within my storyboard because it does not recognize such.

Thanks.

@stanislaw raises an interesting question. However I'm gonna use this approach for business classes and see how it turns out. Coming from ruby I really miss this way of doing things. :)