| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
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.
|
