Spreadsheet cell dependency management
First Claim
Patent Images
1. A computer-implemented method comprising:
- receiving a spreadsheet file and a separate dashboard structure file comprising metadata characterizing a dashboard;
rendering, using the spreadsheet file and the dashboard structure file, the dashboard, wherein the rendered dashboard includes a plurality of visual components, and wherein one or more of the plurality of visual components are adapted to provide visual representations of at least a portion of data from the spreadsheet file;
analyzing the spreadsheet file and the dashboard structure file to determine at least one dependency between one or more cells in the spreadsheet file and a first visual component comprising the rendered dashboard;
registering, for the at least one dependency, an event listener, wherein the event listener is paired with an event source comprising the one or more cells in the spreadsheet file, wherein the first visual component comprises a dependent component and the one or more cells comprise a dependee of the at least one dependency, and wherein the event listener is notified of an event from the event source when the dependee is changed;
notifying the event source that data is required for updating the dependent component in response to an event notification received at the event listener, wherein the first visual component is configured to continue a flow of execution independently of the event listener such that a second visual component is rendered while the event source schedules fetching of the data used to update the dependent component; and
rendering, within the dashboard, the first visual component comprising the dependent component upon the event listener receiving notification that the event source has finished fetching the data required to update the dependent component.
1 Assignment
0 Petitions
Accused Products
Abstract
A spreadsheet file and a dashboard structure file characterizing a dashboard are received. These files are then analyzed to determine dependencies. Subsequently, for each determined dependency, an event listener is registered for a dependent component that corresponds to the determined dependency. These event listeners are notified of an event from an event source when a corresponding dependee is changed. Dependent components are then updated using data from a corresponding dependee in response to event notifications so that each updated dependent component can be rendered within the dashboard. Related apparatus, systems, techniques and articles are also described.
-
Citations
17 Claims
-
1. A computer-implemented method comprising:
-
receiving a spreadsheet file and a separate dashboard structure file comprising metadata characterizing a dashboard; rendering, using the spreadsheet file and the dashboard structure file, the dashboard, wherein the rendered dashboard includes a plurality of visual components, and wherein one or more of the plurality of visual components are adapted to provide visual representations of at least a portion of data from the spreadsheet file; analyzing the spreadsheet file and the dashboard structure file to determine at least one dependency between one or more cells in the spreadsheet file and a first visual component comprising the rendered dashboard; registering, for the at least one dependency, an event listener, wherein the event listener is paired with an event source comprising the one or more cells in the spreadsheet file, wherein the first visual component comprises a dependent component and the one or more cells comprise a dependee of the at least one dependency, and wherein the event listener is notified of an event from the event source when the dependee is changed; notifying the event source that data is required for updating the dependent component in response to an event notification received at the event listener, wherein the first visual component is configured to continue a flow of execution independently of the event listener such that a second visual component is rendered while the event source schedules fetching of the data used to update the dependent component; and rendering, within the dashboard, the first visual component comprising the dependent component upon the event listener receiving notification that the event source has finished fetching the data required to update the dependent component. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A non-transitory computer program product storing instructions, which when executed by at least one data processor of at least one computer system, result in operations comprising:
-
receiving a spreadsheet file and a separate dashboard structure file comprising metadata characterizing a dashboard; rendering, using the spreadsheet file and the dashboard structure file, the dashboard, wherein the rendered dashboard includes a plurality of visual components, and wherein one or more of the plurality of visual components are adapted to provide visual representations of at least a portion of data from the spreadsheet file; analyzing the spreadsheet file and the dashboard structure file to determine at least one dependency between one or more cells in the spreadsheet file and a first visual component comprising the rendered dashboard; registering, for the at least one dependency, an event listener, wherein the event listener is paired with an event source comprising the one or more cells in the spreadsheet file, wherein the first visual component comprises a dependent component and the one or more cells comprise a dependee of the at least one dependency, and wherein the event listener is notified of an event from the event source when the dependee is changed; notifying the event source that data is required for updating the dependent component in response to an event notification received at the event listener, wherein the first visual component is configured to continue a flow of execution independently of the event listener such that a second visual component is rendered while the event source schedules fetching of the data used to update the dependent component; and rendering, within the dashboard, the first visual component comprising the dependent component upon the event listener receiving notification that the event source has finished fetching the data required to update the dependent component. - View Dependent Claims (14, 15, 16)
-
-
17. A system comprising:
-
a client computing system comprising memory and at least one data processor; and a server computing system remote from the client computing system comprising memory and at least one data processor; wherein; the client computing system receives a spreadsheet file and a separate dashboard structure file comprising metadata characterizing a dashboard from the server computing system; the client computing system renders, using the spreadsheet file and the dashboard structure file, the dashboard, wherein the rendered dashboard includes a plurality of visual components, and wherein one or more of the plurality of visual components are adapted to provide visual representations of at least a portion of data from the spreadsheet file; the client computing system analyzes the spreadsheet file and the dashboard structure file to determine at least one dependency between one or more cells in the spreadsheet file and a first visual component comprising the rendered dashboard; the client computing system registers, for the at least one dependency, an event listener, wherein the event listener is paired with an event source comprising the one or more cells in the spreadsheet file, wherein the first visual component comprises a dependent component and the one or more cells comprise a dependee of the at least one dependency, and wherein the event listener is notified of an event from the event source when the dependee is changed; the client computing system notifies the event source that data required for updating the dependent component in response to an event notification received at the event listener, wherein the first visual component is configured to continue a flow of execution independently of the event listener such that a second visual component is rendered while the event source schedules fetching of the data used to update the dependent component; and the client computing system renders, within the dashboard, the first visual component comprising the dependent component upon the event listener receiving notification that the event source has finished fetching the data required to update the dependent component.
-
Specification