Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Tracker: visualization redesign — Redux_GUI renderers

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, react

Research direction

This is a tracker spanning issues #352, #353, #368, #369, and #377, not a standalone implementation task. Start with Documentation/Visualizations/README.md and the mockups in Documentation/Visualizations/mockups/; then use the listed component files and the relevant sub-issue to identify a scoped task. Done is defined by completing a tracker item with its stated dependencies and mockup contract.

Written by the indexing model from the issue text.

Description

tracker

Tracks Redux_GUI's side of the visualization redesign. Backend work: ReduxISU/Redux#655. Redux_Frontend has its own tracker (ReduxISU/Redux_Frontend#198); the two sites are alternatives and are built separately.

Phases

Overall: not started. Redux PR 1 and PR 2 are merged, so the foundation (A) is unblocked; no Redux picture-type PR has merged yet, so no renderer can merge yet.
Last updated: 2026-10-14

Status key: ✅ merged · 🔄 PR open/in review · 🏠 done locally, PR pending · ⏳ not started · 🚧 in progress

Phase Issue What Status Note
A #352 Rendering foundation: state styles, layout rules, solver choice, per-type fallback ⏳ not started Unblocked: ReduxISU/Redux#733 merged Oct 13
B #353 Renderers for the 15 picture types ⏳ not started 0 of 15 (Search Tree #370 moved here from D). Redux has built all its picture types locally, 0 merged (Graph slice 1 is ReduxISU/Redux#746)
C #368 Reduction view ⏳ not started Redux PR 5 (ReduxISU/Redux#660): 2 PRs open, the rest local
D #369 Renderers for the 6 future picture types ⏳ not started 0 of 6. Redux PR 7 not started
E #377 Retire TikZ and the old graph renderer ⏳ not started #291 and #270 close with it

Implementation guide: Documentation/Visualizations/README.md in Redux (docs PR to follow). The mockups that act as the spec are in Documentation/Visualizations/mockups/ — open design.html (one tab per picture type) and redux-gui.html in a browser; each tab lists its input contract and open review questions.

PR Issue What Depends on
A #352 Rendering foundation: state styles, layout rules, solver choice, per-type fallback Redux PR 1 for the solver parameter
B #353 Renderers for the 15 picture types A; each renderer needs its Redux picture-type PR (sub-issue of ReduxISU/Redux#658) merged
C #368 Reduction view A, B (Graph); Redux PR 5
D #369 Renderers for the 6 future picture types A; Redux PR 7
E #377 Retire TikZ and the old graph renderer B (Graph, Automaton)

Rollout: one picture type at a time. Redux keeps its old flat-list visualize response as the default while types migrate, and the foundation PR (A) adds a per-type fallback: a type with a new renderer draws from format=frames, every other type keeps its old renderer. So each renderer PR can merge any time after its Redux picture-type PR, in any order, with no coordinated cross-repo merges. Redux removes the old response in ReduxISU/Redux#732 once every type is ported here and in the other frontend.

Key files: components/pageblocks/VisualizeRowReact.js (controls), components/widgets/VisualizationLogic.js (renderer choice), components/Visualization/svgs/Visualizations.js (registry), components/Visualization/ReducedVisualization.js and components/redux/index.js (reductions).

Dominant language
JavaScript
Stars
3
Forks
18
Avg merge
22h 57m
Merged PRs (30d)
37

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from ReduxISU/Redux_GUI

All issues in ReduxISU/Redux_GUI

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.