Multi-view masters for graphical designs
US-12164858-B2 · Dec 10, 2024 · US
US2016196009A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016196009-A1 |
| Application number | US-201615011043-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jan 29, 2016 |
| Priority date | Oct 19, 2011 |
| Publication date | Jul 7, 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.
In one set of embodiments, methods, systems, and apparatus are provided that include presenting, by a computer system, a task flow in a popup component of an application user interface executing in a user interface layer, where the task flow executes in an application layer of the computer system, and also include communicating, by the computer system, a first notification from the application layer to the user interface layer in response to normal completion of the task flow, and updating, e.g., closing, the component in the application user interface based upon the first notification. A second notification may be communicated from the user interface layer to the application layer in response to a user interface event that is associated with the popup component and causes an abnormal termination of the task flow. Presenting may include displaying the task flow in a region component in the popup component.
Opening claim text (preview).
What is claimed is: 1 . A method comprising: presenting, by a computer system, a task flow in an application user interface, the application user interface executing in a user interface layer of the computer system, and the task flow executing in an application layer of the computer system, wherein the presenting comprises displaying the task flow in a region component and displaying the region component in a first popup component, the first popup component being displayed in a window of the application user interface; communicating, by the computer system, a first notification indicating completion of the task flow from the application layer to the user interface layer in response to completion of the task flow, receiving, by the computer system at the user interface layer, the first notification; and updating, by the computer system, the first popup component in the application user interface in response to receiving the first notification. 2 . The method of claim 1 , wherein the updating comprises closing the first popup component. 3 . The method of claim 1 , wherein the first popup component overlays at least a portion of the application user interface, the method further comprising: presenting, by the computer system, a second task flow in a second popup component, wherein the second popup component overlays the first popup component in the application user interface. 4 . The method of claim 3 , wherein the first and second popup components are presented in different regions. 5 . The method of claim 1 , wherein the task flow is a bounded task flow having defined start and end portions. 6 . The method of claim 5 , wherein the task flow includes one or more page fragments, and the presenting comprises rendering the one or more page fragments in the region component. 7 . The method of claim 1 , further comprising: receiving, by the computer system at the user interface layer, a user interface event that indicates a request to close the first popup component; communicating, by the computer system, a second notification indicating the request to close the popup component from the user interface layer to the application layer in response to receiving the user interface event; receiving, by the computer system at the application layer, the second notification; and executing, by the computer system, an action in the application layer in response to receiving the second notification. 8 . The method of claim 7 , wherein executing the action comprises rolling back and terminating the task flow. 9 . The method of claim 7 , wherein executing the action comprises communicating, by the computer system, a third notification indicating uncommitted transaction data from the application layer to the user interface layer, the method further comprising: receiving, by the computer system in the user interface layer, the third notification indicating uncommitted transaction data; causing display, by the computer system, of a confirmation dialog in the user interface layer in response to receiving the third notification indicating uncommitted transaction data; receiving, by the computer system, a user response to the confirmation dialog in the user interface layer, wherein the user response indicates that the uncommitted transaction data is to be saved; communicating, by the computer system, the user response to the application layer; receiving, at the application layer, the user response; causing, by the computer system at the application layer, the uncommitted data to be saved in response to the user response; and rolling back and terminating, by the computer system at the application layer, the task flow. 10 . A system comprising: a processor configured to: present a task flow in an application user interface, the application user interface executing in a user interface layer of the system, and the task flow executing in an application layer of the system, the task flow being displayed in a region component, the region component being displayed in a first popup component, and the first popup component being displayed in a window of the application user interface; communicate a first notification indicating completion of the task flow from the application layer to the user interface layer in response to completion of the task flow, receive, at the user interface layer, the first notification; and update the first popup component in the application user interface in response to receiving the first notification, wherein the task flow is a bounded task flow having defined start and end portions. 11 . The system of claim 10 , wherein the first popup component overlays at least a portion of the application user interface, and the processor is further configured to: present a second task flow in a second popup component, wherein the second popup component overlays the first popup component in the application user interface. 12 . The system of claim 11 , wherein the processor is further configured to present the first and second popup components in different regions. 13 . The system of claim 10 , wherein the task flow includes one or more page fragments, and the processor is configured to render the one or more page fragments in the region component. 14 . The system of claim 10 , the processor further configured to: receive, at the user interface layer, a user interface event that indicates a request to close the first popup component; communicate a second notification indicating the request to close the first popup component from the user interface layer to the application layer in response to receiving the user interface event; receive, at the application layer, the second notification; and execute an action in the application layer in response to receiving the second notification. 15 . The system of claim 14 , wherein the action comprises rolling back and terminating the task flow. 16 . The system of claim 14 , wherein the action comprises communicating a third notification indicating uncommitted transaction data from the application layer to the user interface layer, and the processor is further configured to: receive, in the user interface layer, the third notification indicating uncommitted transaction data; cause display of a confirmation dialog in the user interface layer in response to receiving the third notification indicating uncommitted transaction data; receive a user response to the confirmation dialog in the user interface layer, wherein the user response indicates that the uncommitted transaction data is to be saved; communicate the user response to the application layer; receive, at the application layer, the user response; cause, at the application layer, the uncommitted data to be saved in response to the user response; and roll back and terminate, at the application layer, the task flow. 17 . A non-transitory machine-readable medium for a computer system, the non-transitory machine-readable medium having stored thereon a series of instructions executable by a processor, the series of instructions comprising: instructions that cause the processor to present a task flow in an application user interface, the application user interface executing in a user interface layer of the system, and the task flow executing in an application layer of the system, the task flow being displayed in a region component, the region component being displayed in a first popup component, and the first popup component being displayed in a window of the application user interface; instructions that cause the processor to
Interaction techniques to control parameter settings, e.g. interaction with sliders or dials · CPC title
for implementing user interfaces · CPC title
based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.