Abstract: The present invention extends to methods, systems, and computer program products for assigning type parameters. Embodiments of the invention permit using a visual editor to edit arbitrary object instances in a graphical fashion. Instances of generic types can be manipulated to change the type parameters for that generic (to be able to change a List<Customer> to a List<Product>, for instance). Values are preserved and data can be patched to other dependent nodes in an object hierarchy.

Abstract: A viewer may be used to navigate through diagrammatic views of hierarchically structured documents. Expansion and collapse controls may be used to show or hide details regarding a particular node in the hierarchy. Furthermore breadcrumb navigation may be employed to show and hide details regarding the ancestral chain for a particular node in the hierarchy.

Abstract: The present invention extends to methods, systems, and computer program products for assigning type parameters. Embodiments of the invention permit using a visual editor to edit arbitrary object instances in a graphical fashion. Instances of generic types can be manipulated to change the type parameters for that generic (to be able to change a List<Customer> to a List<Product>, for instance).

Abstract: A viewer may be used to navigate through diagrammatic views of hierarchically structured documents. Expansion and collapse controls may be used to show or hide details regarding a particular node in the hierarchy. Furthermore breadcrumb navigation may be employed to show and hide details regarding the ancestral chain for a particular node in the hierarchy.

Abstract: The present invention extends to methods, systems, and computer program products for structured arrangement of visual endpoints in diagrams. Generally, endpoint arrangements are consistently used on shapes in a domain (diagram type) based on common information flow characteristics of the domain. In addition, shape specific positioning of endpoints can be based on a shape's unique characteristics. Diagrams are more readable across an organization because diagrams have a more consistent flow structure in the form of endpoints and connections. Diagrams are also easier to construct because endpoints have predictable locations.

Abstract: Developing a declarative workflow application. In a first instance of a workflow designer application, user input is received defining a declarative workflow definition with workflow elements. Some of the workflow elements may be dummy workflow elements having no underlying imperative code. This declarative workflow definition can be provided to a developer. The developer can cause the workflow definition to be loaded into a second instance of a workflow designer application where it is graphically displayed. The developer can provider user input in the second instance of the workflow designer selecting workflow elements to be replaced. Workflow elements can be replaced with existing replacement workflow elements, or by workflow elements developed by the developer to replace selected elements. Embodiments may also include the ability to in-line imperative code editors instantiated by selecting workflow elements to replace.