Add support for progress widgets

[mattpap]

From examples/models/widgets.py:

Screencast.from.2025-02-17.13-47-33.webm

fixes #6556

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.59%. Comparing base (17b0187) to head (7dd98f7).
Report is 203 commits behind head on branch-3.6.

Additional details and impacted files

@@              Coverage Diff               @@
##           branch-3.6   #13546      +/-   ##
==============================================
+ Coverage       92.58%   92.59%   +0.01%     
==============================================
  Files             325      326       +1     
  Lines           20729    20763      +34     
==============================================
+ Hits            19192    19226      +34     
  Misses           1537     1537              

[mattpap]

This is tentatively ready. I will still need to add some tests.

[bryevdv]

FWIW I like the look of the Vue progress bar better, where the entire bar is the same shade, but "washed out" where it is not yet reached. Maybe that is just something to be done with CSS though.

[mattpap]

FWIW I like the look of the Vue progress bar better, where the entire bar is the same shade, but "washed out" where it is not yet reached. Maybe that is just something to be done with CSS though.

This is configurable in CSS, but I would leave such discussions for later for CZI theming and the designer. We will work on all components as whole and not just tweaking individual ones.

[mattpap]

One thing I don't like about this design is that there is no distinction between an active and inactive (not started, paused, finished) progress component, e.g. so that an active progress could have animations and inactive doesn't (for indication that something is happening or not, but also for performance; CSS animations are very heavy on the CPU).

[mattpap]

Added a user guide documentation entry for the new component.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.