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

Tracker: visualization framework and per-problem visualizations

Open
  • Is something wrong?
#294 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
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

This is a tracker for existing visualization issues, not a request to implement a specific change. Read the linked issues #14 and #33 first to understand the proposed shared-component approaches, then review the suggested dependency order; the tracker is done when the existing work is grouped and ordered as described, with no new scope or closures.

Written by the indexing model from the issue text.

Description

tracker

Summary

Two issues propose shared visualization infrastructure; the other five are features and bugs that get materially easier once either one exists.

Why these are grouped

#14 (a universal SVG element for graph problems, with meaningful node/link attributes instead of per-controller attributes) and #33 (a generic boolean-formula visualizer covering SAT, HornSAT, 2SAT and other propositional problems) are the same idea applied to the two dominant problem shapes: build one visualizer instead of one per problem.

Everything else here is downstream of that choice. #41 (node positions reset when highlight-solution is toggled) and #38 (highlighted nodes in the 3SAT formula do not correspond to the highlighted clique nodes) are both state-handling bugs that a shared component would fix once rather than per visualization. #49 (side-by-side comparison of two algorithms' solutions) is only tractable if visualizations are composable. #36 (show-solution renders nothing when there is no solution, instead of saying so) is a shared empty-state. #31 (Knapsack) is a new visualization that should be built on whatever framework this settles, not before it.

Suggested order

  1. decide the shared-component approach: #14 and #33
  2. #36 — shared empty state
  3. #41 + #38 — highlight/position state bugs in the shared component
  4. #31 — new visualization on the settled framework
  5. #49 — side-by-side, once visualizations compose

Related (not re-parented)

Opened by other contributors, so linked for context only — their state is unchanged:

  • #14 — Universal Visualization for Graph Problems (@Andrija-Sevaljevic)
  • #33 — Generic Boolean formula visualizer (@norkish)
  • #31 — Add Knapsack Visualization (@norkish)
  • #41 — Fix visualization resetting node positions when turning on highlight solution (@Jetison333)
  • #49 — Side by side visualization of two solution to the same problem? (i.e., different algorithms) (@norkish)
  • #36 — Show solution doesn't show anything if there is no solution (@norkish)
  • #38 — Highlighted solution in 3SAT to Clique Reduction unclear (@norkish)

[!NOTE]
No sub-issues attached: every issue in this cluster was opened by @Andrija-Sevaljevic, @norkish or @Jetison333, so they are cross-linked for context only and their state is unchanged.

Issue Handling

Umbrella/tracker issue grouping existing work; no new scope is introduced here. Nothing is closed by this issue directly.

Dominant language
JavaScript
Stars
3
Forks
18
Avg merge
1d 3h
Merged PRs (30d)
35

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.