Abstract: A method of forming an insulated composite fabric including attaching an insulating-filler fabric layer to an outer fabric layer, where the insulating-filler fabric layer is a textile fabric with at least one raised surface on the fabric. One side of the insulating-filler layer has a first surface with relatively high pile, including regions of no pile or relatively low pile interspersed among regions of relatively high pile and the other side of the insulating-filler layer has a second surface with relatively high pile, including regions of no pile or relatively low pile interspersed among regions of relatively high pile. The method further contains coupling at least one of a fleece and velour that is respectively lower than the relatively high pile of the first surface or the relatively high pile of the second surface to at least one of the first surface and the second surface.

Abstract: Merging user interface (UI) object trees comprising UI trees from different technologies (e.g., host and one or more guest technologies) can involve registering guest technologies with a technology adapter layer, for example, used to manage UI tree merging. Further, identifying whether a UI object can be switched from a first technology to a second technology can comprise using a host technology provider to identify if a UI object can be switched, when navigating down the UI tree. When navigating up the UI tree, information stored by the technology adapter layer can be used to identify if a UI object can be switched. Additionally, identifying the second technology can comprise having the technology adapter layer request technology switching capability information from registered technologies for the UI object when navigating down the UI tree. When navigating up the UI tree, information stored by the technology adapter layer can be used to identify the second technology.

Abstract: A method, implementable in a system coupled to a display device and a network, includes generating in a first region of a screen of the display device a user-interface portion associated with a first electronic destination address. The user-interface portion is configured to receive from a second region of the screen, in response to a command by a user of the system, a first icon representing a data set. In response to the user-interface portion receiving the first icon, a copy of the data set, or the data set itself, is electronically transferred over the network to the first destination address.

Abstract: A system automatically builds custom virtual appliances and/or other computing environments and their components, where applicable, based on user requirements and may offer a service for hosting, maintaining, monitoring and managing such appliances remotely. These virtual appliances may be delivered over a network, such as the Internet, and can be run at a customer site or at a hosting provider. Some embodiments of the invention can build these appliances using custom applications developed by customers.

Abstract: Automation of actions on a server system (e.g., web server, FTP server) is facilitated by a server system that is ready for actions to be performed upon it. Because there are scenarios when a server system is not in a state to be acted upon (e.g., web page changed due to navigation, script execution, asynchronous request through dynamic web extensions), an automated action needs to be synchronized to when then server system is in a ready state for that action to occur. A wait-for-ready state can be initiated that detects when a server system is ready for a next action.

Abstract: Recording of functional steps resulting from actions in an application is desirable for performing functional testing or user interface automation of an application. However, certain events that may result from actions occurring in an application are often difficult to record, which may lead to playback failure. Further, a user's intent when performing an action is difficult to determine. In order to obtain effective playback, a reliable and efficient recording of an application's functional steps needs to occur. Injecting wrapper functions into an application and monitoring an event generator's state before and after an action has occurred may yield more reliable and effective results.

Abstract: Automation of actions on a server system (e.g., web server, FTP server) is facilitated by a server system that is ready for actions to be performed upon it. Because there are scenarios when a server system is not in a state to be acted upon (e.g., web page changed due to navigation, script execution, asynchronous request through dynamic web extensions), an automated action needs to be synchronized to when then server system is in a ready state for that action to occur. A wait-for-ready state can be initiated that detects when a server system is ready for a next action.

Abstract: Automation of actions on a server system (e.g., web server, FTP server) is facilitated by a server system that is ready for actions to be performed upon it. Because there are scenarios when a server system is not in a state to be acted upon (e.g., web page changed due to navigation, script execution, asynchronous request through dynamic web extensions), an automated action needs to be synchronized to when then server system is in a ready state for that action to occur. A wait-for-ready state can be initiated that detects when a server system is ready for a next action.

Abstract: Merging user interface (UI) object trees comprising UI trees from different technologies (e.g., host and one or more guest technologies) can involve registering guest technologies with a technology adapter layer, for example, used to manage UI tree merging. Further, identifying whether a UI object can be switched from a first technology to a second technology can comprise using a host technology provider to identify if a UI object can be switched, when navigating down the UI tree. When navigating up the UI tree, information stored by the technology adapter layer can be used to identify if a UI object can be switched. Additionally, identifying the second technology can comprise having the technology adapter layer request technology switching capability information from registered technologies for the UI object when navigating down the UI tree. When navigating up the UI tree, information stored by the technology adapter layer can be used to identify the second technology.

Abstract: Recording of functional steps resulting from actions in an application is desirable for performing functional testing or user interface automation of an application. However, certain events that may result from actions occurring in an application are often difficult to record, which may lead to playback failure. Further, a user's intent when performing an action is difficult to determine. In order to obtain effective playback, a reliable and efficient recording of an application's functional steps needs to occur. Injecting wrapper functions into an application and monitoring an event generator's state before and after an action has occurred may yield more reliable and effective results.

Abstract: A system automatically builds custom virtual appliances and/or other computing environments and their components, where applicable, based on user requirements and may offer a service for hosting, maintaining, monitoring and managing such appliances remotely. These virtual appliances may be delivered over a network, such as the Internet, and can be run at a customer site or at a hosting provider. Some embodiments of the invention can build these appliances using custom applications developed by customers.

Abstract: Automation of actions on a server system (e.g., web server, FTP server) is facilitated by a server system that is ready for actions to be performed upon it. Because there are scenarios when a server system is not in a state to be acted upon (e.g., web page changed due to navigation, script execution, asynchronous request through dynamic web extensions), an automated action needs to be synchronized to when then server system is in a ready state for that action to occur. A wait-for-ready state can be initiated that detects when a server system is ready for a next action.

Abstract: Various technologies and techniques are disclosed for providing direct synchronous input. An input monitor determines where an input from a sender that is directed to a target element is about to be delivered. One example for providing an input monitor includes using a system hook. If the input monitor determines that the input is about to be delivered to the target element, the input is delivered to the target element, and the sender is notified that delivery to the target element succeeded. An interface for providing a direct synchronous input is also described. The interface has a start method for monitoring inputs being sent to target elements from a sender. The interface also has a received event for notifying the sender when a particular input is received by the target element.