pbakaus/scroller

Accelerated panning and zooming for HTML and Canvas

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 17th, 2026
Created on September 13th, 2011
Open Issues & Pull Requests: 38 (+0)
GitHub issues: Enabled
Number of forks: 420
Total Stargazers: 3,914 (+0)
Total Subscribers: 87 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Scroller is a pure logic component for accelerated panning and zooming that works independently of any rendering system or event handler.

The tool solves the problem of implementing smooth, performant scrolling and zooming interactions by providing a rendering-agnostic library that handles all the physics and state management. It accepts scroll and zoom events, applies configurable behaviors like deceleration, bouncing, and snapping, and invokes a callback with the new scroll position and zoom level for the application to render. This separation of logic from rendering means the same component can drive DOM elements, Canvas, WebGL, or any other rendering target, on both mouse and touch devices.

Scroller suits projects that need fine-grained control over scrolling behavior or must support multiple rendering backends. The core API requires manual event wiring and rendering, making it appropriate for developers building custom scroll experiences or integrating into larger frameworks. For simpler use cases, the project provides EasyScroller, a higher-level wrapper that automatically initializes on DOM elements marked with data attributes and handles rendering directly, eliminating the need to write callback logic. The README does not compare the tool to other scrolling libraries.

The project shows sparse recent activity with infrequent commits and minimal engagement on issues and pull requests. Documentation is limited to the README and inline code comments, with no dedicated guides or API reference beyond what the README provides. The codebase remains small and focused, with no evidence of active feature development or maintenance cycles.