Abstract: Systems and methods are described herein for enabling a user of a diagramming system to select elements of a diagram and apply a layout constraint thereto. In accordance with certain embodiments described herein, the systems and methods provide the user with a means to perform these tasks in a manner that is faster, easier and more intuitive than interfaces provided by conventional diagramming systems. For example, in accordance with at least one embodiment described herein, a single user gesture is obtained and the steps of selecting elements of a diagram to which a layout constraint is to be applied and selecting the layout constraint are both performed based on the single user gesture.

Abstract: Systems and methods are described herein for enabling a user of a diagramming system to select elements of a diagram and apply a layout constraint thereto. In accordance with certain embodiments described herein, the systems and methods provide the user with a means to perform these tasks in a manner that is faster, easier and more intuitive than interfaces provided by conventional diagramming systems. For example, in accordance with at least one embodiment described herein, a single user gesture is obtained and the steps of selecting elements of a diagram to which a layout constraint is to be applied and selecting the layout constraint are both performed based on the single user gesture.

Abstract: Systems and methods are described herein for enabling a user of a diagramming system to select elements of a diagram and apply a layout constraint thereto. In accordance with certain embodiments described herein, the systems and methods provide the user with a means to perform these tasks in a manner that is faster, easier and more intuitive than interfaces provided by conventional diagramming systems. For example, in accordance with at least one embodiment described herein, a single user gesture is obtained and the steps of selecting elements of a diagram to which a layout constraint is to be applied and selecting the layout constraint are both performed based on the single user gesture.

Abstract: A computer-implemented method for providing a design representation of a software system includes storing in a memory a dataset representative of a plurality of software code elements of the software system, wherein storing the dataset includes incorporating design data into the dataset, the design data being representative of respective design properties regarding the software code elements. A dataset query including a reference to an item of the dataset is received. The dataset query is implemented, with a processing unit in communication with the memory, over the dataset. Implementing the dataset query includes defining a subset of the dataset based on the reference to the item. A user interface rendered via an output device in communication with the processing unit user interface includes a view of the design representation of the software system in accordance with the defined subset of the dataset.

Abstract: A system and method for creating or editing a graph diagram. A system provides a mechanism to specify constraints on edge way points. Constraints may specify alignment with other way points, distribution of way points, spacing from other way points or nodes, or other types of constraints. A system may automatically determine edge way point constraints based on edge direction, edge type, target nodes or regions of nodes, or other characteristics of edges. The system enables a combination of constraints specified by a user and automatically determined by the system. Way points are positioned based on associated constraints, and edges are routed based on their associated way points.

Abstract: A system and method for managing the recognition and processing of gestures. A system provides a mechanism to detect conflicts between gesture recognizers and resolve the conflicts. A runtime system receives notifications from gesture recognizers in the form of requests for resources or actions. A conflict detector determines whether a conflict with another gesture recognizer exists. If a conflict exists, a conflict resolver determines a resolution. This may include determining a winning gesture recognizer and deactivating the losing gesture recognizers. A design time system statically validates gesture recognizers based on static state machines corresponding to each gesture recognizer.

Abstract: A system and method for creating or editing a graph diagram. A system provides a mechanism to specify constraints on edge way points. Constraints may specify alignment with other way points, distribution of way points, spacing from other way points or nodes, or other types of constraints. A system may automatically determine edge way point constraints based on edge direction, edge type, target nodes or regions of nodes, or other characteristics of edges. The system enables a combination of constraints specified by a user and automatically determined by the system. Way points are positioned based on associated constraints, and edges are routed based on their associated way points.

Abstract: Systems and methods are described herein for enabling a user of a diagramming system to select elements of a diagram and apply a layout constraint thereto. In accordance with certain embodiments described herein, the systems and methods provide the user with a means to perform these tasks in a manner that is faster, easier and more intuitive than interfaces provided by conventional diagramming systems. For example, in accordance with at least one embodiment described herein, a single user gesture is obtained and the steps of selecting elements of a diagram to which a layout constraint is to be applied and selecting the layout constraint are both performed based on the single user gesture.

Abstract: Use of declarative constraints in an error validation framework of a graphical modeling tool. The declarative constraints define one or more rules that objects of a graphical model should adhere to. When enforced against the graphical model, objects that do not conform to the rules may be identified. A declarative relationship between the non-conforming object and its visual representation in a graphical diagram may be used to allow for visually identifying the visual representation in the graphical diagram.

Abstract: The reuse of one or more shared components of graphical modeling tools amongst multiple graphical modeling tools. Graphical designers, or graphical modeling tools, allow for the construction of graphical representations of models in which objects, object properties, and object interrelationships may be visualized. Thus, a variety of graphical modeling tools may be supported and populated with portions of other graphical modeling tools.

Abstract: An abstraction can be used to describe interactions with a developer and development actions that should be automated. A recipe defines (1) arguments whose values may be collected to execute the actions, (2) value providers that can query the environment for argument values, (3) sequences of actions that are to be executed and how arguments are passed to the action, (4) methods to interact with the developer to get argument values from him, as opposed to getting the argument values through value providers, and (5) the capability whereby a recipe may spawn one or more further recipes, thereby allowing guidance to be revealed in stages and at the point it is needed.

Abstract: Source code of a graphical designer application may be generated from a definition of graphical elements that can be employed to develop graphical models using the graphical designer application, a definition of one or more object types that can be represented in graphical models developed using the graphical designer application, and a definition of a mapping between the one or more object types and the graphical elements. One or more of these definitions may be stored within a file formatted in accordance with a markup language such as SGML or XML. The graphical designer application may be customized and extended by modifying one or more of the definitions and regenerating the source code and/or by modifying the source code itself. One or more of the definitions may be generated based on a graphical designer template corresponding to a particular model domain.

Abstract: A designer tool that facilitates design of an object model. The tool takes as input a computer-readable representation of a graph of objects (e.g., classes), and creates automatically one or more diagrams that depict these classes as editable trees showing their relationships and properties. These graphs naturally have a tree-like structure which is exploited by the approach. The design tool system includes a layout component that receives as input one or more of the graphs, and converts the one or more graphs into the editable treelike structure. The system further comprises a presentation component that presents the editable treelike structure as a treelike structure diagram, and facilitates user interaction therewith. The tool can be used for opening, editing and saving existing object model files or to create new ones.