wiki:ModalityEngines

Adding engines for new modalities or embodiments

See [1]

Add a new behavior as description level of some (default) BML behavior

In your planner:

static
{
   ...   
   BMLInfo.addDescriptionExtension(MURMLFaceBehaviour.xmlTag(), MURMLFaceBehaviour.class);
}
...
@Override
public List<Class<? extends Behaviour>> getSupportedDescriptionExtensions()
{
   List<Class<? extends Behaviour>> list = new ArrayList<Class<? extends Behaviour>>();
   list.add(MURMLFaceBehaviour.class);
   ...
   return list;
}

When handling a the MURMLFaceBehaviour description in a piece of BML, the scheduler should now call addBehaviour and resolveSynchs in your planner with a MURMLFaceBehaviour.

The extension can now be used as follows:

<bml id="bml1" xmlns:murml="http://www.techfak.uni-bielefeld.de/ags/soa/murml">
<faceLexeme id="face1" start="2" lexeme="BLINK">
<description priority="1" type="murmlface">
<murml:murmlface start="2" id="face1">
...

with murmlface the xml tag of the extension and  http://www.techfak.uni-bielefeld.de/ags/soa/murml its namespace. Any timing constraints defined in the base behavior need to be repeated in the extension.

BiBTeX

Bibtex references stored on: BibTexElckerlycPublications

References

  1. ^Reidsma, Dennis and Welbergen, Herwin van, Elckerlyc in practice on the integration of a BML Realizer in real applications, Proc. of Intetain 2011, 2011, inproceedings,