36 lines
1.3 KiB
HTML
36 lines
1.3 KiB
HTML
|
<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>
|