| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
1) New libLumina classes: LuminaThemes.h
2) Single-line usage to add lumina theme usage to an application (already added to all the Lumina utilities)
3) Include a Lumina-default theme template, as well as a single color scheme (will add more later)
4) Will create a global Qt style for "lumina" so that this theme engine can be automatically applied to all Qt applications at a later date (want to make sure to beat this up and get it working reliably before turning it on for everything).
Major Features:
1) Full Qt theme capabilities through Qt stylesheets (so they can be modified and applied on the fly).
2) Stylesheets are broken into a couple pieces: an "incomplete" stylesheet file (the theme template) with variables in place of colors, font size, and font family. A "color" file which variable->value definitions for the different colors. And a themesettings.cfg files which keeps track of the files/font settings.
3) Along with this, add the ability to specify the icon theme that is used as well, and make that automatically re-loaded as necessary.
4) Add the ability to read/set thes values in lumina-config. The lumina-config usage is still a bit rough: working on cleaning it up right now.
|
| |
|
|
|
|
|
|
|
|
| |
1) Move the global.h file usage into libLumina exclusively
2) Define a new "LuminaOS::LuminaShare()" function for retrieving the install directory for Lumina (based on the PREFIX/global.h)
3) Change all the other lumina sub directories/projects to use the new LuminaShare() function when necessary.
4) This also fixes up the loading of translations in many of the subprojects (found a bug in the path used in a number of them).
Reason:
Previous implementation *only* worked if you built lumina from the base directory, causing problems with rebuilding individual pieces of Lumina. This also cleans up the general lumina projects as they only need the LuminaOS class loaded instead of knowing about this other possible OS implementation.
|
| |
|
|
|
| |
add PREFIX and LIBPREFIX to the qmake .pro files (allows to change prefix and libdir using <qmake PREFIX=/usr LIBDIR=/usr/lib/x86_64-linux-gnu/> or whatever)
update debian packaging scripts accordingly
|
| | |
|
| |
|
|
| |
1) Add the ability to browse through the directory tree for the user's home directory, with the ability to "favorite" any of them.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
UserButton:
1) When creating links, always create them in ~/.lumina/favorites
2) Scan both the Desktop and the favorites dir for favorite items
3) Distinguish between removing a link and deleting a file
4) Allow for setting links to directories
5) Allow removing links to directories
AppLauncher desktop plugin:
1) Make sure to use the session function for launching an item (makes the mouse cursor show the loading icon).
2) Allow for pre-defining a file path for the launcher (syntax: applauncher::<path to file>)
|
| |
|
|
|
|
|
|
| |
lumina-desktop.
1) Should now only reload the applications list if the installed apps changed recently, making the menu show up a ton faster.
2) Move the tabs over to the left side of the UI, and remove a lot of empty space.
3) Attempt to have the widget track the mouse and switch to a new tab on mouse-over instead of requiring a click (still in testing - no loss of functionality at the moment).
|
| | |
|
| |
|
|
|
| |
1) Add a new "All" category that is shown by default for listing applications.
2) Speed up the time to open the user menu by only reloading if more than 30 seconds have passed since the previous time it was opened.
|
| |
|
|
| |
the AppStore/ControlPanel/QtConfig shortcut definitions into the LuminaOS class for use in other OS's.
|
| | |
|
| |
|
|
|
|
| |
application have the same title: make sure to properly select the window that was clicked.
While here, also apply the libLumina dependency order to give preference to the locally/recently compiles libraries during the build if possible in all the lumina tools.
|
| |
|
| |
Change the "charging" text to "connected" instead, since if it is at %100 it is no longer technically charging....
|
| |
|
