Method of displaying and editing properties of artifacts in graphical editors

A method, apparatus and computer-usable medium for improved management of object properties in an integrated development environment (IDE). A cursor mode allows the underlying properties of one or more predetermined objects in a graphical editor to be dynamically viewed and modified by a user. One or more object's properties are displayed in an object properties pop-up viewer/editor window adjacent to the cursor when a user “mouses-over” target objects in a graphical editor and are editable upon explicit user gesture. The properties pop-up viewer/editor window is implementable to move with the cursor, i.e., cursor-attached, and to remain open to dynamically display, without additional user gestures, the respective properties of each predetermined object a user mouses-over.

BACKGROUND OF THE INVENTION

The present invention relates in general to the field of computers and other data processing systems including hardware, software, and processes. More particularly, it relates to the interactive viewing and modification of object properties in a graphical integrated development environment (IDE).

Integrated development environments (IDEs) have grown in popularity with software developers in recent years. Current IDEs include functionalities for authoring, editing, compiling and debugging software, generally through the implementation of a graphical interface that conveys the appearance of all development being performed within a single application. The graphical interface typically comprises separate windows or panes for the display of software objects and their properties and includes an editor that allows users to control artifacts through direct manipulation of their visual representations. An artifact within the graphical editor is typically selected through a user gesture and, once selected, a separate dialog window or pane is opened to read, write, or modify its properties. The resulting, disjointed display is inefficient as it requires the user to visually switch between the editor view and the properties dialog/view of each object they wish to inspect or modify. In some cases, the object's properties view may be minimized or closed, requiring additional user gestures to manually access, view and modify its contents.

It is not always desirable for the editor window and the properties dialog/view window to be open at the same time. If the editor window is maximized to provide the greatest amount of work area, the user will often need to minimize or exit the editor window and then access and open the properties dialog/view window to display a selected object's properties. Once the viewing or editing of object properties is completed, the user reverses the process to return to the graphical editor. This sequence of processes can be awkward, error-prone and time consuming. Conversely, if the properties dialog/view window is kept open, it either reduces the total work area available for use by the graphical editor (e.g., in the case of a docked properties view) or it obscures a portion of the graphical editor's work area (e.g., in the case of a floating dialog window).

Previous approaches include property dialog or inspector windows that float above a graphical editor work space. These property dialog/views can be displayed on-demand and generally do not consume as much workspace as static windows or panes. However, they typically open in their last-used location, requiring the user to maintain their positional orientation between the property dialog/view and the selected object. Furthermore, the user is still required to visually switch between the selected object and the property dialog/view.

Other existing approaches include pop-up windows that display embedded information regarding an object. However, pop-up windows in these approaches are not implemented to display the properties of a selected object in a graphical editor, nor do they display the properties of multiple objects. Furthermore, they do not move with the cursor (i.e., cursor-attached), their content does not change dynamically when the cursor hovers over an object, nor is their content editable upon explicit gesture. In view of the foregoing, there is a need for improved management of an object's properties in a graphical IDE.

SUMMARY OF THE INVENTION

The present invention provides a method, apparatus and computer-usable medium for improved management of object properties in an integrated development environment (IDE). In the present invention, a cursor mode is implemented to allow the underlying properties of one or more predetermined objects in a graphical editor to be dynamically viewed and modified by a user. In various embodiments of the invention, when a user “mouses-over” a target object in a graphical editor, the object's properties are displayed in an object properties pop-up (prop-pop-up) viewer/editor window next to the cursor. In these embodiments, the user is not required to visually switch between the editor view of an object and a separate dialog window or pane. Therefore, the field of view remains within the editor and the vicinity of the object's visual representation.

In an embodiment of the invention, a prop-pop-up window is implemented to open adjacent to the position of the cursor. In another embodiment of the invention, a single prop-pop-up window is implemented to display property information for two or more predetermined objects in a graphical editor, thereby removing the need to open two or more prop-pop-up windows and switch between them to compare the properties of their respective objects. In yet another embodiment of the invention, a prop-pop-up window is implemented to move with the cursor (i.e., cursor-attached) and remain open to dynamically display, without additional user gestures, the respective properties of each predetermined object a user mouses-over in a graphical editor. In this embodiment of the invention, browsing of object properties is faster as users can view an object's properties by simple mouse-over events instead of executing a user gesture for each object to be examined.

In yet another embodiment of the invention, object properties displayed in the prop-pop-up window are visually adjacent to the object's location in the graphical editor and are editable upon explicit user gesture. In this embodiment of the invention, response time to view object properties is optimized as properties are displayed without their editing widgets. Widgets needed to edit object properties (e.g., dropdown boxes, text areas, etc.) are loaded with an explicit user gesture (e.g., clicking on the properties area). Furthermore, fewer mouse movements are required to edit object properties, since the prop-pop-up window is close to the mouse. The above, as well as additional purposes, features, and advantages of the present invention will become apparent in the following detailed written description.

DETAILED DESCRIPTION

A method, apparatus and computer-usable medium are disclosed for improved management of object properties in an integrated development environment (IDE). In various embodiments of the invention, a cursor mode is implemented that allows the underlying properties of one or more predetermined objects in a graphical editor to be dynamically viewed and modified by a user.

Any suitable computer usable or computer readable medium may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, or a magnetic storage device. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, or store the program for use by or in connection with the instruction execution system, apparatus, or device.

FIG. 1is a block diagram of an exemplary client computer102in which the present invention may be utilized. Client computer102includes a processor unit104that is coupled to a system bus106. A video adapter108, which controls a display110, is also coupled to system bus106. System bus106is coupled via a bus bridge112to an Input/Output (I/O) bus114. An I/O interface116is coupled to I/O bus114. The I/O interface116affords communication with various I/O devices, including a keyboard118, a mouse120, a Compact Disk-Read Only Memory (CD-ROM) drive122, a floppy disk drive124, and a flash drive memory126. The format of the ports connected to I/O interface116may be any known to those skilled in the art of computer architecture, including but not limited to Universal Serial Bus (USB) ports.

Client computer102is able to communicate with a service provider server150via a network128using a network interface130, which is coupled to system bus106. Network128may be an external network such as the Internet, or an internal network such as an Ethernet Network or a Virtual Private Network (VPN). Using network128, client computer102is able to use the present invention to access service provider server150.

A hard drive interface132is also coupled to system bus106. Hard drive interface132interfaces with a hard drive134. In a preferred embodiment, hard drive134populates a system memory136, which is also coupled to system bus106. Data that populates system memory136includes client computer102's operating system (OS)138and application programs144.

OS138includes a shell140for providing transparent user access to resources such as application programs144. Generally, shell140is a program that provides an interpreter and an interface between the user and the operating system. More specifically, shell140executes commands that are entered into a command line user interface or from a file. Thus, shell140(as it is called in UNIX®), also called a command processor in Windows®, is generally the highest level of the operating system software hierarchy and serves as a command interpreter. The shell provides a system prompt, interprets commands entered by keyboard, mouse, or other user input media, and sends the interpreted command(s) to the appropriate lower levels of the operating system (e.g., a kernel142) for processing. While shell140generally is a text-based, line-oriented user interface, the present invention can also support other user interface modes, such as graphical, voice, gestural, etc.

As depicted, OS138also includes kernel142, which includes lower levels of functionality for OS138, including essential services required by other parts of OS138and application programs144, including memory management, process and task management, disk management, and mouse and keyboard management.

Application programs144may include a browser146. Browser146includes program modules and instructions enabling a World Wide Web (WWW) client (i.e., client computer102) to send and receive network messages to the Internet using HyperText Transfer Protocol (HTTP) messaging, thus enabling communication with service provider server150.

Application programs144in client computer102's system memory also include a policy validator148. Policy validator148includes code for implementing the processes described inFIGS. 2-5described hereinbelow. In one embodiment, client computer102is able to download policy validator148from a service provider server150.

The hardware elements depicted in client computer102are not intended to be exhaustive, but rather are representative to highlight components used by the present invention. For instance, client computer102may include alternate memory storage devices such as magnetic cassettes, Digital Versatile Disks (DVDs), Bernoulli cartridges, and the like. These and other variations are intended to be within the spirit and scope of the present invention.

FIG. 2is a generalized flowchart of an implementation of object property pop-up viewer/editor (prop-pop-up)148as used in accordance with an embodiment of the invention for the viewing and editing of the properties of a predetermined object depicted in a graphical editor comprising an integrated development environment (IDE). In step202, the user begins object property viewing and editing operations within a graphical editor comprising an IDE. In step204, a first object is selected within the graphical editor through a first mouse-over user gesture (e.g., right-mouse-click) to view its properties. In an embodiment of the invention, prop-pop-up viewer/editor148is implemented to open adjacent to the position of the cursor as a user mouses-over an object depicted in a graphical editor to display its properties. In another embodiment of the invention, prop-pop-up viewer/editor148is implemented to move with the cursor (i.e., cursor-attached) and remain open to dynamically display the respective properties of each depicted object a user mouses-over in a graphical editor.

If the user decides to select a second object to compare its properties to the first selected object in step206, it is selected in step208through a second mouse-over user gesture (e.g., ctrl-right-mouse-click). Step206and step208are then iteratively repeated to select additional objects to compare their respective properties. In one embodiment of the invention, prop-pop-up viewer/editor148is implemented to display the respective properties of two or more predetermined objects depicted in a graphical editor, thereby removing the need to open two or more prop-pop-up windows and switch between them to compare the properties of their respective objects.

If the user decides in step210to view, but not edit, the respective properties of predetermined objects that have been selected in a graphical editor, then the respective object properties are viewed in step216as described in greater detail hereinabove. In an embodiment of the invention, response time to view object properties (i.e., read-only) in the prop-pop-up window is optimized as properties are displayed without their editing widgets. If, in step218, the user decides to view or edit the properties of other or additional objects depicted in a graphical editor, the process is repeated beginning with step204. Otherwise, object property viewing and editing operations within a graphical editor comprising an IDE is ended in step220. If the user decides in step210to edit the respective properties of predetermined objects that have been selected in a graphical editor, then a predetermined mouse-over user gesture (e.g., double-right-mouse-click) alters the behavior of prop-pop-up viewer/editor148to allow the user to edit object properties in step214as described in greater detail hereinabove. In one embodiment of the invention, object properties displayed in the prop-pop-up window are visually adjacent to the object's location in the graphical editor and editable upon explicit user gesture. Widgets needed to edit object properties (e.g., dropdown boxes, text areas, etc.) are loaded with an explicit user gesture (e.g., double-right-mouse-click). Furthermore, fewer mouse movements are required to edit object properties, since the prop-pop-up window is close to the cursor. If, in step218, the user decides to view or edit the properties of other or additional objects depicted in a graphical editor, the process is repeated beginning with step204. Otherwise, object property viewing and editing operations within a graphical editor comprising an IDE is ended in step220.

FIG. 3is a generalized illustration of an integrated development environment (IDE) as implemented with a graphical editor and a prior art object properties viewer/editor. In this illustration, graphical user interface (GUI)302comprises IDE304, which comprises graphical directory structure306, graphical project structure308, graphical editor310and prior art object properties viewer/editor312. Graphical directory structure406and graphical project structure308are used for navigation between various components comprising IDE304. Graphical editor310allows users to control artifacts through direct manipulation of their visual representations. As typically implemented, an artifact within the graphical editor is selected through a user gesture, and once selected, prior art object properties viewer/editor312is opened to read, write, or modify its properties. It will be apparent to those of skill in the art that the resulting, disjointed display is inefficient as it requires the user to visually switch between the editor view and the properties dialog/view of each object they wish to inspect or modify. Furthermore, as described in greater detail hereinabove, it is not always desirable for the editor window and the properties dialog/view window to be open at the same time as the total work area available for use by the graphical editor is reduced.

FIGS. 4a-bare generalized illustrations of object property pop-up viewer/editor (prop-pop-up)148as implemented in accordance with an embodiment of the invention for the viewing of object properties in an IDE. In these illustrations, graphical user interface (GUI)302comprises IDE304, which comprises graphical directory structure306, graphical project structure308, graphical editor310, cursor412, and object prop-pop-up viewer/editor148. Graphical directory structure306and graphical project structure308are used for navigation between various components comprising IDE304. Graphical editor310allows users to control artifacts through direct manipulation of their visual representations. InFIG. 4a, prop-pop-up viewer/editor148is implemented to open adjacent to the position of the cursor412as a user mouses-over an object depicted in graphical editor310to display its properties. InFIG. 4b, prop-pop-up viewer/editor148is implemented to move with the cursor412(i.e., cursor-attached) and remain open to dynamically display the respective properties of each depicted object a user mouses-over in graphical editor310. In another embodiment of the invention, response time to view object properties (i.e., read-only) in prop-pop-up viewer/editor148is optimized as properties are displayed without their editing widgets.

FIG. 5is a generalized illustration of object prop-pop-up viewer/editor as implemented in accordance with an embodiment of the invention for the editing of object properties in an IDE. In this illustration, graphical user interface (GUI)302comprises IDE304, which comprises graphical directory structure306, graphical project structure308, graphical editor310, cursor412, and object prop-pop-up viewer/editor148. Graphical directory structure306and graphical project structure308are used for navigation between various components comprising IDE304. Graphical editor310allows users to control artifacts through direct manipulation of their visual representations. In one embodiment of the invention, prop-pop-up viewer/editor148is implemented to open adjacent to the position of the cursor412as a user mouses-over an object depicted in graphical editor310to view its properties in an edit mode. In another embodiment of the invention, prop-pop-up viewer/editor148is implemented to move with the cursor412(i.e., cursor-attached) and remain open to dynamically display the respective properties of each depicted object a user mouses-over in graphical editor310such that they can be edited.

While the present invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. Furthermore, as used in the specification and the appended claims, the term “computer” or “system” or “computer system” or “computing device” includes any data processing system including, but not limited to, personal computers, servers, workstations, network computers, main frame computers, routers, switches, Personal Digital Assistants (PDAs), telephones, and any other system capable of processing, transmitting, receiving, capturing and/or storing data.