US20090015599A1 - Draggable mechanism for identifying and communicating the state of an application - Google Patents
Draggable mechanism for identifying and communicating the state of an application Download PDFInfo
- Publication number
- US20090015599A1 US20090015599A1 US11/775,097 US77509707A US2009015599A1 US 20090015599 A1 US20090015599 A1 US 20090015599A1 US 77509707 A US77509707 A US 77509707A US 2009015599 A1 US2009015599 A1 US 2009015599A1
- Authority
- US
- United States
- Prior art keywords
- application
- draggable
- predetermined interval
- state
- metadata
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/0486—Drag-and-drop
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/543—User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]
Definitions
- aspects of the present invention relate generally to software and Internet applications, and more particularly to a system and method for a draggable mechanism which identifies and communicates the state of an application.
- a state of an application may be defined as an occurrence of an event in the application.
- An application event occurrence differs per application or even within an application.
- a video player application may measure application states in terms of each second or multiple or fraction of a second elapsed in a video file being executed by the video player, where a new state occurs during each such time interval.
- the same video player alternatively may measure application states in terms of the number of frames elapsed for a video.
- a word processing application may measure application states by a predetermined number of characters typed in a word processing document, e.g., every ten characters typed is a new application state, or alternatively, by a predetermined interval of time, e.g., every ten minutes the document is active is a new application state.
- Embodiments of the present invention overcome the above-mentioned and various other shortcomings of conventional technology, providing a method and system for identifying and communicating a state of an application.
- a namespace is defined for a draggable mechanism.
- the draggable mechanism is located within an application window housing an application.
- Metadata identifying application state information is appended to a URL embedded within the draggable mechanism to reflect a first application state of the application.
- the metadata is updated at a predetermined interval to reflect changed application states.
- FIG. 1 is a diagram illustrating a generic format of a Uniform Resource Identifier.
- FIG. 2 is a diagram illustrating one embodiment of a mechanism for identifying a state of an application.
- FIG. 3 is an exemplary screenshot of a draggable mechanism for identifying a state of an application.
- FIG. 4 is an exemplary screenshot of a draggable mechanism communicating a state of an application.
- FIG. 5 is a simplified flowchart illustrating one embodiment of a method for identifying a state of an application.
- FIG. 6 is a simplified flowchart illustrating one embodiment of a method for communicating a state of an application.
- FIG. 1 is a diagram illustrating a generic format of a Uniform Resource Identifier (URI).
- URI Uniform Resource Identifier
- a URI generally is a compact sequence of characters that identifies an abstract or physical resource.
- the syntax of a URI permits the parsing of components of a URI reference without knowledge of scheme-specific requirements of every possible component.
- Each URI begins with a scheme name 110 which refers to a specification for assigning identifiers within the scheme.
- the URI scheme name defines the syntax and semantics needed to parse a URI reference into components.
- Commonly known URI schemes include http (hypertext transfer protocol), ftp (file transfer protocol), snmp (simple network management protocol), dns (domain name system), mailto (SMTP email addresses), etc.
- an authority or hierarchical part 120 follows the scheme name 110 , and governs the namespace defined by the remainder of the URI.
- the hierarchical part 120 may include optional user information, a hostname, such as a domain name or IP address, and an optional port number preceded by a colon (‘:’).
- the hierarchical part is typically delimited from the scheme name by a double slash “//” and is terminated by either a single slash ‘/’, a question mark ‘?’, or a hash character ‘#’.
- the hierarchical part may be optionally followed by a path component, provided that the path component is separated from the hierarchical part by a single slash ‘/’.
- a query 130 may identify a resource within the scope of the URI's scheme and namespace, together with the path or alone.
- a query 130 is designated by the first question mark ‘?’ in the URI and ends with a hash or pound character ‘#’.
- a fragment identifier component 140 may permit indirect identification of a secondary resource and any additional identifying information. Fragment identifiers 140 also may be used in client-side indirect referencing, allowing an author to specifically identify portions of an existing resource that are only indirectly provided by the resource owner. As a result, a fragment identifier may not be used in the scheme-specific processing of a URI, and dereferencing of the fragment identifier may occur independently of the URI processing.
- FIG. 2 is a diagram illustrating one embodiment of a mechanism for identifying a state of an application.
- this mechanism may take the form of a URI or Uniform Resource Locator (URL) with metadata embodying additional state information appended in the fragment identifier portion of the URI.
- a URL is a subset of a URI in which the URL not only identifies a resource, but also provides a location for the resource, e.g., a network location of the resource.
- the URI may include a scheme name 210 , which, in this embodiment, is the http scheme used for, among other things, publishing and retrieving html documents.
- the URI may also include a hierarchical component 220 , such as a domain name.
- the URI may also include a path 230 to further identify the resource location.
- the scheme name 210 , hierarchical component 220 , and path component 230 may identify an image of the JPG format.
- the mechanism may point to a location of an image, such that an image is displayed in a web browser, through the fragment component of the URI, the mechanism also may identify the state of an application which plays a video or multimedia file.
- the fragment component 240 may specify a namespace that is defined in a way to enable other applications to parse and process this mechanism.
- the namespace may define a URL which has its own scheme, hierarchical component, path, and queries. The queries may serve to identify various aspects of the state of the video or multimedia file being executed on the video player application.
- such aspects may include a video identifier, the current time elapsed of the video file being played, the size or resolution of the video file, whether the video file is currently being played or is paused or stopped, the identifier of the next video to be played, and the URL of the video file.
- a video identifier the various characteristics of the state of an application are not limited to these aforementioned characteristics, and that metadata embodying the characteristics or properties disclosed in the query component of the fragment component are entirely exemplary.
- the properties used to identify or describe a state of an application may vary and depend on the type of application. The type of application is not limited to a video or a multimedia application, but could be any application that can have different states at different times, and thus is amenable to the approach of the present invention.
- FIG. 3 is an exemplary screenshot of a draggable mechanism for identifying a state of an application.
- the screenshot discloses a video or multimedia player 310 embedded in a web page.
- the multimedia player may play video or multimedia files.
- Embedded or placed within the web page, in this embodiment, adjacent to the video player may be a draggable mechanism 320 for identifying a state of an application.
- the draggable mechanism 320 may be a URI, as disclosed in the embodiment of FIG. 2 , in which an image or graphic is displayed as a result of the URI identifying the image or graphic through the URI scheme name, hierarchical component, and path component.
- the draggable mechanism may be a text box, an icon, or any other object which may be dragged or cut-and-pasted from one application to another.
- Metadata identifying application state information related to the state of the multimedia player may be embedded in the image or graphic embodying the draggable mechanism 320 .
- the application state information may be appended to the URI and found in the fragment component 240 .
- the mechanism may update the metadata identifying the application state information appended to the fragment component 240 .
- the draggable mechanism may be created and updated using Javascript or other programming languages. By using Javascript or other programming languages, the application state information may be updated for each application state change without refreshing or reloading the image identified in the URI or otherwise disrupting the executing application.
- multiple draggable mechanisms may be saved and stored to identify different states of an application. For example, a draggable mechanism for a word processing application may be dragged to a location different from the location of the application after each application state change.
- application state changes may be defined to occur every predetermined number of characters or at a predetermined time interval.
- a user may drag the mechanism to a location different from the location of application to save that particular state of the application in the event the user needs to access a previous state.
- the draggable mechanism may then update the application state information to reflect a new application state.
- FIG. 4 is an exemplary screenshot of a draggable mechanism communicating a state of an application.
- a state of an application such as the multimedia video player 310 of FIG. 3
- the draggable mechanism 320 may be dragged from the video player to a different application, such as an Internet messaging application 410 .
- any application may be designed or created to process draggable mechanisms. For example, applications created using Adobe Integrated Runtime or any other application development software supporting drag-and-drop functionality may process draggable mechanisms.
- the draggable mechanism 320 may be communicated to another user of the Internet messaging application through an “instant message” or chat window.
- the draggable mechanism may be conveyed to other users in other manners, such as through email or other interpersonal electronic communication methods.
- the recipient may access the mechanism by clicking on mechanism to launch, in this embodiment, a multimedia player to play the video or multimedia file at the same state at which the video file was playing on the transmitting party's multimedia or video player.
- the multimedia file may be played at the same state on a multimedia player on the recipient's computing device through the Internet messaging application's parsing of the application state information appended to the URI embedded within the mechanism.
- the Internet messaging application may parse the metadata identifying application state information appended to the URI of the draggable mechanism and launch the application needed to play or execute the video identified by the URL within the appended application state information.
- FIG. 5 is a simplified flowchart illustrating one embodiment of a method for identifying a state of an application.
- a namespace may be defined to enable other applications to parse a URI embedded within a draggable mechanism.
- the URI may point to or identify the location of a graphic or image.
- the draggable mechanism may be placed within an application window of an executing application, such that the graphic or image identified by the URI may appear in the application window.
- metadata identifying a state of the application may be appended to the URI within the fragment component of the URI.
- the fragment component may be separated from the URI through the use of a hash or pound character (‘#’).
- the metadata reflecting the application state information may be updated at a predetermined interval corresponding to a change in the state of the application.
- the application state information may be updated every second a video file plays, or alternatively, every predetermined number of elapsed frames.
- the application state information may be updated every time a new level is reached, or if the game is a sports game, for every quarter or period elapsed.
- application state information may be updated every time a new song is added or deleted from a playlist, or every time a new song is added or downloaded to the application.
- FIG. 6 is a simplified flowchart illustrating one embodiment of a method for communicating a state of an application.
- a draggable mechanism which contains appended metadata identifying a state of an application may be dragged from the application to a location different from the location of the application.
- the different location may include other applications housed in other application windows, or may be the desktop of a computing device operating system.
- Applications receiving the draggable mechanism may be created or designed to support drag-and-drop functionality.
- the draggable mechanism may be accessed at the different location, whether it be an application or a desktop.
- the mechanism may be a graphic or an icon whose execution or access may be the result of being clicked.
- parsing of the URI embedded within the mechanism may ensue to determine the components of the URI and what resources they identify, as well as to extract application state information contained within a fragment component of the URI.
- the application identified by the extracted appended application state information may be executed at the state identified by the extracted application state information. In this respect, the state of the application may be communicated to a different application or a different user. The process ends in block 650 .
- a draggable mechanism may be enabled to facilitate the identification and communication of a state of an application.
- the present disclosure is not intended to be limited with respect to the type of application capable of having its state identified or communicated.
- Such Internet applications may include but are not limited to music applications, Internet office applications (i.e., word processing applications, spreadsheet applications, slideshow applications, database applications, etc.), photograph applications, and games.
- the invention also is applicable to non-Internet applications with minor variations to the definition of the namespace for the URI embedded within the draggable mechanism.
- Such applications may include but are not limited to office software, such as word processors, spreadsheet programs, and database programs, as well as games, music applications, photograph applications, and electronic testing applications.
- application state information identifying a state of any of these applications may vary depending on the application, and should not be limited to only those properties or characteristics of application states described herein.
Abstract
Description
- 1. Field of the Invention
- Aspects of the present invention relate generally to software and Internet applications, and more particularly to a system and method for a draggable mechanism which identifies and communicates the state of an application.
- 2. Description of Related Art
- During execution of a software application, the application may have many states. A state of an application may be defined as an occurrence of an event in the application. An application event occurrence differs per application or even within an application. For example, a video player application may measure application states in terms of each second or multiple or fraction of a second elapsed in a video file being executed by the video player, where a new state occurs during each such time interval. The same video player alternatively may measure application states in terms of the number of frames elapsed for a video. In another example, a word processing application may measure application states by a predetermined number of characters typed in a word processing document, e.g., every ten characters typed is a new application state, or alternatively, by a predetermined interval of time, e.g., every ten minutes the document is active is a new application state.
- Currently, several standardized processes exist to communicate a state of an application to other applications. These processes include Component Object Model (COM), MessageBus, and AppleScript™. A disadvantage of these communication standards is that they are often not accessible to an end user, as these standards are employed by application developers during the development of an application. Further, these communications processes do not communicate application states to other applications graphically. As a result, no user-friendly mechanism exists for communicating an application state to another application.
- Thus, it would be desirable to provide a method and system for identifying and communicating a state of an application to other applications.
- Embodiments of the present invention overcome the above-mentioned and various other shortcomings of conventional technology, providing a method and system for identifying and communicating a state of an application.
- In accordance with one aspect, a namespace is defined for a draggable mechanism. The draggable mechanism is located within an application window housing an application. Metadata identifying application state information is appended to a URL embedded within the draggable mechanism to reflect a first application state of the application. The metadata is updated at a predetermined interval to reflect changed application states.
- The foregoing and other aspects of various embodiments of the present invention will be apparent through examination of the following detailed description thereof in conjunction with the accompanying drawing figures.
-
FIG. 1 is a diagram illustrating a generic format of a Uniform Resource Identifier. -
FIG. 2 is a diagram illustrating one embodiment of a mechanism for identifying a state of an application. -
FIG. 3 is an exemplary screenshot of a draggable mechanism for identifying a state of an application. -
FIG. 4 is an exemplary screenshot of a draggable mechanism communicating a state of an application. -
FIG. 5 is a simplified flowchart illustrating one embodiment of a method for identifying a state of an application. -
FIG. 6 is a simplified flowchart illustrating one embodiment of a method for communicating a state of an application. -
FIG. 1 is a diagram illustrating a generic format of a Uniform Resource Identifier (URI). A URI generally is a compact sequence of characters that identifies an abstract or physical resource. The syntax of a URI permits the parsing of components of a URI reference without knowledge of scheme-specific requirements of every possible component. Each URI begins with ascheme name 110 which refers to a specification for assigning identifiers within the scheme. The URI scheme name defines the syntax and semantics needed to parse a URI reference into components. Commonly known URI schemes include http (hypertext transfer protocol), ftp (file transfer protocol), snmp (simple network management protocol), dns (domain name system), mailto (SMTP email addresses), etc. Commonly, an authority orhierarchical part 120 follows thescheme name 110, and governs the namespace defined by the remainder of the URI. Thehierarchical part 120 may include optional user information, a hostname, such as a domain name or IP address, and an optional port number preceded by a colon (‘:’). The hierarchical part is typically delimited from the scheme name by a double slash “//” and is terminated by either a single slash ‘/’, a question mark ‘?’, or a hash character ‘#’. The hierarchical part may be optionally followed by a path component, provided that the path component is separated from the hierarchical part by a single slash ‘/’. Aquery 130 may identify a resource within the scope of the URI's scheme and namespace, together with the path or alone. Aquery 130 is designated by the first question mark ‘?’ in the URI and ends with a hash or pound character ‘#’. Afragment identifier component 140 may permit indirect identification of a secondary resource and any additional identifying information.Fragment identifiers 140 also may be used in client-side indirect referencing, allowing an author to specifically identify portions of an existing resource that are only indirectly provided by the resource owner. As a result, a fragment identifier may not be used in the scheme-specific processing of a URI, and dereferencing of the fragment identifier may occur independently of the URI processing. -
FIG. 2 is a diagram illustrating one embodiment of a mechanism for identifying a state of an application. In one embodiment, this mechanism may take the form of a URI or Uniform Resource Locator (URL) with metadata embodying additional state information appended in the fragment identifier portion of the URI. A URL is a subset of a URI in which the URL not only identifies a resource, but also provides a location for the resource, e.g., a network location of the resource. The URI may include ascheme name 210, which, in this embodiment, is the http scheme used for, among other things, publishing and retrieving html documents. The URI may also include ahierarchical component 220, such as a domain name. The URI may also include apath 230 to further identify the resource location. In the context of this embodiment, thescheme name 210,hierarchical component 220, andpath component 230 may identify an image of the JPG format. - In this embodiment, while the mechanism may point to a location of an image, such that an image is displayed in a web browser, through the fragment component of the URI, the mechanism also may identify the state of an application which plays a video or multimedia file. The
fragment component 240 may specify a namespace that is defined in a way to enable other applications to parse and process this mechanism. In this embodiment, the namespace may define a URL which has its own scheme, hierarchical component, path, and queries. The queries may serve to identify various aspects of the state of the video or multimedia file being executed on the video player application. In this embodiment, such aspects may include a video identifier, the current time elapsed of the video file being played, the size or resolution of the video file, whether the video file is currently being played or is paused or stopped, the identifier of the next video to be played, and the URL of the video file. Those of skill in the art should recognize that the various characteristics of the state of an application are not limited to these aforementioned characteristics, and that metadata embodying the characteristics or properties disclosed in the query component of the fragment component are entirely exemplary. Those of skill in the art should also recognize that the properties used to identify or describe a state of an application may vary and depend on the type of application. The type of application is not limited to a video or a multimedia application, but could be any application that can have different states at different times, and thus is amenable to the approach of the present invention. -
FIG. 3 is an exemplary screenshot of a draggable mechanism for identifying a state of an application. The screenshot discloses a video ormultimedia player 310 embedded in a web page. The multimedia player may play video or multimedia files. Embedded or placed within the web page, in this embodiment, adjacent to the video player may be adraggable mechanism 320 for identifying a state of an application. Thedraggable mechanism 320 may be a URI, as disclosed in the embodiment ofFIG. 2 , in which an image or graphic is displayed as a result of the URI identifying the image or graphic through the URI scheme name, hierarchical component, and path component. Alternatively, the draggable mechanism may be a text box, an icon, or any other object which may be dragged or cut-and-pasted from one application to another. Metadata identifying application state information related to the state of the multimedia player may be embedded in the image or graphic embodying thedraggable mechanism 320. Within the URI defining thedraggable mechanism 320, the application state information may be appended to the URI and found in thefragment component 240. For each application state change, the mechanism may update the metadata identifying the application state information appended to thefragment component 240. The draggable mechanism may be created and updated using Javascript or other programming languages. By using Javascript or other programming languages, the application state information may be updated for each application state change without refreshing or reloading the image identified in the URI or otherwise disrupting the executing application. - In one embodiment, multiple draggable mechanisms may be saved and stored to identify different states of an application. For example, a draggable mechanism for a word processing application may be dragged to a location different from the location of the application after each application state change. In one embodiment, for the word processing application, application state changes may be defined to occur every predetermined number of characters or at a predetermined time interval. Prior to each application state change, a user may drag the mechanism to a location different from the location of application to save that particular state of the application in the event the user needs to access a previous state. When the application state changes, the draggable mechanism may then update the application state information to reflect a new application state.
-
FIG. 4 is an exemplary screenshot of a draggable mechanism communicating a state of an application. In this embodiment, a state of an application, such as themultimedia video player 310 ofFIG. 3 , may be identified by adraggable mechanism 320 through the application state information appended to the URI embedded within the mechanism. Thedraggable mechanism 320 may be dragged from the video player to a different application, such as anInternet messaging application 410. Generally, based on the defined namespace associated with the appended application state information, any application may be designed or created to process draggable mechanisms. For example, applications created using Adobe Integrated Runtime or any other application development software supporting drag-and-drop functionality may process draggable mechanisms. In this embodiment, thedraggable mechanism 320 may be communicated to another user of the Internet messaging application through an “instant message” or chat window. Those of skill in the art should recognize that the draggable mechanism may be conveyed to other users in other manners, such as through email or other interpersonal electronic communication methods. Upon receipt of thedraggable mechanism 420, the recipient may access the mechanism by clicking on mechanism to launch, in this embodiment, a multimedia player to play the video or multimedia file at the same state at which the video file was playing on the transmitting party's multimedia or video player. - Upon execution of the mechanism, the multimedia file may be played at the same state on a multimedia player on the recipient's computing device through the Internet messaging application's parsing of the application state information appended to the URI embedded within the mechanism. Because the
fragment component 240 of the URI includes a namespace defined in such a manner as to enable other applications to properly parse and process the application state information, the Internet messaging application may parse the metadata identifying application state information appended to the URI of the draggable mechanism and launch the application needed to play or execute the video identified by the URL within the appended application state information. -
FIG. 5 is a simplified flowchart illustrating one embodiment of a method for identifying a state of an application. In block 510, a namespace may be defined to enable other applications to parse a URI embedded within a draggable mechanism. The URI may point to or identify the location of a graphic or image. Inblock 520, the draggable mechanism may be placed within an application window of an executing application, such that the graphic or image identified by the URI may appear in the application window. In block 530, metadata identifying a state of the application may be appended to the URI within the fragment component of the URI. The fragment component may be separated from the URI through the use of a hash or pound character (‘#’). Use of the hash character ‘#’ prevents an application which dereferences the embedded URI from attempting to process the fragment component as part of the URI. Inblock 540, the metadata reflecting the application state information may be updated at a predetermined interval corresponding to a change in the state of the application. In one embodiment, for a multimedia video player, the application state information may be updated every second a video file plays, or alternatively, every predetermined number of elapsed frames. In one embodiment, for a video game, the application state information may be updated every time a new level is reached, or if the game is a sports game, for every quarter or period elapsed. In one embodiment, for a music application, such as Yahoo Music Jukebox™ or Apple iTunes™, application state information may be updated every time a new song is added or deleted from a playlist, or every time a new song is added or downloaded to the application. These embodiments are entirely exemplary, and as such, should not be considered as limiting the invention. The process ends inblock 550. -
FIG. 6 is a simplified flowchart illustrating one embodiment of a method for communicating a state of an application. Inblock 610, a draggable mechanism which contains appended metadata identifying a state of an application may be dragged from the application to a location different from the location of the application. The different location may include other applications housed in other application windows, or may be the desktop of a computing device operating system. Applications receiving the draggable mechanism may be created or designed to support drag-and-drop functionality. Inblock 620, the draggable mechanism may be accessed at the different location, whether it be an application or a desktop. In one embodiment, the mechanism may be a graphic or an icon whose execution or access may be the result of being clicked. Inblock 630, upon execution of the mechanism, parsing of the URI embedded within the mechanism may ensue to determine the components of the URI and what resources they identify, as well as to extract application state information contained within a fragment component of the URI. Inblock 640, after parsing is complete, the application identified by the extracted appended application state information may be executed at the state identified by the extracted application state information. In this respect, the state of the application may be communicated to a different application or a different user. The process ends inblock 650. - Those of skill in the art will appreciate that a draggable mechanism may be enabled to facilitate the identification and communication of a state of an application. The present disclosure is not intended to be limited with respect to the type of application capable of having its state identified or communicated. For example, while embodiments described herein have been directed to Internet applications, and in particular to a multimedia video player, the invention is applicable to other Internet applications besides multimedia video players. Such Internet applications may include but are not limited to music applications, Internet office applications (i.e., word processing applications, spreadsheet applications, slideshow applications, database applications, etc.), photograph applications, and games. The invention also is applicable to non-Internet applications with minor variations to the definition of the namespace for the URI embedded within the draggable mechanism. Such applications may include but are not limited to office software, such as word processors, spreadsheet programs, and database programs, as well as games, music applications, photograph applications, and electronic testing applications. Moreover, application state information identifying a state of any of these applications may vary depending on the application, and should not be limited to only those properties or characteristics of application states described herein.
- Several features and aspects of the present invention have been illustrated and described in detail with reference to particular embodiments by way of example only, and not by way of limitation. Those of skill in the art will appreciate that alternative implementations and various modifications to the disclosed embodiments are within the scope and contemplation of the present disclosure. Therefore, it is intended that the invention be considered as limited only by the scope of the appended claims.
Claims (34)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/775,097 US20090015599A1 (en) | 2007-07-09 | 2007-07-09 | Draggable mechanism for identifying and communicating the state of an application |
PCT/US2008/069240 WO2009009442A2 (en) | 2007-07-09 | 2008-07-03 | Draggable mechanism for identifying and communicating the state of an application |
TW097125192A TW200925893A (en) | 2007-07-09 | 2008-07-04 | Draggable mechanism for identifying and communicating the state of an application |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/775,097 US20090015599A1 (en) | 2007-07-09 | 2007-07-09 | Draggable mechanism for identifying and communicating the state of an application |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090015599A1 true US20090015599A1 (en) | 2009-01-15 |
Family
ID=40229430
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/775,097 Abandoned US20090015599A1 (en) | 2007-07-09 | 2007-07-09 | Draggable mechanism for identifying and communicating the state of an application |
Country Status (3)
Country | Link |
---|---|
US (1) | US20090015599A1 (en) |
TW (1) | TW200925893A (en) |
WO (1) | WO2009009442A2 (en) |
Cited By (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090024927A1 (en) * | 2007-07-18 | 2009-01-22 | Jasson Schrock | Embedded Video Playlists |
US20090024923A1 (en) * | 2007-07-18 | 2009-01-22 | Gunthar Hartwig | Embedded Video Player |
US7912924B1 (en) * | 2007-11-06 | 2011-03-22 | Adobe Systems Incorporated | Adding functionality with respect to one or more web pages |
WO2011035944A1 (en) | 2009-09-25 | 2011-03-31 | International Business Machines Corporation | Managing application state information by means of a uniform resource identifier (uri) |
US20110296289A1 (en) * | 2010-05-25 | 2011-12-01 | Sony Corporation | Information processing device, content display method, and computer program |
US20120331372A1 (en) * | 2011-06-24 | 2012-12-27 | Usablenet Inc. | Methods for making ajax web applications bookmarkable and crawlable and devices thereof |
US20130191435A1 (en) * | 2012-01-19 | 2013-07-25 | Microsoft Corporation | Client-Side Minimal Download and Simulated Page Navigation Features |
US20130227457A1 (en) * | 2012-02-24 | 2013-08-29 | Samsung Electronics Co. Ltd. | Method and device for generating captured image for display windows |
US20130314301A1 (en) * | 2009-03-25 | 2013-11-28 | Ami Entertainment Network, Inc. | Multi-region interactive display |
US20140244828A1 (en) * | 2013-02-26 | 2014-08-28 | Jan Besehanic | Methods and apparatus to measure exposure to streaming media |
US9197421B2 (en) | 2012-05-15 | 2015-11-24 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US9210208B2 (en) | 2011-06-21 | 2015-12-08 | The Nielsen Company (Us), Llc | Monitoring streaming media content |
US9313544B2 (en) | 2013-02-14 | 2016-04-12 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US9332035B2 (en) | 2013-10-10 | 2016-05-03 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US9380356B2 (en) | 2011-04-12 | 2016-06-28 | The Nielsen Company (Us), Llc | Methods and apparatus to generate a tag for media content |
US20170078199A1 (en) * | 2015-09-11 | 2017-03-16 | Palo Alto Research Center Incorporated | Network named fragments in a content centric network |
US9609034B2 (en) | 2002-12-27 | 2017-03-28 | The Nielsen Company (Us), Llc | Methods and apparatus for transcoding metadata |
US20170101712A1 (en) * | 2015-10-09 | 2017-04-13 | Applied Materials, Inc. | Showerhead assembly with multiple fluid delivery zones |
US9846605B2 (en) | 2012-01-19 | 2017-12-19 | Microsoft Technology Licensing, Llc | Server-side minimal download and error failover |
US10042946B2 (en) * | 2016-06-07 | 2018-08-07 | Wesley John Boudville | Hashtag, deep link and linket for more user interactions |
US10114805B1 (en) * | 2014-06-17 | 2018-10-30 | Amazon Technologies, Inc. | Inline address commands for content customization |
US10120876B2 (en) * | 2015-05-13 | 2018-11-06 | Samsung Electronics Co., Ltd. | Unguided application crawling architecture |
US10142399B2 (en) | 2011-12-05 | 2018-11-27 | Microsoft Technology Licensing, Llc | Minimal download and simulated page navigation features |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2513525A (en) | 2012-07-30 | 2014-11-05 | Ibm | Provision of alternative text for use in association with image data |
CN104884452A (en) | 2012-11-20 | 2015-09-02 | 沃泰克斯药物股份有限公司 | Compounds useful as inhibitors of indoleamine 2,3-dioxygenase |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6101531A (en) * | 1995-12-19 | 2000-08-08 | Motorola, Inc. | System for communicating user-selected criteria filter prepared at wireless client to communication server for filtering data transferred from host to said wireless client |
US20020054587A1 (en) * | 1997-09-26 | 2002-05-09 | Baker Thomas E. | Integrated customer web station for web based call management |
US20030118167A1 (en) * | 1997-02-26 | 2003-06-26 | Call Sciences | Personal web-based teleconferencing method and system |
US6693652B1 (en) * | 1999-09-28 | 2004-02-17 | Ricoh Company, Ltd. | System and method for automatic generation of visual representations and links in a hierarchical messaging system |
US20040172584A1 (en) * | 2003-02-28 | 2004-09-02 | Microsoft Corporation | Method and system for enhancing paste functionality of a computer software application |
US20050210145A1 (en) * | 2000-07-24 | 2005-09-22 | Vivcom, Inc. | Delivering and processing multimedia bookmark |
US20060075205A1 (en) * | 2004-09-24 | 2006-04-06 | International Business Machines Corporation | Creating annotations of transient computer objects |
US20060230011A1 (en) * | 2004-11-22 | 2006-10-12 | Truveo, Inc. | Method and apparatus for an application crawler |
US20070054627A1 (en) * | 2005-08-23 | 2007-03-08 | Research In Motion Limited | Method and system for transferring an application state from a first electronic device to a second electronic device |
US20070162568A1 (en) * | 2006-01-06 | 2007-07-12 | Manish Gupta | Dynamic media serving infrastructure |
-
2007
- 2007-07-09 US US11/775,097 patent/US20090015599A1/en not_active Abandoned
-
2008
- 2008-07-03 WO PCT/US2008/069240 patent/WO2009009442A2/en active Application Filing
- 2008-07-04 TW TW097125192A patent/TW200925893A/en unknown
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6101531A (en) * | 1995-12-19 | 2000-08-08 | Motorola, Inc. | System for communicating user-selected criteria filter prepared at wireless client to communication server for filtering data transferred from host to said wireless client |
US20030118167A1 (en) * | 1997-02-26 | 2003-06-26 | Call Sciences | Personal web-based teleconferencing method and system |
US20020054587A1 (en) * | 1997-09-26 | 2002-05-09 | Baker Thomas E. | Integrated customer web station for web based call management |
US6693652B1 (en) * | 1999-09-28 | 2004-02-17 | Ricoh Company, Ltd. | System and method for automatic generation of visual representations and links in a hierarchical messaging system |
US20050210145A1 (en) * | 2000-07-24 | 2005-09-22 | Vivcom, Inc. | Delivering and processing multimedia bookmark |
US20040172584A1 (en) * | 2003-02-28 | 2004-09-02 | Microsoft Corporation | Method and system for enhancing paste functionality of a computer software application |
US20060075205A1 (en) * | 2004-09-24 | 2006-04-06 | International Business Machines Corporation | Creating annotations of transient computer objects |
US20060230011A1 (en) * | 2004-11-22 | 2006-10-12 | Truveo, Inc. | Method and apparatus for an application crawler |
US20070054627A1 (en) * | 2005-08-23 | 2007-03-08 | Research In Motion Limited | Method and system for transferring an application state from a first electronic device to a second electronic device |
US20070162568A1 (en) * | 2006-01-06 | 2007-07-12 | Manish Gupta | Dynamic media serving infrastructure |
Cited By (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9609034B2 (en) | 2002-12-27 | 2017-03-28 | The Nielsen Company (Us), Llc | Methods and apparatus for transcoding metadata |
US9900652B2 (en) | 2002-12-27 | 2018-02-20 | The Nielsen Company (Us), Llc | Methods and apparatus for transcoding metadata |
US20090024923A1 (en) * | 2007-07-18 | 2009-01-22 | Gunthar Hartwig | Embedded Video Player |
US9553947B2 (en) * | 2007-07-18 | 2017-01-24 | Google Inc. | Embedded video playlists |
US8069414B2 (en) | 2007-07-18 | 2011-11-29 | Google Inc. | Embedded video player |
US20090024927A1 (en) * | 2007-07-18 | 2009-01-22 | Jasson Schrock | Embedded Video Playlists |
US7912924B1 (en) * | 2007-11-06 | 2011-03-22 | Adobe Systems Incorporated | Adding functionality with respect to one or more web pages |
US20130314301A1 (en) * | 2009-03-25 | 2013-11-28 | Ami Entertainment Network, Inc. | Multi-region interactive display |
US9239695B2 (en) * | 2009-03-25 | 2016-01-19 | Ami Entertainment Network, Llc | Multi-region interactive display |
US20120191840A1 (en) * | 2009-09-25 | 2012-07-26 | Vladislav Gordon | Managing Application State Information By Means Of A Uniform Resource Identifier (URI) |
WO2011035944A1 (en) | 2009-09-25 | 2011-03-31 | International Business Machines Corporation | Managing application state information by means of a uniform resource identifier (uri) |
US20110296289A1 (en) * | 2010-05-25 | 2011-12-01 | Sony Corporation | Information processing device, content display method, and computer program |
US9128751B2 (en) * | 2010-05-25 | 2015-09-08 | Sony Corporation | Schema-based link processing |
US9380356B2 (en) | 2011-04-12 | 2016-06-28 | The Nielsen Company (Us), Llc | Methods and apparatus to generate a tag for media content |
US9681204B2 (en) | 2011-04-12 | 2017-06-13 | The Nielsen Company (Us), Llc | Methods and apparatus to validate a tag for media |
US11296962B2 (en) | 2011-06-21 | 2022-04-05 | The Nielsen Company (Us), Llc | Monitoring streaming media content |
US9838281B2 (en) | 2011-06-21 | 2017-12-05 | The Nielsen Company (Us), Llc | Monitoring streaming media content |
US9210208B2 (en) | 2011-06-21 | 2015-12-08 | The Nielsen Company (Us), Llc | Monitoring streaming media content |
US11784898B2 (en) | 2011-06-21 | 2023-10-10 | The Nielsen Company (Us), Llc | Monitoring streaming media content |
US10791042B2 (en) | 2011-06-21 | 2020-09-29 | The Nielsen Company (Us), Llc | Monitoring streaming media content |
US9515904B2 (en) | 2011-06-21 | 2016-12-06 | The Nielsen Company (Us), Llc | Monitoring streaming media content |
US11252062B2 (en) | 2011-06-21 | 2022-02-15 | The Nielsen Company (Us), Llc | Monitoring streaming media content |
US20120331372A1 (en) * | 2011-06-24 | 2012-12-27 | Usablenet Inc. | Methods for making ajax web applications bookmarkable and crawlable and devices thereof |
US8527862B2 (en) * | 2011-06-24 | 2013-09-03 | Usablenet Inc. | Methods for making ajax web applications bookmarkable and crawlable and devices thereof |
US10015226B2 (en) | 2011-06-24 | 2018-07-03 | Usablenet Inc. | Methods for making AJAX web applications bookmarkable and crawlable and devices thereof |
US10142399B2 (en) | 2011-12-05 | 2018-11-27 | Microsoft Technology Licensing, Llc | Minimal download and simulated page navigation features |
US20130191435A1 (en) * | 2012-01-19 | 2013-07-25 | Microsoft Corporation | Client-Side Minimal Download and Simulated Page Navigation Features |
US10289743B2 (en) * | 2012-01-19 | 2019-05-14 | Microsoft Technology Licensing, Llc | Client-side minimal download and simulated page navigation features |
US9846605B2 (en) | 2012-01-19 | 2017-12-19 | Microsoft Technology Licensing, Llc | Server-side minimal download and error failover |
US20130227457A1 (en) * | 2012-02-24 | 2013-08-29 | Samsung Electronics Co. Ltd. | Method and device for generating captured image for display windows |
US9209978B2 (en) | 2012-05-15 | 2015-12-08 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US9197421B2 (en) | 2012-05-15 | 2015-11-24 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US9357261B2 (en) | 2013-02-14 | 2016-05-31 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US9313544B2 (en) | 2013-02-14 | 2016-04-12 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US20140244828A1 (en) * | 2013-02-26 | 2014-08-28 | Jan Besehanic | Methods and apparatus to measure exposure to streaming media |
US11197046B2 (en) | 2013-10-10 | 2021-12-07 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US9332035B2 (en) | 2013-10-10 | 2016-05-03 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US10356455B2 (en) | 2013-10-10 | 2019-07-16 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US11563994B2 (en) | 2013-10-10 | 2023-01-24 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US10687100B2 (en) | 2013-10-10 | 2020-06-16 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US9503784B2 (en) | 2013-10-10 | 2016-11-22 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US10114805B1 (en) * | 2014-06-17 | 2018-10-30 | Amazon Technologies, Inc. | Inline address commands for content customization |
US10120876B2 (en) * | 2015-05-13 | 2018-11-06 | Samsung Electronics Co., Ltd. | Unguided application crawling architecture |
US9832123B2 (en) * | 2015-09-11 | 2017-11-28 | Cisco Technology, Inc. | Network named fragments in a content centric network |
US20170078199A1 (en) * | 2015-09-11 | 2017-03-16 | Palo Alto Research Center Incorporated | Network named fragments in a content centric network |
US10419345B2 (en) | 2015-09-11 | 2019-09-17 | Cisco Technology, Inc. | Network named fragments in a content centric network |
US20170101712A1 (en) * | 2015-10-09 | 2017-04-13 | Applied Materials, Inc. | Showerhead assembly with multiple fluid delivery zones |
US10042946B2 (en) * | 2016-06-07 | 2018-08-07 | Wesley John Boudville | Hashtag, deep link and linket for more user interactions |
Also Published As
Publication number | Publication date |
---|---|
TW200925893A (en) | 2009-06-16 |
WO2009009442A2 (en) | 2009-01-15 |
WO2009009442A3 (en) | 2009-03-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20090015599A1 (en) | Draggable mechanism for identifying and communicating the state of an application | |
US10817663B2 (en) | Dynamic native content insertion | |
US7747681B2 (en) | Systems and methods for conducting internet content usage experiments | |
TWI409647B (en) | Provisioning a portlet viewer for viewing drag-and-drop content in a portal environment | |
US7631007B2 (en) | System and method for tracking user activity related to network resources using a browser | |
US7506019B2 (en) | Media player system | |
EP2332063B1 (en) | Uniquely identifying network-distributed devices without explicitly provided device or user identifying information | |
US8122360B2 (en) | Automatic selection of user-oriented web content | |
US7865544B2 (en) | Method and system for providing XML-based asynchronous and interactive feeds for web applications | |
US7702811B2 (en) | Method and apparatus for marking of web page portions for revisiting the marked portions | |
US10671698B2 (en) | Language translation using embeddable component | |
US20120011262A1 (en) | Method and System of Processing Cookies Across Domains | |
US9210237B2 (en) | Cached data detection | |
US20060230059A1 (en) | Method and apparatus to select and deliver portable portlets | |
US7987243B2 (en) | Method for media discovery | |
US9912767B1 (en) | Third-party cross-site data sharing | |
WO2010094927A1 (en) | Content access platform and methods and apparatus providing access to internet content for heterogeneous devices | |
US20090083289A1 (en) | System For Accessing A Service Associated With A Resource | |
US20080275963A1 (en) | Dynamically Modifying A Universal Resource Indicator | |
RU2272318C2 (en) | Computer-readable data carrier, on which image file is recorded, device for making a data carrier, carrier on which program is recorded for forming an image file, device for transferring image file, device for processing image file and carrier, on which program for processing an image file is recorded | |
US8239522B1 (en) | Dynamic variables for tracking wireless device website usage | |
US7574701B2 (en) | Syntax for members added through object protocol systems and methods | |
KR20020096519A (en) | System for collecting information based on internet | |
JP2007310808A (en) | Browsing place retrieval method, device and program | |
CN116502001A (en) | Webpage display method and device, electronic equipment and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: YAHOO| INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BENNETT, JEFFERY;SHAFTON, PETER;BLINNIKKA, TOMI;REEL/FRAME:019532/0920 Effective date: 20070706 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: YAHOO HOLDINGS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:YAHOO| INC.;REEL/FRAME:042963/0211 Effective date: 20170613 |
|
AS | Assignment |
Owner name: OATH INC., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:YAHOO HOLDINGS, INC.;REEL/FRAME:045240/0310 Effective date: 20171231 |