MakeCode für den Calliope
Go to file
2018-02-26 09:24:04 -08:00
.vscode fixing getting started 2017-04-28 17:26:19 -07:00
clients Chromeextension (#499) 2017-08-07 22:33:59 -07:00
cmds Few extra typing fixes. 2017-01-03 12:14:25 -08:00
docfiles Add css files under docfiles 2017-08-15 13:19:40 -07:00
docs updated micro:coin 2018-02-26 09:24:04 -08:00
editor override hid deploy if can hid (#678) 2018-02-26 07:43:02 -08:00
electron Release Electron app v0.9.15 2017-03-07 10:19:10 -08:00
external Support for HID-based partial super-fast flashing (#523) 2017-09-18 09:45:27 -07:00
libs pad serial.writeLine to the 32byte boundary (#676) 2018-02-25 09:15:15 -08:00
pxtwapp super basic trouble shooting page for windows app (#585) 2017-12-04 22:26:25 -08:00
sim Fix led brightness visuals where it's offset on latest Chrome, Firefox and Edge (#651) 2018-02-15 13:15:24 -08:00
tests surfacing missing repeat parameter (#380) 2017-04-03 10:30:25 -07:00
theme Serial (#554) 2017-10-20 10:27:43 -07:00
.gitattributes Add own manifest 2016-04-08 17:28:52 -07:00
.gitignore Support for HID-based partial super-fast flashing (#523) 2017-09-18 09:45:27 -07:00
.travis.yml updated pxt and moving to node 8 (#631) 2018-02-06 14:23:52 -08:00
CONTRIBUTING.md Updating with the MIT license text and contributing guideline 2016-11-28 17:11:45 -08:00
faviconDescription.json adding favicon configuration file 2016-10-20 11:09:34 -07:00
LICENSE.txt Updating with the MIT license text and contributing guideline 2016-11-28 17:11:45 -08:00
package-lock.json 0.14.20 2018-02-26 07:43:26 -08:00
package.json 0.14.20 2018-02-26 07:43:26 -08:00
ptrcheck-ignore update ignore file 2016-07-14 12:04:06 -07:00
pxtarget.json remove legacy domain 2018-02-13 12:08:41 -08:00
README.md updated history 2018-02-23 19:52:11 -08:00
targetconfig.json Add kittenbot robotbit (#619) 2018-02-01 21:52:27 -08:00
THIRD-PARTY-NOTICES.txt add attribution 2017-01-30 16:51:40 -08:00
travis-tests.sh Remove 3 converter tests with overflowing numbers 2016-10-04 08:20:30 -07:00
tslint.json fixing various lint violations 2016-05-04 23:31:55 -07:00
webmanifest.json Updating all pxt.microbit.org reference to makecode.microbit.org (#460) 2017-07-24 13:39:27 -07:00

micro:bit target for PXT

This target allows you to program a BBC micro:bit using PXT (Microsoft Programming Experience Toolkit).

Build Status

Issue tracking

Please add an issue if you discover an (unreported) bug.

Local server

The local server lets you to run the editor and serve the documentation from your own computer.

Setup

The following commands perform a one-time setup after synching the repo on your machine.

  • install node.js 8.9.4 or higher
  • install the PXT command line (add sudo for Mac/Linux shells).
npm install -g pxt
  • install the microbit target
pxt target microbit

Running

Run this command to open a local web server (add sudo for Mac/Linux shells)

pxt serve

If the local server opens in the wrong browser, make sure to copy the URL containing the local token. Otherwise, the editor will not be able to load the projects.

The server assumes you have yotta installed. You can skip that requirement by adding --cloud.

pxt serve --cloud

Updates

To update your PXT version and make sure you're running the latest tools, run (add sudo for Mac/Linux shells):

pxt update

More instructions are at https://github.com/Microsoft/pxt#running-a-target-from-localhost

Developer setup

If you need to make source changes to pxt and pxt-microbit, follow these instructions:

git clone https://github.com/Microsoft/pxt
  • checkout the v0 branch in pxt
cd pxt
git checkout v0
  • npm install and run jake
npm install
jake
cd ..
git clone https://github.com/Microsoft/pxt-microbit
  • npm install and link to the pxt folder
cd pxt-microbit
npm install
npm link ../pxt

Both of those repoes are now ready to go. To start your local server, run

pxt serve

or, without yotta tools,

pxt serve --cloud

Repos

The pxt-microbit target depends on several other repos. The main ones are:

History

See the MakeCode blog.

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.