ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
Microsoft MakeCode는 재미있는 프로젝트, 즉각적인 결과 및 다양한 수준의 학습자를 위한 블록 편집기와 텍스트 편집기를 통해 컴퓨터 과학을 모든 학생의 생활에 적용합니다.
Translation pending
EducationTypeScript · JavaScriptGitHub @microsoftOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Microsoft MakeCode (PXT - Programming eXperience Toolkit)
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗Microsoft MakeCode is based on the open source project Microsoft Programming Experience Toolkit (PXT). Microsoft MakeCode is the name in the user-facing editors, PXT is used in all the GitHub sources.
PXT is a framework for creating special-purpose programming experiences for beginners, especially focused on computer science education. PXT's underlying programming language is a subset of TypeScript (leaving out JavaScript dynamic features).
The main features of PXT are:
More info:
Examples of Editors built with MakeCode:
master is the active development branch, currently v3.* buildsv* is the servicing branch for v*.* buildsPlease follow the instructions here.
If you are modifying your own instance of PXT and want a target (such as pxt-microbit) to use your local version, cd to the directory of the target (pxt-microbit, in our example, which should be a directory sibling of pxt) and perform
pxt link ../pxt
If you have multiple checkouts of pxt, you can do the following:
npm i in pxt and the targetpxt link ..\some-other-pxt (you may need to update your CLI first by running npm install -g pxt)If you run npm i afterwards (in either the target or pxt), you might need to repeat these steps.
First, install Node: minimum version 24.
To build the PXT command line tools:
npm install
npm run build
Then install the pxt command line tool (only need to do it once):
npm install -g pxt
Then install gulp (only need to do it once):
npm install -g gulp
After this you can run pxt from anywhere within the build tree.
To start the local web server, run pxt serve from within the root
of an app target (e.g. pxt-microbit). PXT will open the editor in your default web browser.
If you are developing against pxt, you can run gulp watch from within the root of the
pxt repository to watch for changes and rebuild.
gulp watch
If you are working on the CLI exclusively,
gulp watchCli
If you don't need to build the suite of associated webapps (skillmap, multiplayer, etc.), you can skip them and speed up your build a bit:
gulp --no-webapps
There are a number of custom icons (to use in addition
to http://semantic-ui.com/elements/icon.html) in the svgicons/ directory.
These need to be 1000x1000px. Best start with an existing one. To see available icons go to
http://localhost:3232/icons.html (this file, along with icons.css containing
the generated WOFF icon font, is created during build).
If you're having trouble with display of the icon you created, try:
npm install -g svgo
svgo svgicons/myicon.svg
When adding a CSS color or other style element that will be shared across editor targets (e.g. micro:bit, Arcade) and sub-applications (a.k.a. "CRAs", like skillmap, teachertool, etc.). Declare a CSS variable for it in theme/themepacks.less:
:root pseudo-class. Choose a reasonable default value according to the guidelines in the file.theme-highcontrast is defined. Choose a value that works well for the given theme.theme/themepacks.less file (e.g. pxt-microbit, pxt-arcade).Variables declared this way will be available to CRAs at runtime, and they will be initialized with the override values defined by the target in which they're running.
In the documentation, highlighting of code snippets uses highlight.js (hljs). Currently, the following languages are included:
If you need to add other languages or update existing ones,
you can find the distribution at https://highlightjs.org/download/;
select all the languages you want to include (including the ones above!),
download and unzip,
and finally copy over highlight.min.js as webapp/public/highlight.js/highlight.pack.js.
The tests are located in the tests/ subdirectory and are a combination of node and
browser tests. To execute them, run npm run test:all in the root directory.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
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 ([email protected]).