X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=ionconf%2Fnode3.html;fp=ionconf%2Fnode3.html;h=cc7578a7f485aab9c7fee85a960386465d45794d;hb=16a5f824c31d29598763c5f49918ef67a47ad7e0;hp=f3dbd29a000c973dbb5d34114c5918f2ecbae02d;hpb=6e84dc8312f2fdb5b8b7467a0279afd5b2df107f;p=ion3-doc.git
diff --git a/ionconf/node3.html b/ionconf/node3.html
index f3dbd29..cc7578a 100644
--- a/ionconf/node3.html
+++ b/ionconf/node3.html
@@ -227,7 +227,7 @@ implement.
-
+
Figure 2.1:
Partial Ioncore, mod_tiling and mod_query
@@ -237,10 +237,10 @@ Partial Ioncore, mod_tiling and
+
Is the base of Ion's object system.
WRegion
-
+
is the base class for everything corresponding to something on the
screen. Each object of type WRegion has a size and position
relative to the parent WRegion. While a big part of Ion
@@ -277,27 +277,27 @@ The core classes:
WClientWin
- is a class for
+ is a class for
client window objects, the objects that window managers are
supposed to manage.
WWindow
- is the base class for all
+ is the base class for all
internal objects having an X window associated to them
(WClientWins also have X windows associated to them).
WRootWin
- is the class for
+ is the class for
root windows of X screens.
Note that an ''X screen'' or root window is not necessarily a
single physical screen as a root window
- may be split over multiple screens when multi-head extensions
- such as Xinerama are used. (Actually there
- can be only one WRootWin when Xinerama is used.)
+ may be split over multiple screens when hacks such as
+ Xinerama are used. (Actually there can be only
+ one root window when Xinerama is used.)
@@ -310,15 +310,14 @@ The core classes:
WScreen
- is the class for objects
+ is the class for objects
corresponding to physical screens. Screens may share a root
- window when Xinerama multihead extensions are used as explained
- above.
+ window when the Xinerama extension is used as explained above.
WFrame
- is the class for frames.
+ is the class for frames.
While most Ion's objects have no graphical presentation, frames basically
add to WMPlexes the decorations around client windows
(borders, tabs).
@@ -326,11 +325,11 @@ The core classes:
WGroup
- is the base class for groups.
+ is the base class for groups.
Particular types of groups are workspaces
- (WGroupWS)
+ (WGroupWS)
and groups of client windows
- (WGroupCW).
+ (WGroupCW).
@@ -340,12 +339,12 @@ Classes implemented by the mod_tiling module:
- WTiling
-- is the class for tilings
+
- is the class for tilings
of frames.
- WSplit
-- (or, more specifically, classes
+
- (or, more specifically, classes
that inherit it) encode the WTiling tree structure.
@@ -356,19 +355,19 @@ Classes implemented by the mod_query module:
- WInput
-- is a virtual base class for the
+
- is a virtual base class for the
two classes below.
- WEdln
-- is the class for the ''queries'',
+
- is the class for the ''queries'',
the text inputs that usually appear at bottoms of frames and sometimes
screens. Queries are the functional equivalent of ''mini buffers'' in
many text editors.
- WMessage
-- implements the boxes for
+
- implements the boxes for
warning and other messages that Ion may wish to display to the user.
These also usually appear at bottoms of frames.
@@ -392,7 +391,7 @@ binding callbacks in the move and resize mode.
2.2.2.1 Parent-child relations
Each object of type WRegion has a parent and possibly a manager
-associated to it. The parent for an object is always a
+associated to it. The parent for an object is always a
WWindow and for WRegion with an X window (WClientWin,
WWindow) the parent WWindow is given by the same relation of
the X windows. For other WRegions the relation is not as clear.
@@ -402,7 +401,7 @@ Figure 2.2.
-
+
Figure 2.2:
Most common parent-child relations
@@ -423,7 +422,7 @@ Most common parent-child relations
WRegions have very little control over their children as a parent.
-The manager WRegion has much more control over its
+The manager WRegion has much more control over its
managed WRegions. Managers, for example, handle resize requests,
focusing and displaying of the managed regions. Indeed the manager--managed
relationship gives a better picture of the logical ordering of objects on
@@ -441,7 +440,7 @@ but all have a parent-a screen if not anything else.
-
+
Figure 2.3:
Most common manager-managed relations