Bike 2.0 (Preview 218)

[jessegrosjean]

• Added bike.showAlert API
• Added window.presentSheet (domScript permission) API
• Added window.inspector.addItem (domScript permission) API
• Added URL open method and other URL (openURL permission) API
• Added type parameters to clipboard API
• Improved zoom animations when filtering
• Show selected rows at full scale when filtering
• Moved bike provided extension code from @Startup to @Bike
• Fixed console.log output to show in Safari inspector
• Fixed sidebar clicks to work when multiple windows open

New release! Big effort this time around is giving extensions the ability to display their own UI in WebViews. Along the way I also managed to reorganize a bunch of things.

Download:

• Downloads

[jessegrosjean]

Notes

Quite a few changes to extensions in this release. I don’t think that I’ve broken much (any?) API, but I have added a bunch of things and make some structure changes.

The big structure change is that now the @Bike folder (in the extensions folder) is itself an extension. So it contains both API type documentation and extension code that ships with Bike. It is always loaded first. The idea is that things such as “sidebar headings item” that I want in a default Bike install will be added to this folder. It gets replaced on each launch, so the number of default additions can grow over time.

To go with that change the default @Startup extension now does nothing. It’s where you can add your own experiments, but doesn’t contain default behavior.

---

The next big changes is that extensions can now define their own views using web APIs. There are two places where they can do this: 1) window.inspector.addItem and 2) window.presentSheet. In future I will probably add other places.

It’s a bit complex because Bike extensions run in a headless javascript context… not associated Webview or DOM/HTML. To display custom views your extension will need to load a specified Dom script into a web view hosted in Bike’s UI. That script and your main extension code can communicate with each other using on message and postMessage. See this example.

---

Please give these things a try and let me know what needs fixing.

---

If you go digging into the API I just remembered some api that I haven’t filled in yet: inspector.addItem currently ignores the tab parameter and ignores the item.ordering parameter.

[jessegrosjean]

I forgot to mention, while I don’t think this release breaks much API extension structure has changed some. Most importantly extensions point to the @Bike extension for autocomplete types … and those locations have changed. And that means tsconfig.json files needed to change.

If you are playing with @Startup or your own extension your best bet to get everything working well might be:

1. Move your customized @Startup extension to backup location.
2. Launch Bike so that it will recreate @Startup with new structure
3. Move your changes back into project

Open in VS Code and verify that autocomplete and type checking are working properly. Note that when editing files in src/dom you should get different autocomplete options… HTML/DOM API should be available, while most of Bike app API should not be available.

[vinhqt]

I tried to use alert as a form, with the exact example from `bike.d.ts`, but couldn’t get the desired outcome. I’m on macOS 26.3.

/**
     * Show a window or application modal alert.
     *
     * @param options - The options for the alert
     * @param window - A window to attatch the alert to
     * @returns A promise that resolves to the result of the alert.
     * @example
     * ```typescript
     * bike.showAlert({
     *   title: "Login",
     *   buttons: ["OK", "Cancel"],
     *   fields: [
     *     {
     *       type: "text",
     *       id: "username",
     *       placeholder: "Username",
     *     },
     *     {
     *       type: "secure",
     *       id: "password",
     *       placeholder: "Password",
     *     }
     *   ]
     * }).then(result => {
     *   if (result.button === "OK") {
     *     console.log("Username:", result.values.username);
     *     console.log("Password:", result.values.password);
     *   }
     * });
     * ```
     */
    showAlert(options: AlertOptions, window?: Window): Promise<AlertResult>

I expected something like the default dialog for ‘Add/Edit link’:

[jessegrosjean]

@vinhqt

I tried to use alert as a form, with the exact example from bike.d.ts, but couldn’t get the desired outcome. I’m on macOS 26.3.

Thanks for finding, this is a bug. I haven’t made much use of this API and didn’t realize I had broken the field function a while back. Will fix for next release.

[jessegrosjean]

I think fixed in:

Bike 2.0 (Preview 274)

Added button to show/hide inspector Added Restore All Settings in General preferences Compress redundant text in breadcrumb (Navigate to calendar day) Fixed word-granularity drag selection losing the original double-clicked word Fixed font size slider changing line height Fixed font family popup resetting size to 13pt Fixed window opening with zero height after Restore All Settings Extensions Replaced AppleScript resolve with get row command Fixed showAlert fields being silently dropped Fixed…

[vinhqt]

You did, and the alert looks great. Btw, you can see from my screenshot a dark variant of Bike icon. Is that yours or system-generated?

[jessegrosjean]

It’s system generated.