Abstract: A method creates a data grid component in a GUI. The data grid includes data cells, header cells, corner cells, and may further include footer cells. The data grid component may have headers or footers that contain a scale and/or a ruler that relates to graphs shown in a row or column associated with the header or footer. The scale and/or ruler may be horizontal or vertical. The GUI component may allow for multilevel navigation. One level allows for navigating from component to component in the GUI, including the data grid and any other components. Another level allows for navigating within a component, including in the data grid. Available user navigation inputs include level change commands, for example tied to specific keys.

Abstract: A method creates a data grid component in a GUI. The data grid includes data cells, header cells, corner cells, and may further include footer cells. A header, footer, or corner cell includes a software component that allows a user to enter valid data only, such as a date picker or a time picker. The date picker displays a month, a day, and a year, and has controls for changing the date.

Abstract: A method creates a data grid component in a GUI. The data grid includes data cells, header cells, corner cells, and may further include footer cells. The data grid component may have headers or footers that contain a scale and/or a ruler that relates to graphs shown in a row or column associated with the header or footer. The scale and/or ruler may be horizontal or vertical. The GUI component may allow for multilevel navigation. One level allows for navigating from component to component in the GUI, including the data grid and any other components. Another level allows for navigating within a component, including in the data grid. Available user navigation inputs include level change commands, for example tied to specific keys.

Abstract: A method creates a data grid component in a GUI. The data grid includes data cells, header cells, corner cells, and may further include footer cells. A header, footer, or corner cell includes a software component that allows a user to enter valid data only, such as a date picker or a time picker. The date picker displays a month, a day, and a year, and has controls for changing the date. The data grid component may have headers or footers that contain a scale and/or a ruler that relates to graphs shown in a row or column associated with the header or footer. The scale and/or ruler may be horizontal or vertical. The GUI component may allow for multilevel navigation. One level allows for navigating from component to component in the GUI, including the data grid and any other components. Another level allows for navigating within a component, including in the data grid. Available user navigation inputs include level change commands, for example tied to specific keys.

Abstract: A data grid software component has data cells with a style that may be template-based or individual. A data cell may include a software component to show and interact with a bitmap, a graph, a chart, streaming graphics, or streaming bitmaps. The data grid may have footers, headers, and corner cells each capable of holding another software component to show and interact with several data forms. A header, a footer, and a corner cell can each have a style that is template-based or individual. Headers and footers may have multiple levels. Header parts and footer parts at different levels may have a style that is template-based or individual.

Abstract: Techniques are disclosed for event-based architectures for implementing expand-collapse input-output operations in user interfaces. Certain techniques are disclosed herein that allow for a expand and/or collapse functionality via passing asynchronous events to a datasource module, which may or may not be routed through a view module. The datasource module determines what data is to be shown or hidden and issues an insert/delete event back to the view module. The insert/delete event may include additional data to be inserted into the user interface, and may include an identifier of where, within the displayed user interface, data is to be inserted or deleted. A view module may be configured to receive insert or delete events, and, in response, cause the user interface to be modified based upon the event. The view module may perform these updates by inserting or removing Document Object Model (DOM) nodes from a DOM associated with the user interface.

Abstract: Techniques are disclosed for the efficient display of hierarchical datasets using high-water mark scrolling. Certain techniques allow for the creation of simple, intuitive, and computationally inexpensive user interfaces for displaying hierarchical data sets. According to some embodiments, a defined number of items of a hierarchical list are presented in a hierarchical user interface module. This defined number of items may be referred to as a “high-water mark” value. When one of the items having associated child items (that are not currently displayed) is selected, one or more presented items in the hierarchical list are replaced with a corresponding one or more of the child items, thus maintaining a same number of displayed list items (i.e., the high-water mark number of displayed list items).

Abstract: Dual timeline visualizations include a detail timescale shown along two item regions. Display objects shown in an item region may represent events, activities, or multiple stacked events and activities from a set of chronological data items. Display objects have positions and sizes representing those of the corresponding events and activities, and may include data-related or user-selected colors and/or hashing. The detail timescale, in unison with the item regions, may be scrollable and resizable in the direction of time. The item regions may be separately scrollable and resizable in another direction. A visualization may also include an overview panel representing a summary view of both sets of chronological data items, with its own timescale, and a lens showing the position of the detail timescale and item regions.

Abstract: A visualization displays a portion of a big data set in a control in a browser-based GUI. The browser may support HTML and the control may include a DOM element. The control includes a canvas for rendering the big data portion. To create the visualization, the smaller of the browser's maximum canvas size and the big data set's candidate canvas size is determined. The canvas is sized accordingly. A page in the canvas is filled with initial data and the visualization is displayed with a scrollbar. Upon receiving a user input, it is determined if the user input denotes a short or long scroll. It is also determined if the scroll reaches an end of the scrollbar. Data is fetched from a relative location in the big data set in proportion with the relative scroll position, and respecting the data set and canvas limits.

Abstract: Tooltip generation for zoom feedback is described. In response to the initiation of a zoom operation, a tooltip is generated. The tooltip shows an established potential zoom level that will be used to execute the zoom operation if no other zoom level is established or selected. Multiple potential zoom levels may be shown within the tooltip before the zoom operation is executed.

Abstract: Techniques for facilitating navigation in a web-based data entry grid. In one set of embodiments, when a user navigates into a cell of the data entry grid, the user's web browser can wait for a predetermined time period before accessing an application server to retrieve input control information for the cell. If the user enters a command to navigate away from the cell before the predetermined time period has passed, the server access can be avoided, and thus the navigation event can be processed immediately. If no navigation command is received from the user before the predetermined time period has passed, the input control information can be retrieved from the application server and rendered.

Abstract: A process visualization toolkit includes micro-component templates and application programmer's interfaces (APIs) to build a process visualization and show it in a graphical user interface (GUI) on a computer screen. Micro-components share compatible display properties that relate to process visualization. The APIs allow customization, but also allow mixing micro-components with components in standard technologies, such as HTML. Shared properties include display settings, position settings, time settings, and the time type (calendar time, work time, relative time). A time axis micro-component includes functions to convert time to pixel position, and pixel position to time, based on the time type. Developers add functionality and interactive functions using a standard language such as JavaScript, and may customize display rendering using, for example, cascaded stylesheets.

Abstract: A data grid software component has data cells with a style that may be template-based or individual. A data cell may include a software component to show and interact with a bitmap, a graph, a chart, streaming graphics, or streaming bitmaps. The data grid may have footers, headers, and corner cells each capable of holding another software component to show and interact with several data forms. A header, a footer, and a corner cell can each have a style that is template-based or individual. Headers and footers may have multiple levels. Header parts and footer parts at different levels may have a style that is template-based or individual.

Abstract: A data grid software component has data cells with a style that may be template-based or individual. A data cell may include a software component to show and interact with a bitmap, a graph, a chart, streaming graphics, or streaming bitmaps. The data grid may have footers, headers, and corner cells each capable of holding another software component to show and interact with several data forms. A header, a footer, and a corner cell can each have a style that is template-based or individual. Headers and footers may have multiple levels. Header parts and footer parts at different levels may have a style that is template-based or individual.

Abstract: A table display presents animation to show changes in sorting and/or filtering criteria, providing users with visual references about the sorting operation and illustrating relationships between data elements before and after sorting, including data that was off-screen prior to sorting. A table presents a portion of a data element set arranged according to a first sorting criteria, such as the data field value in each data element. Upon receiving a second sorting criteria, a new arrangement of the data elements visible in the table is determined. Animation data is determined to specify the motion of visible and non-visible data elements from their locations under the first sorting criteria to their locations under the second sorting criteria. The transition animation is then initiated to show the movement of data elements from their locations under the first sorting criteria to their locations under the second sorting criteria.

Abstract: A visualization displays a portion of a big data set in a control in a browser-based GUI. The browser may support HTML and the control may include a DOM element. The control includes a canvas for rendering the big data portion. To create the visualization, the smaller of the browser's maximum canvas size and the big data set's candidate canvas size is determined. The canvas is sized accordingly. A page in the canvas is filled with initial data and the visualization is displayed with a scrollbar. Upon receiving a user input, it is determined if the user input denotes a short or long scroll. It is also determined if the scroll reaches an end of the scrollbar. Data is fetched from a relative location in the big data set in proportion with the relative scroll position, and respecting the data set and canvas limits.

Abstract: A data grid software component has data cells with a style that may be template-based or individual. A data cell may include a software component to show and interact with a bitmap, a graph, a chart, streaming graphics, or streaming bitmaps. The data grid may have footers, headers, and corner cells each capable of holding another software component to show and interact with several data forms. A header, a footer, and a corner cell can each have a style that is template-based or individual. Headers and footers may have multiple levels. Header parts and footer parts at different levels may have a style that is template-based or individual.

Abstract: A process visualization toolkit includes micro-component templates and application programmer's interfaces (APIs) to build a process visualization and show it in a graphical user interface (GUI) on a computer screen. Micro-components share compatible display properties that relate to process visualization. The APIs allow customization, but also allow mixing micro-components with components in standard technologies, such as HTML. Shared properties include display settings, position settings, time settings, and the time type (calendar time, work time, relative time). A time axis micro-component includes functions to convert time to pixel position, and pixel position to time, based on the time type. Developers add functionality and interactive functions using a standard language such as JavaScript, and may customize display rendering using, for example, cascaded stylesheets.

Abstract: Tooltip generation for zoom feedback is described. In response to the initiation of a zoom operation, a tooltip is generated. The tooltip shows an established potential zoom level that will be used to execute the zoom operation if no other zoom level is established or selected. Multiple potential zoom levels may be shown within the tooltip before the zoom operation is executed.

Abstract: Tooltip generation for zoom feedback is described. In response to the initiation of a zoom operation, a tooltip is generated. The tooltip shows an established potential zoom level that will be used to execute the zoom operation if no other zoom level is established or selected. Multiple potential zoom levels may be shown within the tooltip before the zoom operation is executed.