| Commit message (Collapse) | Author | Age |
|
|
|
| |
may be set/loaded for all apps using the theme engine (including the session - which propagates to new non-lumina applications as well)
|
|
|
|
|
|
| |
Fedora packaging).
Also convert the last X11 usage in LPanel over to XCB
|
|
|
|
| |
the installation of the translation files (the translations in this repo are highly incomplete, you should use the translation files from the lumina-i18n repo instead since that is where almost all the translation work is being committed).
|
|
|
|
|
|
|
| |
- lumina-fileinfo file (where file is a not existing file) now return expected values
- lumina-fileinfo file.desktop (where file.destp is an empty file) now present the correct screen allowing users to enter values of the desktop file
Thanks to last fix, users willing to create a desktop file (via lumina-fm -> new file) in their ~/Desktop folder are able to edit it.
|
|
|
|
| |
that is new as of Qt 5.4, and some platforms (OpenBSD) do not have that version yet.
|
|
|
|
| |
editor (but leave it visible) if the file is not writable by the user.
|
|
|
|
| |
*.desktop shortcuts).
|
|
|
|
| |
removed the tabs
|
|
|
|
| |
update the port files as necessary
|
|
|
|
| |
type is supplied to the utility.
|
|
|
|
|
|
|
| |
1) Get it setup for translations
2) Update the project file to work with all the Lumina defines/locations
3) Remove the registration of the *.desktop shortcut (CLI requirements, not a stand-alone app)
4) Clean up the icon/theme usage so if the icon theme gets changed it will be updated in the utility right away.
|
| |
|
|
|
|
|
| |
The most important element is that during the loadDEsktopFile we check the content of the file.
In case the file does not contains the mandatory elements (cfr http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.1.html) we reject it and ask the user to manually (via an anoter tool) correct it, or to restart from scratch.
|
| |
|
|
|
|
|
|
| |
- detect if a field exist in different language and inform the user
- add the inMemoryFile which contains the whole lines of the config. every modifications are stored in there and once the user click "apply" the whole content goes to disk
- adapt the changes requested by the user in the inMemoryFile (no more when the user click on "Apply").
|
| |
|
|
|