feat: options to disable individual window controls, closes #116

[caesar]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

Platform support

API	macOS	Windows	Linux
Window::set_closable	✔️	✔️	✔️
Window::is_closable	✔️	✔️	✔️
WindowBuilder::with_closable	✔️	✔️	✔️
Window::set_minimizable	✔️	✔️	❌
Window::is_minimizable	✔️	✔️	❌
WindowBuilder::with_minimizable	✔️	✔️	❌
Window::set_maximizable	✔️	✔️	❌
Window::is_maximizable	✔️	✔️	❌
WindowBuilder::with_maximizable	✔️	✔️	❌

I am not able to find any GTK APIs which would make it possible to implement the minimizable and maximizable APIs on Linux.

See #116 and tauri-apps/tauri#2353, tauri-apps/tauri#4286.

[caesar]

Maximizable / Zoomable / Fullscreenable could also be considered.

It should be noted that disabling maximize was requested in each of the linked issues.
However, a few thoughts…:

• Disabling resize already disables maximize. Would it ever make sense to disable maximize when the window can be resized to that size anyway?
• On macOS, maximize isn't (really) a thing. We would want to disable "zoom" which is sometimes equivalent to maximize but not always (app-dependent). In which case: should a hypothetical set_maximizable also enable/disable zoom on macOS, or would a separate set_zoomable method be better?
• On macOS, zoom and fullscreen share the same button. I think the only way to disable either of them is to directly disable the button, something like this:

  NSButton *button = [window standardWindowButton:NSWindowZoomButton];
  [button setEnabled: NO];

[amrbashir]

Maximizable / Zoomable / Fullscreenable could also be considered.

It should be noted that disabling maximize was requested in each of the linked issues. However, a few thoughts…:

• Disabling resize already disables maximize. Would it ever make sense to disable maximize when the window can be resized to that size anyway?

Yeah, they can be separate from each other.

• On macOS, maximize isn't (really) a thing. We would want to disable "zoom" which is sometimes equivalent to maximize but not always (app-dependent). In which case: should a hypothetical set_maximizable also enable/disable zoom on macOS, or would a separate set_zoomable method be better?

set_maximizable is better to fit the terminology of other platforms and other methods like set_maximized

• On macOS, zoom and fullscreen share the same button. I think the only way to disable either of them is to directly disable the button, something like this:

  NSButton *button = [window standardWindowButton:NSWindowZoomButton];
  [button setEnabled: NO];

Sure, whatever works for macOS.

[caesar]

set_maximizable is better to fit the terminology of other platforms and other methods like set_maximized

Agreed, that probably makes the most sense, especially since Tao seems to implement "zoom" as if it was maximize anyway.

[caesar]

Note: I added an example for closable and modified the example for minimize to also cover minimizable.
I hope that's ok.
I thought it unnecessary to also add an example for maximizable since it works identically to minimizable.

[amrbashir]

Great work! Thanks

[caesar]

Thanks for the review @amrbashir. All the changes made a lot of sense except #574 (comment) – please see my comment there. Is the change in behaviour intended? If so it will be different behaviour from other platforms.

[amrbashir]

Last few nit-pick

[caesar]

Thanks @amrbashir, that seems to work.