Abstract: In some implementations, at least a partial view of a jog wheel user interface (UI) element is displayed on a graphical user interface (GUI). The jog wheel UI element is operable to manipulate one or more secondary elements. In response to a touch input for controlling the jog wheel UI element, a rotation of the jog wheel UI element is animated concurrently with manipulation of the secondary element(s). In some embodiments, the jog wheel UI element is rotated at an initial rotational speed based on the touch input, continues rotating after cessation of the touch input, and is reduced until it reaches zero. In one embodiment, a distance between the contact of the touch input and the jog wheel UI element is used to determine a degree of rotation of jog wheel UI element.

Abstract: In some implementations, at least a partial view of a jog wheel user interface (UI) element is displayed on a graphical user interface (GUI). The jog wheel UI element is operable to manipulate one or more secondary elements. In response to a touch input for controlling the jog wheel UI element, a rotation of the jog wheel UI element is animated concurrently with manipulation of the secondary element(s). In some embodiments, the jog wheel UI element is rotated at an initial rotational speed based on the touch input, continues rotating after cessation of the touch input, and is reduced until it reaches zero. In one embodiment, a distance between the contact of the touch input and the jog wheel UI element is used to determine a degree of rotation of jog wheel UI element.

Abstract: A content-generating user is enabled to set visible attributes for a content item from any device so that the content item maintains a uniform look and feel across the various platforms. The visible attributes set by the generating user are stored in the user's profile on a user profile database. When a request to display the content item is received from a client device, the platform associated with the request is determined. Display data comprising one or more of the visible attributes retrieved from the user profile database, the content item and a template based on the platform is transmitted to the client device. The client device configures a display of the content item to a viewer based on the received display data.

Abstract: A content-generating user is enabled to set visible attributes for a content item from any device so that the content item maintains a uniform look and feel across the various platforms. The visible attributes set by the generating user are stored in the user's profile on a user profile database. When a request to display the content item is received from a client device, the platform associated with the request is determined. Display data comprising one or more of the visible attributes retrieved from the user profile database, the content item and a template based on the platform is transmitted to the client device. The client device configures a display of the content item to a viewer based on the received display data.

Abstract: A content-generating user is enabled to set visible attributes for a content item from any device so that the content item maintains a uniform look and feel across the various platforms. The visible attributes set by the generating user are stored in the user's profile on a user profile database. When a request to display the content item is received from a client device, the platform associated with the request is determined. Display data comprising one or more of the visible attributes retrieved from the user profile database, the content item and a template based on the platform is transmitted to the client device. The client device configures a display of the content item to a viewer based on the received display data.

Abstract: A content-generating user is enabled to set visible attributes for a content item from any device so that the content item maintains a uniform look and feel across the various platforms. The visible attributes set by the generating user are stored in the user's profile on a user profile database. When a request to display the content item is received from a client device, the platform associated with the request is determined. Display data comprising one or more of the visible attributes retrieved from the user profile database, the content item and a template based on the platform is transmitted to the client device. The client device configures a display of the content item to a viewer based on the received display data.

Abstract: A content-generating user is enabled to set visible attributes for a content item from any device so that the content item maintains a uniform look and feel across the various platforms. The visible attributes set by the generating user are stored in the user's profile on a user profile database. When a request to display the content item is received from a client device, the platform associated with the request is determined. Display data comprising one or more of the visible attributes retrieved from the user profile database, the content item and a template based on the platform is transmitted to the client device. The client device configures a display of the content item to a viewer based on the received display data.

Abstract: A content-generating user is enabled to set visible attributes for a content item from any device so that the content item maintains a uniform look and feel across the various platforms. The visible attributes set by the generating user are stored in the user's profile on a user profile database. When a request to display the content item is received from a client device, the platform associated with the request is determined. Display data comprising one or more of the visible attributes retrieved from the user profile database, the content item and a template based on the platform is transmitted to the client device. The client device configures a display of the content item to a viewer based on the received display data.