Presenting Search Results in a Dynamically Formatted Graphical User Interface
US-2024420206-A1 · Dec 19, 2024 · US
US2016103805A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016103805-A1 |
| Application number | US-201514878148-A |
| Country | US |
| Kind code | A1 |
| Filing date | Oct 8, 2015 |
| Priority date | Oct 9, 2014 |
| Publication date | Apr 14, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A variety of data structures, components, runtime viewers and methods are described for defining, delivering and rendering wrapped packages of cards in a manner particularly well suited, but not limited to, display on mobile devices. Each card may selectively include media content, a palette of application functionality and/or supporting e-commerce related services. A wrap descriptor, composed of a plurality of card descriptors defines the structure, layout and content of a set of cards that constitute the wrap. The wrap descriptor may take the form of a JSON data object. A runtime viewer that executes on the rendering computing device may be used to transform the wrap descriptor into a runtime instance of the wrap that includes the content and functionality defined by the descriptor. In some implementations, the runtime viewer creates an object graph, which may then be converted to an object model suitable for rendering on the consuming device.
Opening claim text (preview).
What is claimed is: 1 . A runtime viewer embedded in a tangible computer readable medium and arranged to operate on a computing device to generate an instance of a wrap package of cards to be displayed on a screen associated with the computing device based on a JSON wrap descriptor that defines the structure, layout and content of the set of cards, the runtime viewer comprising: a deserializer arranged to create an object graph of the wrap package based on the wrap descriptor, and a document object model (DOM) of the wrap package based on the object graph, wherein the object graph includes an ordered card list that defines an order of the cards, and a plurality of card definitions, each card definition corresponding to an associated one of the cards and having at least one associated component; and an event handler arranged to handle user inputted navigation commands to facilitate navigation between the cards of the wrap package when the wrap package is displayed on the screen; and wherein the runtime viewer is configured to obtain the wrap descriptor, create the wrap package instance based on the wrap descriptor at a computing device, and render the wrap package instance in a browser executing on the computing device. 2 . A runtime viewer as recited in claim 1 wherein the JSON data object is a BSON (Binary JSON) data object. 3 . A runtime viewer as recited in claim 1 wherein the ordered card list is a doubly linked list. 4 . A runtime viewer as recited in claim 1 , further comprising a dependent card list arranged to identify one or more cards that are dependent upon an associated card in the ordered card list. 5 . A runtime viewer as recited in claim 1 , wherein the object graph further includes an asset load state structure that includes a multiplicity of asset entries, each asset entry corresponding to an associated asset referenced in the wrap descriptor that is arranged to be obtained from a source external to the wrap descriptor, wherein each entry in the asset load state structure is arranged to indicate whether the associated referenced asset has been loaded into the object graph. 6 . A runtime viewer as recited in claim 1 , wherein: the JSON wrap descriptor includes a plurality of cards descriptors, each card descriptor arranged to define the structure, layout and content of an associated one of the cards; and the cards all have the same aspect ratio when rendered, and within each card, the relative positioning of the content of the card is immutable. 7 . A runtime viewer as recited in claim 1 , wherein: the wrap descriptor includes at least one behavior declaration; and for each behavior declaration, the deserializer associates a corresponding behavior with a corresponding component in the wrap package instance based upon a corresponding behavior definition. 8 . A runtime viewer as recited in claim 7 further comprising a library of behavior definitions, wherein when a selected one of the behaviors declared in the wrap descriptor has a corresponding behavior definition in the library of behavior definitions, the corresponding behavior definition is used to associate the selected behavior with the associated component. 9 . A runtime viewer as recited in claim 8 , wherein when the selected behavior does not have a corresponding behavior definition in the library of behavior definitions, the runtime viewer obtains an appropriate behavior definition from a source external to the computing device. 10 . A runtime viewer as recited in claim 1 wherein: the ordered card list is a doubly linked list; the object graph further includes an asset load state structure that includes a multiplicity of asset entries, each asset entry corresponding to an associated asset referenced in the wrap descriptor that is arranged to be obtained from a source external to the wrap descriptor, wherein each entry in the asset load state structure is arranged to indicate whether the associated referenced asset has been loaded into the object graph; the wrap descriptor includes a plurality of cards descriptors, each card descriptor arranged to define the structure, layout and content of an associated one of the cards and at least one behavior declaration; for each behavior declaration, the deserializer associates a corresponding behavior with a corresponding component in the wrap package instance based upon a corresponding behavior definition; and the cards all have the same aspect ratio when rendered, and within each card, the relative positioning of the content of the card is immutable; and the runtime viewer further comprises a library of behavior definitions, wherein when a selected one of the behaviors declared in the wrap descriptor has a corresponding behavior definition in the library of behavior definitions, the corresponding behavior definition is used to associate the selected behavior with the associated component. 11 . A runtime viewer as recited in claim 1 , further comprising an event handler arranged to handle user inputted navigation commands to facilitate navigation between cards within the wrap package when the wrap package is displayed on the screen. 12 . A runtime viewer as recited in claim 11 wherein the event handler includes: a set of event handling components, each event handling components being arranged to handle one or more specific events; a handler registry that identifies the set of available event handling components; and a current handler set list that identifies a set of the available event handling components that are currently active; and a handler rules engine that provides rules regarding the selection of a particular one of the of the currently active event handling components in response to the receipt of a particular event. 13 . A runtime viewer embedded in a tangible computer readable medium and arranged to operate on a computing device to generate an instance of a wrap package of cards to be displayed on a screen associated with the computing device based on a wrap descriptor, the runtime viewer comprising: a deserializer arranged to create an object model of the wrap package of cards based on the wrap descriptor; and an event handler arranged to handle user inputted navigation commands to facilitate navigation between the cards of the wrap package when the wrap package is displayed on the screen. 14 . A runtime viewer as recited in claim 13 wherein: the deserializer is further arranged to create an object graph based on the wrap descriptor, wherein the object graph represents the wrap package in the runtime viewer; and the object model is created based on the object graph. 15 . A runtime viewer as recited in claim 14 wherein the object model conforms with the document object model (DOM) convention. 16 . A runtime viewer as recited in claim 14 wherein the object graph includes: a plurality of card definitions, each card definition corresponding to an associated one of the cards and having at least one associated component; and an ordered card list that defines an order of the cards. 17 . A runtime viewer as recited in claim 14 , wherein the object graph further includes an asset load state structure that includes a multiplicity of asset entries, each asset entry corresponding to an associated asset referenced in the wrap descriptor that is arranged to be obtained from a source external to the wrap descriptor. 18 . A runtime viewer as recited in claim 13 , wherein: the wrap descriptor includes a plurality of cards descriptors, each card descriptor arranged to define the
Interaction with lists of selectable items, e.g. menus · CPC title
Physics · mapped topic
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 · CPC title
Physics · mapped topic
Execution arrangements for user interfaces · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.