|Number of watchers on Github||128|
|Number of open issues||3|
|Average time to merge a PR||1 day|
|Open pull requests||4+|
|Closed pull requests||1+|
|Last commit||7 months ago|
|Repo Created||over 2 years ago|
|Repo Last Updated||7 months ago|
|Organization / Author||apple|
|Do you use swift-xcode-playground-support? Leave a review!|
|View open issues (3)|
|View swift-xcode-playground-support activity|
|View on github|
|Latest Open Source Launches|
Trendy new open source projects in your inbox! View examples
Welcome to Swift Xcode Playground Support!
The Xcode Playground Support project enables Xcode playgrounds to communicate their results in a displayable fashion, and to control some aspects of playground behavior. In order to use a custom build of Swift with Xcode the frameworks described below must be compiled with the new Swift compiler and included in a toolchain. Snapshots will include this project to deliver everything required. Just download, install, and select the toolchain to work with the corresponding Swift features in Xcode playgrounds.
The project contains these frameworks:
PlaygroundSupport. This framework defines API that may be explicitly referred to by playground code to communicate with Xcode. For example: this is typical for playgrounds that identify a particular view to display live for animation or interaction, and when playgrounds automatically move between pages when defined criteria are met. A legacy XCPlayground version is also provided for compatibility with older playgrounds.
PlaygroundLogger. This project is used implicitly to record values of interest on a line-by-line basis and communicate them to Xcode. Calls are automatically injected into playground code so no explicit reference is required.
PlaygroundSupport offers a limited set of APIs for communicating specific requests to Xcode and should be self-explanatory.
The standard Swift build script included in the Swift repository automatically pulls and builds the Xcode Playground Support source.
Via HTTPS For those checking out sources as read-only, HTTPS works best:
git clone https://github.com/apple/swift-xcode-playground-support.git cd swift-xcode-playground-support
Via SSH For those who plan on regularly making direct commits, cloning over SSH may provide a better experience (which requires uploading SSH keys to GitHub):
git clone firstname.lastname@example.org:apple/swift-xcode-playground-support.git cd swift-xcode-playground-support
PlaygroundSupport and PlaygroundLogger can be built individually building the respective Xcode projects. It is critical that they're built using the Swift compiler they're intended to be used with, which can be achieved by building, installing, and selecting the corresponding toolchain in the Xcode UI.
Both projects contain universal targets that build all applicable products.
The target in PlaygroundLogger is named
All Platforms Logger; in
PlaygroundSupport it is named
For testing purposes, PlaygroundLogger requires the presence of the
StdlibUnittest module which is part of Swift. This can be overriden either by
BuildAndIntegration configuration, or via the
conditional compilation directive.
Command-line builds using
xcodebuild require setting the
environment variable to a fully-qualified path for the corresponding Swift
Swift Xcode Playground Support changes may be required as the Swift language evolves. As with other aspects of Swift, contributions are welcomed and encouraged! Please see the Contributing to Swift guide.
To be a truly great community, Swift.org needs to welcome developers from all walks of life, with different backgrounds, and with a wide range of experience. A diverse and friendly community will have more great ideas, more unique perspectives, and produce more great code. We will work diligently to make the Swift community welcoming to everyone.
To give clarity of what is expected of our members, Swift has adopted the code of conduct defined by the Contributor Covenant. This document is used across many open source communities, and we think it articulates our values well. For more, see the Code of Conduct.