Zebar: baixar versions anteriors

Getting started on macOS? Install via Homebrew:
brew install --cask glzr-io/tap/zebar

🐛 Bug fixes
- Hotfixed an issue where windows were being positioned incorrectly on Windows (#274, closes #272).

/ @lars-berger

This version ships alongside a long-awaited release of GlazeWM, which introduces macOS support. The glazewm provider works on both platforms without any setup changes (including earlier Zebar versions).🎉 New features
- macOS code signing - the .dmg below is now signed and won't show Gatekeeper warnings. (#268)
- When docking a widget to the top edge, it'll now be shown in the reserved menubar space on macOS. (#266)
- System tray icons now support double-click actions. (#260 by @CtByte)
- Added komorebi provider support on macOS (#258 by @geneccx).
🐛 Bug fixes
- Fixed window positioning on multi-monitor setups for macOS. (#272)
- Fixed a resource leak in battery and media providers. (#262 by @johnsideserf)
- Fixed top_most z-order not being applied on macOS. (#265)
🛠️️ Internal changes
- Removed pinned WebView2 runtime version (#267).
- Added optional npm publishing to release pipeline (#270).
- Bumped cargo crates (#271).
⚠️ Deprecations
Shell exec via glazewm provider: In a future GlazeWM release, the shell-exec command will be restricted to GlazeWM's keybinding config only. If your Zebar widgets use runCommand('shell-exec ...') from the glazewm provider, please refer to the guide at Running shell commands for migrating.
Big thanks to @CtByte, @geneccx, and @johnsideserf for contributing to this release 💛/ @lars-berger

🎉 New features
- Add permissions for vibrancy and cursor events APIs on the Tauri window (#249).
🐛 Bug fixes
- Fix to #252: bundles a fixed WebView2 runtime to work around a bug introduced in a recent Windows update.
- Upstream issue: MicrosoftEdge/WebView2Feedback#5492
- Correct typo transmitSpeed in type definition of NetworkInterface (#235).
📘 Docs improvements
- Update some outdated info in the readme after the upgrade to v3 (#244).

Big thanks to @Miitto, @blaiyz, and @RedPhortex for contributing to this release 💛/@lars-berger

🐛 Bug fixes
- Fix message parsing error in komorebi provider. It's now compatible with the latest v0.1.37 version of komorebi.
- Correct type definition of arg param of startWidget.

/ @lars-berger

🎉 New features
- Add errors.log file for error dumps.
- Add configurable stdout logging verbosity with new --quiet and --verbose CLI flags.
- Allow fractional units for widget width, length, and offset (e.g. 90.5%).
- Add tauriWindow getter and close function to currentWidget.
// ## For example, auto-close a widget when focus is lost (e.g. for popups like calendars, volume).
// ## Best used with "Focus on launch" option enabled for widgets.

// Listen to widget losing focus.
zebar.currentWidget().tauriWindow.listen("tauri://blur", () => {
zebar.currentWidget().close(); // close the widget!
});

🐛 Bug fixes
- Prevent memory buildup from debug logging (#226).
- Fix widget z-order not working (always on top/bottom).
- Add better handling for apps that emit frequent systray update events.
- Fix 404 error when installing Zebar with an instance already running.
- Fix "Empty cache & reload configs" menu option not relaunching widget windows.
- Fix "Run on startup-up" menu option not working in some scenarios.
⚠️ Deprecations
// Previously:
const tauriWindow = currentWidget().window.tauri;

// After:
const tauriWindow = currentWidget().tauriWindow;

/ @lars-berger

🎉 New features
Offline support (#141)
Zebar already works totally fine without an internet connections, but the current starter configs make web requests for their assets (e.g. CSS files, fonts, etc.). These requests will now be cached so that they don't have to be re-fetched on the next launch (also improving performance!). The default caching duration is 1 week and can be configured in the widget's settings.Since some requests should not be cached, there's also a way to add rules for URL's that match a given regex. For example, if you make a fetch for stock market data or social feeds, you'd likely want to cache it for less time than something like a font file.cachingRunning shell commands (#160)
It’s now possible to run shell commands! This means you can now launch programs and scripts programmatically. There’s 2 new API’s:
- shellExec - Executes a program and waits till exit. Returns its stdout, stderr, and exit status.
- shellSpawn - Executes a program without waiting for exit. Allows for interaction with the spawned process (e.g. listening to stdout/stderr, writing to stdin, and killing the process).
import * as zebar from 'zebar';

const curl = await zebar.shellExec('curl', 'https://www.google.com');
console.log(curl.stdout);

const ping = await zebar.shellSpawn('ping', '127.0.0.1 -n 10 -w 3000');
ping.onStdout(output => console.log('stdout', output));
ping.onStderr(output => console.log('stderr', output));
ping.onExit(output => console.log('exit', output));

// Interacting with the spawned process:
ping.write('hello world!');
ping.kill();

Since shell commands can run destructive actions, there’s a UI to configure which commands a widget is allowed to run. This is mainly for the sake of an upcoming feature (see below!), so that if a widget is shared with others, they can check what shell privileges it uses.shellOther features
- Add pause button to with-glazewm starter config (#180).
- Make the text in the starter examples non-selectable (#176).
🐛 Bug fixes
- Export audio provider TypeScript types.
📘 Docs improvements
- Add docs for media provider functions.
- Add docs for isPaused to glazewm provider (#182).
Upcoming feature: community/marketplace 🚀
Currently in development is a new community/marketplace feature where you can download and run widgets that other people submit. Widgets would be uploadable through a community GitHub repo. And then through the settings UI, there will be a tab where all widgets are listed and instantly downloadable.If you have ideas/feedback on the feature, drop a message in the #zebar-chat channel on Discord!
Big thanks to @HolbyFPV, @michidk, and @veryard for contributing to this release 💛/ @lars-berger

🐛 Bug fixes
- Hotfix to crash due to paused state unavailable on glazewm provider.

/ @lars-berger

** Will write some better descriptions of the changes tomorrow morning.🎉 New features
- Add "Edit" system tray option for linking directly to widget config form (#163).
- Add all active sessions and media control functions to media provider (#158).
- Add audio provider (#154).
- Add binding mode toggle to example glazewm config (#155).
- Add config path to widget window title (#164).
- Add count of how many widgets are open to settings UI sidebar.
- Add recording devices and setVolume to audio provider (#170).
- Allow widget window title to be set via tauri window API.
- Export startWidget for programmatically launching widget at given placement.
- Expose current window as currentWidget().window.
- Expose whether WM is paused in glazewm provider (#167).
- Prevent duplicate emissions for keyboard + media providers (#162).
- Rename start-preset -> start-widget-preset.
- Setup for provider functions (#156).
🛠️️ Internal changes
- Add dev:local npm command (#171).
- Prettier lint fix.
- Rename MediaControlArgs -> MediaControlOptions.

Big thanks to @HolbyFPV and @michidk for contributing to this release 💛/ @lars-berger

🐛 Bug fixes
- Hotfix to media provider for handling null sessions (#153).
- Corrections to return types on new disk provider. Docs.

/ @lars-berger

🎉 New features
- New disk provider for hard-drive and storage capacity info (#138).
- New media provider for currently playing media info like song, album, artist, etc. (#136).
- Config option to dock Zebar windows to monitor edge (#131, #150). Only available on Windows for now.
- Set "Open settings" as the default system tray menu option.
- Add allWindows to glazewm provider (#149).
🐛 Bug fixes
- Fix incorrect version number shown in system tray and CLI.

Big thanks to @HolbyFPV, @veryard, and @fooooooooooooooo for contributing to this release 💛/ @lars-berger