Live Object Exploration: Observing and Manipulating Behavior and State of Java Objects
Total Page：16
File Type：pdf, Size：1020Kb
Live Object Exploration: Observing and Manipulating Behavior and State of Java Objects Benjamin Biegel, Benedikt Lesch, and Stephan Diehl Department of Computer Science University of Trier Trier, Germany Email: fbiegel,[email protected] Abstract—In this paper we introduce a visual representation of It is not surprising that developers try to avoid compre- Java objects that can be used for observing and manipulating be- hending the program behavior by solely reading the source havior and state of currently developed classes. It runs separately, code. In about 40% of the time spent for understanding a e.g., on a tablet, beside an integrated development environment. Within the visualization, developers are able to arbitrarily change certain code fragment, developers execute the program and the object state, then invoke any method with custom parameters investigate the code rational at runtime [5]. This includes a and observe how the object state changes. When changing the frequent use of debuggers [6], testing the program behavior source code of the related class, the visualization holds the by using the user interface as end-users will do [7], or simply previous object state and adapts the new behavior defined by using loggers or console outputs. Nevertheless, developers the underlying source code. This instantly enables developers to observe functionalities objects of a certain class have and are forced to permanently switch between the structural and how they manipulate their state, and especially, how source behavioral view on a program, which still is tedious and code changes influence their behavior. We implemented a first cognitively demanding. Furthermore, since the program state prototype as a touch-enabled web application that is connected is only changed temporarily, for subsequent executions, all to a conventional integrated development environment. In order changes to the program state must be re-applied manually. to gain first practical insights, we evaluated our approach in a pilot user study. A promising paradigm that addresses the previously men- tioned issues is live programming [8]–[10]. In general, live I. INTRODUCTION programming environments provide an infrastructure, that Current tools and research methods introduce many tech- enables developers to immediately recognize how state and niques that help developers to comprehend and manage their behavior of a running program are affected, when changing source code [1]. When syntax or compiler errors occur, for the underlying source code [11], [12]. Live programming example, modern integrated development environments pro- occurs in several application scenarios, e.g., creating user vide built-in features that immediately notify developers. What interfaces [13], in continuous testing [14], or when using an in- is more, syntax highlighting, displaying structural context in- situ debugger [15]. Recent studies show that live programming formation, automatic source code formatting, links for source significantly helps developers in finding and fixing bugs [16], code navigation, specialized visualizations like UML [2] and [17]. In particular, since live programming narrows the gap other features support understanding the overall structure of between editing and debugging, developers become aware of a software project. Nevertheless, the behavior (or semantics) newly introduced bugs more early. Nevertheless, when using of a certain code fragment is not observable. While creating object-oriented languages like Java, current live programming or changing source code, developers have to put themselves approaches have some limitations. Some only allow to execute into the role of a computer [3]. As for that, they are forced to the entire program, which makes it hard to investigate smaller execute code fragments mentally and guess how a code change parts in isolation. Others use a fine-grained view on runtime would affect state and behavior of the program at runtime [4]. data by putting it directly into or beside source code, e.g., This issue was nicely summarized by Chris Granger, who is line by line, which makes it hard to keep track of bigger mainly known for developing an interactive open-source IDE parts of the program. Beside program and source code level, named ‘Light Table’1: however, object-oriented languages also require observing on the object level, which is not explicitly supported by current “We are quite literally throwing darts in the dark live programming approaches. and praying that we at least hit the board. We simply This paper fills this gap by introducing an additional visual- cannot see what our programs do and that’s a huge ization representing Java objects. Such objects are instantiated problem whether you’re just starting out or have directly from classes developed within an IDE and can be written millions of lines of beautiful code.” explored by changing their states and invoking their methods. —Chris Granger, 20142 Changes in the underlying class will be injected into the 1http://lighttable.com/ “living objects” and can immediately be observed in the 2http://www.chris-granger.com/2014/03/27/toward-a-better-programming/ visualization. Fig. 1. A Screenshot from our prototype implementation displaying a living object of a class named “Motorcycle”. II. MAIN CONCEPT AND PROTOTYPE IMPLEMENTATION settings for showing and hiding several types of members, like The main idea of this paper is to bring live execution inherited members or constructors. Another way for filtering feedback to the development of Java classes. An advantage specific members is pinning. By clicking on the star symbol of live programming is that effects on the program execution in the upper right corner of any box, the related box can be can be observed continuously while changing the source pinned or unpinned. Changing the mode from “Show all” to code in the editor. As for that, we propose a visualization “Show pinned” (right side of the toolbar) hides all unpinned that (1) is permanently connected to an IDE, (2) represents boxes and shows only the selected ones. instances of currently developed classes, (3) ensures updating 2) Fields: In the head of a field box (green part) the name object behavior that comes with source code changes while of the field is displayed. In this first concept, we refrain from keeping the current object state, and (4) enables to observe and displaying type information to keep the layout more tidy. manipulate behavior and state of currently represented objects The value of the field is displayed in the lower white area. within the visualization. Depending on the type, the value is represented differently, e.g., a toggle button is used for boolean values, whereas for A. Live Object Exploration string values an input field is used. Arrays and objects are not As can be seen in Figure 1, the entire view is used to displayed directly on the main screen. They are only indicated visualize an object. Its fields (green), constructors (orange) by buttons that lead to a special dialog showing their array and methods (red) are represented as floating boxes. These elements and members respectively. If any number is saved in boxes can be rearranged by simple drag and drop gestures a field, developers can chose between a regular representation, with mouse or touch input. In the toolbar at the top, there are that is only displaying the current value, and a line chart tabs for switching between currently living objects. In order representation, that makes it possible to observe how the to distinguish between multiple objects of the same class, it is underlying value changed over time. With the button next to possible to rename the tabs. The + symbol on the right allows the star symbol one can toggle between both representations. to create new instances of classes from the currently opened 3) Changing Values: The object state can be changed project within the IDE. directly within the visualization by entering new field values. 1) Filtering: Because all members of an object, including In order to support an explorative interaction style, we also the inherited members, are shown per default, representing provide, besides entering new values solely with the keyboard, larger objects can be very complex. To solve this problem, we touch-optimized visual components like sliders and buttons to use two different filtering mechanisms. First, by clicking on the change the values interactively. Furthermore, instead of typing cog symbol in the upper right of the toolbar, a menu opens with a new value, the developer is also able to choose from a list CodePad [18] and our previous work [19] we suggest using a conventional desktop environment with an additional touch device. Furthermore, we wrote a plug-in for the IntelliJ IDE4 that handles the communication between IDE and web ap- plication. By using the reflection API of Java, this plug-in instantiates new objects, manipulates their state and invokes their methods. After changing the source code, a new object is being created based on previously chosen parameter values for the constructor. Then, based on the saved object state in the web application, the newly created object in the IDE will be updated immediately. It is worth mentioning that living objects in the web application and objects within the IDE are only loosely connected. That means, we synchronize structure and state manually. In contrast to standard Java techniques like serializing objects, this enables us to also change the structure of a living object without losing its state. C. Application Scenarios While elaborating our approach, we discussed several ap- Fig. 2. A dialog for creating a new object. plication scenarios. A classical live programming scenario is using the tool next to an IDE by a single developer. But also a pair programming setting is conceivable, as we have seen of predefined values. Field boxes that contain changed values in our study. The driver could concentrate on writing code are temporarily highlighted by changing its color. and the navigator could use our tool for testing the expected 4) Method Invocation: In order to explore the behavior of behavior.