After you submit an extension for publishing, the mBlock team will review it in accordance with the review criteria. After being approved, the extension is provided on mBlock 5.
To improve the publishing efficiency and quality of your extension, it is suggested that you test it before submitting it for publishing. The following table lists the check items and their corresponding requirements.
Check items and their requirements
Check item |
Requirements |
Blocks |
In the Variables category, after you make a variable, the show variable () and hide variable () blocks are disabled in Upload mode. |
The functions in Live mode, if any, can be used properly. |
|
The functions in Upload mode, if any, can be used properly. |
|
The check box for reading a value, if any, can be used properly. |
|
Firmware |
The firmware can be properly updated. |
The firmware name includes no version number. |
|
Translation |
Device/extension—blocks translated |
Device/extension—block category names translated |
|
Device—device name translated (in accordance with product specifications) |
|
Extension— extension introduction translated |
|
Device/extension—parameters translated (in accordance with product specifications) |
|
Device—firmware name translated (if any) |
|
Device—setting items in the pop-up box translated (if any) |
|
Device—serial connection messages translated (if any) |
|
Device—Bluetooth 4.0 connection messages translated (if any) |
|
Device—firmware update failure messages translated (if any) |
|
Connection |
Serial connection works properly (if any). |
Bluetooth 4.0 connection works properly (if any, note that Bluetooth 4.0 connection here refers to the connection through the Bluetooth 4.0 adapter of your PC). |
|
Compatibility |
Blocks included in the new version of an extension are compatible to the earlier versions. |
Blocks can be used on the mBlock 5 PC client, webpage, and mobile apps (if selected when you create the blocks). |
|
Others |
Links provided in the messages are valid. |
No wording errors are found in the blocks, messages, or extension introduction. |
Test suggestions
- Test the combination of the reporter blocks and repeat ()/forever () block.
- Test the parameters of the blocks.
- Test the combination of the blocks and common blocks (especially blocks involving transcoding, such as the Events blocks).
- Select multiple check boxes for reading values (if any) and see whether the stage displays multiple values properly.
Message configuration
Suggestions and requirements
Links to connection help are correct
- Currently, you can't configure messages to indicate successful connections. (The message "Connected!" is displayed by default. It is suggested that you configure one message for all successful connections even if the message can be configued in the future.)
- It is suggested that you configure a maximum of five messages indicating connection failure, with each one no more than 30 characters and the total of the messages no more than 80 characters.
Links to upload help are correct
- Currently, you can't configure messages to indicate successful code upload. (The message "The code has been uploaded!" is displayed by default. It is suggested that you configure one message for successful code upload even if the message can be configured in the future.)
- It is suggested that you configure a maximum of five messages indicating code upload failure, with each one no more than 30 characters and the total of the messages no more than 120 characters.
Links to firmware update help are correct
It is suggested that you configure:
- A maximum of five firmware update prompts, with each one no more than 30 characters and the total of the prompts no more than 80 characters
- A maximum of five messages indicating that the firmware is being updated, with each one no more than 30 characters and the total of the messages no more than 80 characters
- A maximum of five messages indicating that the firmware is successfully updated, with each one no more than 30 characters and the total of the messages no more than 80 characters
- A maximum of five messages indicating that the firmware update fails, with each one no more than 30 characters and the total of the messages no more than 120 characters
Note: Pay attention to the translation of the messages when configuring them.
Comments
Please sign in to leave a comment.