Abstract: There are methods and apparatus, including computer program products, for preventing data loss. For example, there is a client agent that automatically performs a data loss prevention action in response to detecting (i) a client navigation event and (ii) a difference between a client data state and a base data state, wherein the detection of the difference between the client data state and the base data state occurs without transmitting data to and from a server. The data loss prevention action can include generating a user prompt. The navigation event can include a navigation that replaces a user interface that the user had used to modify data associated with an application program. The data loss prevention action can be performed without receiving instructions corresponding to the action from the application program.

Abstract: Methods and apparatus, including computer program products, for representing hierarchical list data. One method involves receiving a first list comprising an element A1 and an element A2, the element A2 comprising a first nested list comprising an element N1 and an element N2; receiving a second list comprising an element B1 and an element B2, the element B2 comprising a second nested list comprising an element M1 and an element M2; storing the elements A1 and B1 in a first array; and storing the elements A2 and B2 in a second array, the second array comprising a first sub-array to store the elements N1 and M1, and a second sub-array to store the N2 and M2.

Abstract: Methods and apparatus, including computer program products, for processing a user interaction with an application, such as a browser-based application. A user interaction with the browser-based application is detected at a software framework. The browser-based application is executing in a browser at a local computer system. The user interaction is processed at the software framework, where processing includes determining whether the user interaction can be handled locally or requires access to a resource at a remote computer system. The user interaction is processed based on a result of the determination. A data item representative of the user interaction can be created at the software framework and stored at a data store. The data item can later be retrieved and the user interaction represented by the data item reprocessed at the software framework to replay the user interaction.

Abstract: An XML client abstraction layer for providing an XML page description as an abstraction of an HTML page at design time. A style sheet XSLT translator is used to derive the run time code from the XML page. Additional features or improvements may be added through an XML parser.

Abstract: There are methods and apparatus, including computer program products, for generating an integrated trace output file on a system having a first computing device and a second computing device. The first computing device generates a first trace output and receives a second trace output from the second computing device. The first computing device generates an integrated trace output file by combining the second trace output with the first trace output.

Abstract: Methods, system and apparatus, including computer program products, for rendering a user interface in a client program. The techniques include detecting multiple changes to a user interface of a computer program, the user interface having multiple user interface elements, each change being a change to one of the multiple user interface elements; generating a rendering request for each change, each rendering request specifying the user interface element that has changed and a type of modification to be performed on the user interface element; and filtering the requests to eliminate redundant requests. The user interface can be rendered based on the filtered requests.

Abstract: There are methods and apparatus, including computer program products, for preventing data loss. For example, there is a client agent that automatically performs a data loss prevention action in response to detecting (i) a client navigation event and (ii) a difference between a client data state and a base data state, wherein the detection of the difference between the client data state and the base data state occurs without transmitting data to and from a server. The data loss prevention action can include generating a user prompt. The navigation event can include a navigation that replaces a user interface that the user had used to modify data associated with an application program. The data loss prevention action can be performed without receiving instructions corresponding to the action from the application program.

Abstract: Methods and apparatus, including computer program products, implementing techniques for undoing user actions in a client program. The techniques include displaying a user interface in a client program, the user interface having a plurality of controls, the plurality of controls including multiple types of controls, each control having a state; for each control in the plurality of controls, storing the state of the control as a first state for the control; receiving user input comprising a change to the state of a control in the plurality of controls; updating the state of the control based on the user input; storing the updated state of the control as a second state for the control; receiving user input comprising a request to undo the change; and restoring the state of the control to reflect the first state for the control.

Abstract: Methods and apparatus, including computer program products, implement techniques for rendering the user interface of a software application. A client computer provides a user interface for a computer program application. The user interface is operable to receive input from a user interacting with the client and to generate user interaction events from the input. One or more possible user interaction events are identified on the client while the user interface is in a current user interface state. The possible user interaction events are user interaction events that would arise from input the user interface could possibly receive in the current user interface state from the user. One or more of the possible user interaction events are pre-processed to generate one or more possible user interface states. The possible user interface states are stored for later use.

Abstract: Methods and apparatus, including computer program products, for representing hierarchical list data. One method involves receiving a first list comprising an element A1 and an element A2, the element A2 comprising a first nested list comprising an element N1 and an element N2; receiving a second list comprising an element B1 and an element B2, the element B2 comprising a second nested list comprising an element M1 and an element M2; storing the elements A1 and B1 in a first array; and storing the elements A2 and B2 in a second array, the second array comprising a first sub-array to store the elements N1 and M1, and a second sub-array to store the N2 and M2.

Abstract: Systems, methods, and apparatus, including computer program products, for abstracting rendering logic and automatically generating platform-specific renderers from the abstracted rendering logic for multiple platforms. A platform-independent description of rendering logic for a control is specified. The platform-independent description is used to generate a platform-specific renderer for the control. The platform-specific renderer is operable to be executed on a specific platform to produce code that can be used in rendering the control on a client computer. Some implementations enable code for platform-specific renderers to be generated automatically based on centrally defined rendering logic. Rendering logic can thus be modified once and used to automatically update code and libraries for platform-specific renderers on multiple platforms.

Abstract: Methods and apparatus, including computer program products, implementing techniques for document object model caching and validation. A client identifies a change of a user interface (UI) element that references a node of the DOM hierarchy. The client determines whether the change of the UI element can be applied to the DOM hierarchy by using an update function, for example, a delta renderer. If so, the client finds in the DOM hierarchy the node that is referenced by the UI element and modifies at least one attribute related to the node according to the change by using the update function. Otherwise, the client sets a dirty flag.

Abstract: A fastening element 30 is fed from a feed track 64 through a feed chamber, formed by interfacing closed channels 132 and 160, to a junction point located in a feed passage 84, formed by two communicating feed openings 86 and 88. An inclined surface 82, located between the feed chamber and the junction point, is inclined downward from the feed chamber to the junction point. A ram 105, located movably in the feed chamber, transfers the fastening element 30 from the feed track 64 to the inclined surface 82, where the fastening element moves down the inclined surface to the junction point. Upon the application of a pressure medium into the feed passage 84, selectively in either of two directions, the fastening element 30 can be directed toward a fastening device 104.

Abstract: A client-side framework for enhancing the functionality of web browsers. The client-side framework enhancing a client-side scripting language, such as JavaScript, so that it provides object-oriented features and enabling cross-window and cross-frame communications.

Abstract: An XML client abstraction layer for providing an XML page description as an abstraction of an HTML page at design time. A style sheet XSLT translator is used to derive the run time code from the XML page. Additional features or improvements may be added through an XML parser.

Abstract: Methods and apparatus, including computer program products, for processing a user interaction with an application, such as a browser-based application. A user interaction with the browser-based application is detected at a software framework. The browser-based application is executing in a browser at a local computer system. The user interaction is processed at the software framework, where processing includes determining whether the user interaction can be handled locally or requires access to a resource at a remote computer system. The user interaction is processed based on a result of the determination. A data item representative of the user interaction can be created at the software framework and stored at a data store. The data item can later be retrieved and the user interaction represented by the data item reprocessed at the software framework to replay the user interaction.

Abstract: A fastening element 30 is fed from a feed track 64 through a feed chamber, formed by interfacing closed channels 132 and 160, to a junction point located in a feed passage 84, formed by two communicating feed openings 86 and 88. An inclined surface 82, located between the feed chamber and the junction point, is inclined downward from the feed chamber to the junction point. A ram 105, located movably in the feed chamber, transfers the fastening element 30 from the feed track 64 to the inclined surface 82, where the fastening element moves down the inclined surface to the junction point. Upon the application of a pressure medium into the feed passage 84, selectively in either of two directions, the fastening element 30 can be directed toward a fastening device 104.

Abstract: To set two-part fasteners (8), in particular blind rivets, in which for setting a first part (7) has to be pulled while a second part (6) is held, a device is proposed with a housing (1), a feed appliance (9) on the housing (1) to transfer a fastener (8) into the housing (1) through an orifice (12) in the housing (1), an abutment (3), which holds the second part (6) during the setting process, and a pulling device pulling the first part (7) during the setting process, which has a gripper (5) at an open end of a pulling element (4) which cooperates with a pulling piston (13) which is movable forwards and backwards along an axis of the housing (1) in a first chamber (14) by an actuating unit. To transfer a fastener (8) the pulling element (4) opens the orifice (12). The pulling element (4) extends through the piston (13). The pulling piston (13) and the pulling element (4) are movable relative to one another along the axis. The pulling element (4) has a piston (17) on the end opposed to the gripper (5).

Abstract: A component installation tool of the type having a rearward stroke to accommodate delivery of a component to the front of the tool and a forward stroke to engage, deliver and install the component at a workpiece, the tool including a housing, a reciprocating mechanism contained therein, a feeder support mounted on the housing, a reciprocal magazine mounted on the feeder support for reciprocation between a component receiving position adjacent the tool and a position for delivering a component in front of the mechanism; and delivery means for delivering a component to a chamber in the magazine when the magazine is in the component receiving position and the mechanism is in the forward stroke.

Abstract: A rivet setting tool for use with double headed blind rivets comprises a collet assembly adapted to engage a pulling head of the rivet mandrel and support segments for engaging the rivet. A single piston drive pulls the collet assembly and the mandrel rearwards relative to the support segments and rivet to set the rivet. Continued movement of the piston further retracts the collet assembly and the support segments to permit delivery of a new rivet at the front of the tool and returns the collet assembly and support segments to a forward position in engagement, respectively, with the mandrel head and the rivet.