|
|
@ -1,18 +1,23 @@ |
|
|
|
These are the core modules of this desktop. |
|
|
|
There are currently the following modules, in the order of loading: |
|
|
|
1) error.lua - Error handling |
|
|
|
2) vars.lua - Variable definitions |
|
|
|
3) style.lua - ``beautiful`` theme and style definitions |
|
|
|
4) binds.lua - Binds |
|
|
|
5) layout.lua - Wibar layout |
|
|
|
6) rules.lua - Rules |
|
|
|
7) signals.lua - Signals |
|
|
|
1) error.lua - Error handling |
|
|
|
2) vars.lua - Variable definitions |
|
|
|
3) style.lua - ``beautiful`` theme and style definitions |
|
|
|
4) binds.lua - Binds |
|
|
|
5) layout.lua - Wibar layout |
|
|
|
6) rules.lua - Rules |
|
|
|
7) signals.lua - Signals |
|
|
|
|
|
|
|
Some of the modules were further split into distinct components: |
|
|
|
1) client.lua - Additional client hook to be run when a client is created. |
|
|
|
2) titlebar.lua - Titlebar configuration, also run when a client is created. |
|
|
|
3) widgets/* - Default widgets and their parameters. |
|
|
|
|
|
|
|
Notice that Error handling and Variable definitions come before beautiful |
|
|
|
initialization. That is normal. Those modules don't depend on any of the |
|
|
|
above, therefore they are loaded before anything else. |
|
|
|
|
|
|
|
Additionally, notice that Binds come before Wibar. That is not exactly how it |
|
|
|
Additionally, notice that Binds come before layout. That is not exactly how it |
|
|
|
was in the default rc.lua, but it is important to load them in exactly that |
|
|
|
order. Widgets, which are called from layout.lua, override the global bindings |
|
|
|
table. If you load binds after the layout is loaded, the bindings are reset to |
|
|
|