Search results
- ...t]. KDE's [https://techbase.kde.org/Projects/Usability/HIG Human Interface Guidelines] provide many useful tips how you can create intuitive user interfaces with - general guidelines: units, iconSizes, ...41 KB (6,386 words) - 09:34, 18 April 2023
- == Guidelines == ...39 KB (6,015 words) - 19:59, 19 April 2021
- KDE software development usually follows the Human Interface Guidelines HIG: http://techbase.kde.org/Projects/Usability/HIG ...18 KB (2,979 words) - 01:43, 16 February 2015
- Instead it was agreed to better document the existing informal guidelines like: ...14 KB (2,182 words) - 10:36, 9 July 2010
- == Guidelines == ...ase. We want, also, to create a cohesive ecosystem of resources and design guidelines that can be easily reused. Main goal of this project is to enhance the exis ...60 KB (9,405 words) - 00:41, 14 March 2019
- ...ttp://qt-project.org/wiki/Writing_Qt_Examples Writing Qt Examples] - style guidelines for examples ...ckr || demos/flickr || Exe || Demo || This demo is used in the QML porting guidelines. || ...63 KB (7,586 words) - 13:17, 27 November 2012
- == Guidelines == ...48 KB (7,487 words) - 16:57, 22 August 2023
- == Guidelines == ...Maps on Android follows the Google [https://material.io/ Material Design] Guidelines ...58 KB (8,854 words) - 13:36, 27 November 2017
- * guidelines (with code support) for consistent looking rows of different widgets (e.g. ...16 KB (2,341 words) - 23:55, 26 July 2010
- Replace <tt>[version]</tt> with an appropriate version string; see [[Guidelines and HOWTOs/Write a version string]] to find out how to write one. If you ca ...24 KB (4,082 words) - 01:54, 12 July 2020
- ...t be documented as per the [http://dep.debian.net/deps/dep3/|Patch Tagging Guidelines]. In particular the fields ''Forwarded'' and ''Reviewed-by'' must be presen ...23 KB (3,550 words) - 15:05, 23 June 2020
- == Guidelines == ...54 KB (8,293 words) - 16:54, 22 August 2023
- = Guidelines = .... You can find the guidelines here: http://community.kde.org/Commit_Digest/Guidelines ...122 KB (18,582 words) - 10:56, 20 March 2013
- *Every file should have a file-level comment. This is suggested in the KDE guidelines anyway -- near the top of your file, write down what the file is for, vague ...28 KB (4,658 words) - 13:01, 12 June 2023
- == Guidelines == ...67 KB (10,614 words) - 10:38, 9 March 2016
- == Guidelines == ...65 KB (10,314 words) - 09:04, 18 February 2015
- * [https://hig.kde.org/ KDE Human Interface Guidelines] ...22 KB (835 words) - 13:00, 25 April 2022
- == Guidelines == ...80 KB (12,522 words) - 09:21, 30 March 2013
- == Guidelines == ...76 KB (11,914 words) - 21:54, 8 August 2013
- ...uld like all the SIGs to fill in their results here. The results of the UI guidelines SIG should already be on developer.kde.org, and as I wrote above, the resul ...26 KB (4,537 words) - 14:02, 7 February 2010