Microsoft MakeCode editor for the GHI Brainpad
Перейти к файлу
microsoft-github-policy-service[bot] 16e1dabc86
Microsoft mandatory file (#144)
Co-authored-by: microsoft-github-policy-service[bot] <77245923+microsoft-github-policy-service[bot]@users.noreply.github.com>
2022-08-15 14:55:35 -07:00
.github try travis command 2021-10-25 08:58:35 -07:00
.vs Fixed LightTut 2018-08-28 13:45:20 -04:00
docfiles initial commit 2018-03-08 13:32:35 -08:00
docs new version 2021-11-30 09:05:29 -05:00
editor Upgrade pxt (#140) 2021-11-30 08:57:50 -05:00
libs remove unused file 2021-11-30 09:56:43 -05:00
sim Upgrade pxt (#140) 2021-11-30 08:57:50 -05:00
theme Upgrade pxt (#140) 2021-11-30 08:57:50 -05:00
.gitignore ignoring.vs 2018-05-07 08:16:35 -07:00
.travis.yml Remove Jenkins in favor of Travis (#120) 2018-10-29 14:12:41 -04:00
CONTRIBUTING.md initial commit 2018-03-08 13:32:35 -08:00
LICENSE initial commit 2018-03-08 13:32:35 -08:00
README.md revert README.md 2021-11-30 08:59:50 -05:00
SECURITY.md Microsoft mandatory file (#144) 2022-08-15 14:55:35 -07:00
THIRD-PARTY-NOTICES.txt initial commit 2018-03-08 13:32:35 -08:00
faviconData.json adding icons 2018-05-08 10:41:40 -07:00
faviconDescription.json adding icons 2018-05-08 10:41:40 -07:00
package-lock.json 0.22.14 2021-11-30 15:48:50 -05:00
package.json 0.22.14 2021-11-30 15:48:50 -05:00
pxtarget.json Upgrade pxt (#140) 2021-11-30 08:57:50 -05:00
targetconfig.json Upgrade pxt (#140) 2021-11-30 08:57:50 -05:00
tslint.json initial commit 2018-03-08 13:32:35 -08:00

README.md

GHI Electronics Brain Pad target for MakeCode

Build Status Community Discord

Local Dev setup

These instructions assume familiarity with dev tools and languages.

In a common folder,

npm install
jake
  • go to pxt-common-packages and run
npm install
npm link ../pxt
  • go to pxt-brainpad and run
npm install
npm link ../pxt
npm link ../pxt-common-packages

to run the local server

From root github folder,

cd pxt-brainpad
pxt serve --cloud

If you are editing C++, install [docker.com] and make sure your drive is shared.

pxt serve

to build and deploy a single package via command line

cd libs/core
pxt deploy

Updating CODAL dependency

pxt clean
  • build again
pxt buildtarget

Releasing the editor

The version served under / is controlled by /docs/index-ref.json. Change the version in that file and push to immediately update the version.

Each time you bump (using pxt bump) and the build passes, the /beta will point to that release. /beta can be used to test new features before pushing down the release to all users. The update is handled automatically by MakeCode afterwards.

Be careful when updating the version number of the editor, as MakeCode follows semver. In particular, do not change the major version unless you are releasing a completely new and incompatible editor.

  • run pxt udpdate to pick any updates to the PXT engine
  • run pxt bump to create a new release (say vX.Y.Z)
  • wait for build to finish, typically 10 minutes
  • test new build in /beta. You can check the version number in the bottom of the home screen is vX.Y.Z. Remember that it will update the background and load after a dozen of seconds or so.
  • when ready and tested, run pxt tag index vX.Y.Z, and commit /docs/index-ref.json if successfull. This command does some routine checks to make sure everything is ok.

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.