Skip to content

Latest commit

 

History

History
114 lines (83 loc) · 4.43 KB

CONTRIBUTING.md

File metadata and controls

114 lines (83 loc) · 4.43 KB

Contributing Guidelines

While one may use any editors to work with BP Studio, it is highly recommended to use VS Code as the project folder is already configured for it. As you open the project with it, it will also hint you the recommended extensions to install.

Contributing new languages

Please refer to the readme of the Locale section.

Environment and build instructions

To build BP Studio, first you need the following:

  1. Install or upgrade Node.js to v20+.
  2. BP Studio had migrated from NPM to PNPM for package managing, so install PNPM by the command npx pnpm install -g pnpm.
  3. Use the command pnpm install under the project root folder to install all dependencies.
  4. Run pnpm gulp once to create pre-build assets.

And then you can simply press F5 in VS Code to build and launch the app automatically. This is the preferred way to launch as it allows debugging in the IDE.

Alternatively, run pnpm build to build the entire project manually, and then run pnpm preview to launch the local server on production build.

Note: one should always run BP Studio through a server, as some of the features would not work in files:// protocol.

Developing optimizer

The BP Studio optimizer is written in C++. Pre-compiled WASM binaries are already included in the repo, but if you'd like to compile it, you'll need:

  • Emscripten, and make sure that emcc is available in PATH.
    You may also need to change configurations.compilerPath in the .vscode/c_cpp_properties.json file to reflect the location of your Emscripten installation.
  • GNU make, if you're on Windows.
    (Our makefile should work on all desktop platforms regardlessly.)

Then you can compile the Optimizer by:

make      # For debug build
make dist # For dist (release) build

For more about the optimizer, see README.

Browser compatibility

BP Studio have tried to support as much browser versions as possible, but there are some essential barriers that cannot be compromised. First of all, IE is obviously not supported as there're way too many modern features that cannot be used, plus it's REALLY dead by now. And then:

  • Firefox < 78 and Safari < 11.1 (or iOS < 11.3) does not support the s flag of regular expressions. See caniuse.
  • Chrome < 66 and Opera < 53 does not support Array.prototype.values. See caniuse.

Both these features are used in Vue 3, which is a critical dependency of BP Studio. The second issue could be polyfilled, but I see less point in doing so as those versions are old enough already, while the first issue is impossible to polyfill.

Note that the targeted version almost coincide with the support for optional catch binding, with Firefox being the only exception.

There's currently no plans for officially supporting browsers other than Chrome, Edge, Safari, Firefox, Opera, and Samsung Internet. Not that I don't want to, but that I don't have the resource to do so.

Automate testing

BP Studio contains three test sets: the Mocha unit tests, the Playwright e2e tests, and the Python tests. Refer to the README of each for details.

Code styling

This project use ESLint for both linting and formatting (using @stylistic/eslint-plugin). If one opens it with VS Code plus the recommended extensions, all files will go through auto formatting as one saves them.

About the source code organization

BP Studio consists mainly of three parts: the App, the Client, and the Core. Their relations can be roughly depicted as follows:

graph LR
	a("App<br>(user interface)")
	b("Client<br>(workspace)")
	c("Core<br>(worker thread)")
	a -->|controls| b
	b -->|data| a
	b -->|manipulates| c
	c -->|graphics| b
Loading

Refer to the README of each of them through the links above for more details.

All comments are now in English! Feel free to contact me in any part of the code is unclear to you.