Abstract: Methods, systems, and computer-readable media are disclosed to provide change notification based on updates to an uncompiled software development project. A particular method includes detecting a project switch to a first software development project from an uncompiled second software development project. A metadata representation of one or more software entities associated with the second software development project is created. The method also includes updating a file including one or more proxy classes of the first software development project, where the proxy classes are updated based on the metadata representation. One or more clients of the first software development project are notified that the file has been updated.

Abstract: Development environments are commonly used to facilitate the development of user interfaces (e.g. windows forms, web forms, etc.). Drawing objects are components that may be used within the development environment to provide visual enhancements to the user interface. An effective method for drawing one or more drawing objects is disclosed herein to draw the drawing objects as windowless shapes within a shape container. The shape container may be configured to participate in a windows message loop (e.g. event handling system), wherein the windowless shapes do not participate in the windows message loop (e.g. lack a windows handle). The shape container listens, for example, within the windows message loop for operations pertaining to windowless shapes, and executes the operations upon the windowless shapes. Computer resources may be efficiently allocated, for example to the graphical user interface during runtime, instead of the windowless shapes consuming resources to participate in the windows message loop.

Abstract: In one embodiment, a computer system receives an indication that a portion of data at a first node in a first database table is to be modified according to a received update command. The computer system assigns the first database table a base height value indicating that the first database table is the base node in a search for related nodes, accesses one or more other database tables in the database, and identifies at least one other accessed database table that has a node with data related to the modified data of the first node. The computer system assigns the other accessed database table a height value different than that assigned to the base node, orders the first database table and any other identified database tables by assigned height value, and updates the data at each node based on the established height value ordering and the type of update command received.

Abstract: Form controls can be reused so that the control can be bound to large volumes of data without adverse performance issues because of a large number of controls. A maximum number of rows of data N that can appear in a form are calculated. A container in memory is created for N+2 rows. The additional two rows are used to store the row after the last displayed row and the row previous to the first displayed row. In response to a user scroll or tab operation, rows within the container are reused. Child controls are hosted by the control and are also reused when the data is scrolled out of view.

Abstract: Methods, systems, and computer-readable media are disclosed to provide change notification based on updates to an uncompiled software development project. A particular method includes detecting a project switch to a first software development project from an uncompiled second software development project. A metadata representation of one or more software entities associated with the second software development project is created. The method also includes updating a file including one or more proxy classes of the first software development project, where the proxy classes are updated based on the metadata representation. One or more clients of the first software development project are notified that the file has been updated.

Abstract: A system and method for method facilitating design-time data binding of business object(s) and/or web service(s) is provided. Developer(s) can specify their own class(es) that do not require specific inheritance, interface implementation or default public constructors. The system includes a binding component that generates control information associated with control(s) based, at least in part, upon binding information associated with an entity (e.g., object, business object and/or web service). The system further includes a control generator that generates control(s) of a form associated with the entity based upon the generated by the binding component. The binding component can utilize public property(ies) of the entity (e.g., object, business object and/or web service). The entity can represent a hierarchy of objects that drill down (e.g., endlessly), including circular relationships. At design-time, a user (e.g., developer) can drag the root of an object (e.g.

Abstract: A data source extensibility model establishes extensibility points to allow a data source window or integrated development environment to work with new data source providers and/or new designer technologies and/or new UI controls. Various object/entity management techniques are provided to orchestrate which component is present in given conditions.

Abstract: Form controls can be reused so that the control can be bound to large volumes of data without adverse performance issues because of a large number of controls. A maximum number of rows of data N that can appear in a form are calculated. A container in memory is created for N+2 rows. The additional two rows are used to store the row after the last displayed row and the row previous to the first displayed row. In response to a user scroll or tab operation, rows within the container are reused. Child controls are hosted by the control and are also reused when the data is scrolled out of view.

Abstract: Development environments are commonly used to facilitate the development of user interfaces (e.g. windows forms, web forms, etc.). Drawing objects are components that may be used within the development environment to provide visual enhancements to the user interface. An effective method for drawing one or more drawing objects is disclosed herein to draw the drawing objects as windowless shapes within a shape container. The shape container may be configured to participate in a windows message loop (e.g. event handling system), wherein the windowless shapes do not participate in the windows message loop (e.g. lack a windows handle). The shape container listens, for example, within the windows message loop for operations pertaining to windowless shapes, and executes the operations upon the windowless shapes. Computer resources may be efficiently allocated, for example to the graphical user interface during runtime, instead of the windowless shapes consuming resources to participate in the windows message loop.

Abstract: In one embodiment, a computer system receives an indication that a portion of data at a first node in a first database table is to be modified according to a received update command. The computer system assigns the first database table a base height value indicating that the first database table is the base node in a search for related nodes, accesses one or more other database tables in the database, and identifies at least one other accessed database table that has a node with data related to the modified data of the first node. The computer system assigns the other accessed database table a height value different than that assigned to the base node, orders the first database table and any other identified database tables by assigned height value, and updates the data at each node based on the established height value ordering and the type of update command received.

Abstract: A development system is provided. The system includes a workspace component to visually display one or more model components. A separation component automatically segments the model components into two or more project components. A synchronization component can be provided to automatically update at least one of the project components in view of changes made to at least one other project component.