scratchfoundation/scratch-vm
1
0
Fork 0
mirror of https://github.com/scratchfoundation/scratch-vm.git synced 2025-05-23 11:46:47 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions1

add existing extension docs in docs directory

Browse source
This commit is contained in:
Christopher Willis-Ford 2019-04-05 13:50:24 -07:00
parent f02433510a
commit bcda700818
2 changed files with 507 additions and 0 deletions

189
docs/extension-translation-straw-cat.md Normal file
View file

@ -0,0 +1,189 @@
Not really a proposal, more a starting point for discussion. Currently only considering extensions.
Essentially strings turn into an array of `['default string', 'translation-key']`, and `translation_map` has a dictionary for each language code supported. When someone switches language, the dictionary for the corresponding language code should be used if available.
# Example
```js
class SomeBlocks {
constructor (runtimeProxy) {
/**
* A proxy to communicate with the Scratch 3.0 runtime across a worker boundary.
* @type {Runtime}
*/
this.runtime = runtimeProxy;
}
/**
* @return {object} This extension's metadata.
*/
getInfo () {
return {
// Required: the machine-readable name of this extension.
// Will be used as the extension's namespace.
id: 'someBlocks',
// Optional: the human-readable name of this extension as string or array.
// If not present, use the ID.
// If an array, first element is default text, second is the id
// of the string in the translation map
name: ['Some Blocks', 'someBlocks'],
// Optional: URI for an icon for this extension. Data URI OK.
// If not present, use a generic icon.
// TODO: what file types are OK? All web images? Just PNG?
iconURI: 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAkAAAAFCAAAAACyOJm3AAAAFklEQVQYV2P4DwMMEMgAI/+DEUIMBgAEWB7i7uidhAAAAABJRU5ErkJggg==',
// Optional: Link to documentation content for this extension.
// If not present, offer no link.
docsURI: 'https://....',
// Required: the list of blocks implemented by this extension,
// in the order intended for display.
blocks: [
{
// Required: the machine-readable name of this operation.
// This will appear in project JSON.
opcode: 'myReporter', // becomes 'someBlocks.myReporter'
// Required: the kind of block we're defining, from a predefined list:
// 'command' - a normal command block, like "move {} steps"
// 'reporter' - returns a value, like "direction"
// 'Boolean' - same as 'reporter' but returns a Boolean value
// 'hat' - starts a stack if its value is truthy
// 'conditional' - control flow, like "if {}" or "repeat {}"
// A 'conditional' block may return the one-based index of a branch
// to run, or it may return zero/falsy to run no branch. Each time a
// child branch finishes, the block is called again. This is only a
// slight change to the current model for control flow blocks, and is
// also compatible with returning true/false for an "if" or "repeat"
// block.
// TODO: Consider Blockly-like nextStatement, previousStatement, and
// output attributes as an alternative. Those are more flexible, but
// allow bad combinations.
blockType: 'reporter',
// Required for conditional blocks, ignored for others: the number of
// child branches this block controls. An "if" or "repeat" block would
// specify a branch count of 1; an "if-else" block would specify a
// branch count of 2.
// TODO: should we support dynamic branch count for "switch"-likes?
branchCount: 0,
// Optional, default false: whether or not this block ends a stack.
// The "forever" and "stop all" blocks would specify true here.
terminal: true,
// Optional, default false: whether or not to block all threads while
// this block is busy. This is for things like the "touching color"
// block in compatibility mode, and is only needed if the VM runs in a
// worker. We might even consider omitting it from extension docs...
blockAllThreads: false,
// Required: the human-readable text on this block, as a map from IETF
// language tags to strings in ICU message format. Note that
// '{MY_ARG,string}' tells the extension system the name and type of
// this argument. If the type is found in the `menus` object below,
// then this is a menu. If the extension only supplies one language,
// this may be a single string instead of a map.
// I make no claims about the correctness of my German grammar...
text: ['give {MY_ARG} to my reporter', 'myReporter_text']
// Optional: each argument may specify a default value.
// If absent, the default is a blank/empty field.
defaults: {
MY_ARG: ['some string', 'MY_ARG_default']
}
// Required: the function implementing this block.
func: this.myReporter,
// Optional: list of target types for which this block should appear.
// If absent, assume it applies to all builtin targets -- that is:
// ['sprite', 'stage']
filter: ['someBlocks.wedo2', 'sprite', 'stage']
},
{
// Another block...
}
],
// Optional: define extension-specific menus here.
menus: {
// Required: an identifier for this menu, unique within this extension.
menuA: [
// Static menu: list items which should appear in the menu.
{
// Required: the value of the menu item when it is chosen.
value: 'itemId1',
// Optional: the human-readable label for this item, in ICU format.
// Use `value` as the text if this is absent.
text: ['Item One', 'menuA_item1']
},
// The simplest form of a list item is a string which will be used as
// both value and text.
'itemId2'
],
// Dynamic menu: returns an array as above.
// Called each time the menu is opened.
menuB: this.getItemsForMenuB
},
// Optional: translations
translation_map: {
'de' : {
'someBlocks' : 'Einige Blöcke',
'myReporter_text' : 'Gib {MY_ARG} zu meinem Reporter',
'myReporter_val' : '{my_arg} ist mein wert'
'MY_ARG_default' : 'etwas inhalt',
'menuA_item1' : 'Artikel eins',
'menuB_default' : 'Beispiel' //default to use for getItemsForMenuB
},
'it' : {
...
}
}
// Optional: list new target type(s) provided by this extension.
targetTypes: [
'wedo2', // automatically transformed to 'someBlocks.wedo2'
'speech' // automatically transformed to 'someBlocks.speech'
]
};
}
/**
* Implement myReporter.
* @param {object} args - the block's arguments.
* @property {string} MY_ARG - the string value of the argument.
* @returns {string} a string which includes the block argument value.
*/
myReporter (args) {
//return `${args.MY_ARG} is my argument`;
return _trans(['{my_arg} is my argument', myReporter_val], {'my_arg' : args.MY_ARG})
}
}
```
# Questions and Issues
* What about collisions? If two extensions have 'MY_ARG_default', they shouldn't collide. Should the keys include the extension id: 'someBlocks.MY_ARG_default', or should we assume that the strings will get loaded into a map that is name-spaced by extension:
```
'someBlocks' : {
...
'MY_ARG_default' : 'something',
...
},
'otherExt' : {
...
'MY_ARG_default' : 'something else',
...
}
```
* Should we insist that the default is English?
* If people want to provide additional translations, how are the original key:strings extracted, and how are new translations included? Do we expect ongoing translation of extensions?
* Should we provide translation for the extension functions as in `_trans` in the myReporter function? How likely are extensions to actually return strings?
* Using ICU formatted strings, by default arguments are only typed if they are number, date or time. We may want to know what type of argument is allowed (e.g. Boolean) to determine the look of the block, but that probably doesn't belong in the translation string.
* This assumes that we'll do some sort of mapping from ICU format `'give {MY_ARG} to my reporter'` to Blockly `'give %1 to my reporter'`. An alternative would be to use Blockly type string format in extensions.

318
docs/extensions.md Normal file
View file

@ -0,0 +1,318 @@
# Scratch 3.0 Extensions
This document describes technical topics related to Scratch 3.0 extension development, including the Scratch 3.0
extension specification.
For documentation regarding other aspects of Scratch 3.0 extensions see [this Extensions page on the
wiki](https://github.com/LLK/docs/wiki/Extensions).
## Types of Extensions
There are four types of extensions that can define everything from the Scratch's core library (such as the "Looks" and
"Operators" categories) to unofficial extensions that can be loaded from a remote URL. Unofficial extensions are not
yet supported.
For more details, see [this Extensions page on the wiki](https://github.com/LLK/docs/wiki/Extensions).
| | Core | Team | Official | Unofficial |
| ------------------------------ | ---- | ---- | -------- | ---------- |
| Developed by Scratch Team | √ | √ | O | X |
| Maintained by Scratch Team | √ | √ | O | X |
| Shown in Library | X | √ | √ | X |
| Sandboxed | X | X | √ | √ |
| Can save projects to community | √ | √ | √ | X |
## Translation
Scratch extensions use the [ICU message format](http://userguide.icu-project.org/formatparse/messages) to handle
translation across languages. For **core, team, and official** extensions, the function `formatMessage` is used to
wrap any ICU messages that need to be exported to the [Scratch Transifex group](https://www.transifex.com/llk/public/)
for translation.
**All extensions** may additionally define a `translation_map` object within the `getInfo` function which can provide
translations within an extension itself. The "Annotated Example" below provides a more complete illustration of how
translation within an extension can be managed.
## Backwards Compatibility
Scratch is designed to be fully backwards compatible. Because of this, block definitions and opcodes should *never*
change in a way that could cause previously saved projects to fail to load or to act in unexpected / inconsistent
ways.
## Defining an Extension
Scratch extensions are defined as a single Javascript class which accepts either a reference to the Scratch
[VM](https://github.com/llk/scratch-vm) runtime or a "runtime proxy" which handles communication with the Scratch VM
across a well defined worker boundary (i.e. the sandbox).
```js
var SomeBlocks = function (runtimeProxy) {
/**
* A proxy to communicate with the Scratch 3.0 runtime across a worker boundary.
* @type {Runtime}
*/
this.runtime = runtimeProxy;
}
```
All extensions must define a function called `getInfo` which returns an object that contains the information needed to
render both the blocks and the extension itself.
```js
SomeBlocks.prototype.getInfo = function () {
return {
id: 'someBlocks',
name: 'Some Blocks',
blocks: [
{
opcode: 'myReporter',
blockType: BlockType.REPORTER,
text: 'letter [LETTER_NUM] of [TEXT]',
arguments: {
LETTER_NUM: {
type: ArgumentType.STRING,
defaultValue: '1'
},
TEXT: {
type: ArgumentType.STRING,
defaultValue: 'text'
}
}
}
]
};
};
```
Finally the extension must define a function for any "opcode" defined in the blocks. For example:
```js
SomeBlocks.prototype.myReporter = function (args) {
return args.TEXT.charAt(args.LETTER_NUM);
};
```
## Annotated Example
```js
var SomeBlocks = function (runtimeProxy) {
/**
* A proxy to communicate with the Scratch 3.0 runtime across a worker boundary.
* @type {Runtime}
*/
this.runtime = runtimeProxy;
};
/**
* @return {object} This extension's metadata.
*/
SomeBlocks.prototype.getInfo = function () {
return {
// Required: the machine-readable name of this extension.
// Will be used as the extension's namespace.
id: 'someBlocks',
// Optional: the human-readable name of this extension as string.
// This and any other string to be displayed in the Scratch UI may either be
// a string or a call to `formatMessage`; a plain string will not be
// translated whereas a call to `formatMessage` will connect the string
// to the translation map (see below). The `formatMessage` call is
// similar to `formatMessage` from `react-intl` in form, but will actually
// call some extension support code to do its magic. For example, we will
// internally namespace the messages such that two extensions could have
// messages with the same ID without colliding.
// See also: https://github.com/yahoo/react-intl/wiki/API#formatmessage
name: formatMessage({
id: 'extensionName',
defaultMessage: 'Some Blocks',
description: 'Extension name'
}),
// Optional: URI for a block icon, to display at the edge of each block for this
// extension. Data URI OK.
// TODO: what file types are OK? All web images? Just PNG?
blockIconURI: 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAkAAAAFCAAAAACyOJm3AAAAFklEQVQYV2P4DwMMEMgAI/+DEUIMBgAEWB7i7uidhAAAAABJRU5ErkJggg==',
// Optional: URI for an icon to be displayed in the blocks category menu.
// If not present, the menu will display the block icon, if one is present.
// Otherwise, the category menu shows its default filled circle.
// Data URI OK.
// TODO: what file types are OK? All web images? Just PNG?
menuIconURI: 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAkAAAAFCAAAAACyOJm3AAAAFklEQVQYV2P4DwMMEMgAI/+DEUIMBgAEWB7i7uidhAAAAABJRU5ErkJggg==',
// Optional: Link to documentation content for this extension.
// If not present, offer no link.
docsURI: 'https://....',
// Required: the list of blocks implemented by this extension,
// in the order intended for display.
blocks: [
{
// Required: the machine-readable name of this operation.
// This will appear in project JSON.
opcode: 'myReporter', // becomes 'someBlocks.myReporter'
// Required: the kind of block we're defining, from a predefined list:
// 'command' - a normal command block, like "move {} steps"
// 'reporter' - returns a value, like "direction"
// 'Boolean' - same as 'reporter' but returns a Boolean value
// 'hat' - starts a stack if its value is truthy
// 'conditional' - control flow, like "if {}" or "if {} else {}"
// A 'conditional' block may return the one-based index of a branch to
// run, or it may return zero/falsy to run no branch.
// 'loop' - control flow, like "repeat {} {}" or "forever {}"
// A 'loop' block is like a conditional block with two differences:
// - the block is assumed to have exactly one child branch, and
// - each time a child branch finishes, the loop block is called again.
blockType: 'reporter',
// Required for conditional blocks, ignored for others: the number of
// child branches this block controls. An "if" or "repeat" block would
// specify a branch count of 1; an "if-else" block would specify a
// branch count of 2.
// TODO: should we support dynamic branch count for "switch"-likes?
branchCount: 0,
// Optional, default false: whether or not this block ends a stack.
// The "forever" and "stop all" blocks would specify true here.
terminal: true,
// Optional, default false: whether or not to block all threads while
// this block is busy. This is for things like the "touching color"
// block in compatibility mode, and is only needed if the VM runs in a
// worker. We might even consider omitting it from extension docs...
blockAllThreads: false,
// Required: the human-readable text on this block, including argument
// placeholders. Argument placeholders should be in [MACRO_CASE] and
// must be [ENCLOSED_WITHIN_SQUARE_BRACKETS].
text: formatMessage({
id: 'myReporter',
defaultMessage: 'letter [LETTER_NUM] of [TEXT]',
description: 'Label on the "myReporter" block'
}),
// Required: describe each argument.
// Argument order may change during translation, so arguments are
// identified by their placeholder name. In those situations where
// arguments must be ordered or assigned an ordinal, such as interaction
// with Scratch Blocks, arguments are ordered as they are in the default
// translation (probably English).
arguments: {
// Required: the ID of the argument, which will be the name in the
// args object passed to the implementation function.
LETTER_NUM: {
// Required: type of the argument / shape of the block input
type: 'number',
// Optional: the default value of the argument
default: 1
},
// Required: the ID of the argument, which will be the name in the
// args object passed to the implementation function.
TEXT: {
// Required: type of the argument / shape of the block input
type: 'string',
// Optional: the default value of the argument
default: formatMessage({
id: 'myReporter.TEXT_default',
defaultMessage: 'text',
description: 'Default for "TEXT" argument of "myReporter"'
})
}
},
// Required: the function implementing this block.
func: 'myReporter',
// Optional: list of target types for which this block should appear.
// If absent, assume it applies to all builtin targets -- that is:
// ['sprite', 'stage']
filter: ['someBlocks.wedo2', 'sprite', 'stage']
},
{
// Another block...
}
],
// Optional: define extension-specific menus here.
menus: {
// Required: an identifier for this menu, unique within this extension.
menuA: [
// Static menu: list items which should appear in the menu.
{
// Required: the value of the menu item when it is chosen.
value: 'itemId1',
// Optional: the human-readable label for this item.
// Use `value` as the text if this is absent.
text: formatMessage({
id: 'menuA_item1',
defaultMessage: 'Item One',
description: 'Label for item 1 of menu A'
})
},
// The simplest form of a list item is a string which will be used as
// both value and text.
'itemId2'
],
// Dynamic menu: returns an array as above.
// Called each time the menu is opened.
menuB: 'getItemsForMenuB'
},
// Optional: translations
translation_map: {
de: {
'extensionName': 'Einige Blöcke',
'myReporter': 'Buchstabe [LETTER_NUM] von [TEXT]',
'myReporter.TEXT_default': 'Text',
'menuA_item1': 'Artikel eins',
// Dynamic menus can be translated too
'menuB_example': 'Beispiel',
// This message contains ICU placeholders (see `myReporter()` below)
'myReporter.result': 'Buchstabe {LETTER_NUM} von {TEXT} ist {LETTER}.'
},
it: {
// ...
}
},
// Optional: list new target type(s) provided by this extension.
targetTypes: [
'wedo2', // automatically transformed to 'someBlocks.wedo2'
'speech' // automatically transformed to 'someBlocks.speech'
]
};
};
/**
* Implement myReporter.
* @param {object} args - the block's arguments.
* @property {string} MY_ARG - the string value of the argument.
* @returns {string} a string which includes the block argument value.
*/
SomeBlocks.prototype.myReporter = function (args) {
// This message contains ICU placeholders, not Scratch placeholders
const message = formatMessage({
id: 'myReporter.result',
defaultMessage: 'Letter {LETTER_NUM} of {TEXT} is {LETTER}.',
description: 'The text template for the "myReporter" block result'
});
// Note: this implementation is not Unicode-clean; it's just here as an example.
const result = args.TEXT.charAt(args.LETTER_NUM);
return message.format({
LETTER_NUM: args.LETTER_NUM,
TEXT: args.TEXT,
LETTER: result
});
};
```