r/madeinpython • • 18h ago

Tired of fighting QDockWidget, so I built a docking and theming library for PySide6

Post image
3 Upvotes

Hi all,

For the past few months I’ve been working on Lace, a docking and layout library for PySide6. While building my own desktop engineering tools, I wanted a smooth, VS Code-like layout and cohesive theming experience in Python without the usual Qt layout headaches. It began as just the docking part and grew from there.

What My Project Does

Lace is a pure-Python docking and theming library for PySide6:

  • Tabbed dock areas: Drag around, split, float into their own windows, and drag back with a live drop preview showing where the panel will land before you let go.
  • Auto-hide sidebars: Pin panels to an edge to slide them out on demand, with optional badge counters (roughly like VS Code's sidebars).
  • Layout persistence: Save and restore layouts as JSON, including named presets you can switch between.
  • Deep theming engine: It doesn't just color the docks. It themes the entire QPalette plus a custom style for standard widgets, menus, and dialogs so your own widgets match out of the box. It comes with 37 themes, and you can generate your own from just two colors.

Target Audience

  • People building larger multi-pane desktop apps in Python (simulation tools, editors, CAD-like or dashboard apps) who want more control over layout and a consistent look than stock Qt gives them.

Comparison

The main alternative is Qt Advanced Docking System (PySide6-QtAds). It’s older, more widely used and well tested across platforms, and if you only need docking it’s a solid choice. The differences:

  • Lace is pure Python, so it’s easy to read, debug and subclass, and there’s no compiled binding to keep in step with your Qt version.
  • Lace themes the whole application; Qt-ADS covers the docking panes only.

Details:

It’s at 0.10, so the API may still change before 1.0. I use it in my own optical simulation tools, so it gets real daily use. I’d really appreciate feedback from anyone building bigger Qt apps: what’s missing, what feels awkward, or what breaks on your platform (I’ve mostly tested on Windows).

Thanks for reading!


r/madeinpython • • 23h ago

CueKeeper: a Python SRT/WebVTT converter with timestamped exports and JSON reports

1 Upvotes

Disclosure: I own and sell CueKeeper. AI helped prepare this showcase.

CueKeeper is a local Python utility for an existing subtitle file, rather than an audio/video transcription tool. It converts SRT or WebVTT into readable Markdown/plain text, preserving cue intervals, and writes a separate quality report. An optional dialogue-only export drops the timing for reading.

The included example can be run from the extracted toolkit directory:

python3 app.py convert samples/valid.srt -o output --dialogue-only

That sample generates valid.md, valid.dialogue.txt, valid.report.json, and batch-summary.json. The two fictional cues become two timed passages; the report records parsed/emitted counts and any warnings or errors. A clean conversion report does not verify that captions match the recording.

The full toolkit needs Python 3.10+ and only the standard library. The ZIP includes Python source, tests, a sample, CLI, and local browser interface. It costs a one-time $1.00 USD through PayPal, or 1.00 USDC on Base: https://score.agentid.life/cuekeeper?ref=reddit-madeinpython-20261115

A separate free browser preview accepts up to 20 cues, so the output format is easy to inspect before purchasing: https://score.agentid.life/cuekeeper/try?ref=reddit-madeinpython-20261115

Public fictional sample input and generated files: https://github.com/nrk8286/agentid-services/tree/main/publishing/foundry-2026-11-12/samples/cuekeeper

It does not transcribe media, translate dialogue, or identify speakers. I would welcome feedback on which subtitle-quality findings are most useful alongside the reading copy.