aboutsummaryrefslogtreecommitdiff
path: root/src-qt5/core/lumina-desktop-unified/global-objects.h
Commit message (Collapse)AuthorAge
* Another large update to Lumina 2:Ken Moore2018-01-08
| | | | Starting to hook up the new QML window frame with the C++ backend.
* Add the new "DesktopManager" class into lumina2 sources.Ken Moore2018-01-02
| | | | This is the class that watches for settings file changes and/or converts settings into interface object values.
* Another checkpoint commit for Lumina 2Ken Moore2017-10-13
| | | | Almost have the QML-based desktop canvas working - still tracking down some QML syntax issues.
* Get a lot of the root context menu up and running. Now the application list ↵Ken Moore2017-08-29
| | | | is available and functional, plus the beginnings of the task manager plugin for the menu.
* Move Lumina2 over to using the static instance of the DesktopSettings class ↵Ken Moore2017-07-05
| | | | rather than a global object (lets us use the DesktopSettings within the standalone classes in libLumina as well).
* Another large batch of re-organization for lumina-desktop-unified.Ken Moore2017-06-27
| | | | This gets the new "NativeWindowSystem" and associated Native* classes all integrated (untested)
* Another large update for Lumina 2:Ken Moore2017-01-27
| | | | | | | | | | | | Get the new LShortcutEvents class setup and functional. This is what converts the key presses and mouse clicks into a format that can be scanned for user-defined shortcuts to do things in the session. NOTES: The format of the keys.conf files uses "keycodes" (in ascending order") delimited by "+" to make the settings searchable and non-ordered-specific. Example: [strict] 22+37+64=logout This is a shortcut for [L_Ctrl (37), L_Alt (64), Backspace (22)] and it will trigger the start of the logout procedures. The "strict" section (and it's alternative "desktop" section) determine priority of the shortcut (strict is always evaluated, desktop is only evaluated if the desktop has focus and there is no corresponding "strict" shortcut).
* Another large batch of work on the new unified desktop.Ken Moore2017-01-26
| | | | | | 1) Get the RootWindow up and functional. 2) Get the lumina-desktop-unified binary functional for starting to test the various pieces (not ready yet for general use) 3) Get the start-lumina-desktop binary setup to launch the new unified binary for testing if the "--unified" flag is used.
* Finish up the new RootWindow class, and tie it into the ↵Ken Moore2017-01-26
| | | | lumina-desktop-unified build. Also finish cleaning up the compilation of the lumina-desktop-unified project - still not ready for actual testing yet.
* A few more code changes for Lumina2.Ken Moore2017-01-10
|
* More setup for Lumina2:Ken Moore2017-01-10
| | | | | 1) Make a new "DesktopSettings" class in libLumina for managing desktop settings files. This class understands/uses a hierarchy of files (User Overrides > System Overrides > Default Settings) and layers them as needed for the session. 2) Cleanup the new source tree a lot more, and get it *mostly* compiling (mostly just the backend classes right now - none of the desktop/WM classes yet).
* Continue the re-assembly of the desktop backend.Ken Moore2017-01-06
| | | | | Move the system tray registration/management into the XCB Event Filter class itself (since it needs access to the XCB library functions to work). This should restrict almost all use of the XCB classes to the EventFilter instance itself. Also continue moving around the source files as they are evaluated and tied into the project file. The src-screensaver and src-eventfilter directories are used now, but the src-DE and src-WM directories are still just holding cells for the files from the old lumina-desktop and lumina-wm subprojects that are not yet evaluated.
* Get some more stuff merged over. Starting to glue the various global ↵Ken Moore2017-01-05
| | | | structures together.
* Create a new "lumina-desktop-unified" core subproject (DO NOT USE)Ken Moore2017-01-04
This is just a staging area for the merging of the desktop, window manager, etc.. into a single unified application. It is highly fragmented right now and will not build *AT ALL* for a while.
bgstack15