#browser #swift #WebAssembly
WebAssembly: Swift, C#, Java and Oxygene in the Browser
by Marc Hoffman: Over the past few weekly builds, we've been rolling out support for WebAssembly, our next major compiler target for Elements.
Built upon our Island platform, this now allows you to write Oxygene, C#, Swift or Java Language code that runs in the WebBrowser parallel to and interacting with JavaScript and the browser document model.
How Does This Work?
Elements compiles your code to native WebAssemly byte code in a .wasm file that you can deploy as part of your website and load into your page just like you would regular JavaScript.
From within your WebAssembly code, you have full access to all the capabilities of your preferred language (Oxygene, C#, Swift or Java, and you can also mix them file-by-file, as always). Of course you also can use our low-level "Island RTL" shared between all Island-based sub-platforms, and our cross-platform Elements RTL, Swift Base Library (for Swift users) and even the "Delphi RTL" compatibility library are available we well.
With a few restrictions (for example, WebAssmebly is currently single-threaded, so certain threading APIs are not available; also – for obvious reasons – there is no direct file system access), you can write Elements code as you would on any other platform (and also share code with other platforms, where desired).
You also have direct access to browser objects, the DOM, and of course you can interact with and expose classes and methods to the JavaScript that runs in the web page (or in separate .js files).

#swift #optional #extension
Useful Optional Extensions
by Benedikt Terhechte: Optionals are a staple of Swift. I guess everybody will agree that they are a huge boon insofar as they force us to properly handle edge cases. The Optional language feature alone removes a whole category of bugs from the development process.
However, the API surface of Swift's optional is rather limited

#ios #swift #NotificationCenter #removeObserver
Do you have to manually unregister block-based NotificationCenter observers?
by Ole Begemann: Yes, you still have to unregister block-based observations manually (as of iOS 11.2). The documentation for removeObserver(_:) is at least misleading if not wrong.
If you don’t unregister, the notification center will retain the observer block forever and keep invoking it for every incoming notification. Whether this will wreak havoc with your app depends on what you do in the block (and what objects the block has captured).
When you do the unregistering in deinit, you must make sure not to capture self in your observer block. If you do, your deinit will never get called because the block retains self (preventing its destruction) and the notification center holds a strong reference to the block. Your object will live forever.

#ios11 #swift #ARKit #tutorial ##SceneKit #physics
ARKit Tutorial: Understanding Physics by Launching a Rocketship
by Jayven N: Did that just move? Is that real? That’s augmented reality. Welcome back to the fourth installment of the ARKit tutorial series. In this tutorial, we will be looking at the basics of physics inside of ARKit. We shall launch a rocketship by the end of this tutorial then celebrate like it’s the 4th of July because we can. Let’s go!

#ios11 #swift #machine #learning #CoreML
How to Train a Core ML Model for an iOS App
by Doron Katz: In this tutorial, you will learn about how to apply machine learning algorithms to a set of training data, to create a trained model which will subsequently make predictions based on new input. All thanks to Apple’s new Core ML framework.

#Swift 4 #Language, A Complete Overview With #IOS 11 #CoreML #App

Swift 4 Language, A Complete Overview With IOS 11 CoreML App. This course will provide a foundation for basic and advanced swift concepts, not only to the swift but also to many other languages; As many of the topics covered will transcend to multiple…