Abstract: A mashup widget can include a widget component and a widget container. The widget container can be graphically rendered within widget defined boundaries of a mashup application. The widget component can detect an externally defined video file. The video file can have a native frame size, which is a frame size at which the video file is encoded. The video file can be loaded from a remote data source over an IP network. The native frame size of the video file can be determined. The defined boundaries of an embedded multimedia application can be dynamically adjusted to the native size. The defined boundaries of the widget container can be resized to accommodate the adjusted embedded multimedia application. The video can be rendered and presented within in the adjusted widget container.

Abstract: A mapping data of a location associated with a traffic collision incident can be presented within an automobile incident application interface executing within a computing device. A visualization of the incident can be performed within the interface. The visualization can be a computer generated graphic re-creation of the incident having a starting location and a collision location associated with an object model. The object model can be a graphical representation of a vehicle. A user input can be received during the visualization. The user input can include manipulating the position of an object model presented upon the mapping data. The manipulation can be a translation, rotation, and/or scaling operation. The object model can be associated with visualization data which can link the object model with a heading and/or a track. The appropriate heading and track of the object model can be visually presented within the interface.

Abstract: One or more computing devices proximate to a source device are identified. The source device is an end-user device having a touch sensitive surface. A gesture performed on the touch sensitive surface is detected. The gesture indicates a selection of a displayed representation of content and indicates a direction. The gesture is at least one of a touch based gesture, a stylus based gesture, a keyboard based gesture, and a pointing device gesture. A target device or a device proxy is determined that is within line-of-site of a human being that made the gesture and that is in the direction of the gesture. An action programmatically executes involving the gesture selected content and the determined target device or device proxy.

Abstract: A system that provides interactive three-dimensional (3D) augmented realities can include an augmented reality item marker (ARIM), a network-enabled mobile computing device, an augmented reality item lookup service (ARILS), and an augmented reality item viewer (ARIV). The ARIM can be a two-dimensional graphic conforming to a standardized encoding specification that can encode data elements about a product item. The network-enabled mobile computing device can include a camera configured to digitally capture the ARIM. The ARILS can be configured to provide a data response that includes augmented reality item data to the network-enabled mobile computing device. The ARIV can be configured to present an interactive 3D augmented reality visualization of the product item utilizing the augmented reality item data provided by the ARILS.

Abstract: A computer program product that includes a project object. The project object can be configured for linearly organizing a series of custom self-contained content. The project object can be a compliable object that includes at least one menu framework object and a set of project data objects. The menu framework object can define a menu. The menu framework object conforms to a standardized menu slideshow framework. The standardized menu slideshow framework can be a reusable templated framework. Each of the project data objects can include a self-contained content object. Each self-contained content object can be programmatically linked to the menu framework object without modifying source code of the self-contained content object. The menu framework object can define a linear ordering of the set of project data objects.

Abstract: A system for presenting FLASH presentations contained in a storage medium. Such a system can include a FLASH presentation (FLAPRE) markup language (FLML) document, a FLASH-based FLAPRE player, and a launching application. The FLML document can textually represent a user-created FLASH presentation using the FLAPRE markup language (FLML). The FLAPRE player can be configured to visually render the user-created FLASH presentation contained within the FLML document. The launching application can be configured to display the FLAPRE player and can support the use of FLASH animation.

Abstract: A document written in a specialized FLASH presentation markup language (FLML) stored in a storage medium. Such a document can textually represent a FLASH presentation. The text can correspond to a FLAPRE markup language (FLML) that can be interpreted at run-time. The structure and syntax of the FLML can conform to a standardized markup language. The FLML document can include FLML tags having FLML attributes and FLML attribute values.

Abstract: Incident data for an insurance claim associated with an incident can be received by an incident application executing within a computing device. The incident can be an insurable event associated with an insurance policy of an insurance carrier. The incident data can be simultaneously conveyed to an independent third party entity as a serialized data format and as an insurance claim to the insurance carrier. The third party entity can automatically verify the incident data and generate a verification report. The verification report can be associated with the incident claim. The verification report can be communicated to the insurance carrier which can be utilized to determine the validity of the insurance claim.

Abstract: A mapping data of a location associated with a traffic collision incident can be presented within an automobile incident application interface executing within a computing device. A visualization of the incident can be performed within the interface. The visualization can be a computer generated graphic re-creation of the incident having a starting location and a collision location associated with an object model. The object model can be a graphical representation of a vehicle. A user input can be received during the visualization. The user input can include manipulating the position of an object model presented upon the mapping data. The manipulation can be a translation, rotation, and/or scaling operation. The object model can be associated with visualization data which can link the object model with a heading and/or a track. The appropriate heading and track of the object model can be visually presented within the interface.

Abstract: A three-dimensional vehicle scene including an image can be rendered within an interactive user interface. The image can be generated from a model and can be rotatable by user selections of user selectable rotation controls. Vehicle panels can be shown and hidden within the interactive user interface responsive to positionings of an interface pointer. While one of the vehicle panels is shown, user-configurable damage fields can be included in the user interface to describe damage to the vehicle. Input of the damage fields can be used to indicate damage for insurance claim purposes and can be used to update damage indicia on the interface. Damage indicia can be overlaid on top of the image. A damaged vehicle can be shown in the interface by combining (in real-time and at runtime) the image of the undamaged vehicle and the damage indicia, which overlay the image.

Abstract: A system that provides interactive three-dimensional (3D) augmented realities can include an augmented reality item marker (ARIM), a network-enabled mobile computing device, an augmented reality item lookup service (ARILS), and an augmented reality item viewer (ARIV). The ARIM can be a two-dimensional graphic conforming to a standardized encoding specification that can encode data elements about a product item. The network-enabled mobile computing device can include a camera configured to digitally capture the ARIM. The ARILS can be configured to provide a data response that includes augmented reality item data to the network-enabled mobile computing device. The ARIV can be configured to present an interactive 3D augmented reality visualization of the product item utilizing the augmented reality item data provided by the ARILS.

Abstract: A mashup widget can include a widget component and a widget container. The widget container can be graphically rendered within widget defined boundaries of a mashup application. The widget component can detect an externally defined video file. The video file can have a native frame size, which is a frame size at which the video file is encoded. The video file can be loaded from a remote data source over an IP network. The native frame size of the video file can be determined. The defined boundaries of an embedded multimedia application can be dynamically adjusted to the native size. The defined boundaries of the widget container can be resized to accommodate the adjusted embedded multimedia application. The video can be rendered and presented within in the adjusted widget container.

Abstract: A MobilePointer pointer controller for hand-held devices that includes an isometric joystick and three buttons; right, middle, and left. The isometric joystick is able to be moved in a variety positions from center. The right button, a middle button, and left button, can each be user selectable buttons. The MobilePointer can be configured for single-hand use while a mobile computing device is being held in the hand that is manipulating the MobilePointer. User-selectable manipulations of the MobilePointer can map to standard mouse events, which permits Applications to respond to standard mouse events as opposed to mobile device specific ones.

Abstract: A system for presenting FLASH presentations contained in a storage medium. Such a system can include a FLASH presentation (FLAPRE) markup language (FLML) document, a FLASH-based FLAPRE player, and a launching application. The FLML document can textually represent a user-created FLASH presentation using the FLAPRE markup language (FLML). The FLAPRE player can be configured to visually render the user-created FLASH presentation contained within the FLML document. The launching application can be configured to display the FLAPRE player and can support the use of FLASH animation.

Abstract: A system for authoring a FLASH presentation can include a FLASH-based FLASH presentation (FLAPRE) authoring tool and a launching application. The FLAPRE authoring tool can be configured to create a specialized FLAPRE code file containing a user-created FLASH presentation. The specialized FLAPRE code file can be created without the use of a FLASH specification. The launching application can be configured to present the FLASH-based FLAPRE authoring tool. The launching application can also support the use of FLASH animation.

Abstract: A document written in a specialized FLASH presentation markup language (FLML) stored in a storage medium. Such a document can textually represent a FLASH presentation. The text can correspond to a FLAPRE markup language (FLML) that can be interpreted at run-time. The structure and syntax of the FLML can conform to a standardized markup language. The FLML document can include FLML tags having FLML attributes and FLML attribute values.

Abstract: A computer program product that includes a project object. The project object can be configured for linearly organizing a series of custom self-contained content. The project object can be a compliable object that includes at least one menu framework object and a set of project data objects. The menu framework object can define a menu. The menu framework object conforms to a standardized menu slideshow framework. The standardized menu slideshow framework can be a reusable templated framework. Each of the project data objects can include a self-contained content object. Each self-contained content object can be programmatically linked to the menu framework object without modifying source code of the self-contained content object. The menu framework object can define a linear ordering of the set of project data objects.