macOS Development Fundamentals

Course Overview
Hi everyone, my name is Corissa Jesseman, and welcome to my course, macOS Development Fundamentals. I'm an independent macOS and iOS software developer. In the past few years, macOS has experienced a surge in popularity. In this course, we're going to learn how to build a macOS application from start to finish. Some of the major topics we will cover include designing the windows and view controllers, laying out the controls using Auto Layout, storing data using Core Data, working with table and collection views, and releasing the app to the Apple App Store. By the end of this course, you will know how to build a fully-functional macOS app and be ready to develop your own app. Before beginning this course, you should be familiar with Swift. I hope you'll join me on this journey to learn macOS with the macOS Development Fundamentals course at Pluralsight.

Introduction to Course and Xcode
Hi, and welcome to macOS Development Fundamentals. I'm Corissa Jesseman. Today we're going to learn about Xcode. We're going to start with a brief overview of what you will learn in this course, and then we will get into Xcode, going over the types of projects, the files in the project, and some of the useful features of Xcode. So, first let's go over what you will learn in this course. We're going to build three apps over the duration of the course. The majority of our time will be spent building a trip planning app. This is a fully functional app that we will use to learn about controls and view controllers, including the Split View Controller, Table View Controllers, and Collection View Controllers. And all of the data will be stored in core data. At the end of the course we're going to go through the process of submitting this app to the Apple App Store as well as releasing it independently. Next is our text editor app. It will allow the user to view and edit basic text files. We'll be building this app to learn about document-based applications. Last will be the factors calculator. We'll be using this app to learn how to work with command line tools. So, those are the three apps that we're going to build. One thing we will be referencing a lot during this course is the macOS Human Interface Guidelines. These are guidelines released by Apple with recommendations as to how your app should be designed. These are the best practices for building macOS apps, and by following them your app will have the same look and feel the users are used to. And don't feel like they're restrictive. You can follow the guidelines and still have a unique user experience.

Creating Other Types of Applications
Hi and welcome to MacOS development fundamentals. I'm Corissa Jesseman. Today we're going to learn how to create other types of applications. So far we've been focused on single-window applications. But now we're going to look at two other types of common apps: Command line and document-based. First, let's discuss Command Line Tools. Command line tools run from Terminal. The difference between Command Line Tools and what we've been working with is the user interface. There are no windows, no controls. You get input using command-line parameters, and you output information just by printing basic text, which actually makes command-line apps a lot simpler. There are no storyboards, no autolayout constraints. You just command-line to arguments to get the parameters passed in. One thing to know is that the first argument is always to executable path. So to get the first real parameter, you want to look at the argument at index one. Also there are some standard formats for parameters. Options are usually indicated with either a single or double hyphen. In general single hyphens are used for single letter or abbreviated parameters, and double hyphens are used for full words. So in this example you would use a single hyphen H or double hyphen help, and both would perform the same function. Most times apps have support for both the short and long forms, allowing the user to decide which version they prefer to use. An output is very simple, just call print your message.