Browser-based graphical development tool that runs uLisp scripts on BL602 RISC-V Board.
Read the article...
Watch the demo on YouTube...
Try it here...
https://appkaki.github.io/blockly-ulisp/demos/code/
uLisp Firmware needs to be installed on the BL602 Board...
https://github.com/lupyuen/bl_iot_sdk/tree/ulisp/customer_app/sdk_app_ulisp
Or try it with the BL602 Simulator in WebAssembly...
https://appkaki.github.io/blockly-ulisp/demos/simulator/
The following have been added into the existing generators folder to generate Lisp code and to add blocks specific to uLisp...
-
generators/lisp.js: Main interface for Lisp Code Generator -
generators/lisp: Lisp Code Generator for various blocks -
generators/lisp/lisp_library.xml: Blocks XML file used by Block Exporter to generate the custom blocks
The Lisp Code Generator is incomplete. The only blocks supported are...
-
Forever
-
On Start
-
Wait
-
GPIO Digital Write
The Lisp Code Generator is based on Visual Embedded Rust...
https://lupyuen.github.io/articles/advanced-topics-for-visual-embedded-rust-programming
Watch the demo on YouTube...
Try it here...
https://appkaki.github.io/blockly-ulisp/demos/code/
Or try it with the BL602 Simulator in WebAssembly...
https://appkaki.github.io/blockly-ulisp/demos/simulator/
The Blockly demo at demos/code has been customised to include the Lisp Code Generator...
-
demos/code/index.html: Customised to load the Lisp Code Generator and Lisp Blocks -
demos/code/code.js: Customised to load the Lisp Code Generator and Lisp Blocks
The Blockly demo calls the Web Serial API to transfer the generated uLisp Script to BL602...
https://github.com/AppKaki/blockly-ulisp/blob/master/demos/code/code.js#L641-L738
We assume that BL602 is running the uLisp Firmware and connected to our computer via USB...
https://github.com/lupyuen/bl_iot_sdk/tree/ulisp/customer_app/sdk_app_ulisp
The BL602 Simulator HTML and JavaScript files are here...
-
demos/simulator/index.html: Customised to load the Lisp Code Generator, Lisp Blocks and BL602 Simulator -
demos/simulator/code.js: Customised to load the Lisp Code Generator, Lisp Blocks and BL602 Simulator
The BL602 Simulator includes uLisp compiled for WebAssembly...
https://github.com/lupyuen/ulisp-bl602/tree/wasm
Inspired by MakeCode for BBC micro:bit...
https://makecode.microbit.org/
Google's Blockly is a library that adds a visual code editor to web and mobile apps. The Blockly editor uses interlocking, graphical blocks to represent code concepts like variables, logical expressions, loops, and more. It allows users to apply programming principles without having to worry about syntax or the intimidation of a blinking cursor on the command line. All code is free and open source.
Blockly has many resources for learning how to use the library. Start at our Google Developers Site to read the documentation on how to get started, configure Blockly, and integrate it into your application. The developers site also contains links to:
Help us focus our development efforts by telling us what you are doing with Blockly. The questionnaire only takes a few minutes and will help us better support the Blockly community.
Blockly is available on npm.
npm install blocklyFor more information on installing and using Blockly, see the Getting Started article.
- Report a bug or file a feature request on GitHub
- Ask a question, or search others' questions, on our developer forum. You can also drop by to say hello and show us your prototypes; collectively we have a lot of experience and can offer hints which will save you time. We actively monitor the forums and typically respond to questions within 2 working days.
We have a number of resources such as example code, demos, and plugins in another repository called blockly-samples. A plugin is a self-contained piece of code that adds functionality to Blockly. Plugins can add fields, define themes, create renderers, and much more. For more information, see the Plugins documentation.
Want to make Blockly better? We welcome contributions to Blockly in the form of pull requests, bug reports, documentation, answers on the forum, and more! Check out our Contributing Guidelines for more information. You might also want to look for issues tagged "Help Wanted" which are issues we think would be great for external contributors to help with.
The next major release will be March 25th, 2021.
We release by pushing the latest code to the master branch, followed by updating the npm package, our docs, and demo pages. We typically release a new version of Blockly once a quarter (every 3 months). If there are breaking bugs, such as a crash when performing a standard action or a rendering issue that makes Blockly unusable, we will cherry-pick fixes to master between releases to fix them. The releases page has a list of all releases.
Releases are tagged by the release date (YYYYMMDD) with a leading '4.' and a trailing '.0' in case we ever need a major or patch version (such as 2.20190722.1). Releases that have breaking changes or are otherwise not backwards compatible will have a new major version. Patch versions are reserved for bug-fix patches between scheduled releases.
We now have a beta release on npm. If you'd like to test the upcoming release, or try out a not-yet-released new API, you can use the beta channel with:
npm install blockly@betaAs it is a beta channel, it may be less stable, and the APIs there are subject to change.
There are two main branches for Blockly.
master - This is the (mostly) stable current release of Blockly.
develop - This is where most of our work happens. Pull requests should always be made against develop. This branch will generally be usable, but may be less stable than the master branch. Once something is in develop we expect it to merge to master in the next release.
other branches: - Larger changes may have their own branches until they are good enough for people to try out. These will be developed separately until we think they are almost ready for release. These branches typically get merged into develop immediately after a release to allow extra time for testing.
Once a new API is merged into master it is considered beta until the following release. We generally try to avoid changing an API after it has been merged to master, but sometimes we need to make changes after seeing how an API is used. If an API has been around for at least two releases we'll do our best to avoid breaking it.
Unreleased APIs may change radically. Anything that is in develop but not master is subject to change without warning.
We typically triage all bugs within 2 working days, which includes adding any appropriate labels and assigning it to a milestone. Please keep in mind, we are a small team so even feature requests that everyone agrees on may not be prioritized.
Upcoming release - The upcoming release milestone is for all bugs we plan on fixing before the next release. This typically has the form of year_quarter_release (such as 2019_q2_release). Some bugs will be added to this release when they are triaged, others may be added closer to a release.
Bug Bash Backlog - These are bugs that we're still prioritizing. They haven't been added to a specific release yet, but we'll consider them for each release depending on relative priority and available time.
Icebox - These are bugs that we do not intend to spend time on. They are either too much work or minor enough that we don't expect them to ever take priority. We are still happy to accept pull requests for these bugs.
- Cross-browser Testing Platform and Open Source <3 Provided by Sauce Labs
- We support IE11 and test it using BrowserStack