| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Now the utilites are arranged by category (core, core-utils, desktop-utils), so all the -utils may be excluded by a package system (or turned into separate packages) as needed.
|
| |
|
|
| |
close right now.
|
| |
|
|
|
|
| |
screensaver. Also setup the screensaver so that the "--test-ss" option makes it fully-functional even if the WM event handler is not installed for valid testing).
The *only* thing which is still broken is that PAM is allowing all passwords for the user to unlock the system (probably some kind of password cache for the current credentials?). Still need to find some way to register a "lock" with PAM so that it forces the validation of the user's login credentials again.
|
| |
|
|
|
|
| |
and fix up the starting of screensavers on all screens simultaneously.
This solidifies the Screensaver plugin framework as completely functional - just need to finish up the lock/unlock screen now.
|
| |
|
|
|
|
|
| |
1) The LWindow class seems to function properly for embedding/controlling a window now.
2) Add a "testwin" CLI flag to simply run a text of the window class (with a sample window). This allows testing without having to stop the currently running WM.
3) Setup the XCB access class so it is globally accessible to the individual classes in the WM (no need to constantly be passing the structure around).
4) Already include built-in support for simple window animations/effects (3-lines per effect is all that is needed). Will need to define animation flags/settings for use later, probably with an abstracted function to "performAnimation(type, size)"
|
|
|
using yet.
|
