Releases: sminez/penrose
Release list
0.4
What's Changed
- Add is_greedy and right_justified support to IntervalText widget" by @greweln in #322
- Removing & renaming workspaces (includes status bar bug fixes) by @sminez in #325
44c1ab6 Removing & renaming workspaces (includes status bar bug fixes) (#325)
58f83b4 #289 preventing clients on invisible workspaces from being focused
b03d7f9 #289 preventing invisible workspaces from being focused
d74a464 Add is_greedy and right_justified support to IntervalText widget" (#322)
ffc74b0 exposing layout method from workspace
7be1a44 adding Send + Sync bounds to layout traits
e7276bf exporting diff
ef44674 making Diff and related types public
062ef0a moving to using signed integers for positions
d4084a6 fix: #317 match window position shrinking when manipulating clients with the mouse
3d6c4d4 fix: fixing bug in focus_head method of Stack and adding focus_tail
a0f3669 fix: accounting for border resizing when setting fullscreen
74962e5 fix: #312 removing window borders when setting a client to fullscreen via ewmh hooks
331a081 feat: allowing for creating a SpawnOnStartup hook without boxing it
New Contributors
Full Changelog: c8f04ab...0.4
Contributors
Assets 2
0.3.6
What's Changed
- #297 improving the behaviour of IntervalText to run all updates in a single thread by @sminez in #298
- Adding meta queries to support combinations of queries as queries. by @favilo in #291
- fixing #113 and adding proper mouse support by @sminez in #300
- add battery finder by @bbarker in #303
- feat: toggle_floating_state and is_floating (#306) by @codybloemhard in #307
- feat: support customising the behaviour of the workspaces status bar widget by @sminez in #309
- Only honour removal of fullscreen state if the state is currently present by @sminez in #311
New Contributors
- @favilo made their first contribution in #291
- @bbarker made their first contribution in #303
- @codybloemhard made their first contribution in #307
Full Changelog: 0.3.5...0.3.6
Contributors
Assets 2
0.3.5
Contributors
Assets 2
0.3.4 release
0.3.3
What's Changed?
- Issue 272 - removing the dependency on pango and cairo (#274)
- fixed invalid desktop entry example in the getting started guide
- added resise request xevent and marking xevent as being non-exhaustive
- fixing an issue with floating windows continually shrinking as the gain focus
- added new layouts
- fixed underflow bug in reflect transformers
- added quickcheck tests for ensuring layouts don't panic on unexpected inputs
- adding focus_element and focus_element_by methods to Stack
- replaced internal usage of linked lists with vecdeque
- adding helper function for printing and ASCII repr of a layout
- added a split_at_mid methods to Rect
- added IntervalText as a base widget type for the status bar
- #268 clearing destroyed Xids from NSP state (#269)
- we now remove unknown clients from state when XConn impls return Error::UnknownClient from next_event
- added a helper macro for composing manage hooks
- fixed an issue where certain windows (e.g. chromium) render with transparent borders
- fixed the behaviour of the non_hidden_workspaces method on StackSet
- added LayoutHooks as a feature in Config
- allowing pointer warp when a workspace has floating clients
- added new manage hooks
Full Changelog can be viewed here: 0.3.2...0.3.3
0.3.2: bug fixes & QOL Improvements
There's a reasonable amount in this one but the main bugs that have been squashed are:
- #129 #223 #231 pop up windows and dialogues no longer make programs unresponsive(!)
- #244
manage_existing_clientsnow correctly avoids tiling windows that should be ignored - #251 transient windows now render on the same workspace as their parent
New features:
- #265 @thebashpotato the
DMenuhelper now supports triggeringdmenu-rsas well as the default suckless version - #166 keybindings can now be updated while Penrose is running
This also includes an update of the dependency on x11rb to 0.11 from @psychon #250
Contributors
Assets 2
0.3.1 fixing issue with kill_client
The kill_client method on StackSet was only removing the internal state, not shutting down the client on the X side. This is a pretty unfortunate bug so I'm pushing the fix as a new version immediately.
v0.3.0
📦 🦀 V0.3.0 is now live on crates.io 🦀 📦
This is a near total rewrite of the previous design to provide a nicer API to work with going forward. An overview of the new design is published to GitHub pages here and the new crate docs are now live on docs.rs.
NOTE: Some (but not all) of the functionality from the old
contribmodule has been ported over to the new API. If something you were using is not there yet please raise an issue and I can take a look at getting it re-implemented. I didn't make use of everything that was available in my day-to-day set up so I'll need some help verifying that the behaviour is as people expect!
Highlights
- A new "diff" based approach to rendering window state that provides a clean split between pure logic and side effect filled X logic
- Smarter internal data structures that allow for much simpler implementations of extensions to the core behaviour
- A base layer for extending the UI that is actually usable as opposed to being all kinds of scary! (Currently there is a status bar but a native dmenu replacement is in the works as well)
- A richer API for layouts that solves a lot of the issues that the pervious release had around implementing more complicated layouts and sharing common functionality (like gaps).
Version 0.2 end of life
⚠️ The rewrite branch is being merged to the develop ⚠️
Users pulling this repo directly from the mainline branch will see this as a breaking change
The original API of penrose was written fairly quickly(!) and has a number of issues that make future development difficult:
- Basing the original design on the
dwmcode base lead to a very C like API - State management is overly complicated
- Hooks are overly complicated
- Testing core window manager operations is a lot harder than it should be
- Far too many macros (I wrote penrose originally in part to learn how to write proc-macros...)
- Default impls used the rust-XCB crate rather than the wonderful x11rb from @psychon
A near total rewrite for v0.3 is reaching a usable state which moves over to an API that is more suited for ongoing development and extension by users of the crate. In particular the APIs are now designed with composition in mind as a rich set of primatives and a clear split between "pure" logical operations on the internal state and code that then updates things on the X side based on diffs of that pure state.
What does this mean for me?
I like things the way they are!
🏷️ Please pin your usage of penrose to this tag if you are intending on making use of the original penrose API but be aware that there will be no more development taking place on this version of the code.
How do I start making use of the new APIs?
The rewrite branch is being merged to mainline following the creation of this EOL release and is now in a usable state. I've been using it as my daily driver for a few weeks now and it is relatively stable to live in so long as you are only making use of the top level APIs shown in the examples directory.
🐛 That said, there are bugs. There are some issues around tracking mouse based focus changes in a multi-monitor set up and I suspect that it will be easier than it should be to shoot yourself in the foot if you try something clever beyond what is shown in the current examples.
I am planning on writing up the docs and more examples for the API now that it is stablising but for now please be aware that I am making frequent changes to APIs in order to address issues as they crop up. If you are interested in taking things for a spin and providing feedback then please do! Just be aware that I am not yet aiming for stability.
When will the new APIs be stable?
There are a couple of final high profile bugs / behaviours that I want to correct before pushing this live to crates.io. Once those are addressed I'll be publishing a 0.3.0 version to crates which will mark the new stable API.
👋 Happy window managing!