#swift3

[fooooooooooooooooool]

[Swift3]C-style for statement has been removed in Swift 3

[Swift3]C-style for statement has been removed in Swift 3

建议阅读时间：1分钟 0.太长不看版 Swift3使用for-in结构来写for循环 需要使用index下标的结构  for index in list.indices {    //循环体 } 实例：  var someInts:[Int] = [10, 20, 30] ​ for index in someInts.indices {    print( "索引 [\(index)] 对应的值为 \(someInts[index])") } 1.问题现象 C-style for statement has been removed in Swift 3 2.分析原因 根据问题英文报错，Swift 3不支持类似C结构的声明局部变量来更新index的操作 3.解决: Swift3只能使用for in结构

View On WordPress

[thedespicableblog]

上網不要亂按東西，會很容易出事.. 💸 #acer #swift3 #laptop #notebook #amd #radeon https://www.instagram.com/p/CEtrhchpdYp/?igshid=1ahc5p0m9d7gh

[kame-u-y]

Kame Flashcard

iOS用の単語帳アプリ

写真で撮影したものをそのまま単語帳に登録できる

自動車教習所に通っていたとき、冊子で学科試験の勉強をしている間に考えていたアプリケーション

冊子で間違えた問題をその場で撮影し、単語帳に登録できたらという発想

Swift3で作成

動画(Twitter) 

[ges-sa]

New Post has been published on https://ges-sa.com/acer-swift-3/

Acer Swift 3

[vc_row][vc_column][vc_column_text]

“Empowered Performance: Choose a laptop that lets you stay active and on the move—combining speed, efficiency and power, all in one device.” – Acer

For this review I received the Acer Swift 3 (SF314-52). Let’s see what makes this little ultra-book so cool.

Design-wise the Swift 3 looks absolutely amazing! From the brushed aluminium exterior to the polished bevelled edges. Complimenting this industrial look is the glossy Gorilla Glass screen. The Swift 3 has no beaming lights trying to impress you, other than the backlit keyboard you wouldn’t even know it’s on. The Swift 3 would not look out of place in any corporate boardroom next to its much pricier competitors. But let us not start comparing fruit…

The Screen is glossy Gorilla Glass, which to some might be an issue, but I quite like it. It gives the Swift 3 a classy appearance, yes reflections and dust might be an issue, but as with everything in life, you have to choose your battles. The panel is nice and bright and comparing it to my monster gaming laptop, it measured up pretty well.

Acer offers the Swift 3 in various hardware levels, I received the Core i7-7500U processor with 8 GB of DDR4 RAM, two SSDs and an Nvidia MX150 dedicated graphics chip with 2 GB of GDDR5 memory. Performance wise I cannot fault the Swift 3, it even allowing me to try to odd game or two without any issues.

The keyboard is nice and compact, some might call it small, but I found it more than ample considering that this is a 14″ laptop. The keys are backlit and can be adjusted for various levels of illumination. The trackpad was nice and easy to use and very responsive.

The typing surface also includes a fingerprint reader. Initially I was weary of this feature because fingerprint readers from back in the day felt slow and archaic. I am pleased to say that the one included with the Swift 3 is sharp and instant and makes using Windows Hello a pleasure.

Probably the most impressive feature of the Swift 3 is how they managed to squeeze a battery in that small space that can last a claimed 10 hours. Obviously, I jumped at the opportunity to test this claimed figure of 10 hours at various stages of performance.

All tests were performed with Wi-Fi on as I was connected to the internet all the time.

Light browsing, YouTube and responding to mails – 7 hours

Playing FHD movies using the laptop speakers – 10 hours

Gaming – 2 hours

I could not get enough of the Acer Swift 3. With its sharp design and awe-inspiring features. I would recommend it to anyone in the market for a compact ultra-book that can run a full day on a single charge.

[/vc_column_text][vc_gallery type=”image_grid” images=”29833,29834,29835,29836,29837,29838,29839,29840″][/vc_column][/vc_row][vc_row][vc_column width=”1/2″][vc_column_text]

Likes

[/vc_column_text][vc_column_text]

Super light weight

Sharp design elements in a classy package

Incredible battery life

[/vc_column_text][vc_column_text]

Dislikes

[/vc_column_text][vc_column_text]

Glossy screen prone to marks and dust

Keyboard might be a little small for some, but please keep in mind that this is a 14″ ultra portable laptop

[/vc_column_text][/vc_column][vc_column width=”1/2″][vc_column_text]

Hardware

[/vc_column_text][vc_column_text]

Screen: 14.0 inch, 1920 x 1080 px, IPS, non-touch, glossy

Processor: Intel Skylake Core i7-7500U CPU

Video: Intel HD 620 + Nvidia MX150 2GB DDR5 (optional)

Memory: 8 GB LPDDR3

Storage: 128 M.2 SATA SSD (80 mm) + 512 GB SSD (2.5″ bay)

Connectivity: Wireless AC (Intel AC 7265), Bluetooth 4.1

Ports: 2x USB 3.0 and 1 x USB 2.0, HDMI, card-reader, 3.5mm, Kensington lock

Battery: 48 Wh, 65W charger

OS: Windows 10

Size: 338 mm (w) x 234 mm (d) x 18 mm (h)

Weight: 1.74 kg

Extras: backlit keyboard, HD webcam, fingerprint reader

[/vc_column_text][/vc_column][/vc_row]

[georgioupanayiotis]

Make Query URL using swift 3

Some times we need to extract some data or get the specific key data from URL. In order to achieve that we need to break the whole url string in “&” and we have to store data as  array in a variable. After that we have to make search so doing this , is taking more time and more complexity. The post will show a simple and easy way to Make Query URL using swift 3. (more…)

View On WordPress

[iosdevelopersfan]

Using Advanced iOS Frameworks and Techniques with Swift 3 ☞ http://deal.thegeeknews.net/p/SyZb3eefl?utm_source=3

#IOS

[for-the-user]

NSNotificationCenter

Create a new file:

NSNotificationCenterKeys.swift

Specify one or more unique notification keys inside it:

let someNotificationKey = "com.someGroovyKey.specialNotificationKey"

Post a notification to NSNotificationCenter.default, identifying a key you have put in NSNotificationCenterKeys.swift

class FirstViewController: UIViewController { @IBAction func notify() { //Swift 3 NotificationCenter.default.post(name: Notification.Name(rawValue: someNotificationKey), object: self) // Swift 2 NSNotificationCenter.defaultCenter().postNotificationName(someNotificationKey, object: nil) } }

Set up one or more class or struct instances to be listeners, or more properly, observers of a particular notification. Such an observer will be able to tell that it’s “heard” the notification, because it will be “listening for” a notification that uses the same key.

class SecondViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() // Swift 3 NotificationCenter.default.addObserver(self, selector: #selector(SecondViewController.actOnSpecialNotification), name: NSNotification.Name(rawValue: someNotificationKey), object: nil) // Swift 2 NSNotificationCenter.defaultCenter().addObserver(self, selector: #selector(SecondViewController.actOnNotification), name: someNotificationKey, object: nil) } }

With no posts to the notification center on that station, tuning in will do no good. Likewise, posting a notification but having no listeners accomplishes nothing. when signing up to be an observer, the instance must also specify the name of a function that will be called upon receipt of the notification it’s listening for.

class SecondViewController: UIViewController { @IBOutlet weak var notificationLabel: UILabel! func actOnSpecialNotification() { self.notificationLabel.text = "I heard the notification!" } }

One final requirement for working with NSNotificationCenter is to remove an observer when it no longer needs to listen for notifications. We should unregister as soon as we don’t need to receive notifications anymore.

deinit { // Swift 3 NSNotificationCenter.default.removeObserver(self) // Swift 2 NSNotificationCenter.defaultCenter().removeObserver(self) }

[for-the-user]

NSUserDefaults

One method we could use is NSUserDefaults. It is best when used for little bits of information like user preferences, but not for larger things like UIImages.

NSUserDefaults is read and written atomically. This means when you write something to it, the whole thing needs to be written again. And when you read one key from it, it reads the whole thing and presents just the key you requested. This is good for making sure the data is read and written correctly, but might effect performance if the amount of data in NSUserDefaults is large. It is cached after the initial app load, so subsequent reads should be quite fast, but the initial one could be slow.

NSUserDefaults is like a Property List or plist that saves stuff to the iOS defaults system. There are six data types it can store:

NSData NSString NSNumber UInt Int Float Double Bool NSDate NSArray NSDictionary

Initialising NSUserDefaults:

public let defaults = NSUserDefaults.standardUserDefaults()

Writing to NSUserDefaults:

defaults.setBool(value: Bool, forKey defaultName: String) defaults.setInteger(value: Int, forKey defaultName: String) defaults.setFloat(value: Float, forKey defaultName: String) defaults.setDouble(value: Double, forKey defaultName: String) defaults.setObject(value: AnyObject?, forKey defaultName: String) defaults.setURL(url: NSURL?, forKey defaultName: String) e.g. defaults.setBool(true, forKey: "myGroovyKey") defaults.setObject("myGroovyValue", forKey: "myGroovyKey")

The limit for how much data can be stored in NSUserDefaults is the maximum file size for iOS (logically), which is currently 4GB. But for large amounts of data storage, a good idea might be to use something else like core data.

Reading from NSUserDefaults:

defaults.boolForKey("myGroovyKey") defaults.integerForKey("myGroovyKey") defaults.floatForKey("myGroovyKey") defaults.doubleForKey("myGroovyKey") defaults.objectForKey("myGroovyKey") defaults.URLForKey("myGroovyKey") defaults.dataForKey("myGroovyKey") defaults.stringForKey("myGroovyKey") defaults.stringArrayForKey("myGroovyKey") defaults.arrayForKey("myGroovyKey") defaults.dictionaryForKey("myGroovyKey") e.g. if (defaults.boolForKey("myGroovyKey")) == true { do something awesome }

If you try to read a key and it does not exist it will return nil.