perlguy99

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<array/>
</plist>

perlguy99

Easily fix SwiftUI Previews

100 Days of SwiftUI

perlguy99

//  ImageSaver.swift
//
//  Created by Brent Michalski on 11/30/19.
//  Copyright © 2019 Brent Michalski. All rights reserved.
//

import UIKit

class ImageSaver: NSObject {
    var successHandler: (() -> Void)?

perlguy99

//
//  KeyboardAvoiding+ViewModifier.swift
//
//  Created by Michalski (US), James B on 11/27/19.
//  Copyright © 2019 Brent Michalski. All rights reserved.
//

import SwiftUI
import Combine

perlguy99

//
//  DismissingKeyboard+ViewModifier.swift
//
//  Created by Michalski (US), James B on 11/27/19.
//  Copyright © 2019 Brent Michalski. All rights reserved.
//

import SwiftUI

struct DismissingKeyboard: ViewModifier {

perlguy99

//
//  ImagePicker.swift
//
//  Created by Brent Michalski on 11/25/19.
//  Copyright © 2019 Perlguy, Inc. All rights reserved.
//

import SwiftUI

struct ImagePicker: UIViewControllerRepresentable {

perlguy99

SwiftUI Coordinators

BEST place to learn, in detail is:

SwiftUI in 100 Days - Coordinators

perlguy99

Swift Git Ignore

From https://github.com/github/gitignore/blob/master/Swift.gitignore

# Xcode
#
# gitignore contributors: remember to update Global/Xcode.gitignore, Objective-C.gitignore & Swift.gitignore

## User settings
xcuserdata/

perlguy99

SwiftUI

AnyView vs Group: type erasure in practice

SwiftUI in 100 Days

Key Points

• Type erasure is the process of hiding the underlying type of some data.
  • This is used often in Swift: we have type erasing wrappers such as AnyHashable and AnySequence, and all they do is act as shells that forward on their operations to whatever they contain, without revealing what the contents are to anything externally.

perlguy99

Core Data Relationships and SwiftUI

From 100 Days of SwiftUI

For Core Data entities to track candy bars and their contries of origin...

Relationships come in four forms:

• A one to one relationship means that one object in an entity links to exactly one object in another entity. In our example, this would mean that each type of candy has one country of origin, and each country could make only one type of candy.
• A one to many relationship means that one object in an entity links to many objects in another entity. In our example, this would mean that one type of candy could have been introduced simultaneously in many countries, but that each country still could only make one type of candy.
• A many to one relationship means that many objects in an entity link to one object in another entity. In our example, this would mean that each type of candy has one country of origin, and