Abstract: A device can receive an identification of an environmental model associated with a user navigating a website and receive an identification of an item model associated with an item requested by the user to be shown in connection with the environmental model on a client device. The environmental model could be a body model of the user or of another force like wind. The item model models how the item would move in connection with the environmental model. The device identifies movement associated with the environmental model and generates, based on the environmental model and the item model, frames each having respective data of the item as it would move on the environmental model according to the movement to yield movement key attributes. The device transmits the movement key attributes to the client device for rendering using a client device rendering engine.

Abstract: A scene comprising a set of visual elements may allow a user to perform “zoom” operations in order to navigate the depth of the scene. The “zoom” semantic is often applied to simulate optical visual depth, wherein the visual elements are presented with different visual dimensions and visual resolution to simulate physical proximity or distance. However, the “zoom” semantic may be alternatively applied to other aspects of the visual elements of a scene, such as a user selection of a zoomed-in visual element, a “drill-down” operation on a data set, or navigation through a portal in a first data set to view a second data set. These alternative “zoom” semantics may be achieved by presenting the effects of a “zoom” operation within the scene on the visual presentation of the visual element in a manner other than an adjustment of the visual dimensions and resolution of the visual element.

Abstract: A scene comprising a set of visual elements may allow a user to perform “zoom” operations in order to navigate the depth of the scene. The “zoom” semantic is often applied to simulate optical visual depth, wherein the visual elements are presented with different visual dimensions and visual resolution to simulate physical proximity or distance. However, the “zoom” semantic may be alternatively applied to other aspects of the visual elements of a scene, such as a user selection of a zoomed-in visual element, a “drill-down” operation on a data set, or navigation through a portal in a first data set to view a second data set. These alternative “zoom” semantics may be achieved by presenting the effects of a “zoom” operation within the scene on the visual presentation of the visual element in a manner other than an adjustment of the visual dimensions and resolution of the visual element.

Abstract: A scene comprising a set of visual elements may allow a user to perform “zoom” operations in order to navigate the depth of the scene. The “zoom” semantic is often applied to simulate optical visual depth, wherein the visual elements are presented with different visual dimensions and visual resolution to simulate physical proximity or distance. However, the “zoom” semantic may be alternatively applied to other aspects of the visual elements of a scene, such as a user selection of a zoomed-in visual element, a “drill-down” operation on a data set, or navigation through a portal in a first data set to view a second data set. These alternative “zoom” semantics may be achieved by presenting the effects of a “zoom” operation within the scene on the visual presentation of the visual element in a manner other than an adjustment of the visual dimensions and resolution of the visual element.

Abstract: Information describing a type registration regarding which an action is being requested by the client application is received as one or more parameters of an application programming interface method invoked by the client application. Based on the one or more parameters, one of multiple type extensions to which the action being requested corresponds is determined. At least part of the information describing the type registration is sent to the one of the multiple type extensions, and the one of the multiple type extensions performs the action being requested.

Abstract: Information describing a type registration regarding which an action is being requested by the client application is received as one or more parameters of an application programming interface method invoked by the client application. Based on the one or more parameters, one of multiple type extensions to which the action being requested corresponds is determined. At least part of the information describing the type registration is sent to the one of the multiple type extensions, and the one of the multiple type extensions performs the action being requested.

Abstract: Information describing a type registration regarding which an action is being requested by the client application is received as one or more parameters of an application programming interface method invoked by the client application. Based on the one or more parameters, one of multiple type extensions to which the action being requested corresponds is determined. At least part of the information describing the type registration is sent to the one of the multiple type extensions, and the one of the multiple type extensions performs the action being requested.

Abstract: A scene comprising a set of visual elements may allow a user to perform “zoom” operations in order to navigate the depth of the scene. The “zoom” semantic is often applied to simulate optical visual depth, wherein the visual elements are presented with different visual dimensions and visual resolution to simulate physical proximity or distance. However, the “zoom” semantic may be alternatively applied to other aspects of the visual elements of a scene, such as a user selection of a zoomed-in visual element, a “drill-down” operation on a data set, or navigation through a portal in a first data set to view a second data set. These alternative “zoom” semantics may be achieved by presenting the effects of a “zoom” operation within the scene on the visual presentation of the visual element in a manner other than an adjustment of the visual dimensions and resolution of the visual element.

Abstract: Information describing a type registration regarding which an action is being requested by the client application is received as one or more parameters of an application programming interface method invoked by the client application. Based on the one or more parameters, one of multiple type extensions to which the action being requested corresponds is determined. At least part of the information describing the type registration is sent to the one of the multiple type extensions, and the one of the multiple type extensions performs the action being requested.