Having Fun With Evaluation

Brel, Christian; Gonin, Philippe Renevier; Giboin, Alain; Riveill, Michel; Dery, Anne-Marie

doi:10.14236/ewic/hci2014.1

Cited by 4 publications

(1 citation statement)

References 25 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Task modeling in these frameworks can use the ConcurTaskTrees notation [17] that contains specifications of user or system actions in each task, as well as temporal relations and data streams across them. ConcurTaskTrees are also used by other frameworks for UI generation such as Dygimes [6], OntoCompo [2], UsiComp [10], and MARIA (Model-based language for interactive applications) [18]. Dygimes uses ConcurTaskTrees along with an XML-based language to describe UI building blocks, and utilizes a set of constraints to generate UIs for mobile and embedded systems.…”

Section: Model-based Developmentmentioning

confidence: 99%

Yeti

Karuzaki

Savidis

2015

Proceedings of the 7th ACM SIGCHI Symposium on Engineering Interactive Computing Systems

View full text Add to dashboard Cite

As applications become larger, building their UI is getting harder. While a lot of research focuses on new ways of building UIs, little work focuses on reusing existing UI components to automatically compose large-scale interfaces. This paper introduces Yeti, an automatic UI composer for desktop and android applications written in Java, that adopts a task-driven discipline where task hierarchy denotes component containment and control. We propose the notion of globally unique task identifiers to avoid task naming confusions across components and repositories. To enable applications set mandatory control aspects for the retrieved UI components, we introduce required APIs as part of task definitions. Yeti emphasizes the composition of reusable coarse-grained UI components rather than automatic UI creation from scratch, so no lowerlevel specifications are deployed. Retrieved and composed components can be directly handled inside application logic via the application-defined APIs and the generic component interface required for all components. This programmingoriented approach allows UI programmers to deploy Yeti as a software library, while it enables the mix of composed UI parts with manually coded ones. To validate our system and demonstrate its deployment, we present an example application created from existing components.

show abstract

Section: Model-based Developmentmentioning

confidence: 99%