On 2008-05-21, Alain-Pierre Manine <[EMAIL PROTECTED]> wrote:
> 1) An easy way to save a workspace configuration to cfg_layouts.lua: after  
> have set frames configuration of a workspace to fit a specific task, I  
> would like to save it, just in case.

This should be implementable as a script with WRegion.get_configuration,
ioncore.write/read_savefile, and WMPlex.attach_new (after possibly
filtering the results a bit from stuff related to currently attached
client windows).

> 2) A "modal" keyboard handling (VI-like): for instance, a default "App  
> Mode", in which all keys would be handling by the application, until the  
> user presses an "echap" key, which would allow to switch between several  
> modes (frames modes, tabs mode, resize mode, etc.). 

On my old TODO-list there indeed was an entry for locking submaps
(that are only explicitly terminated). I however never got around to 
doing that, although it shouldn't be too difficult. A nice simple
exercise for the budding Ion hacker. (Properly altering _ and _sub
passed to binding handlers after focus change within the mode demands 
a bit more work, although initially it can be emulated within the
binding handlers.)

> 3) A screen-like "detach" functionality: I already use scripts to, when I  
> press a key, open a new terminal in a screen session named according to  
> the workspace name. That allows to "import" consoles of a workspace into a  
> distant computer, and continue the work where we left it. Nevertheless, it  
> would be great to have this feature built-in in the WM, in order to import  
> a complete distant Ion workspace, including the frame configuration. The  
> only work I know related to this is done here:  
> http://partiwm.org/wiki/xpra .

An interesting hack, but *eugh*. I think VNC is quite enough for access of
running remote programs (if VNC implementations itself didn't suck). For
finer workspace/task or even single program level control I'd rather do 
this through proper session management: instead of saving individual 
workspaces as above, you could save the state of all the programs on that
workspace and start the session anywhere, even after reboots. I'd like my
tasks/workspaces to be truly mobile, their state possibly living anywhere 
in cyberspace, and attachable/restartable on any computer I might stumble
upon (and deem safe enough), possibly without constant a high-speed internet
connection.

-- 
Tuomo

Reply via email to