
Hi everyone, In earlier versions of xmonad, when pressing the full screen button while watching a flash-movie, a new window would be opened, integrated in whichever layout one was using at the time, and the video, now running in "full-screen-mode", would take as much screen-real-estate as xmonad was willing to let it have. This behavior has changed with recent versions of xmonad (or at least the version that I am currently running). A new window with the movie is still created, however, the movie now runs with the same resolution as the screen. For example, if you're running the Tiled-layout and start a flash-movie within Firefox, you would see the Firefox-window on the right and the video-window on the left, however, now the movie being cut off in the middle. (I also have the issue that when the video-window is loosing focus, it disappears, e.g. when moving the mouse out of the window, or when changing layouts, or when switching workspaces.) I was always thinking of the old behavior of xmonad as a feature. A program running in "full-screen" would optimize itself according to the real-estate you -- as a user -- are willing to give to it. This had great advantages. You could watch a taped university lecture on youtube in full-screen WHILE looking things up on the web, etc. This is not possible anymore, as each program running in "full-screen-mode" actually thinks that it would have the *full screen* available. So, I have two questions. 1) I compiled xmonad from source. Where in the code would I need to change what to get the old behavior back, handling full-screen movies? I would be really thankful, if someone could point me into the right direction. Where to look, what to change, etc.? Or even better, is it possible to trigger this within ones xmonad.hs? Thanks so much for help. 2) I would propose going back to the old behavior of handling full-screen-programs in xmonad. It really should be the *user* who decides how "full-screen" a full-screen-program shall be. Isn't this also more following the philosophy of xmonad? You as a user decide, what is happening on your screen? It might be not as intuitive, when switching to xmonad and you are used to other WMs, where full-screen means *full screen*. I really miss that functionality, now that its gone. What do you think? Cheers, Thomas

On Sat, 06 Jun 2009 12:41:52 -0400
Thomas Friedrich
In earlier versions of xmonad, when pressing the full screen button while watching a flash-movie, a new window would be opened, integrated in whichever layout one was using at the time, and the video, now running in "full-screen-mode", would take as much screen-real-estate as xmonad was willing to let it have.
Hi Thomas, I do not see a problem here, since the "not-full-screen-mode" works exactly as you want. What program do you use to play movies, mplayer? The other story is that mplayer's window is floating by default You can add to manageHook: ..... ,[ className =? "MPlayer" --> unFloat ] ..... where unFloat = ask >>= doF . W.sink ..... Cheers, Sergey

2009/6/6 Sergey Manucharian
On Sat, 06 Jun 2009 12:41:52 -0400 Thomas Friedrich
wrote: .... In earlier versions of xmonad, when pressing the full screen button while watching a flash-movie, a new window would be opened, integrated in whichever layout one was using at the time, and the video, now running in "full-screen-mode", would take as much screen-real-estate as xmonad was willing to let it have.
I do not see a problem here, since the "not-full-screen-mode" works exactly as you want. What program do you use to play movies, mplayer?
I think he is talking about what most programs do when they go to "full screen", namely remove all decoration and only show the central part (of whatever it is they do). Therefor there can be a tremendous difference between how a program uses the available screen-real-estate in full-screen and not-full-screen. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad?

Jens Peter Secher wrote:
2009/6/6 Sergey Manucharian
: On Sat, 06 Jun 2009 12:41:52 -0400 Thomas Friedrich
wrote: .... In earlier versions of xmonad, when pressing the full screen button while watching a flash-movie, a new window would be opened, integrated in whichever layout one was using at the time, and the video, now running in "full-screen-mode", would take as much screen-real-estate as xmonad was willing to let it have.
I do not see a problem here, since the "not-full-screen-mode" works exactly as you want. What program do you use to play movies, mplayer?
I think he is talking about what most programs do when they go to "full screen", namely remove all decoration and only show the central part (of whatever it is they do). Therefor there can be a tremendous difference between how a program uses the available screen-real-estate in full-screen and not-full-screen.
Cheers,
Yeah, this is exactly what I was talking about. I use the Adobe Flash-Payer 10.0.22.87 to watch movie in Firefox. Now, I realized that not all programs act as above. For example, when you go into full-screen with xpdf, it acts just as expected, i.e. xpdf simply removes all decoration and only show the central part, the document. Cheers, Thomas

Quoting Thomas Friedrich
Hi everyone,
In earlier versions of xmonad, when pressing the full screen button while watching a flash-movie, a new window would be opened, integrated in whichever layout one was using at the time, and the video, now running in "full-screen-mode", would take as much screen-real-estate as xmonad was willing to let it have.
This behavior has changed with recent versions of xmonad (or at least the version that I am currently running). A new window with the movie is still created, however, the movie now runs with the same resolution as the screen. For example, if you're running the Tiled-layout and start a flash-movie within Firefox, you would see the Firefox-window on the right and the video-window on the left, however, now the movie being cut off in the middle. (I also have the issue that when the video-window is loosing focus, it disappears, e.g. when moving the mouse out of the window, or when changing layouts, or when switching workspaces.)
I was always thinking of the old behavior of xmonad as a feature. A program running in "full-screen" would optimize itself according to the real-estate you -- as a user -- are willing to give to it. This had great advantages. You could watch a taped university lecture on youtube in full-screen WHILE looking things up on the web, etc. This is not possible anymore, as each program running in "full-screen-mode" actually thinks that it would have the *full screen* available.
So, I have two questions.
1) I compiled xmonad from source. Where in the code would I need to change what to get the old behavior back, handling full-screen movies? I would be really thankful, if someone could point me into the right direction. Where to look, what to change, etc.? Or even better, is it possible to trigger this within ones xmonad.hs? Thanks so much for help.
2) I would propose going back to the old behavior of handling full-screen-programs in xmonad. It really should be the *user* who decides how "full-screen" a full-screen-program shall be. Isn't this also more following the philosophy of xmonad? You as a user decide, what is happening on your screen? It might be not as intuitive, when switching to xmonad and you are used to other WMs, where full-screen means *full screen*. I really miss that functionality, now that its gone. What do you think?
I think the old behaviour made much more sense. As it is now, it's not possible to play a web flash movie in a separate, arbitrarily sized, window. You either have to watch it fullscreen-floating, or integrated in the web-page. @Thomas - Did you ever manage to revert Xmonad to the old behaviour? Regards, Rickard Nilsson

2009/6/23 Rickard Nilsson
Quoting Thomas Friedrich
: In earlier versions of xmonad, when pressing the full screen button while watching a flash-movie, a new window would be opened, integrated in whichever layout one was using at the time, and the video, now running in "full-screen-mode", would take as much screen-real-estate as xmonad was willing to let it have. [...]
I think the old behaviour made much more sense.[...]
+1 -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad?
participants (4)
-
Jens Peter Secher
-
Rickard Nilsson
-
Sergey Manucharian
-
Thomas Friedrich