aboutsummaryrefslogtreecommitdiff
path: root/lumina-wm-INCOMPLETE/GlobalDefines.h
Commit message (Collapse)AuthorAge
* Rearrange the Lumina source tree quite a bit:Ken Moore2016-04-25
| | | | 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.
* Get some more of the new WM functional. Still not ready to be used by the ↵Ken Moore2016-04-23
| | | | faint of heart.
* Quick checkpoint for the window manager: NOT STABLE - crashes on window ↵Ken Moore2015-11-20
| | | | close right now.
* Couple minor changes to the screensaver functionality: Ensure the ↵Ken Moore2015-11-06
| | | | SSBaseWidget background color is set properly (so it can now be different from the main LScreenSaver background - as designed), set the main background color gray (for now - until we add custom backgrounds in), and disable the debugging on the main screensaver class (no need for all the event debugging info to be seen any more - is working fine).
* Get the new lockscreen all setup and (somewhat) functional in the ↵Ken Moore2015-11-04
| | | | | | 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.
* Add all the animations framework for the screensaver side of lumina-wm (with ↵Ken Moore2015-11-02
| | | | a quick "sample" plugin).
* Commit some more work on lumina-wm:Ken Moore2015-09-04
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)"
bgstack15