Undo for anyone, anywhere, anytime

O’Brien, James; Shapiro, Marc

doi:10.1145/1133572.1133579

Cited by 11 publications

(12 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Advanced history manipulations therefore require recovery mechanisms to detect and cope with paradoxes. Systems like Joyce [22] and Script [3] reject commands that generate paradoxes. Cascading undo [6] takes a different approach, tracking forward through every conflicting command, and triggering undo mechanisms to remove the conflict(s).…”

Section: Error Recoverymentioning

confidence: 99%

“…Tree structures allow histories to diverge from a common past state, usually at the user's explicit command, so that several versions of a document can coexist in parallel. They enable exploration of alternative modifications of a single document [27] or the whole file system [22]. Finally, directed graph structures enable merging of parallel branches of history, such as those produced by multiple users [19] or from a single user's alternative designs [8].…”

Section: History Structurementioning

confidence: 99%

“…A number of these works address technical aspects of interacting with command histories, including how to visualize them [8,12,14] and navigate through them [22,24]. However items of prior work generally address separated problems or functionalities.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Causality

Nancel

Cockburn

2014

Proceedings of the SIGCHI Conference on Human Factors in Computing Systems

View full text Add to dashboard Cite

Simple history systems such as Undo and Redo permit retrieval of earlier or later interaction states, but advanced systems allow powerful capabilities to reuse or reapply combinations of commands, states, or data across interaction contexts. Whether simple or powerful, designing interaction history mechanisms is challenging. We begin by reviewing existing history systems and models, observing a lack of tools to assist designers and researchers in specifying, contemplating, combining, and communicating the behaviour of history systems. To resolve this problem, we present CAUSALITY, a conceptual model of interaction history that clarifies the possibilities for temporal interactions. The model includes components for the work artifact (such as the text and formatting of a Word document), the system context (such as the settings and parameters of the user interface), the linear timeline (the commands executed in real time), and the branching chronology (a structure of executed commands and their impact on the artifact and/or context, which may be navigable by the user). We then describe and exemplify how this model can be used to encapsulate existing user interfaces and reveal limitations in their behaviour, and we also show in a conceptual evaluation how the model stimulates the design of new and innovative opportunities for interacting in time.

show abstract

Section: Error Recoverymentioning

confidence: 99%

Section: History Structurementioning

confidence: 99%

See 1 more Smart Citation

Causality

Nancel

Cockburn

2014

Proceedings of the SIGCHI Conference on Human Factors in Computing Systems

View full text Add to dashboard Cite

show abstract

“…Certain systems [2,3] have been developed to address the issue, which presuppose errors on the part of the operator, provide undo utilities that allow the operator to roll a service back to a previous state, and minimize the Mean Time To Repair (MTTR) for higher availability; however, the systems take into account neither the diversity of services nor their dependency. The development of additional software components for each service is required for the adoption.…”

Section: Introductionmentioning

confidence: 99%

“…Moreover, their operational scope is restricted to a single service, and the resulting state is not necessarily consistent with that after past management tasks. We might exploit tools [4,5] for multi-vendor routers and switches; however, they are the same as the systems [2,3] in terms of the limited operational scope. This paper proposes a new network-wide rollback scheme for fast recovery from operator errors, as work in progress.…”

Section: Introductionmentioning

confidence: 99%

Proposal on Network-Wide Rollback Scheme for Fast Recovery from Operator Errors

Yoshihara

Arai

Idoue

et al. 2007

Managing Virtualization of Networks and Services

View full text Add to dashboard Cite

Abstract. This paper proposes a new network-wide rollback scheme for fast recovery from operator errors, toward the high availability of networks and services. A technical issue arises from the fact that operators, who manipulate one or more diverse devices and services due to their network-wide dependency in a typical management task, are the major cause of failure. The lack of systems or tools fully addressing the issue motivated us to develop a new scheme. The underlying idea is that, for any operational device or service, the observable behavior is identical whenever the same setting is configured. High availability will thus be achieved by rolling the settings that may cause an abnormal state by an operator error, back to past ones with which devices and services were stable. Certain policies for the network-wide rollback are identified and a prototype implementation and preliminary results will be presented.

show abstract

An Application Framework for Nomadic, Collaborative Applications

O’Brien

Shapiro

2006

Distributed Applications and Interoperable Systems

View full text Add to dashboard Cite

Abstract. To maintain availability and responsiveness, mobile applications sharing data often work on their own copy and transmit local changes to other participants. Existing systems for recording, transmitting and reconciling concurrent changes are usually ad-hoc and specific to particular applications. In contrast, we present Joyce; a general application programming framework for creating highly dynamic mobile, collaborative applications. The framework abstracts application semantics using an action-constraint formal model and provides communication and consistency services based on this model. The framework exposes an interface that allows application programmers to concentrate on core functionality without worrying about these issues. Applications made with the framework can run seamlessly across changing combination of devices, users and synchrony. We discuss the principles behind the framework, its implementation and evaluate its utility by creating a complex, shared application.

show abstract

Undo for anyone, anywhere, anytime

Abstract: Abstract

Cited by 11 publications

References 4 publications

Causality

Causality

Proposal on Network-Wide Rollback Scheme for Fast Recovery from Operator Errors

An Application Framework for Nomadic, Collaborative Applications

Contact Info

Product

Resources

About