Written by Gaz Davidson the 19 Feb 10 at 13:21.

Have Nautilus remember which windows have recently been closed so it can open them again in response to a specific key combination.

Ctrl+Shift+T would be an ideal default

Have Nautilus remember which windows have recently been closed so it can open them again in response to a specific key combination. Ctrl+Shift+T would be an ideal default

Written by forteller the 19 Feb 10 at 22:07.

Yes.

Yes.

Written by Lachu the 20 Feb 10 at 15:14.

Change behavior of close button. It should only minimize "closed window" for 10 seconds. After that the window could been closed.

This change should only change way of informing window with DestroyNotify. I don't know how change behavior of main windows of applications.

Change behavior of close button. It should only minimize "closed window" for 10 seconds. After that the window could been closed. This change should only change way of informing window with DestroyNotify. I don't know how change behavior of main windows of applications.

Written by Lachu the 21 Feb 10 at 12:27.

Extend way how application supports sessions. There should exist signals, like HIBERNATE(save session) to file, RESTORE SESSION from file, etc.

Window Managers could use this feature to achieve idea goal, but not all application could been integrated. The behavior is: give application order to save session in $HOME/.sessions-tmp/$CURRENT_DATE/pid/WINDOWID(or whole session if user wanna to close application instead of window).

To restore window, WM's will give only the same location with signal RESTORE.

Extend way how application supports sessions. There should exist signals, like HIBERNATE(save session) to file, RESTORE SESSION from file, etc. Window Managers could use this feature to achieve idea goal, but not all application could been integrated. The behavior is: give application order to save session in $HOME/.sessions-tmp/$CURRENT_DATE/pid/WINDOWID(or whole session if user wanna to close application instead of window). To restore window, WM's will give only the same location with signal RESTORE.

Written by Afroman10496 the 21 Feb 10 at 23:52.

Put a recently closed tray next to the workspace applet that holds the last three (changeable by the user) windows that you closed in the state they were in when you closed it, showing when it was closed and a screenshot of it when you closed it. Clicking on it should open a menu showing options to open, close, minimize, maximize, move, or move it to another workspace.
http://yfrog.com/juscreenshotckp

Put a recently closed tray next to the workspace applet that holds the last three (changeable by the user) windows that you closed in the state they were in when you closed it, showing when it was closed and a screenshot of it when you closed it. Clicking on it should open a menu showing options to open, close, minimize, maximize, move, or move it to another workspace. http://yfrog.com/juscreenshotckp

Written by Darwin Survivor the 23 Feb 10 at 00:02.

When an application closes, it would have the ability to "register" with the window manager that it is now closing and can be resumed by executing .

The window manager is now in complete control over whether or not to offer the session to the user.

This would allow:
-any app to be written to allow session resuming
-the app can de-register itself if the user resumes or creates a new session
-the app actually closes (no sleeping or anything)
-the user could chose how many "closes" to remember (wm disregards anything older)
-backwards compatible (would not affect apps that don't implement it)
-apps that already have a resume command don't need to change their switches (they tell the wm what to call)
-apps could create numerous sessions by registering with different commands (ex: app --resume )

When an application closes, it would have the ability to "register" with the window manager that it is now closing and can be resumed by executing <command>. The window manager is now in complete control over whether or not to offer the session to the user. This would allow: -any app to be written to allow session resuming -the app can de-register itself if the user resumes or creates a new session -the app actually closes (no sleeping or anything) -the user could chose how many "closes" to remember (wm disregards anything older) -backwards compatible (would not affect apps that don't implement it) -apps that already have a resume command don't need to change their switches (they tell the wm what to call) -apps could create numerous sessions by registering with different commands (ex: app --resume <session_id>)

Written by rayken_wong the 15 Apr 10 at 23:37.

In the right click drop down menu (ie the one w/ the always on top option) add an option whereby the close button is disabled

In the right click drop down menu (ie the one w/ the always on top option) add an option whereby the close button is disabled

Written by Lachu the 1 May 10 at 14:52.

Add history of recent closed applications/windows. If application don't be integrated, the window would been added to recent closed. Applications, like OpenOffice, which asks user to close window can remove own windows from history. Also, integrated application can inform WM's that it supports signals to reopen window.

Add history of recent closed applications/windows. If application don't be integrated, the window would been added to recent closed. Applications, like OpenOffice, which asks user to close window can remove own windows from history. Also, integrated application can inform WM's that it supports signals to reopen window.