playgroundbook 0.6.0 → 1.0.0

data/.ruby-version

@@ -1 +0,0 @@
-ruby-2.1.1

data/Changelog.md

@@ -1,37 +0,0 @@
-# Current Master
-
-# 0.6.0
-
-- Adds basic support for Swift Package Manager dependencies. See [#50](https://github.com/playgroundbooks/playgroundbook/pull/50).
-
-# 0.5.0
-
-- Embeds images inside the local Playground when converting from markdown. See [#30](https://github.com/ashfurrow/playgroundbook/pull/30).
-
-# 0.4.0
-
-- Support converting a random Markdown file into a playground. See [#29](https://github.com/ashfurrow/playgroundbook/pull/29).
-
-
-# 0.3.0
-
-- Glossary support. See [#18](https://github.com/ashfurrow/playgroundbook/issues/18).
-- Removes newlines surrounding markdown blocks. See [#20](https://github.com/ashfurrow/playgroundbook/issues/20).
-
-# 0.2.1
-
-- Support for cover images. See [#16](https://github.com/ashfurrow/playgroundbook/issues/16).
-
-# 0.2.0
-
-- Book rendering.
-- Book linting moved to subcommand.
-
-# 0.1.0
-
-- Adds support for linting manifest file optional values. See [#3](https://github.com/ashfurrow/playground-book-lint/issues/3). - @rpowelll
-- Adds support for playground cutscene linting. See [#9](https://github.com/ashfurrow/playground-book-lint/issues/9). - @rpowelll
-
-# 0.0.1
-
-- Initial release.

data/CodeOfConduct.md

@@ -1,50 +0,0 @@
-# Contributor Code of Conduct
-
-As contributors and maintainers of this project, and in the interest of  
-fostering an open and welcoming community, we pledge to respect all people who  
-contribute through reporting issues, posting feature requests, updating  
-documentation, submitting pull requests or patches, and other activities.
-
-We are committed to making participation in this project a harassment-free  
-experience for everyone, regardless of level of experience, gender, gender  
-identity and expression, sexual orientation, disability, personal appearance,  
-body size, race, ethnicity, age, religion, or nationality.
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery  
-* Personal attacks  
-* Trolling or insulting/derogatory comments  
-* Public or private harassment  
-* Publishing other's private information, such as physical or electronic  
-  addresses, without explicit permission  
-* Other unethical or unprofessional conduct
-
-Project maintainers have the right and responsibility to remove, edit, or  
-reject comments, commits, code, wiki edits, issues, and other contributions  
-that are not aligned to this Code of Conduct, or to ban temporarily or  
-permanently any contributor for other behaviors that they deem inappropriate,  
-threatening, offensive, or harmful.
-
-By adopting this Code of Conduct, project maintainers commit themselves to  
-fairly and consistently applying these principles to every aspect of managing  
-this project. Project maintainers who do not follow or enforce the Code of  
-Conduct may be permanently removed from the project team.
-
-This code of conduct applies both within project spaces and in public spaces  
-when an individual is representing the project or its community.
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be  
-reported by contacting a project maintainer at [ash@ashfurrow.com](mailto:ash@ashfurrow.com) or [orta.therox@gmail.com](mailto:orta.therox@gmail.com). All  
-complaints will be reviewed and investigated and will result in a response that  
-is deemed necessary and appropriate to the circumstances. Maintainers are  
-obligated to maintain confidentiality with regard to the reporter of an  
-incident.  
-
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],  
-version 1.3.0, available at
-[http://contributor-covenant.org/version/1/3/0/][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/3/0/

data/Community.md

@@ -1,52 +0,0 @@
-# Community Continuity Guidelines v2.0.0
-
-As the creators, and maintainers of this project, we want to ensure that the project lives and continues to grow. Not blocked by any singular person's computer time. One of the simplest ways of doing this is by encouraging a larger set of shallow contributors. Through this, we hope to mitigate the problems of a project that needs updates but there's no-one who has the power to do so.
-
-#### Ownership
-
-If you get a merged Pull Request, regardless of content (typos, code, doc fixes), then you're eligible for push access to this organization. This is checked for on pull request merges and an invite to the organization is sent via GitHub.
-
-Offhand, it's easy to imagine that this would make code quality suffer, but in reality it offers fresh perspectives to the codebase and encourages ownership from people who are depending on the project. If you are building a project that relies on this codebase, then you probably have the skills to improve it and offer valuable feedback.
-
-Everyone comes in with their own perspective on what a project could/should look like, and encouraging discussion can help expose good ideas sooner.
-
-#### Why do we give out push access?
-
-It can be overwhelming to offered the chance to wipe the source code for a project. Don't worry, we don't let you push to master. All code is peer-reviewed, and we have the convention that someone other than the submitter should merge non-trivial pull requests.
-
-As an organization contributor, you can merge other people's pull requests, or other contributors can merge yours. You won't be assigned a pull request, but you're welcome to jump in and take a code review on topics that interest you.
-
-This project is not continuously deployed, there is space for debate after review too. Offering everyone the chance to revert, or make an amending pull request. If it feels right, merge.
-
-#### How can we help you get comfortable contributing?
-
-It's normal for a first pull request to be a potential fix for a problem, and moving on from there to helping the project's direction can be difficult. We try to help contributors cross that barrier by offering good first step issues. These issues can be fixed without feeling like you're stepping on toes. Ideally, these are non-critical issues that are well defined. They will be purposely avoided by mature contributors to the project. To make space for others.
-
-We aim to keep all project discussion inside GitHub issues. This is to make sure valuable discussion is accessible via search. If you have questions about how to use the library, or how the project is running - GitHub issues are the goto tool for this project.
-
-#### Our expectations on you as a contributor
-
-To quote [@alloy](https://github.com/alloy) from [this issue](https://github.com/Moya/Moya/issues/135):
-
-> Don't ever feel bad for not contributing to open source.
-
-We want contributors to provide ideas, keep the ship shipping and to take some of the load from others. It is non-obligatory; we’re here to get things done in an enjoyable way. :trophy:
-
-The fact that you'll have push access will allow you to:
-
-- Avoid having to fork the project if you want to submit other pull requests as you'll be able to create branches directly on the project.
-- Help triage issues, merge pull requests.
-- Pick up the project if other maintainers move their focus elsewhere.
-
-It's up to you to use those superpowers or not though 😉
-
-If someone submits a pull request that's not perfect, and you are reviewing, it's better to think about the PR's motivation rather than the specific implementation. Having braces on the wrong line should not be a blocker. Though we do want to keep test coverage high, we will work with you to figure that out together.
-
-#### What about if you have problems that cannot be discussed in a public issue?
-
-Both [Ash Furrow](https://github.com/ashfurrow) and [Orta Therox](https://github.com/orta) have contactable emails on their GitHub profiles, and are happy to talk about any problems.
-
-#### Where can I get more info about this document?
-
-The original source of this document can be found at https://github.com/moya/contributors.
-

data/Gemfile

@@ -1,13 +0,0 @@
-source "https://rubygems.org"
-
-gem "rake"
-gem "guard-rspec"
-gem "mocha"
-gem "bacon"
-gem "mocha-on-bacon"
-gem "prettybacon"
-gem "fakefs"
-gem "rubocop", "~> 0.41.2", require: false
-
-require "pp" # https://github.com/defunkt/fakefs/issues/99
-gemspec

data/Gemfile.lock

@@ -1,102 +0,0 @@
-PATH
-  remote: .
-  specs:
-    playgroundbook (0.4.0)
-      colored (~> 1.2)
-      cork (~> 0.1)
-      plist (~> 3.2)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    ast (2.3.0)
-    bacon (1.2.0)
-    coderay (1.1.1)
-    colored (1.2)
-    cork (0.2.0)
-      colored (~> 1.2)
-    diff-lcs (1.2.5)
-    fakefs (0.9.0)
-    ffi (1.9.10)
-    formatador (0.2.5)
-    guard (2.14.0)
-      formatador (>= 0.2.4)
-      listen (>= 2.7, < 4.0)
-      lumberjack (~> 1.0)
-      nenv (~> 0.1)
-      notiffany (~> 0.0)
-      pry (>= 0.9.12)
-      shellany (~> 0.0)
-      thor (>= 0.18.1)
-    guard-compat (1.2.1)
-    guard-rspec (4.7.2)
-      guard (~> 2.1)
-      guard-compat (~> 1.1)
-      rspec (>= 2.99.0, < 4.0)
-    listen (3.0.7)
-      rb-fsevent (>= 0.9.3)
-      rb-inotify (>= 0.9.7)
-    lumberjack (1.0.10)
-    metaclass (0.0.4)
-    method_source (0.8.2)
-    mocha (1.1.0)
-      metaclass (~> 0.0.1)
-    mocha-on-bacon (0.2.2)
-      mocha (>= 0.13.0)
-    nenv (0.3.0)
-    notiffany (0.1.0)
-      nenv (~> 0.1)
-      shellany (~> 0.0)
-    parser (2.3.1.2)
-      ast (~> 2.2)
-    plist (3.2.0)
-    powerpack (0.1.1)
-    prettybacon (0.0.2)
-      bacon (~> 1.2)
-    pry (0.10.3)
-      coderay (~> 1.1.0)
-      method_source (~> 0.8.1)
-      slop (~> 3.4)
-    rainbow (2.1.0)
-    rake (11.2.2)
-    rb-fsevent (0.9.7)
-    rb-inotify (0.9.7)
-      ffi (>= 0.5.0)
-    rspec (3.5.0)
-      rspec-core (~> 3.5.0)
-      rspec-expectations (~> 3.5.0)
-      rspec-mocks (~> 3.5.0)
-    rspec-core (3.5.1)
-      rspec-support (~> 3.5.0)
-    rspec-expectations (3.5.0)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.5.0)
-    rspec-mocks (3.5.0)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.5.0)
-    rspec-support (3.5.0)
-    rubocop (0.41.2)
-      parser (>= 2.3.1.1, < 3.0)
-      powerpack (~> 0.1)
-      rainbow (>= 1.99.1, < 3.0)
-      ruby-progressbar (~> 1.7)
-      unicode-display_width (~> 1.0, >= 1.0.1)
-    ruby-progressbar (1.8.1)
-    shellany (0.0.1)
-    slop (3.6.0)
-    thor (0.19.1)
-    unicode-display_width (1.1.0)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  bacon
-  fakefs
-  guard-rspec
-  mocha
-  mocha-on-bacon
-  playgroundbook!
-  prettybacon
-  rake
-  rubocop (~> 0.41.2)

data/Guardfile

@@ -1,14 +0,0 @@
-guard :rspec, cmd: "bundle exec rspec" do
-  require "guard/rspec/dsl"
-  dsl = Guard::RSpec::Dsl.new(self)
-
-  # RSpec files
-  rspec = dsl.rspec
-  watch(rspec.spec_helper) { rspec.spec_dir }
-  watch(rspec.spec_support) { rspec.spec_dir }
-  watch(rspec.spec_files)
-
-  # Ruby files
-  ruby = dsl.ruby
-  dsl.watch_spec_files_for(ruby.lib_files)
-end

data/Rakefile

@@ -1,8 +0,0 @@
-require "bundler/gem_tasks"
-require "rspec/core/rake_task"
-require "rubocop/rake_task"
-
-RSpec::Core::RakeTask.new(:spec)
-RuboCop::RakeTask.new
-
-task default: :spec

data/playgroundbook.gemspec

@@ -1,21 +0,0 @@
-# coding: utf-8
-lib = File.expand_path("../lib", __FILE__)
-$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-require "version"
-
-Gem::Specification.new do |s|
-  s.name        = "playgroundbook"
-  s.version     = Playgroundbook::VERSION
-  s.licenses    = ["MIT"]
-  s.summary     = "Lints/renders Swift Playground books."
-  s.description	= "Tooks for Swift Playground books on iOS, a renderer and a linter."
-  s.authors     = ["Ash Furrow"]
-  s.homepage	= "https://github.com/ashfurrow/playground-book-lint"
-  s.email       = "ash@ashfurrow.com"
-  s.files       = `git ls-files`.split($INPUT_RECORD_SEPARATOR)
-  s.require_paths = ["lib"]
-  s.executables = ["playgroundbook"]
-  s.add_runtime_dependency "plist", "~> 3.2"
-  s.add_runtime_dependency "colored", "~> 1.2"
-  s.add_runtime_dependency "cork", "~> 0.1"
-end

data/spec/fixtures/Starter.playgroundbook/Contents/Chapters/Chapter1.playgroundchapter/Manifest.plist

@@ -1,15 +0,0 @@
-<?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">
-<dict>
-	<key>Version</key>
-	<string>1.0</string>
-	<key>Name</key>
-	<string>Sample Chapter</string>
-	<key>Pages</key>
-	<array>
-		<string>Page1.playgroundpage</string>
-		<string>Page2.playgroundpage</string>
-	</array>
-</dict>
-</plist>

data/spec/fixtures/Starter.playgroundbook/Contents/Chapters/Chapter1.playgroundchapter/Pages/Page1.playgroundpage/Contents.swift

@@ -1,8 +0,0 @@
-/*
- Copyright (C) 2016 Apple Inc. All Rights Reserved.
- See LICENSE.txt for this sample’s licensing information.
- 
- This is an example playground page.
-*/
-
-print("Hello World")

data/spec/fixtures/Starter.playgroundbook/Contents/Chapters/Chapter1.playgroundchapter/Pages/Page1.playgroundpage/Manifest.plist

@@ -1,12 +0,0 @@
-<?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">
-<dict>
-	<key>Version</key>
-	<string>1.0</string>
-	<key>Name</key>
-	<string>Example Page</string>
-	<key>LiveViewMode</key>
-	<string>HiddenByDefault</string>
-</dict>
-</plist>

data/spec/fixtures/Starter.playgroundbook/Contents/Chapters/Chapter1.playgroundchapter/Pages/Page2.playgroundpage/Contents.swift

@@ -1,8 +0,0 @@
-/*
- Copyright (C) 2016 Apple Inc. All Rights Reserved.
- See LICENSE.txt for this sample’s licensing information.
- 
- This is a second example page.
-*/
-
-print("Hello World")

data/spec/fixtures/Starter.playgroundbook/Contents/Chapters/Chapter1.playgroundchapter/Pages/Page2.playgroundpage/Manifest.plist

@@ -1,12 +0,0 @@
-<?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">
-<dict>
-	<key>Version</key>
-	<string>1.0</string>
-	<key>Name</key>
-	<string>Second Example Page</string>
-	<key>LiveViewMode</key>
-	<string>HiddenByDefault</string>
-</dict>
-</plist>

data/spec/fixtures/Starter.playgroundbook/Contents/Manifest.plist

@@ -1,20 +0,0 @@
-<?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">
-<dict>
-	<key>Version</key>
-	<string>1.0</string>
-	<key>ContentVersion</key>
-	<string>1.0</string>
-	<key>Name</key>
-	<string>Starter</string>
-	<key>ContentIdentifier</key>
-	<string>com.example.apple-samplecode.Starter</string>
-	<key>DeploymentTarget</key>
-	<string>ios10.0</string>
-	<key>Chapters</key>
-	<array>
-		<string>Chapter1.playgroundchapter</string>
-	</array>
-</dict>
-</plist>

data/spec/fixtures/book.yml

@@ -1,6 +0,0 @@
-name: Testing book
-identifier: com.ashfurrow.example
-resources: assets
-cover: file.jpeg
-chapters:
-  - name: test_chapter

data/spec/fixtures/test_chapter.playground/Contents.swift

@@ -1,17 +0,0 @@
-import UIKit
-
-public var str = "Hello, playground"
-
-public func sharedFunc() {
-  print("This should be accessible to all pages.")
-}
-
-//// Page 1
-
-str = "Yo, it's page 1."
-sharedFunc()
-
-//// Page 2
-
-sharedFunc()
-str = "Page 2 awww yeah."

data/spec/fixtures/test_chapter.playground/contents.xcplayground

@@ -1,4 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
-<playground version='5.0' target-platform='ios'>
-    <timeline fileName='timeline.xctimeline'/>
-</playground>

data/spec/fixtures/wrapper/destination/swift_at_artsy_1.swift

@@ -1,200 +0,0 @@
-import Foundation
-/*:
-(Note: a screen recording of a presentation of this material is [available on YouTube](https://github.com/artsy/Swift-at-Artsy/tree/master/Beginners/Lesson%20One).)
-
-Hey! So we're going to be looking at Swift from the perspective of learning programming. This means you get to ask awkward questions and I struggle to verbalise concepts that are the programming equivalent of muscle memory. It'll be fun!
-
-To start off we need to get to a point where we can write any code. We're going to assume that you already have a copy of Xcode 7 installed. With that, let's get started!
-
-Open Xcode and you'll get this Welcome dialogue. 
-
-![Xcode Welcome Screen](img/welcome.png)
-
-We'll be using _playgrounds_ to learn Swift. Click "Get started with a playground", give it a name, and make sure the platform is set to **OS X**. 
-
-![Creating a new playground](img/newplayground.png)
-
-Awesome. Xcode will create an open the playground for you. It'll look something like this. 
-
-![Empty Playground](img/emptyplayground.png)
-
-The large pane on the left is where we're going to write code. On the right is where the results of our code are displayed. You can see that there's already one line of code written for us, `var str = "Hello, playground"`, and the results pane says `"Hello, playground"`. Neat. 
-
-
-Normally for things I work with, the code we are writing gets transformed from something we, as humans, kind-of understand to something a machine understands via a compiler. Let's stick with the idea that it's basically a translator from human to machine. Normally its a big upfront conversion, for example Eigen can take 5 minutes to compile. 
-
-We're going to use Playgrounds, which is more like a back and forth conversation with the compiler, so it's much faster to write code and test things out. These are called REPLs.
-
-What this means is whatever you type will be run by Xcode and the results will be shown on the right. When Xcode is compiling code (whenever you change text), the top bar of the window will change to say "Running" and will show a little spinner. 
-
-Let's start by saying what _isn't_ code. You see the the first line, how it is greyed out? Well that's a comment. Comments are annotations in the code that are not ran by the compiler. We'll be using comments occasionally to skip bits of code, or to remind us what something is.
-
-OK let's write some code, let's try typing some things. 
-
-*/
-
-1 + 2
-
-1 / 2
-1.0 / 2.0
-
-"Hello, Artsy"
-/*:
-
-You can see the results in the results pane:
-
-![Results](img/results.png)
-
-In programming, we want to work with abstractions. So let's make our first variable. A variable holds a value that you can refer to later, you can name them (almost) whatever you want. 
-
-Variables are themselves an abstract concept, and it's normal for beginners to take time getting comfortable with them. In essence, a variable is a way to store something in a place that you can refer to later. There are a few good reasons to do this, but the most common one is that we need to refer to the same value more than once. 
-
-On an artist's Artsy page, we show their name more than once. It's useful to be able to store the artists name in a variable _once_ and then refer to that variable multiple times to show the user an artist's page.
-
-We're going to make a simple calculator with 3  variables. What I'd like to do is define a variable called `a` and `b` then add them together to make `c`. This is a simple example, but it's about foundations.
-
-*/
-
-var a = 2
-var b = 3
-
-var c = a + b
-/*:
-
-In this case, you can see that we're referring back to `a` and `b` as variables, instead of the numbers `2` and `3`. This is a simple example, and with more experience, you'll get more comfortable. 
-
-Variables all have a _type_. Some variables are numbers, and some are strings, and some are other things, too! Numbers are often `Int`, or an integer (basically a round number: 1, 2, 3, -500, 401). Swift is a **strongly-typed language**, which means that types matter a lot. Swift won't let you confuse one type for another. Even though we haven't _told_ Swift what the type of our variables are, the compiler figures it out automatically. 
-
-In Swift, `:` specifies a type. So the following two lines are equivalent.
-
-*/
-
-var myString = "Hello, Artsy"
-var myString: String = "Hello, Artsy"
-/*:
-
-In this case we're dealing with a collection of letters, that combined, we call a string. This is common terminology in most programming languages, think of it as a string of letters.
-
-*/
-
-var myString: String = 1
-/*:
-
-Swift will complain and say that `'Int' is not convertible to 'String'`. This is Swift's compile-time type checking. It prevents bugs from happening in apps at runtime by giving you errors before-hand. Swift's primary goal is safety against crashes in apps. 
-
-When we're writing code, very often we want to print out some useful information for someone to read. We're going to use this to show that some of our code is running. So lets add a print statement saying what the value of `c` is:
-
-*/
-
-print(c)
-/*: 
-
-With `print` working, we can start doing some logic. We want to start checking how big our `c` is, and just like in English, we'll use an `if` statement:
-
-*/
-
-if c > 6 {
-    print("Pretty big c you got there.")
-}
-/*:
-
-Let's unpack what we're seeing here. `if [something]` - what's happening here is that the bit after the `if` is checking to see if `c` is greater than the number (`Int`) `6`. If it is, then it will run the code inside the braces. 
-
-`if` statements are fundamentally about doing some code only under certain circumstances. For example, Artsy only shows the "Inquire on Artwork" button **if** that artwork can be inquired upon. There are lots of different places in our code where it's useful to do something only if a condition is met.
-
-It is common to use a left margin / indentation to indicate that something is inside a braced section. It's not enforced though.
-
-*/
-
-if c > 6 {
-            print("Pretty big c you got there.")
-}
-/*:
-
-*/
-
-if c > 6 { 
-print("Pretty big c you got there.") 
-}
-/*:
-
-*/
-
-if c > 6 { print("Pretty big c you got there.") }
-/*:
-
-We've got one more thing to go over, and that is loops. Loops repeat a section of code. Computers are really good at doing the same thing over and over, and loops are how programmers tell computers to do that. Repeating code is really useful in the Artsy's artwork pages, specifically in the related artworks section. As programmers, we tell the computer how to add _one_ artwork to the page, and then tell the computer to do that over and over for all the related artworks.
-
-Let's make a nice simple loop, one that reads like English. For _a_ number in _zero to c_. 
-
-*/
-
-for number in 0...c {
-    print("hi")
-}
-/*:
-
-It has the same behavior that we saw in the `if` example. It will run the thing inside the braces as many times as the value of `c`. Each time it will print out `"hi"`. I think we can expand on this one little bit. The word `number` here is actually a variable, let's make it sound all mathematical and call it `x` instead.
-
-*/
-
-for x in 0...c {
-    print("hi")
-}
-/*:
-
-Now we know it's a variable, lets print it!
-
-*/
-
-for x in 0...c {
-    print(x)
-}
-/*:
-
-For loops, often just called "loops", are foundational to programming. In this example above, we've looped over all the numbers from `0` to `c`, but you can loop over other things, too. Say we're making an app at Artsy that shows a bunch of artworks – we might loop over all the artworks to show them on the screen. 
-
-If you hit the little triangle in the bottom left you can see the printed output!
-
-----------------
-
-So let's recap.
-
-* We've learned a little bit about variables, they are named values that make it easier for us to think about what something represents vs what it is.
-
-* Then we looked at some `String`s, and showed that you can't change something from a string to a number once you've start using it as a `String`,
-
-* We then printed some information.
-
-* After that we looked at adding an `if` statement to add some logic to our code.
-
-* Finally we wrapped up with a `for in` loop.
-
-If you're keen, feel free to keep playing in the playground. Try changing things in the loops to see what happens. Is it what you expected to happen? Why or why not?
-
-What do you think this code would do?
-
-*/
-
-for number in 0...15 {
-	if number > 5 {
-		print("This is greater than five")
-	}
-}
-/*:
-
-What about this?
-
-*/
-
-for number in 0...15 {
-	if number > 5 {
-		print("This is greater than five")
-	} else {
-		print("This is less than five")
-	}
-}
-/*:
-
-You can also look at the free Stanford Swift Course: https://www.youtube.com/playlist?list=PLxwBNxx9j4PW4sY-wwBwQos3G6Kn3x6xP
-*/