Experiences in using Java on a software tool integration project
John Grundy,John Hosking,Rick Mugridge +2 more
- 26 Jan 1998
- pp 286-293
TL;DR: This work describes the experiences in developing the Banquet set of integrated software development tools, initially using C++, and then Java as the tool interfacing and implementation and languages, and identifies where the advantages of a Java-based approach lie.
read more
Abstract: Building and integrating complex software development tools is a difficult task, but one which can result in great usability and productivity gains for software development. We describe our experiences in developing the Banquet set of integrated software development tools, initially using C++, and then Java as the tool interfacing and implementation and languages. We identify where, for us, the advantages of a Java-based approach lie.
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
Engineering for Human-Computer Interaction
Stéphane Chatty,Prasun Dewan +1 more
- 01 Jan 1999
TL;DR: This paper presents and defines a new paradigm for user interface design, Embodied User Interfaces, and places it in the evolution of user interface paradigms leading towards the ideal of an invisible user interface.
19
Engineering Component-based, User-configurable Collaborative Editing Systems
John Grundy
- 14 Sep 1998
TL;DR: This work describes the recent work in adding collaborative editing support onto a previously single-user CASE tool, using a component-based approach that allows users to move from asynchronous to synchronous editing as desired, and even allow a user to support different levels of collaborative editing with different other users simultaneously.
A Component-Oriented Architecture for the CASE-Tool AUTOFOCUS
Klaus Bergner,Andreas Rausch,Marc Sihling,bergner rausch sihling +3 more
- 01 Jan 1999
TL;DR: This case study concentrates on the repository subsystem, as this is the most critical component with respect to the overall design and has strong implications on the possible working modes available to the developers.
1
Controversy Corner: A new research agenda for tool integration
M. N. Wicks,R. G. Dewar +1 more
TL;DR: A timely analysis and review of many of the significant projects in the field is provided and an empirical manifesto for future research is proposed, where the need for work to justify tool integration efforts in terms of relevant socio-economic indicators is seen.
References
Groupware: some issues and experiences
TL;DR: C categories and examples of groupware are described and some underlying research and development issues are discussed and GROVE, a novel group editor, is explained in some detail as a salient groupware example.
Connecting tools using message passing in the Field environment
TL;DR: An overview is given of the Field environment, which was developed to show that highly integrated, interactive environments like those on PCs can be implemented on workstations and can be used for classical-language and large-scale programming.
PECAN: Program Development Systems that Support Multiple Views
TL;DR: The PECAN family of program development systems is designed to make effective use of powerful personal machines with high-resolution graphics displays and is currently implemented on APOLLO workstations.
330
Pecan: Program development systems that support multiple views
Steven P. Reiss
- 26 Mar 1984
TL;DR: PECAN as mentioned in this paper is a family of program development systems that support multiple views of the user's program, including expression trees, data type diagrams, flow graphs, and symbol tables.
313
Interacting with the FIELD Environment
TL;DR: The key concepts behind FIELD are an integration mechanism based on a simple, central message server, an annotation editor for integrating access to the source file with the other tools, and the use of a high‐level user interface toolset.
117