whitesmith / whitesmith/rubycritic

Animation over time

Open
#212 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion feature
Dominant language
Ruby
Stars
3.5k
Forks
234
PR merge metrics
No merged PRs in 30d

Description

It's kind of a question if it's even possible, but I was thinking that with an awesome presentation as it is now, would it be possible to animate it over time ?

I'm not 100% sure how would be the best way to do it, but I was thinking that:

  • over a range of let's say 1000 commits
  • jump every 100 commits
  • gather the stats (perhaps churn could be optimized - running from the oldest to the newest and for all but the first step run for the 100 commits and add them)
  • show on the UI with some animation - well chart mostly, but the the score perhaps as well. Perhaps leaving track of the movement on the chart.

I got the idea from a nice TED talk:
https://www.ted.com/talks/hans_rosling_shows_the_best_stats_you_ve_ever_seen

I know it's a kind of pie in the sky, but I was wondering about feasibility & feedback :)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points; begin by locating the existing presentation UI and the code that gathers commit-range statistics. Clarify the animation scope and commit-step behavior, then define completion around displaying the requested time sequence and chart movement.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
data-visualization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.