| Commit message (Collapse) | Author | Age |
| |
|
|\ |
|
| |
| |
| |
| | |
icon set (no longer rely on the "oxygen" icon set).
|
| |
| |
| |
| | |
*-x-generic icon)
|
|/
|
|
|
| |
1) Better support for the "inherited" property in icon themes
2) Some other random WM stuff
|
| |
|
| |
|
| |
|
|
|
|
| |
manage it)
|
|
|
|
| |
registration, window create/close handling, etc)
|
| |
|
|
|
|
| |
class (associated with the much more static "class" name from X11 - use the Title/ShortTitle properties for the ones that change regularly).
|
|
|
|
| |
NativeWindowSystem (GlobalPos, Size, MinSize, MaxSize)
|
|
|
|
| |
ShortTitle, Icon)
|
|
|
|
| |
init routine all ported over, and start filling in the mouse/key handling routines.
|
|
|
|
| |
(close, kill, ping).
|
|
|
|
|
|
|
|
| |
1) Handle all property changes in bulk groups for efficiency
2) Add simplification functions for changing single properties.
3) Automatically prune redundant property settings from signals
4) Add another property or two, and simplify the number of "extra" signals/functions for non-property changes/requests.
5) Starting cleaning up the new NativeWindowSystem class to use the new plumbing, and get it ready for the XCB "guts" to be copied in.
|
|
|
|
| |
respected, and the border extents have been standardized.
|
|
|
|
| |
classes). This seems to be working much better so far - still need to finish filling out the various interaction functions and themeing (stylesheet object names done).
|
|
|
|
|
| |
1) Add the ability for plugins to set their own high-priority context menu, and put the plugin modification menu into that as needed.
2) For the applauncher plugin, generate a custom context menu specifically for the file in question. This may include the various "actions" in .desktop files as appropriate, and also adds shortcuts for launch, open, open-with, file properties, and delete file.
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| | |
| | | |
add more compatibility for Slackware
|
| | | |
|
| | | |
|
|/ /
| |
| |
| | |
It looks like the newer version does not like the window workspace assignment to be "-1" any more, it starts to lose it's mind and treat windows really weird now. Just use workspace 0 instead for now, and hope that Fluxbox continues to respect the window "sticky" settings for the forseeable future.
|
| |
| |
| |
| | |
the various options that are available.
|
| |
| |
| |
| | |
device detection routines.
|
| |
| |
| |
| |
| |
| | |
getting there.
Also commit a simple "test" app which can be modified/used to test out individual library classes as needed.
|
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
client message asking it to take focus properly as well.
|
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
| |
functional, with 2-way create/show/hide/close detection. Windows do not detect/resize as needed yet though.
|
|
|
|
| |
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).
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
lumina-desktop-unified build. Also finish cleaning up the compilation of the lumina-desktop-unified project - still not ready for actual testing yet.
|
|
|
|
| |
virtual root functionality with all wallpaper painting routines embedded within.
|
|
|
|
| |
they block off the replacement within double quotes instead of single-quotes.
|
|
|
|
| |
of the LuminaOS class, but is not hooked in to be used yet.
|
|
|
|
| |
the exact function to call to detach a live process from a QProcess.
|
|
|
|
|
| |
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).
|
|
|
|
| |
specifically designed for launching external processes in an unattended manner and automatically cleaning up the object on the heap when finished. It will also hide any output from the process or forward it to a designated log file rather than polluting the current process output channel.
|
|
|
|
| |
the recent 1.2.0 release.
|
| |
|
|
|
|
|
|
| |
QString generateExec(QStringList inputfiles, QString ActionID);
This will automatically evaluate the input file's syntax and adjust as needed for the application to recognize/run the file. Similarly it will perform all the substitutions and such as necessary to end up with a fully-formatted executable command which can easily be launched with QProcess as necessary.
|