Basic notes on how DoenetML works

[melissa-lynn]

What Duane said (mod errors introduced in notetaking):

Repositories:

• DoenetApps: AWS, website, users, logging in, assignments
• DoenetML: editor, formatter, converter
• math-expressions: simplify, expand, stuff that tag does

In DoenetML:

• doenetml: react app
• doenetml-worker-javascript: components, core

In a component definition:

• componentDocs: for documentation description of each attribute for docs
• forRenderer only if needed for rendering (affects speed)
• returnChildGroups: what its allowed to have as children

(Still in component) State variable definition:

• public: can access with .svname in DoenetML (then need description)
• returnDependencies: needed for directed acyclic graph updates
• there are essential state variables, which are the only things actually holding values, and updates propagate through the DAG
• inverseDefinition: used when the user interacts with an object, this goes back in the DAG to update the essential state variable. success true if successfully updates essential state variable; have "desired" values because might not be able to update essential values.

attribute: input (e.g. , simplify is attribute)
property: output (public state variable, e.g. $x.simplify, simplify is property)

More information: https://github.com/Eyuelwoldeh/DoenetML-documentation

[melissa-lynn]

Helpful for development:

• Edit DoenetML code in packages/doenetml/dev/testCode.doenet
• run dev server (npm run dev, after npm run build) to test
• in console, returnAllStatevariables1()
• get two versions of state variables, first is actual javascript, document. second argument is simpler version.