awesome/core
Yessiest 780f63f1a0 Removed duplicated context menus for windows 2022-04-18 15:54:23 +04:00
..
binds Phone style + smarter ubuntu layout 2022-04-15 14:02:00 +04:00
widgets Phone style + smarter ubuntu layout 2022-04-15 14:02:00 +04:00
README.txt Added stuff to README 2021-11-14 14:56:28 +04:00
binds.lua Initial commit 2021-11-14 14:28:13 +04:00
client.lua Initial commit 2021-11-14 14:28:13 +04:00
error.lua Initial commit 2021-11-14 14:28:13 +04:00
layout.lua Removed duplicated context menus for windows 2022-04-18 15:54:23 +04:00
rules.lua Added necessary dependencies, included stickers in layout, added rules for onboard 2021-11-15 12:43:27 +04:00
signals.lua Pre-beta-ish-release rush 2022-04-03 19:18:03 +04:00
style.lua Initial commit 2021-11-14 14:28:13 +04:00
titlebar.lua Removed duplicated context menus for windows 2022-04-18 15:54:23 +04:00
vars.lua Fixed volume control on per-application basis 2022-04-03 14:45:52 +04:00

README.txt

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

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 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
defaults.

Everything else is kept in exactly the same order as it was in the default
rc.lua

Additionally, it should be noted that all widgets in this config are entirely
independent. Simply not loading them will not load any keybindings or break
the config. Therefore, if you want to change any keybindings for the widgets,
you would want to search for them in their respective modules.