| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
1. Adjust the pkg-plist for FreeBSD to include the trident-dark color file.
2. Add a new function for fetching XDG standard directory paths (and create dir as needed)
3. Setup the desktop and lib classes to use the XDG standard path function now.
4. Add a bunch of fallback icons if the "start-here-lumina" icon could not be found in the current theme. These are all based on the OS name.
5. Ensure we run "xdg-user-dirs-update" before launching the session (if it is installed). This is used for the main standard dir detection.
6. Ensure that start-lumina-desktop *always* starts a new desktop session (bypassing any existing lock files for the desktop session).
|
|
|
|
| |
the screen session was resized.
|
| |
|
|
|
|
| |
This should make it generic enough to support all XDG icon themes.
|
|
|
|
|
|
| |
1. Ensure that reading the file to be used for the chime is done correctly.
2. Ensure that the session does not crash during cleanup if the exit chime could not be played.
3. Ensure that the default audio chime files are used if nothing else is specified/valid in the settings.
|
|
|
|
|
| |
When moving the owner of the clipboard over to the desktop session, we need to copy *all* of the data on the clipboard, not just the text.
Very often, text on the clipboard is "paired" with control codes or alternate info in other mimetype fields.
|
| |
|
|
|
|
| |
This includes some larger changes to lumina-pdf, and some fixes for the 1.x session (battery chimes and such)
|
| |
|
|
|
|
| |
This reverts commit 4455528cd9cd0b0594c3bcabf619a50e64e37832.
|
| |
|
|
|
|
| |
Ensure that the lumina theme engine is always set in the session environment unless manually replaced/removed in the session settings.
|
|
|
|
| |
external process.
|
|
|
|
| |
Got the "init" time from ~4.2 seconds to ~0.6 seconds on my laptop.
|
|
|
|
| |
Now the user files are scanned/created from within the start-lumina-desktop process, not the desktop process. This fixes the loading of the theme engine for the desktop process on first-run situations, and also ensures that the desktop process does not need to make any major changes to it's configs while it is still running.
|
|
|
|
| |
is completely deleted.
|
| |
|
|
|
|
| |
QApplication instance.
|
| |
|
|
|
|
| |
Lumina 1, and also fix the pkg plist so it includes the qss files.
|
|
|
|
| |
"ExternalProcess" class can provide a better way of doing that on a per-process basis.
|
|\ |
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
(for now - needs more testing).
|
|
|
|
| |
scfb) to a non-"default" ID.
|
|
|
|
| |
It looks like the OS-specific functionality to save/restore the last audio setting is borked, so I bypassed it with a lumina-specific "session state" value in the user's settings file.
|
|
|
|
| |
the volume reset on login is not consistent.
|
|
|
|
| |
"applauncher" plugins. This seems to be working quite well, and now we just need to start using this for all the other pieces of the desktop.
|
|
|
|
| |
After testing this more robustly and with more variations, the issue appears to be so ingrained into the Fluxbox state/property event handling that anything we do from the Lumina side is quickly overwritten/ignored by Fluxbox.
|
| |
|
| |
|
|
|
|
| |
to another on the first start of the desktop, and enable that migration for single-monitor arrangements.
|
|\ |
|
| | |
|
|/
|
|
|
| |
Now whenever a screen is added/changed it will print out the physical/logical DPI values into the log, and if a logicalDPI (X or Y) is greater than 110 it will enabled the Qt5 auto-scale functionality.
Note: My 1080p laptop monitor has a logical DPI of ~96, but a physical DPI of ~150 and the Qt5 auto-scale stuff is based on physical DPI (so things got massive on a normal-res screen). I am leaving the DPI print-out in the logs for now so that if we run into any other monitors where the logicalDPI>110 rule is invalid we can view/tweak the rule really easily.
|
|
|
|
| |
This needs to be set for applications, but not the desktop itself (since there are so many pixel-specific calculations that need to be performed).
|
|
|
|
| |
for re-reading the /media directory as well.
|
|
|
|
| |
will be very useful for systems that auto-create dirs in /media when devices are attached to the system, and mount-on-demand when browsing into that directory (*SPOILERS*).
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
file/list changes*.
|
|
|
|
| |
tips for Lumina itself (avoids strange stuff from fortune, and ensures information which is at least semi-useful for the user).
|
|
|
|
| |
accent the rest of the UI.
|
|
|
|
| |
auto-started apps by 1/2 second.
|
|
|
|
|
|
|
| |
1) Dismantle the Lumina library completely.
2) Setup lots of small subproject files (.pri) for the individual classes within the old library.
3) Move all the Lumina binaries to use the new subproject files
4) Split up the LuminaUtils class/files into LUtils and LDesktopUtils (generic utilities, and desktop-specific utilities)
|
|
|
|
|
|
| |
Qt5_theme_engine=<some theme engine>
This will allow the user to set some global Qt5 theme engine (such as qt5ct), and activate it for the entire session.
|
|
|
|
| |
them in that case.
|
|
|
|
|
|
| |
1) for the "low" battery icon, move it down to the 5-20% range instead of 20-50%.
2) When battery is between 0-5%, change the background color of the icon to red in addition to the "warning" battery icon.
3) Play an audio file when the battery drops to the 0-5% range( <Lumina Share directory>/low-battery.ogg), if the file exists.
|