tree: 24e418b0cc55906eef20cf230f0d5adb0db277ac [path history] [tgz]
  1. .gitignore
  2. Makefile
  4. autoroll-widget-sk-demo.html
  5. autoroll-widget-sk.html
  6. capacity-stats-sk-demo.html
  7. capacity-stats-sk.html
  8. commit-popup-sk-demo.html
  9. commit-popup-sk.html
  10. commits-canvas-sk-demo.html
  11. commits-canvas-sk.html
  12. commits-data-sk.html
  13. commits-table-d3-sk.html
  14. commits-table-d3.css
  15. commits-table-sk.html
  16. fuzzer-widget-sk-demo.html
  17. fuzzer-widget-sk.html
  19. gold-status-sk-demo.html
  20. gold-status-sk.html
  21. perf-status-sk.html
  22. status-menu-section-sk.html
  23. status-popup.html
  24. status-sk-demo.html
  25. status-sk.html
  26. task-popup-sk-demo.html
  27. task-popup-sk.html
  28. taskspec-popup-sk-demo.html
  29. taskspec-popup-sk.html
  30. tree-status-sk.html

Status Elements

Before being able to run the demo pages, run the

make web

in the infra/status directory.

To run the demo pages, navigate to this directory and run

make run

This will download the necessary dependencies, download the demo data from Google Storage and set up a local server for debugging on http://localhost:8080.

The general idea for many of these elements is to have a *-data element that fetches the data needed for rendering, parses and formats it, and then makes it available via data bindings. There are then UI elements that takes the data and renders it. The UI elements may have user-operable widgets, the output of which are exposed for databinding as well. This helps break apart the components and makes it easier to, for example, change from using Polymer to using D3 for a component of the visualization.

For performance reasons, the drawing of the main table on status (commits-table-sk) is done with D3. An excellent primer on D3 is Interactive Data Visualization for the Web by Scott Murray.

The elements were previously written in Polymer 0.5. Many of these were deleted after commit 9b8bb9c04.