| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
it represents the desktop folder), and also verify that the monitor ID migrator works properly when the single-monitor id changes between sessions.
|
| |
|
|
| |
This will be used to determine whether to automatically show the /media files on the desktop.
|
| |
|
|
| |
Now it is properly doing calcuations in the right coordinate frame again, and saving/loading the better metrics for re-placing the items in the same place between different desktop sessions.
|
| |\ |
|
| | |
| |
| |
| | |
to be detected/shown.
|
| |/
|
|
| |
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.
|
| | |
|
| |
|
|
| |
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*).
|
| | |
|
| |
|
|
| |
This just adds a shortcut to the context menu for locking the desktop session.
|
| | |
|
| | |
|
| |
|
|
| |
This reduces the number of widgets in the stack by 1, and seems to help performance a bit.
|
| |
|
|
| |
screen number. It seems like X randomly assigns numbers to screens in some instances - resulting in multi-monitor arrays occasionally getting rotated/scrambled. After the automatic conversion of the settings to the new system (the first time the user logs into the updated version of Lumina), screen settings are tied to that particular monitor now (HDMI-0, DP-1, etc...)
|
| |
|
|
|
|
| |
1) Randomize the background image *every time* it changes.
2) Add support for per-workspace wallpaper image settings (background/filelist-workspace-<number>, where <number> is 0+ )
3) Add detection of workspace changes to the session, and update the background wallpaper on change as needed.
|
| |
|
|
|
|
| |
This impacts almost all tools/utilities within Lumina - please test (passed internal tests so far).
This cleans up a lot of the backend XDG compliance class, moving lots of functionality into child functions of the XDGDesktop class and ensuring that they get cleaned up more regularly/properly. This *seems* to make the desktop startup a lot faster, even if the overall memory savings are slight (so far).
|
| |
|
|
| |
the entry is a .desktop entry (non-binary)
|
| |
|
|
|
| |
1) Ensure that lumina-open is used to open the default terminal app (additional binary verification/checking)
2) Add some additional verification of the binary to run within lumina-open, and warn the user about a missing binary as needed.
|
| |
|
|
| |
that vertical arrangements of monitors are better supported.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a recursive, auto-generating menu which runs an external utility (a script of some kind usually), which generates a JSON document/object which is used to populate the menu.
Syntax:
(Per object)
{
"type" : "item",
"icon" : "icon name (optional)",
"action" : "something lumina-open can run (optional)"
}
Or for a recursive menu generation
{
"type" : "jsonmenu",
"exec" : "some command to run to populate menu",
"icon" : "icon name (optional)"
}
Example for a full return:
{
"Item1" : {
"type" : "item",
"icon" : "folder",
"action" : "~/item1.jpg"
},
"Menu1" : {
"type" : "jsonmenu",
"exec" : "some script",
"icon" : "system-run"
}
}
Item1 will open ~/item1.jpg with lumina-open when clicked, while Menu1 will call "some script" to generate a new menu with additional options.
}
|
| |
|
|
|
| |
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) Cleanup a compile warning in LDesktopBackground.cpp
2) Ensure the desktop re-themes when the theme changes (another leftover from changing the binary name)
3) Setup the appmenu and userbutton panel plugin to try and register themselves as "Start buttons" for the purpose of keyboard shortcuts opening them on demand.
|
| |
|
|
| |
registering/finding the default email/terminal applications.
|
| |
|
|
| |
Generate a QPixmap and use it during paintEvent
|
| | |
|
|
|
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.
|
