US20030158975A1 - Real-time data interface and method for browsers and the like - Google Patents

Real-time data interface and method for browsers and the like Download PDF

Info

Publication number
US20030158975A1
US20030158975A1 US10/368,066 US36806603A US2003158975A1 US 20030158975 A1 US20030158975 A1 US 20030158975A1 US 36806603 A US36806603 A US 36806603A US 2003158975 A1 US2003158975 A1 US 2003158975A1
Authority
US
United States
Prior art keywords
engine
interface
data
widgets
network device
Prior art date
Legal status (The legal status 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 status listed.)
Abandoned
Application number
US10/368,066
Inventor
Brian Frank
John Sublett
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tridium Inc
Original Assignee
Tridium Inc
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 Tridium Inc filed Critical Tridium Inc
Priority to US10/368,066 priority Critical patent/US20030158975A1/en
Publication of US20030158975A1 publication Critical patent/US20030158975A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/34Graphical or visual programming
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/957Browsing optimisation, e.g. caching or content distillation
    • G06F16/9577Optimising the visualization of content, e.g. distillation of HTML documents
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/36Software reuse

Definitions

  • the present invention relates generally to user interfaces and more particularly to an extensible interface that draws in resources, as needed, for real-time presentation of data.
  • the present invention includes a method for providing a real-time data interface for a network device.
  • a page is loaded in a browser configured for operation on the network device.
  • the page includes an engine which is executed in the browser.
  • the engine is used to automatically load a definition file from a remote source in response to content within the loaded page.
  • One or more widgets are instantiated for display in the interface, with each widget making data requests at intervals prescribed by parameters for each respective widget. These data requests are forwarded to one or more servers that are in communication with the network device, and the requested data is thereafter received and presented in the interface as updated data.
  • the present invention includes an engine for providing a real-time data interface to a network device.
  • the engine comprises executable code configured to instantiate one or more widgets for rendering within the display of the real-time data interface.
  • the engine further includes a reference to a definition file which defines prescribed parameters for one or more of the widgets.
  • FIG. 1 is a flow diagram illustrating steps taken in accordance with a preferred method of the present invention.
  • FIG. 2 illustrates, schematically, a hierarchy of files for implementing the methodology of the preferred embodiment.
  • FIG. 3 is an illustrative display of several widgets that maybe displayed in a user interface constructed in accordance with the preferred embodiment.
  • the present invention concerns improvements in user interfaces, and more particularly, a lightweight and flexible software engine that permits visualization of real-time data feeds and other constantly changing information.
  • the interface of the present invention is unique in combining portability, low use of resources, and flexibility to accommodate changing operational platforms on which the interface can be presented as well as the changing needs of developers and users.
  • the particular platform that executes the user interface is sometimes referred to herein as the “network device.”
  • the interface of this invention allows the display of visual objects (called “widgets” herein), wherein each object can contain codes governing its own continuously changing behavior and the ability to interface with a user.
  • the interface is suitable for use with a component model as described in U.S. patent application Ser. No.
  • thin client we mean a user interface program, which can run in a standard off the shelf web browser such as Internet Explorer or Netscape Navigator/Communicator. Since non-programmers build systems, it is important that these screens be easily created using high-level graphical programming tools without knowledge of programming, HTML, JavaScript, etc.
  • the types of screens that would be desirable to display in a browser include graphics, alarms, charts, reports, and properties.
  • the graphical display of real-time status of system operation typically includes the display of current device status using pictorial representations. For example if a fan is on, then the graphic would display the fan blades rotating or air blowing.
  • the display and management of system alarms includes the ability to view, query, sort, and filter alarms from multiple systems and perform various levels of acknowledgement. It is beneficial to provide charts such as pie charts, line graphics, and bar charts to visually illustrate any data that has been mined from the system being monitored or controlled.
  • the solution of the present invention can be used in the Niagara component model as described in U.S. patent application Ser. No. To Be Assigned, filed on even date herewith [Attorney Docket No.: 3929/1K294US1] and entitled “Component Model for Real Time System Control,” or in any other application.
  • a Java applet called Wisp is used to creat the user interface; however, other compiled applications can be used.
  • a Java applet is a small Java program, which is downloaded to a web browser to fill a piece of an HTML page. In our case the Wisp applet typically fills the entire HTML page.
  • a browser is launched on a supporting platform in a conventional manner. If the platform is a personal computer, then the browser can be, for example, the Internet Explorer browser made available by the Microsoft Corporation, or the Netscape Communicator browser of Netscape Communications Corporation. If the platform is some other electronic device such as a cellular telephone or PDA, then the browser that is launched can be a streamlined version of one of those browsers, or a different browser altogether.
  • the platform is a personal computer
  • the browser can be, for example, the Internet Explorer browser made available by the Microsoft Corporation, or the Netscape Communicator browser of Netscape Communications Corporation. If the platform is some other electronic device such as a cellular telephone or PDA, then the browser that is launched can be a streamlined version of one of those browsers, or a different browser altogether.
  • the user operating a given platform references content that is available on a network from a server to which the browser is in communication. Communications between the platform and other devices on the network are not part of the present invention; however, they maybe in any one of a variety of wired or wireless arrangements as is conventional in the art.
  • Content is referenced, for example, by entering a web address in a location field of the browser, by selecting a destination from a pull down list, book mark, etc.
  • the reference comprises the address of a particular file that is available on the network to which the platform is in communication (e.g. “www.tridium.com/main.htm”).
  • communications are initiated across the network and the requested content is loaded into the browser, as indicated at step 115 .
  • the browser can be a conventional HTML browser, or another browser that is optimized to operate on a given platform.
  • an engine included within the loaded content is executed.
  • the engine comprises a java applet; however, the engine alternatively could be a servlett, a plug-in, or other code located within the content.
  • the engine is preferably a small footprint segment of executable code (e.g., java code) that is configured to automatically reference various definitions that are necessary to implement a given user interface. In this way, the web page itself can be trivial in design and rely upon the engine to fill the screen, and engines provide different user interfaces by referencing different definition files.
  • a remote definition file is referenced at step 125 , which defines a portion of the presentation of the user interface.
  • the definition file is preferably an XML file and governs the lay-out, appearance, border, font color, and other parameters that influence the visual presentation of widgets within the interface, as well as the interaction of the widgets with sources of data that populate each widget's respective data fields.
  • the definition file can influence the placement and sizing of each widget relative to one another within the user interface.
  • Widgets are visual objects. They can represent software components or physical devices. They may comprise graphs, pie-charts or tables and they can be animated and provide information in a number of different ways. Widgets also can have the ability to interact with the user.
  • the definition file that is referenced at step 125 can be configured to draw into the browser one or more gif images of a fan as well as the code that causes rotation of the gifs to emulate the movement of fan blades on the screen.
  • definition files are performed on the fly, that is, as the engine is executed. In this way, developers are not constrained to interface resources that are resident on the local browser, and users are not required to update their browsers in order to execute a given interface. Rather, the engine draws in passively and automatically the components and code necessary to implement the widgets that comprise a given user interface.
  • definition files can be sourced from a remote machine connected to the network, or can be resident locally on the platform.
  • the definition file is processed which causes any further extensions that may be necessary to implement a given widget to be fetched from a specified location (the configuration parameters for the widget itself), together with any code that is needed to process real-time data feeds for that widget (the configuration parameters for the data feed).
  • the engine can be relatively small in size and therefore suitable for use on cellular phones and with network configurations that have security settings that prevent downloading large objects.
  • the engine preferred embodiment is lightweight and able to render a table, chart, etc. in accordance with a given developer's requirements.
  • the individual widgets are not predefined, but can be added by way of extensions that are fetched at step 130 on an as-needed basis.
  • the one or more widgets that comprise the interface are displayed on the platform's browser.
  • Each widget referenced in the definition file can be supplied with a data feed in accordance with its own specific configuration parameters.
  • the configuration parameters define, among other things, the source for the data field, various protocal and handshaking parameters, and the ranges of the data to be supplied and displayed within a given widget.
  • the data feed requirements are periodically sent out to one or more remote sources available on the network and data that is obtained is returned back to the user interface for display in the browser.
  • the data feed requirements of multiple widgets are bundled together in an intelligent manner in order to minimize the number of requests issued out through the network.
  • the bundled request is done in accordance with the configuration parameters for the given data feed (for example, in order to request data from multiple devices at the same interval). While there are advantages to bundling data feed requirements such as reducing network bandwidth usage, the method in accordance with the present invention can be operated without, that is, free of, the bundling step.
  • a request for data from one or more remote sources is issued from the platform to a remote source.
  • the data request can be marshaled through the engine, or each individual widget can issue its own data request.
  • data is obtained in response to the data feed requirements and, as noted above, can optionally be bundled together from a remote source for transmission back to the browser.
  • a response is provided to the data feed request from the engine or a given widget, optionally as a single response.
  • step 160 responses to various data feed requests are unbundled at the software engine, assuming they were bundled in the first place. Thereafter at step 165 , the user interface display is updated. After a prescribed time interval or other interval, as indicated at step 170 , a test is made at step 175 to see whether there was any input from the platform to the browser.
  • the type of inputs that can be provided via the user interface can vary greatly.
  • the user interface can be a passive display of updated information from a remote source free of any input from the user. This may be appropriate in certain applications in which data is pushed to the user, such as applications in which stock prices and other financial data are being provided to a user. However, there are applications in which the user may wish to input data or an action through his browser to cause a change at a remote device. Such input can cause an action to be invoked on a remote server, for example, the purchase or sale of stock.
  • the user might wish to change configuration parameters for a given widget (say, the range of information being displayed within a graph) or may wish to change the state of an object being monitored (such as the on/off state of a fan).
  • Other inputs can include requests for new data feeds or requests for adding new gadgets to the user interface.
  • the variety of input that can be made at the client's side is not limited to the foregoing examples, which are meant to merely illustrate the types of input that could be provided. If there has been no input at the client's side, then the process loops back to step 145 to request more data from remote sources in order to update the user interface display.
  • the input is obtained at step 180 and is processed at step 185 either by forwarding the input to a remote server for handling, or handling locally if appropriate.
  • Inputs can be from a human user or provided automatically in response to rules or other program that is executing or providing control-information to the particular platform on which the user interface is running.
  • the visualization system is designed to be compatible with popular software used for displaying third party content over standardized file formats, such as an HTML browser.
  • the content that is referenced at step 110 can be the HTML file 210 which includes a plurality of tags as well as an applet entitled “Wispapplet.class” as the engine 220 .
  • the applet tags are encountered and the applet is executed.
  • Execution of the applet comprises executing a series of instructions included within the applet itself, and one of those instructions is a reference 222 to a remote definition file 225 .
  • the definition file can be an XML format or some other format, as noted above.
  • the definition file defines the presentation of the user interface and, in turn, includes one or more references 226 , 227 , 228 , 229 to respective extensions 236 , 237 , 238 , 239 .
  • the extensions include code suitable for executing various widgets and data processes that are necessary to the operation of the user interface. More specifically, each widget in a user interface can have its own extension of code that may be necessary for driving that widget.
  • the XML file itself may include sufficient information to execute the widget or the data feed.
  • the data feed execution codes that are referenced by the XML or other file provide code suitable for interacting with remote servers and devices in order to obtain data in the manner required by the user interface.
  • a user interface 300 contains a variety of illustrative widgets.
  • this user interface there is a visual representation of an analog gauge 310 , a bargraph of voltage versus time 320 , a pie chart 330 and a ticker 340 .
  • analog gauge 310 a bargraph of voltage versus time 320
  • pie chart 330 a pie chart 330
  • ticker 340 a ticker 340
  • the user can use an input device such as a mouse or other pointer to interact with one of these elements or with further control features such as a button 350 and the like in order to provide an input to perform any one of the functions described above in connection with steps 175 - 185 of FIG. 1.
  • an input device such as a mouse or other pointer to interact with one of these elements or with further control features such as a button 350 and the like in order to provide an input to perform any one of the functions described above in connection with steps 175 - 185 of FIG. 1.
  • Extensions may be located on the user's computer or on another computer connected to the user's computer by a computer network. Extensions can be located by references included in the configuration file.
  • the engine parses the configuration file and locates the extensions. The engine then loads the extensions, downloading them over a computer network, if necessary (step 104 ). The engine then executes in parallel all the extensions. If the engine is running in an environment that does not allow spawning parallel processes, the engine may be configured to simulate parallelism. Once the extensions are executing they display the user interface with the help of the engine. Each extension displays the widget it is associated with.
  • the engine displays the general layout, described in the configuration file, and it manipulates the displayed widgets in order to size and place them according to the configuration file.
  • the extensions may communicate with other software modules, and may change/update the widgets they are associated with according to these communications.
  • the extensions may further interact with the user, by accepting and responding to commands by the user.
  • the extensions may attempt to send or receive information from other software components based on interaction from the user.
  • the widgets thus continuously update, based on the software code of the extensions, communications with other software modules, and/or interaction with the user.
  • the extension may furthermore send control signals received from the user to other software modules.
  • the entire page can be a single applet deployed by a Java JAR file called wisp.jar.
  • the wisp jar file doesn't actually contain any predefined screens but rather contains a software engine used to construct any screen on the fly.
  • a parameter passed to the Wisp applet specifies a wisp file which contains the description of how to build the screen.
  • This wisp file can be a simple XML file which contains the instructions for how and what to build.
  • wisp files can be served off the file system or automatically generated using dynamic web technologies such as CGI, ASP, or Java Servlets. Only one small engine is sent to the client, which knows how to generically build any user interface from a wisp XML definition.
  • new user interface widgets can be plugged in by writing wisp extensions such as charts, alarm consoles, schedulers, etc.; a page may be partially re-loaded without requiring an entire refresh of the HTML page; and widgets may display a real-time data feed without requiring the page to be refreshed or reloaded.
  • wisp engine can maintain a persistent or polled connection back to the server. This connection may be used to refresh individual widgets in the page or to asynchronously receive events from the server.
  • Standard HTML technology requires a refresh of the entire page, but since the Wisp engine is an applet it can selectively do these networking calls under the covers.
  • the browser loads the HTML page which contains the Wisp applet with a parameter specifying which wisp file to use;
  • the Wisp applet initializes itself then loads the specified wisp file from the server;
  • the Wisp applet parses the XML to build the widgets specified; in our case this is a fan graphic and the alarm console;
  • the Wisp applet opens a logical connection back to the server to get the current status of the fan and the current list of alarms. This information is used to initialize the fan and alarm console widgets;
  • the Wisp applet maintains a connection either through polling or with a persistent HTML connection to listen for events on either the fan or alarm console. If for example a new alarm is generated, it is automatically updated in the alarm console widget. If the fan turns on or off it is immediately reflected in the graphical presentation of the fan.
  • Wisp architecture only requires that a simple XML file be created in order to build new screens it is extremely easy for developers to write CGI, ASP, or servlets to generate the Wisp XML on the fly. Likewise it is also very easy to create graphical programming tools to construct Wisp files without knowledge of the XML syntax.
  • the gauge 310 can represent a thermostat, which is controlled by a software module or a software component.
  • the extension for the widget corresponding to the thermostat sends requests for updated temperature readings over a network with which the platform is in communication.
  • the module controlling the thermostat answers those requests with data such as updates on temperature readings, operational state, associatiations with other devices, or device parameters.
  • a user can interact with the widget through the interface 300 , such as by clicking on the widget itself, for example, to change the scale from Celsius to Fahrenheit.
  • the extension receives such an input (at step 180 of FIG. 1).
  • the user can also send commands to the actual thermostat through the widget. For example, the user can switch the thermostat off (or devices associated with that thermostat), or put the thermostat and/or associated devices into a power saving mode. In this case, the widget forwards the command to the module controlling the thermostat.
  • the visual interface can better ensure efficient network communications by minimizing the number of open communication channels between the interface and one or more remote servers. Because multiple network communication channels operating in parallel can cause performance problems, the requests from individual widgets out to the network can be channeled through and managed by the engine 210 .
  • the engine can aggregate network communication requests over predefined periods of time and combine them as appropriate into bundles of larger size for transmission over the network, thus improving network efficiency. As noted in connection with the process of FIG. 1, only communications destined for the same network address or root server can be bundled. Bundling requires an associated software module at the receiving end to unbundle the communications.
  • the engine 210 may also receive bundles from certain remote software modules which contain data concerning more than one widget in the interface 300 . Such bundles are unbundled and provided to the extensions (that is, to the particular widget's code) that made the initial data request.
  • the visual interface system has been described using languages, formats and protocols, such as HTML, Java, XML, for the purpose of concreteness and clarity.
  • the visual interface system is not limited to these languages, formats and protocols.
  • the visual interface system may be configured to operate with any language that allows embedded applications. Any data file format, including proprietary data formats may be used instead of XML for the definition file.

Abstract

Providing a real-time data display and interface for a network device by loading a page in a browser, the page including an engine which is executed in the browser and used to automatically load a definition file from a remote source in response to content within the page. Widgets are instantiated for display in the interface, each making data requests at intervals which are forwarded to one or more servers in communication with the network device. Requested data is received and presented in the interface thereby providing the user with dynamically updated data. An engine for driving such display comprises executable code configured to instantiate one or more widgets for rendering within the display of the real-time data interface. The engine further includes a reference to a definition file which defines prescribed parameters for one or more of the widgets.

Description

  • This patent application claims the benefit of priority under 35 U.S.C. 119 from U.S. Provisional Patent Application Serial No. 60/357,329, filed Feb. 15, 2002, entitled “COMPONENT MODEL FOR REAL-TIME SYSTEM CONTROL”, which is hereby incorporated by reference as if set forth in its entirety herein.[0001]
  • FIELD OF THE INVENTION
  • The present invention relates generally to user interfaces and more particularly to an extensible interface that draws in resources, as needed, for real-time presentation of data. [0002]
  • BACKGROUND OF THE INVENTION
  • Several technologies are available to assist in gathering and presenting data for display through a user interface. One technology is ActiveX of the Microsoft Corporation which provides a robust set of tools to assist in issuing data requests and in processing the requests for presentation on a display. A limitation of ActiveX technology is that it has a large footprint, that is, its memory requirement is not practical for all applications (e.g., for some wireless platforms such as cellular telephones and personal digital assistants (“PDA”)). Another technology is Sun's Java engine but again, an interface that requires that engine has a large footprint and has a predetermined set of abilities as of the release date of the engine. There remains a need in the art for an open, extensible interface engine that has a small native footprint yet is capable of pulling in components, as needed, to suit a given application or platform. The present invention addresses these and other needs. [0003]
  • SUMMARY OF THE INVENTION
  • In one aspect, the present invention includes a method for providing a real-time data interface for a network device. In that method, a page is loaded in a browser configured for operation on the network device. The page includes an engine which is executed in the browser. The engine is used to automatically load a definition file from a remote source in response to content within the loaded page. One or more widgets are instantiated for display in the interface, with each widget making data requests at intervals prescribed by parameters for each respective widget. These data requests are forwarded to one or more servers that are in communication with the network device, and the requested data is thereafter received and presented in the interface as updated data. [0004]
  • In another aspect, the present invention includes an engine for providing a real-time data interface to a network device. The engine comprises executable code configured to instantiate one or more widgets for rendering within the display of the real-time data interface. The engine further includes a reference to a definition file which defines prescribed parameters for one or more of the widgets. [0005]
  • These and other aspects, features and advantages of the present invention can be further understood from the accompanying Drawing figures and description of a preferred embodiment.[0006]
  • BRIEF DESCRIPTION OF THE DRAWING FIGURES
  • FIG. 1 is a flow diagram illustrating steps taken in accordance with a preferred method of the present invention. [0007]
  • FIG. 2 illustrates, schematically, a hierarchy of files for implementing the methodology of the preferred embodiment. [0008]
  • FIG. 3 is an illustrative display of several widgets that maybe displayed in a user interface constructed in accordance with the preferred embodiment.[0009]
  • DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT
  • By way of overview and introduction, the present invention concerns improvements in user interfaces, and more particularly, a lightweight and flexible software engine that permits visualization of real-time data feeds and other constantly changing information. The interface of the present invention is unique in combining portability, low use of resources, and flexibility to accommodate changing operational platforms on which the interface can be presented as well as the changing needs of developers and users. The particular platform that executes the user interface is sometimes referred to herein as the “network device.” The interface of this invention allows the display of visual objects (called “widgets” herein), wherein each object can contain codes governing its own continuously changing behavior and the ability to interface with a user. In part, the interface is suitable for use with a component model as described in U.S. patent application Ser. No. To Be Assigned, filed on even date herewith [Attorney Docket No.: 3929/1K294US1] and entitled “Component Model for Real Time System Control,” which is hereby incorporated by reference as if set forth in in its entirety herein. [0010]
  • It is generally desirable to allow non-programmers to create their own thin-client user interfaces. By “thin client” we mean a user interface program, which can run in a standard off the shelf web browser such as Internet Explorer or Netscape Navigator/Communicator. Since non-programmers build systems, it is important that these screens be easily created using high-level graphical programming tools without knowledge of programming, HTML, JavaScript, etc. [0011]
  • Among others, the types of screens that would be desirable to display in a browser include graphics, alarms, charts, reports, and properties. The graphical display of real-time status of system operation typically includes the display of current device status using pictorial representations. For example if a fan is on, then the graphic would display the fan blades rotating or air blowing. The display and management of system alarms includes the ability to view, query, sort, and filter alarms from multiple systems and perform various levels of acknowledgement. It is beneficial to provide charts such as pie charts, line graphics, and bar charts to visually illustrate any data that has been mined from the system being monitored or controlled. For example if the system is collecting historical data for outside air temperature and runtimes for a piece of equipment, it is valuable to see that historical data presented in one chart. Users should be able to generically query any data found within the system to build reports using text, tabular information, or charts. It is also desirable to be able to view and edit properties of any component in the system generically without the component developer having to manually create a special web user interface. [0012]
  • The solution of the present invention can be used in the Niagara component model as described in U.S. patent application Ser. No. To Be Assigned, filed on even date herewith [Attorney Docket No.: 3929/1K294US1] and entitled “Component Model for Real Time System Control,” or in any other application. In the preferred embodiment, a Java applet called Wisp is used to creat the user interface; however, other compiled applications can be used. A Java applet is a small Java program, which is downloaded to a web browser to fill a piece of an HTML page. In our case the Wisp applet typically fills the entire HTML page. [0013]
  • Referring now to FIG. 1, use of an interface and method in accordance with a preferred embodiment is described. At [0014] step 105, a browser is launched on a supporting platform in a conventional manner. If the platform is a personal computer, then the browser can be, for example, the Internet Explorer browser made available by the Microsoft Corporation, or the Netscape Communicator browser of Netscape Communications Corporation. If the platform is some other electronic device such as a cellular telephone or PDA, then the browser that is launched can be a streamlined version of one of those browsers, or a different browser altogether.
  • At [0015] step 110, the user operating a given platform references content that is available on a network from a server to which the browser is in communication. Communications between the platform and other devices on the network are not part of the present invention; however, they maybe in any one of a variety of wired or wireless arrangements as is conventional in the art. Content is referenced, for example, by entering a web address in a location field of the browser, by selecting a destination from a pull down list, book mark, etc. The reference comprises the address of a particular file that is available on the network to which the platform is in communication (e.g. “www.tridium.com/main.htm”). Upon referencing a particular web page or other contents, communications are initiated across the network and the requested content is loaded into the browser, as indicated at step 115. Again, the browser can be a conventional HTML browser, or another browser that is optimized to operate on a given platform.
  • At [0016] step 120, an engine included within the loaded content, is executed. In one implementation, the engine comprises a java applet; however, the engine alternatively could be a servlett, a plug-in, or other code located within the content. More specifically, the engine is preferably a small footprint segment of executable code (e.g., java code) that is configured to automatically reference various definitions that are necessary to implement a given user interface. In this way, the web page itself can be trivial in design and rely upon the engine to fill the screen, and engines provide different user interfaces by referencing different definition files.
  • As a result of executing the engine, a remote definition file is referenced at step [0017] 125, which defines a portion of the presentation of the user interface. The definition file is preferably an XML file and governs the lay-out, appearance, border, font color, and other parameters that influence the visual presentation of widgets within the interface, as well as the interaction of the widgets with sources of data that populate each widget's respective data fields. As well, the definition file can influence the placement and sizing of each widget relative to one another within the user interface.
  • Widgets are visual objects. They can represent software components or physical devices. They may comprise graphs, pie-charts or tables and they can be animated and provide information in a number of different ways. Widgets also can have the ability to interact with the user. [0018]
  • As an example, the definition file that is referenced at step [0019] 125 can be configured to draw into the browser one or more gif images of a fan as well as the code that causes rotation of the gifs to emulate the movement of fan blades on the screen.
  • Referencing of definition files is performed on the fly, that is, as the engine is executed. In this way, developers are not constrained to interface resources that are resident on the local browser, and users are not required to update their browsers in order to execute a given interface. Rather, the engine draws in passively and automatically the components and code necessary to implement the widgets that comprise a given user interface. These definition files can be sourced from a remote machine connected to the network, or can be resident locally on the platform. As a result of execution of the engine and references to the definition file, at [0020] step 130 the definition file is processed which causes any further extensions that may be necessary to implement a given widget to be fetched from a specified location (the configuration parameters for the widget itself), together with any code that is needed to process real-time data feeds for that widget (the configuration parameters for the data feed).
  • As can be appreciated, the engine can be relatively small in size and therefore suitable for use on cellular phones and with network configurations that have security settings that prevent downloading large objects. Rather than providing a large native engine within the browser, the engine preferred embodiment is lightweight and able to render a table, chart, etc. in accordance with a given developer's requirements. The individual widgets are not predefined, but can be added by way of extensions that are fetched at [0021] step 130 on an as-needed basis. At step 135, the one or more widgets that comprise the interface are displayed on the platform's browser.
  • Each widget referenced in the definition file can be supplied with a data feed in accordance with its own specific configuration parameters. The configuration parameters define, among other things, the source for the data field, various protocal and handshaking parameters, and the ranges of the data to be supplied and displayed within a given widget. The data feed requirements are periodically sent out to one or more remote sources available on the network and data that is obtained is returned back to the user interface for display in the browser. [0022]
  • Optionally, the data feed requirements of multiple widgets are bundled together in an intelligent manner in order to minimize the number of requests issued out through the network. The bundled request is done in accordance with the configuration parameters for the given data feed (for example, in order to request data from multiple devices at the same interval). While there are advantages to bundling data feed requirements such as reducing network bandwidth usage, the method in accordance with the present invention can be operated without, that is, free of, the bundling step. [0023]
  • Regardless of whether data feed requirements are bundled at [0024] step 140, at step 145 a request for data from one or more remote sources is issued from the platform to a remote source. The data request can be marshaled through the engine, or each individual widget can issue its own data request. At step 150, data is obtained in response to the data feed requirements and, as noted above, can optionally be bundled together from a remote source for transmission back to the browser. Thus, as shown at step 155, a response is provided to the data feed request from the engine or a given widget, optionally as a single response. Of course, if the data comes from sources connected to different machines on the network, there would be no need to bundle all requests to a single response; the point here is that a minimized number of network data-feed requests can be issued through computer networks by aggregating those requests that are destined for the same server.
  • At [0025] step 160, responses to various data feed requests are unbundled at the software engine, assuming they were bundled in the first place. Thereafter at step 165, the user interface display is updated. After a prescribed time interval or other interval, as indicated at step 170, a test is made at step 175 to see whether there was any input from the platform to the browser.
  • The type of inputs that can be provided via the user interface can vary greatly. The user interface can be a passive display of updated information from a remote source free of any input from the user. This may be appropriate in certain applications in which data is pushed to the user, such as applications in which stock prices and other financial data are being provided to a user. However, there are applications in which the user may wish to input data or an action through his browser to cause a change at a remote device. Such input can cause an action to be invoked on a remote server, for example, the purchase or sale of stock. As another example, the user might wish to change configuration parameters for a given widget (say, the range of information being displayed within a graph) or may wish to change the state of an object being monitored (such as the on/off state of a fan). Other inputs can include requests for new data feeds or requests for adding new gadgets to the user interface. The variety of input that can be made at the client's side is not limited to the foregoing examples, which are meant to merely illustrate the types of input that could be provided. If there has been no input at the client's side, then the process loops back to step [0026] 145 to request more data from remote sources in order to update the user interface display.
  • On the other hand, if there was an input at the client's side, the input is obtained at [0027] step 180 and is processed at step 185 either by forwarding the input to a remote server for handling, or handling locally if appropriate. Inputs can be from a human user or provided automatically in response to rules or other program that is executing or providing control-information to the particular platform on which the user interface is running.
  • The process continues as described above to request additional data from one or more remote sources in order to continuously update the display the user interface with real time data feeds. [0028]
  • The visualization system is designed to be compatible with popular software used for displaying third party content over standardized file formats, such as an HTML browser. [0029]
  • Referring now to FIG. 2, the content that is referenced at [0030] step 110 can be the HTML file 210 which includes a plurality of tags as well as an applet entitled “Wispapplet.class” as the engine 220. Upon loading the HTML file 210 the applet tags are encountered and the applet is executed. Execution of the applet comprises executing a series of instructions included within the applet itself, and one of those instructions is a reference 222 to a remote definition file 225. The definition file can be an XML format or some other format, as noted above. The definition file defines the presentation of the user interface and, in turn, includes one or more references 226, 227, 228, 229 to respective extensions 236, 237, 238, 239. The extensions include code suitable for executing various widgets and data processes that are necessary to the operation of the user interface. More specifically, each widget in a user interface can have its own extension of code that may be necessary for driving that widget. On the other hand, the XML file itself may include sufficient information to execute the widget or the data feed. As well, the data feed execution codes that are referenced by the XML or other file provide code suitable for interacting with remote servers and devices in order to obtain data in the manner required by the user interface.
  • Referring now to FIG. 3, a [0031] user interface 300 contains a variety of illustrative widgets. In this user interface, there is a visual representation of an analog gauge 310, a bargraph of voltage versus time 320, a pie chart 330 and a ticker 340. Of course, these are merely illustrative of some of the different types of devices that can be displayed within the user interface. As noted above, each of these widgets sends out data request to remote devices to populate their respective displays with real time information. In addition, the user can use an input device such as a mouse or other pointer to interact with one of these elements or with further control features such as a button 350 and the like in order to provide an input to perform any one of the functions described above in connection with steps 175-185 of FIG. 1.
  • There is some executable code associated with each widget, referenced in the configuration file. This code is referred to as an extension. Extensions may be located on the user's computer or on another computer connected to the user's computer by a computer network. Extensions can be located by references included in the configuration file. The engine parses the configuration file and locates the extensions. The engine then loads the extensions, downloading them over a computer network, if necessary (step [0032] 104). The engine then executes in parallel all the extensions. If the engine is running in an environment that does not allow spawning parallel processes, the engine may be configured to simulate parallelism. Once the extensions are executing they display the user interface with the help of the engine. Each extension displays the widget it is associated with. The engine displays the general layout, described in the configuration file, and it manipulates the displayed widgets in order to size and place them according to the configuration file. The extensions may communicate with other software modules, and may change/update the widgets they are associated with according to these communications. The extensions may further interact with the user, by accepting and responding to commands by the user. The extensions may attempt to send or receive information from other software components based on interaction from the user. The widgets thus continuously update, based on the software code of the extensions, communications with other software modules, and/or interaction with the user. The extension may furthermore send control signals received from the user to other software modules.
  • An example of a Wisp HTML page: [0033]
    <html> <body bgcolor = ′#c8c8c8′ >
    <applet name = ’Wisp′ code = ′wisp.WispApplet′
    width = ′100%′ height = ′100%′
    codebase = ‘/’ archive = ′wisp.jar′ >
    <param name = ′file’ value = ′/homepage wisp′ >
    < /applet>
    < /body > < /html >
  • The entire page can be a single applet deployed by a Java JAR file called wisp.jar. The wisp jar file doesn't actually contain any predefined screens but rather contains a software engine used to construct any screen on the fly. A parameter passed to the Wisp applet specifies a wisp file which contains the description of how to build the screen. This wisp file can be a simple XML file which contains the instructions for how and what to build. A simple example of what a wisp file looks like is as follows: [0034]
    < wisp >
    < content type = “EdgePane” >
    <center type = ”Table” data = ”/go-get-table-data” / >
    <bottom type = ”Button” invoke = ” refresh( )” />
    < /content >
    < /wisp >
  • The major advantage of this approach is that wisp files can be served off the file system or automatically generated using dynamic web technologies such as CGI, ASP, or Java Servlets. Only one small engine is sent to the client, which knows how to generically build any user interface from a wisp XML definition. [0035]
  • Thus, new user interface widgets can be plugged in by writing wisp extensions such as charts, alarm consoles, schedulers, etc.; a page may be partially re-loaded without requiring an entire refresh of the HTML page; and widgets may display a real-time data feed without requiring the page to be refreshed or reloaded. What makes these features possible is the fact that the wisp engine can maintain a persistent or polled connection back to the server. This connection may be used to refresh individual widgets in the page or to asynchronously receive events from the server. Standard HTML technology requires a refresh of the entire page, but since the Wisp engine is an applet it can selectively do these networking calls under the covers. [0036]
  • To take an example, imagine a wisp page, which displays two widgets. One is a graphical representation of a fan and another is an alarm console. The steps to load this page include: [0037]
  • 1. The browser loads the HTML page which contains the Wisp applet with a parameter specifying which wisp file to use; [0038]
  • 2. The Wisp applet initializes itself then loads the specified wisp file from the server; [0039]
  • 3. The Wisp applet parses the XML to build the widgets specified; in our case this is a fan graphic and the alarm console; [0040]
  • 4. The Wisp applet opens a logical connection back to the server to get the current status of the fan and the current list of alarms. This information is used to initialize the fan and alarm console widgets; [0041]
  • 5. The Wisp applet maintains a connection either through polling or with a persistent HTML connection to listen for events on either the fan or alarm console. If for example a new alarm is generated, it is automatically updated in the alarm console widget. If the fan turns on or off it is immediately reflected in the graphical presentation of the fan. [0042]
  • Since the Wisp architecture only requires that a simple XML file be created in order to build new screens it is extremely easy for developers to write CGI, ASP, or servlets to generate the Wisp XML on the fly. Likewise it is also very easy to create graphical programming tools to construct Wisp files without knowledge of the XML syntax. [0043]
  • Referring again to FIG. 3, the [0044] gauge 310 can represent a thermostat, which is controlled by a software module or a software component. The extension for the widget corresponding to the thermostat sends requests for updated temperature readings over a network with which the platform is in communication. The module controlling the thermostat answers those requests with data such as updates on temperature readings, operational state, associatiations with other devices, or device parameters. A user can interact with the widget through the interface 300, such as by clicking on the widget itself, for example, to change the scale from Celsius to Fahrenheit. The extension receives such an input (at step 180 of FIG. 1). The user can also send commands to the actual thermostat through the widget. For example, the user can switch the thermostat off (or devices associated with that thermostat), or put the thermostat and/or associated devices into a power saving mode. In this case, the widget forwards the command to the module controlling the thermostat.
  • Alternatively, the visual interface can better ensure efficient network communications by minimizing the number of open communication channels between the interface and one or more remote servers. Because multiple network communication channels operating in parallel can cause performance problems, the requests from individual widgets out to the network can be channeled through and managed by the [0045] engine 210. The engine can aggregate network communication requests over predefined periods of time and combine them as appropriate into bundles of larger size for transmission over the network, thus improving network efficiency. As noted in connection with the process of FIG. 1, only communications destined for the same network address or root server can be bundled. Bundling requires an associated software module at the receiving end to unbundle the communications. The engine 210 may also receive bundles from certain remote software modules which contain data concerning more than one widget in the interface 300. Such bundles are unbundled and provided to the extensions (that is, to the particular widget's code) that made the initial data request.
  • The visual interface system has been described using languages, formats and protocols, such as HTML, Java, XML, for the purpose of concreteness and clarity. The visual interface system is not limited to these languages, formats and protocols. The visual interface system may be configured to operate with any language that allows embedded applications. Any data file format, including proprietary data formats may be used instead of XML for the definition file. [0046]
  • The present invention has been described in connection with an exemplary embodiment thereof, but is limited only with respect to the recitations in any claims that follow. [0047]

Claims (18)

We claim:
1. A method for providing a real-time data interface for a network device, comprising the steps of:
loading a page in a browser configured for operation on the network device, the page including an engine;
executing the engine in the browser;
using the engine to automatically load a definition file from a remote source in response to content within the loaded page;
instantiating one or more widgets in the interface and displaying them therein, each widget making data requests;
forwarding the data requests to one or more servers in communication with the network device;
receiving the requested data; and
updating the interface with the received data.
2. The method of claim 1, including the additional steps of:
loading one or more software programs each being associated with the one or more widgets in response to the instantiating step; and
executing the software programs.
3. The method of claim 1, including the additional step of repeating the forwarding, receiving and updating steps at intervals prescribed by resprective widgets in the interface.
4. The method of claim 1, including the additional step of directing data requests from at least one of the widgets directly to a particular server in communication with the network device.
5. The method of claim 1, including the additional step of directing data requests from each respective widget to the engine, wherein the forwarding step is performed by the engine.
6. The method of claim 1, wherein the forwarding and receiving steps are performed over a wireless communication link.
7. The method of claim 1, including the additional steps of:
testing for inputs provided through the interface at the network device; and
processing the inputs at one of the network device and the remote source.
8. The method of claim 7, wherein the input provided through the interface influences the appearance of the data displayed in the one or more widgets.
9. The method of claim 7, wherein the inputs are provided by a human user.
10. The method of claim 7, wherein the inputs are provided programmatically by the network device itself.
11. The method of claim 1, wherein the page loaded in the browser is a web page.
12. The method of claim 11, wherein the web page includes a body portion that consists essentially of the engine.
13. The method of claim 1, wherein each widget is generated dynamically in response to the definition file at the remote source.
14. An engine for providing a real-time data interface to a network device, comprising:
executable code configured to instantiate one or more widgets for rendering within the display of the real-time data interface; and
a reference to a definition file which defines prescribed parameters for one or more of the widgets.
15. The engine of claim 14, wherein the definition file includes extensions to futher code suitable for at least one of: rendering one or more of the widgets, requesting data for the widget to display within the interface, and receiving data for the widget to display in the interface.
16. The engine of claim 14, futher comprising a page in a prescribed format that includes the engine.
17. The engine of claim 16, wherein the page is in an HTML format.
18. The engine of claim 14, wherein the definition file is located at a source remote from the network device.
US10/368,066 2002-02-15 2003-02-18 Real-time data interface and method for browsers and the like Abandoned US20030158975A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/368,066 US20030158975A1 (en) 2002-02-15 2003-02-18 Real-time data interface and method for browsers and the like

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US35732902P 2002-02-15 2002-02-15
US10/368,066 US20030158975A1 (en) 2002-02-15 2003-02-18 Real-time data interface and method for browsers and the like

Publications (1)

Publication Number Publication Date
US20030158975A1 true US20030158975A1 (en) 2003-08-21

Family

ID=27757598

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/368,084 Active 2025-05-07 US7225426B2 (en) 2002-02-15 2003-02-18 Dynamic objects with property slot definition and runtime mechanisms
US10/368,066 Abandoned US20030158975A1 (en) 2002-02-15 2003-02-18 Real-time data interface and method for browsers and the like
US10/485,848 Active 2025-12-09 US7822806B2 (en) 2002-02-15 2003-02-18 Real-time data interface and method for browsers and the like

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/368,084 Active 2025-05-07 US7225426B2 (en) 2002-02-15 2003-02-18 Dynamic objects with property slot definition and runtime mechanisms

Family Applications After (1)

Application Number Title Priority Date Filing Date
US10/485,848 Active 2025-12-09 US7822806B2 (en) 2002-02-15 2003-02-18 Real-time data interface and method for browsers and the like

Country Status (8)

Country Link
US (3) US7225426B2 (en)
EP (1) EP1474753B1 (en)
JP (1) JP2006504156A (en)
KR (1) KR20040096577A (en)
CN (2) CN1669020A (en)
AU (2) AU2003211125A1 (en)
CA (1) CA2475050A1 (en)
WO (2) WO2003071442A1 (en)

Cited By (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040199543A1 (en) * 2003-04-04 2004-10-07 Braud Luke A. Facilitating data manipulation in a browser-based user interface of an enterprise business application
US20040199541A1 (en) * 2003-04-04 2004-10-07 Goldberg Evan M. Concise communication of real-time business information in an enterprise network
US20060005207A1 (en) * 2004-06-25 2006-01-05 Louch John O Widget authoring and editing environment
US20060015818A1 (en) * 2004-06-25 2006-01-19 Chaudhri Imran A Unified interest layer for user interface
US20060047728A1 (en) * 2004-08-31 2006-03-02 International Business Machines Corporation Method and apparatus for updating a portal page
US20060085754A1 (en) * 2004-10-19 2006-04-20 International Business Machines Corporation System, apparatus and method of selecting graphical component types at runtime
US20060179118A1 (en) * 2005-01-12 2006-08-10 Vlad Stirbu Platform-specific application user interface remoting
WO2006096919A1 (en) * 2005-03-16 2006-09-21 Airscape Technology Pty. Limited Method for distributing computing between server and client
US20070043476A1 (en) * 2005-08-22 2007-02-22 Richards David M Dynamically extensible and automatically configurable building automation system and architecture
US20070055758A1 (en) * 2005-08-22 2007-03-08 Mccoy Sean M Building automation system data management
US20070055759A1 (en) * 2005-08-22 2007-03-08 Mccoy Sean M Building automation system data management
US20070055757A1 (en) * 2005-08-22 2007-03-08 Mairs Susan M Building automation system facilitating user customization
US20070055698A1 (en) * 2005-08-22 2007-03-08 Mccoy Sean M Building automation system data management
US20070061046A1 (en) * 2005-08-22 2007-03-15 Mairs Susan M Building automation system facilitating user customization
US20070067062A1 (en) * 2005-08-22 2007-03-22 Mairs Susan M Building automation system facilitating user customization
US20070130541A1 (en) * 2004-06-25 2007-06-07 Louch John O Synchronization of widgets and dashboards
US20070185065A1 (en) * 2006-02-03 2007-08-09 Vikramjit Chhokar Combination therapy for coronary artery disease
US20080004725A1 (en) * 2006-06-29 2008-01-03 Honeywell International Inc. Generic user interface system
US20080010049A1 (en) * 2006-06-29 2008-01-10 Honeywell International Inc. Graphical language compiler system
US20080009956A1 (en) * 2006-06-29 2008-01-10 Honeywell International Inc. Flexible resource rotation linking system
US20080016493A1 (en) * 2006-06-29 2008-01-17 Honeywell International Inc. System level function block engine
WO2008121410A1 (en) * 2007-03-29 2008-10-09 Ludi Labs, Inc. Interface definition for implementing contextual applications
US20080271127A1 (en) * 2007-04-24 2008-10-30 Business Objects, S.A. Apparatus and method for creating stand-alone business intelligence widgets within an authentication framework
US20090089668A1 (en) * 2007-09-28 2009-04-02 Yahoo! Inc. System and method of automatically sizing and adapting a widget to available space
US20090113037A1 (en) * 2007-10-24 2009-04-30 Honeywell International Inc. Interoperable network programmable controller generation system
US7681112B1 (en) 2003-05-30 2010-03-16 Adobe Systems Incorporated Embedded reuse meta information
US20100100829A1 (en) * 2008-10-16 2010-04-22 Honeywell International Inc. Wall module configuration tool
US7707514B2 (en) 2005-11-18 2010-04-27 Apple Inc. Management of user interface elements in a display environment
US7743336B2 (en) 2005-10-27 2010-06-22 Apple Inc. Widget security
US7752556B2 (en) 2005-10-27 2010-07-06 Apple Inc. Workflow widgets
US7761800B2 (en) 2004-06-25 2010-07-20 Apple Inc. Unified interest layer for user interface
US20100228805A1 (en) * 2009-02-23 2010-09-09 Mccoy Sean M Log collection data harvester for use in a building automation system
US7908391B1 (en) * 2008-03-25 2011-03-15 Symantec Corporation Application streaming and network file system optimization via feature popularity
US7917232B2 (en) 2005-08-22 2011-03-29 Trane International Inc. Building automation system data management
US7954064B2 (en) 2005-10-27 2011-05-31 Apple Inc. Multiple dashboards
US7970901B2 (en) 2004-07-12 2011-06-28 Netsuite, Inc. Phased rollout of version upgrades in web-based business information systems
US20110209085A1 (en) * 2002-08-01 2011-08-25 Apple Inc. Mode activated scrolling
US20110208803A1 (en) * 2010-02-23 2011-08-25 Mccoy Sean M Active device management for use in a building automation system
US20110213867A1 (en) * 2010-02-26 2011-09-01 Mccoy Sean Simultaneous connectivity and management across multiple building automation system networks
KR101105177B1 (en) 2004-02-19 2012-01-12 퀄컴 캠브리지 리미티드 Data container for user interface content data
US8140975B2 (en) 2005-01-07 2012-03-20 Apple Inc. Slide show navigation
US8156467B2 (en) 2007-08-27 2012-04-10 Adobe Systems Incorporated Reusing components in a running application
US8176466B2 (en) 2007-10-01 2012-05-08 Adobe Systems Incorporated System and method for generating an application fragment
US8196097B1 (en) * 2007-03-02 2012-06-05 Google Inc. Method and apparatus for extending a software gadget
US8239749B2 (en) 2004-06-25 2012-08-07 Apple Inc. Procedurally expressing graphic objects for web pages
US8302020B2 (en) 2004-06-25 2012-10-30 Apple Inc. Widget authoring and editing environment
US8453065B2 (en) 2004-06-25 2013-05-28 Apple Inc. Preview and installation of user interface elements in a display environment
US8538588B2 (en) 2011-02-28 2013-09-17 Honeywell International Inc. Method and apparatus for configuring scheduling on a wall module
US8543931B2 (en) 2005-06-07 2013-09-24 Apple Inc. Preview including theme based installation of user interface elements in a display environment
US8543824B2 (en) 2005-10-27 2013-09-24 Apple Inc. Safe distribution and use of content
US8656293B1 (en) 2008-07-29 2014-02-18 Adobe Systems Incorporated Configuring mobile devices
US8667415B2 (en) 2007-08-06 2014-03-04 Apple Inc. Web widgets
US20140208250A1 (en) * 2004-06-21 2014-07-24 Apple Inc. Methods and apparatuses for operating a data processing system
US8793022B2 (en) 2010-02-26 2014-07-29 Trane International, Inc. Automated air source and VAV box association
US8869027B2 (en) 2006-08-04 2014-10-21 Apple Inc. Management and generation of dashboards
US20150039981A1 (en) * 2013-08-01 2015-02-05 Raytheon Company Embedded system web server
US8954871B2 (en) 2007-07-18 2015-02-10 Apple Inc. User-centric widgets and dashboards
US20150095820A1 (en) * 2005-08-12 2015-04-02 Barry Fellman Service for generation of customizable display widgets
US9009313B2 (en) 2004-07-12 2015-04-14 NetSuite Inc. Simultaneous maintenance of multiple versions of a web-based business information system
US9104294B2 (en) 2005-10-27 2015-08-11 Apple Inc. Linked widgets
US9558278B2 (en) 2012-09-11 2017-01-31 Apple Inc. Integrated content recommendation
US9619304B2 (en) 2008-02-05 2017-04-11 Adobe Systems Incorporated Automatic connections between application components
US20170315706A1 (en) * 2016-04-27 2017-11-02 Rockwell Collins, Inc. Avionics Picture-in-Picture Display
US9920944B2 (en) 2015-03-19 2018-03-20 Honeywell International Inc. Wall module display modification and sharing
US10031660B2 (en) 2012-09-11 2018-07-24 Apple Inc. Media player playlist management
US10269235B2 (en) 2016-08-26 2019-04-23 Trane International Inc. System and method to assist building automation system end user based on alarm parameters
US10545639B1 (en) * 2014-09-29 2020-01-28 Rockwell Collins, Inc. Run-time widget creating system, device, and method
US10929497B2 (en) * 2013-08-23 2021-02-23 Huawei Device Co., Ltd. Replacing a web page while maintaining a communication link

Families Citing this family (74)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6981250B1 (en) * 2001-07-05 2005-12-27 Microsoft Corporation System and methods for providing versioning of software components in a computer programming language
US8001523B1 (en) * 2001-07-05 2011-08-16 Microsoft Corporation System and methods for implementing an explicit interface member in a computer programming language
US7987421B1 (en) 2002-01-30 2011-07-26 Boyd H Timothy Method and apparatus to dynamically provide web content resources in a portal
US7890639B1 (en) * 2002-01-30 2011-02-15 Novell, Inc. Method and apparatus for controlling access to portal content from outside the portal
WO2003071442A1 (en) 2002-02-15 2003-08-28 Tridium, Inc. Real-time data interface and method for browsers and the like
US7565647B2 (en) * 2002-03-22 2009-07-21 Sun Microsystems, Inc. Markup compiler that outputs MIDlets
US20030181196A1 (en) * 2002-03-22 2003-09-25 Eran Davidov Extensible framework for code generation from XML tags
US7512932B2 (en) 2002-03-22 2009-03-31 Sun Microsystems, Inc. Language and object model for describing MIDlets
US20030182626A1 (en) * 2002-03-22 2003-09-25 Eran Davidov On-demand creation of MIDlets
US7305671B2 (en) * 2002-03-22 2007-12-04 Sun Microsystems, Inc. Conversion of an object model to a source file generation model
US7246324B2 (en) * 2002-05-23 2007-07-17 Jpmorgan Chase Bank Method and system for data capture with hidden applets
US20040044755A1 (en) * 2002-08-27 2004-03-04 Chipman Timothy W. Method and system for a dynamic distributed object-oriented environment wherein object types and structures can change while running
CA2513498C (en) * 2003-01-22 2011-10-11 Nimcat Networks Inc. Call transfer system, method and network devices
US7392512B2 (en) * 2003-09-08 2008-06-24 Microsoft Corporation System and method for automatic conversion from WAP client provisioning XML represented objects to OMA DM tree structure represented objects
WO2005029382A2 (en) * 2003-09-19 2005-03-31 Lattix, Inc. Apparatus and method for managing design of a software system using dependency structure
US7480709B2 (en) * 2003-11-14 2009-01-20 Rockwell Automation Technologies, Inc. Dynamic browser-based industrial automation interface system and method
US7412367B1 (en) * 2003-11-17 2008-08-12 The Mathworks, Inc. Transparent subsystem links
US7324931B1 (en) * 2003-11-17 2008-01-29 The Mathworks, Inc. Conversion of model components into references
US20050125787A1 (en) * 2003-12-05 2005-06-09 Leonid Tertitski Convertible runtime graphical user interface
US7392295B2 (en) * 2004-02-19 2008-06-24 Microsoft Corporation Method and system for collecting information from computer systems based on a trusted relationship
US8875040B2 (en) * 2005-06-07 2014-10-28 Rockwell Automation Technologies, Inc. Universal web-based reprogramming method and system
US7926029B1 (en) * 2005-01-13 2011-04-12 21St Century Systems, Inc. System and method of progressive domain specialization product solutions
US7546582B2 (en) 2005-03-30 2009-06-09 International Business Machines Corporation Managing dynamic configuration data for producer components in a computer infrastructure
CA2619970C (en) * 2005-08-19 2013-03-26 Google Inc. Software architecture for displaying information content from plug-in modules in a user interface
US20070143673A1 (en) * 2005-12-20 2007-06-21 Microsoft Corporation Extensible architecture for chart styles and layouts
US20070182841A1 (en) * 2006-02-07 2007-08-09 Donnie Drake Image sensing microelectronic device with glass tilt control features, and various methods of making same
US20070257354A1 (en) * 2006-03-31 2007-11-08 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Code installation decisions for improving aggregate functionality
US8560840B2 (en) * 2006-10-23 2013-10-15 InMobi Pte Ltd. Method and system for authenticating a widget
US8839100B1 (en) * 2007-01-26 2014-09-16 The Mathworks, Inc. Updating information related to data set changes
WO2008131417A1 (en) * 2007-04-23 2008-10-30 Snac, Inc. Mobile widget dashboard
KR101415023B1 (en) * 2007-04-26 2014-07-04 삼성전자주식회사 Apparatus and method for providing information through network
US8578330B2 (en) * 2007-06-11 2013-11-05 Sap Ag Enhanced widget composition platform
US7418710B1 (en) 2007-10-05 2008-08-26 Kaspersky Lab, Zao Processing data objects based on object-oriented component infrastructure
US20090199205A1 (en) * 2008-02-06 2009-08-06 Honeywell International Inc. Configurable graphics virtual machine based display system
US8307300B1 (en) * 2008-05-13 2012-11-06 Google Inc. Content resizing and caching in multi-process browser architecture
US20100070881A1 (en) * 2008-09-12 2010-03-18 At&T Intellectual Property I, L.P. Project facilitation and collaboration application
JP5097070B2 (en) * 2008-09-24 2012-12-12 株式会社日立システムズ Property file reading system and method and program
US20100083219A1 (en) * 2008-10-01 2010-04-01 Microsoft Corporation Runtime Object Composition
US8762708B2 (en) 2008-10-11 2014-06-24 David L. Blankenbeckler Secure content distribution system
US8954488B2 (en) 2009-01-21 2015-02-10 Microsoft Corporation Extensibility for web based diagram visualization
US8495566B2 (en) * 2009-07-28 2013-07-23 International Business Machines Corporation Widget combos: a widget programming model
CN101655795B (en) * 2009-09-25 2012-10-10 金蝶软件(中国)有限公司 Method for creating service embodiment and system thereof
US20130275890A1 (en) * 2009-10-23 2013-10-17 Mark Caron Mobile widget dashboard
US8661408B2 (en) * 2009-11-23 2014-02-25 Michael James Psenka Integrated development environment and methods of using the same
US20110246913A1 (en) * 2010-03-30 2011-10-06 Microsoft Corporation Automated User Interface Generator
US20130019195A1 (en) * 2011-07-12 2013-01-17 Oracle International Corporation Aggregating multiple information sources (dashboard4life)
US9058401B2 (en) * 2011-08-16 2015-06-16 Fabebook, Inc. Aggregating plug-in requests for improved client performance
US10083247B2 (en) 2011-10-01 2018-09-25 Oracle International Corporation Generating state-driven role-based landing pages
US20130139073A1 (en) * 2011-11-09 2013-05-30 Revionics Inc. System and method for changing functionalities of websites using widgets
US8826158B1 (en) * 2011-12-14 2014-09-02 The United States Of America As Represented By The Director, National Security Agency Device for and method of determining changes to GUI
US8930886B2 (en) * 2011-12-15 2015-01-06 Microsoft Corporation Identifying application resources through implicit application models
CN103853534B (en) * 2012-11-30 2017-12-01 腾讯科技(深圳)有限公司 A kind of photo instant playback method and device
US11373191B2 (en) 2013-03-15 2022-06-28 Usgbc Systems, devices, components and methods for dynamically displaying performance scores associated with the performance of a building or structure
CN104346149A (en) * 2013-07-30 2015-02-11 商业对象软件有限公司 Descriptive framework used for data visualization
US10228837B2 (en) * 2014-01-24 2019-03-12 Honeywell International Inc. Dashboard framework for gadgets
US9274790B2 (en) * 2014-04-30 2016-03-01 Oracle International Corporation Customization manager
CN104298750B (en) * 2014-10-14 2018-02-23 北京国双科技有限公司 Renewal processing method and processing device for real-time system communication
US11108539B2 (en) * 2017-11-21 2021-08-31 Disney Enterprises, Inc. Techniques for analyzing and verifying time in machine-based networks
CA3054216C (en) 2018-09-05 2023-08-01 Honeywell International Inc. Methods and systems for improving infection control in a facility
CN109814778B (en) * 2018-12-24 2020-12-22 天津字节跳动科技有限公司 Method and device for realizing small program tab, electronic equipment and medium
US10978199B2 (en) 2019-01-11 2021-04-13 Honeywell International Inc. Methods and systems for improving infection control in a building
US11620594B2 (en) 2020-06-12 2023-04-04 Honeywell International Inc. Space utilization patterns for building optimization
US11914336B2 (en) 2020-06-15 2024-02-27 Honeywell International Inc. Platform agnostic systems and methods for building management systems
US11783652B2 (en) 2020-06-15 2023-10-10 Honeywell International Inc. Occupant health monitoring for buildings
US11783658B2 (en) 2020-06-15 2023-10-10 Honeywell International Inc. Methods and systems for maintaining a healthy building
US11823295B2 (en) 2020-06-19 2023-11-21 Honeywell International, Inc. Systems and methods for reducing risk of pathogen exposure within a space
US11184739B1 (en) 2020-06-19 2021-11-23 Honeywel International Inc. Using smart occupancy detection and control in buildings to reduce disease transmission
US11619414B2 (en) 2020-07-07 2023-04-04 Honeywell International Inc. System to profile, measure, enable and monitor building air quality
US11402113B2 (en) 2020-08-04 2022-08-02 Honeywell International Inc. Methods and systems for evaluating energy conservation and guest satisfaction in hotels
CN112130856B (en) * 2020-09-29 2023-11-03 重庆紫光华山智安科技有限公司 Strong-expansibility front-end visual interface generation method, system, medium and terminal
US11894145B2 (en) 2020-09-30 2024-02-06 Honeywell International Inc. Dashboard for tracking healthy building performance
US11372383B1 (en) 2021-02-26 2022-06-28 Honeywell International Inc. Healthy building dashboard facilitated by hierarchical model of building control assets
US11662115B2 (en) 2021-02-26 2023-05-30 Honeywell International Inc. Hierarchy model builder for building a hierarchical model of control assets
US11474489B1 (en) 2021-03-29 2022-10-18 Honeywell International Inc. Methods and systems for improving building performance

Family Cites Families (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4435764A (en) 1981-08-06 1984-03-06 Data General Corp. Computer network having a single electrically continuous bi-directional bus
US4747041A (en) 1983-06-27 1988-05-24 Unisys Corporation Automatic power control system which automatically activates and deactivates power to selected peripheral devices based upon system requirement
JPS6170654A (en) 1984-09-14 1986-04-11 Hitachi Ltd Resource control system of decentralized processing system
US4635195A (en) 1984-09-25 1987-01-06 Burroughs Corporation Power control network using reliable communications protocol
US4677566A (en) 1984-10-18 1987-06-30 Burroughs Corporation Power control network for multiple digital modules
FR2610120B1 (en) 1987-01-26 1989-07-13 Merlin Gerin CONTROL AND PROTECTION ASSEMBLY CONNECTING A LOCAL COMMUNICATION NETWORK TO AN INDUSTRIAL PROCESS
US5175852A (en) 1987-02-13 1992-12-29 International Business Machines Corporation Distributed file access structure lock
DE69108900D1 (en) 1990-01-30 1995-05-18 Johnson Service Co NETWORKED RESOURCE MANAGEMENT SYSTEM.
US5608870A (en) * 1992-11-06 1997-03-04 The President And Fellows Of Harvard College System for combining a plurality of requests referencing a common target address into a single combined request having a single reference to the target address
WO1997027553A1 (en) * 1996-01-29 1997-07-31 Futuretense, Inc. Distributed electronic publishing system
US5862052A (en) 1996-04-12 1999-01-19 Fisher-Rosemount Systems, Inc. Process control system using a control strategy implemented in a layered hierarchy of control modules
US5918233A (en) 1996-05-30 1999-06-29 The Foxboro Company Methods and systems for providing electronic documentation to users of industrial process control systems
US5982362A (en) 1996-05-30 1999-11-09 Control Technology Corporation Video interface architecture for programmable industrial control systems
US5786993A (en) 1996-06-14 1998-07-28 Landis & Gyr Technology Innovation Corp. Apparatus for and method of controlling and/or regulating process parameters of an installation
US6047222A (en) 1996-10-04 2000-04-04 Fisher Controls International, Inc. Process control network with redundant field devices and buses
JP2865136B2 (en) * 1996-11-11 1999-03-08 日本電気株式会社 Test consideration logic synthesis system
US5916306A (en) 1996-11-14 1999-06-29 Johnson Controls Technology Communication protocol for a router-based building automation and control network
US6262729B1 (en) * 1997-04-14 2001-07-17 Apple Computer, Inc. Method and apparatus for binding user interface objects to application objects
US6055562A (en) * 1997-05-01 2000-04-25 International Business Machines Corporation Dynamic mobile agents
US6266721B1 (en) 1997-05-13 2001-07-24 Micron Electronics, Inc. System architecture for remote access and control of environmental management
CA2306767C (en) 1997-10-13 2007-05-01 Rosemount Inc. Communication technique for field devices in industrial processes
US6067477A (en) 1998-01-15 2000-05-23 Eutech Cybernetics Pte Ltd. Method and apparatus for the creation of personalized supervisory and control data acquisition systems for the management and integration of real-time enterprise-wide applications and systems
US6356920B1 (en) 1998-03-09 2002-03-12 X-Aware, Inc Dynamic, hierarchical data exchange system
US6028998A (en) 1998-04-03 2000-02-22 Johnson Service Company Application framework for constructing building automation systems
US6119125A (en) 1998-04-03 2000-09-12 Johnson Controls Technology Company Software components for a building automation system based on a standard object superclass
US6185566B1 (en) 1998-05-05 2001-02-06 Robert A. Adams Network management system having an embedded network database
US6591305B2 (en) * 1998-06-30 2003-07-08 Sun Microsystems, Inc. Method and system for delivering data from a server object to a client object using a non-proprietary data transfer protocol
US6353853B1 (en) 1998-10-26 2002-03-05 Triatek, Inc. System for management of building automation systems through an HTML client program
US6411700B1 (en) * 1998-10-30 2002-06-25 Nec America, Inc. Telemanagement system with single point of entry
US6157943A (en) * 1998-11-12 2000-12-05 Johnson Controls Technology Company Internet access to a facility management system
US6728960B1 (en) * 1998-11-18 2004-04-27 Siebel Systems, Inc. Techniques for managing multiple threads in a browser environment
DE19853205A1 (en) * 1998-11-18 2000-06-15 Siemens Ag Process for controlling technical processes
US6636885B1 (en) * 1999-03-26 2003-10-21 Sun Microsystems, Inc. System using interface class in client computer to resolve references and retrieve delayed class applet from server
JP2000347866A (en) * 1999-06-04 2000-12-15 Nec Corp Decentralized system and unit and method for access control, and recording medium where program for access control is recorded
DE19933584A1 (en) * 1999-07-17 2001-01-18 Ibm Process for the compact presentation of information packets and their storage or transmission
US6681243B1 (en) * 1999-07-27 2004-01-20 Intel Corporation Network environment supporting mobile agents with permissioned access to resources
US6842906B1 (en) * 1999-08-31 2005-01-11 Accenture Llp System and method for a refreshable proxy pool in a communication services patterns environment
US7010503B1 (en) * 2000-03-10 2006-03-07 Ams Services, Inc. Traffic reduction in networked data collection
US20030221162A1 (en) 2000-03-20 2003-11-27 Sridhar Mandayam Andampillai Meta-templates in website development and methods therefor
US6922685B2 (en) * 2000-05-22 2005-07-26 Mci, Inc. Method and system for managing partitioned data resources
US6721777B1 (en) * 2000-05-24 2004-04-13 Sun Microsystems, Inc. Modular and portable deployment of a resource adapter in an application server
JP2001337823A (en) * 2000-05-25 2001-12-07 Sony Corp Componentware making method and storage medium
US7388831B2 (en) 2000-07-26 2008-06-17 Pluris, Inc. Method and apparatus for bond management according to hierarchy
KR100352549B1 (en) 2000-07-29 2002-09-12 주식회사 알티캐스트 Management method of contents data for digital broadcasting using application definition file and its system
US7080159B2 (en) * 2000-12-15 2006-07-18 Ntt Docomo, Inc. Method and system for effecting migration of application among heterogeneous devices
WO2003071442A1 (en) 2002-02-15 2003-08-28 Tridium, Inc. Real-time data interface and method for browsers and the like

Cited By (143)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110209085A1 (en) * 2002-08-01 2011-08-25 Apple Inc. Mode activated scrolling
US8327257B2 (en) 2003-04-04 2012-12-04 NetSuite Inc. Facilitating data manipulation in a browser-based user interface of an enterprise business application
US20100138734A1 (en) * 2003-04-04 2010-06-03 Netsuite, Inc. Facilitating data manipulation in a browser-based user interface of an enterprise business application
US8214239B2 (en) 2003-04-04 2012-07-03 Netsuite, Inc. Concise communication of real-time business information in an enterprise network
US8949705B2 (en) * 2003-04-04 2015-02-03 NetSuite Inc. Facilitating data manipulation in a browser-based user interface of an enterprise business application
US8195493B2 (en) 2003-04-04 2012-06-05 Netsuite, Inc. Concise communication of real-time business information in an enterprise network
US7685515B2 (en) * 2003-04-04 2010-03-23 Netsuite, Inc. Facilitating data manipulation in a browser-based user interface of an enterprise business application
US20130174019A1 (en) * 2003-04-04 2013-07-04 NetSuite Inc. Facilitating data manipulation in a browser-based user interface of an enterprise business application
US20040199543A1 (en) * 2003-04-04 2004-10-07 Braud Luke A. Facilitating data manipulation in a browser-based user interface of an enterprise business application
US7685010B2 (en) 2003-04-04 2010-03-23 Netsuite, Inc. Concise communication of real-time business information in an enterprise network
US8838465B2 (en) 2003-04-04 2014-09-16 NetSuite Inc. Concise communication of real-time business information in an enterprise network
US20100138263A1 (en) * 2003-04-04 2010-06-03 Netsuite, Inc. Concise communication of real-time business information in an enterprise network
US20040199541A1 (en) * 2003-04-04 2004-10-07 Goldberg Evan M. Concise communication of real-time business information in an enterprise network
US7681112B1 (en) 2003-05-30 2010-03-16 Adobe Systems Incorporated Embedded reuse meta information
KR101105177B1 (en) 2004-02-19 2012-01-12 퀄컴 캠브리지 리미티드 Data container for user interface content data
US9552141B2 (en) 2004-06-21 2017-01-24 Apple Inc. Methods and apparatuses for operating a data processing system
US9542081B2 (en) * 2004-06-21 2017-01-10 Apple Inc. Methods and apparatuses for operating a data processing system
US20140208250A1 (en) * 2004-06-21 2014-07-24 Apple Inc. Methods and apparatuses for operating a data processing system
EP2221710A3 (en) * 2004-06-25 2012-05-09 Apple Inc. Web view layer for accessing user interface elements
US7761800B2 (en) 2004-06-25 2010-07-20 Apple Inc. Unified interest layer for user interface
US10489040B2 (en) 2004-06-25 2019-11-26 Apple Inc. Visual characteristics of user interface elements in a unified interest layer
US10387549B2 (en) 2004-06-25 2019-08-20 Apple Inc. Procedurally expressing graphic objects for web pages
US8239749B2 (en) 2004-06-25 2012-08-07 Apple Inc. Procedurally expressing graphic objects for web pages
US9753627B2 (en) 2004-06-25 2017-09-05 Apple Inc. Visual characteristics of user interface elements in a unified interest layer
US20060005207A1 (en) * 2004-06-25 2006-01-05 Louch John O Widget authoring and editing environment
US8266538B2 (en) 2004-06-25 2012-09-11 Apple Inc. Remote access to layer and user interface elements
US7490295B2 (en) * 2004-06-25 2009-02-10 Apple Inc. Layer for accessing user interface elements
US8291332B2 (en) 2004-06-25 2012-10-16 Apple Inc. Layer for accessing user interface elements
US7503010B2 (en) * 2004-06-25 2009-03-10 Apple Inc. Remote access to layer and user interface elements
US20060015818A1 (en) * 2004-06-25 2006-01-19 Chaudhri Imran A Unified interest layer for user interface
US9507503B2 (en) 2004-06-25 2016-11-29 Apple Inc. Remote access to layer and user interface elements
US7530026B2 (en) * 2004-06-25 2009-05-05 Apple Inc. User interface element with auxiliary function
US7546543B2 (en) * 2004-06-25 2009-06-09 Apple Inc. Widget authoring and editing environment
US8302020B2 (en) 2004-06-25 2012-10-30 Apple Inc. Widget authoring and editing environment
US9477646B2 (en) 2004-06-25 2016-10-25 Apple Inc. Procedurally expressing graphic objects for web pages
US20070130541A1 (en) * 2004-06-25 2007-06-07 Louch John O Synchronization of widgets and dashboards
EP2284663A3 (en) * 2004-06-25 2012-11-07 Apple Inc. Unified interest layer for user interface
US20110239140A1 (en) * 2004-06-25 2011-09-29 Chaudhri Imran A Desktop Widgets for Presentation in a Layer
US8321801B2 (en) 2004-06-25 2012-11-27 Apple Inc. Desktop widgets for presentation in a layer
US8453065B2 (en) 2004-06-25 2013-05-28 Apple Inc. Preview and installation of user interface elements in a display environment
US8464172B2 (en) 2004-06-25 2013-06-11 Apple Inc. Configuration bar for launching layer for accessing user interface elements
US7984384B2 (en) 2004-06-25 2011-07-19 Apple Inc. Web view layer for accessing user interface elements
US20060156248A1 (en) * 2004-06-25 2006-07-13 Chaudhri Imran A Configuration bar for lauching layer for accessing user interface elements
EP2221711A3 (en) * 2004-06-25 2012-04-25 Apple Inc. Remote access to layer and user interface elements
US7793232B2 (en) * 2004-06-25 2010-09-07 Apple Inc. Unified interest layer for user interface
US7793222B2 (en) 2004-06-25 2010-09-07 Apple Inc. User interface element with auxiliary function
US8566732B2 (en) * 2004-06-25 2013-10-22 Apple Inc. Synchronization of widgets and dashboards
US7873910B2 (en) * 2004-06-25 2011-01-18 Apple Inc. Configuration bar for lauching layer for accessing user interface elements
US9009313B2 (en) 2004-07-12 2015-04-14 NetSuite Inc. Simultaneous maintenance of multiple versions of a web-based business information system
US8484346B2 (en) 2004-07-12 2013-07-09 NetSuite Inc. Simultaneous maintenance of multiple versions of a web-based business information system
US7970901B2 (en) 2004-07-12 2011-06-28 Netsuite, Inc. Phased rollout of version upgrades in web-based business information systems
US20060047728A1 (en) * 2004-08-31 2006-03-02 International Business Machines Corporation Method and apparatus for updating a portal page
US7500181B2 (en) 2004-08-31 2009-03-03 International Business Machines Corporation Method for updating a portal page
US20060085754A1 (en) * 2004-10-19 2006-04-20 International Business Machines Corporation System, apparatus and method of selecting graphical component types at runtime
US9471332B2 (en) * 2004-10-19 2016-10-18 International Business Machines Corporation Selecting graphical component types at runtime
US8140975B2 (en) 2005-01-07 2012-03-20 Apple Inc. Slide show navigation
US9384470B2 (en) 2005-01-07 2016-07-05 Apple Inc. Slide show navigation
US20060179118A1 (en) * 2005-01-12 2006-08-10 Vlad Stirbu Platform-specific application user interface remoting
AU2006225078B2 (en) * 2005-03-16 2008-11-06 Airscape Technology Pty. Limited Method for distributing computing between server and client
US20140115041A1 (en) * 2005-03-16 2014-04-24 Airscape Technology Pty. Limited Method for distributing computing between server and client
US8645461B2 (en) 2005-03-16 2014-02-04 Airscape Technology Pty. Limited Method for distributing computing between server and client
US9479614B2 (en) * 2005-03-16 2016-10-25 Airscape Technology Pty. Limited Method for distributing computing between server and client
CN101176079B (en) * 2005-03-16 2011-12-07 航空照片技术有限公司 Method for distributing computing between server and client
US8280947B2 (en) * 2005-03-16 2012-10-02 Airscape Technology Pty. Limited Method for distributing computing between server and client
WO2006096919A1 (en) * 2005-03-16 2006-09-21 Airscape Technology Pty. Limited Method for distributing computing between server and client
US20080189358A1 (en) * 2005-03-16 2008-08-07 Airscape Technology Pty. Limited Method for Distributing Computing Between Server and Client
US8543931B2 (en) 2005-06-07 2013-09-24 Apple Inc. Preview including theme based installation of user interface elements in a display environment
US20150095820A1 (en) * 2005-08-12 2015-04-02 Barry Fellman Service for generation of customizable display widgets
US7917232B2 (en) 2005-08-22 2011-03-29 Trane International Inc. Building automation system data management
US8055387B2 (en) 2005-08-22 2011-11-08 Trane International Inc. Building automation system data management
US7904186B2 (en) 2005-08-22 2011-03-08 Trane International, Inc. Building automation system facilitating user customization
US20070055759A1 (en) * 2005-08-22 2007-03-08 Mccoy Sean M Building automation system data management
US7870090B2 (en) 2005-08-22 2011-01-11 Trane International Inc. Building automation system date management
US20070055758A1 (en) * 2005-08-22 2007-03-08 Mccoy Sean M Building automation system data management
US20070061046A1 (en) * 2005-08-22 2007-03-15 Mairs Susan M Building automation system facilitating user customization
US20070043476A1 (en) * 2005-08-22 2007-02-22 Richards David M Dynamically extensible and automatically configurable building automation system and architecture
US20070055698A1 (en) * 2005-08-22 2007-03-08 Mccoy Sean M Building automation system data management
US20070067062A1 (en) * 2005-08-22 2007-03-22 Mairs Susan M Building automation system facilitating user customization
US8099178B2 (en) 2005-08-22 2012-01-17 Trane International Inc. Building automation system facilitating user customization
US20070055757A1 (en) * 2005-08-22 2007-03-08 Mairs Susan M Building automation system facilitating user customization
US8290627B2 (en) 2005-08-22 2012-10-16 Trane International Inc. Dynamically extensible and automatically configurable building automation system and architecture
US8024054B2 (en) 2005-08-22 2011-09-20 Trane International, Inc. Building automation system facilitating user customization
US8055386B2 (en) 2005-08-22 2011-11-08 Trane International Inc. Building automation system data management
US8050801B2 (en) 2005-08-22 2011-11-01 Trane International Inc. Dynamically extensible and automatically configurable building automation system and architecture
US9032318B2 (en) 2005-10-27 2015-05-12 Apple Inc. Widget security
US9104294B2 (en) 2005-10-27 2015-08-11 Apple Inc. Linked widgets
US9513930B2 (en) 2005-10-27 2016-12-06 Apple Inc. Workflow widgets
US7752556B2 (en) 2005-10-27 2010-07-06 Apple Inc. Workflow widgets
US7954064B2 (en) 2005-10-27 2011-05-31 Apple Inc. Multiple dashboards
US7743336B2 (en) 2005-10-27 2010-06-22 Apple Inc. Widget security
US8543824B2 (en) 2005-10-27 2013-09-24 Apple Inc. Safe distribution and use of content
US11150781B2 (en) 2005-10-27 2021-10-19 Apple Inc. Workflow widgets
US9417888B2 (en) 2005-11-18 2016-08-16 Apple Inc. Management of user interface elements in a display environment
US7707514B2 (en) 2005-11-18 2010-04-27 Apple Inc. Management of user interface elements in a display environment
US20070185065A1 (en) * 2006-02-03 2007-08-09 Vikramjit Chhokar Combination therapy for coronary artery disease
US8112162B2 (en) 2006-06-29 2012-02-07 Honeywell International Inc. System level function block engine
US20080004725A1 (en) * 2006-06-29 2008-01-03 Honeywell International Inc. Generic user interface system
US20080010049A1 (en) * 2006-06-29 2008-01-10 Honeywell International Inc. Graphical language compiler system
US8418128B2 (en) 2006-06-29 2013-04-09 Honeywell International Inc. Graphical language compiler system
US9726392B2 (en) 2006-06-29 2017-08-08 Honeywell International Inc. Generic user interface system
US7738972B2 (en) 2006-06-29 2010-06-15 Honeywell International Inc. Modular shared-memory resource stage driver system for flexible resource linking in an energy conversion system
US20080016493A1 (en) * 2006-06-29 2008-01-17 Honeywell International Inc. System level function block engine
US20080009956A1 (en) * 2006-06-29 2008-01-10 Honeywell International Inc. Flexible resource rotation linking system
US10495335B2 (en) 2006-06-29 2019-12-03 Honeywell International Inc. Generic user interface system
US8869027B2 (en) 2006-08-04 2014-10-21 Apple Inc. Management and generation of dashboards
US8196097B1 (en) * 2007-03-02 2012-06-05 Google Inc. Method and apparatus for extending a software gadget
WO2008121410A1 (en) * 2007-03-29 2008-10-09 Ludi Labs, Inc. Interface definition for implementing contextual applications
US20080271127A1 (en) * 2007-04-24 2008-10-30 Business Objects, S.A. Apparatus and method for creating stand-alone business intelligence widgets within an authentication framework
US9483164B2 (en) 2007-07-18 2016-11-01 Apple Inc. User-centric widgets and dashboards
US8954871B2 (en) 2007-07-18 2015-02-10 Apple Inc. User-centric widgets and dashboards
US8667415B2 (en) 2007-08-06 2014-03-04 Apple Inc. Web widgets
US8156467B2 (en) 2007-08-27 2012-04-10 Adobe Systems Incorporated Reusing components in a running application
US10176272B2 (en) * 2007-09-28 2019-01-08 Excalibur Ip, Llc System and method of automatically sizing and adapting a widget to available space
US20090089668A1 (en) * 2007-09-28 2009-04-02 Yahoo! Inc. System and method of automatically sizing and adapting a widget to available space
US8176466B2 (en) 2007-10-01 2012-05-08 Adobe Systems Incorporated System and method for generating an application fragment
US8650306B2 (en) 2007-10-24 2014-02-11 Honeywell International Inc. Interoperable network programmable controller generation system
US20090113037A1 (en) * 2007-10-24 2009-04-30 Honeywell International Inc. Interoperable network programmable controller generation system
US9619304B2 (en) 2008-02-05 2017-04-11 Adobe Systems Incorporated Automatic connections between application components
US7908391B1 (en) * 2008-03-25 2011-03-15 Symantec Corporation Application streaming and network file system optimization via feature popularity
US8656293B1 (en) 2008-07-29 2014-02-18 Adobe Systems Incorporated Configuring mobile devices
US9488992B2 (en) 2008-10-16 2016-11-08 Honeywell International Inc. Wall module configuration tool
US20100100829A1 (en) * 2008-10-16 2010-04-22 Honeywell International Inc. Wall module configuration tool
US8180824B2 (en) 2009-02-23 2012-05-15 Trane International, Inc. Log collection data harvester for use in a building automation system
US8635338B2 (en) 2009-02-23 2014-01-21 Trane International, Inc. Log collection data harvester for use in a building automation system
US20100228805A1 (en) * 2009-02-23 2010-09-09 Mccoy Sean M Log collection data harvester for use in a building automation system
US20110208803A1 (en) * 2010-02-23 2011-08-25 Mccoy Sean M Active device management for use in a building automation system
US9258201B2 (en) 2010-02-23 2016-02-09 Trane International Inc. Active device management for use in a building automation system
US9605859B2 (en) 2010-02-26 2017-03-28 Trane International Inc. Automated air source and VAV box association
US8793022B2 (en) 2010-02-26 2014-07-29 Trane International, Inc. Automated air source and VAV box association
US8219660B2 (en) 2010-02-26 2012-07-10 Trane International Inc. Simultaneous connectivity and management across multiple building automation system networks
US20110213867A1 (en) * 2010-02-26 2011-09-01 Mccoy Sean Simultaneous connectivity and management across multiple building automation system networks
US8925358B2 (en) 2011-02-28 2015-01-06 Honeywell International Inc. Methods and apparatus for configuring scheduling on a wall module
US8538588B2 (en) 2011-02-28 2013-09-17 Honeywell International Inc. Method and apparatus for configuring scheduling on a wall module
US10031660B2 (en) 2012-09-11 2018-07-24 Apple Inc. Media player playlist management
US9558278B2 (en) 2012-09-11 2017-01-31 Apple Inc. Integrated content recommendation
US9697299B2 (en) * 2013-08-01 2017-07-04 Raytheon Company Embedded system web server
US20150039981A1 (en) * 2013-08-01 2015-02-05 Raytheon Company Embedded system web server
US10929497B2 (en) * 2013-08-23 2021-02-23 Huawei Device Co., Ltd. Replacing a web page while maintaining a communication link
US10545639B1 (en) * 2014-09-29 2020-01-28 Rockwell Collins, Inc. Run-time widget creating system, device, and method
US9920944B2 (en) 2015-03-19 2018-03-20 Honeywell International Inc. Wall module display modification and sharing
US20170315706A1 (en) * 2016-04-27 2017-11-02 Rockwell Collins, Inc. Avionics Picture-in-Picture Display
US10684756B2 (en) * 2016-04-27 2020-06-16 Rockwell Collins, Inc. Avionics picture-in-picture display
US10269235B2 (en) 2016-08-26 2019-04-23 Trane International Inc. System and method to assist building automation system end user based on alarm parameters

Also Published As

Publication number Publication date
US7822806B2 (en) 2010-10-26
US20040215740A1 (en) 2004-10-28
JP2006504156A (en) 2006-02-02
WO2003071442A9 (en) 2003-10-16
WO2003071442A1 (en) 2003-08-28
KR20040096577A (en) 2004-11-16
CN1669020A (en) 2005-09-14
WO2003071444A1 (en) 2003-08-28
WO2003071444A9 (en) 2003-10-16
CN101719056A (en) 2010-06-02
US7225426B2 (en) 2007-05-29
EP1474753A4 (en) 2009-12-09
EP1474753B1 (en) 2018-08-22
AU2003211126A1 (en) 2003-09-09
AU2003211125A1 (en) 2003-09-09
US20030159129A1 (en) 2003-08-21
CA2475050A1 (en) 2003-08-28
CN101719056B (en) 2016-01-27
EP1474753A1 (en) 2004-11-10

Similar Documents

Publication Publication Date Title
US7822806B2 (en) Real-time data interface and method for browsers and the like
CN110442816B (en) Method and device for configuring web form and computer readable storage medium
EP1388783B1 (en) Method and computer system for handling incremental data in client-server communication
EP1296233A2 (en) Web page authoring tool
US10685155B2 (en) Method and system for designing a distributed heterogeneous computing and control system
US20040119713A1 (en) Interactive and web-based Gantt Chart
US20090265705A1 (en) System and method for developing and deploying computer applications over a network
CN108614776A (en) Across the dynamic fixing method and system of language protocol test request
US7966427B2 (en) Proxy object configuration of industrial component
US7962659B2 (en) Interoperably configurable HMI system and method
US11822870B2 (en) Customizable user interface layouts
US9805017B2 (en) Spreadsheet to webpage conversion system and method
CN104021016B (en) Method and browser for loading browser plug-in icons
US20160012145A1 (en) Client-Side Template Engine and Method for Constructing a Nested DOM Module for a Website
EP1488344A2 (en) Document transformation
WO2016005886A2 (en) Self-referencing of running script elements in asychronously loaded dom modules
CN115994517A (en) Information processing method, apparatus, storage medium, device, and program product
US20160012146A1 (en) Client Web Browser and Method for Constructing a Website DOM Module With Client-Side Functional Code
US20080189537A1 (en) HMI configuration with limited interoperability
US20230247115A1 (en) Protocol driver creating device
Sundar et al. Content Management System and Automation of Model Cloning Scalable EAV Model in GNEISYS Framework
Verzani gWidgetsWWW: Creating Interactive Web Pages within R
CN116149653A (en) Method and device for constructing list page, storage medium and computer equipment
CN115686692A (en) Rendering method and system of desktop component, electronic device and storage medium
US20090198771A1 (en) Client device and server device

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: EXPRESSLY ABANDONED -- DURING EXAMINATION