MakeCode für den Calliope
Go to file
2017-07-24 10:23:43 -07:00
.vscode fixing getting started 2017-04-28 17:26:19 -07:00
clients pxt-> makecode (#412) 2017-06-13 12:56:55 -07:00
cmds Few extra typing fixes. 2017-01-03 12:14:25 -08:00
docs add a new project 2017-07-24 10:23:43 -07:00
editor Fix td extension. 2017-04-19 10:40:39 -07:00
electron Release Electron app v0.9.15 2017-03-07 10:19:10 -08:00
libs Fixing array pop (#458) 2017-07-21 13:42:48 -05:00
sim Fix A+B selection issue on click. Fixes Microsoft/pxt#2373 2017-06-30 01:41:48 -07:00
tests surfacing missing repeat parameter (#380) 2017-04-03 10:30:25 -07:00
theme Monaco editor background is now defined in pxtarget.json 2017-07-11 12:01:40 +03:00
.gitattributes Add own manifest 2016-04-08 17:28:52 -07:00
.gitignore Change default product names for Electron app; Add release manifest 2016-12-21 12:31:00 -08:00
.travis.yml removing upload step 2016-11-06 20:38:53 -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.json 0.12.45 2017-07-11 16:40:29 +03:00
ptrcheck-ignore update ignore file 2016-07-14 12:04:06 -07:00
pxtarget.json Monaco editor background is now defined in pxtarget.json 2017-07-11 12:01:40 +03:00
README.md Update README.md 2017-07-18 11:05:28 -07:00
targetconfig.json Update approved package list to include PXT minode (#450) 2017-07-24 06:54:53 -07: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 link to samsung app for chrome 2017-04-27 23:50:46 -07:00

micro:bit target for PXT

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

Build Status

Issue tracking

All issue tracking for this repo happens at https://github.com/Microsoft/pxt, see you there!

Local server

The local server allows to run the editor and the documentation from your computer.

Setup

The following commands are a 1-time setup after synching the repo on your machine.

git clone https://github.com/microsoft/pxt-microbit
cd pxt-microbit
  • install the PXT command line (add sudo for Mac/Linux shells).
npm install -g pxt
  • install the dependencies
npm install

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.

If you need modify the .cpp files, turn on yotta compilation with the -yt flag (add sudo for Mac/Linux shells):

pxt serve -yt

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 at https://github.com/Microsoft/pxt#running-a-target-from-localhost

Testing

The build automatically runs the following:

  • make sure the built-in packages compile
  • pxt run in libs/lang-test* - this will run the test in command line runner; there is a number of asserts in both of these
  • pxt testdir in tests - this makes sure all the files compile and generates .hex files
  • run the TD->TS converter on a number of test scripts from microbit.co.uk and make sure the results compile

To test something on the device:

  • do a pxt deploy in libs/lang-test* - they should show 1 or 2 on the screen (and not unhappy face)
  • run pxt testdir in tests and deploy some of the hex files from tests/built

The lang-test0 source comes from the pxt-core package. It's also tested with pxt run there.

Repos

There are a number of repos that pxt-microbit depends on. The main ones are:

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.