summaryrefslogtreecommitdiffstats
path: root/.reuse/dep5 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* UI: move icons from default into colorful theme.Kyle Kienapfel2022-09-161-2/+4
| | | | | | | | | colorful theme has been default theme for awhile. having colorful theme try and grab icons from other theme doesn't work on Linux. Also adding two additional icons, info is to hint to the user that they should hit verify after pasting in a token, sync is to show that the verification is occurring.
* qt_themes: Add colorful and dark mode sd card iconsMorph2022-09-131-3/+2
|
* Moving Icons away from CC BY-ND 3.0 for FOSS packaging purposesKyle Kienapfel2022-08-141-14/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've seen some comments stating that sharing pre-compiled packages of yuzu is problematic for linux distributions due to some contents having license of CC BY-ND 3.0 Better licensed sources of icons have been found for most cases, see the changes to the .reuse/dep5 file for details. Placeholders for connected/disconnected icons At the time of writing I consider these icons to be placeholders, hence three copies. colorful is grey, default is black, qdarkstyle is white connected is gnome/16x16/network-idle.png with no changes connected_notification is gnome/16x16/network-error.png with changes disconnected is gnome/16x16/network-offline.png with changes Looking at licenses: GNOME icon theme is distributed under the terms of either GNU LGPL v.3 or Creative Commons BY-SA 3.0 license. Debian appears to explicitly state they're licensing under Creative Commons Attribution-Share Alike 3.0 From a tarball at the following link suggests we can just attribute GNOME Project https://download.gnome.org/sources/gnome-icon-theme/ When attributing the artwork, using "GNOME Project" is enough. Please link to http://www.gnome.org where available. CC-BY-SA-3.0.txt from https://creativecommons.org/licenses/by-sa/3.0/legalcode.txt
* Merge pull request #8647 from Docteh/default_darkliamwhite2022-08-121-6/+4
|\ | | | | Linux: handle dark system themes nicely
| * Linux: handle dark system themes nicelyKyle K2022-08-051-6/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | yuzu's default theme doesn't specify everything, which is fine for windows, but in linux anything unspecified is set to the users theme. Symptoms of this are that a linux user with a dark theme won't think to change the theme to a dark theme when first using yuzu Idea here is to try and support arbitrary themes on linux. preliminary work on a "default_dark" theme, used only as overlay for any themes that are measured to be dark mode. Other work done: FreeDesktop standard icon names: plus -> list-add delete refresh, we use view-refresh remove duplicated icons for qdarkstyle_midnight_blue referencing icon aliases in the qrc files is the way to go Note: Dynamic style changing doesn't appear to work with AppImage
* | Merge pull request #8499 from Docteh/pluralsbunnei2022-08-101-1/+2
|\ \ | |/ |/| Translate english plurals
| * Translate english pluralsKyle Kienapfel2022-07-301-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Turns out that for Qt to properly handle plurals in English a translation needs to be provided, otherwise the user is left with messages such as "Building: 2 shader(s)" Plurals for other all other languages are handled on transifex. I wrote the README.md to just refer to it as a translation collaboration site just in case we ever switch. These translations being out of date won't pose any technical problems so I believe it is fine to handle them manually on a "best effort" basis. The files are generated into the source directory so that the relative filenames are correct. The generated file is added to .gitignore
* | ci: use dep5 for GitHub issue template filesLiam2022-07-291-0/+8
|/
* chore: make yuzu REUSE compliantAndrea Pappacoda2022-07-271-0/+106
[REUSE] is a specification that aims at making file copyright information consistent, so that it can be both human and machine readable. It basically requires that all files have a header containing copyright and licensing information. When this isn't possible, like when dealing with binary assets, generated files or embedded third-party dependencies, it is permitted to insert copyright information in the `.reuse/dep5` file. Oh, and it also requires that all the licenses used in the project are present in the `LICENSES` folder, that's why the diff is so huge. This can be done automatically with `reuse download --all`. The `reuse` tool also contains a handy subcommand that analyzes the project and tells whether or not the project is (still) compliant, `reuse lint`. Following REUSE has a few advantages over the current approach: - Copyright information is easy to access for users / downstream - Files like `dist/license.md` do not need to exist anymore, as `.reuse/dep5` is used instead - `reuse lint` makes it easy to ensure that copyright information of files like binary assets / images is always accurate and up to date To add copyright information of files that didn't have it I looked up who committed what and when, for each file. As yuzu contributors do not have to sign a CLA or similar I couldn't assume that copyright ownership was of the "yuzu Emulator Project", so I used the name and/or email of the commit author instead. [REUSE]: https://reuse.software Follow-up to 01cf05bc75b1e47beb08937439f3ed9339e7b254