Abstract: An example method facilitates modification and generation of User Interface (UI) display screens for webpages and web applications, such as process-based software applications. The example method includes receiving a first signal to access a webpage that includes a static UI display screen for a web application; serving the webpage in response to the signal; detecting the dynamic configuration functionality associated with the webpage, wherein the configuration functionality includes code and UI metadata provided in or with a dynamic layout file, the code and UI metadata including one or more rules and specifications for configuring schema used to generate rendering instructions for the dynamic part of the webpage.

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: An example method facilitates modification and generation of User Interface (UI) display screens for webpages and web applications, such as process-based software applications. The example method includes receiving a first signal to access a webpage that includes a static UI display screen for a web application; serving the webpage in response to the signal; detecting the dynamic configuration functionality associated with the webpage, wherein the configuration functionality includes code and UI metadata provided in or with a dynamic layout file, the code and UI metadata including one or more rules and specifications for configuring schema used to generate rendering instructions for the dynamic part of the webpage.

Abstract: An example method facilitates modification and generation of User Interface (UI) display screens for webpages and web applications, such as process-based software applications. The example method includes receiving a first signal to access a webpage that includes a static UI display screen for a web application; serving the webpage in response to the signal; detecting the dynamic configuration functionality associated with the webpage, wherein the configuration functionality includes code and UI metadata provided in or with a dynamic layout file, the code and UI metadata including one or more rules and specifications for configuring schema used to generate rendering instructions for the dynamic part of the webpage.

Abstract: An example system and method facilitates operation of a networked software application that communicates with a network resource during periods of intermittent network connectivity and includes determining when a networked software application is offline and when it is online; selectively intercepting one or more request messages from the networked software application addressed to a network resource when the software application is offline, resulting in a store of intercepted request messages; detecting when the networked software application transitions from being offline to being online; and selectively issuing the one or more request messages to the network resource in a sequence in which the one or more request messages were stored in the store of intercepted request messages.

Abstract: An example system and method facilitates operation of a networked software application during periods of intermittent network connectivity, by selectively intercepting and shredding and/or unshredding service response messages. In a specific embodiment, the example system includes one or more pluggable shredders and unshredders to explode a payload into its constituent structured primitive objects for ease of consumption by the User Interface (UI) of the client application. The exploded payloads are stored in local cache, where the cached data is structured as compared to the received payload. One or more unshredders selectively reconstruct one or more response message payloads if client reissues the corresponding request message while offline. The client may operate as if it is online, and the system will provide one or more mock responses containing the last known data set for the scenario wherein the server cannot be reached.

Abstract: A system for providing user assistance receives a request for user assistance from a component on a user interface. The component includes a help identifier, and the request is generated by a type of user selection, such as the clicking of an icon. The system determines a level of user assistance based on the type of selection and retrieves user assistance content based on the help identifier and the determined level of user assistance. In one embodiment, the user interface includes three levels of user assistance.

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 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: An example system and method facilitates operation of a networked software application that communicates with a network resource during periods of intermittent network connectivity and includes determining when a networked software application is offline and when it is online; selectively intercepting one or more request messages from the networked software application addressed to a network resource when the software application is offline, resulting in a store of intercepted request messages; detecting when the networked software application transitions from being offline to being online; and selectively issuing the one or more request messages to the network resource in a sequence in which the one or more request messages were stored in the store of intercepted request messages.

Abstract: An example system and method facilitates operation of a networked software application that communicates with a network resource during periods of intermittent network connectivity and includes determining when a networked software application is offline and when it is online; selectively intercepting one or more request messages from the networked software application addressed to a network resource when the software application is offline, resulting in a store of intercepted request messages; detecting when the networked software application transitions from being offline to being online; and selectively issuing the one or more request messages to the network resource in a sequence in which the one or more request messages were stored in the store of intercepted request messages.

Abstract: An example system and method facilitates operation of a networked software application, i.e., client application which communicates with a network resource (e.g., web service) during periods of intermittent network connectivity, by selectively intercepting and shredding and/or unshredding service response messages. In a specific embodiment, the example system includes one or more pluggable shredders and unshredders that are used to explode a complex REpresentational State Transfer (REST) payload into its constituent structured primitive objects for ease of consumption by the User Interface (UI) of the client application. The exploded, i.e., shredded response message payloads are stored in local cache, where the cached data is strategically structured as compared to the received REST payload. One or more unshredders selectively reconstruct one or more REST response message payloads if client reissues the corresponding REST request message while offline.

Abstract: An example system and method facilitates operation of a networked software application, i.e., client application which communicates with a network resource (e.g., web service) during periods of intermittent network connectivity, by selectively intercepting and shredding and/or unshredding service response messages. In a specific embodiment, the example system includes one or more pluggable shredders and unshredders that are used to explode a complex REpresentational State Transfer (REST) payload into its constituent structured primitive objects for ease of consumption by the User Interface (UI) of the client application. The exploded, i.e., shredded response message payloads are stored in local cache, where the cached data is strategically structured as compared to the received REST payload. One or more unshredders selectively reconstruct one or more REST response message payloads if client reissues the corresponding REST request message while offline.

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: 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: 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: An example system and method facilitates operation of a networked software application, i.e., client application which communicates with a network resource (e.g., web service) during periods of intermittent network connectivity, by selectively intercepting and shredding and/or unshredding service response messages. In a specific embodiment, the example system includes one or more pluggable shredders and unshredders that are used to explode a complex REpresentational State Transfer (REST) payload into its constituent structured primitive objects for ease of consumption by the User Interface (UI) of the client application. The exploded, i.e., shredded response message payloads are stored in local cache, where the cached data is strategically structured as compared to the received REST payload. One or more unshredders selectively reconstruct one or more REST response message payloads if client reissues the corresponding REST request message while offline.