Abstract: Techniques for group messaging on a mobile computing device are described. An apparatus may comprise a message server to communicate messages between multiple mobile computing devices. The message server may have a group message management module to establish a group messaging session between the multiple mobile computing devices. The group message management module may have a group generating module to receive a message with a group message indicator and identifying information for multiple mobile computing devices within the message. The group generating module may form a message group to communicate messages from any one of the mobile computing devices to all of the mobile computing devices for the group messaging session. Other embodiments are described and claimed.

Abstract: A system and a method are disclosed for discovering widgets for computing devices. A computing device parses data to identify rich content. The computing device searches for widgets supporting the identified rich content in a remote server and retrieves a widget supporting the identified rich content. The computing device executes the widget to process the rich content.

Abstract: A widget engine renders widgets using operating system platform-specific attributes. A widget application written at least partly in platform non-specific code is rendered by the widget engine through a series of system calls and callbacks. Upon interpreting particular code, the widget engine issues a system call to a module for performing a particular type of action. The module, based on the operating system platform, calls a platform-specific library that specifies how to carry out the action according to the operating system platform. Thereafter, using the returned platform-specific data, the widget engine renders the widget.

Abstract: A computing device is configured to receive an incoming communication from another computing device. The incoming communication may be for purpose of initiating a voice-exchange session. In response to receiving the incoming call, the computing device may identify or determine a message identifier of the other computing device. The message identifier is determined based at least in part on data provided with the incoming communication. The computing device may programmatically address a message to the other computing device using the message identifier determined from the incoming communication.

Abstract: A method and system are provided that translates tabular data prepared for a first display format into a second display format. Tabular data prepared for display on a conventional desktop display device may be adjusted for display on a portable computing device having a different display device. Tabular formatting may be removed for single row and single column tables. The method and system may also remove tabular formatting for tables having horizontal dimensions exceeding a specified amount. Tabular data may be removed from tables having more than one column that exceeds a specified maximum column size. The method and system may also identify nested tables and eliminate tabular formatting for all but the innermost tables.

Abstract: Unique identifiers referred to as “keys” are generated for objects stored on each node. When a container object including at least one embedded object is transferred from a sending node to a receiving node, the sending node sends the key uniquely identifying the embedded object to the receiving node to determine whether the embedded object is already stored on the receiving node. If the receiving node indicates that the embedded object is already stored at the receiving node, then the sending node determines that the embedded object does not need to be sent to the receiving node. In that case, if the embedded object has not been sent, the sending node does not send the embedded object. If the sending node has already started sending the embedded object, then the sending node terminates sending of the embedded object.

Abstract: A computing device is configured to receive an incoming communication from another computing device. The incoming communication may be for purpose of initiating a voice-exchange session. In response to receiving the incoming call, the computing device may identify or determine a message identifier of the other computing device. The message identifier is determined based at least in part on data provided with the incoming communication. The computing device may programmatically address a message to the other computing device using the message identifier determined from the incoming communication.

Abstract: Unique identifiers referred to as “keys” are generated for objects stored on each node. When a container object including at least one embedded object is transferred from a sending node to a receiving node, the sending node sends the key uniquely identifying the embedded object to the receiving node to determine whether the embedded object is already stored on the receiving node. If the receiving node indicates that the embedded object is already stored at the receiving node, then the sending node determines that the embedded object does not need to be sent to the receiving node. In that case, if the embedded object has not been sent, the sending node does not send the embedded object. If the sending node has already started sending the embedded object, then the sending node terminates sending of the embedded object.

Abstract: A computing device is configured to receive an incoming communication from another computing device. The incoming communication may be for purpose of initiating a voice-exchange session. In response to receiving the incoming call, the computing device may identify or determine a message identifier of the other computing device. The message identifier is determined based at least in part on data provided with the incoming communication. The computing device may programmatically address a message to the other computing device using the message identifier determined from the incoming communication.

Abstract: Unique identifiers referred to as “keys” are generated for objects stored on each node. When a container object including at least one embedded object is transferred from a sending node to a receiving node, the sending node sends the key uniquely identifying the embedded object to the receiving node to determine whether the embedded object is already stored on the receiving node. If the receiving node indicates that the embedded object is already stored at the receiving node, then the sending node determines that the embedded object does not need to be sent to the receiving node. In that case, if the embedded object has not been sent, the sending node does not send the embedded object. If the sending node has already started sending the embedded object, then the sending node terminates sending of the embedded object.

Abstract: A widget engine renders widgets using operating system platform-specific attributes. A widget application written at least partly in platform non-specific code is rendered by the widget engine through a series of system calls and callbacks. Upon interpreting particular code, the widget engine issues a system call to a module for performing a particular type of action. The module, based on the operating system platform, calls a platform-specific library that specifies how to carry out the action according to the operating system platform. Thereafter, using the returned platform-specific data, the widget engine renders the widget.

Abstract: A widget engine renders widgets using operating system platform-specific attributes. A widget application written at least partly in platform non-specific code is rendered by the widget engine through a series of system calls and callbacks. Upon interpreting particular code, the widget engine issues a system call to a module for performing a particular type of action. The module, based on the operating system platform, calls a platform-specific library that specifies how to carry out the action according to the operating system platform. Thereafter, using the returned platform-specific data, the widget engine renders the widget.

Abstract: A computing device is configured to receive an incoming communication from another computing device. The incoming communication may be for purpose of initiating a voice-exchange session. In response to receiving the incoming call, the computing device may identify or determine a message identifier of the other computing device. The message identifier is determined based at least in part on data provided with the incoming communication. The computing device may programmatically address a message to the other computing device using the message identifier determined from the incoming communication.

Abstract: Unique identifiers referred to as “keys” are generated for objects stored on each node. When a container object including at least one embedded object is transferred from a sending node to a receiving node, the sending node sends the key uniquely identifying the embedded object to the receiving node to determine whether the embedded object is already stored on the receiving node. If the receiving node indicates that the embedded object is already stored at the receiving node, then the sending node determines that the embedded object does not need to be sent to the receiving node. In that case, if the embedded object has not been sent, the sending node does not send the embedded object. If the sending node has already started sending the embedded object, then the sending node terminates sending of the embedded object.

Abstract: Techniques to manage contact information are described. An apparatus may comprise a mobile computing device. The mobile computing device may include a subscriber identity module having a first set of contact information. The mobile computing device may also include a contact management module. The contact management module may include a subscriber identity module cache manager to retrieve the first set of contact information from the subscriber identity module and store it in a subscriber identity module cache. The contact management module may also include a contact information database having a second set of contact information. The contact management module may further include a contact database manager to retrieve the first set of contact information from the contact information database and the second set of contact information from the subscriber identity module cache for a contact application. Other embodiments are described and claimed.

Abstract: A computing device is configured to receive an incoming communication from another computing device. The incoming communication may be for purpose of initiating a voice-exchange session. In response to receiving the incoming call, the computing device may identify or determine a message identifier of the other computing device. The message identifier is determined based at least in part on data provided with the incoming communication. The computing device may programmatically address a message to the other computing device using the message identifier determined from the incoming communication.

Abstract: A system and a method are disclosed for discovering widgets for computing devices. A computing device parses data to identify rich content. The computing device searches for widgets supporting the identified rich content in a remote server and retrieves a widget supporting the identified rich content. The computing device executes the widget to process the rich content.

Abstract: A widget engine renders widgets using operating system platform-specific attributes. A widget application written at least partly in platform non-specific code is rendered by the widget engine through a series of system calls and callbacks. Upon interpreting particular code, the widget engine issues a system call to a module for performing a particular type of action. The module, based on the operating system platform, calls a platform-specific library that specifies how to carry out the action according to the operating system platform. Thereafter, using the returned platform-specific data, the widget engine renders the widget.

Abstract: Techniques to manage contact information are described. An apparatus may comprise a mobile computing device. The mobile computing device may include a subscriber identity module having a first set of contact information. The mobile computing device may also include a contact management module. The contact management module may include a subscriber identity module cache manager to retrieve the first set of contact information from the subscriber identity module and store it in a subscriber identity module cache. The contact management module may also include a contact information database having a second set of contact information. The contact management module may further include a contact database manager to retrieve the first set of contact information from the contact information database and the second set of contact information from the subscriber identity module cache for a contact application. Other embodiments are described and claimed.

Abstract: An electrically powered tool comprises a unitary chassis and a novel strain relief system incorporating a molded housing having a bore therein for securing power wiring to said chassis and preventing stress thereto.