| Commit message (Collapse) | Author | Age |
|---|
| |\ |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
| |
(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.
|
| | |
|
| |
|
|
| |
This reduces the number of widgets in the stack by 1, and seems to help performance a bit.
|
| | |
|
| |
|
|
| |
(not the start menu options yet).
|
| |
|
|
| |
start-lumina-desktop).
|
| |
|
|
|
| |
1) Move the "runtime" directory in the users home to the XDG_CONFIG_HOME/lumina-desktop rather than ~/.lumina
2) Update the Glass theme a bit more.
|
| |
|
|
|
| |
1) Move from "NO_I18N" to "WITH_I18N". This will ensure that the source version of the localizations are not installed unless explicitly requested (since the "real" localization files are in the lumina-i18n repo - these source files are theauto-generated ones before getting sent up to the pootle localization system).
2) Add a few more .desktop files for the various Lumina utilities.
|
| |
|
|
| |
start-menu-like plugins to determine whether they should respond to a show command, and setup all the systemstart plugins to use this system (will expand later to the appmenu and userbutton plugins as well).
|
| |
|
|
| |
menu is closed right away.
|
| |
|
|
| |
aligned with the y=0 axis for the top of the monitor.
|
| |
|
|
| |
update the screen numbers/geometries 50ms after the WM changes the _NET_DESKTOP_GEOMETRY or _NET_WORKAREA properties on it. This bypasses a bug in the QDesktopWidget class where it might not send out the changed() signals when something really did change (noticed this in virtualbox instances in particular).
|
| |
|
|
| |
applications. This prepares us to use a "real" Qt style plugin for application appearances instead of stylesheets for a few lumina-* apps.
|
| |
|
|
|
|
| |
sequentual loading of various utilities (WM, DE, screensaver, compositing manager, etc..)
Also setup lumina-session to auto-start xcompmgr if it is installed, and adjust the Lumina-DE.desktop xsession entry to launch the session instead of the Lumina-DE binary directly.
|
|
|
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.
|
