aboutsummaryrefslogtreecommitdiff
path: root/src-qt5/core/lumina-desktop-unified
Commit message (Collapse)AuthorAge
* Large amount of whitespace cleanup, and almost get the LuminaRandR class ↵Ken Moore2017-06-23
| | | | finished (one last calculation to do)
* Summary:fjs-github2017-05-11
| | | | | | | | | | | | | | | | | | | | The workspace information wasn't getting updated in the workspace-switcher-panel-plugin(wsp) when the workspace was changed via keyboard-shortcut, for example <ctrl-F2> etc. Specifically, the tooltip for the wsp would show the incorrect number for the current workspace. Details: The wsp menu always did indicate the correct workspace number because the user has to click on the wsp to display the menu. The click-action sends a signal which updates the workspace info in the menu. But, the tooltip doesn't necessarily display the correct workspace number unless the user clicks on a workspace in the menu. To reproduce the problem: 1. The current workspace is workspace 1. 2. Change to a different workspace via keyboard-shortcut, for example <ctrl-F2>. 3. Mouse-hover over the wsp and the tooltip displays the previous workspace number which is incorrect. Code Changes: The code changes are small and limited to the two source files in the desktopswitcher subdir.
* Ensure that all Lumina tools/utilities are setup with high-DPI icons.Ken Moore2017-05-01
|
* Update the new screensaver framework a bit, and add a replacement for the ↵Ken Moore2017-03-02
| | | | default "sample" screensaver: a "Fireflies" screensaver.
* Commit my work-in-progress on a new NativeWindowSystem class.Ken Moore2017-02-03
| | | | This will be a replacement for the current LuminaX11 class usage in the desktop, with a generic Qt5 API that talks to the X11/Wayland subsystems in the background.
* Another large batch of work on Lumina2:Ken Moore2017-02-01
| | | | | The NativeWindow intermediary seems to be working really well, now just to start adding the the various event detection parsing in to modify that object on-demand. There is still a window focus issue too - the setActive routine is not properly setting that window to have focus yet - need to examine further.
* Add a new "NativeWindow" class to the library. This is a pure Qt container ↵Ken Moore2017-02-01
| | | | | | class for setting/announcing changes to native windows on the system. This allows the WM class (XCB/Wayland-specific) to simply adjust each window object as needed, and the interface (pure Qt) will automatically adjust as needed. NOTE: Still need to adjust the LXCBEventFilter to use this new class, but the root window and rootsubwindow classes are all setup to use it.
* Get a lot more of Lumina2 working. Now the window embed systems are ↵Ken Moore2017-01-31
| | | | functional, with 2-way create/show/hide/close detection. Windows do not detect/resize as needed yet though.
* Get the next phase of Lumina2 working: The context menu for the desktop itself.Ken Moore2017-01-30
| | | | While not fully up to where the current contextmenu for Lumina is yet, it can be used for logging out, locking the screen, and launching commands (so far - will gradually add back in the other plugins/functionality later after these steps are used for more testing of other components).
* 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