TDE
/
tdesdk
mirror of https://mirror.git.trinitydesktop.org/gitea/TDE/tdesdk
0
0
Fork 0
Code Issues Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'v3.5.13-sru'
${ noResults }
tdesdk/scheck
History
Slávek Banko 16dfe83e60
Fix various cmake build issues 		12 years ago
..
CMakeLists.txt Fix various cmake build issues 12 years ago
Makefile.am Updated obsolete GPL license addresses to current GPL address 15 years ago
README Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
bitmaps.h Remove the tq in front of these incorrectly TQt4-converted methods/data members: 13 years ago
scheck.cpp Rename obsolete tq methods to standard names 12 years ago
scheck.h Rename old tq methods that no longer need a unique name 12 years ago
scheck.themerc Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
status.txt Remove the tq in front of these incorrectly TQt4-converted methods/data members: 13 years ago

README 

Scheck - An interface style to highlight accel and style guide conflicts

When starting an application with "KDE_LANG=xx application --style check"
scheck will, for text parts it checks, strip the "xx"s and display the ones
missing them (missing i18n() calls/.desktop entries) with violet background.

To use it: "program -style check". Yes, there should be a verbose README.

In short:

- Orange shows accel conflicts.
- Green proposed accels.
- Dotted red lines show nested groupboxes (not prohibited, but not favored :-).
- Potential style guide violations are marked with yellow, likely ones with red.
- Missing colons are drawn with two small red squares.
- Errors in window titles are marked with "foo|b|ar".
- Violet background show untranslated string.

Note: Not everything is checked (like list/combo box choices) and
scheck is error-prone so read HIG[*] and think before you change anything. :-)

*:http://developer.kde.org/documentation/standards/kde/style/basics/index.html