Abstract: An effector having an extendible range and a method for extending the range of an effector includes using an axially translatable center body that is movable from a stowed position, in which the center body is stowed in an outer body of the effector, to a deployed position in which the center body extends out of the outer body to extend the axial length of the effector. The effector includes a ramjet assembly and the subsystems of the effector are contained in the center body. The movement of the center body exposes radially positioned ramjet fuel in the outer body, such that the air entering the ramjet inlet may be heated by combusting the air with the fuel for additional fuel and propulsion of the effector.

Abstract: An effector having an extendible range and a method for extending the range of an effector includes using an axially translatable center body that is movable from a stowed position, in which the center body is stowed in an outer body of the effector, to a deployed position in which the center body extends out of the outer body to extend the axial length of the effector. The effector includes a ramjet assembly and the subsystems of the effector are contained in the center body. The movement of the center body exposes radially positioned ramjet fuel in the outer body, such that the air entering the ramjet inlet may be heated by combusting the air with the fuel for additional fuel and propulsion of the effector.

Abstract: The present invention extends to methods, systems, and computer program products for asynchronously binding data from a data source to a data target. A user interface thread and a separate thread are used to enable the user interface thread to continue execution rather than blocking to obtain updated data, to which elements of a user interface that the user interface thread is managing, are bound. The separate thread obtains updated data from a data source, stores the updated data in a local cache, and notifies the user interface thread of the updated data's presence in the local cache. The user interface thread, upon detecting the notification, accesses the updated data in the local cache and populates the updated data into the user interface.

Abstract: The present invention extends to methods, systems, and computer program products for asynchronously binding data from a data source to a data target. A user interface thread and a separate thread are used to enable the user interface thread to continue execution rather than blocking to obtain updated data, to which elements of a user interface that the user interface thread is managing, are bound. The separate thread obtains updated data from a data source, stores the updated data in a local cache, and notifies the user interface thread of the updated data's presence in the local cache.

Abstract: The present invention extends to methods, systems, and computer program products for asynchronously binding data from a data source to a data target. A user interface thread and a separate thread are used to enable the user interface thread to continue execution rather than blocking to obtain updated data, to which elements of a user interface that the user interface thread is managing, are bound. The separate thread obtains updated data from a data source, stores the updated data in a local cache, and notifies the user interface thread of the updated data's presence in the local cache. The user interface thread, upon detecting the notification, accesses the updated data in the local cache and populates the updated data into the user interface.

Abstract: The present invention extends to methods, systems, and computer program products for asynchronously binding data from a data source to a data target. A user interface thread and a separate thread are used to enable the user interface thread to continue execution rather than blocking to obtain updated data, to which elements of a user interface that the user interface thread is managing, are bound. The separate thread obtains updated data from a data source, stores the updated data in a local cache, and notifies the user interface thread of the updated data's presence in the local cache.

Abstract: Methods, systems, and computer program products to serialize user interface objects having custom object types and serialization formats. A serialization manager may coordinate standard serialization providers to identify standard serializers for standard object types or serialization formats, and as needed, may be extended by loading custom serialization providers to identify custom serializers for custom object types or serialization formats, which may not be covered by the standard serialization providers. From available serialization providers, the serialization manager identifies a serializer for a particular serialization format and object type. The object, custom or standard, is serialized using the identified serializer to a custom or standard format, including source code representations, XML representations, etc.

Abstract: Methods, systems, and computer program products that automatically generate and track undo information so that the developer of a user interface object need not be responsible for generating and tracking undo information. Change notifications for changes to an object within a visual user interface designer are processed. Data representing an initial state of the object prior to the changes and data representing a subsequent state of the object after the changes is persisted. From the persisted data, an undo unit is prepared for undoing the changes to the object. The undo unit may comprise a transaction of multiple changes made to the object. Each undo unit may identify corresponding routines for undoing and redoing the actions included within the undo unit. An undo unit may be stored until an undo/redo notification is received, and then used to undo/redo the changes represented by the undo unit.

Abstract: Methods, systems, and computer program products that automatically generate and track undo information so that the developer of a user interface object need not be responsible for generating and tracking undo information. Change notifications for changes to an object within a visual user interface designer are processed. Data representing an initial state of the object prior to the changes and data representing a subsequent state of the object after the changes is persisted. From the persisted data, an undo unit is prepared for undoing the changes to the object. The undo unit may comprise a transaction of multiple changes made to the object. Each undo unit may identify corresponding routines for undoing and redoing the actions included within the undo unit. An undo unit may be stored until an undo/redo notification is received, and then used to undo/redo the changes represented by the undo unit.

Abstract: Methods, systems, and computer program products to serialize user interface objects having custom object types and serialization formats. A serialization manager may coordinate standard serialization providers to identify standard serializers for standard object types or serialization formats, and as needed, may be extended by loading custom serialization providers to identify custom serializers for custom object types or serialization formats, which may not be covered by the standard serialization providers. From available serialization providers, the serialization manager identifies a serializer for a particular serialization format and object type. The object, custom or standard, is serialized using the identified serializer to a custom or standard format, including source code representations, XML representations, etc. Certain serialization formats produce a snippet of code without producing a class representation of an object.