Users may not see the warning that insertPosition definitely needs to be
inserted at the leftmost position, which can cause undesired behaviour.
Having a combinator that handles this automatically seems like a sane
idea.
f833d949 X.A.Navigation2D: Add sideNavigation as to default tiled navigation
Add sideNavigation as a fallback if needed. This should not have any
user-facing behaviour change when not using gaps or spacing, as line
navigation is preferred. However, users who do use spacing or gaps
should now potentially not have to change the default strategy in order
to have a usable module.
[x] I've considered how to best test these changes (property, unit,
manually, ...) and concluded: most of this is docs, but I've manually tested e.g. the changes to FloatKeys.
Commit Summary
7ec2cf25 Refer to the tutorial instead of X.D.Extending more often
Essentially, whenever the tutorial actually has decent material on the subject matter. The replacement is roughly done as follows:
09c47c2c X.A.FloatKeys: Add direction{Move,Resize}Window
These are simpler, more easily understood, alternatives to the existing functions.
Fixes: https://github.com/xmonad/xmonad-contrib/issues/712
180a4aa8 X.H.InsertPosition: Add combinator
Users may not see the warning that insertPosition definitely needs to be inserted at the leftmost position, which can cause undesired behaviour. Having a combinator that handles this automatically seems like a sane idea.
Fixes: https://github.com/xmonad/xmonad-contrib/issues/709
84c94d83 X.A.Navigation2D: More prominently document strategies
Also, add a note that users who use gaps or spacing may need to look into these strategies a bit more deeply.
Fixes: https://github.com/xmonad/xmonad-contrib/issues/627
f833d949 X.A.Navigation2D: Add sideNavigation as to default tiled navigation
Add sideNavigation as a fallback if needed. This should not have any user-facing behaviour change when not using gaps or spacing, as line navigation is preferred. However, users who do use spacing or gaps should now potentially not have to change the default strategy in order to have a usable module.
Checklist
[x] I've read CONTRIBUTING.md
[x] I've considered how to best test these changes (property, unit, manually, ...) and concluded: most of this is docs, but I've manually tested e.g. the changes to FloatKeys.
[x] I updated the
CHANGES.md
fileWhere appropriate.