X-Git-Url: https://git.decadent.org.uk/gitweb/?p=ion3.git;a=blobdiff_plain;f=doc%2Fionconf%2Fnode4.html;h=d156abd426bc9cb0516db9e6753a0984443e03db;hp=60acef34ef86df91f2c7e41b94e0d6e4d5204d07;hb=20070203;hpb=8366314611bf30a0f31d25bf5f5023186fa87692 diff --git a/doc/ionconf/node4.html b/doc/ionconf/node4.html index 60acef3..d156abd 100644 --- a/doc/ionconf/node4.html +++ b/doc/ionconf/node4.html @@ -153,9 +153,9 @@ explained. For a reference on exported functions, see section Ion3, to which document applies, stores its stock configuration files in /usr/local/etc/ion3/ unless you, the OS package maintainer or whoever installed the package on the system has modified the variables -PREFIX or -ETCDIR in -system.mk before compiling Ion. +PREFIX or +ETCDIR in +system.mk before compiling Ion. In the first case you probably know where to find the files and in the other case the system administrator or the OS package maintainer should have provided documentation to point to the correct location. @@ -573,8 +573,8 @@ defbindings("WFrame", { As seen above, the functions that create key binding specifications require a keyspec argument. This argument should be a string containing the name of a key as listed in the X header file keysymdef.h3.1 without the XK_ prefix. - + HREF="#foot857">3.1 without the XK_ prefix. + Most of the key names are quite intuitive while some are not. For example, the Enter key on the main part of the keyboard has the less common name Return while the one the numpad is called KP_Enter. @@ -586,23 +586,23 @@ modifiers:
Shift, Control, Mod1 to Mod5, AnyModifier and Lock. + -

X allows binding all of these modifiers to almost any key and while this list of modifiers does not explicitly list keys such as -Alt that are common on modern keyboards, such +Alt that are common on modern keyboards, such keys are bound to one of the ModN. On systems running XFree86 Alt is usually Mod1. On Suns Mod1 is the diamond key and Alt something else. One of the ''flying window'' keys on so called Windows-keyboards is probably mapped to Mod3 if you have -such a key. Use the program xmodmap +such a key. Use the program xmodmap to find out what exactly is bound where.

@@ -614,10 +614,10 @@ default.

Ion ignores the Lock modifier and any ModN () -bound to NumLock or -ScrollLock +bound to NumLock or +ScrollLock by default because such3.2 locking keys may otherwise + HREF="#foot836">3.2 locking keys may otherwise cause confusion.

@@ -630,7 +630,7 @@ cause confusion. Button specifications are similar to key definitions but now instead of specifying modifiers and a key, you specify modifiers and one of the button names Button1 to -Button5. Additionally the +Button5. Additionally the specification may end with an optional area name following an @-sign. Only frames currently support areas, and the supported values in this case are @@ -681,10 +681,10 @@ to it is available virtually everywhere.

- - + + In the stock configuration file setup, menus are defined in the file cfg_menus.lua as previously mentioned. The mod_menu module must be loaded for one to be able to define menus, and this is done with @@ -739,6 +739,13 @@ just like the menus defined as above. workspacelist List of all workspaces. Activating an entry jumps to that workspaces. +focuslist +List of client windows with recent activity in them, followed by + previously focused client windows. + +focuslist_ +List of previously focused client windows. + stylemenu List of available look_*.lua style files. Activating an entry loads that style and ask to save the selection. @@ -814,7 +821,7 @@ handlers (and elsewhere): after which the selected entry is activated. This function is meant to be used for implementing, for example, Win***s-style Alt-Tab handling.3.3 + HREF="#foot1174">3.3 @@ -842,7 +849,7 @@ defbindings("WFrame", {

-The so-called ''winprops'' can be used to change how +The so-called ''winprops'' can be used to change how specific windows are handled and to set up some kludges to deal with badly behaving applications. They are defined by calling the function defwinprop with a table containing the properties to set and the @@ -860,7 +867,7 @@ usual method of identifying windows, and how to obtain this information.

Description:
-
+
Set this to true for Acrobat Reader. It has an annoying habit of trying to manage its dialogs instead of setting them as transients and letting the window manager do its job, causing @@ -878,7 +885,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
The table should contain the entries w and h that override application-supplied aspect ratio hint. @@ -893,7 +900,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
Set this to open the window in a floating frame, when in a group. @@ -908,7 +915,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
Should the window be initially in full screen mode?
@@ -922,7 +929,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
Should configure requests on the window be ignored? Only has effect on floating windows. @@ -937,7 +944,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
Ignore extended WM hints _NET_ACTIVE_WINDOW request.
@@ -951,7 +958,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
Should application supplied size increments be ignored?
@@ -965,7 +972,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
Should a newly created client window always be made active, even if the allocated frame isn't. @@ -980,7 +987,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
The table should contain the entries w and h that override application-supplied maximum size hint. @@ -995,12 +1002,31 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
Similar to max_size but for the minimum size hint.
+

+ +

+
Winprop:
+
new_group (string) + +
+
Description:
+
+ If the region specified by target winprop does not exist + (or that winprop is not set), create a new workspace using the + previously stored layout (see ioncore.deflayout) named by + this property. After creating the workspace, target is + attempted to be found again. (If that still fails, the newly + created workspace is still asked to manage the client window.) + +
+
+

@@ -1009,12 +1035,29 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
Discard this winprop after first use.
+

+ +

+
Winprop:
+
statusbar (string) + +
+
Description:
+
+ Put the window on the statusbar, in the named tray component, + (The default tray component is called simply ``systray'', + and others you give names to in your custom template, always + prefixed by ``systray_''. + +
+
+

@@ -1023,7 +1066,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
Should a newly mapped client window be switched to within its frame. @@ -1038,9 +1081,9 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
The name of an object (workspace, frame) that should manage - windows of this type. + windows of this type. See also new_group.
@@ -1053,7 +1096,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
"normal": No change in behaviour. "current": The window should be thought of as a transient for the current active client window (if any) even if it is not marked as a @@ -1072,7 +1115,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
When transients are managed by the client window itself (as it is the case on tiled workspaces), should the transients be placed at the top of the window instead of bottom? @@ -1088,7 +1131,7 @@ usual method of identifying windows, and how to obtain this information.
Description:
-
+
Should frames be made transparent when this window is selected?
@@ -1105,9 +1148,9 @@ usual method of identifying windows, and how to obtain this information.

The identification information in the winprop specification is usually the -class, -role, -instance and +class, +role, +instance and name of the window. The name field is a Lua-style regular expression matched against the window's title and the rest are strings that must @@ -1190,7 +1233,7 @@ can be used to list the identification information required to set winprops for a window and all the transient windows managed within it.

- + Another way to get the identification information is to use xprop. Simply run To get class and instance, simply run xprop WM_CLASS and click on the particular window of interest. The class is the latter of @@ -1199,7 +1242,7 @@ windows have this property - use the command xprop WM_ROLE. This method, however, will not work on transients.

- + So-called ''transient windows'' are usually short-lived dialogs (although some programs abuse this property) that have a parent window that they are ''transient for''. On tiled workspaces Ion displays these windows @@ -1208,7 +1251,7 @@ Unfortunately xprop is stupid and can't cope with this situation, returning the parent window's properties when the transient is clicked on. For this reason you'll have to do a little extra work to get the properties for that window.3.4 + HREF="#foot1451">3.4

Finally, it should be mentioned that too many authors these days ''forget'' to set this vital identification to anything meaningful: @@ -1308,26 +1351,26 @@ default name formed from the frame's class name and an instance number.



Footnotes

-
...keysymdef.h...keysymdef.h3.1
This file can usually be found in the directory /usr/X11R6/include/X11/.
-
... such... such3.2
Completely useless keys that should be gotten rid of in the author's opinion.
-
... handling.... handling.3.3
See the wcirculate.lua script in the Ion scripts repository http://iki.fi/tuomov/repos/ion-scripts-3/.
-
... window.... window.3.4
There's a patch to xprop to fix this, but nothing seems to be happening with respect to including it in