docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.86k stars 288 forks source link

Docker Desktop IHM basic concepts : mono task, Clicodrome and so on... #13301

Open rv2931 opened 1 year ago

rv2931 commented 1 year ago

Hello I allow myself to write these lines because certain choices of operation of the graphical interface cause me concern and with the updates I realize that these choices persist in the same direction

We had to wait many years for having real multi tasking working so please stop using the concept of "modal window" everytime Docker Desktop is doing something that reduce the software of doing only ONE THING at a time, overall when it takes lots of time (too much) for stopping some containers. You can't do anything else during this time except in CLI. As soon as you take more time via GUI than CLI, you just have missed something in your design

The big point is when Docker Desktop is starting and you switch between Proxy and NoProxy environment. If you forget to remove proxy setting last time you launch it and want to launch it without proxy, it take a long to start because it doesn't manage to reach a website that is uselesss for me, but overall, during the time it try to reach something on the internet YOU CAN'T go to settings to change the proxy settings and make it's life easier... it's crazy I often have to reboot my machine to manage to launch desktop correctly just for having the possibility to change the proxy setting... crazy !!!

Most of important settings are editable by file even on windows even on Docker Desktop but for example, the proxy settings of docker engine via Docker Desktop seems to be unreachable by file. Because i'm switching Proxy/NoProxy every day I made a script that change the proxy settings for most of tools and for Docker Cients too but I have not found a way to change it by files for Docker Desktop as we can do it for proxy client settings with ~/.docker/config.json

Imagine you have two containers and want to work with CLI on both at the same time ? You have to launch both, clic on menu, clic on Terminal, then clic on "open in external terminal". Result : => 3 clics for one terminal Then you have to clic on "Containers" tab to get the list of containers then again, clic on menu/container, clic on terminal, clic on "open in external terminal" Result : => 4 clic for second terminal And this each time you stop and start you settup What I said to myself each time... several times per day, "this GUI has been made by Linux users that spit on Windows but they are doing it worse" because it is known as a "Clicodrome" (aka lots of clic to do everything) but clearly the philosophy of Docker Desktop that force user to make evrything IN the GUI is making the life harder than the worse windows application I ever seen

Proposition : just add Open in external Terminal directly in Containers Tab menu OR give the ability to set it by defaults in settings by a checkbox "Open external terminal by default : yes/no" for terminal but for everything, even the log output and so on...

In addition, this external terminal is a new terminal that doesn't take in account the historic of the internal terminal if you already have done smething into it but anyway just a detail

In the last version you remove the ability of copy/paste with selection/one with the mouse to replace that with a menu "Copy", then a second menu "Paste"... again : Okay you love clics and menus and so on, but don't remove the Linux way of doing it that is clearly more efficient for those that are used to use it

So as I said, I wrote these lines just because Docker Desktop was a good idea but clearly some basic concepts of GUI for real Windows Users are missing and it is making life harder, and for Linux and Windows users it is even worse

docker-robot[bot] commented 1 year ago

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale