| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
"Disk I/O"
|
| |
|
|
| |
icon should always match what was requested for the button.
|
| |
|
|
|
|
|
| |
1) Adjust the font outlines quite a bit more - now it properly respects the theme settings and adjusts appropriately.
2) Add options to re-size all the desktop icons at the same time (use 16 pixel increments)
3) Adjust the default desktop icon size (use a 64x64 icon be default).
4) Ensure that the applauncher re-scales the icon as necessary to ensure it is the proper size.
|
| |
|
|
| |
readable in all situations/backgrounds, as well as accounting for the change in thickness to ensure that the text is not cut off at the edge of the box.
|
| | |
|
| |
|
|
| |
for any text. This still needs a bit of tweaking, but overall seems to work quite well.
|
| |
|
|
| |
file as well. Also remove the "sample" desktop plugin from being included in the build.
|
| |
|
|
|
|
| |
1) Make sure the calendar desktop plugin updates the date occasionally.
2) Add the framework for a custom-painted Toolbutton for the applauncher plugin. This will be used to ensure font outlines in the near future.
3) Another small adjustment for new window geometries - run the overall adjustment first - then re-check and see if the window is off the top of the screen before trying the fallback movement routine.
|
| |
|
|
|
|
|
|
|
| |
- Now the desktop plugins are drag-and-drop based, resulting in the user being able to simply drag the plugins around as necessry.
- All the plugins now have a special context menu (right-click, or click and hold the left mouse button for 1/2 second), which provides options to start moving/resizing the plugin as well as the removal option.
Known Issues:
- The cross-application drop event for files is currently flagged as valid - but does not actually run anything yet (to be finished up soon)
- Hidden panels are not being updated when plugins are moved around yet - resulting in some screen artifacting on the panel. (to be fixed soon)
|
| |
|
|
| |
desktopview plugin a bit more.
|
| |
|
|
| |
to the grid, item sizes are a bit bigger than the icon width, and the icon increase/decrease code works better.
|
| |
|
|
| |
routines may be added (only used for some applaunchers right now). This now makes a desktop icon which was explicitly closed/removed by the user also delete the file from the desktop folder (instead of having that plugin get re-created at a later time)
|
| |
|
|
| |
theme changes.
|
| |
|
|
| |
their text/icons when the system locale is changed.
|
| |
|
|
|
|
| |
1) Switch some X11->XCB functions around (SetAsDesktop(), SetDisableWMActions()).
2) Fix up some QtQuick plugin detection routines (now it will properly see the user's quickplugins if any).
3) Connect the status change signal/slots for QtQuick plugins to try and detect script failures and remove the script (still not working reliably).
|
| |
|
|
| |
to implement my own tiling algorithm for initial plugin placements (and adjust a lot of the plugins to have better auto-set default sizes depending on font settings)
|
| |
|
|
| |
system. Also add a default size for the calendar plugin.
|
| | |
|
| | |
|
| |
|
|
| |
created/arranged initially. Now the desktopview should be oriented the proper way, and the applauncher icons should be the proper size (although they are still not being placed in non-overlapping locations yet).
|
| |
|
|
| |
consistency and proper size calculations (especially for new plugins).
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
watchers:
1) Move the ~/Desktop directory watcher into the Session (no extra overhead, already have a watcher there), and have te session send out signals when the contents of the ~/Desktop dir change.
2) Setup the plugins that poll the desktop to use the new session implementation (reducing overhead overall)
3) Add the ability to use files/dirs in the "applauncher" plugin as well (not exposed to user yet)
4) Add a new desktop flag for auto-creating applauncher plugins for any files/dirs on the desktop (not added to lumina-config yet)
5) Get rid of all the config files for the desktop plugins and merge them all together into a single conf file that the session maintains the pointer to (so plugins can grab that pointer as necessary)
6) Make sure that desktop plugins go through a special [read/save]Setting() functions in the plugin implementation itself so that they don't accidentally trample other plugin settings (keeps it restricted to the particular group for that plugin)
|
| |
|
|
| |
pluins. It appears that there is a fundamental issue with embedding QML objects into a panel/window with the "always on top" flag set - it never finishes painting the QML object and prevents the rest of the panel from being updated as well.
|
| |
|
|
|
|
| |
respectively).
These are QtQuick "containers" which allow the loading of user/system supplied QML scripts for non-compiled plugin support. These plugins must be single *.qml files located in <Lumina Share>/quickplugins/*.qml or ~/.lumina/quickplugins/*.qml
|
| |
|
|
|
| |
This returns the current stats about the available disks on the system (current read/write rates on FreeBSD - not implemented on other OS's yet).
Also use this new function in the systemmonitor desktop plugin.
|
| |
|
|
| |
just files)
|
| |
|
|
| |
plugins to all use that for checking whether a thumbnail can be shown. Also add thumbnail support into the user button for favorite files.
|
| |
|
|
| |
initialization. Something about the addition processEvents() call is screwing up the init procedures.
|
| |
|
|
| |
(only able to reproduce on a 11.x VM).
|
| | |
|
| |
|
|
| |
add a new desktop plugin for monitoring system statistics (CPU/Mem usage, CPU temps).
|
| |
|
|
|
|
| |
1) Remove the Qt "UniformItemSizes" flag, and instead force particular grid sizing for items (fixes issue with entire grid being re-adjusted to smallest icon size).
2) Add the ability for two lines of text underneath each icon, with the string elided and split as necessary to fit.
3) If there is a natural word break in the file name, use that for the lines and elide each line individually.
|
| | |
|
| |
|
|
| |
desktop plugin widgets by the name of the plugin. Leaving this disabled by default until some more testing is performed to see how well it works.
|
| |
|
|
|
|
|
|
| |
1) Desktop plugins are not getting removed.
- This appears to be a bug in Qt 5.4.1 from what I can tell (any window buttons in the QMdiSubWindow are non-responsive), but for the moment the user can right-click on the plugin titlebar and select "close" from the menu for the same effect. I have fixed a couple edge cases/situations where forcibly closing/removing a desktop plugin will crash the session (it behaves properly in all situations now from my testing).
2) Disable the panel location limitations in lumina-config since with the new lenght settings it is possible to place panels in any location now (such as two panels on the top - one pinned left and the other pinned right).
3) Fix up the desktop plugin area calculations so they properly handle panels in any configuration.
4) If the desktop area was re-configured, go through and adjust the location/sizing of any desktop plugins (to ensure that they are all within the available space - use the grid alignment procedure).
|
| |
|
|
| |
the selected directory. Also enable the use of lumina-fileinfo for *any* file within the desktopview plugin.
|
| |
|
|
| |
active window and then re-activate that other window when the mouse leaves the panel.
|
| |
|
|
| |
desktopview plugin (does not support other types of files yet).
|
| |\ |
|
| | |
| |
| |
| | |
Also update the port makefile for FreeBSD so that has the proper gstreamer plugins installed for audio support.
|
| |/ |
|
| |
|
|
| |
desktop plugin.
|
| |
|
|
| |
update/change the current UI for a programmatic save of the info to disk.
|
| |
|
|
|
|
|
|
|
| |
to the desktopview plugin:
1) Multi-item selection
2) cut/copy files to clipboard
3) delete files
4) increase/decrease icon sizes
|
| | |
|
| |
|
|
| |
for non-valid *.desktop files.
|
| |
|
|
| |
synctimer when the plugin is closed/removed.
|
| |
|
|
| |
plugin interactions).
|
| |
|
|
| |
transparent/opaque on a plugin-level. This allows for finer control via the theme.
|
