Abstract: The structuring of data items in a hierarchical structure. A user interface permits a user to define, for each generation of a hierarchical tree, the child characteristics for child data items of particular nodes in the hierarchical tree. Then, a query, or a query template, may be formulated using the child characteristic and the designated parent data item. This may be repeatedly performed to allow for multiple generations of data items to be formed. The query may, at some point, be submitted to identify which data items are child data items or the parent data item. The data items that result from the query (or at least a portion of the data items) may then be assigned as child data items of the parent data item. The query may be postponed until the node is expanded by the user.

Abstract: Data-driven configuration of various views on data models. A framework may be provided that offers one or more parameterized view generation components, each aimed at generating a particular view type in response to configuration data that populates the parameters of the associated component. A user or other computing entity merely provides configuration data to an appropriate view generation component to generate a custom view. That custom view may then optionally perhaps be applied to any number of data models, or perhaps not applied to any data model at all and just saved for perhaps some future use. This view generation may generate composite views on a data model, or even hierarchical views on a data model.

Abstract: The present invention extends to methods, systems, and computer program products for smart gestures for diagram state transitions. Embodiments of the invention expose a set of gestures and behaviors, which permit diagram transitions to be made with a reduced number of (and potentially a single) user gesture(s). For example, zoom levels can be toggled between a working zoom level and a zoom level sufficient to present an entire diagram and vice versa using a single user input gesture. Likewise, diagrams can be appropriately (and automatically) panned to make selected as well as newly created diagram elements visible in their entirety using a single user input gesture.

Abstract: The structuring of data items in a hierarchical structure. A user interface permits a user to define, for each generation of a hierarchical tree, the child characteristics for child data items of particular nodes in the hierarchical tree. Then, a query, or a query template, may be formulated using the child characteristic and the designated parent data item. This may be repeatedly performed to allow for multiple generations of data items to be formed. The query may, at some point, be submitted to identify which data items are child data items or the parent data item. The data items that result from the query (or at least a portion of the data items) may then be assigned as child data items of the parent data item. The query may be postponed until the node is expanded by the user.

Abstract: The display in a scrollable window of large data sets, which is not loaded into memory all at one time. Rather, a control module manages the scrollable window by repeatedly estimating data ranges of the data set that are to be either presently displayed or that may soon be displayed in the scrollable window. In response to each of at least some of such estimations, the estimated data ranges are then loaded into memory without loading the entire data set into memory. At least portions of the loaded data may then be displayed in the scrollable window. If the scrollable window is scrolled to a particular portion of the data set, but that portion of the data set is not yet loaded into memory, scrolling is permitted to that area even though the actual data is populated into the window after loading.

Abstract: Data-driven configuration of various views on data models. A framework may be provided that offers one or more parameterized view generation components, each aimed at generating a particular view type in response to configuration data that populates the parameters of the associated component. A user or other computing entity merely provides configuration data to an appropriate view generation component to generate a custom view. That custom view may then optionally perhaps be applied to any number of data models, or perhaps not applied to any data model at all and just saved for perhaps some future use. This view generation may generate composite views on a data model, or even hierarchical views on a data model.