NL2012236C2 - Graphical user interface for mobile touchscreen-based navigation. - Google Patents

Graphical user interface for mobile touchscreen-based navigation. Download PDF

Info

Publication number
NL2012236C2
NL2012236C2 NL2012236A NL2012236A NL2012236C2 NL 2012236 C2 NL2012236 C2 NL 2012236C2 NL 2012236 A NL2012236 A NL 2012236A NL 2012236 A NL2012236 A NL 2012236A NL 2012236 C2 NL2012236 C2 NL 2012236C2
Authority
NL
Netherlands
Prior art keywords
gui
data
activation area
user
gui element
Prior art date
Application number
NL2012236A
Other languages
Dutch (nl)
Inventor
Robert Overweg
Daan Zonneveld
Jordi Bruin
Original Assignee
Triple It B V
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Triple It B V filed Critical Triple It B V
Priority to NL2012236A priority Critical patent/NL2012236C2/en
Application granted granted Critical
Publication of NL2012236C2 publication Critical patent/NL2012236C2/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/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/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/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/0486—Drag-and-drop

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)

Description

Graphical user interface for mobile touchscreen-based navigation
Field of the invention
The invention relates to a graphical user interface for mobile navigation and, in particular, though not exclusively, to a method and user device for rendering GUIs on a mobile user device and a computer program product for using such method.
Background of the invention
Nowadays mobile handhelds like a smart phone provide a very effective way of accessing and/or submitting information associated with an online service, e.g. a user account of mobile telecommunication or an online shopping service. Access to the information and navigation through the information however is still based for a large part on the basis of conventional navigation techniques such as scrolling, buttons and/or pull-down menus that are used when browsing for information on the web using a large-screen desktop.
Improved user experience may be provided by using application that can be downloaded from a website and installed on mobile device wherein the app renders a touchscreen based GUI that is especially adapted for mobile devices. When the amount of accessible information however becomes large, it becomes more difficult for the user to properly navigate through the information in a simple and intuitive way.
Further, the rendered GUIs are usually part of the software that is unpacked during installation of the application that runs on the user device. The application may have functionality that allows a user to personalize certain items of the GUI. Such scheme however only allows for limited personalization and does not a flexible scheme wherein a GUI can be dynamically modified in a simple way. For example, in certain situations it would be desirable to render a modified GUI, e.g. GUI adding one or more buttons and/or activation areas, on the basis of certain information of contextual information, e.g. information in the user account and/or information
Hence, from the above, it follows that there is a need in the art for improved methods and systems for rendering GUIs on a mobile user device. In particular there is a need for methods and systems that allow simple generation of GUIs that can be modified and/or personalized on the basis of .
Summary of the invention
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module" or "system." Functions described in this disclosure may be implemented as an algorithm executed by a microprocessor of a computer. Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied, e.g., stored, thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non- exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electromagnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber, cable, RF, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java(TM), Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor, in particular a microprocessor or central processing unit (CPU), of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer, other programmable data processing apparatus, or other devices create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It is an objective of the invention to reduce or eliminate at least one of the drawbacks known in the prior art. In an aspect the invention may relate to a method for rendering GUIs on a mobile user device, wherein said user device may comprise a GUI client for communicating with a GUI server which is configured for delivering GUI data to said GUI client.
In an embodiment, said method may comprise at least one processor, preferably at least one microprocessor, in said user device executing computer readable program code for: rendering a first GUI on the basis of first GUI data, said first GUI comprising a first activation area and at least a first GUI element pointing to a second GUI; rendering said second GUI on the basis of second GUI data if a user selects said first GUI element by touching said first GUI element and sliding said first GUI element over said first activation area while keeping contact with said first GUI element, said second GUI comprising at least a second activation area and at least a second GUI element pointing to a third GUI, wherein said first GUI element is displayed in said second activation area; and, rendering said first GUI on the basis of said first GUI data if a user selects said first GUI element in said second activation area by touching said first GUI element and sliding said first GUI element outside said second activation area; or, rendering said third GUI on the basis of third GUI data by touching said second GUI element and sliding said second GUI element over said second activation area and said first GUI element, while keeping contact with said second GUI element.
Hence, the method allows a simple and intuitive way of rendering GUIs and navigating through a set of GUIs by sliding GUI elements in or out said activation area. Positioning an GUI element in the activation area may trigger the GUI client to request GUI data from a GUI server, wherein the GUI data enables the GUI client to render an activation area and one or more GUI elements.
In an embodiment said GUI data may comprise a GUI identifier, GUI parameters for defining at least an activation area and/or for defining one or more selectable GUI elements; and, optionally, at least one GUI pointer for linking a GUI element to a further GUI. Hence, wherein retrieving GUI data GUI elements may be rendered that point to a further GUIs, so that when a user selects a GUI element, the GUI client is able to request the GUI data for the selected GUI element.
In an embodiment said method may further comprise: sending a first request message, preferably an HTTP request message, for requesting said GUI server the delivery of said first GUI data, said request message comprising a first GUI identifier for identifying said first GUI; receiving a first response message comprising said first GUI data. Hence, the communication between the GUI server and the GUI client may be based on the HTTP protocol that is transparent for firewalls.
In an embodiment said method may comprise if said user selects said first GUI element, sending a request message, preferably a HTTP request message, to said GUI server for requesting the delivery of said second GUI data to said GUI client, preferably said request message comprising a GUI identifier for identifying said second GUI; and, receiving a response message, preferably an HTTP response message, comprising said second GUI data.
In an embodiment said request message may be sent to said GUI server when the user releases the contact of said GUI element while said first GUI element is positioned over said first activation area. Hence, when contact is released the GUI client is triggered to request the GUI data associated with the selected GUI.
In an embodiment, said GUI client may be configured to track the GUI rendering by said user on the basis of a GUI stack of GUI identifiers, wherein the GUI identifier of the top of the GUI stack represents the currently active GUI.
Hence, when the user selects further GUIs by sliding GUI elements into the activation area, GUI identifiers are added to the stack so that the client is able to track the navigation history of the user.
In an embodiment said method may comprise: adding the GUI identifier of the second GUI to a GUI stack if the user selects said first GUI element by touching said first GUI element and sliding slides said first GUI element over said first activation area; and, removing the GUI identifier of the second GUI from the GUI stack if the user selects said first GUI element in said second activation area by touching said first GUI element and sliding said first GUI element outside said second activation area.
In an embodiment said GUI parameters may determine the shape, color, coordinates and/or content of said at least one activation element and/or said one or more GUI elements.
In an embodiment said GUI server may comprise a GUI ΔΙΡ that is configured to collect GUI data requested by said GUI client from a GUI database, content provider and/or service provider.
In an embodiment said GUI AIP may be configured for modifying at least part of said collected GUI data before sending the collected GUI data to said GUI client. In another embodiment, said GUI AIP may modify at least part of said collected GUI data on the basis of user information and/or one or more conditions associated with said user information. In yet another embodiment, GUI AIP may modify at least part of said collected GUI data such that the shape, color, coordinates and/or content of said activation area and/or GUI elements is modified if one or more conditions associated with said user information are met. Hence, the GUI API in the GUI server may be configured to modify the GUI data on the basis of certain conditions (e.g. subscription is almost expired or calling credit is decreased below a certain value) so that the GUI may be personalized in a dynamic way without re-installing the application.
In an embodiment said GUIs may be hierarchically structured on the basis of a decision tree comprising a root and a plurality of branch nodes, said root and said branch nodes being associated with one of said GUIs and wherein sliding GUI elements in or out of said activation area enables the user to navigate through GUIs located on a path in said decision tree.
In a further aspect, the invention may relate to a mobile user device comprising a GUI client for rendering GUIs, wherein said GUI client is configured for communicating with a GUI server which is configured for delivering GUI data to said GUI client; wherein said user device may comprise a microprocessor coupled to a touch-sensitive display, a communication module, and a computer-readable first memory having computer readable program code embodied therewith, wherein responsive to executing the computer readable program code, the microprocessor is configured to perform executable operations for: rendering a first GUI on the basis of first GUI data, said first GUI comprising a first activation area and at least a first GUI element pointing to a second GUI; rendering said second GUI on the basis of second GUI data if a user selects said first GUI element by touching said first GUI element and sliding said first GUI element over said first activation area while keeping contact with said first GUI element, said second GUI comprising at least a second activation area and at least a second GUI element pointing to a third GUI, wherein said first GUI element is displayed in said second activation area; rendering said first GUI on the basis of said first GUI data if a user selects said first GUI element in said second activation area by touching said first GUI element and sliding said first GUI element outside said second activation area; and, rendering said third GUI on the basis of third GUI data by touching said second GUI element and sliding said second GUI element over said second activation area and said first GUI element, while keeping contact with said second GUI element.
In an embodiment said microprocessor in said user device may further configured to perform executable operations for: if said user selects said first GUI element, sending a request message, preferably a HTTP request message, to said GUI server for requesting the delivery of said second GUI data to said GUI client, preferably said request message comprising a GUI identifier for identifying said second GUI; and, receiving a response message, preferably an HTTP response message, comprising said second GUI data.
In an embodiment said request message may be sent to said GUI server when the user releases the contact of said GUI element while said first GUI element is positioned over said first activation area.
In an embodiment said GUI client may be further configured to track the GUI rendering by said user on the basis of a GUI stack of GUI identifiers, wherein the GUI identifier of the top of the GUI stack represents the currently active GUI.
In a further embodiment, the microprocessor in said user device may be further configured to perform executable operations for: adding the GUI identifier of the second GUI to a GUI stack if the user selects said first GUI element by touching said first GUI element and sliding slides said first GUI element over said first activation area; and, removing the GUI identifier of the second GUI from the GUI stack if the user selects said first GUI element in said second activation area by touching said first GUI element and sliding said first GUI element outside said second activation area.
The invention may further relate to a computer program product comprising software code portions configured for, when run in the memory of a computer, executing the method steps as described above.
The invention will be further illustrated with reference to the attached drawings, which schematically will show embodiments according to the invention. It will be understood that the invention is not in any way restricted to these specific embodiments.
Brief description of the drawings
Fig. 1A and IB schematically depict a process for rendering GUIs on a mobile user device according to an embodiment of the invention.
Fig. 2A-2C schematically depict a system for rendering GUIs on a mobile user device according to an embodiment of the invention.
Fig. 3 depicts a user device comprising a GUI client according an embodiment of the invention.
Fig. 4 schematically depicts a flow diagram of a process for rendering GUIs on a mobile user device according an embodiment of the invention.
Fig. 5A-5C schematically user-interaction on the basis of a GUI according to an embodiment of the invention.
Fig. 6A- 6C schematically user-interaction on the basis of a GUI according to an embodiment of the invention.
Fig. 7A -7C schematically user-interaction on the basis of a GUI according to an embodiment of the invention.
Fig. 8A-8C schematically user-interaction on the basis of a GUI according to an embodiment of the invention.
Fig. 9 schematically the navigation through a structured set of GUIs according to an embodiment of the invention.
Fig. 10 depicts a schematic of a client or server system for use in a system according to the invention.
Detailed description
Fig. 1A and IB depict a process for rendering GUIs on a mobile user device according to an embodiment of the invention. In particular, Fig. 1A and IB depict user-interaction and navigation through a structured set of GUIs.
In this embodiment, a plurality of GUIs for (a touch screen based display of) a mobile device may be structured according to a decision tree scheme 100 as depicted in Fig. 1A. The decision tree comprises a root 102, branch nodes 104 and end-leaves 106, wherein the root and branch nodes may be labelled with an index (L,N) wherein L indicates the level of the node and N indicates the Nth node at level L.
As shown in Fig. IB, the root (the level 0 node) may be associated with a first "home" GUI 110 comprising selectable GUI elements 112, e.g. in this particular example five GUI elements, which refer to GUIs that are associated with branch nodes at on level lower (in this case level 1) in the decision tree. Hence, when selecting a particular GUI element in the first GUI(0,0), e.g. GUI element (1,3), the rendering of the associated second GUI(1,3) 114 may be triggered.
As will be described hereunder in more detail, a GUI element may be configured as a slidable graphical element that is uniquely identifiable by the user on the basis of visual information (e.g. color, icon, shape, symbol, picture, etc.).
In particular, each GUI element may comprise visual information informing the user on the type or class of information that can be accessed in the GUI can be selected on the basis of the GUI element.
The GUI elements may be arranged at positions relative to (in this case around) an activation area 116. A GUI element may be become freely movable by maintaining contact with the element while sliding the element in a certain direction. In this way, the second GUI(1,3) may be rendered by sliding a first GUI element (1,3) into the activation area 116 of the first GUI(0,0) and releasing the GUI element.
Similar to the first GUI(0,0), the second GUI(1,3) may comprise selectable GUI elements 118 and an activation area 120, wherein the activation area of GUI(1,3) displays GUI element (1,3). The user may again select a certain GUI element (e.g. GUI element (2,5)) and drag the element in the activation area of the second GUI(1,3) over the GUI element (1,2) in order to select the (next) third GUI(2,5) 122 comprising GUI elements 124 and an activation area 126, comprising GUI element (2,5) . The activation area comprises visual information informing the user on the type or class of information that can be accessed in the active GUI.
One or more of GUI elements in a GUI, e.g. GUI (1,3) or GUI(2,5), may point to information in the form of text, video and/or audio that the user can access by navigation through the GUIs as described above. Hence, these GUI elements do not point to branch nodes of yet a lower level but to end-leaves of the decision tree (see e.g. end-leave 106 in Fig. 1A). Hence, by selecting a GUI element and sliding GUI elements in the activation area, a user can navigate through the different GUIs in a very simple and intuitive way in order to access certain information.
The GUI navigation path 110 (schematically depicted in Fig. 1A) may be stored by the mobile device in the form of a GUI stack 128, e.g. a dedicated memory, comprising the sequence of GUI elements that were selected by the user when navigating from the root to a particular GUI in the decision tree. The GUI stack thus represents the sequence of GUI elements that are slided (dragged) by the user into the activation area wherein the GUI element on top of the stack represents the GUI that is currently active. A user may navigate back to GUIs of higher levels along the navigation path by simply touching the activation area of the GUI and maintaining contact while sliding the GUI element of the active GUI out of the activation area. This user interaction will trigger the user device to remove the last GUI element from the stack and to render the GUI associated with the next GUI element that is positioned at the top of the GUI stack.
The process of user-interaction and navigation through the structured GUIs as described with reference to Fig. 1A and IB will be executed on a mobile device comprising a client which is connected to a back-end as illustrated in Fig. 2A-2C. In particular, Fig. 2A depicts a dynamic GUI generation system comprising a user device 202 and a GUI server wherein the GUI server may be connected to one or more storage media 206, one or more content servers 208 and/or one or more service providers 209. The communication between the user device and the server may be realized on the basis of the HTTP protocol thereby avoiding problems with firewalls.
The user device may comprise an HTTP client 212 for transmitting HTTP request to the GUI server and receiving HTTP responses from the GUI sever. The user device may comprise a touch-sensitive display 218 for displaying GUIs to the user. The GUI may be rendered on the display by a GUI Tenderer 216. A GUI may be rendered on the basis of data that are transmitted upon request to the client. In particular, when activating an application that uses a GUI interaction and navigation process as depicted in Fig. 1A and IB, the application may instruct the HTTP client to request GUI data associated with the first GUI (0,0). The HTTP request may be received by an HTTP server 213 and trigger a GUI API 215 in the GUI server to collect GUI data associated with the requested GUI from the storage medium and, optionally, a content provider and/or a service provider, and send the GUI data back to the user device. In an embodiment, before it is sent to the client the GUI API may modify certain parts of the GUI data if certain conditions are met® Depending on the circumstances, the conditions may relate to the user data, e.g. subscription period, location data, etc., or other data such 0s the occuinrerice of 0. ceirtuiri event (e « cj« 0. temp0nsijri. 1 y sales offer, etc.). The GUI API may use these data to party modify the GUI data before they are sent to the GUI client.
This way the requested GUIs may be personalized in a dynamic way without re-installing the GUI application on the user di~\ TT1 /''I Z!T\ evice.
The GUI data sent to the user device may have a predetermined dst0 structure 0s depicted in more de10i1 in Fig. 2B and 2C. The GUI Tenderer will parse the structured GUI data and render a GUI on the basis of the GUI data. The GUI renderer may store the GUI data for further use and update the GUI stack in order to administer that GUI(0,0) is the active GUI. As shown in Fig. 2B, the GUI data may have a predetermined format, comprising a unique GUI identifier 224, e.g. the name of the requested GUI in terms of the location of the GUI within the decision tree (e.g. in terms of an index such as the (L,N) index as mentioned above) or any other suitable identifiers.
Further, the GUI data may comprise a reference to one or more GUI activation areas 226 and/or GUI elements 228. Both the activation area and the GUI elements may be associated with GUI parameters that define the shape, colour, coordinates, content, animation, text labels, etc. of the activation and/or the GUI elements. Further, for at least part of GUI elements the GUI data may comprise a GUI pointer (e.g. in the form of a GUI identifier or an URL) 230 that can be used by the GUI API to retrieve GUI data for GUIs that may be selected by a user when interacting with the active GUI(0,0). For example, in the GUI data example of Fig. 2B, each GUI element (e.g. GuiEl__l) points to a further GUI at level 1 (GuiWorld(1,1)). Alternatively, a GUI element of a GUI may point an end-label, e.g. a piece of information in the form of text, video and/or audio. Hence, in case a user selects such GUI element, the information may be presented to the user.
Fig. 2C depicts another embodiment of format of the GUI data. In this particular embodiment, the GUI data may comprise a GUI identifier, GUI activation area and/or GUI elements similar to those described with reference to Fig. 2B, In addition, the GUI elements may point to GUIs at a lower level (e.g. levell) that may be selected by a user when interacting with the GUI (0,0). In contrast with the embodiment of Fig. 2b, at least part of the GUI data 240,242 of these lower-level GUIs (in this example GUI(1,1) and GUI (1,2)) are already included in the GUI data of the requested GUI (in this case GUI (0,0)) . These GUI data may be stored in the memory 220 of the user device for later use. This way the user device may increase the response time as it is not necessary to update the GUI data by sending a request to the GUI server.
Hence, as will be described in more detail hereunder, when the GUI Tenderer has parsed the GUI data and built the GUI on the basis of the information therein, a user may start interacting with the GUI by selecting one of the GUI elements. In that case, a GUI interaction module may determine that the user has activated the activation area by sliding a particular GUI element (1,2) over it. In response, an HTTP request comprising the identifier of the requested GUI may be sent to the GUI server in order to send the GUI data to the user device .
Alternatively, if the GUI data of the requested GUI is already incorporated in the GUI data of the currently active GUI (e.g. as shown in Fig. 2C), the GUI data of the requested GUI may be retrieved directly from the GUI data in the memory.
Fig. 3 schematically depicts a user device 300 comprising a GUI client according to an embodiment of information. In particular, Fig. 3 depicts a user device, e.g. a smart phone or an electronic table or the like, comprising an GUI client 308, a memory module 308, a (touch-sensitive) display module 316 and an HTTP client connected via a data bus 318 to a microprocessor 306. The microprocessor may run software that is stored in the memory module for controlling the processes that are executed by and between the different modules and that enable the rendering of GUIs that are structured in a decision tree as described in detail with reference to Fig. 1A and IB. As shown in Fig. 3, the GUI data may be retrieved from a GUI server, wherein the GUI data comprise GUI activation area and/or GUI elements and their attributes defining shape, color, coordinates, etc. of the areas and elements. These data may be parsed by the GUI parser 312 and used by the GUI Tenderer 314 to configure the display 316 such that the activation area and the GUI elements are rendered in the display in accordance with the attribute values in the GUI data.
Fig. 4 depicts a flow diagram of a process for user-interaction and navigation through a structured set of GUIs according to an embodiment of the invention. The process may start with the user starting an application that requires the rendering of a first GUI(0,0) (the root) so that the GUI client sends a request for GUI data associated with the first GUI(0,0)(step 402). The request may have the form of an HTTP GET request comprising a request URL with a query string comprising additional one or more GUI parameters that may be used by an GUI API at the GUI server that is configured to collect the GUI data associated with GUI(0,0). The one or more GUI parameters may include a unique user identifier for identifying the client or the user and a GUI identifier for identifying the requested GUI.
The data collection may include requesting a GUI storage medium, e.g. database or the like, to deliver the GUI data of the requested GUI(0,0) (step 404). These GUI data may include information as described with reference to Fig. 2B and 2C. In certain embodiments the GUI data of one GUI may also include (parts of) GUI data of further GUIs, in particular GUIs that can be accessed by the user on the basis GUI(0,0) (in this example GUIs(l,l) (1,2) (1,3)). These GUI data may be returned to the GUI API in the GUI sever (step 406). Further, the GUI API may request a content provider for certain content that is needed to render the requested GUI. Alternatively and/or in addition the GUI API may request a service provider, e.g. a telecommunications provider or an energy delivery company, to provide user data or other data that are needed for rendering the GUI (steps 408 and 410).
In an embodiment the GUI API may modify certain parts of the GUI data if certain conditions are met. For example, in an embodiment, in case the user data relate to a subscription, the appearance (e.g. color and/or shape) of certain GUI elements may be changed is a condition is met (e.g. the end of the subscription is approaching). In another embodiment, the GUI API may add an additional GUI element if a certain condition is met. For example, an additional GUI element linked to a targeted advertisement or a personal offer may be added to the GUI.
Thereafter, the HTTP server may send the data in an HTTP response message back to the GUI client (step 412). The GUI client may then store the returned data in the memory (step 414) and add a reference to GUI(0,0), e.g. its identifiers, to the GUI stack, thereby indicating that GUI (0,0) is the active GUI. An the GUI render may use the GUI data for rendering the requested GUI(0,0) (step 416 and 418).
Thereafter, the user may slide GUI element (1,3) into the activation area of GUI(0,0) in order to access GUI(1,3) (step 420). Before sending an request to the GUI server for retrieving the GUI data for GUI(1,3) (in a similar way as described with reference to steps 402-412), the GUI client may first check the memory for the GUI data. As the GUI data of GUI(1,3) were sent along with the GUI data of GUI(0,0), the GUI client may check the memory and directly retrieve the data from the memory (step 422). The GUI client may add a reference to GUI(1,3) to the GUI stack (in order to make GUI(1,3) the active GUI) (step 424) and display the GUI to the user (steps 426 and 428).
In case the user decides to return to the previous GUI (in this case GUI (0,0)) by sliding GUI element (1,3) out of the activation area of GUI(1,3) (step 430), the GUI client may remove the reference to GUI(1,3) from the GUI stack (step 432) so that earlier GUI(0,0) becomes the active GUI. The GUI client may then use the stored GUI data of GUI(0,0) to display the GUI(0,0) to the user (step 434 and 436).
Examples of interactions of a user with the GUIs rendered by the GUI client on the display of a mobile device are described in more detail with reference to Fig. 5,6,7 and 8. In this particular example, the GUI application may be configured for allowing a user to access his subscription data for a mobile subscription. Fig. 5A depicts a first GUI comprising a first activation area 502 and one or more first GUI elements 504. A GUI element is selectable by contacting the GUI element. Upon contact, a first GUI element may be slided towards the first activation area as depicted in Fig. 5A-5C, wherein the user maintains contact with the first GUI element. During the sliding process, a message 506 associated with the first GUI element may be displayed for indicating the information (in this case the calling credit of the user) that is presented in or that can be accessed via the second GUI which will be rendered on the display of the mobile device once the first GUI element is moved into the first activation area.
In Fig. 6A the first GUI element 602 enters the first activation area 604 and once the user releases the contact 608 with the first GUI element, the GUI client is triggered to render the second GUI. In order to provide a smooth transition from the first GUI to the second GUI, the other first GUI elements may slowly decrease in size as shown in Fig. SB. In Fig. 6C the second GUI is rendered, wherein the a second activation area 610 and one or more second GUI elements are displayed. Here, the second activation area displays the first GUI element so that the user knows the type or class of information that can be accessed via the one or more second GUI elements 612 of the second GUI.
As shown in Fig. 7A, if the user decides to leave the second and to return to the first GUI, the user may select the first GUI element 702 in the second activation area of the second GUI and drag the first GUI element out of the second activation area while maintaining contact with said first GUI element. When the first GUI element is dragged out of the second activation area, a small first activation area 704 of the first GUI may already be displayed in order to provide a smooth transition from the second GUI to the first GUI. This process is shown in Fig. 7B and 7C,
In Fig. 8Ά the first GUI element 802 is dragged completely out of the second activation area, while the user is maintaining contact with the first GUI element. Thereafter, once the user released contact 807 with the first GUI element 802 (as shown in Fig. 8B) the GUI client will be triggered to render the first GUI comprising the first activation area and the all the GUI first elements 806 as shown in Fig. 8C (which is identical to Fig. 5A).
Hence, from Fig. 5-8 it follows that the invention allows simple rendering of GUIs in which the information for navigation through the GUIs and/or accessing certain information presented in a very clear and intuitive way to the user. The GUIs may be rendered on the basis of GUI data (including parameters that determine the shape and presentation of the activation area and/or GUI elements) that can be retrieved from a GUI server. Further, a GUI API in the GUI server may be configured to modify the GUI data on the basis of certain conditions (e.g. subscription is almost expired or calling credit is decreased below a certain value) so that the GUI may be personalized in a dynamic way without re-installing the application.
Fig. 9 depicts a further example the rendering and navigation through a structured set of GUIs that is structured on the basis of a decision tree as explained with reference to Fig. 1A and IB. In this particular example, a first "root" GUI 902 may be rendered comprising an activation area and GUI elements that point to further GUIs 904-912 at a lower level in the decision tree can be selected by moving a GUI element into the activation area. Certain GUIs may display certain user information 914 (in this case the calling credit of the user) to the user. A user may return to the previous GUI (on step higher in the decision tree) by moving the GUI element thcit is presented in the sotivstion <3.re3. out the sotivetion area. This way a user may navigate through the different GUIs.
Fig. 10 is a block diagram illustrating an exemplary data processing system that may be used in as described in this disclosure. Data processing system 1000 may include at least one processor 1002 coupled to memory elements 1004 through a system bus 806. As such, the data processing system may store program code within memory elements 1004. Further, processor 1002 may execute the program code accessed from memory elements 1004 via system bus 1006. In one aspect, data processing system may be implemented as a computer that is suitable for storing and/or executing program code. It should be appreciated, however, that data processing system 1000 may 1 n +- n fn ν'τη dhr· ρ^τί\7 q \ 7 q +~ οτπ ι πγ,1 τιπι τίγγ λ π τήρο q cn γ _JL. ALL px _A— C. X I L V*, X X O- V**. CA ~L- X X U* X X J_ W -Xm AAL W A. C-6. X X y y &G G. ALL —L, A X G** ï— CA GA. -A- A A Gj GA GA Λ-. GA G, G* Ay -ί- and memory that is capable of performing the functions described within this specification.
Memory elements 1004 may include one or more physical memory devices such as, for example, local memory 1008 and one or more bulk storage devices 1010. Local memory may refer to random access memory or other non-persistent memory device(s) generally used during actual execution of the program code. A bulk storage device may be implemented as a hard drive or other persistent data storage device. The processing system 1000 may also include one or more cache memories (not shown) that provide temporary storage of at least some program code in πγΗργ +- n T'P^Hiir^Ph fhp n 11 m Vh p* τ rvF 1—i τηρ c πγππττππ ρπΗρ vnii c? t~ Vac* _s_i x gx 1_Nai x_ g. up 1_m v_x. gx g*, tp g» x x gt x x ig x l n./ pg j_ vg x_ g*g x l l m m xx x_ex tj x_ex x l l g» gx ex g* x l l gx o g. eu retrieved from bulk storage device 1010 during execution.
Input/output (I/O) devices depicted as input device 1012 and output device 1014 optionally can be coupled to the data processing system. Examples of input device may include, but are not limited to, for example, a keyboard, a pointing device such as a mouse, or the like. Examples of output device may include, but are not limited to, for example, a monitor or display, speakers, or the like. Input device and/or output device may be coupled to data processing system either directly or through intervening I/O controllers, A network adapter 1016 may also be coupled to data processing system to enable it to become coupled to other systems, computer systems, remote network devices, and/or remote storage devices through intervening private or public networks. The network adapter may comprise a data receiver for receiving data that is transmitted by said systems, devices and/or networks to said data and a data transmitter for transmitting data to said systems, devices and/or networks. Modems, cable modems, and Ethernet cards are examples of different types of network adapter that may be used with data processing system.
As pictured in FIG. 10, memory elements 1004 may store an application 1018. It should be appreciated that data processing system 1000 may further execute an operating system (not shown) that can facilitate execution of the application. Application, being implemented in the form of executable program code, can be executed by data processing system 1000, e.g., by processor 1002, Responsive to executing application, data processing system may be configured to perform one or more operations to be described herein in further detail.
In one aspect, for example, data processing system 1000 may represent a client data processing system. In that case, application 1018 may represent a client application that, when executed, configures data processing system 1000 to perform the various functions described herein with reference to a "client". Examples of a client can include, but are not limited to, a personal computer, a portable computer, a mobile phone, or the like.
In another aspect, data processing system may represent a server. For example, data processing system may represent an (HTTP) server in which case application 1018, when executed, may configure data processing system to perform (HTTP) server operations. In another aspect, data processing system may represent a module, unit or function as referred to in this specification.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

Claims (17)

1. Werkwijze voor het weergeven van grafische gebruikersinterfaces (GUIs) op een mobiel gebruikersapparaat, het mobiele gebruikersapparaat omvattende een GUI cliënt voor het communiceren met een GUI server, die geconfigureerd is voor het leveren van GUI data aan de GUI cliënt, waarbij de methode het uitvoeren van computer-leesbare softwarecode omvat door ten minste één processor, bij voorkeur ten minste één microprocessor, in het mobiele gebruikersapparaat voor: het weergeven van een eerste GUI op basis van eerste GUI data, waarbij de eerste GUI een eerste activatiegebied en een eerste GUI element omvat dat naar een tweede GUI wijst; het weergeven van de tweede GUI op basis van tweede GUI data als een gebruiker van het eerste GUI element selecteert door het aanraken van het eerste GUI element en door het verschuiven van het eerste GUI element over het eerste activatiegebied, waarbij contact wordt gehouden met het eerste GUI element, de tweede GUI ten minste omvattende een tweede activatiegebied en ten minste een tweede GUI element dat naar een derde GUI wijst, waarbij het eerste GUI element wordt weergegeven in het tweede activatiegebied; het weergeven van de eerste GUI op basis van de eerste GUI data als een gebruiker het eerste GUI element in het tweede activatiegebied selecteert door het aanraken van het eerste GUI element en het verschuiven van het eerste GUI element buiten het tweede activatiegebied; en, het weergeven van de derde GUI op basis van derde GUI data door het aanraken van het tweede GUI element en het verschuiven van het tweede GUI element over het tweede activatiegebied en het eerste GUI element, terwijl contact wordt gehouden met het tweede GUI element.A method for displaying graphical user interfaces (GUIs) on a mobile user device, the mobile user device comprising a GUI client for communicating with a GUI server, which is configured to provide GUI data to the GUI client, the method executing computer-readable software code comprising at least one processor, preferably at least one microprocessor, in the mobile user device for: displaying a first GUI based on first GUI data, the first GUI having a first activation area and a first GUI element that points to a second GUI; displaying the second GUI based on second GUI data when a user selects the first GUI element by touching the first GUI element and by shifting the first GUI element over the first activation area, keeping in contact with the first GUI element, the second GUI comprising at least a second activation area and at least a second GUI element pointing to a third GUI, the first GUI element being displayed in the second activation area; displaying the first GUI based on the first GUI data when a user selects the first GUI element in the second activation area by touching the first GUI element and shifting the first GUI element outside the second activation area; and displaying the third GUI based on third GUI data by touching the second GUI element and shifting the second GUI element over the second activation area and the first GUI element while maintaining contact with the second GUI element. 2. Werkwijze volgens conclusie 1, waarbij de GUI data een GUI identifier, GUI parameters voor het definiëren van ten minste één activatiegebied en/of voor het definiëren van één of meerdere selecteerbare GUI elementen omvat; en, optioneel, ten minste één GUI pointer voor het verbinden van een GUI element met een verdere GUI.Method according to claim 1, wherein the GUI data comprises a GUI identifier, GUI parameters for defining at least one activation area and / or for defining one or more selectable GUI elements; and, optionally, at least one GUI pointer for connecting a GUI element to a further GUI. 3. Werkwijze volgens conclusie 1 of 2 omvattende: het verzenden een eerste verzoekbericht, bij voorkeur een http verzoekbericht, om de GUI server te verzoeken de eerste GUI data te leveren, waarbij het verzoekbericht een eerste GUI identifier omvat voor het identificeren van de eerste GUI; het ontvangen van een eerste antwoordbericht die de eerste GUI data omvat.The method of claim 1 or 2 comprising: sending a first request message, preferably an http request message, to request the GUI server to provide the first GUI data, the request message comprising a first GUI identifier for identifying the first GUI ; receiving a first response message comprising the first GUI data. 4. Werkwijze volgens één van de conclusies 1-3 omvattende : het verzenden van een verzoekbericht, bij voorkeur een http verzoekbericht, naar de GUI server voor het verzoeken van de levering van de tweede GUI data naar de GUI cliënt, als de gebruiker het eerste GUI element selecteert, het verzoekbericht bij voorkeur omvattende een GUI identifier voor het identificeren van de tweede GUI; en, het ontvangen van een antwoordbericht, bij voorkeur een http antwoordbericht, die de tweede GUI data omvat.The method of any one of claims 1-3 comprising: sending a request message, preferably an http request message, to the GUI server for requesting the delivery of the second GUI data to the GUI client, if the user is the first Select a GUI element, the request message preferably comprising a GUI identifier for identifying the second GUI; and, receiving a response message, preferably an http response message, which includes the second GUI data. 5. Werkwijze volgens conclusie 4 waarbij het verzoekbericht naar de GUI server wordt verzonden als de gebruiker het contact met het GUI element verbreekt terwijl het eerste GUI element is gepositioneerd over het eerste activatiegebied .The method of claim 4 wherein the request message is sent to the GUI server if the user disconnects the contact with the GUI element while the first GUI element is positioned over the first activation area. 6. Werkwijze volgens één van de conclusies 1-5 waarbij de GUI cliënt is geconfigureerd om de GUI weergave door de gebruiker te volgen op basis van een GUI stapelgeheu-gen met GUI identifiers, waarbij de GUI identifier op de top van het GUI stapelgeheugen de thans actieve GUI representeert .The method of any one of claims 1-5 wherein the GUI client is configured to track the GUI display by the user based on a GUI stack memory with GUI identifiers, wherein the GUI identifier at the top of the GUI stack memory currently active GUI. 7. Werkwijze volgens claim 6 omvattende: het toevoegen van de GUI identifier van de tweede GUI aan een GUI stapelgeheugen als de gebruiker het eerste GUI element selecteert door het aanraken van het eerste GUI element en het verschuiven van het eerste GUI element over het eerste activatiegebied; en, het verwijderen van de GUI identifier van de tweede GUI van het GUI stapelgeheugen als de gebruiker het eerste GUI element selecteert en het eerste GUI element buiten het tweede activatiegebied verschuift.The method according to claim 6 comprising: adding the GUI identifier of the second GUI to a GUI stack memory if the user selects the first GUI element by touching the first GUI element and shifting the first GUI element over the first activation area ; and, removing the GUI identifier from the second GUI from the GUI stack if the user selects the first GUI element and the first GUI element shifts outside the second activation area. 8. Werkwijze volgens één van de conclusies 1-7 waarbij de GUI parameters de vorm, kleur, coördinaten en/of de inhoud van het ten minste één activatiegebied en/of de één of meerdere GUI elementen.A method according to any one of claims 1-7, wherein the GUI parameters are the shape, color, coordinates and / or the content of the at least one activation area and / or the one or more GUI elements. 9. Werkwijze volgens één van de conclusies 1-8 waarbij de GUI server een GUI AIP omvat die geconfigureerd is om GUI data te verzamelen die opgevraagd zijn door de GUI cliënt bij een GUI database, een content provider en/of service provider.A method according to any one of claims 1-8 wherein the GUI server comprises a GUI AIP configured to collect GUI data requested by the GUI client from a GUI database, a content provider and / or service provider. 10. Werkwijze volgens één van de conclusies 1-9 waarbij de GUI AIP is geconfigureerd om ten minste een deel van de verzamelde GUI data te wijzigen voordat de verzamelde GUI data worden verzonden naar de GUI cliënt, waarbij bij voorkeur de GUI API ten minste een deel van de gebruikersin-formation en/of één of meerdere condities met betrekking tot de gebrulkersinformatie wijzigt; waarbij meer bij voorkeur de GUI API ten minst een deel van de verzamelde GUI data wijzigt zodanig dat het activatiegebied en/of GUI elementen wordt/worden gewijzigd als aan één of meerdere condities met betrekking tot de gebruikersinformatie is voldaan.The method of any one of claims 1-9 wherein the GUI AIP is configured to change at least a portion of the collected GUI data before the collected GUI data is sent to the GUI client, preferably the GUI API having at least one changes part of the user information and / or one or more conditions with regard to the user information; more preferably the GUI API modifying at least a portion of the collected GUI data such that the activation area and / or GUI elements is / are changed if one or more conditions with respect to the user information are met. 11. Werkwijze volgens één van de conclusies 1-10 waarbij de GUIs hiërarchisch gestructureerd zijn op basis van een beslissingsboom omvattende een wortel en een hoeveelheid takknooppunten, waarbij de wortel en de takknooppunten geassocieerd zijn met GUIs en waarbij het verschuiven van GUI elementen in of uit het activatiegebied het de gebruiker mogelijk maakt om door de GUIs te navigeren die zich bevinden op een pad van de beslissingsboom.The method of any one of claims 1-10 wherein the GUIs are hierarchically structured based on a decision tree comprising a root and a plurality of branch nodes, the root and branch nodes being associated with GUIs and shifting GUI elements in or out the activation area allows the user to navigate through the GUIs located on a path of the decision tree. 12. Mobiel gebruikersapparaat omvattende een GUI cliënt voor het weergeven van GUIs, waarbij de GUI cliënt is geconfigureerd om te communiceren met een GUI server die geconfigureerd is voor het leveren van GUI data aan de GUI cliënt, waarbij bij voorkeur de GUI data een GUI identifier, GUI parameters voor het definiëren van ten minste één activatiegebied en/of voor het definiëren van één of meerdere selecteerbare GUI elementen; en, optioneel, ten minste een GUI pointer voor het verbinden van een GUI element met een verdere GUI; het gebruikersapparaat omvattende een microprocessor die gekoppeld is aan een aanrakingsgevoelige display, een communicatiemodule, en een computer-leesbaar eerste geheugen met daarop computer-leesbare programmacode, waarbij in reactie op het uitvoeren van de computer-leesbare programmacode, de microprocessor geconfigureerd is om executeerbare operaties uit te voeren voor: het weergeven van een eerste GUI op basis van eerste GUI data, waarbij de eerste GUI een eerste activatiegebied en een eerste GUI element omvat dat naar een tweede GUI wijst; het weergeven van de tweede GUI op basis van tweede GUI data als een gebruiker van het eerste GUI element selecteert door het aanraken van het eerste GUI element en door het verschuiven van het eerste GUI element over het eerste activatiegebied, waarbij contact wordt gehouden met het eerste GUI element, de tweede GUI ten minste omvattende een tweede activatiegebied en ten minste een tweede GUI element dat naar een derde GUI wijst, waarbij het eerste GUI element wordt weergegeven in het tweede activatiegebied; het weergeven van de eerste GUI op basis van de eerste GUI data als een gebruiker het eerste GUI element in het tweede activatiegebied selecteert door het aanraken van het eerste GUI element en het verschuiven van het eerste GUI element buiten het tweede activatiegebied; en, het weergeven van de derde GUI op basis van derde GUI data door het aanraken van het tweede GUI element en het verschuiven van het tweede GUI element over het tweede activatiegebied en het eerste GUI element, terwijl contact wordt gehouden met het tweede GUI element.A mobile user device comprising a GUI client for displaying GUIs, wherein the GUI client is configured to communicate with a GUI server configured to provide GUI data to the GUI client, the GUI data preferably being a GUI identifier , GUI parameters for defining at least one activation area and / or for defining one or more selectable GUI elements; and, optionally, at least one GUI pointer for connecting a GUI element to a further GUI; the user device comprising a microprocessor coupled to a touch sensitive display, a communication module, and a computer-readable first memory with computer-readable program code thereon, wherein in response to executing the computer-readable program code, the microprocessor is configured to perform executable operations to perform for: displaying a first GUI based on first GUI data, the first GUI including a first activation area and a first GUI element pointing to a second GUI; displaying the second GUI based on second GUI data when a user selects the first GUI element by touching the first GUI element and by shifting the first GUI element over the first activation area, keeping in contact with the first GUI element, the second GUI comprising at least a second activation area and at least a second GUI element pointing to a third GUI, the first GUI element being displayed in the second activation area; displaying the first GUI based on the first GUI data when a user selects the first GUI element in the second activation area by touching the first GUI element and shifting the first GUI element outside the second activation area; and displaying the third GUI based on third GUI data by touching the second GUI element and shifting the second GUI element over the second activation area and the first GUI element while maintaining contact with the second GUI element. 13. Gebruikersapparaat volgens claim 12 waarbij de microprocessor verder geconfigureerd is om executeerbare operaties uit te voeren voor: het verzenden van een verzoekbericht, bij voorkeur een http verzoekbericht, naar de GUI server voor het verzoeken van de levering van de tweede GUI data naar de GUI cliënt, als de gebruiker het eerste GUI element selecteert, het verzoekbericht bij voorkeur omvattende een GUI identifier voor het identificeren van de tweede GUI; en, het ontvangen van een antwoordbericht, bij voorkeur een http antwoordbericht, die de tweede GUI data omvat.A user device according to claim 12 wherein the microprocessor is further configured to perform executable operations for: sending a request message, preferably an http request message, to the GUI server for requesting the delivery of the second GUI data to the GUI client, if the user selects the first GUI element, the request message preferably comprising a GUI identifier for identifying the second GUI; and, receiving a response message, preferably an http response message, which includes the second GUI data. 14. Gebruikersapparaat volgens claim 13 waarbij het verzoekbericht wordt verzonden naar de GUI server als de gebruiker het contact met het GUI element verbreekt terwijl het eerst GUI element gepositioneerd is over het eerst activatie-gebied.A user device according to claim 13 wherein the request message is sent to the GUI server if the user disconnects the contact with the GUI element while the first GUI element is positioned over the first activation area. 15. Gebruikersapparaat volgens één van de claims 12-14 waarbij de GUI cliënt is geconfigureerd om de GUI weergave door de gebruiker te volgen op basis van een GUI stapelgeheugen met GUI identifiers, waarbij de GUI identifier aan de top van het GUI stapelgeheugen de thans actieve GUI representeert.A user device according to any of claims 12-14 wherein the GUI client is configured to track the GUI display by the user based on a GUI stack with GUI identifiers, the GUI identifier at the top of the GUI stack being the currently active GUI represents. 16. Gebruikersapparaat volgens conclusie 15 waarbij de microprocessor verder is geconfigureerd om executeerbare operaties uit te voeren voor: het toevoegen van de GUI identifier van de tweede GUI aan een GUI stapelgeheugen als de gebruiker het eerste GUI element selecteert door het aanraken van het eerste GUI element en het verschuiven van het eerste GUI element over het eerste activatiegebied; en, het verwijderen van de GUI identifier van de tweede GUI van het GUI stapelgeheugen als de gebruiker het eerste GUI element selecteert en het eerste GUI element buiten het tweede activatiegebied verschuift.The user device of claim 15 wherein the microprocessor is further configured to perform executable operations for: adding the GUI identifier of the second GUI to a GUI stack memory if the user selects the first GUI element by touching the first GUI element and shifting the first GUI element over the first activation area; and, removing the GUI identifier from the second GUI from the GUI stack memory if the user selects the first GUI element and shifts the first GUI element outside the second activation area. 17. Computerprogrammaproduct omvattende delen van softwarecode die, wanneer die in het geheugen van een computer uitgevoerd worden, geconfigureerd zijn voor het uitvoeren van de werkwijzestappen volgens één van de conclusies 1-11.A computer program product comprising portions of software code which, when executed in the memory of a computer, are configured to perform the method steps of any one of claims 1-11.
NL2012236A 2014-02-10 2014-02-10 Graphical user interface for mobile touchscreen-based navigation. NL2012236C2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
NL2012236A NL2012236C2 (en) 2014-02-10 2014-02-10 Graphical user interface for mobile touchscreen-based navigation.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
NL2012236A NL2012236C2 (en) 2014-02-10 2014-02-10 Graphical user interface for mobile touchscreen-based navigation.
NL2012236 2014-02-10

Publications (1)

Publication Number Publication Date
NL2012236C2 true NL2012236C2 (en) 2015-08-17

Family

ID=50733261

Family Applications (1)

Application Number Title Priority Date Filing Date
NL2012236A NL2012236C2 (en) 2014-02-10 2014-02-10 Graphical user interface for mobile touchscreen-based navigation.

Country Status (1)

Country Link
NL (1) NL2012236C2 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2251442A1 (en) * 1998-10-22 2000-04-22 Northern Telecom Limited Web based gui server and method for a telecommunications node
US20070273663A1 (en) * 2006-05-24 2007-11-29 Ho Joo Park Touch screen device and operating method thereof
US20090122018A1 (en) * 2007-11-12 2009-05-14 Leonid Vymenets User Interface for Touchscreen Device
EP2088500A1 (en) * 2008-02-11 2009-08-12 Idean Enterprises Oy Layer based user interface

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2251442A1 (en) * 1998-10-22 2000-04-22 Northern Telecom Limited Web based gui server and method for a telecommunications node
US20070273663A1 (en) * 2006-05-24 2007-11-29 Ho Joo Park Touch screen device and operating method thereof
US20090122018A1 (en) * 2007-11-12 2009-05-14 Leonid Vymenets User Interface for Touchscreen Device
EP2088500A1 (en) * 2008-02-11 2009-08-12 Idean Enterprises Oy Layer based user interface

Similar Documents

Publication Publication Date Title
US10437418B2 (en) Overloading app icon touchscreen interaction to provide action accessibility
EP2548104B1 (en) Method and apparatus for displaying relative motion of objects on graphical user interface
KR101562098B1 (en) Progress bar
TWI604368B (en) Data processing method and device
EP2960765B1 (en) Method for selecting an entry for an application using a graphical user interface
US20160269498A1 (en) Frequent Sites Based on Browsing Patterns
US11934629B2 (en) Action tool bar for mobile applications
EP2511813A2 (en) Enhanced user interface to transfer media content
US9996222B2 (en) Automatic deep view card stacking
JP6440828B2 (en) Visibility detection of digital content
WO2012088483A2 (en) Application reporting in an application-selectable user interface
CN103809857A (en) Information processing method and electronic device
US10205678B2 (en) Systems and methods for client-side dynamic information resource activation and deactivation
US20130151937A1 (en) Selective image loading in mobile browsers
US11169652B2 (en) GUI configuration
CN110992112A (en) Method and device for processing advertisement information
KR102084701B1 (en) Associating content with a graphical interface window using a fling gesture
NL2012236C2 (en) Graphical user interface for mobile touchscreen-based navigation.
US11829573B2 (en) Dynamic user interface pagination operation
CN110622135B (en) System and method for providing content items in situations involving suboptimal network conditions
CN110083407B (en) Method and device for realizing step bar in applet, electronic equipment and storage medium
CN110045895B (en) Information processing method, system, medium, and computing device
KR102176912B1 (en) Apparatus for managing bookmark list and apparatus for the same
US20240111410A1 (en) Drag and drop interactions for a browser software application
CN112149028A (en) Page control method and device