Skip to content
Microsoft MakeCode editor for Adafruit Circuit Playground Express
Branch: master
Clone or download
ganicke Logic Lab mini-course (#1072)
* page set, pics, etc.

* Do explorer page and fill in overview

* rearrange sections

* Last blast, rearranging, and more
Latest commit 7c9bd3e Jul 19, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Update issue tracker templates May 17, 2018
.vscode adding tab size in settings Oct 18, 2016
docfiles Update docs avatar image (#429) Oct 26, 2017
docs Logic Lab mini-course (#1072) Jul 19, 2019
editor Removing left over $s from template strings (#996) Apr 17, 2019
fieldeditors No mbed build (#951) Mar 12, 2019
libs Add check for dot star leds before making APA102 strip (#1059) Jun 4, 2019
pxtwapp Merge branch 'master' of https://www.github.com/Microsoft/pxt-adafruit Jul 21, 2017
resources Add files via upload Jan 3, 2019
schematics Upgrading to codal 0.1.4 (#160) May 23, 2017
sim fix acceleration (#990) Apr 17, 2019
theme Dark theme colors for animated tooltip (#1057) Jun 19, 2019
.clang-format Auto-format C++ code Dec 16, 2016
.gitattributes initial drop Oct 11, 2016
.gitignore remove package lock Apr 26, 2019
.travis.yml Upgrading to node 8 (#622) Feb 6, 2018
CONTRIBUTING.md Contributing information (#209) Jun 16, 2017
LICENSE Update License name to Pxt-adafruit Jun 16, 2017
README.md Trademarks May 2, 2019
THIRD-PARTY-NOTICES.txt Add open sans into the repo and include in third party notices (#486) Nov 8, 2017
adafruit.code-workspace updated pxt (#968) Mar 19, 2019
faviconData.json generic icons Jan 23, 2017
faviconDescription.json generic icons Jan 23, 2017
package.json 1.4.30 Jun 4, 2019
pxtarget.json Pointing to latest codal core (#1033) May 17, 2019
targetconfig.json Setup the 'Behind the MakeCode Hardware' gallery (#1025) May 8, 2019
tslint.json initial drop Oct 11, 2016

README.md

MakeCode for Adafruit Circuit Playground Express Build Status

This repo contains the editor hosted at https://makecode.adafruit.com .

Local server setup

This setup gives you a local version of the editor and the ability to load packages from your machine. This is the setup to develop new packages.

Setup

npm install

Don't forget to periodically git pull and npm install to get the latest changes.

Launching the server

This command launches a local web server. Note that this web server is meant for development purposes only. It was not designed or secured to be run on a web server.

npm run serve

Creating and editing a package

  • go to /projects under the pxt-adafruit folder
  • clone your package repo, say pxt-helloworld
  • launch the server with npm run serve from the pxt-adafruit folder using npm serve
  • create a new project
  • go to project settings and click on Edit settings as text
  • add an entry in the dependency section that points to your project
    "dependencies": {
        "circuit-playground": "*",
        "helloworld": "file:../pxt-helloworld"
    },
  • click on the Blocks icon to reload the blocks.

Once this project is setup, simply reload the editor after making changes on disk.

Local Dev setup

This setup is needed if you plan to make changes in PXT itself. In most cases, it's a bit of an overkill if you are building a package for the Adafruit editor.

npm install -g pxt

In a common folder,

npm install
npm run build
  • go to pxt-common-packages and run
npm install
npm link ../pxt
  • go to pxt-adafruit and run
npm install
npm link ../pxt
npm link ../pxt-common-packages

to run the local server

From root github folder,

cd pxt-adafruit
pxt serve

to build and deploy a single package via command line

cd libs/core
pxt deploy

License

MIT

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

MICROSOFT, the Microsoft Logo, and MAKECODE are registered trademarks of Microsoft Corporation. They can only be used for the purposes described in and in accordance with Microsoft’s Trademark and Brand guidelines published at https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general.aspx. If the use is not covered in Microsoft’s published guidelines or you are not sure, please consult your legal counsel or MakeCode team (makecode@microsoft.com).

You can’t perform that action at this time.