Skip to main content

Missing an API? Found a bug?

Got an idea for Rootless? This is the place for you to vote, discuss and share it.

I read every one of these :)

  • If you're requesting a feature, be as specific as you can: tell us what you're trying to do and why it would help, not just the feature itself. Understanding the underlying problem helps me.

  • If you're reporting a bug, the fastest way to get it fixed is a minimal reproducible example: the shortest sequence of steps that brings the problem back, starting from a clean state. Please include:

    1. what you expected to happen, and what happened instead;

    2. the exact steps to reproduce it, numbered;

    3. your Rootless version and operating system;

    4. any error messages, screenshots, or screen recordings

If the bug only shows up with certain data or a specific file, attach the smallest version that still triggers it.

What doesn't belong here: personal data, credentials, anything that is not meant for the public

In Progress

Widget timelines

today a script produces one widget state, so anything that changes over time (a clock, a flip clock, a countdown drawn as graphics) is frozen until the next reload, and reloads are budgeted (circa 40-70/day per widget and iOS decides when). States inside one timeline cost nothing: one run that draws the next 60 minutes is one reload, and iOS shows each state at its time. It enables time-based parameters for any graphic, expanding beyond what Text.timer could previously display. Limits to eventually keep in mind: precision is minute wise, not seconds memory: N trees within the extension's 30 MB. Maybe cap the count (60–180?) and fail clearly beyond it run time: the whole timeline is built in one run, inside the 8s budget

Edoardo Balducci4 hours ago
High Priority