blob: 11a97cad2aa89012b2a98a99751fe57450424caa (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
<html>
<head>
<title>The Official FVWM Homepage - Concept</title>
</head>
<body BACKGROUND="black-stone1.jpg"
bgcolor="#000000" text="#ffffff"
link="#FFFF88" vlink="#EEDDDD" alink="#ff0000">
<center>
<h1><font color="pink">The Official FVWM Homepage - Concept</font></h1>
</center>
<P>
The module interface has several design goals:
<UL>
<LI>Modules are used to implement "extra" or "elaborate" features so
that the additional resources these features take don't affect users that
don't want to sacrifice the resources.
<LI>Modules (user programs) should be able to provide the window
manager with a limited amount of instruction regarding instructions to
execute.
<LI>Modules should not be able to corrupt the internal data bases
maintained by Fvwm, nor should unauthorized modules be able to
interface to Fvwm.
<LI>Modules should be able to extract all or nearly all information
held by the window manager, in a simple manner, to provide users with
feedback not available from built in services.
<LI>Modules should gracefully terminate when the window manager
dies, quits, or is re-started.
<LI>It should be possible for programmer-users to add modules
without understanding the internals of Fvwm. Ideally, modules could be
written in some scripting language such as Tcl/Tk.
</UL>
<P>
<hr>
</body>
</html>
|
