Reduce to single framework target, configured with jdhealy/FABConfig.

• Reduce to single test target, also configured with jdhealy/FABConfig.
• Reduce to single scheme.
• Support additional platforms of tvOS and watchOS and corresponding simulators.
• Set CODE_SIGNING_REQUIRED to NO (through jdhealy/FABConfig).
  • Remove configuration CODE_SIGN_IDENTITY[sdk=iphoneos*] = "iPhone Developer".
  • Trust in Xcode 8+ automatic code signing defaults.
    • Code signing will usually still be required at the point of embedding PrettyColors in a code-signed bundle.
    • See https://github.com/jdhealy/FABConfig/pull/1 for more info.
• Set SWIFT_VERSION to 2.3, solely to prevent Xcode from offering the Swift Migrator.
  • No source migration was necessary; compatibility with Swift 2.2 remains.

• Add Xcode 8.3 and Xcode 9 jobs
• Remove redundant Xcode 8 and Xcode 8.1 jobs
• Remove redundant Swift 3.0 and Swift 3.0.1 jobs on Linux
• Explicit git submodule update --init --recursive is not needed anymore
• Submodules are not needed for SwiftPM

Getting the following error when trying to do pod install on latest Xcode 10.2

Installing PrettyColors 5.0.2

[!] Invalid `PrettyColors.podspec` file: undefined method `swift_versions=' for #<Pod::Specification name="PrettyColors">
Did you mean?  swift_version=
               swift_version.

 #  from /var/folders/0f/pbyp18ds4psf0d6_37twvfbc0000gn/T/d20190327-39339-1gjgqm1/PrettyColors.podspec:13
 #  -------------------------------------------
 #    spec.source_files = 'Source/**/*.{h,swift}'
 >    spec.swift_versions = ['3.0', '4.0', '4.2', '5.0']
 #    spec.requires_arc = true
 #  -------------------------------------------

It seems that SPM needs a version tag that isn't prefixed with "v" in order to work.

i.e. 4.0.0 not v4.0.0. Luckily there is nothing that prevents git from having both tags if you don't want to just switch. For the next release could you tag it this way?

swift build
Cloning https://github.com/jdhealy/PrettyColors.git
error: The dependency graph could not be satisfied. The package (https://github.com/jdhealy/PrettyColors.git) with version tag in range (4.0.0..<4.9223372036854775807.9223372036854775807) is not found. Found tags ([0.0.1, 0.0.2])

Thank you for useful library!

❓ Does PrettyColors outputs strings that are colored in Xcode console output?

I've tried using XcodeColors, which works well with manually inserted color codes. https://github.com/robbiehanson/XcodeColors but could not seem get it to recognize PrettyColors strings.

Escape code in resulting string: [fg64,64,192; works [33;22m does not

In all likelihood, Swift Package Manager will eventually no longer require this.

However, PrettyColors will soon be supporting too many non-Darwin versions of Swift to test manually, as was done previously.

Thankfully, Sourcery now provides tooling to generate LinuxMain.swift on macOS.

Ideally, this would be automated, but probably not worth the effort in the near future; pull requests with test changes will need vigilance in requiring LinuxMain.swift changes, should be easy enough to remember… 😅

Particular Areas of Interest

• Color.Wrap.add returns a new struct. This differs from the foreground and background methods which are mutating. I figure that adding a Parameter will be much more common than modifying a ColorType and the convenience of adding parameters outside of var variables makes this worth it. Thoughts?

• Ridiculous workaround Cannot downcast from 'Parameter' to non-@objc protocol type 'ColorType'

Hello. Thank you for PrettyColors. In this pull request I fixed the warning messages that appear when compiling PrettyColors in Xcode 11.6 / Swift 4. And also added some news tasks for Travis CI. I think I also fixed #25 in this pull request.

That's because the project's SWIFT_VERSION build setting is still 3.0, but Xcode 10.2 (Swift 5 compiler) drops support for Swift 3 language mode, so the setting must be changed to 4.0 at least.

Currently, this library supports Swift 3.x.

However, Xcode 10.2 drops supporting for Swift 3.x. So we can't build Carthage on Xcode 10.2 because of this library.

This PR make it dropping Swift 3.x and Xcode 8.x/9.x supporting.

CocoaPods and Carthage are awesome tools and make our life really easier, but there are some devs who still don't know how to use them.

It would be cool to add the Manual installation guide in your README.md. You can take a look at my iOS Readme Template to see how you can do it.