Critique your plugin #2 — Obsidian October 2024

Timeline View for Obsidian turns notes into a navigable timeline by plotting them according to the value of a chosen frontmatter property. It’s built to feel native—matching familiar navigation controls and configuration patterns from Obsidian’s core graph view—while keeping the scope focused on one job: presenting notes along a time axis. That combination makes it promising for anyone who wants quick visual browsing of dated notes, release logs, or project milestones.

In day-to-day use, the plugin’s biggest practical weakness shows up on high-density displays and trackpads. On a MacBook Pro Retina display, the timeline rendering looks blurry because the plugin draws its content to a fixed-size HTML canvas that doesn’t scale to the screen’s pixel density. Input handling also appears incomplete: two-finger scrolling on a Magic Trackpad barely advances the timeline, and horizontal scrolling doesn’t work unless the user holds Shift. Small UI inconsistencies add friction too—missing horizontal padding in the navigation bar and hover effects that don’t match native Obsidian buttons.

The critique then shifts from user experience to implementation details. Using Obsidian developer tools, the canvas issue is traced to a canvas element rendered at a fixed pixel size (effectively using “virtual pixels” that don’t match the display). A CSS scaling approach could correct the blur, but it would require changes in how the canvas is created and scaled. Navigation alignment can be improved by adjusting CSS positioning for the timeline controls container, and tooltip placement can be influenced via a data attribute that the tooltip library reads.

Code review highlights mostly solid plugin lifecycle hygiene inside the main onload function: settings tab registration, ribbon icon and command registration, custom view registration, and event wiring are generally structured in ways that should load reliably. One notable bug risk appears in the editor menu event handler—an event reference returned from an on() call isn’t properly unloaded, which could leave a lingering listener after the plugin is disabled. Performance is also checked using Obsidian’s “notify if startup takes longer than expected” feature; the timeline view reports loading in about 17 milliseconds in the reviewer’s test.

A deeper design point centers on Obsidian’s navigation flag for custom views. Timeline View’s leaf is treated as not eligible for navigation when users click notes, which causes clicks to open new tabs instead of replacing the existing timeline view. The critique argues that, when a view belongs in the main workspace split, setting navigation to true is usually the more consistent convention—especially because it affects how workspace link previews, status bar updates, and file-open events propagate.

Finally, a demo with Obsidian release notes shows the plugin’s potential: notes grouped and plotted by release date and version. The demo initially fails because the “published” frontmatter value is stored as a string, so the plugin’s property-to-number conversion needs to parse dates. Converting valid date strings into Unix timestamps fixes the timeline distribution. Notes missing the chosen property become outliers, and the critique suggests ignoring such notes would be a valuable future feature. After cleanup, the timeline zooms to fit cleanly and groups releases by major version (1.5, 1.6, 1.7), demonstrating the plugin’s core value when its data mapping is correct.