Publication statistics

Pub. period:1991-2006
Pub. count:10
Number of co-authors:9


Number of publications with 3 favourite co-authors:

Christopher H. Brooks:
Brad A. Myers:
Richard G. McDaniel:



Productive colleagues

David Wolber's 3 most productive colleagues in number of publications:

Brad A. Myers:154
Richard G. McDanie..:5
Gene L. Fisher:3

Upcoming Courses

go to course
Become a UX Designer from scratch
go to course
User Research - Methods and Best Practices
Starts the day after tomorrow !

Featured chapter

Marc Hassenzahl explains the fascinating concept of User Experience and Experience Design. Commentaries by Don Norman, Eric Reiss, Mark Blythe, and Whitney Hess

User Experience and Experience Design !


Our Latest Books

The Glossary of Human Computer Interaction
by Mads Soegaard and Rikke Friis Dam
start reading
The Social Design of Technical Systems: Building technologies for communities. 2nd Edition
by Brian Whitworth and Adnan Ahmad
start reading
Gamification at Work: Designing Engaging Business Software
by Janaki Mythily Kumar and Mario Herger
start reading
The Social Design of Technical Systems: Building technologies for communities
by Brian Whitworth and Adnan Ahmad
start reading
The Encyclopedia of Human-Computer Interaction, 2nd Ed.
by Mads Soegaard and Rikke Friis Dam
start reading

David Wolber


Publications by David Wolber (bibliography)

 what's this?
Edit | Del

Wolber, David (2006): Political e-identity: campaign funding data and beyond. In: Fortes, Jos A. B. and MacIntosh, Ann (eds.) DG.O 2006 - Proceedings of the 7th Annual International Conference on Digital Government Research May 21-24, 2006, San Diego, California, USA. pp. 29-37.

Edit | Del

Wolber, David and Brooks, Christopher H. (2004): Associative sources and agents for zero-input publishing. In: Proceedings of the 2004 International Conference on the World Wide Web 2004. pp. 494-495.

This paper presents an associative agent that allows seamless navigation from one's own personal space to third-party associative sources, as well as the personal spaces of other users. The agent provides users with access to a dynamically growing list of information sources, all of which follow a common associative sources API that we have defined. The agent also allows users act as sources themselves and take part in peer-to peer knowledge sharing.

© All rights reserved Wolber and Brooks and/or ACM Press

Edit | Del

Wolber, David, Kepe, Michael and Ranitovic, Igor (2002): Exposing document context in the personal web. In: Gil, Yolanda and Leake, David (eds.) International Conference on Intelligent User Interfaces 2002 January 13-16, 2002, San Francisco, California, USA. pp. 151-158.

Reconnaissance agents show context by displaying documents with similar content to the one(s) the user currently has open. Research paper search engines show context by displaying documents that cite or are cited by the currently open document(s). We present a tool that applies such ideas to the personal web, that is, the space rooted in user documents but tightly connected to web documents as well. The tool organizes the personal web with a single topic hierarchy based on direct links, instead of the traditional file, bookmark, and (hidden) direct link hierarchies. The tool allows a user to easily navigate through related user and web documents, no matter whether the documents are related by directory-document, bookmark-document, direct-link, or even similar content relationships.

© All rights reserved Wolber et al. and/or ACM Press

Edit | Del

Wolber, David, Su, Yingfeng and Chiang, Yih Tsung (2002): Designing dynamic web pages and persistence in the WYSIWYG interface. In: Gil, Yolanda and Leake, David (eds.) International Conference on Intelligent User Interfaces 2002 January 13-16, 2002, San Francisco, California, USA. pp. 228-229.

WebSheets is a programming in the WYSIWYG interface tool for building dynamic web pages that access and modify databases. Without programming, designers can specify not only the presentation of a page, but the dynamic content as well. This capability is facilitated through a novel application of Programming by Example (PBE), Query by Example (QBE), and spreadsheet formulas within the WYSIWYG HTML editor environment.

© All rights reserved Wolber et al. and/or ACM Press

Edit | Del

Myers, Brad A., McDaniel, Richard G. and Wolber, David (2000): Intelligence in Demonstrational Interfaces. In Communications of the ACM, 43 (3) pp. 82-89.

Edit | Del

Wolber, David (1998): A Multiple Timeline Editor for Developing Multi-Threaded Animated Interfaces. In: Mynatt, Elizabeth D. and Jacob, Robert J. K. (eds.) Proceedings of the 11th annual ACM symposium on User interface software and technology November 01 - 04, 1998, San Francisco, California, United States. pp. 117-118.

This paper describes a new approach for the static viewing and editing of an animated interface that has been created with a Programming By Demonstration system. The approach is based on an event-based, multiple-timeline view that extends the traditional single timeline view found in systems such as Director. The result is a reduction in the amount of frame branching required to build an interface, and an ability to display some multi-threaded interfaces not in the range of the single timeline approach.

© All rights reserved Wolber and/or ACM Press

Edit | Del

Wolber, David (1997): Pavlov: An Interface Builder for Designing Animated Interfaces. In ACM Transactions on Computer-Human Interaction, 4 (4) pp. 347-386.

Conventional interface builders provide little support for interactive development of interfaces with application-specific graphics. Some Programming by Demonstration (PBD) systems do provide such support, but none provide full support for demonstrating interfaces, such as those in games, in which the graphics are animated. This article proposes a number of techniques for creating animated interfaces, all of which have been included in an exploratory system, Pavlov. Many of the techniques are based on the addition of timing controls to a form of PBD called stimulus-response demonstration. Others are based on an adaptation of a traditional animation time-line that integrates end-user interaction with animation. The article also evaluates Pavlov with (1) a comparison to other PBD systems in terms of the behaviors that can be specified interactively and (2) a report on an informal user study comparing development in Pavlov to development in a conventional interface builder.

© All rights reserved Wolber and/or ACM Press

Edit | Del

Wolber, David (1996): Pavlov: Programming by Stimulus-Response Demonstration. In: Tauber, Michael J., Bellotti, Victoria, Jeffries, Robin, Mackinlay, Jock D. and Nielsen, Jakob (eds.) Proceedings of the ACM CHI 96 Human Factors in Computing Systems Conference April 14-18, 1996, Vancouver, Canada. pp. 252-259.

Pavlov is a Programming By Demonstration (PBD) system that allows animated interfaces to be created without programming. Using a drawing editor and a clock, designers specify the behavior of a target interface by demonstrating stimuli (end-user actions or time) and the (time-stamped) graphical transformations that should be executed in response. This stimulus-response model allows interaction and animation to be defined in a uniform manner, and it allows for the demonstration of interactive animation, i.e., game-like behaviors in which the end-user (player) controls the speed and direction of object movement.

© All rights reserved Wolber and/or ACM Press

Edit | Del

Fisher, Gene L., Busse, Dale E. and Wolber, David (1992): Adding Rule-Based Reasoning to a Demonstrational Interface Builder. In: Mackinlay, Jock D. and Green, Mark (eds.) Proceedings of the 5th annual ACM symposium on User interface software and technology November 15 - 18, 1992, Monteray, California, United States. pp. 89-97.

This paper presents a demonstrational interface builder with improved reasoning capabilities. The system is comprised of two major components: an interactive display manager and a rule-based reasoner. The display manager provides facilities to draw the physical appearance of an interface and define interface behavior by graphical demonstration. The behavior is defined using a technique of stimulus-response demonstration. With this technique, an interface developer first demonstrates a stimulus that represents an action that an end user will perform on the interface. After the stimulus, the developer demonstrates the response(s) that should result from the given stimulus. As the behavior is demonstrated, the reasoner observes the demonstrations and draws inferences to expedite behavior definition. The inferences entail generalizing from specific behavior demonstrations and identifying constraints that define the generalized behavior. Once behavior constraints are identified, the reasoner sends them to the display manager to complete the definition process. When the interface is executed by an end-user, the display manager uses the constraints to implement the run-time behavior of the interface.

© All rights reserved Fisher et al. and/or ACM Press

Edit | Del

Wolber, David and Fisher, Gene L. (1991): A Demonstrational Technique for Developing Interfaces with Dynamically Created Objects. In: Rhyne, James R. (ed.) Proceedings of the 4th annual ACM symposium on User interface software and technology Hilton Head, South Carolina, United States, 1991, Hilton Head, South Carolina, United States. pp. 221-230.

The development of user interfaces is often facilitated by the use of a drawing editor. The user interface specialist draws pictures of the different "states" of the interface and passes these specifications on to the programmer. The user interface specialist might also use the drawing editor to demonstrate to the programmer the interactive behavior that the interface should exhibit; that is he might demonstrate to the programmer the actions that an end-user can perform and the graphical manner by which the application should respond to the end-user's stimuli. From the specifications, and the in-person demonstrations, the programmer implements a prototype of the interface. DEMO is a User Interface Development System (UIDS) that eliminates the programmer from the above process. Using an enhanced drawing editor, the user interface specialist demonstrates the actions of the end-user and the system, just as he would if the programmer were watching. However no programmer is necessary: DEMO records these demonstrations, makes generalizations from them, and automatically generates a prototype of the interface.

© All rights reserved Wolber and Fisher and/or ACM Press

Add publication
Show list on your website

Join our community and advance:




Join our community!

Page Information

Page maintainer: The Editorial Team