v0.2.0

What's Changed

This marks the first major milestone since the first release! As mentioned in the v0.1.0 release, winbar is in a usable state, but there's still quite a bit of work to be done to make it more useful. With that being said, this release makes major strides in the stability of winbar, and focus on building features to get winbar to that more useful state can now begin.

Here are some highlights:

• You now have the ability to do more customization with the existing components (see #3 and docs)
• Improved memory footprint
• Starting winbar with winbarc now properly starts the background process

Full list of changes and their context can be found below.

A note on v0.3.0

With this release, work on v0.3.0 will now begin. The tentative plan is to start building out the plugin system to create the winbar component ecosystem. Quite a bit of work surrounding this is expected, so it may take a little while for the v0.3.0 release.

Features

• feat: styling by @Sulaxan in #3

Fixes

• fix: status bar visibility and background running when starting winbar using winbarc by @Sulaxan in #1
• fix: default style memory leak by @Sulaxan in #2
• fix: flickering by @Sulaxan in #4

Full Changelog: v0.1.0...v0.2.0

v0.1.0

winbar v0.1.0 release features the following:

• Ability to customize the status bar (size, location, colors, etc.) -- see configuration in README
• 2 components: static text & datetime
• winbarc - a CLI tool to manage winbar

See README for download, install, and usage instructions.

Note that though winbar is in a usable state in this release, it is still lacking in more useful features. This will hopefully improve over time. Also note that performance, though seemingly fine during test, is still a question mark. Please create an issue if you decide to use this release and notice any problems.

Full Changelog: https://github.com/Sulaxan/winbar/commits/v0.1.0