Limits...
ECCE Toolkit: Prototyping Sensor-Based Interaction

View Article: PubMed Central - PubMed

ABSTRACT

Building and exploring physical user interfaces requires high technical skills and hours of specialized work. The behavior of multiple devices with heterogeneous input/output channels and connectivity has to be programmed in a context where not only the software interface matters, but also the hardware components are critical (e.g., sensors and actuators). Prototyping physical interaction is hindered by the challenges of: (1) programming interactions among physical sensors/actuators and digital interfaces; (2) implementing functionality for different platforms in different programming languages; and (3) building custom electronic-incorporated objects. We present ECCE (Entities, Components, Couplings and Ecosystems), a toolkit for non-programmers that copes with these issues by abstracting from low-level implementations, thus lowering the complexity of prototyping small-scale, sensor-based physical interfaces to support the design process. A user evaluation provides insights and use cases of the kind of applications that can be developed with the toolkit.

No MeSH data available.


Web interface of the ECCE Authoring Environment to create an ecosystem: (1) add/edit new entities via the Entity & Components Editor and (2) define their behavior (Couplings Editor). By selecting an existing entity, a preview gives users a prompt feedback regarding the entity design. (3) Users can automatically generate the runtime code of the entities as well as the server logic (Ecosystem Code Generator).
© Copyright Policy - open-access
Related In: Results  -  Collection

License
getmorefigures.php?uid=PMC5375724&req=5

sensors-17-00438-f001: Web interface of the ECCE Authoring Environment to create an ecosystem: (1) add/edit new entities via the Entity & Components Editor and (2) define their behavior (Couplings Editor). By selecting an existing entity, a preview gives users a prompt feedback regarding the entity design. (3) Users can automatically generate the runtime code of the entities as well as the server logic (Ecosystem Code Generator).

Mentions: The toolkit implements a graphical web-based interface for authoring sensor-based physical interactions (Figure 1). The ECCE Authoring Environment provides three main modules (Figure 2):


ECCE Toolkit: Prototyping Sensor-Based Interaction
Web interface of the ECCE Authoring Environment to create an ecosystem: (1) add/edit new entities via the Entity & Components Editor and (2) define their behavior (Couplings Editor). By selecting an existing entity, a preview gives users a prompt feedback regarding the entity design. (3) Users can automatically generate the runtime code of the entities as well as the server logic (Ecosystem Code Generator).
© Copyright Policy - open-access
Related In: Results  -  Collection

License
Show All Figures
getmorefigures.php?uid=PMC5375724&req=5

sensors-17-00438-f001: Web interface of the ECCE Authoring Environment to create an ecosystem: (1) add/edit new entities via the Entity & Components Editor and (2) define their behavior (Couplings Editor). By selecting an existing entity, a preview gives users a prompt feedback regarding the entity design. (3) Users can automatically generate the runtime code of the entities as well as the server logic (Ecosystem Code Generator).
Mentions: The toolkit implements a graphical web-based interface for authoring sensor-based physical interactions (Figure 1). The ECCE Authoring Environment provides three main modules (Figure 2):

View Article: PubMed Central - PubMed

ABSTRACT

Building and exploring physical user interfaces requires high technical skills and hours of specialized work. The behavior of multiple devices with heterogeneous input/output channels and connectivity has to be programmed in a context where not only the software interface matters, but also the hardware components are critical (e.g., sensors and actuators). Prototyping physical interaction is hindered by the challenges of: (1) programming interactions among physical sensors/actuators and digital interfaces; (2) implementing functionality for different platforms in different programming languages; and (3) building custom electronic-incorporated objects. We present ECCE (Entities, Components, Couplings and Ecosystems), a toolkit for non-programmers that copes with these issues by abstracting from low-level implementations, thus lowering the complexity of prototyping small-scale, sensor-based physical interfaces to support the design process. A user evaluation provides insights and use cases of the kind of applications that can be developed with the toolkit.

No MeSH data available.