Patent Application
20160274736
Computer systems are currently in wide use. Some computer systems are relatively large and may model the various operations of an entire enterprise or operation. Typically, effective modeling of a large operation will employ an extensive hierarchy of interrelated data. In order to effectively interact with the hierarchical interrelated data, such systems provide various forms and report, which are generally surfaced to a user through a rich client application executing on a client device that is on the same local area network as the computer system. Some systems may include, for instance, thousands of different forms (e.g. electronic fillable documents) and other types of elements. By having such forms or views available, users can cross-check and enter data more effectively and easily.
Some computer systems that manage significant amounts of hierarchical, interrelated data, such as a business system, are employed in geographically-separated implementations. For example, a user of such system may be located at an office or factory, while the server(s) with which the user interacts may be located thousands of miles away. In such instances, the user will typically interact with the server(s) using a thin client, such as a web browser. While the cloud implementation of the overall system may provide significant benefits to the end users, providing effective interaction with the hierarchical, interrelated data within the design constraints of a thin client, such as a web browser, is a challenge.
The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.
A computing device is configured to provide multi-window interaction with a source of hierarchical data. The computing devices includes a display, a processor configured to execute programmatic instructions, and a computer-readable storage media containing a sequence of instructions that, when executed by the processor, provide a thin-client application configured to interact with the source of hierarchical data. The thin-client application provides a first user interface relative to the source of hierarchical data and a second user interface relative to a selection of hierarchical data in the first user interface. The first and second user interfaces are rendered simultaneously in response to a user input requesting multi-window display.
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. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.
Embodiments described herein provide a multi-window interface for a thin-client application, such as a web browser, that includes dynamic linking of data provided in the multiple windows. The information displayed in the multiple windows is related. In accordance with an embodiment, as a user enters information into one window, related portions in the other windows automatically update. This dynamic communication between multiple windows allows a user to have an effective view of multi-level, interrelated data within a thin-client application.
In order to accommodate this variety of structure, data management system 102 is generally provided in a highly customizable fashion that may be tailored for an individual implementation by one or more developers. Once implemented, data management system 102 provides effective interactions with the data to users thereof. Data management system 102 includes user interface (UI) module 114 coupled to processor(s) 110. UI module 114, when executed by one or more processors 110, generates various user interfaces, such as forms, dialogs, reports, et cetera to users of data management system 102. Additionally, as shown in
Various thin-client applications, such as web browsers, typically implement a certain degree of standardized functionality. While the ubiquity and standardization facilities interoperability and widespread use of data management system 102, it can provide challenges for data interactions where multi-level views of data are necessary. In accordance with various embodiments herein, a multi-window interface is provided within a thin-client application, such as a web browser, that includes dynamic linking of data provided in the multiple windows. The information displayed in the multiple windows is related. In accordance with an embodiment, as a user enters information into one window, related portions in the other windows automatically update. This dynamic communication between multiple windows allows a user to have an effective view of multi-level, interrelated data within the thin-client application. Accordingly, at least some of the advantages of previous rich-client interactions with hierarchical, interrelated data are extended to thin-client applications within the design constraints of such thin-client applications.
Master UI 200 includes or is coupled to messaging module 206 as well as mapping module 208. Messaging module 206 ensures that the flow of messages to master UI 200, as well as any of its children 202, 204 is performed effectively. Mapping module 208 includes an indication of which data is provided by which child form 202, 204. In this way, as master UI 200 receives information from data management system 102, information is conveyed to the appropriate forms 202, 204 via messaging module 206. In one embodiment, displays, 200, 202, and 204 share the same session identification value at data management system 102. Thus, the physical resources of data management system 102 are conserved even as multiple, related user interfaces are spawned and used. In this way, no additional load is provided on data management system 102 even as significant additional data interaction functionalities are provided by the various interface. In one embodiment, the messaging between master user interface 200 and associated forms 202, 204 is provided using JavaScript. Additionally, in one embodiment, the thin-client application is compliant with at least one suitable thin-client application standard, such as HTML 5.
Messaging module 206 can be considered a dispatcher in that it will invoke code and notify appropriate interfaces on changes of state (across thread and/or across session). Additionally, in one embodiment, when a form is executed, an additional property can be added to the parameters passed to the form execution method that will couple the form to messaging module 206 such that inter-form communication is enabled. Messaging module 206 supports requests to invoke specific code on a UI thread as well as to call a refresh on the master UI 200. Additionally, Messaging module 206 notifies listener dispatchers (subscribed to or otherwise coupled to messaging module 206) that the current object has changed state. However, those skilled in the art will recognize that other forms of communication between the various user interfaces can be employed in accordance with the various embodiments described herein. Additionally, while embodiments have been described with respect to the various user interfaces having the same session, it is contemplated that embodiments can be practiced where the different user interfaces have different session identifiers on data management system 102. Further still, while embodiments have been described with respect to multiple windows operating within a single thin-client application on a single device, embodiments can be practiced wherein multiple related windows are provided across multiple thin-client applications on one or more computing devices.
The present discussion has mentioned processors and servers. In one embodiment, the processors and servers include computer processors with associated memory and timing circuitry, not separately shown. They are functional parts of the systems or devices to which they belong and are activated by, and facilitate the functionality of the other components or items in those systems.
Also, a number of user interface displays have been discussed. They can take a wide variety of different forms and can have a wide variety of different user actuatable input mechanisms disposed thereon. For instance, the user actuatable input mechanisms can be text boxes, check boxes, icons, links, drop-down menus, search boxes, et cetera. They can also be actuated in a wide variety of different ways. For instance, they can be actuated using a point and click device (such as a track ball or mouse). They can be actuated using hardware buttons, switches, a joystick or keyboard, thumb switches or thumb pads, et cetera. They can also be actuated using a virtual keyboard or other virtual actuators. In addition, where the screen on which they are displayed is a touch sensitive screen, they can be actuated using touch gestures. Also, where the device that displays them has speech recognition components, they can be actuated using speech commands.
A number of data stores have also been discussed. It will be noted they can each be broken into multiple data stores. All can be local to the systems accessing them, all can be remote, or some can be local while others are remote. All of these configurations are contemplated herein.
Also, the figures show a number of blocks with functionality ascribed to each block. It will be noted that fewer blocks can be used so the functionality is performed by fewer components. Also, more blocks can be used with the functionality distributed among more components.
The description is intended to include both public cloud computing and private cloud computing. Cloud computing (both public and private) provides substantially seamless pooling of resources, as well as a reduced need to manage and configure underlying hardware infrastructure.
A public cloud is managed by a vendor and typically supports multiple consumers using the same infrastructure. Also, a public cloud, as opposed to a private cloud, can free up the end users from managing the hardware. A private cloud may be managed by the organization itself and the infrastructure is typically not shared with other organizations. The organization still maintains the hardware to some extent, such as installations and repairs, etc.
It will also be noted that architecture 100, or portions of it, can be disposed on a wide variety of different devices. Some of those devices include servers, desktop computers, laptop computers, tablet computers, or other mobile devices, such as palm top computers, cell phones, smart phones, multimedia players, personal digital assistants, et cetera.
Under other embodiments, applications or systems are received on a removable Secure Digital (SD) card that is connected to a SD card interface 15. SD card interface 15 and communication links 13 communicate with a processor 17 along a bus 19 that is also connected to memory 21 and input/output (I/O) components 23, as well as clock 25 and location system 27.
I/O components 23, in one embodiment, are provided to facilitate input and output operations. I/O components 23 for various embodiments of the device 16 can include input components such as buttons, touch sensors, multi-touch sensors, optical or video sensors, voice sensors, touch screens, proximity sensors, microphones, tilt sensors, and gravity switches and output components such as a display device, a speaker, and or a printer port. Other I/O components 23 can be used as well.
Clock 25 illustratively comprises a real time clock component that outputs a time and date. It can also, illustratively, provide timing functions for processor 17.
Location system 27 illustratively includes a component that outputs a current geographical location of device 16. This can include, for instance, a global positioning system (GPS) receiver, a LORAN system, a dead reckoning system, a cellular triangulation system, or other positioning system. It can also include, for example, mapping software or navigation software that generates desired maps, navigation routes and other geographic functions.
Memory 21 stores operating system 29, network settings 31, applications 33, application configuration settings 35, data store 37, communication drivers 39, and communication configuration settings 41. Memory 21 can include all types of tangible volatile and non-volatile computer-readable memory devices. It can also include computer storage media (described below). Memory 21 stores computer readable instructions that, when executed by processor 17, cause the processor to perform computer-implemented steps or functions according to the instructions. Device 16 can have a thin-client application 24 which can be directed to interact with data management system 102. Processor 17 can be activated by other components to facilitate their functionality as well.
Examples of the network settings 31 include things such as proxy information, Internet connection information, and mappings. Application configuration settings 35 include settings that tailor the application for a specific enterprise or user. Communication configuration settings 41 provide parameters for communicating with other computers and include items such as GPRS parameters, SMS parameters, connection user names and passwords.
Applications 33 can be applications that have previously been stored on the device 16 or applications that are installed during use, although these can be part of operating system 29, or hosted external to device 16, as well.
The mobile device of
Note that other forms of the devices 16 are possible.
Computer 810 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 810 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media is different from, and does not include, a modulated data signal or carrier wave. It includes hardware storage media including both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 810. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
The system memory 830 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 831 and random access memory (RAM) 832. A basic input/output system 833 (BIOS), containing the basic routines that help to transfer information between elements within computer 810, such as during start-up, is typically stored in ROM 831. RAM 832 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 820. By way of example, and not limitation,
The computer 810 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only,
Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), et cetera.
The drives and their associated computer storage media discussed above and illustrated in
A user may enter commands and information into the computer 810 through input devices such as a keyboard 862, a microphone 863, and a pointing device 861, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 820 through a user input interface 860 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A visual display 891 or other type of display device is also connected to the system bus 821 via an interface, such as a video interface 890. In addition to the monitor, computers may also include other peripheral output devices such as speakers 897 and printer 896, which may be connected through an output peripheral interface 895.
The computer 810 is operated in a networked environment using logical connections to one or more remote computers, such as a remote computer 880. The remote computer 880 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 810. The logical connections depicted in
When used in a LAN networking environment, the computer 810 is connected to the LAN 871 through a network interface or adapter 870. When used in a WAN networking environment, the computer 810 typically includes or is coupled to a modem 872 or other means for establishing communications over the WAN 873, such as the Internet. The modem 872, which may be internal or external, may be connected to the system bus 821 via the user input interface 860, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 810, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
It should also be noted that the different embodiments described herein can be combined in different ways. That is, parts of one or more embodiments can be combined with parts of one or more other embodiments. All of this is contemplated herein.
Example 1 is a computing device is configured to provide multi-window interaction with a source of hierarchical data. The computing devices includes a display, a processor configured to execute programmatic instructions, and a computer-readable storage media containing a sequence of instructions that, when executed by the processor, provide a thin-client application configured to interact with the source of hierarchical data. The thin-client application provides a first user interface relative to the source of hierarchical data and a second user interface relative to a selection of hierarchical data in the first user interface. The first and second user interfaces are rendered simultaneously in response to a user input requesting multi-window display.
Example 2 is the computing device of any or all previous examples wherein the first and second user interfaces are communicatively coupled such that changes made to data displayed in one user interface are automatically applied to data in the other user interface.
Example 3 is the computing device of any or all previous examples wherein the first and second user interfaces have an identical session identifier relative to the source of hierarchical data.
Example 4 is the computing device of any or all previous examples wherein the first user interface is a master user interface.
Example 5 is the computing device of any or all previous examples wherein the second user interface is a child user interface receiving information via the master user interface.
Example 6 is the computing device of any or all previous examples wherein the thin-client application includes a messaging module that conveys information from the first user interface to the second user interface.
Example 7 is the computing device of any or all previous examples wherein the messaging module is a dispatcher that is configured to invoke code that provides a notification of a change of state.
Example 8 is the computing device of any or all previous examples and further comprising a third user interface rendered simultaneously with the first and second user interfaces and wherein the notification is provided to all user interfaces.
Example 9 is the computing device of any or all previous examples wherein the notification is provided to at least one subscriber.
Example 10 is the computing device of any or all previous examples wherein the first and second user interfaces are rendered side-by-side.
Example 11 is the computing device of any or all previous examples wherein the first and second user interfaces are rendered on the display.
Example 12 is the computing device of any or all previous examples wherein the thin-client application includes a mapping module containing an indication of which data from the source of hierarchical data is provided by the second user interface.
Example 13 is the computing device of any or all previous examples and further comprising a third user interface rendered simultaneously with the first and second user interfaces and wherein the mapping module contains an indication of which data from the source of hierarchical data is provided by each of the second and third interfaces.
Example 14 is a computer-implemented method for interacting with inter-related, hierarchical data using a thin-client application. The method includes directing the thin-client application to a source of inter-related, hierarchical data. A first display of the inter-related, hierarchical data is rendered. A user input is received selecting an aspect of the first display. A second display of the inter-related, hierarchical data is rendered. An input requesting multi-window display is received and the first and second displays are responsively provided showing inter-related data. The first and second displays are communicatively coupled together.
Example 15 is the computer-implemented method of any or all previous examples wherein directing the thin-client application to the source of inter-related, hierarchical data includes supplying a uniform resource locator to the thin-client application.
Example 16 is the computer-implemented method of any or all previous examples and further comprising receiving a user modification to data displayed in one of the first and second displays and automatically updating the other of the first and second displays based on the modification.
Example 17 is the computer-implemented method of any or all previous examples wherein the first and second displays are rendered on a single device.
Example 18 is the computer-implemented method of any or all previous examples and further comprising receiving a user input relative to one of the first and second displays, executing an operation relative to data displayed in the first and second windows, and blocking interaction with the first and second displays while the operation executes.
Example 19 is the computer-implemented method of any or all previous examples wherein receiving an input requesting multi-window display includes sensing a user action relative to a user interface element provided on the second display.
Example 20 is a data management system for inter-related hierarchical data. The data management system includes a processor and a data store coupled to the processor that contains the inter-related, hierarchical data. A user interface module is coupled to the processor and is configured to generate a plurality of user interfaces. A network interface is coupled to the user interface module and configured to couple the data management system to a network. The user interface module is configured to provide a plurality of user interfaces to a thin-client application, where each of the plurality of user interfaces has an identical session identifier.
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 specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
The present application is based on and claims the benefit of U.S. provisional patent application Ser. No. 62/133,704, filed Mar. 16, 2015, the content of which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 62133704 | Mar 2015 | US |
