As per: https://groups.google.com/forum/#!topic/trex-tgn/_Owo86jrieU

I've noticed that throughout documentation for stateful TRex manual, and many of the supplied traffic profiles, have this acronym "SFR" used.

doc example: https://trex-tgn.cisco.com/trex/doc/trex_manual.html#_traffic_profiles_provided_with_the_trex_package
traffic profile mix example: https://github.com/cisco-system-traff

For example:

async function C() {
  const res = await fetch();
  return res;
}

We want a way to rerun the fetch request, probably by rerendering the C component.

This would be beneficial simply because most other crates do this, including rustc. Authors of other crates would not have to make special clauses regarding the MIT only licence of rugl.

See this rationale for the full details.

We need to provide further documentation (beyond the README) to make the library approachable. This includes documentation in code (right now it's practically inexistent) and as a wiki book.

The OCR example which adds slack notifications should use an environment property in the project manifest instead of parameters.

https://github.com/nimbella/demo-projects/blob/bd922f8eb03e9345556ccc4f82b12b47ab61825f/ocr/project-slack-notification.yml#L12-L14

This is also needed for the Printer demo.

https://github.com/nimbella/demo-projects/blob/bd922f8eb03e9345556ccc4f82b12b47ab61825f

Allow caching queried attribute locations with AttributeLocation:

const cmd = ...;
const aPosition = dev.queryAttributeLocation(cmd, "a_position");
const aColor = dev.queryAttributeLocation(cmd, "a_color");

// .index property allows for getting the location
const positionLocation = a_position.index;

// toString() allows for use in computed properties
const attrs = dev