Create Xcode Playgrounds for the Swift programming language with rich documentation generated from Markdown
Follow me on Twitter @jasonsandmeyer or watch this repo for updates!
Swift code is extracted from the Markdown with the same syntax used to specify languages for code blocks in GitHub-flavored Markdown. All other text is parsed normally as Markdown using marked.
# A Swift Tour Tradition suggests that the first program in a new language should print the words "Hello, world" on the screen. In Swift, this can be done in a single line: ```swift println("Hello, world!") ```
This tool requires Node.js. Download the installer from the Node.js website and follow the instructions.
In your Terminal, run the following command to install the Playground Builder:
$ npm install -g playground
That's it! You should now be able to use the
Usage: playground <paths>... [options]paths Markdown files(s), or directory containing Markdown files,from which to build the Playground(s).The Markdown file(s) must have one of these common Markdownfile extensions: .md .markdown .mdown .mkdn .mkdOptions:-d, --destination Directory in which to output the Playground(s);defaults to the current working directory-p, --platform Specifies which platform's frameworks can be importedin the Playground(s); only one platform can be choosen[options: ios, osx] [default: osx]-n, --noreset Don't allow edited code to be reset from the"Editor → Reset Playground" menu in Xcode-s, --stylesheet Path to custom stylesheet-v, --version Print "playground" version and exit
You can also import the Playground Builder as a Node.js module.
var playground = ;playground;playground;playground;
createFromFilesexpect a path to a Markdown file or directory containing Markdown files. An array of file and/or directory paths is also acceptable.
createFromStringexpects a string containing Markdown.
See the "Options" section below for available options.
Function to be called once all Playground files have been output. First argument is
err which contains an
Error, if any.
createFromString, specify a name for the playground. The name will be used for
the filename. (The
.playground extension is appended automatically.)
Path to directory in which to output the built Playground(s).
A Playground's code can be modified and saved. The Playground can be reset to its original code from the "Editor → Reset Playground" menu. This menu can be disabled for a Playground by setting this option to
Set the platform to
ios to be able to import each platform's respective frameworks.
Path to a custom stylesheet.
var playground = ;// Outputs `Introduction.playground` to current working directoryplayground;// Outputs `Variables.playground` to `/User/Jason/Playgrounds`playground;// outputs `Constants.playground` and `Closures.playground` to CWDplayground;// outputs playgrounds for Markdown files in `./playgrounds` directory,// then invokes callback functionplayground;
You may be wondering why I chose to use Node.js for this project.
I wrote this script with the intention of using it as part of a web-based CMS. It would be awesome to have downloadable playgrounds when I post Swift-related articles on my website, and a huge time-saver if they are generated automatically from the post's Markdown. Although this version already works very well from the Terminal, I'd love to one day rewrite it in Swift itself.
The MIT License
Copyright (c) 2014 Jason Sandmeyer
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.