WO2015048205A1 - Persisting state at scale across browser sessions - Google Patents
Persisting state at scale across browser sessions Download PDFInfo
- Publication number
- WO2015048205A1 WO2015048205A1 PCT/US2014/057323 US2014057323W WO2015048205A1 WO 2015048205 A1 WO2015048205 A1 WO 2015048205A1 US 2014057323 W US2014057323 W US 2014057323W WO 2015048205 A1 WO2015048205 A1 WO 2015048205A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user interface
- state
- interface elements
- user
- parent
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2428—Query predicate definition using graphical user interfaces, including menus and forms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/332—Query formulation
- G06F16/3329—Natural language query formulation or dialogue systems
-
- 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/017—Gesture based interaction, e.g. based on a set of recognized hand gestures
-
- 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]
-
- 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/0481—Interaction techniques based on graphical user interfaces [GUI] 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
-
- 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/0481—Interaction techniques based on graphical user interfaces [GUI] 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
- G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] 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 using icons
-
- 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/0481—Interaction techniques based on graphical user interfaces [GUI] 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
- G06F3/0482—Interaction with lists of selectable items, e.g. menus
-
- 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
-
- 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/04842—Selection of displayed objects or displayed text elements
-
- 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/0485—Scrolling or panning
-
- 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/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
- G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/103—Formatting, i.e. changing of presentation of documents
- G06F40/117—Tagging; Marking up; Designating a block; Setting of attributes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- 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
-
- 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/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
- G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
-
- 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/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
- G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
Definitions
- At least some embodiments described herein relate to the management of application state storage associated with a hierarchical application.
- the hierarchical application includes multiple parent user interface elements, each of at least some having child user interface elements arranged in a corresponding hierarchy.
- the user may navigate through the hierarchical application. For instance, by selecting a child user interface element of a first parent user interface element having a first hierarchy of child user interface elements, the user might navigate to (and potentially also create) a second parent user interface element having a second hierarchy of child user interface elements.
- a hierarchical storage agent manages the state of the hierarchical application.
- the hierarchical storage agent provides application state to a remote storage over an application program interface in a manner that preserves at least some of the hierarchy of one or more parent user interface elements of the hierarchical application.
- the application program interface also allows the retrieval of hierarchically described portions of the remotely saved state. Accordingly, as navigation and edit operations occur in the hierarchical application, the corresponding navigation or edit state may be incrementally preserved. Since the amount of information passing through the API is much smaller due to the hierarchical structure of the storage, the providing of state (i.e., saving) may be performed much more frequently, perhaps in response to every navigation or edit event that changes application state.
- Figure 1 abstractly illustrates an example computing system in which the principles described herein may be employed
- Figure 2 abstractly illustrates a user interface that a user may be experiencing and interacting with, and includes multiple parent user interface elements, each having a corresponding hierarchy of child user interface element;
- Figure 3 illustrates a supporting architecture for a user interface presentation component, allowing a user interface showing a hierarchical application to hierarchically store and retrieve application state from a storage in a manner that preserves hierarchy;
- Figure 4 illustrates a flowchart of a method for reconstructing all or a portion of a user interface previously interacted with by a user
- Figure 5 illustrates an environment that includes a displayed portion of a user interface showing four blades, each having a hierarchy of parts;
- Figure 6 illustrate an environment in which an application provides state via a view model to a user interface element.
- the principles described herein involve augmenting an application in such a way that user interface state is implicitly and automatically saved as the user interacts with the application, and later restored so that the user interface state remains consistent when it is re-rendered. For instance, state would be restored when the application is restarted. It can also be restored as user interface controls are instantiated when windows/pages are restored on screen due to user interaction. Accordingly, the user experience has two distinct phases, one when the user is first interacting with the user interface to thereby affect user interface state, and one when the application is restarted and the user is hoping for the same user interface state.
- a user interface program presents multiple parent user interface elements, each having a corresponding hierarchy of contained user interface elements.
- the user may navigate, between the parent user interface elements. For instance, the user may select or otherwise interact with a child user interface element of one parent user interface element to generate another parent user interface element.
- the user may also edit user interface elements by entering or inputting data into the user interface elements, or reconfiguring one or more user interface elements.
- a hierarchical storage agent tracks the navigation and editing activity of the user and provides corresponding state to a remote storage using an application program interface.
- the provided state includes a navigation sequence through which a user had navigated the multiple parent user interfaces. Furthermore, for each of some or all of the user interface elements, the provided state includes an edit state of the user interface element describing how the user populated the user interface elements with data that has yet to be saved.
- the provided state is provided in a manner that preserves information regarding the corresponding hierarchy of the parent user interface elements in the remote storage.
- An application program interface is provided for this purpose, which also allows retrieval of the state for different granularities ranging from perhaps all of the state for the user interface, to perhaps state for just a single parent user interface element, to perhaps only hierarchically described portions of a specific user interface element.
- a user interface may retrieve the provided state to thereby repopulate all or portions of a user interface. For instance, this might be used in a simple restart scenario in which a browser refreshes, and the state is restored with all of the user's work preserved. This might be used in a sharing scenario in which the user allows another user to access the state to restore the first user's work and user interface experience to a second user. If this is done concurrently with the first user's work, this may also support a collaboration experience. The same user might also roam from one computer to another, and use the restored state to continue working where the user had left off. Thus, the user experience is enhanced, even in complex environments involving hierarchically structured user elements.
- Computing systems are now increasingly taking a wide variety of forms.
- Computing systems may, for example, be handheld devices, appliances, laptop computers, desktop computers, mainframes, distributed computing systems, or even devices that have not conventionally been considered a computing system.
- the term "computing system” is defined broadly as including any device or system (or combination thereof) that includes at least one physical and tangible processor, and a physical and tangible memory capable of having thereon computer-executable instructions that may be executed by the processor.
- the memory may take any form and may depend on the nature and form of the computing system.
- a computing system may be distributed over a network environment and may include multiple constituent computing systems.
- a computing system 100 typically includes at least one processing unit 102 and memory 104.
- the memory 104 may be physical system memory, which may be volatile, non-volatile, or some combination of the two.
- the term “memory” may also be used herein to refer to nonvolatile mass storage such as physical storage media. If the computing system is distributed, the processing, memory and/or storage capability may be distributed as well.
- the term "executable module” or “executable component” can refer to software objects, routines, or methods that may be executed on the computing system. The different components, modules, engines, and services described herein may be implemented as objects or processes that execute on the computing system (e.g., as separate threads).
- embodiments are described with reference to acts that are performed by one or more computing systems. If such acts are implemented in software, one or more processors of the associated computing system that performs the act direct the operation of the computing system in response to having executed computer- executable instructions.
- such computer-executable instructions may be embodied on one or more computer-readable media that form a computer program product.
- An example of such an operation involves the manipulation of data.
- the computer-executable instructions (and the manipulated data) may be stored in the memory 104 of the computing system 100.
- Computing system 100 may also contain communication channels 108 that allow the computing system 100 to communicate with other message processors over, for example, network 110.
- the computing system 100 also includes a display 112 on which a user interface, such as the user interfaces described herein, may be rendered.
- a user interface such as the user interfaces described herein
- Such user interfaces may be generated in computer hardware or other computer-represented form prior to rendering.
- the presentation and/or rendering of such user interfaces may be performed by the computing system 100 by having the processing unit(s) 102 execute one or more computer-executable instructions that are embodied on one or more computer- readable media.
- Such computer-readable media may form all or a part of a computer program product.
- Embodiments described herein may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below.
- Embodiments described herein also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures.
- Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system.
- Computer-readable media that store computer-executable instructions are physical storage media.
- Computer-readable media that carry computer- executable instructions are transmission media.
- embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: computer storage media and transmission media.
- Computer storage media includes RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
- a "network” is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices.
- a network or another communications connection can include a network and/or data links which can be used to carry or desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.
- program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (or vice versa).
- computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a "NIC"), and then eventually transferred to computer system RAM and/or to less volatile computer storage media at a computer system.
- a network interface module e.g., a "NIC”
- NIC network interface module
- computer storage media can be included in computer system components that also (or even primarily) utilize transmission media.
- Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
- the computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code.
- the invention may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, pagers, routers, switches, and the like.
- the invention may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks.
- program modules may be located in both local and remote memory storage devices.
- FIG. 2 illustrates a user interface 200 that a user may be experiencing and interacting with.
- the user interface 200 includes a first parent user interface element 201 that contains multiple child user interface elements 211 through 215 in accordance with a particular hierarchy suitable for the first parent user interface element 201.
- a second parent user interface element 202 also contains multiple child user interface elements 221 through 226 arranged in accordance with another particular hierarchy suitable for the second parent user interface element 202.
- the ellipses 203 represent that there may be further parent user interface elements in the user interface 200.
- the user may navigate through the user interface 200. For instance, in order to generate the second parent user interface element 202, the user might have selected one of the child user interface elements of the first parent user interface element 201.
- Figure 3 illustrates a supporting architecture 300 for a user interface component.
- a user interface presentation component 302 presents a user interface 301.
- the user interface 301 may represent the user interface 200 of Figure 2.
- a hierarchical storage agent 303 provides state (as represented by arrow 311) to a remote storage 321 using an Application Program Interface (API) 320.
- the remote storage 321 might be, for example, cloud based storage, a storage within a storage area network, or any other remote storage.
- the provided state includes navigation state representing how a user navigated through at least some of the user interface elements to arrive at a current state.
- the provided state also includes state of each of some or all of the user interface elements within the user interface 301.
- the provided state might include state from the parent user interface elements 201 and 202 and their child user elements, or a subset of those user interface elements.
- the state is provided through a flexible API 320.
- the API 320 and/or the manner in which the provided state is structured preserves information regarding the original hierarchy of the user interface elements from which the state came. That way, when the state is retrieved, the relevant state may be applied to the appropriate user interface elements.
- the API 320 perhaps provides state to be saved and/or retrieves the state using different granularities. For instance, all of the state of the user interface 200 might be saved and/or retrieved in a single call or handshake. However, finer granularities might be saved and/or retrieved, such as perhaps at the granularity of a parent user interface elements, the granularity of a child user interface element, or even perhaps at the granularity of a portion of the state of a user interface element.
- the API 320 would respond to the hierarchical data identification provided by the hierarchical storage agent 303 by retrieving the identified hierarchically structured data from, or providing such hierarchically structured data to, the remote store 321.
- the hierarchical storage agent 303 updates the provided state upon further navigation by the user. For instance, a navigation component 304 detects user navigation through the user interface 301. The navigation component 304 notifies the user interface presentation component 302 so that the navigation may be reflected in the user interface 301, and also notifies the storage agent 303, so that the navigation state may be persisted in the store 321.
- the hierarchical storage agent 303 also updates the provided state upon a change in at least some state of the user interface elements.
- an edit component 305 allows the user to edit user interface components within the user interface 301.
- the editing is detected by the edit component 305, and caused to project back to the user interface 301 via the user interface presentation component 302.
- the editing causes the hierarchical storage agent to provide further state representing the editing to the remote storage. For instance, a user might edit data within a field, which in a broad context, is a state of the user interface element. On the other hand, the user might change the appearance or properties of the user interface element itself.
- the editing component 305 might not cause all editing state to be persisted. For instance, if the user were to change the size or otherwise reconfigure or move a user interface element, these operations might be not be important to the user on a permanent basis. Accordingly, the user element might be marked to indicate which reconfiguring and/or editing operations are to be persisted.
- the editing component 305 might also determine whether to make the corresponding edit only to the user interface element that was edited, or whether to make the corresponding edit to one or more related user interface elements also to which the edit may be applied.
- the editing component 305 may consider user instructions, as well as default settings in considering the scope of user interface elements to apply the change to, and cause the storage agent 303 to store the state as appropriate.
- the user interface presentation component 302 may use a number of different types of user interface elements. Some of these user interface elements may be intrinsic user interface elements 331 provided by a system that can support as a platform for operation of multiple applications. Such intrinsic user interface elements might have general utility across multiple applications. Other user interface elements may be extrinsic user interface elements 332 provided by application developers, and which might have more specific utility to that application.
- the storage agent 303 provides state associated with navigation to and from any user interface elements, and editing of any user interface element, regardless of whether the user interface element is intrinsic or extrinsic. For instance, the provided state may be associated with extrinsic elements displayed in the user interface 301 , as well as intrinsic elements from different applications also displayed in the user interface 301.
- the system 300 also includes a virtualization component 306 that determines 1) when to remove state associated with a given user interface element of the multiple parent user interface element from the computing system (e.g., from the local memory or storage associated with the user interface 301), and 2) when to retrieve state associated with the given user interface element of the multiple parent user interface elements from the remote storage 321.
- the virtualization component 306 might determine to remove state for a given user interface element from local memory and/or storage when it is less likely that the given user interface element will appear on a display of the computing system based on user navigation behavior and options.
- the virtualization component 306 might determine to retrieve state when it is more likely that the given parent user interface element will appear on a display of the computing system based on user navigation behavior.
- the virtualization component 306 might free up local memory and/or storage for parent user interface elements that are not within the display area, especially if it is not likely that the parent user interface elements will be displayed in the near future.
- state for parent user interface elements may be released from local memory and/or storage and retrieved from remote storage as appropriate so that it appears that the state is ever present on the local machine.
- the remote storage 321 can vary to enable interesting application experiences.
- the state can be stored per-user to allow for per-user customization of the application.
- the state can be stored in a "state service" available on the internet, enabling the user's application state to "roam" between computers.
- the state can be stored per-team to allow the application to show the same user interface arrangement to a group of application users.
- User interface state can be saved in a file and shared with others like one would share a word processing or spreadsheet document (created/saved by one user, and opened/modified by another, and so forth).
- FIG. 4 illustrates a flowchart of a method 400 for reconstructing all or a portion of a user interface previously interacted with by a user.
- the method 400 includes reading the user interface state that was previously provided to the store (act 401).
- the method 400 then includes using that read state to reformulate the user interfaces on a user interface in a state in which the user had previously navigated (act 402).
- an application restart e.g., a browser refresh
- Restart might occur at any time, whereas refresh usually implies that the reformulation is occurring as part of the same work session as the user interface was originally formulated in.
- a roaming scenario is enabled when the same user that formulated the user interface in the first place goes to a different display that is used to reformulate the user interface.
- a sharing scenario is enabled when a different user reformulates the user interface as compared to the original user that originally formulated the user interface.
- a collaboration scenario is enabled when the different users are formulating and reformulating in real-time.
- a more specific user interface will now be described.
- a canvas that extends in an extensible dimension (assumed horizontal in the remaining description, but may be vertical also).
- a new user interface element (called a "blade” herein) may appear and be added to the canvas in an extensible direction (assumed on the right in the remaining description, but the principles are not limited to adding blades to the right).
- Each blade is an example of a parent user interface element described above, and thus may contain multiple child user interface elements, which will be sometimes referred to herein as a "part". By selecting a part in an existing blade, a new blade may appear to the right of the canvas.
- a long sequence of blades may be formulated on the canvas, which may be an "infinite" canvas having no practical limit on the length of extensibility.
- the user may pan the canvas when the sequence of blades is too long to fit in a single display.
- Figure 5 illustrates an environment 500 that includes a displayed portion 501 of a user interface.
- the displayed portion shows pieces of four different blades 510, 520, 530 and 540, though by scrolling or panning left or right, other blades in the sequences will be exposed to view.
- the blade 520 is illustrated as including parts 521 through 524.
- the blade 530 is illustrated as including parts 531 through 535.
- the other blades 510 and 540 also have parts that are not labeled.
- the blade 520 may have been created by selecting a part in a previous blade (such as blade 510).
- the blade 530 might have been created by selecting a part in a previous blade (e.g., part 521 of blade 520).
- the blade 540 might have been created by selecting a part in a previous blade (e.g., part 531 of blade 530, or perhaps part 522 of blade 520)
- the parts contain a user interface that is generated by the provider of the system if the part is an intrinsic part, or by applications developers if the part is an extrinsic part.
- the applications are developed separately and loaded into the system.
- the system is largely unaware of the kind of user interface being generated into a given part by the application.
- this is a composed application that shows lots of user interface on screen.
- the overall user experience is greatly benefited by preserving user interface state (such as user navigation, edits, and configuration) across shutdown and restart of the system.
- user interface state such as user navigation, edits, and configuration
- the canvas can contain many, many blades arranged side by side
- the user interface state is maintained using virtualization to manage the local runtime resources in such a way that many blades do not degrade system performance due to excessive memory or processor use.
- the virtualization keeps the user interface state associated with visible blades active, while the user interface states for many or all of the off-screen blades are not retained locally.
- the "user interface state” refers to the type and relative position of each blade on the canvas, the number, arrangement and sizes of parts on each blade, as well as state contained in each part (e.g., the selection in a list part, the user-selected lines shown on a line chart part, the user-selected column names in a grid part, and so forth).
- state contained in each part e.g., the selection in a list part, the user-selected lines shown on a line chart part, the user-selected column names in a grid part, and so forth.
- the store 550 itself may be a conventional key/value structure.
- This design allows for the larger, logical state tree to be decomposed into small subtrees whose nodes are each stored under discrete keys. Since there is the potential for the user to create vast numbers of blades/parts - beyond what could be reasonably loaded into application memory and rendered as UI controls - this flattening allows for subsets of the larger state tree to be loaded and managed by the system at a given time. This is the basis for user interface virtualization.
- the application loads subsets of the state tree sufficient to render only those blades/parts that are on-screen (plus potentially some extra user interface that is slightly off-screen, to optimize for panning by the user).
- the application may save these changes incrementally. In that case, only discrete changes would be applied to the state store. There would be no wholesale rewrites of any significant part of the state tree.
- the key/value-shaped state store can be efficiently queried for batches of nodes in the logical state tree.
- Each query against the store describes those nodes whose values are to be returned to the application, sufficient to render one or more blades (and contained parts) on the screen.
- the query language uses nested queries in a novel way. In the simple example of Figure 5, the most nested query returns the key for the "current" blade on the canvas, the enclosing query returns the value of the blade node under that key.
- state store 550 is a simple key/value store and the use of the store by the application is regular, many different application scenarios can be developed in terms of this state save/restore functionality.
- state can be saved "per user" to reflect user customizations.
- state can be saved in a store hosted in a service available on the internet (at an URL known to the application), making the application state roam with the user from computer to computer.
- State can be loaded from a store shared by multiple users in a group, so that each user can see the same shared application layout/configuration.
- the store itself can be developed as a file that can be distributed/shared with others, to allow for collaboration by people using this same application.
- the user interface state stored by the system here includes state of "parts” that are themselves developed as applications, developed separately from the system itself. Importantly, being developed separately, the system has no static awareness of any application. That being the case, to save the state contained within these parts, the system dynamically interacts with the part to extract its state each time the user interacts with the part, so that the system can include part state as an aspect of the state of its containing blade.
- the part conveys state and changes to the state (reflecting user interaction) to the system using the following method referring to Figure 6.
- these parts are designed to an MVVM (model/view/view model) pattern.
- MVVM model/view/view model
- the view model determines the values shown in the view (in the part), and changes to the view model are reflected as corresponding changes to the part's user interface.
- the application-provided view model not only drives the visual experience within a part, it also models the part's savable state.
- the part in question will ultimately be disposed of - either the system itself will be closed or a blade will be panned off-screen by the user. Once disposed, a given part can be reinstantiated (when the application is restarted, when a given blade is panned back on-screen). As part of initializing such a reinstantiated part, the system will load its state properties from the settings store, and before the part is rendered, set the state properties on a new instantiated view model.
- embodiments described herein provide an effective mechanism for persisting navigation and/or edit state of an application across application restarts.
- the state of user interface elements may be virtualized through active removal and retrieval of user interface state in response to navigation behavior.
Abstract
The management of application state storage associated with a hierarchical application. The hierarchical application includes multiple parent user interface elements, each of at least some having child user interface elements arranged in a corresponding hierarchy. The user may navigate through the hierarchical application. For instance, by selecting a child user interface element of a first parent user interface element having a first hierarchy of child user interface elements, the user might navigate to (and potentially also create) a second parent user interface element having a second hierarchy of child user interface elements. A hierarchical storage agent manages the state of the hierarchical application. The hierarchical storage agent provides application state to a remote storage over an application program interface in a manner that preserves at least some of the hierarchy of one or more parent user interface elements of the hierarchical application.
Description
PERSISTING STATE AT SCALE ACROSS BROWSER SESSIONS
BACKGROUND
[0001] Often, users interact with an application up to a certain point, and thereafter restart the application. In web applications run in an internet browser, it is exceedingly easy to restart the application by running the browser's standard refresh command, or navigating to a different web site and back. Sometimes, some or all of the state of the application is not preserved prior to a restart. In computer applications that show significant user interface at the same time (such as multiple windows/pages, multiple user interface controls, and so forth), this could represent significant loss of state.
[0002] To preserve state, some applications allow the user to save in response to an explicit save command (e.g., by pressing the save button). Other applications allow the user to designate time intervals for automatic saving of the state. In either case, however, there is often some state that is not preserved through the restart. Some applications automatically save application state when the application is shut down, but not all shutdowns are orderly, and thus sometimes save at shutdown does not happen. Even if saves happen, the saves often occur in a local save only, and thus the restart cannot be from a different machine without losing state. Furthermore, if there is a loss in local storage performance, the locally saved state may not be useful anyway.
BRIEF SUMMARY
[0003] At least some embodiments described herein relate to the management of application state storage associated with a hierarchical application. The hierarchical application includes multiple parent user interface elements, each of at least some having child user interface elements arranged in a corresponding hierarchy. The user may navigate through the hierarchical application. For instance, by selecting a child user interface element of a first parent user interface element having a first hierarchy of child user interface elements, the user might navigate to (and potentially also create) a second parent user interface element having a second hierarchy of child user interface elements.
[0004] A hierarchical storage agent manages the state of the hierarchical application. The hierarchical storage agent provides application state to a remote storage over an application program interface in a manner that preserves at least some of the hierarchy of one or more parent user interface elements of the hierarchical application. The application program interface also allows the retrieval of hierarchically described portions of the remotely saved state. Accordingly, as navigation and edit operations occur in the
hierarchical application, the corresponding navigation or edit state may be incrementally preserved. Since the amount of information passing through the API is much smaller due to the hierarchical structure of the storage, the providing of state (i.e., saving) may be performed much more frequently, perhaps in response to every navigation or edit event that changes application state.
[0005] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] In order to describe the manner in which the above-recited and other advantages and features of the invention can be obtained, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:
[0007] Figure 1 abstractly illustrates an example computing system in which the principles described herein may be employed;
[0008] Figure 2 abstractly illustrates a user interface that a user may be experiencing and interacting with, and includes multiple parent user interface elements, each having a corresponding hierarchy of child user interface element;
[0009] Figure 3 illustrates a supporting architecture for a user interface presentation component, allowing a user interface showing a hierarchical application to hierarchically store and retrieve application state from a storage in a manner that preserves hierarchy;
[0010] Figure 4 illustrates a flowchart of a method for reconstructing all or a portion of a user interface previously interacted with by a user;
[0011] Figure 5 illustrates an environment that includes a displayed portion of a user interface showing four blades, each having a hierarchy of parts; and
[0012] Figure 6 illustrate an environment in which an application provides state via a view model to a user interface element.
DETAILED DESCRIPTION
[0013] In computer applications that show significant user interface at the same time (e.g., multiple windows/pages, multiple user interface controls, and so forth), the user often hopes to restore the user interface state of the aggregate application user interface when the application is restarted. Importantly, in web applications run in an internet browser, it is exceedingly easy to "restart" the application by running the browser's standard "refresh" command, or navigating to a different web site and back.
[0014] The principles described herein involve augmenting an application in such a way that user interface state is implicitly and automatically saved as the user interacts with the application, and later restored so that the user interface state remains consistent when it is re-rendered. For instance, state would be restored when the application is restarted. It can also be restored as user interface controls are instantiated when windows/pages are restored on screen due to user interaction. Accordingly, the user experience has two distinct phases, one when the user is first interacting with the user interface to thereby affect user interface state, and one when the application is restarted and the user is hoping for the same user interface state.
[0015] In accordance with the principles described herein, a user interface program presents multiple parent user interface elements, each having a corresponding hierarchy of contained user interface elements. In the first phase of a user experience, when state is being generated and stored, the user may navigate, between the parent user interface elements. For instance, the user may select or otherwise interact with a child user interface element of one parent user interface element to generate another parent user interface element. The user may also edit user interface elements by entering or inputting data into the user interface elements, or reconfiguring one or more user interface elements.
[0016] A hierarchical storage agent tracks the navigation and editing activity of the user and provides corresponding state to a remote storage using an application program interface. The provided state includes a navigation sequence through which a user had navigated the multiple parent user interfaces. Furthermore, for each of some or all of the user interface elements, the provided state includes an edit state of the user interface element describing how the user populated the user interface elements with data that has yet to be saved.
[0017] The provided state is provided in a manner that preserves information regarding the corresponding hierarchy of the parent user interface elements in the remote storage. An application program interface is provided for this purpose, which also allows
retrieval of the state for different granularities ranging from perhaps all of the state for the user interface, to perhaps state for just a single parent user interface element, to perhaps only hierarchically described portions of a specific user interface element.
[0018] In the second phase of the user experience, a user interface may retrieve the provided state to thereby repopulate all or portions of a user interface. For instance, this might be used in a simple restart scenario in which a browser refreshes, and the state is restored with all of the user's work preserved. This might be used in a sharing scenario in which the user allows another user to access the state to restore the first user's work and user interface experience to a second user. If this is done concurrently with the first user's work, this may also support a collaboration experience. The same user might also roam from one computer to another, and use the restored state to continue working where the user had left off. Thus, the user experience is enhanced, even in complex environments involving hierarchically structured user elements.
[0019] Some introductory discussion of a computing system will be described with respect to Figure 1. Then, example user interfaces, methods and supporting architectures will be described with respect to subsequent figures.
[0020] Computing systems are now increasingly taking a wide variety of forms. Computing systems may, for example, be handheld devices, appliances, laptop computers, desktop computers, mainframes, distributed computing systems, or even devices that have not conventionally been considered a computing system. In this description and in the claims, the term "computing system" is defined broadly as including any device or system (or combination thereof) that includes at least one physical and tangible processor, and a physical and tangible memory capable of having thereon computer-executable instructions that may be executed by the processor. The memory may take any form and may depend on the nature and form of the computing system. A computing system may be distributed over a network environment and may include multiple constituent computing systems.
[0021] As illustrated in Figure 1, in its most basic configuration, a computing system 100 typically includes at least one processing unit 102 and memory 104. The memory 104 may be physical system memory, which may be volatile, non-volatile, or some combination of the two. The term "memory" may also be used herein to refer to nonvolatile mass storage such as physical storage media. If the computing system is distributed, the processing, memory and/or storage capability may be distributed as well. As used herein, the term "executable module" or "executable component" can refer to software objects, routines, or methods that may be executed on the computing system. The
different components, modules, engines, and services described herein may be implemented as objects or processes that execute on the computing system (e.g., as separate threads).
[0022] In the description that follows, embodiments are described with reference to acts that are performed by one or more computing systems. If such acts are implemented in software, one or more processors of the associated computing system that performs the act direct the operation of the computing system in response to having executed computer- executable instructions. For example, such computer-executable instructions may be embodied on one or more computer-readable media that form a computer program product. An example of such an operation involves the manipulation of data. The computer-executable instructions (and the manipulated data) may be stored in the memory 104 of the computing system 100. Computing system 100 may also contain communication channels 108 that allow the computing system 100 to communicate with other message processors over, for example, network 110.
[0023] The computing system 100 also includes a display 112 on which a user interface, such as the user interfaces described herein, may be rendered. Such user interfaces may be generated in computer hardware or other computer-represented form prior to rendering. The presentation and/or rendering of such user interfaces may be performed by the computing system 100 by having the processing unit(s) 102 execute one or more computer-executable instructions that are embodied on one or more computer- readable media. Such computer-readable media may form all or a part of a computer program product.
[0024] Embodiments described herein may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below. Embodiments described herein also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media that store computer-executable instructions are physical storage media. Computer-readable media that carry computer- executable instructions are transmission media. Thus, by way of example, and not limitation, embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: computer storage media and transmission media.
[0025] Computer storage media includes RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
[0026] A "network" is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmissions media can include a network and/or data links which can be used to carry or desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.
[0027] Further, upon reaching various computer system components, program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (or vice versa). For example, computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a "NIC"), and then eventually transferred to computer system RAM and/or to less volatile computer storage media at a computer system. Thus, it should be understood that computer storage media can be included in computer system components that also (or even primarily) utilize transmission media.
[0028] Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.
[0029] Those skilled in the art will appreciate that the invention may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, pagers, routers, switches, and the like. The invention may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.
[0030] Figure 2 illustrates a user interface 200 that a user may be experiencing and interacting with. The user interface 200 includes a first parent user interface element 201 that contains multiple child user interface elements 211 through 215 in accordance with a particular hierarchy suitable for the first parent user interface element 201. A second parent user interface element 202 also contains multiple child user interface elements 221 through 226 arranged in accordance with another particular hierarchy suitable for the second parent user interface element 202. The ellipses 203 represent that there may be further parent user interface elements in the user interface 200. The user may navigate through the user interface 200. For instance, in order to generate the second parent user interface element 202, the user might have selected one of the child user interface elements of the first parent user interface element 201.
[0031] Figure 3 illustrates a supporting architecture 300 for a user interface component. A user interface presentation component 302 presents a user interface 301. For instance, the user interface 301 may represent the user interface 200 of Figure 2. A hierarchical storage agent 303 provides state (as represented by arrow 311) to a remote storage 321 using an Application Program Interface (API) 320. The remote storage 321 might be, for example, cloud based storage, a storage within a storage area network, or any other remote storage.
[0032] The provided state includes navigation state representing how a user navigated through at least some of the user interface elements to arrive at a current state. The provided state also includes state of each of some or all of the user interface elements within the user interface 301.
[0033] For instance, in the case of Figure 2, the provided state might include state from the parent user interface elements 201 and 202 and their child user elements, or a subset of those user interface elements. The state is provided through a flexible API 320. The API 320 and/or the manner in which the provided state is structured preserves information regarding the original hierarchy of the user interface elements from which the state came. That way, when the state is retrieved, the relevant state may be applied to the appropriate user interface elements.
[0034] In addition, the API 320 perhaps provides state to be saved and/or retrieves the state using different granularities. For instance, all of the state of the user interface 200 might be saved and/or retrieved in a single call or handshake. However, finer granularities might be saved and/or retrieved, such as perhaps at the granularity of a parent user interface elements, the granularity of a child user interface element, or even perhaps at the granularity of a portion of the state of a user interface element. The API 320 would respond to the hierarchical data identification provided by the hierarchical storage agent 303 by retrieving the identified hierarchically structured data from, or providing such hierarchically structured data to, the remote store 321.
[0035] The hierarchical storage agent 303 updates the provided state upon further navigation by the user. For instance, a navigation component 304 detects user navigation through the user interface 301. The navigation component 304 notifies the user interface presentation component 302 so that the navigation may be reflected in the user interface 301, and also notifies the storage agent 303, so that the navigation state may be persisted in the store 321.
[0036] The hierarchical storage agent 303 also updates the provided state upon a change in at least some state of the user interface elements. For instance, an edit component 305 allows the user to edit user interface components within the user interface 301. The editing is detected by the edit component 305, and caused to project back to the user interface 301 via the user interface presentation component 302. Also, the editing causes the hierarchical storage agent to provide further state representing the editing to the remote storage. For instance, a user might edit data within a field, which in a broad context, is a state of the user interface element. On the other hand, the user might change the appearance or properties of the user interface element itself.
[0037] In any case, the editing component 305 might not cause all editing state to be persisted. For instance, if the user were to change the size or otherwise reconfigure or move a user interface element, these operations might be not be important to the user on a
permanent basis. Accordingly, the user element might be marked to indicate which reconfiguring and/or editing operations are to be persisted.
[0038] The editing component 305 might also determine whether to make the corresponding edit only to the user interface element that was edited, or whether to make the corresponding edit to one or more related user interface elements also to which the edit may be applied. The editing component 305 may consider user instructions, as well as default settings in considering the scope of user interface elements to apply the change to, and cause the storage agent 303 to store the state as appropriate.
[0039] The user interface presentation component 302 may use a number of different types of user interface elements. Some of these user interface elements may be intrinsic user interface elements 331 provided by a system that can support as a platform for operation of multiple applications. Such intrinsic user interface elements might have general utility across multiple applications. Other user interface elements may be extrinsic user interface elements 332 provided by application developers, and which might have more specific utility to that application. The storage agent 303 provides state associated with navigation to and from any user interface elements, and editing of any user interface element, regardless of whether the user interface element is intrinsic or extrinsic. For instance, the provided state may be associated with extrinsic elements displayed in the user interface 301 , as well as intrinsic elements from different applications also displayed in the user interface 301.
[0040] The system 300 also includes a virtualization component 306 that determines 1) when to remove state associated with a given user interface element of the multiple parent user interface element from the computing system (e.g., from the local memory or storage associated with the user interface 301), and 2) when to retrieve state associated with the given user interface element of the multiple parent user interface elements from the remote storage 321. The virtualization component 306 might determine to remove state for a given user interface element from local memory and/or storage when it is less likely that the given user interface element will appear on a display of the computing system based on user navigation behavior and options. The virtualization component 306 might determine to retrieve state when it is more likely that the given parent user interface element will appear on a display of the computing system based on user navigation behavior.
[0041] For instance, instead of the two parent user interface elements 201 and 202 shown side-by-side in Figure 2, suppose that there were a hundred parent user interface
elements side -by- side. Not all of the parent user interface elements are displayable at one time given the finite dimensions of a display. Accordingly, the virtualization component 306 might free up local memory and/or storage for parent user interface elements that are not within the display area, especially if it is not likely that the parent user interface elements will be displayed in the near future. As the user navigates through the hundred parent user interface elements, state for parent user interface elements may be released from local memory and/or storage and retrieved from remote storage as appropriate so that it appears that the state is ever present on the local machine.
[0042] The remote storage 321 can vary to enable interesting application experiences. The state can be stored per-user to allow for per-user customization of the application. The state can be stored in a "state service" available on the internet, enabling the user's application state to "roam" between computers. The state can be stored per-team to allow the application to show the same user interface arrangement to a group of application users. User interface state can be saved in a file and shared with others like one would share a word processing or spreadsheet document (created/saved by one user, and opened/modified by another, and so forth).
[0043] In the second phase of the user experience, an application retrieves state from the store in order to reconstruct all or portions of the user interface. Figure 4 illustrates a flowchart of a method 400 for reconstructing all or a portion of a user interface previously interacted with by a user. The method 400 includes reading the user interface state that was previously provided to the store (act 401). The method 400 then includes using that read state to reformulate the user interfaces on a user interface in a state in which the user had previously navigated (act 402).
[0044] Various scenarios are enabled depending on the situation around reformulation of the user (which machine, which user, when reformulated). For instance, an application restart (e.g., a browser refresh) is enabled by reformulation of the user interface on the same display as was being used by the user when the state was originally formulated and the user interface displayed. Restart might occur at any time, whereas refresh usually implies that the reformulation is occurring as part of the same work session as the user interface was originally formulated in. A roaming scenario is enabled when the same user that formulated the user interface in the first place goes to a different display that is used to reformulate the user interface. A sharing scenario is enabled when a different user reformulates the user interface as compared to the original user that originally formulated
the user interface. A collaboration scenario is enabled when the different users are formulating and reformulating in real-time.
[0045] A more specific user interface will now be described. In a more specific user interface, there is a canvas that extends in an extensible dimension (assumed horizontal in the remaining description, but may be vertical also). When a user selects a user interface element on the canvas, a new user interface element (called a "blade" herein) may appear and be added to the canvas in an extensible direction (assumed on the right in the remaining description, but the principles are not limited to adding blades to the right). Each blade is an example of a parent user interface element described above, and thus may contain multiple child user interface elements, which will be sometimes referred to herein as a "part". By selecting a part in an existing blade, a new blade may appear to the right of the canvas. Thus, by interacting with the canvas, a long sequence of blades may be formulated on the canvas, which may be an "infinite" canvas having no practical limit on the length of extensibility. The user may pan the canvas when the sequence of blades is too long to fit in a single display.
[0046] For instance, Figure 5 illustrates an environment 500 that includes a displayed portion 501 of a user interface. The displayed portion shows pieces of four different blades 510, 520, 530 and 540, though by scrolling or panning left or right, other blades in the sequences will be exposed to view. The blade 520 is illustrated as including parts 521 through 524. The blade 530 is illustrated as including parts 531 through 535. The other blades 510 and 540 also have parts that are not labeled. The blade 520 may have been created by selecting a part in a previous blade (such as blade 510). The blade 530 might have been created by selecting a part in a previous blade (e.g., part 521 of blade 520). The blade 540 might have been created by selecting a part in a previous blade (e.g., part 531 of blade 530, or perhaps part 522 of blade 520)
[0047] The parts contain a user interface that is generated by the provider of the system if the part is an intrinsic part, or by applications developers if the part is an extrinsic part. The applications are developed separately and loaded into the system. The system is largely unaware of the kind of user interface being generated into a given part by the application.
[0048] Thus, this is a composed application that shows lots of user interface on screen. With such a large user interface, the overall user experience is greatly benefited by preserving user interface state (such as user navigation, edits, and configuration) across shutdown and restart of the system. Likewise, as the canvas can contain many, many
blades arranged side by side, the user interface state is maintained using virtualization to manage the local runtime resources in such a way that many blades do not degrade system performance due to excessive memory or processor use. The virtualization keeps the user interface state associated with visible blades active, while the user interface states for many or all of the off-screen blades are not retained locally.
[0049] In this particular embodiment, the "user interface state" refers to the type and relative position of each blade on the canvas, the number, arrangement and sizes of parts on each blade, as well as state contained in each part (e.g., the selection in a list part, the user-selected lines shown on a line chart part, the user-selected column names in a grid part, and so forth). The user experience of the application would be significantly degraded if any of this state were lost across shutdown/restart.
[0050] Referring again to Figure 5, as the user customizes the user interface (adds blades to the canvas, removes blades, adds/removes parts from blades, repositions parts within or between blades, resizes parts, and so forth), this is captured by the application as serializable state. This state can be thought of as a large, tree-shaped data structure - the root of the tree being the list of blades and their state, each blade containing a list of lenses (another user interface container that may contain one or more parts), each lens containing its list of parts and their state. As the user proceeds to customize the user interface (open/close a blade, add/remove a part, and so forth), updates are made to the state tree. Accordingly, subtrees of this larger canvas state may be incrementally updated and the subtrees are saved to a state store.
[0051] The store 550 itself may be a conventional key/value structure. This design allows for the larger, logical state tree to be decomposed into small subtrees whose nodes are each stored under discrete keys. Since there is the potential for the user to create vast numbers of blades/parts - beyond what could be reasonably loaded into application memory and rendered as UI controls - this flattening allows for subsets of the larger state tree to be loaded and managed by the system at a given time. This is the basis for user interface virtualization. The application loads subsets of the state tree sufficient to render only those blades/parts that are on-screen (plus potentially some extra user interface that is slightly off-screen, to optimize for panning by the user). As the user pans the canvas and blades move off-screen, the state of the blade and its contained parts is saved and application resources (memory) for the blades/parts are freed. As blades are panned onto the screen, respective blade/part state is loaded from the state store and the state is
configured into newly instantiated UI components/controls, effectively returning the UI to the state last seen by the user.
[0052] When the state tree is incrementally modified by the system in response to user customization/interaction (e.g., adding/removing a blade, adding/removing a part, interacting with a part to change its state (e.g., selecting a list item, choosing alternate columns in a grid view)), the application may save these changes incrementally. In that case, only discrete changes would be applied to the state store. There would be no wholesale rewrites of any significant part of the state tree.
[0053] In support of user interface virtualization, the key/value-shaped state store can be efficiently queried for batches of nodes in the logical state tree. Each query against the store describes those nodes whose values are to be returned to the application, sufficient to render one or more blades (and contained parts) on the screen. The query language uses nested queries in a novel way. In the simple example of Figure 5, the most nested query returns the key for the "current" blade on the canvas, the enclosing query returns the value of the blade node under that key.
[0054] Since the state store 550 is a simple key/value store and the use of the store by the application is regular, many different application scenarios can be developed in terms of this state save/restore functionality. In the simplest case, state can be saved "per user" to reflect user customizations. In other cases, state can be saved in a store hosted in a service available on the internet (at an URL known to the application), making the application state roam with the user from computer to computer. State can be loaded from a store shared by multiple users in a group, so that each user can see the same shared application layout/configuration. The store itself can be developed as a file that can be distributed/shared with others, to allow for collaboration by people using this same application.
[0055] As mentioned earlier, the user interface state stored by the system here includes state of "parts" that are themselves developed as applications, developed separately from the system itself. Importantly, being developed separately, the system has no static awareness of any application. That being the case, to save the state contained within these parts, the system dynamically interacts with the part to extract its state each time the user interacts with the part, so that the system can include part state as an aspect of the state of its containing blade.
[0056] In one embodiment, the part conveys state and changes to the state (reflecting user interaction) to the system using the following method referring to Figure 6. First,
these parts are designed to an MVVM (model/view/view model) pattern. For the system to generate user interface to be rendered within the visible boundaries of a part, that application shares with the system a view model, following the MVVM pattern. That is, the view model determines the values shown in the view (in the part), and changes to the view model are reflected as corresponding changes to the part's user interface. The application-provided view model not only drives the visual experience within a part, it also models the part's savable state. It is common that those view model properties driving visuals significantly overlap with those that should be saved/restored, so this leads to a natural application programming model for state save/restore. With this, user interactions with the part update the view and the view proceeds to reflect these changes in the view model. As the view model changes, for certain view model properties designated as "state properties" by the application authors, the system saves these part "state properties" to the settings store.
[0057] The part in question will ultimately be disposed of - either the system itself will be closed or a blade will be panned off-screen by the user. Once disposed, a given part can be reinstantiated (when the application is restarted, when a given blade is panned back on-screen). As part of initializing such a reinstantiated part, the system will load its state properties from the settings store, and before the part is rendered, set the state properties on a new instantiated view model.
[0058] Accordingly, embodiments described herein provide an effective mechanism for persisting navigation and/or edit state of an application across application restarts. Furthermore, in some embodiments, the state of user interface elements may be virtualized through active removal and retrieval of user interface state in response to navigation behavior.
[0059] The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Claims
1. A computer program product comprising one or more computer-readable storage media having thereon computer-executable instructions that are structured such that, when executed by one or more processors of a computing system, cause the computing system to instantiate and/or operate the following:
a user interface component for presenting multiple parent user interface elements having a corresponding hierarchy of contained user interface elements, the multiple parent user interface elements including at least 1) a first parent user interface element having a first hierarchy of contained user interface elements, and 2) a second parent user interface element having a second hierarchy of contained user interface elements, wherein the user may navigate, directly or indirectly, to the second parent user interface element by interfacing with the first parent user interface element; and
a hierarchical storage agent that provides state to a remote storage using an application program interface, the provided state including a state of each of at least some of the multiple parent user interface elements, including the first and second parent user interface elements, the provided state provided in a manner that preserves in the remote storage at least some of the corresponding hierarchy, the application program interface also allowing retrieval of only hierarchically described portions of the remotely saved state of the first and second parent user interface element.
2. The computer program product in accordance with Claim 1, the provided state including state from multiple user interface elements including both intrinsic user interface elements and extrinsic user interface elements.
3. The computer program product in accordance with Claim 1, the provided state including state from multiple user interface elements including extrinsic user interface elements from a first application, and extrinsic user interface elements from a second application
4. The computer program product in accordance with Claim 1, the provided state also including navigation state representing how a user navigated through at least some of the multiple parent user interface elements to arrive at a current state.
5. The computer program product in accordance with Claim 4, the hierarchical storage agent updating the provided state upon a change in at least some state of the first and second parent user interface elements.
6. The computer program product in accordance with Claim 4, the hierarchical storage agent updating the provided state upon further navigation by the user.
7. The computer program product in accordance with Claim 1, further comprising:
a virtualization component that determines 1) when to remove state associated with a given parent user interface element of the multiple parent user interface element from the computing system, and 2) when to retrieve state associated with the given parent user interface element of the multiple parent user interface elements from the remote storage.
8. The computer program product in accordance with Claim 1, the computer executable instructions further structured such that, when executed by the one or more processors of the computing system, cause the computing system to instantiate and/or operation the following:
an editing component configured to allow the user to edit a user interface component, causing the hierarchical storage agent to provide further state to the remote storage representing the editing.
9. A method for using a user interface comprising:
an act of reading state that was previously provided to a store, the state including a state of multiple parent user interfaces, the state including a navigation sequence through which a user had previously navigated the multiple parent user interfaces, each of the multiple parent user interfaces having a corresponding hierarchy of contained user interface elements, the state for each of the multiple parent user interfaces being structured in accordance with the corresponding hierarchy for that parent user interface; and
an act of using the read state to reformulate the multiple parent user interfaces on a user interface in the state in which the user had previously navigated.
10. The method in accordance with Claim 9, the reformulation of the multiple parent user interfaces occurs on a same display as was being used by the user when the state was formulated, to thus accomplish refresh.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14783733.0A EP3053027A1 (en) | 2013-09-30 | 2014-09-25 | Persisting state at scale across browser sessions |
CN201480053811.6A CN105683907B (en) | 2013-09-30 | 2014-09-25 | The state of browser-cross session is persistently stored in proportion |
Applications Claiming Priority (24)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361884743P | 2013-09-30 | 2013-09-30 | |
US61/884,743 | 2013-09-30 | ||
US201361905128P | 2013-11-15 | 2013-11-15 | |
US201361905114P | 2013-11-15 | 2013-11-15 | |
US201361905129P | 2013-11-15 | 2013-11-15 | |
US201361905105P | 2013-11-15 | 2013-11-15 | |
US201361905111P | 2013-11-15 | 2013-11-15 | |
US201361905116P | 2013-11-15 | 2013-11-15 | |
US201361905119P | 2013-11-15 | 2013-11-15 | |
US201361905101P | 2013-11-15 | 2013-11-15 | |
US61/905,119 | 2013-11-15 | ||
US61/905,114 | 2013-11-15 | ||
US61/905,129 | 2013-11-15 | ||
US61/905,128 | 2013-11-15 | ||
US61/905,111 | 2013-11-15 | ||
US61/905,105 | 2013-11-15 | ||
US61/905,101 | 2013-11-15 | ||
US61/905,116 | 2013-11-15 | ||
US201361905243P | 2013-11-17 | 2013-11-17 | |
US201361905247P | 2013-11-17 | 2013-11-17 | |
US61/905,243 | 2013-11-17 | ||
US61/905,247 | 2013-11-17 | ||
US14/231,891 | 2014-04-01 | ||
US14/231,891 US9483549B2 (en) | 2013-09-30 | 2014-04-01 | Persisting state at scale across browser sessions |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015048205A1 true WO2015048205A1 (en) | 2015-04-02 |
Family
ID=52741177
Family Applications (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2014/057322 WO2015048204A1 (en) | 2013-09-30 | 2014-09-25 | Query building using schema |
PCT/US2014/057324 WO2015048206A1 (en) | 2013-09-30 | 2014-09-25 | Rendering interpreter for visualizing data provided from restricted environment container |
PCT/US2014/057323 WO2015048205A1 (en) | 2013-09-30 | 2014-09-25 | Persisting state at scale across browser sessions |
PCT/US2014/057321 WO2015048203A1 (en) | 2013-09-30 | 2014-09-25 | Control and part compliant hierarchy |
PCT/US2014/057940 WO2015048602A1 (en) | 2013-09-30 | 2014-09-29 | Pan and selection gesture detection |
PCT/US2014/057938 WO2015048600A1 (en) | 2013-09-30 | 2014-09-29 | Extendable blade sequence along pannable canvas direction |
PCT/US2014/057939 WO2015048601A1 (en) | 2013-09-30 | 2014-09-29 | Context aware user interface parts |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2014/057322 WO2015048204A1 (en) | 2013-09-30 | 2014-09-25 | Query building using schema |
PCT/US2014/057324 WO2015048206A1 (en) | 2013-09-30 | 2014-09-25 | Rendering interpreter for visualizing data provided from restricted environment container |
Family Applications After (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2014/057321 WO2015048203A1 (en) | 2013-09-30 | 2014-09-25 | Control and part compliant hierarchy |
PCT/US2014/057940 WO2015048602A1 (en) | 2013-09-30 | 2014-09-29 | Pan and selection gesture detection |
PCT/US2014/057938 WO2015048600A1 (en) | 2013-09-30 | 2014-09-29 | Extendable blade sequence along pannable canvas direction |
PCT/US2014/057939 WO2015048601A1 (en) | 2013-09-30 | 2014-09-29 | Context aware user interface parts |
Country Status (17)
Country | Link |
---|---|
US (11) | US20150095849A1 (en) |
EP (6) | EP3053028B1 (en) |
JP (2) | JP6465870B2 (en) |
KR (3) | KR102186865B1 (en) |
CN (6) | CN105683907B (en) |
AU (2) | AU2014324620A1 (en) |
BR (1) | BR112016004551A8 (en) |
CA (2) | CA2922725A1 (en) |
CL (1) | CL2016000729A1 (en) |
HK (1) | HK1222731A1 (en) |
IL (1) | IL244368A0 (en) |
MX (2) | MX2016003946A (en) |
PH (1) | PH12016500256A1 (en) |
RU (2) | RU2679540C2 (en) |
SG (2) | SG10201802632SA (en) |
TW (4) | TW201528106A (en) |
WO (7) | WO2015048204A1 (en) |
Families Citing this family (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
USD750112S1 (en) * | 2013-01-04 | 2016-02-23 | Samsung Electronics Co., Ltd. | Portable electronic device with graphical user interface |
US20150095849A1 (en) * | 2013-09-30 | 2015-04-02 | Microsoft Corporation | Dialogs positioned with action visualization |
USD745877S1 (en) * | 2013-10-17 | 2015-12-22 | Microsoft Corporation | Display screen with graphical user interface |
US10176218B2 (en) * | 2014-11-07 | 2019-01-08 | Sap Se | OData custom query composer |
US10452750B2 (en) | 2015-08-04 | 2019-10-22 | Google Llc | Systems and methods for interactively presenting a visible portion of a rendering surface on a user device |
US10990258B2 (en) * | 2015-08-04 | 2021-04-27 | Google Llc | Interactively presenting a visible portion of a rendering surface on a user device |
JP6812639B2 (en) * | 2016-02-03 | 2021-01-13 | セイコーエプソン株式会社 | Electronic devices, control programs for electronic devices |
US10289297B2 (en) * | 2016-08-26 | 2019-05-14 | Google Llc | Animating an image to indicate that the image is pannable |
US9871911B1 (en) * | 2016-09-30 | 2018-01-16 | Microsoft Technology Licensing, Llc | Visualizations for interactions with external computing logic |
KR102605332B1 (en) * | 2016-11-02 | 2023-11-23 | 주식회사 넥슨코리아 | Device and method to provide content |
US10796088B2 (en) * | 2017-04-21 | 2020-10-06 | International Business Machines Corporation | Specifying a conversational computer agent and its outcome with a grammar |
WO2018208047A1 (en) | 2017-05-09 | 2018-11-15 | Samsung Electronics Co., Ltd. | Method and system for managing and displaying application |
US10827319B2 (en) * | 2017-06-02 | 2020-11-03 | Apple Inc. | Messaging system interacting with dynamic extension app |
CN110019717B (en) * | 2017-12-15 | 2021-06-29 | 上海智臻智能网络科技股份有限公司 | Device for modifying multi-turn question-answering system |
CN110019718B (en) * | 2017-12-15 | 2021-04-09 | 上海智臻智能网络科技股份有限公司 | Method for modifying multi-turn question-answering system, terminal equipment and storage medium |
US11341422B2 (en) | 2017-12-15 | 2022-05-24 | SHANGHAI XIAOl ROBOT TECHNOLOGY CO., LTD. | Multi-round questioning and answering methods, methods for generating a multi-round questioning and answering system, and methods for modifying the system |
US11379252B1 (en) * | 2018-01-31 | 2022-07-05 | Parallels International Gmbh | System and method for providing layouts for a remote desktop session |
US11659003B2 (en) | 2018-08-30 | 2023-05-23 | International Business Machines Corporation | Safe shell container facilitating inspection of a virtual container |
US10902045B2 (en) * | 2018-09-18 | 2021-01-26 | Tableau Software, Inc. | Natural language interface for building data visualizations, including cascading edits to filter expressions |
US11048871B2 (en) * | 2018-09-18 | 2021-06-29 | Tableau Software, Inc. | Analyzing natural language expressions in a data visualization user interface |
CN109542563B (en) * | 2018-11-09 | 2022-06-07 | 优信数享(北京)信息技术有限公司 | Multi-state integrated android page management method, device and system |
US11385766B2 (en) | 2019-01-07 | 2022-07-12 | AppEsteem Corporation | Technologies for indicating deceptive and trustworthy resources |
EP3764210A1 (en) | 2019-07-08 | 2021-01-13 | dSPACE digital signal processing and control engineering GmbH | Display of display areas on a desktop |
US11089050B1 (en) * | 2019-08-26 | 2021-08-10 | Ca, Inc. | Isolating an iframe of a webpage |
US11455339B1 (en) | 2019-09-06 | 2022-09-27 | Tableau Software, LLC | Incremental updates to natural language expressions in a data visualization user interface |
US11474975B2 (en) | 2019-09-18 | 2022-10-18 | Microsoft Technology Licensing, Llc | Identity represented assets in a content management system |
US11199955B2 (en) * | 2019-10-02 | 2021-12-14 | Palantir Technologies Inc. | Enhanced techniques for building user interfaces |
CN110825766A (en) * | 2019-11-13 | 2020-02-21 | 恩亿科(北京)数据科技有限公司 | Query condition generation method and device, server and readable storage medium |
CN110995942B (en) * | 2019-12-06 | 2021-08-06 | 科大国创软件股份有限公司 | Soft switch automatic calling method and system based on interface visualization |
CN111177455A (en) * | 2019-12-31 | 2020-05-19 | 精英数智科技股份有限公司 | Method, device and equipment for determining cutting tooth load type of coal mining machine and storage medium |
CN111610912B (en) * | 2020-04-24 | 2023-10-10 | 北京小米移动软件有限公司 | Application display method, application display device and storage medium |
WO2022049220A2 (en) | 2020-09-02 | 2022-03-10 | Genmab A/S | Antibody therapy |
US11698933B1 (en) | 2020-09-18 | 2023-07-11 | Tableau Software, LLC | Using dynamic entity search during entry of natural language commands for visual data analysis |
US11301631B1 (en) | 2020-10-05 | 2022-04-12 | Tableau Software, LLC | Visually correlating individual terms in natural language input to respective structured phrases representing the natural language input |
CN112732243A (en) * | 2021-01-11 | 2021-04-30 | 京东数字科技控股股份有限公司 | Data processing method and device for generating functional component |
US11363050B1 (en) | 2021-03-25 | 2022-06-14 | Bank Of America Corporation | Information security system and method for incompliance detection in data transmission |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030058286A1 (en) * | 2001-09-25 | 2003-03-27 | Owen Dando | Configurable user-interface component management system |
US7062475B1 (en) * | 2000-05-30 | 2006-06-13 | Alberti Anemometer Llc | Personalized multi-service computer environment |
US20080109714A1 (en) * | 2006-11-03 | 2008-05-08 | Sap Ag | Capturing screen information |
Family Cites Families (179)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS6362033A (en) * | 1986-09-02 | 1988-03-18 | Nec Corp | Display device for relative information |
WO1994024657A1 (en) * | 1993-04-20 | 1994-10-27 | Apple Computer Inc. | Interactive user interface |
US5625763A (en) * | 1995-05-05 | 1997-04-29 | Apple Computer, Inc. | Method and apparatus for automatically generating focus ordering in a dialog on a computer system |
JPH09245188A (en) * | 1996-03-12 | 1997-09-19 | Fujitsu Ltd | Graphic displaying method and its device |
US5845299A (en) | 1996-07-29 | 1998-12-01 | Rae Technology Llc | Draw-based editor for web pages |
US6049812A (en) | 1996-11-18 | 2000-04-11 | International Business Machines Corp. | Browser and plural active URL manager for network computers |
US6128632A (en) * | 1997-03-06 | 2000-10-03 | Apple Computer, Inc. | Methods for applying rubi annotation characters over base text characters |
US6091415A (en) * | 1997-05-02 | 2000-07-18 | Inventec Corporation | System and method for displaying multiple dialog boxes in a window display |
US5886694A (en) * | 1997-07-14 | 1999-03-23 | Microsoft Corporation | Method for automatically laying out controls in a dialog window |
US5995101A (en) * | 1997-10-29 | 1999-11-30 | Adobe Systems Incorporated | Multi-level tool tip |
US6236400B1 (en) * | 1998-04-02 | 2001-05-22 | Sun Microsystems, Inc. | Method and apparatus for controlling the display of hierarchical information |
US6473102B1 (en) | 1998-05-11 | 2002-10-29 | Apple Computer, Inc. | Method and system for automatically resizing and repositioning windows in response to changes in display |
US7801913B2 (en) | 1998-12-07 | 2010-09-21 | Oracle International Corporation | System and method for querying data for implicit hierarchies |
US6460060B1 (en) | 1999-01-26 | 2002-10-01 | International Business Machines Corporation | Method and system for searching web browser history |
JP2000331020A (en) * | 1999-05-21 | 2000-11-30 | Nippon Telegr & Teleph Corp <Ntt> | Method and device for information reference and storage medium with information reference program stored |
US6701513B1 (en) | 2000-01-14 | 2004-03-02 | Measurement Computing Corporation | Program-development environment for use in generating application programs |
US7243335B1 (en) * | 2000-02-17 | 2007-07-10 | Microsoft Corporation | Method and system for reducing coding complexity by providing intelligent manipulable defaults |
US6681383B1 (en) * | 2000-04-04 | 2004-01-20 | Sosy, Inc. | Automatic software production system |
US6473891B1 (en) | 2000-05-03 | 2002-10-29 | Lsi Logic Corporation | Wire routing to control skew |
US6750887B1 (en) | 2000-06-02 | 2004-06-15 | Sun Microsystems, Inc. | Graphical user interface layout manager |
US7171455B1 (en) | 2000-08-22 | 2007-01-30 | International Business Machines Corporation | Object oriented based, business class methodology for generating quasi-static web pages at periodic intervals |
US6919890B2 (en) | 2000-09-28 | 2005-07-19 | Curl Corporation | Grid and table layout using elastics |
US6640655B1 (en) * | 2000-10-03 | 2003-11-04 | Varco I/P, Inc. | Self tracking sensor suspension mechanism |
US6950198B1 (en) | 2000-10-18 | 2005-09-27 | Eastman Kodak Company | Effective transfer of images from a user to a service provider |
US7370040B1 (en) * | 2000-11-21 | 2008-05-06 | Microsoft Corporation | Searching with adaptively configurable user interface and extensible query language |
WO2002046878A2 (en) | 2000-12-06 | 2002-06-13 | American Express Travel Related Services Company, Inc. | Layout generator system and method |
US6760128B2 (en) | 2000-12-06 | 2004-07-06 | Eastman Kodak Company | Providing a payment schedule for utilizing stored images using a designated date |
JP2002182812A (en) * | 2000-12-14 | 2002-06-28 | Smg Kk | Site map display system |
US7233998B2 (en) | 2001-03-22 | 2007-06-19 | Sony Computer Entertainment Inc. | Computer architecture and software cells for broadband networks |
US7203678B1 (en) | 2001-03-27 | 2007-04-10 | Bea Systems, Inc. | Reconfigurable query generation system for web browsers |
US20020147963A1 (en) | 2001-04-09 | 2002-10-10 | Lee Rusty Shawn | Method and apparatus for generating machine control instructions |
US20020180811A1 (en) | 2001-05-31 | 2002-12-05 | Chu Sing Yun | Systems, methods, and articles of manufacture for providing a user interface with selection and scrolling |
US20030011638A1 (en) | 2001-07-10 | 2003-01-16 | Sun-Woo Chung | Pop-up menu system |
US6950993B2 (en) | 2001-08-02 | 2005-09-27 | Microsoft Corporation | System and method for automatic and dynamic layout of resizable dialog type windows |
US7480864B2 (en) * | 2001-10-12 | 2009-01-20 | Canon Kabushiki Kaisha | Zoom editor |
US7620908B2 (en) | 2001-12-28 | 2009-11-17 | Sap Ag | Managing a user interface |
US20050066037A1 (en) * | 2002-04-10 | 2005-03-24 | Yu Song | Browser session mobility system for multi-platform applications |
CA2385224C (en) | 2002-05-07 | 2012-10-02 | Corel Corporation | Dockable drop-down dialogs |
US7065707B2 (en) | 2002-06-24 | 2006-06-20 | Microsoft Corporation | Segmenting and indexing web pages using function-based object models |
US7293024B2 (en) | 2002-11-14 | 2007-11-06 | Seisint, Inc. | Method for sorting and distributing data among a plurality of nodes |
US20080177994A1 (en) | 2003-01-12 | 2008-07-24 | Yaron Mayer | System and method for improving the efficiency, comfort, and/or reliability in Operating Systems, such as for example Windows |
US7000184B2 (en) * | 2003-01-24 | 2006-02-14 | The Cobalt Group, Inc. | Remote web site editing in a standard web browser without external software |
US20040165009A1 (en) * | 2003-02-20 | 2004-08-26 | International Business Machines Corporation | Expansion of interactive user interface components |
US7823077B2 (en) | 2003-03-24 | 2010-10-26 | Microsoft Corporation | System and method for user modification of metadata in a shell browser |
US7769794B2 (en) | 2003-03-24 | 2010-08-03 | Microsoft Corporation | User interface for a file system shell |
US7720616B2 (en) | 2003-05-07 | 2010-05-18 | Sureprep, Llc | Multi-stage, multi-user engagement submission and tracking process |
US7417644B2 (en) | 2003-05-12 | 2008-08-26 | Microsoft Corporation | Dynamic pluggable user interface layout |
US7669140B2 (en) | 2003-08-21 | 2010-02-23 | Microsoft Corporation | System and method for providing rich minimized applications |
US8230366B2 (en) | 2003-10-23 | 2012-07-24 | Apple Inc. | Dynamically changing cursor for user interface |
US8037420B2 (en) | 2003-12-04 | 2011-10-11 | International Business Machines Corporation | Maintaining browser navigation relationships and for choosing a browser window for new documents |
US7711742B2 (en) | 2003-12-11 | 2010-05-04 | International Business Machines Corporation | Intelligent data query builder |
US20080109785A1 (en) | 2004-01-16 | 2008-05-08 | Bailey Bendrix L | Graphical Program Having Graphical and/or Textual Specification of Event Handler Procedures for Program Objects |
GB2411331A (en) * | 2004-02-19 | 2005-08-24 | Trigenix Ltd | Rendering user interface using actor attributes |
US7577938B2 (en) | 2004-02-20 | 2009-08-18 | Microsoft Corporation | Data association |
US7536672B1 (en) | 2004-03-05 | 2009-05-19 | Adobe Systems Incorporated | Management of user interaction history with software applications |
US7694233B1 (en) * | 2004-04-30 | 2010-04-06 | Apple Inc. | User interface presentation of information in reconfigured or overlapping containers |
CN100343802C (en) * | 2004-05-10 | 2007-10-17 | 华为技术有限公司 | Method and system for unifying users'interface |
US8453065B2 (en) | 2004-06-25 | 2013-05-28 | Apple Inc. | Preview and installation of user interface elements in a display environment |
US8046712B2 (en) | 2004-06-29 | 2011-10-25 | Acd Systems International Inc. | Management of multiple window panels with a graphical user interface |
US8117542B2 (en) * | 2004-08-16 | 2012-02-14 | Microsoft Corporation | User interface for displaying selectable software functionality controls that are contextually relevant to a selected object |
EP1779216A1 (en) | 2004-08-20 | 2007-05-02 | Rhoderick John Kennedy Pugh | Server authentication |
US7434173B2 (en) | 2004-08-30 | 2008-10-07 | Microsoft Corporation | Scrolling web pages using direct interaction |
US7720867B2 (en) | 2004-09-08 | 2010-05-18 | Oracle International Corporation | Natural language query construction using purpose-driven template |
US8819569B2 (en) | 2005-02-18 | 2014-08-26 | Zumobi, Inc | Single-handed approach for navigation of application tiles using panning and zooming |
US7728825B2 (en) * | 2005-03-22 | 2010-06-01 | Microsoft Corporation | Targeting in a stylus-based user interface |
US20060224951A1 (en) * | 2005-03-30 | 2006-10-05 | Yahoo! Inc. | Multiple window browser interface and system and method of generating multiple window browser interface |
US20060236264A1 (en) * | 2005-04-18 | 2006-10-19 | Microsoft Corporation | Automatic window resize behavior and optimizations |
US8195646B2 (en) | 2005-04-22 | 2012-06-05 | Microsoft Corporation | Systems, methods, and user interfaces for storing, searching, navigating, and retrieving electronic information |
US7721225B2 (en) | 2005-05-03 | 2010-05-18 | Novell, Inc. | System and method for creating and presenting modal dialog boxes in server-side component web applications |
US7730418B2 (en) | 2005-05-04 | 2010-06-01 | Workman Nydegger | Size to content windows for computer graphics |
US20070024646A1 (en) * | 2005-05-23 | 2007-02-01 | Kalle Saarinen | Portable electronic apparatus and associated method |
US20060282771A1 (en) | 2005-06-10 | 2006-12-14 | Tad Vinci | Verifying document compliance to a subsidiary standard |
US20070033522A1 (en) | 2005-08-02 | 2007-02-08 | Lin Frank L | System and method for dynamic resizing of web-based GUIs |
US7933632B2 (en) | 2005-09-16 | 2011-04-26 | Microsoft Corporation | Tile space user interface for mobile devices |
US8543824B2 (en) | 2005-10-27 | 2013-09-24 | Apple Inc. | Safe distribution and use of content |
US7954064B2 (en) | 2005-10-27 | 2011-05-31 | Apple Inc. | Multiple dashboards |
US8434021B2 (en) * | 2005-11-30 | 2013-04-30 | Microsoft Corporation | Centralized user interface for displaying contextually driven business content and business related functionality |
US7836303B2 (en) | 2005-12-09 | 2010-11-16 | University Of Washington | Web browser operating system |
US8898203B2 (en) | 2005-12-27 | 2014-11-25 | International Business Machines Corporation | Generating a separable query design object and database schema through visual view editing |
JP4635894B2 (en) | 2006-02-13 | 2011-02-23 | ソニー株式会社 | Information processing apparatus and method, and program |
JP4415961B2 (en) | 2006-03-15 | 2010-02-17 | ブラザー工業株式会社 | Removable media device and data control program |
US20070233854A1 (en) | 2006-03-31 | 2007-10-04 | Microsoft Corporation | Management status summaries |
US20070234195A1 (en) | 2006-04-03 | 2007-10-04 | National Instruments Corporation | Simultaneous update of a plurality of user interface elements displayed in a web browser |
US7685519B1 (en) * | 2006-07-18 | 2010-03-23 | Intuit Inc. | Process and apparatus for providing a customizable content tooltip |
US20080018665A1 (en) * | 2006-07-24 | 2008-01-24 | Jay Behr | System and method for visualizing drawing style layer combinations |
US8869027B2 (en) | 2006-08-04 | 2014-10-21 | Apple Inc. | Management and generation of dashboards |
US20080065974A1 (en) * | 2006-09-08 | 2008-03-13 | Tom Campbell | Template-based electronic presence management |
US7890957B2 (en) | 2006-09-08 | 2011-02-15 | Easyonme, Inc. | Remote management of an electronic presence |
US8082539B1 (en) | 2006-12-11 | 2011-12-20 | Parallels Holdings, Ltd. | System and method for managing web-based forms and dynamic content of website |
JP5031353B2 (en) | 2006-12-15 | 2012-09-19 | キヤノン株式会社 | Display device, control method, and program |
CN101004685A (en) * | 2007-01-08 | 2007-07-25 | 叶炜 | Method for realizing graphical user interface |
US9032329B2 (en) | 2007-03-23 | 2015-05-12 | Siemens Product Lifecycle Management Software Inc. | System and method for dialog position management |
US8321847B1 (en) | 2007-05-17 | 2012-11-27 | The Mathworks, Inc. | Dynamic function wizard |
US20080306933A1 (en) * | 2007-06-08 | 2008-12-11 | Microsoft Corporation | Display of search-engine results and list |
US10019570B2 (en) | 2007-06-14 | 2018-07-10 | Microsoft Technology Licensing, Llc | Protection and communication abstractions for web browsers |
US8065628B2 (en) | 2007-06-25 | 2011-11-22 | Microsoft Corporation | Dynamic user interface for previewing live content |
KR20090000507A (en) * | 2007-06-28 | 2009-01-07 | 삼성전자주식회사 | Method and apparatus of displaying information |
US8762880B2 (en) * | 2007-06-29 | 2014-06-24 | Microsoft Corporation | Exposing non-authoring features through document status information in an out-space user interface |
US7873746B2 (en) | 2007-07-27 | 2011-01-18 | Lagavulin Limited | User interface for a portable, image-processing transmitter |
US9009181B2 (en) * | 2007-08-23 | 2015-04-14 | International Business Machines Corporation | Accessing objects in a service registry and repository |
US8126840B2 (en) | 2007-10-22 | 2012-02-28 | Noria Corporation | Lubrication program management system and methods |
US8046353B2 (en) | 2007-11-02 | 2011-10-25 | Citrix Online Llc | Method and apparatus for searching a hierarchical database and an unstructured database with a single search query |
CN101499004A (en) * | 2008-01-31 | 2009-08-05 | 株式会社日立制作所 | System and method for connecting virtual machine and user interface |
JP2009193423A (en) * | 2008-02-15 | 2009-08-27 | Panasonic Corp | Input device for electronic equipment |
US20090254822A1 (en) | 2008-04-04 | 2009-10-08 | International Business Machines Corporation | Hi-efficiency wizard framework system and method |
US8219385B2 (en) | 2008-04-08 | 2012-07-10 | Incentive Targeting, Inc. | Computer-implemented method and system for conducting a search of electronically stored information |
JP4171770B1 (en) * | 2008-04-24 | 2008-10-29 | 任天堂株式会社 | Object display order changing program and apparatus |
US8375336B2 (en) * | 2008-05-23 | 2013-02-12 | Microsoft Corporation | Panning content utilizing a drag operation |
US8156445B2 (en) * | 2008-06-20 | 2012-04-10 | Microsoft Corporation | Controlled interaction with heterogeneous data |
US20100005053A1 (en) | 2008-07-04 | 2010-01-07 | Estes Philip F | Method for enabling discrete back/forward actions within a dynamic web application |
US8345014B2 (en) * | 2008-07-12 | 2013-01-01 | Lester F. Ludwig | Control of the operating system on a computing device via finger angle using a high dimensional touchpad (HDTP) touch user interface |
US8566741B2 (en) | 2008-08-29 | 2013-10-22 | Microsoft Corporation | Internal scroll activation and cursor adornment |
US8402381B2 (en) * | 2008-09-23 | 2013-03-19 | International Business Machines Corporation | Automatically arranging widgets of a model within a canvas using iterative region based widget relative adjustments |
US8095412B1 (en) | 2008-11-03 | 2012-01-10 | Intuit Inc. | Method and system for evaluating expansion of a business |
KR20100049474A (en) | 2008-11-03 | 2010-05-12 | 삼성전자주식회사 | A method for remote user interface session migration to other device |
US20120188286A1 (en) * | 2008-11-26 | 2012-07-26 | Lila Aps (Ahead.) | Dynamic image tiling |
US7962547B2 (en) | 2009-01-08 | 2011-06-14 | International Business Machines Corporation | Method for server-side logging of client browser state through markup language |
US20100229115A1 (en) | 2009-03-05 | 2010-09-09 | Microsoft Corporation | Zoomable user interface data generation |
US8806371B2 (en) * | 2009-03-26 | 2014-08-12 | Apple Inc. | Interface navigation tools |
US8819570B2 (en) * | 2009-03-27 | 2014-08-26 | Zumobi, Inc | Systems, methods, and computer program products displaying interactive elements on a canvas |
US20100251143A1 (en) | 2009-03-27 | 2010-09-30 | The Ransom Group, Inc. | Method, system and computer program for creating and editing a website |
US8819597B2 (en) | 2009-04-10 | 2014-08-26 | Google Inc. | Glyph entry on computing device |
US9213541B2 (en) | 2009-04-17 | 2015-12-15 | ArtinSoft Corporation, S.A. | Creation, generation, distribution and application of self-contained modifications to source code |
US20100287530A1 (en) | 2009-05-05 | 2010-11-11 | Borland Software Corporation | Requirements definition using interactive prototyping |
US8269737B2 (en) * | 2009-08-20 | 2012-09-18 | Hewlett-Packard Development Company, L.P. | Method and apparatus for interpreting input movement on a computing device interface as a one- or two-dimensional input |
IN2012DN02458A (en) | 2009-11-13 | 2015-08-21 | Irdeto Canada Corp | |
US8782562B2 (en) * | 2009-12-02 | 2014-07-15 | Dell Products L.P. | Identifying content via items of a navigation system |
US8407598B2 (en) | 2009-12-09 | 2013-03-26 | Ralph Lee Burton | Dynamic web control generation facilitator |
JP5523090B2 (en) * | 2009-12-25 | 2014-06-18 | キヤノン株式会社 | INPUT DEVICE, CONTROL METHOD FOR INPUT DEVICE, PROGRAM, AND STORAGE MEDIUM |
US8533667B2 (en) | 2009-12-30 | 2013-09-10 | International Business Machines Corporation | Call wizard for information management system (IMS) applications |
CN101763218A (en) * | 2010-01-06 | 2010-06-30 | 广东欧珀移动通信有限公司 | Input method for handheld equipment |
WO2011085387A2 (en) * | 2010-01-11 | 2011-07-14 | Everspeech, Inc. | Integrated data processing and transcription service |
EP2548200A4 (en) | 2010-03-19 | 2014-01-22 | Siemens Healthcare Diagnostics | System and method for changeable focus modal windows |
US8316323B2 (en) | 2010-03-26 | 2012-11-20 | Microsoft Corporation | Breadcrumb navigation through heirarchical structures |
US8631350B2 (en) * | 2010-04-23 | 2014-01-14 | Blackberry Limited | Graphical context short menu |
US20120089914A1 (en) * | 2010-04-27 | 2012-04-12 | Surfwax Inc. | User interfaces for navigating structured content |
US20110271184A1 (en) * | 2010-04-28 | 2011-11-03 | Microsoft Corporation | Client application and web page integration |
US9160756B2 (en) | 2010-05-19 | 2015-10-13 | International Business Machines Corporation | Method and apparatus for protecting markup language document against cross-site scripting attack |
JP5674779B2 (en) * | 2010-06-03 | 2015-02-25 | パナソニック インテレクチュアル プロパティ コーポレーション オブアメリカPanasonic Intellectual Property Corporation of America | Scroll device, scroll method, scroll program, and integrated circuit |
CN102270125A (en) * | 2010-06-04 | 2011-12-07 | 中兴通讯股份有限公司 | Device and method for developing Web application |
US20110314415A1 (en) * | 2010-06-21 | 2011-12-22 | George Fitzmaurice | Method and System for Providing Custom Tooltip Messages |
US8706854B2 (en) | 2010-06-30 | 2014-04-22 | Raytheon Company | System and method for organizing, managing and running enterprise-wide scans |
US8544027B2 (en) | 2010-07-30 | 2013-09-24 | Sap Ag | Logical data model abstraction in a physically distributed environment |
US8630462B2 (en) * | 2010-08-31 | 2014-01-14 | Activate Systems, Inc. | Methods and apparatus for improved motion capture |
JP2012069065A (en) * | 2010-09-27 | 2012-04-05 | Nintendo Co Ltd | Information processing program, and information processing device and method |
US8612366B2 (en) | 2010-09-29 | 2013-12-17 | Moresteam.Com Llc | Systems and methods for performing design of experiments |
US8990199B1 (en) | 2010-09-30 | 2015-03-24 | Amazon Technologies, Inc. | Content search with category-aware visual similarity |
US20120124555A1 (en) * | 2010-11-11 | 2012-05-17 | Codekko Software, Inc. | Optimization of Compiled Control Objects |
US9069577B2 (en) * | 2010-11-23 | 2015-06-30 | Apple Inc. | Grouping and browsing open windows |
CN102023749A (en) * | 2010-12-02 | 2011-04-20 | 广东宝莱特医用科技股份有限公司 | Area dragging treating method of list type control on touch screen interface of medical equipment |
US8612874B2 (en) * | 2010-12-23 | 2013-12-17 | Microsoft Corporation | Presenting an application change through a tile |
US20120191508A1 (en) | 2011-01-20 | 2012-07-26 | John Nicholas Gross | System & Method For Predicting Outcome Of An Intellectual Property Rights Proceeding/Challenge |
JP2012168790A (en) | 2011-02-15 | 2012-09-06 | Brother Ind Ltd | Display program and display device |
US9384183B2 (en) * | 2011-03-31 | 2016-07-05 | Infosys Limited | Method and system for reporting web standard non-compliance of web pages |
US9152616B2 (en) | 2011-04-28 | 2015-10-06 | Flipboard, Inc. | Template-based page layout for web content |
US9753699B2 (en) | 2011-06-16 | 2017-09-05 | Microsoft Technology Licensing, Llc | Live browser tooling in an integrated development environment |
US8566100B2 (en) | 2011-06-21 | 2013-10-22 | Verna Ip Holdings, Llc | Automated method and system for obtaining user-selected real-time information on a mobile communication device |
US8799862B2 (en) * | 2011-06-24 | 2014-08-05 | Alcatel Lucent | Application testing using sandboxes |
CN102253841B (en) * | 2011-08-09 | 2014-07-23 | 东莞兆田数码科技有限公司 | Small-scale graphical user interface system |
US20130080913A1 (en) * | 2011-09-22 | 2013-03-28 | Microsoft Corporation | Multi-column notebook interaction |
US8836654B2 (en) | 2011-10-04 | 2014-09-16 | Qualcomm Incorporated | Application window position and size control in (multi-fold) multi-display devices |
JP5553812B2 (en) * | 2011-10-26 | 2014-07-16 | 株式会社ソニー・コンピュータエンタテインメント | Scroll control device, terminal device, and scroll control method |
KR101888457B1 (en) | 2011-11-16 | 2018-08-16 | 삼성전자주식회사 | Apparatus having a touch screen processing plurality of apllications and method for controlling thereof |
US8799780B2 (en) | 2011-11-28 | 2014-08-05 | International Business Machines Corporation | Installation wizard with multidimensional views |
US8799988B2 (en) | 2012-01-25 | 2014-08-05 | Microsoft Corporation | Document communication runtime interfaces |
US20150058709A1 (en) * | 2012-01-26 | 2015-02-26 | Michael Edward Zaletel | Method of creating a media composition and apparatus therefore |
DE102013202782A1 (en) | 2012-02-20 | 2013-08-22 | Wixpress Ltd | Server-based web page design system that integrates dynamic layout and dynamic content |
KR101892567B1 (en) * | 2012-02-24 | 2018-08-28 | 삼성전자 주식회사 | Method and apparatus for moving contents on screen in terminal |
US9389872B2 (en) | 2012-03-16 | 2016-07-12 | Vmware, Inc. | Software wizard implementation framework |
EP2665042A1 (en) | 2012-05-14 | 2013-11-20 | Crytek GmbH | Visual processing based on interactive rendering |
US9043722B1 (en) * | 2012-06-19 | 2015-05-26 | Surfwax, Inc. | User interfaces for displaying relationships between cells in a grid |
US20140096042A1 (en) * | 2012-07-09 | 2014-04-03 | Aaron Tyler Travis | Method and system for generating and storing a collection of interactive browsers within a navigation plane |
US9195477B1 (en) | 2012-10-09 | 2015-11-24 | Sencha, Inc. | Device profiles, deep linking, and browser history support for web applications |
US9244971B1 (en) | 2013-03-07 | 2016-01-26 | Amazon Technologies, Inc. | Data retrieval from heterogeneous storage systems |
US9158518B2 (en) | 2013-03-11 | 2015-10-13 | Blackberry Limited | Collaborative application development environment using a connected device |
WO2014157908A1 (en) | 2013-03-27 | 2014-10-02 | Samsung Electronics Co., Ltd. | Device and method for displaying execution result of application |
US10410003B2 (en) | 2013-06-07 | 2019-09-10 | Apple Inc. | Multiple containers assigned to an application |
US20150095849A1 (en) * | 2013-09-30 | 2015-04-02 | Microsoft Corporation | Dialogs positioned with action visualization |
US9875116B2 (en) | 2013-11-26 | 2018-01-23 | Cellco Partnership | Sharing of a user input interface of an application session of one application between two or more applications |
-
2014
- 2014-04-01 US US14/231,912 patent/US20150095849A1/en not_active Abandoned
- 2014-04-01 US US14/231,891 patent/US9483549B2/en active Active
- 2014-04-01 US US14/231,917 patent/US20150095846A1/en not_active Abandoned
- 2014-04-01 US US14/231,897 patent/US9805114B2/en active Active
- 2014-04-01 US US14/231,869 patent/US9754018B2/en active Active
- 2014-04-01 US US14/231,862 patent/US9792354B2/en active Active
- 2014-04-01 US US14/231,880 patent/US20150095365A1/en not_active Abandoned
- 2014-04-01 US US14/231,873 patent/US20150095812A1/en not_active Abandoned
- 2014-04-01 US US14/231,905 patent/US9727636B2/en active Active
- 2014-04-01 US US14/231,883 patent/US9672276B2/en active Active
- 2014-04-01 US US14/231,846 patent/US20150095842A1/en not_active Abandoned
- 2014-08-28 TW TW103129730A patent/TW201528106A/en unknown
- 2014-09-24 TW TW103133046A patent/TW201528108A/en unknown
- 2014-09-24 TW TW103133045A patent/TW201516834A/en unknown
- 2014-09-25 EP EP14783734.8A patent/EP3053028B1/en active Active
- 2014-09-25 WO PCT/US2014/057322 patent/WO2015048204A1/en active Application Filing
- 2014-09-25 EP EP14825480.8A patent/EP3053031A1/en not_active Ceased
- 2014-09-25 KR KR1020167008327A patent/KR102186865B1/en active IP Right Grant
- 2014-09-25 CN CN201480053811.6A patent/CN105683907B/en active Active
- 2014-09-25 CN CN201480054151.3A patent/CN105683909B/en active Active
- 2014-09-25 WO PCT/US2014/057324 patent/WO2015048206A1/en active Application Filing
- 2014-09-25 TW TW103133249A patent/TW201528103A/en unknown
- 2014-09-25 WO PCT/US2014/057323 patent/WO2015048205A1/en active Application Filing
- 2014-09-25 EP EP14783733.0A patent/EP3053027A1/en not_active Ceased
- 2014-09-25 CN CN201480054050.6A patent/CN105593813B/en active Active
- 2014-09-25 WO PCT/US2014/057321 patent/WO2015048203A1/en active Application Filing
- 2014-09-29 EP EP14786398.9A patent/EP3053030A1/en not_active Withdrawn
- 2014-09-29 CN CN201480054049.3A patent/CN105593812A/en active Pending
- 2014-09-29 AU AU2014324620A patent/AU2014324620A1/en not_active Abandoned
- 2014-09-29 WO PCT/US2014/057940 patent/WO2015048602A1/en active Application Filing
- 2014-09-29 MX MX2016003946A patent/MX2016003946A/en unknown
- 2014-09-29 KR KR1020167008352A patent/KR20160063340A/en not_active Application Discontinuation
- 2014-09-29 EP EP14783748.8A patent/EP3053029A1/en not_active Ceased
- 2014-09-29 WO PCT/US2014/057938 patent/WO2015048600A1/en active Application Filing
- 2014-09-29 WO PCT/US2014/057939 patent/WO2015048601A1/en active Application Filing
- 2014-09-29 SG SG10201802632SA patent/SG10201802632SA/en unknown
- 2014-09-29 RU RU2016111604A patent/RU2679540C2/en not_active IP Right Cessation
- 2014-09-29 SG SG11201601888UA patent/SG11201601888UA/en unknown
- 2014-09-29 JP JP2016518686A patent/JP6465870B2/en not_active Expired - Fee Related
- 2014-09-29 RU RU2016111610A patent/RU2686822C2/en not_active IP Right Cessation
- 2014-09-29 MX MX2016004113A patent/MX2016004113A/en unknown
- 2014-09-29 JP JP2016518687A patent/JP6446038B2/en not_active Expired - Fee Related
- 2014-09-29 CA CA2922725A patent/CA2922725A1/en not_active Abandoned
- 2014-09-29 CA CA2922985A patent/CA2922985A1/en not_active Abandoned
- 2014-09-29 AU AU2014324618A patent/AU2014324618A1/en not_active Abandoned
- 2014-09-29 EP EP14790838.8A patent/EP3053017A1/en not_active Withdrawn
- 2014-09-29 CN CN201480053988.6A patent/CN105683908B/en not_active Expired - Fee Related
- 2014-09-29 CN CN201480053821.XA patent/CN105659199A/en active Pending
- 2014-09-29 KR KR1020167008368A patent/KR20160064115A/en not_active Application Discontinuation
- 2014-09-29 BR BR112016004551A patent/BR112016004551A8/en not_active Application Discontinuation
-
2016
- 2016-02-05 PH PH12016500256A patent/PH12016500256A1/en unknown
- 2016-03-01 IL IL244368A patent/IL244368A0/en unknown
- 2016-03-30 CL CL2016000729A patent/CL2016000729A1/en unknown
- 2016-09-14 HK HK16110904.6A patent/HK1222731A1/en unknown
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7062475B1 (en) * | 2000-05-30 | 2006-06-13 | Alberti Anemometer Llc | Personalized multi-service computer environment |
US20030058286A1 (en) * | 2001-09-25 | 2003-03-27 | Owen Dando | Configurable user-interface component management system |
US20080109714A1 (en) * | 2006-11-03 | 2008-05-08 | Sap Ag | Capturing screen information |
Non-Patent Citations (1)
Title |
---|
See also references of EP3053027A1 * |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9483549B2 (en) | Persisting state at scale across browser sessions | |
US8555249B2 (en) | Lifecycle stable user interface adaptations | |
US8775923B1 (en) | Web page restoration | |
RU2598991C2 (en) | Data recovery client for moveable client data | |
US9043750B2 (en) | Automated generation of two-tier mobile applications | |
US20110154226A1 (en) | Chip model of an extensible plug-in architecture for enterprise mashups | |
US9842091B2 (en) | Switching to and from native web applications | |
EP1266289A1 (en) | Method and apparatus for storing changes to file attributes without having to store an additional copy of the file contents | |
US20180307736A1 (en) | Efficient Snapshot Generation of Data Tables | |
US9038019B2 (en) | Paige control for enterprise mobile applications | |
CN113986424A (en) | Page display method and device | |
US9785320B2 (en) | Service gallery user interface presentation | |
US10678561B2 (en) | Virtualizing extension code in an application | |
US20180225333A1 (en) | Data write/import performance in a database through distributed memory | |
CN104133678A (en) | Method and device for building and operating SIDIS | |
CN112235132A (en) | Method, device, medium and server for dynamically configuring service | |
US9575734B2 (en) | System and method for improved light-weight business process modeling in offline mode using browser resources | |
CN113961298A (en) | Page switching method, device, equipment and medium | |
US11301498B2 (en) | Multi-cloud object store access | |
US10671412B1 (en) | Fast cloning for background processes in scripting environments | |
CN113360154A (en) | Page construction method, device, equipment and readable medium | |
CN109002343B (en) | Method and device for realizing batch creation of virtual machines | |
US20140059538A1 (en) | Virtual machine state tracking using object based storage | |
WO2024039477A1 (en) | Bridging ui elements across multiple operating systems | |
US20170344956A1 (en) | User calendar control for web page |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14783733 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2014783733 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014783733 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |