Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some ideas to inprove it #63

Open
Predatux opened this issue Mar 16, 2016 · 2 comments
Open

Some ideas to inprove it #63

Predatux opened this issue Mar 16, 2016 · 2 comments
Labels

Comments

@Predatux
Copy link

The program is great, thanks :)

I have two ideas for improvement.

  1. add a indicator function next to the buttons to maximize, minimize and close, like the app "Moom" for Mac.
    https://www.youtube.com/watch?v=1gYFYWhO3PY
    moom
  2. Add another option in the window so it is fixed indefinitely at the last position used by quicktile, and that is not lost when you restart the computer.

Greetings.

@ssokolow
Copy link
Owner

Unfortunately, replicating Moom's popup is more difficult than it sounds because of differences between OSX and X11.

  1. On OSX, the compositor doesn't do tiling, so you need to monkey-patch it in with Moom. On Linux, some window managers (eg. Compiz, KWin, Xfwm4, etc.) have tiling as an option and some don't... so QuickTile monkey-patches in tiling in a "not the best, but guaranteed to work everywhere" fashion.
  2. Moom is able to give that style of popup because it's designed and debugged to work with one specific compositor... similar to the tiling plugins for various Linux window managers.

The main issue is that there's no simple, reliable, efficient way to figure out where those titlebar buttons are (or even if they exist)... I could add a keyboard-triggered popup (or possibly triggered by an extra mouse button on fancy mice) which appears at the mouse cursor, but not what Moom does.

Also, given that QuickTile relies on the dangerous ability for any X11 application to meddle in any other X11 application, I don't want to spend too much effort on new features because Wayland will make it impossible anyway. (On Wayland, sensitive things like moving windows and accepting passwords are handled as part of the compositor and applications don't have those privileges.)

As for having it remember positions, I actually have been wanting to do that for years but things keep coming up which eat up the time I need to rework its innards for better extensibility.

At the moment, all my time is taken up by my degree project, but I'll leave this open as a TODO note.

@ssokolow
Copy link
Owner

Given that Wayland is taking significantly longer to mature than I'd expected, I'll consider implementing what is feasible of these options.

No promises, but we'll see how much motivation I have when I finish clearing out all the bugs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants