Normally, when editing an IKAROS XML file, one is faced with module definitions like the following:
Bark instead, provides GUI editing for the parameters associated with the module definitions.
C. G. Prince & E. J. Mislivec
24 September 2005
This document describes an editor for the XML files used as input for running networks of modules in the IKAROS (http://asip.lucs.lu.se/IKAROS/) system.
Module Definitions & Parameters
Normally, when editing an IKAROS XML file, one is faced with module definitions like the following:
Bark instead, provides GUI editing for the parameters associated with the module definitions.
Networks: Module Connections
Editing of the module parameters is provided through a network diagram. The network diagram is rendered based on the contents of the <connections> tag of the XML file. Normally, the contents of this tag look something like:
In Bark, the view looks like this:
In order to edit the parameters for a given module, the user places their cursor over the rectangle representing a particular module. For example, when the user places their cursor over the "outputAV" module, this changes the display to the following:
The user is now able to edit the values associated with the module parameters.
1) It may be useful to enable module definitions to be created, independent of any particular XML file. For example, this would allow for the full set of parameters for a module to be defined, and documented. Any particular XML file may not have the full set of parameters for a module defined, and documentation is not included. Also, this might include definition of the data types of parameters (e.g., int, string, float).
2) It may be useful to enable a collection of parameters, across modules, to have the same value. I'm thinking of file names here. In particular, the visual and audio module in networks for iSenseStream use the same file as input, and hence have the same filename parameter.