Abstract:
A centralizer comprises a first collar, a second collar, a plurality of bow springs coupling the first collar to the second collar, and a plurality of particulates disposed on an outer surface of at least one bow spring. One or more of the first collar, the second collar, and the bow springs comprises a composite material. In some embodiments, the centralizer comprises a third collar, wherein the plurality of bow springs comprise a first portion of bow springs and a second portion of bow springs, and wherein the first portion of the bow springs couple the first collar to the third collar and the second portion of the bow springs couple the second collar to the third collar.
Abstract:
A centralizer comprises a first collar, a second collar, a plurality of bow springs coupling the first collar to the second collar, and a plurality of particulates disposed on an outer surface of at least one bow spring. One or more of the first collar, the second collar, and the bow springs comprises a composite material. In some embodiments, the centralizer comprises a third collar, wherein the plurality of bow springs comprise a first portion of bow springs and a second portion of bow springs, and wherein the first portion of the bow springs couple the first collar to the third collar and the second portion of the bow springs couple the second collar to the third collar.
Abstract:
Various embodiments of systems and methods for a composition model for components of a user interface framework for Web applications are described. The methods include a loosely coupled method and a tightly coupled method for composing components in a UI framework. The loosely coupled method includes triggering a navigation pipe from an out-port of a first component to an in-port of a second component and defining a context mapping between a first set of parameters of the out-port of the first component and a second set of parameters of the in-port of the second component. The tightly coupled method includes exposing a binding reference from the first component to the second component and specifying a first data model entity from the first component to be bound to a second data model entity of the second component via a binding contract.
Abstract:
Methods and apparatus for displaying objects in client GUI. A lead selection and scoping information is used to determine whether the object is viewable, and the object is rendered only if it is at least partially viewable. The lead selection and scoping information is used to determine whether data is needed to render the object, and data is received from a corresponding object on a server only if it is needed to render the object. Determining whether the object is viewable in the GUI can be based on declaratively marked entities within the object's view and on view calculation rules. Determining whether data is needed to render the object can be based on declaratively marked entities within the object's data model such as flags indicating whether the data field is valid or whether the binding of the data field to a data source is valid.
Abstract:
Displaying a plurality of objects on a grid. Metadata indicates an object's display column and span. A lowest position is determined from objects displayed in the same column span. The object is displayed in the column span at the lowest position. A lowest position is determined after the last object is displayed. The grid is resized to minimize whitespace beyond the lowest position to border whitespace. Display overlay of first and second graphical objects. When the first object is directly manipulated in a GUI, the second object is automatically manipulated the same way. When the first object is scrolled in a first direction by a first amount, the second object is automatically displaced opposite the first direction by the first amount. When the first object is resized in a first dimension by a first amount, the second object can be automatically resized by the first amount in the first dimension.
Abstract:
A computer system includes a UI designer client that runs on a client device and is configured to enable creation of UI models. A client engine runs on a client device and is configured to initiate requests for the UI models, receive the UI models in response to the requests and interpret and render the UI models at runtime. A UI runtime server client is located on a server and is configured to interface with the client engine to receive and process the requests for the UI models from the client engine. A repository is located on the server and is configured to interface with the UI designer client and store the UI models as created using the UI designer client and interface with the UI runtime server client to deliver requested UI models to the UI runtime server client for interpretation and rendering by the client engine.
Abstract:
A component object binds business driven services to a graphical user interface (GUI). The object includes a data model, view model and controller. The view model graphically presents, and the controller manipulates data used by the object. The controller includes an event handler that respond to events generated within the GUI and binds data used by the object to a data source which can be another component object or a remotely located source. The event handler can call a local script to calculate the value of a data element within the object. The component object can be instantiated on a client, and can be configured to communicate with a corresponding component object on a server. The client and server component objects can exchange only that data that needs to be exchanged to maintain the current state of a user interface in the client computer.
Abstract:
A host software application implementing business processes and providing a graphical display associated with a user interface (UI) for a user in a client program executing on a client frontend device that is separate from a backend device storing metadata associated with the UI may be initiated. An automation graphical symbol may provide the user with an option to initiate a test on events of the host software application, during execution of the host software application. A request from the user may be received, to initiate a test on events of the host software application. Information may be received from the user indicating one or more selected specific events for performing the test. The test may be initiated on the selected specific events, based on a state of execution of the host software application at an initial time of the user indicating the selected specific events for performing the test.
Abstract:
A method and device for measuring electric currents in n conductors (n≧2), the measurement of the currents being carried out with (n−1) magnetoresistive sensors. Reliable excess current and/or fault current protection is obtained.
Abstract:
A component object binds business driven services to a graphical user interface (GUI). The object includes a data model, view model and controller. The view model graphically presents, and the controller manipulates data used by the object. The controller includes an event handler that respond to events generated within the GUI and binds data used by the object to a data source which can be another component object or a remotely located source. The event handler can call a local script to calculate the value of a data element within the object. The component object can be instantiated on a client, and can be configured to communicate with a corresponding component object on a server. The client and server component objects can exchange only that data that needs to be exchanged to maintain the current state of a user interface in the client computer.