Abstract: Embodiments provide techniques for tracking the lifecycles of client-side browser windows in the context of a web application. In an embodiment, a server component of a web application can receive a notification that an application page in a first window has been unloaded. In response, the server component can associate the first window with an expiration time and add the first window to an expiration list of windows that are potentially inactive. If a request is received by the server component from the first window while the first window is in the expiration list, the server component can identify the first window as active and remove it from the list. If a request is received by the server component from a second window after the expiration time associated with the first window, the server component can identify the first window as inactive and free all resources for the first window.

Abstract: In one set of embodiments, a web document is associated with a style sheet that can include style rules, which provide details about how the document is to be presented and formatted by, for example, a web browser. A reduced set of style rules is determined based upon contents of the web document and style sheet. Reducing the size of the style sheet is desirable, e.g., to increase communication and processing efficiency when the style sheet is sent with the document in an e-mail message. The reduced set of style rules can include rules that are referenced by user interface components present in the document, and can exclude rules that are not referenced by the document, or are incompatible with or not applicable to e-mail. The reduced set of style rules can be embedded in an e-mail message or other communication in place of the original style sheet.

Abstract: In one set of embodiments, a web document is associated with a style sheet that can include style rules, which provide details about how the document is to be presented and formatted by, for example, a web browser. A reduced set of style rules is determined based upon contents of the web document and style sheet. Reducing the size of the style sheet is desirable, e.g., to increase communication and processing efficiency when the style sheet is sent with the document in an e-mail message. The reduced set of style rules can include rules that are referenced by user interface components present in the document, and can exclude rules that are not referenced by the document, or are incompatible with or not applicable to e-mail. The reduced set of style rules can be embedded in an e-mail message or other communication in place of the original style sheet.

Abstract: In one set of embodiments, methods, systems, and apparatus are provided that include presenting, by a computer system, a task flow in a popup component of an application user interface executing in a user interface layer, where the task flow executes in an application layer of the computer system, and also include communicating, by the computer system, a first notification from the application layer to the user interface layer in response to normal completion of the task flow, and updating, e.g., closing, the component in the application user interface based upon the first notification. A second notification may be communicated from the user interface layer to the application layer in response to a user interface event that is associated with the popup component and causes an abnormal termination of the task flow. Presenting may include displaying the task flow in a region component in the popup component.

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: In one set of embodiments, methods, systems, and apparatus are provided that include presenting, by a computer system, a task flow in a popup component of an application user interface executing in a user interface layer, where the task flow executes in an application layer of the computer system, and also include communicating, by the computer system, a first notification from the application layer to the user interface layer in response to normal completion of the task flow, and updating, e.g., closing, the component in the application user interface based upon the first notification. A second notification may be communicated from the user interface layer to the application layer in response to a user interface event that is associated with the popup component and causes an abnormal termination of the task flow. Presenting may include displaying the task flow in a region component in the popup component.

Abstract: Embodiments of the present invention provide techniques for tracking the lifecycles of client-side browser windows in the context of a web application. In one set of embodiments, a server component of a web application can receive a request originating from a client-side browser window, where the request includes a resource locator (e.g., a URL) and a window identifier. In response, the server component can send a script to the window for retrieving the window's actual identifier/name. Based on the actual identifier returned by the script and the window identifier included in the initial request, the server component can determine whether the window is a new window or an existing window and can process the request as appropriate.

Abstract: A system generates a computer user interface by including a tag in an area of the user interface that corresponds to a task flow component. The task flow component includes a plurality of sub-pages and control flow for the sub-pages. The user interface receives the task flow component and displays a current task flow sub-page within the area of the user interface and enables the control flow.

Abstract: A system and method for facilitating authoring computer code to facilitate rendering a display of data via a user interface display screen. An example method includes accepting a signal from a user input device to specify an attribute in accordance with a definition of a class of attributes in a data model; providing the specification of the attribute to a software component characterizing a webpage, wherein the software component includes an indicator for dynamic rendering of at least a portion of data included in the data model and associated with the attribute; and storing the definition of the class of attributes and data associated with the attribute, for retrieval and rendering of the data on a target device. The example method may include providing a mechanism for modifying attributes of the data model and propagating data model changes to webpage computer code.

Abstract: In various embodiments, one or more visual elements are introduced with menu item that indicate that action on this item has already been performed at least once. In various aspects, a distinctive icon can be placed with a menu item to indicate that a search field has been previously added to a search form, that a column has been added to a report, or that existing data or queries under construction have been modified by the action on an indicated item.

Abstract: Embodiments of the present invention provide techniques for tracking the lifecycles of client-side browser windows in the context of a web application. In one set of embodiments, a server component of a web application can receive a request originating from a client-side browser window, where the request includes a resource locator (e.g., a URL) and a window identifier. In response, the server component can send a script to the window for retrieving the window's actual identifier/name. Based on the actual identifier returned by the script and the window identifier included in the initial request, the server component can determine whether the window is a new window or an existing window and can process the request as appropriate.

Abstract: Embodiments of the present invention provide techniques for tracking the lifecycles of client-side browser windows in the context of a web application. In one set of embodiments, a server component of a web application can receive a request originating from a client-side browser window, where the request includes a resource locator (e.g., a URL) and a window identifier. In response, the server component can send a script to the window for retrieving the window's actual identifier/name. Based on the actual identifier returned by the script and the window identifier included in the initial request, the server component can determine whether the window is a new window or an existing window and can process the request as appropriate.

Abstract: Embodiments provide techniques for tracking the lifecycles of client-side browser windows in the context of a web application. In an embodiment, a server component of a web application can receive a notification that an application page in a first window has been unloaded. In response, the server component can associate the first window with an expiration time and add the first window to an expiration list of windows that are potentially inactive. If a request is received by the server component from the first window while the first window is in the expiration list, the server component can identify the first window as active and remove it from the list. If a request is received by the server component from a second window after the expiration time associated with the first window, the server component can identify the first window as inactive and free all resources for the first window.

Abstract: An automated test tool interface is described. A developer of a reusable web component provides an interface for obtaining an accurate identification of a root element of a component and any sub elements within the root element on a web page. An automated test framework uses this interface when recording automated tests to obtain a stable identification of the element that is independent of the rendering of the component on the web page. When the automated test is played back, the test framework again uses the interface to convert the stable identification of the element to a form that is dependent on the rendering of the component on the web page. Thus, changes in the rendering of a component will no longer cause an automated test tool to fail, as element identification in the testing framework is no longer tied to the specific rendering of the web page.

Abstract: Embodiments of the present invention provide techniques for tracking the lifecycles of client-side browser windows in the context of a web application. In one set of embodiments, a server component of a web application can receive a notification that an application page in a first window has been unloaded/destroyed. In response, the server component can associate the first window with an expiration time and add the first window to an “expiration” list of windows that are potentially inactive. If a request is received by the server component from the first window while the first window is in the expiration list, the server component can identify the first window as active and remove it from the list. If a request is received by the server component from a second window after the expiration time associated with the first window, the server component can identify the first window as inactive and free all resources for the first window.

Abstract: A system and method for facilitating automatically adjusting a user interface display screen or portion thereof. An example method includes determining context information associated with data, wherein the data is maintained in accordance with a data model; generating a signal when the context information changes; and employing the signal to automatically configure one or more characteristics of a user interface architecture, resulting in an adjusted user interface architecture. The context information may include information specifying one or more attributes relating to the data model. Generating may further include analyzing the one or more attributes to determine a modification to be made to the user interface architecture and then rendering a user interface display screen based on a modified user interface architecture.

Abstract: A system and method for facilitating characterizing data to enable dynamic generation of a user interface feature based on the data. An example method includes maintaining data in accordance with a data model accessible to webpage computer code, wherein the data model is adapted to be populated with data associated with one or more data attributes in the data model; and providing a signal, identifying a data attribute, from the data model to webpage computer code to facilitate dynamic construction of one or more user interface features characterizing a rendering of a webpage. Data in the data model is characterized by one or more data attributes, each of which is associated with an attribute definition. The example method may further include organizing one or more attribute definitions in the data model as computing objects containing characterizations of the one or more data attributes.

Abstract: A system and method for facilitating authoring computer code to facilitate rendering a display of data via a user interface display screen. An example method includes accepting a signal from a user input device to specify an attribute in accordance with a definition of a class of attributes in a data model; providing the specification of the attribute to a software component characterizing a webpage, wherein the software component includes an indicator for dynamic rendering of at least a portion of data included in the data model and associated with the attribute; and storing the definition of the class of attributes and data associated with the attribute, for retrieval and rendering of the data on a target device. The example method may include providing a mechanism for modifying attributes of the data model and propagating data model changes to webpage computer code.

Abstract: In various embodiments, one or more visual elements are introduced with menu item that indicate that action on this item has already been performed at least once. In various aspects, a distinctive icon can be placed with a menu item to indicate that a search field has been previously added to a search form, that a column has been added to a report, or that existing data or queries under construction have been modified by the action on an indicated item.