Policies/Kdelibs Coding Style/cs - Revision history

FuzzyBot: Updating to match new version of source page

2013-04-07T18:22:45Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2012-12-08T16:50:55Z

Updating to match new version of source page

Tampakrap: Updating to match new version of source page

2012-01-23T14:53:58Z

Updating to match new version of source page

Tampakrap: Updating to match new version of source page

2011-12-22T19:59:10Z

Updating to match new version of source page

Tampakrap: Updating to match new version of source page

2011-08-23T11:40:46Z

Updating to match new version of source page

PingusPepan: Created page with "Při použití astyle (>=2.01) musíte spustit následující příkaz:"

2011-08-03T11:30:24Z

Created page with "Při použití astyle (>=2.01) musíte spustit následující příkaz:"

PingusPepan: Created page with "// správně"

2011-08-03T11:29:47Z

Created page with "// správně"

PingusPepan: Created page with "// špatně"

2011-08-03T11:29:43Z

Created page with "// špatně"

PingusPepan: Created page with "Příklad:"

2011-08-03T11:29:39Z

Created page with "Příklad:"

PingusPepan: Created page with "// správně"

2011-08-03T11:29:29Z

Created page with "// správně"

@@ Line 151: / Line 151: @@
 </syntaxhighlight>
-A related shell script could be found for unix in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs kdesdk/scripts/astyle-kdelibs] and for windows in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs.bat kdesdk/scripts/astyle-kdelibs.bat].
+You can find a shell script to run this command in:
 == Emacs and Vim scripts ==
-The "scripts" directory in the kdesdk module contains, among other useful things, some useful additions to the Emacs and Vim text editors that make it easier to edit KDE code with them.
+The [https://projects.kde.org/projects/kde/kdesdk/kde-dev-scripts/repository/revisions/master/show kde-dev-scripts] directory in the kdesdk module contains, among other useful things, some useful additions to the Emacs and Vim text editors that make it easier to edit KDE code with them.
 === Emacs ===
-The [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-emacs kde-emacs] directory contains a set of key bindings, macros and general useful code. It is compatible with both GNU Emacs and XEmacs.
+The [https://projects.kde.org/projects/kde/kdesdk/kde-dev-scripts/repository/revisions/master/show/kde-emacs kde-emacs] directory contains a set of key bindings, macros and general useful code. It is compatible with both GNU Emacs and XEmacs.
 To start using kde-emacs, add the following to your .emacs:
@@ Line 171: / Line 174: @@
 === Vim ===
-You can find a vim script in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim kdesdk/scripts/kde-devel-vim.vim] that helps you to keep the coding style correct. In addition to defaulting to the kdelibs coding style it will automatically use the correct style for Solid and kdepim code. If you want to add rules for other projects feel free to add them in the SetCodingStyle function.
+You can find a vim script in [https://projects.kde.org/projects/kde/kdesdk/kde-dev-scripts/repository/revisions/master/raw/kde-devel-vim.vim kde-devel-vim.vim] that helps you to keep the coding style correct. In addition to defaulting to the kdelibs coding style it will automatically use the correct style for Solid and kdepim code. If you want to add rules for other projects feel free to add them in the SetCodingStyle function.
 To use the script, include it in your {{path|~/.vimrc}} like this:

@@ Line 14: / Line 14: @@
 * Take useful names. No short names, except:
 ** Single character variable names can denote counters and temporary variables whose purpose is obvious
-** Variables and functions start with a lowercase letter
+* Variables and functions start with a lowercase letter
 Příklad:
@@ Line 27: / Line 27: @@
 QString errorString;
 </syntaxhighlight>
 == Whitespace ==

@@ Line 2: / Line 2: @@
 This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.
-'''In short: Kdelibs coding style follows the Qt 4 coding style.'''
+'''In short: Kdelibs coding style follows the [http://wiki.qt-project.org/Coding_Style Qt 4 coding style].'''
 == Odsazení ==
@@ Line 138: / Line 138: @@
         --one-line=keep-statements --convert-tabs \
         --indent-preprocessor \
-        `find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`
+        `find -type f -name '*.cpp'-or -name '*.cc' -or -name '*.h'`
 </syntaxhighlight>
@@ Line 147: / Line 147: @@
         --keep-one-line-statements --convert-tabs \
         --indent-preprocessor \
-        `find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`
+        `find -type f -name '*.cpp' -or -name '*.cc' -or -name '*.h'`
 </syntaxhighlight>

@@ Line 135: / Line 135: @@
 <syntaxhighlight lang="text">
 astyle --indent=spaces=4 --brackets=linux \
-        --indent-labels --pad-oper --unpad-paren \
+        --indent-labels --pad=oper --unpad=paren \
         --one-line=keep-statements --convert-tabs \
         --indent-preprocessor \
@@ Line 144: / Line 144: @@
 <syntaxhighlight lang="text">
 astyle --indent=spaces=4 --brackets=linux \
-        --indent-labels --pad-oper --unpad-paren \
+        --indent-labels --pad-oper --unpad-paren --pad-header \
         --keep-one-line-statements --convert-tabs \
         --indent-preprocessor \

← Older revision		Revision as of 11:40, 23 August 2011
Line 1:		Line 1:
		+	<languages />
	This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.		This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.

@@ Line 126: / Line 126: @@
 #include <QString>
-// correct
+// správně
 #include <QtCore/QString>
 </syntaxhighlight>

@@ Line 123: / Line 123: @@
 Příklad:
 <syntaxhighlight lang="cpp-qt">
-// wrong
+// špatně
 #include <QString>

@@ Line 87: / Line 87: @@
      qDebug("%i", i);
-// correct
+// správně
 if (true) {
      return true;