• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

Advanced Search Include Citations

Tools

Sorted by:
Try your query at:
Semantic Scholar Scholar Academic
Google Bing DBLP
Results 1 - 10 of 135
Next 10 →

Separating Application Code from Toolkits: Eliminating the Spaghetti of Call-Backs

by Brad A. Myers - SIGGRAPH SYMPOSIUM ON USER INTERFACE SOFTWARE AND TECHNOLOGY, PROCEEDINGS UIST’91. HILTON HEAD, SC, NOV.1991 , 1991
"... Conventional toolkits today require the programmer to attach call-back procedures to most buttons, scroll bars, menu items, and other widgets in the interface. These procedures are called by the system when the user operates the widget in order to notify the application of the user’s actions. Unfort ..."
Abstract - Cited by 71 (14 self) - Add to MetaCart
Conventional toolkits today require the programmer to attach call-back procedures to most buttons, scroll bars, menu items, and other widgets in the interface. These procedures are called by the system when the user operates the widget in order to notify the application of the user’s actions

Lynx: A Programmatic SAT Solver for the RNA-folding Problem

by Vijay Ganesh, Charles W. O’donnell, Mate Soos, Srinivas Devadas, Martin Rinard, O Solar-lezama
"... Abstract. This paper introduces Lynx, an incremental programmatic SAT solver that allows non-expert users to easily introduce domain-specific code into modern Conflict-driven Clause-learning (CDCL) SAT solvers, thus enabling users to control the behavior of the solver in ways not possible otherwise. ..."
Abstract - Cited by 1 (1 self) - Add to MetaCart
. The key idea of Lynx is an easy-to-use callback interface that enables non-expert users to specialize the SAT solver to a class of Boolean instances by allowing user-provided code to examine partial solutions generated by the solver during its search, and to dynamically and incrementally add CNF clauses

Separating Application Code From Toolkits: Eliminating The Spaghetti of Call-Backs

by Brad A. Myers , 1991
"... Conventional toolkits today require the programmer to attach call-back procedures to most buttons, scroll bars, menu items, and other widgets in the interface. These procedures are called by the system when the user operates the widget in order to notify the application of the user's action ..."
Abstract - Add to MetaCart
Conventional toolkits today require the programmer to attach call-back procedures to most buttons, scroll bars, menu items, and other widgets in the interface. These procedures are called by the system when the user operates the widget in order to notify the application of the user

Course: Component-Based Software Development

by Teacher Dr, Keith Leonard Mannock , 2005
"... Components and interfaces- of callbacks and contracts ..."
Abstract - Add to MetaCart
Components and interfaces- of callbacks and contracts

Lynx: A high-resolution synthetic aperture radar

by S. I. Tsunoda, F. Pace, J. Stence, M. Woodring, W. H. Hensley, A. W. Doerry, B. C. Walker
"... Lynx is a high resolution, synthetic aperture radar (SAR) that has been designed and built by Sandia National Laboratories in collaboration with General Atomics (GA). Although Lynx may be operated on a wide variety of manned and unmanned platforms, it is primarily intended to be fielded on unmanned ..."
Abstract - Cited by 1 (0 self) - Add to MetaCart
(minimum) spotlight images or of 0.3 m resolution (minimum) strip images. The Lynx user interface features a view manager that allows it to pan and zoom like a video camera. Lynx was developed under corporate funding from GA and will be manufactured by GA for both military and commercial applications

WASH/CGI: Server-side Web Scripting with Sessions and Typed, Compositional Forms

by Peter Thiemann - Practical Aspects of Declarative Languages: 4th International Symposium, PADL 2002, volume 2257 of LNCS , 2002
"... The common gateway interface (CGI) is one of the prevalent methods to provide dynamic contents on the Web. Since it is cumbersome to use in its raw form, there are many libraries that make CGI programming easier. WASH/CGI is a Haskell library for server-side Web scripting. Its implementation relies ..."
Abstract - Cited by 67 (3 self) - Add to MetaCart
The common gateway interface (CGI) is one of the prevalent methods to provide dynamic contents on the Web. Since it is cumbersome to use in its raw form, there are many libraries that make CGI programming easier. WASH/CGI is a Haskell library for server-side Web scripting. Its implementation relies

Behavioral Interface Contracts for Java

by Robert Bruce Findler , Matthias Felleisen , 2000
"... Programs should consist of off-the-shelf, interchangeable, black-box components that are produced by a network of independent software companies. These components should not only come with type signatures but also with contracts that describe other aspects of their behavior. One way to express contr ..."
Abstract - Cited by 4 (0 self) - Add to MetaCart
between components and trigger callbacks. Another problem is that object-oriented languages allow objects to satisfy several interfaces at once. In this paper, we analyze existing approaches to adding contracts to class-based languages and show how they blame the wrong component in certain situations

The Interface Between Distributed Operating System and High-Level Progrnmming Language

by Michael L. Scott - Proceedings of the 1986 International Conference on Parallel Processing , 1986
"... A distributed operating system provides a process abstraction and primitives for communication between processes. A distributed programming language regularizes the use of the primitives, making them both safer and more convenient. The level of abstraction of the primitives, and therefore the divisi ..."
Abstract - Cited by 18 (11 self) - Add to MetaCart
the division of labor between the operating system and the language support routines, has serious ramifications for efficiency and flexibility. Experience with three implementations of the LYNX distributed programming language suggests that functions that can be implemented on either side of the interface

User Interface Continuations

by Dennis Quan David, David Huynh, David R. Karger, Robert Miller - Proceedings of UIST 2003 , 2003
"... Dialog boxes that collect parameters for commands often create ephemeral, unnatural interruptions of a program's normal execution flow, encouraging the user to complete the dialog box as quickly as possible in order for the program to process that command. In this paper we examine the idea of t ..."
Abstract - Add to MetaCart
of turning the act of collecting parameters from a user into a first class object called a user interface continuation. Programs can create user interface continuations by specifying what information is to be collected from the user and supplying a callback (i.e., a continuation) to be notified

Architectural Implications of Common Operator Interfaces

by Richard N. Taylor, Nenad Medvidovic, Peyman Oreizy , 1998
"... If a common operator interface (COI) for satellite ground systems is built with conventional user interface (UI) technology, then there is substantial risk that the UI will end up determining a significant part of the ground system's architecture. UI technology typically forces applications to ..."
Abstract - Add to MetaCart
to be constructed as a set of call-backs to the UI. To avoid this situation an approach is required which sharply divides the user interface part of the system from the rest of the software. If the ground system is to run on heterogeneous hardware platforms a second sharp separation is also recommended
Next 10 →
Results 1 - 10 of 135
Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University