KDE TechBase - User contributions [en]

Development/FAQs/General FAQ/pl

2012-06-28T05:18:07Z

Toudidel: Created page with "Przed rozpoczęciem pisania nowej aplikacji zawsze dobrym pomysłem jest zajrzenie do [http://www.kde-apps.org/ KDE-Apps.org], aby przejrzeć istniejące aplikacje i zapytać na ..."

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Przed rozpoczęciem pisania nowej aplikacji zawsze dobrym pomysłem jest zajrzenie do [http://www.kde-apps.org/ KDE-Apps.org], aby przejrzeć istniejące aplikacje i zapytać na liście mailingowej [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel], czy przypadkiem ktoś inny nie pracuje nad czymś podobnym.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice i KDevelop, mimo że bardzo popularne, mają niewielu programistów, więc możesz sprawdzić się tam. Nie ma potrzeby pomocy jako core-developer. KDE jest modułowy, więc doskonale możesz usprawniać jakis jeden obszar bez znajomości, jak działa cały system.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==Nie chcę stracić mojej historii SVN==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==Co to jest kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?==

Tak, sprawdź w dokumentacji Building 2 Versions

==Skąd mam wiedzieć, której wersji Qt/KDE używam?==

<tt>kde-config</tt> i w ogóle wszystkie programy kde akceptują <tt>--version</tt> jako argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==Jak mogę utworzyć klucz SSH?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==Jak mogę monitorować zmiany dokonane przez innych?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/5/pl

2012-06-28T05:18:07Z

Przed rozpoczęciem pisania nowej aplikacji zawsze dobrym pomysłem jest zajrzenie do [http://www.kde-apps.org/ KDE-Apps.org], aby przejrzeć istniejące aplikacje i zapytać na liście mailingowej [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel], czy przypadkiem ktoś inny nie pracuje nad czymś podobnym.

Development/FAQs/General FAQ/pl

2012-06-28T05:16:32Z

Toudidel: Created page with "KOffice i KDevelop, mimo że bardzo popularne, mają niewielu programistów, więc możesz sprawdzić się tam. Nie ma potrzeby pomocy jako core-developer. KDE jest modułowy, wi..."

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice i KDevelop, mimo że bardzo popularne, mają niewielu programistów, więc możesz sprawdzić się tam. Nie ma potrzeby pomocy jako core-developer. KDE jest modułowy, więc doskonale możesz usprawniać jakis jeden obszar bez znajomości, jak działa cały system.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==Nie chcę stracić mojej historii SVN==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==Co to jest kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?==

Tak, sprawdź w dokumentacji Building 2 Versions

==Skąd mam wiedzieć, której wersji Qt/KDE używam?==

<tt>kde-config</tt> i w ogóle wszystkie programy kde akceptują <tt>--version</tt> jako argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==Jak mogę utworzyć klucz SSH?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==Jak mogę monitorować zmiany dokonane przez innych?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/7/pl

2012-06-28T05:16:31Z

KOffice i KDevelop, mimo że bardzo popularne, mają niewielu programistów, więc możesz sprawdzić się tam. Nie ma potrzeby pomocy jako core-developer. KDE jest modułowy, więc doskonale możesz usprawniać jakis jeden obszar bez znajomości, jak działa cały system.

Translations:Off-line Translation/9/pl

2012-06-27T22:09:00Z

Toudidel: Created page with "Category:Translator_Help"

[[Category:Translator_Help]]

Off-line Translation/pl

2012-06-27T22:08:54Z

Toudidel: Created page with "* Użyj linku <menuchoice>Prześlij plik</menuchoice> na pasku bocznym, aby zaimportować plik. * W polu New Imports umieść nazwę importowanego pliku. * Kiedy okaże się,..."

<languages />

Zakładamy, że jeśli zamierzasz tłumaczyć w trybie offline, to masz jakieś doświadczenie z '''Lokalize''' lub podobnym narzędziem, dlatego ta strona dotyczy wyłącznie tłumaczenia w trybie online.

== Zasady pracy ==

* Poproś o dodanie do grupy tłumaczy (grupa Translator):
** Kliknij [[Special:myLanguage/Translator Account|Załóż konto tłumacza]] na pasku bocznym
** Kliknij na zakładce <menuchoice>Edytuj</menuchoice> i wpisz swoją nazwę użytkownika, język, na który chciałbyś tłumaczyć i czy jesteś zainteresowany tłumaczeniem w trybie offline
** Użyj opcji <menuchoice>Zapisz stronę</menuchoice>, aby zapisać informacje
* Kiedy użytkownik zostanie dodany do grupy (powinieneś dostać powiadomienie e-mailem), kliknij [[Special:LanguageStats|Rozpocznij tłumaczenie]] na pasku bocznym
* Wprowadź język, na który chcesz tłumaczyć w polu <menuchoice>Kod języka </menuchoice> i kliknij <menuchoice>Rozpocznij</menuchoice> (możesz zaznaczyć, by nie były pokazywane strony przetłumaczone w 100%)
* Wybierz stronę, którą chciałbyś się zająć - zostaniesz przeniesiony do narzędzia, w którym możesz tłumaczyć (w trybie online i offline)
* Aby zmniejszyć ryzyko konfliktów podczas edycji, przesyłaj swoją pracę dość często. Potem możesz kontynuować na innych sekcjach pobranego pliku - procedura importu będzie wiedzieć, które sekcje są nowe.

==Eksport strony==

* Na liście rozwijanej <menuchoice>Chcę...</menuchoice> powinna być wybrana opcja <menuchoice>Eksportuj tłumaczenie w formacie Gettext</menuchoice>.
* Sprawdź, czy nazwa strony i język są poprawnie ustawione.
* <menuchoice>Rozpocznij</menuchoice> uruchomi eksport.

===Importuj nowe tłumaczenie===

Na początku poprosimy Cię, abyś przysłał plik z tłumaczeniem do nas. Oto jak to zrobić:

* Użyj linku <menuchoice>Prześlij plik</menuchoice> na pasku bocznym, aby zaimportować plik.
* W polu [[New Imports]] umieść nazwę importowanego pliku.
* Kiedy okaże się, że nie ma żadnych problemów, pokażemy Ci, jak w przyszłości bezpośrednio przesyłać pliki z tłumaczeniami.

[[Category:Translator_Help]]

Translations:Off-line Translation/8/pl

2012-06-27T22:08:53Z

* Użyj linku <menuchoice>Prześlij plik</menuchoice> na pasku bocznym, aby zaimportować plik.
* W polu [[New Imports]] umieść nazwę importowanego pliku.
* Kiedy okaże się, że nie ma żadnych problemów, pokażemy Ci, jak w przyszłości bezpośrednio przesyłać pliki z tłumaczeniami.

Off-line Translation/pl

2012-06-27T22:06:36Z

Toudidel: Created page with "Na początku poprosimy Cię, abyś przysłał plik z tłumaczeniem do nas. Oto jak to zrobić:"

<languages />

Zakładamy, że jeśli zamierzasz tłumaczyć w trybie offline, to masz jakieś doświadczenie z '''Lokalize''' lub podobnym narzędziem, dlatego ta strona dotyczy wyłącznie tłumaczenia w trybie online.

== Zasady pracy ==

* Poproś o dodanie do grupy tłumaczy (grupa Translator):
** Kliknij [[Special:myLanguage/Translator Account|Załóż konto tłumacza]] na pasku bocznym
** Kliknij na zakładce <menuchoice>Edytuj</menuchoice> i wpisz swoją nazwę użytkownika, język, na który chciałbyś tłumaczyć i czy jesteś zainteresowany tłumaczeniem w trybie offline
** Użyj opcji <menuchoice>Zapisz stronę</menuchoice>, aby zapisać informacje
* Kiedy użytkownik zostanie dodany do grupy (powinieneś dostać powiadomienie e-mailem), kliknij [[Special:LanguageStats|Rozpocznij tłumaczenie]] na pasku bocznym
* Wprowadź język, na który chcesz tłumaczyć w polu <menuchoice>Kod języka </menuchoice> i kliknij <menuchoice>Rozpocznij</menuchoice> (możesz zaznaczyć, by nie były pokazywane strony przetłumaczone w 100%)
* Wybierz stronę, którą chciałbyś się zająć - zostaniesz przeniesiony do narzędzia, w którym możesz tłumaczyć (w trybie online i offline)
* Aby zmniejszyć ryzyko konfliktów podczas edycji, przesyłaj swoją pracę dość często. Potem możesz kontynuować na innych sekcjach pobranego pliku - procedura importu będzie wiedzieć, które sekcje są nowe.

==Eksport strony==

* Na liście rozwijanej <menuchoice>Chcę...</menuchoice> powinna być wybrana opcja <menuchoice>Eksportuj tłumaczenie w formacie Gettext</menuchoice>.
* Sprawdź, czy nazwa strony i język są poprawnie ustawione.
* <menuchoice>Rozpocznij</menuchoice> uruchomi eksport.

===Importuj nowe tłumaczenie===

Na początku poprosimy Cię, abyś przysłał plik z tłumaczeniem do nas. Oto jak to zrobić:

* Use the <menuchoice>Upload file</menuchoice> link in the sidebar to import your file.
* Place a message on [[New Imports]] giving the filename of the upload.
* Once we have confirmed that there are no problems we will show you how to upload your own future translations.

[[Category:Translator_Help]]

Translations:Off-line Translation/7/pl

2012-06-27T22:06:36Z

Toudidel: Created page with "Na początku poprosimy Cię, abyś przysłał plik z tłumaczeniem do nas. Oto jak to zrobić:"

Na początku poprosimy Cię, abyś przysłał plik z tłumaczeniem do nas. Oto jak to zrobić:

Off-line Translation/pl

2012-06-27T22:05:38Z

Toudidel: Created page with "===Importuj nowe tłumaczenie==="

<languages />

Zakładamy, że jeśli zamierzasz tłumaczyć w trybie offline, to masz jakieś doświadczenie z '''Lokalize''' lub podobnym narzędziem, dlatego ta strona dotyczy wyłącznie tłumaczenia w trybie online.

== Zasady pracy ==

* Poproś o dodanie do grupy tłumaczy (grupa Translator):
** Kliknij [[Special:myLanguage/Translator Account|Załóż konto tłumacza]] na pasku bocznym
** Kliknij na zakładce <menuchoice>Edytuj</menuchoice> i wpisz swoją nazwę użytkownika, język, na który chciałbyś tłumaczyć i czy jesteś zainteresowany tłumaczeniem w trybie offline
** Użyj opcji <menuchoice>Zapisz stronę</menuchoice>, aby zapisać informacje
* Kiedy użytkownik zostanie dodany do grupy (powinieneś dostać powiadomienie e-mailem), kliknij [[Special:LanguageStats|Rozpocznij tłumaczenie]] na pasku bocznym
* Wprowadź język, na który chcesz tłumaczyć w polu <menuchoice>Kod języka </menuchoice> i kliknij <menuchoice>Rozpocznij</menuchoice> (możesz zaznaczyć, by nie były pokazywane strony przetłumaczone w 100%)
* Wybierz stronę, którą chciałbyś się zająć - zostaniesz przeniesiony do narzędzia, w którym możesz tłumaczyć (w trybie online i offline)
* Aby zmniejszyć ryzyko konfliktów podczas edycji, przesyłaj swoją pracę dość często. Potem możesz kontynuować na innych sekcjach pobranego pliku - procedura importu będzie wiedzieć, które sekcje są nowe.

==Eksport strony==

* Na liście rozwijanej <menuchoice>Chcę...</menuchoice> powinna być wybrana opcja <menuchoice>Eksportuj tłumaczenie w formacie Gettext</menuchoice>.
* Sprawdź, czy nazwa strony i język są poprawnie ustawione.
* <menuchoice>Rozpocznij</menuchoice> uruchomi eksport.

===Importuj nowe tłumaczenie===

Initially you are requested to send the translated file to us. Here is the procedure:

* Use the <menuchoice>Upload file</menuchoice> link in the sidebar to import your file.
* Place a message on [[New Imports]] giving the filename of the upload.
* Once we have confirmed that there are no problems we will show you how to upload your own future translations.

[[Category:Translator_Help]]

Translations:Off-line Translation/6/pl

2012-06-27T22:05:38Z

Toudidel: Created page with "===Importuj nowe tłumaczenie==="

===Importuj nowe tłumaczenie===

Off-line Translation/pl

2012-06-27T22:05:18Z

Toudidel: Created page with "* Na liście rozwijanej <menuchoice>Chcę...</menuchoice> powinna być wybrana opcja <menuchoice>Eksportuj tłumaczenie w formacie Gettext</menuchoice>. * Sprawdź, czy nazwa str..."

<languages />

Zakładamy, że jeśli zamierzasz tłumaczyć w trybie offline, to masz jakieś doświadczenie z '''Lokalize''' lub podobnym narzędziem, dlatego ta strona dotyczy wyłącznie tłumaczenia w trybie online.

== Zasady pracy ==

* Poproś o dodanie do grupy tłumaczy (grupa Translator):
** Kliknij [[Special:myLanguage/Translator Account|Załóż konto tłumacza]] na pasku bocznym
** Kliknij na zakładce <menuchoice>Edytuj</menuchoice> i wpisz swoją nazwę użytkownika, język, na który chciałbyś tłumaczyć i czy jesteś zainteresowany tłumaczeniem w trybie offline
** Użyj opcji <menuchoice>Zapisz stronę</menuchoice>, aby zapisać informacje
* Kiedy użytkownik zostanie dodany do grupy (powinieneś dostać powiadomienie e-mailem), kliknij [[Special:LanguageStats|Rozpocznij tłumaczenie]] na pasku bocznym
* Wprowadź język, na który chcesz tłumaczyć w polu <menuchoice>Kod języka </menuchoice> i kliknij <menuchoice>Rozpocznij</menuchoice> (możesz zaznaczyć, by nie były pokazywane strony przetłumaczone w 100%)
* Wybierz stronę, którą chciałbyś się zająć - zostaniesz przeniesiony do narzędzia, w którym możesz tłumaczyć (w trybie online i offline)
* Aby zmniejszyć ryzyko konfliktów podczas edycji, przesyłaj swoją pracę dość często. Potem możesz kontynuować na innych sekcjach pobranego pliku - procedura importu będzie wiedzieć, które sekcje są nowe.

==Eksport strony==

* Na liście rozwijanej <menuchoice>Chcę...</menuchoice> powinna być wybrana opcja <menuchoice>Eksportuj tłumaczenie w formacie Gettext</menuchoice>.
* Sprawdź, czy nazwa strony i język są poprawnie ustawione.
* <menuchoice>Rozpocznij</menuchoice> uruchomi eksport.

===Import the new translation===

Initially you are requested to send the translated file to us. Here is the procedure:

* Use the <menuchoice>Upload file</menuchoice> link in the sidebar to import your file.
* Place a message on [[New Imports]] giving the filename of the upload.
* Once we have confirmed that there are no problems we will show you how to upload your own future translations.

[[Category:Translator_Help]]

Translations:Off-line Translation/5/pl

2012-06-27T22:05:18Z

* Na liście rozwijanej <menuchoice>Chcę...</menuchoice> powinna być wybrana opcja <menuchoice>Eksportuj tłumaczenie w formacie Gettext</menuchoice>.
* Sprawdź, czy nazwa strony i język są poprawnie ustawione.
* <menuchoice>Rozpocznij</menuchoice> uruchomi eksport.

Off-line Translation/pl

2012-06-27T22:02:38Z

Toudidel: Created page with "==Eksport strony=="

<languages />

Zakładamy, że jeśli zamierzasz tłumaczyć w trybie offline, to masz jakieś doświadczenie z '''Lokalize''' lub podobnym narzędziem, dlatego ta strona dotyczy wyłącznie tłumaczenia w trybie online.

== Zasady pracy ==

* Poproś o dodanie do grupy tłumaczy (grupa Translator):
** Kliknij [[Special:myLanguage/Translator Account|Załóż konto tłumacza]] na pasku bocznym
** Kliknij na zakładce <menuchoice>Edytuj</menuchoice> i wpisz swoją nazwę użytkownika, język, na który chciałbyś tłumaczyć i czy jesteś zainteresowany tłumaczeniem w trybie offline
** Użyj opcji <menuchoice>Zapisz stronę</menuchoice>, aby zapisać informacje
* Kiedy użytkownik zostanie dodany do grupy (powinieneś dostać powiadomienie e-mailem), kliknij [[Special:LanguageStats|Rozpocznij tłumaczenie]] na pasku bocznym
* Wprowadź język, na który chcesz tłumaczyć w polu <menuchoice>Kod języka </menuchoice> i kliknij <menuchoice>Rozpocznij</menuchoice> (możesz zaznaczyć, by nie były pokazywane strony przetłumaczone w 100%)
* Wybierz stronę, którą chciałbyś się zająć - zostaniesz przeniesiony do narzędzia, w którym możesz tłumaczyć (w trybie online i offline)
* Aby zmniejszyć ryzyko konfliktów podczas edycji, przesyłaj swoją pracę dość często. Potem możesz kontynuować na innych sekcjach pobranego pliku - procedura importu będzie wiedzieć, które sekcje są nowe.

==Eksport strony==

* The top combi-box <menuchoice>I want to...</menuchoice> should be set to <menuchoice>Export translation in Gettext format</menuchoice>.
* Check that the page-name and language are correctly set.
* <menuchoice>Go</menuchoice> completes the export.

===Import the new translation===

Initially you are requested to send the translated file to us. Here is the procedure:

* Use the <menuchoice>Upload file</menuchoice> link in the sidebar to import your file.
* Place a message on [[New Imports]] giving the filename of the upload.
* Once we have confirmed that there are no problems we will show you how to upload your own future translations.

[[Category:Translator_Help]]

Translations:Off-line Translation/4/pl

2012-06-27T22:02:38Z

Toudidel: Created page with "==Eksport strony=="

==Eksport strony==

Off-line Translation/pl

2012-06-27T22:02:26Z

Toudidel: Created page with "Zakładamy, że jeśli zamierzasz tłumaczyć w trybie offline, to masz jakieś doświadczenie z '''Lokalize''' lub podobnym narzędziem, dlatego ta strona dotyczy wyłącznie t..."

<languages />

Zakładamy, że jeśli zamierzasz tłumaczyć w trybie offline, to masz jakieś doświadczenie z '''Lokalize''' lub podobnym narzędziem, dlatego ta strona dotyczy wyłącznie tłumaczenia w trybie online.

== Zasady pracy ==

* Poproś o dodanie do grupy tłumaczy (grupa Translator):
** Kliknij [[Special:myLanguage/Translator Account|Załóż konto tłumacza]] na pasku bocznym
** Kliknij na zakładce <menuchoice>Edytuj</menuchoice> i wpisz swoją nazwę użytkownika, język, na który chciałbyś tłumaczyć i czy jesteś zainteresowany tłumaczeniem w trybie offline
** Użyj opcji <menuchoice>Zapisz stronę</menuchoice>, aby zapisać informacje
* Kiedy użytkownik zostanie dodany do grupy (powinieneś dostać powiadomienie e-mailem), kliknij [[Special:LanguageStats|Rozpocznij tłumaczenie]] na pasku bocznym
* Wprowadź język, na który chcesz tłumaczyć w polu <menuchoice>Kod języka </menuchoice> i kliknij <menuchoice>Rozpocznij</menuchoice> (możesz zaznaczyć, by nie były pokazywane strony przetłumaczone w 100%)
* Wybierz stronę, którą chciałbyś się zająć - zostaniesz przeniesiony do narzędzia, w którym możesz tłumaczyć (w trybie online i offline)
* Aby zmniejszyć ryzyko konfliktów podczas edycji, przesyłaj swoją pracę dość często. Potem możesz kontynuować na innych sekcjach pobranego pliku - procedura importu będzie wiedzieć, które sekcje są nowe.

===Export the page===

* The top combi-box <menuchoice>I want to...</menuchoice> should be set to <menuchoice>Export translation in Gettext format</menuchoice>.
* Check that the page-name and language are correctly set.
* <menuchoice>Go</menuchoice> completes the export.

===Import the new translation===

Initially you are requested to send the translated file to us. Here is the procedure:

* Use the <menuchoice>Upload file</menuchoice> link in the sidebar to import your file.
* Place a message on [[New Imports]] giving the filename of the upload.
* Once we have confirmed that there are no problems we will show you how to upload your own future translations.

[[Category:Translator_Help]]

Translations:Off-line Translation/1/pl

2012-06-27T22:02:26Z

Zakładamy, że jeśli zamierzasz tłumaczyć w trybie offline, to masz jakieś doświadczenie z '''Lokalize''' lub podobnym narzędziem, dlatego ta strona dotyczy wyłącznie tłumaczenia w trybie online.

Off-line Translation/pl

2012-06-27T21:58:53Z

Toudidel: Created page with "* Poproś o dodanie do grupy tłumaczy (grupa Translator): ** Kliknij Załóż konto tłumacza na pasku bocznym ** Kliknij na zakładce ..."

<languages />

It is assumed that if you intend translating pages off-line you have some experience with '''Lokalize''' or a similar tool, therefore this page only addresses the on-line part of the process, the part that is carried out within TechBase.

== Zasady pracy ==

* Poproś o dodanie do grupy tłumaczy (grupa Translator):
** Kliknij [[Special:myLanguage/Translator Account|Załóż konto tłumacza]] na pasku bocznym
** Kliknij na zakładce <menuchoice>Edytuj</menuchoice> i wpisz swoją nazwę użytkownika, język, na który chciałbyś tłumaczyć i czy jesteś zainteresowany tłumaczeniem w trybie offline
** Użyj opcji <menuchoice>Zapisz stronę</menuchoice>, aby zapisać informacje
* Kiedy użytkownik zostanie dodany do grupy (powinieneś dostać powiadomienie e-mailem), kliknij [[Special:LanguageStats|Rozpocznij tłumaczenie]] na pasku bocznym
* Wprowadź język, na który chcesz tłumaczyć w polu <menuchoice>Kod języka </menuchoice> i kliknij <menuchoice>Rozpocznij</menuchoice> (możesz zaznaczyć, by nie były pokazywane strony przetłumaczone w 100%)
* Wybierz stronę, którą chciałbyś się zająć - zostaniesz przeniesiony do narzędzia, w którym możesz tłumaczyć (w trybie online i offline)
* Aby zmniejszyć ryzyko konfliktów podczas edycji, przesyłaj swoją pracę dość często. Potem możesz kontynuować na innych sekcjach pobranego pliku - procedura importu będzie wiedzieć, które sekcje są nowe.

===Export the page===

* The top combi-box <menuchoice>I want to...</menuchoice> should be set to <menuchoice>Export translation in Gettext format</menuchoice>.
* Check that the page-name and language are correctly set.
* <menuchoice>Go</menuchoice> completes the export.

===Import the new translation===

Initially you are requested to send the translated file to us. Here is the procedure:

* Use the <menuchoice>Upload file</menuchoice> link in the sidebar to import your file.
* Place a message on [[New Imports]] giving the filename of the upload.
* Once we have confirmed that there are no problems we will show you how to upload your own future translations.

[[Category:Translator_Help]]

Translations:Off-line Translation/3/pl

2012-06-27T21:58:53Z

Toudidel: Created page with "* Poproś o dodanie do grupy tłumaczy (grupa Translator): ** Kliknij Załóż konto tłumacza na pasku bocznym ** Kliknij na zakładce ..."

* Poproś o dodanie do grupy tłumaczy (grupa Translator):
** Kliknij [[Special:myLanguage/Translator Account|Załóż konto tłumacza]] na pasku bocznym
** Kliknij na zakładce <menuchoice>Edytuj</menuchoice> i wpisz swoją nazwę użytkownika, język, na który chciałbyś tłumaczyć i czy jesteś zainteresowany tłumaczeniem w trybie offline
** Użyj opcji <menuchoice>Zapisz stronę</menuchoice>, aby zapisać informacje
* Kiedy użytkownik zostanie dodany do grupy (powinieneś dostać powiadomienie e-mailem), kliknij [[Special:LanguageStats|Rozpocznij tłumaczenie]] na pasku bocznym
* Wprowadź język, na który chcesz tłumaczyć w polu <menuchoice>Kod języka </menuchoice> i kliknij <menuchoice>Rozpocznij</menuchoice> (możesz zaznaczyć, by nie były pokazywane strony przetłumaczone w 100%)
* Wybierz stronę, którą chciałbyś się zająć - zostaniesz przeniesiony do narzędzia, w którym możesz tłumaczyć (w trybie online i offline)
* Aby zmniejszyć ryzyko konfliktów podczas edycji, przesyłaj swoją pracę dość często. Potem możesz kontynuować na innych sekcjach pobranego pliku - procedura importu będzie wiedzieć, które sekcje są nowe.

Off-line Translation/pl

2012-06-27T21:48:45Z

Toudidel: Created page with "== Zasady pracy =="

<languages />

It is assumed that if you intend translating pages off-line you have some experience with '''Lokalize''' or a similar tool, therefore this page only addresses the on-line part of the process, the part that is carried out within TechBase.

== Zasady pracy ==

* Request addition to the Translator group:
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar
** Click on the <menuchoice>Edit</menuchoice> tab and enter your username, the language you want to translate for and if you intend to translate off-line
** Use <menuchoice>Save page</menuchoice> to save the information
* When your user has been added to the group (you should get an e-mail notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar
* Enter the language you want to translate to in <menuchoice>Language code </menuchoice> and click on <menuchoice>Go</menuchoice> (You can select to suppress pages that are 100% complete.)
* Choose your page to work on, from the list presented - this will take you to the tool where you choose on-line or off-line translation.
* In order to reduce the risk of edit conflicts, upload your work frequently. You can continue to work on other sections from your downloaded file - import will know which sections are new.

===Export the page===

* The top combi-box <menuchoice>I want to...</menuchoice> should be set to <menuchoice>Export translation in Gettext format</menuchoice>.
* Check that the page-name and language are correctly set.
* <menuchoice>Go</menuchoice> completes the export.

===Import the new translation===

Initially you are requested to send the translated file to us. Here is the procedure:

* Use the <menuchoice>Upload file</menuchoice> link in the sidebar to import your file.
* Place a message on [[New Imports]] giving the filename of the upload.
* Once we have confirmed that there are no problems we will show you how to upload your own future translations.

[[Category:Translator_Help]]

Translations:Off-line Translation/2/pl

2012-06-27T21:48:45Z

Toudidel: Created page with "== Zasady pracy =="

== Zasady pracy ==

Translations:Off-line Translation/Page display title/pl

2012-06-27T21:47:27Z

Toudidel: Created page with "Tłumaczenie offline"

Tłumaczenie offline

Off-line Translation/pl

2012-06-27T21:47:27Z

Toudidel: Created page with "Tłumaczenie offline"

<languages />

It is assumed that if you intend translating pages off-line you have some experience with '''Lokalize''' or a similar tool, therefore this page only addresses the on-line part of the process, the part that is carried out within TechBase.

== Workflow ==

* Request addition to the Translator group:
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar
** Click on the <menuchoice>Edit</menuchoice> tab and enter your username, the language you want to translate for and if you intend to translate off-line
** Use <menuchoice>Save page</menuchoice> to save the information
* When your user has been added to the group (you should get an e-mail notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar
* Enter the language you want to translate to in <menuchoice>Language code </menuchoice> and click on <menuchoice>Go</menuchoice> (You can select to suppress pages that are 100% complete.)
* Choose your page to work on, from the list presented - this will take you to the tool where you choose on-line or off-line translation.
* In order to reduce the risk of edit conflicts, upload your work frequently. You can continue to work on other sections from your downloaded file - import will know which sections are new.

===Export the page===

* The top combi-box <menuchoice>I want to...</menuchoice> should be set to <menuchoice>Export translation in Gettext format</menuchoice>.
* Check that the page-name and language are correctly set.
* <menuchoice>Go</menuchoice> completes the export.

===Import the new translation===

Initially you are requested to send the translated file to us. Here is the procedure:

* Use the <menuchoice>Upload file</menuchoice> link in the sidebar to import your file.
* Place a message on [[New Imports]] giving the filename of the upload.
* Once we have confirmed that there are no problems we will show you how to upload your own future translations.

[[Category:Translator_Help]]

Development/FAQs/General FAQ/pl

2012-06-27T21:46:49Z

Toudidel: Created page with "<tt>kde-config</tt> i w ogóle wszystkie programy kde akceptują <tt>--version</tt> jako argument."

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==Nie chcę stracić mojej historii SVN==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==Co to jest kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?==

Tak, sprawdź w dokumentacji Building 2 Versions

==Skąd mam wiedzieć, której wersji Qt/KDE używam?==

<tt>kde-config</tt> i w ogóle wszystkie programy kde akceptują <tt>--version</tt> jako argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==Jak mogę utworzyć klucz SSH?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==Jak mogę monitorować zmiany dokonane przez innych?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/54/pl

2012-06-27T21:46:48Z

Toudidel: Created page with "<tt>kde-config</tt> i w ogóle wszystkie programy kde akceptują <tt>--version</tt> jako argument."

<tt>kde-config</tt> i w ogóle wszystkie programy kde akceptują <tt>--version</tt> jako argument.

Development/FAQs/General FAQ/pl

2012-06-27T21:46:08Z

Toudidel: Created page with "Tak, sprawdź w dokumentacji Building 2 Versions"

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==Nie chcę stracić mojej historii SVN==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==Co to jest kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?==

Tak, sprawdź w dokumentacji Building 2 Versions

==Skąd mam wiedzieć, której wersji Qt/KDE używam?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==Jak mogę utworzyć klucz SSH?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==Jak mogę monitorować zmiany dokonane przez innych?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/52/pl

2012-06-27T21:46:08Z

Toudidel: Created page with "Tak, sprawdź w dokumentacji Building 2 Versions"

Tak, sprawdź w dokumentacji Building 2 Versions

Translations:Development/FAQs/General FAQ/77/pl

2012-06-27T21:45:16Z

Toudidel: Created page with "Category:FAQs"

[[Category:FAQs]]

Development/FAQs/General FAQ/pl

2012-06-27T21:45:10Z

Toudidel: Created page with "==Jak mogę monitorować zmiany dokonane przez innych?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==Nie chcę stracić mojej historii SVN==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==Co to jest kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?==

Yes, check the Building 2 Versions documentation.

==Skąd mam wiedzieć, której wersji Qt/KDE używam?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==Jak mogę utworzyć klucz SSH?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==Jak mogę monitorować zmiany dokonane przez innych?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/75/pl

2012-06-27T21:45:09Z

Toudidel: Created page with "==Jak mogę monitorować zmiany dokonane przez innych?=="

==Jak mogę monitorować zmiany dokonane przez innych?==

Development/FAQs/General FAQ/pl

2012-06-27T21:44:19Z

Toudidel: Created page with "==Jak mogę utworzyć klucz SSH?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==Nie chcę stracić mojej historii SVN==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==Co to jest kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?==

Yes, check the Building 2 Versions documentation.

==Skąd mam wiedzieć, której wersji Qt/KDE używam?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==Jak mogę utworzyć klucz SSH?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/69/pl

2012-06-27T21:44:19Z

Toudidel: Created page with "==Jak mogę utworzyć klucz SSH?=="

==Jak mogę utworzyć klucz SSH?==

Development/FAQs/General FAQ/pl

2012-06-27T21:43:48Z

Toudidel: Created page with "==Skąd mam wiedzieć, której wersji Qt/KDE używam?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==Nie chcę stracić mojej historii SVN==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==Co to jest kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?==

Yes, check the Building 2 Versions documentation.

==Skąd mam wiedzieć, której wersji Qt/KDE używam?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/53/pl

2012-06-27T21:43:48Z

Toudidel: Created page with "==Skąd mam wiedzieć, której wersji Qt/KDE używam?=="

==Skąd mam wiedzieć, której wersji Qt/KDE używam?==

Development/FAQs/General FAQ/pl

2012-06-27T21:43:19Z

Toudidel: Created page with "==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==Nie chcę stracić mojej historii SVN==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==Co to jest kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/51/pl

2012-06-27T21:43:18Z

Toudidel: Created page with "==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?=="

==Mogę mieć na tym samym komputerze stabilne i niestabilne KDE?==

Development/FAQs/General FAQ/pl

2012-06-27T21:42:43Z

Toudidel: Created page with "==Co to jest kdebindings?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==Nie chcę stracić mojej historii SVN==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==Co to jest kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/47/pl

2012-06-27T21:42:43Z

Toudidel: Created page with "==Co to jest kdebindings?=="

==Co to jest kdebindings?==

Development/FAQs/General FAQ/pl

2012-06-27T21:42:27Z

Toudidel: Created page with "==Nie chcę stracić mojej historii SVN=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==Nie chcę stracić mojej historii SVN==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/45/pl

2012-06-27T21:42:27Z

Toudidel: Created page with "==Nie chcę stracić mojej historii SVN=="

==Nie chcę stracić mojej historii SVN==

Development/FAQs/General FAQ/pl

2012-06-27T21:42:02Z

Toudidel: Created page with "==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/43/pl

2012-06-27T21:42:02Z

Toudidel: Created page with "==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE=="

==Moja aplikacja nie jest stabilna, ale chciałbym ją mieć w KDE==

Development/FAQs/General FAQ/pl

2012-06-27T21:41:22Z

Toudidel: Created page with "Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym."

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/24/pl

2012-06-27T21:41:22Z

Toudidel: Created page with "Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym."

Nie zapomnij zrobić {{path|/usr/local/bin/_svndiff}} wykonywalnym.

Development/FAQs/General FAQ/pl

2012-06-27T21:40:55Z

Toudidel: Created page with "==Co powinienem wstawić w moim .subversion/config?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==Co powinienem wstawić w moim .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/21/pl

2012-06-27T21:40:55Z

Toudidel: Created page with "==Co powinienem wstawić w moim .subversion/config?=="

==Co powinienem wstawić w moim .subversion/config?==

Development/FAQs/General FAQ/pl

2012-06-27T21:40:32Z

Toudidel: Created page with "==Czy mam dostęp online do kodów źródłowych KDE?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Czy mam dostęp online do kodów źródłowych KDE?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/19/pl

2012-06-27T21:40:32Z

Toudidel: Created page with "==Czy mam dostęp online do kodów źródłowych KDE?=="

==Czy mam dostęp online do kodów źródłowych KDE?==

Development/FAQs/General FAQ/pl

2012-06-27T21:40:06Z

Toudidel: Created page with "==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/17/pl

2012-06-27T21:40:05Z

Toudidel: Created page with "==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?=="

==Jak mogę pobrać oprogramowanie KDE z repozytoriów git lub SVN?==

Development/FAQs/General FAQ/pl

2012-06-27T21:39:23Z

Toudidel: Created page with "==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==How do I get KDE software from the KDE git or SVN repositories?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/15/pl

2012-06-27T21:39:23Z

Toudidel: Created page with "==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?=="

==Jaki poziom wiedzy jest konieczny, by wspomóc KDE? Czego powinienem się nauczyć? Co powinienem przeczytać?==

Development/FAQs/General FAQ/pl

2012-06-27T21:38:13Z

Toudidel: Created page with "==Gdzie mogę znaleźć obrazy Konqi?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Gdzie mogę znaleźć obrazy Konqi?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==What is the level required to contribute to KDE? What should I learn? What should I read?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==How do I get KDE software from the KDE git or SVN repositories?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/12/pl

2012-06-27T21:38:13Z

Toudidel: Created page with "==Gdzie mogę znaleźć obrazy Konqi?=="

==Gdzie mogę znaleźć obrazy Konqi?==

Development/FAQs/General FAQ/pl

2012-06-27T21:37:45Z

Toudidel: Created page with "==Nie jestem programistą, jak mogę pomóc?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==Nie jestem programistą, jak mogę pomóc?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Where can I find images of Konqi the dragon?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==What is the level required to contribute to KDE? What should I learn? What should I read?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==How do I get KDE software from the KDE git or SVN repositories?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/10/pl

2012-06-27T21:37:44Z

Toudidel: Created page with "==Nie jestem programistą, jak mogę pomóc?=="

==Nie jestem programistą, jak mogę pomóc?==

Development/FAQs/General FAQ/pl

2012-06-27T21:37:22Z

Toudidel: Created page with "==Jestem programistą, jak mogę wspomóc KDE?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==Jestem programistą, jak mogę wspomóc KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==I am not a developer, how can I help?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Where can I find images of Konqi the dragon?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==What is the level required to contribute to KDE? What should I learn? What should I read?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==How do I get KDE software from the KDE git or SVN repositories?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/6/pl

2012-06-27T21:37:22Z

Toudidel: Created page with "==Jestem programistą, jak mogę wspomóc KDE?=="

==Jestem programistą, jak mogę wspomóc KDE?==

Development/FAQs/General FAQ/pl

2012-06-27T21:36:44Z

Toudidel: Created page with "Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc."

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==I am a developer, how can I contribute to KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==I am not a developer, how can I help?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Where can I find images of Konqi the dragon?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==What is the level required to contribute to KDE? What should I learn? What should I read?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==How do I get KDE software from the KDE git or SVN repositories?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/4/pl

2012-06-27T21:36:44Z

Toudidel: Created page with "Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc."

Zobacz [http://www.kde.org/jobs/ tę stronę], by sprawdzić obszary, w których potrzebna jest pomoc.

Development/FAQs/General FAQ/pl

2012-06-27T21:34:42Z

Toudidel: Created page with "To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy."

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

To see the areas where help is needed, check [http://www.kde.org/jobs/ this page].

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==I am a developer, how can I contribute to KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==I am not a developer, how can I help?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Where can I find images of Konqi the dragon?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==What is the level required to contribute to KDE? What should I learn? What should I read?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==How do I get KDE software from the KDE git or SVN repositories?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/3/pl

2012-06-27T21:34:42Z

Toudidel: Created page with "To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy."

To prawda, że jest wiele aplikacji KDE, które powinny być napisane. Ale jest też wiele istniejących programów, które potrzebują Twojej pomocy.

Development/FAQs/General FAQ/pl

2012-06-27T21:33:49Z

Toudidel: Created page with "==Chcę napisać nową aplikację. Jakieś rady?=="

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==Chcę napisać nową aplikację. Jakieś rady?==

We all agree that there are plenty of KDE applications that need to be written. But there are also a lot of existing kde applications that need your help.

To see the areas where help is needed, check [http://www.kde.org/jobs/ this page].

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==I am a developer, how can I contribute to KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==I am not a developer, how can I help?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Where can I find images of Konqi the dragon?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==What is the level required to contribute to KDE? What should I learn? What should I read?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==How do I get KDE software from the KDE git or SVN repositories?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/2/pl

2012-06-27T21:33:49Z

Toudidel: Created page with "==Chcę napisać nową aplikację. Jakieś rady?=="

==Chcę napisać nową aplikację. Jakieś rady?==

Development/FAQs/General FAQ/pl

2012-06-27T21:32:14Z

Toudidel: Created page with "Kodowanie/FAQ/FAQ ogólny"

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==I want to start this new application. What do you advise?==

We all agree that there are plenty of KDE applications that need to be written. But there are also a lot of existing kde applications that need your help.

To see the areas where help is needed, check [http://www.kde.org/jobs/ this page].

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] for existing applications and to ask on the [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.

==I am a developer, how can I contribute to KDE?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

You can also ask on [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of KDE and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE needs more non-geek oriented applications.

==I am not a developer, how can I help?==

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).

==Where can I find images of Konqi the dragon?==

The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2] 
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==What is the level required to contribute to KDE? What should I learn? What should I read?==

You need to know C++. Read the [http://qt.nokia.com/learning Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a kde developer. Using kde's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

==How do I get KDE software from the KDE git or SVN repositories?==

See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.

==I want to put my app in KDE==

There are three requirements:
* your app must compile with the latest version of KDE (git master or SVN trunk).
* your app must be stable.
* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
See also the next question.

==Is it better to develop inside or outside KDE?==

As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

==How do I get write access to KDE repositories?==

See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].

Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})

See also [[#How do I create a SSH key?]]

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE Commit Policy]].

==My app is not stable but I would like to have it in KDE==

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

==I don't want to lose my SVN history.==

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

==What is kdebindings?==

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.

==Does the feature freeze apply to playground?==

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

==Can I have a stable and an unstable KDE on the same computer?==

Yes, check the Building 2 Versions documentation.

==How do I know which version of Qt/KDE I am using?==

<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.

==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?==

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

==How can I checkout a single directory from a SVN module?==

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils:
<code>svn co -N /playground/utils; svn up reaktivate</code>
Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

==How can I get one of the KDE application as a standalone tarball?==

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

==How do I close my own bug reports?==

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

<Code>BUG: XXXXX</code> where '''''XXXXX''''' is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

==How do I create a SSH key?==

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen.
When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.ssh/id_dsa.pub}}.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,
{{Input|1= Host svn.kde.org
IdentityFile ~/.ssh/id_dsa_kde }}
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

==How can I monitor changes made by others?==

The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.

[[Category:FAQs]]

Translations:Development/FAQs/General FAQ/Page display title/pl

2012-06-27T21:32:13Z

Toudidel: Created page with "Kodowanie/FAQ/FAQ ogólny"

Kodowanie/FAQ/FAQ ogólny

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:30:54Z

Toudidel: Created page with "Aby uzyskać znaczniki czasu (timestampy) w wyniku debugowania, które sa przydatne podczas debugowania wielowątkowych, sieciowych i asynchronicznych operacji, użyj <tt>export ..."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny).

1. Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania.

Jeśli tak, sprawdź Q_OBJECT, czy nazwy parametru nie ma w połączeniu, czy typy parametru są odpowiednie i czy gniazdo jest zdefiniowane oraz czy moc został skompilowany.

1b. Lub możesz sprawdzić, co zwraca connect() mimo, że nie daje żadnego komunikatu o błędzie
2. Upewnij się, że sygnał rzeczywiście jest emitowany
3. Upewnij się, że odbiorca nie jest już skasowany w tym momencie
4. Upewnij się, że emitter->signalsBlocked() zwraca false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

Składnia przypomina cout, możesz używać wiele natywnych typów pomiędzy "<<". Wyświetli to komunikat debugowy, który zostanie automatyczne wyłączony w releasie (poprzez <tt>--disable-debug</tt>). W przypadku, kiedy chcesz, by komunikaty były nadal widoczne także podczas releasu - ponieważ jest to ostrzeżenie lub błąd - użyj <tt>kWarning()</tt> lub <tt>kError()</tt>.

Komponenty i biblioteki powinny używać numerów obszarów debugowania (debug area number) tak, jak w kDebug(1234). Do tego numer musi być zarejestrowany w kdelibs/kdecore/kdebug.areas. Obszary debugowania pozwalają wyłączyć lub włączyć wynik debugowania dla określonych numerów obszarów, używając programu {{program|kdebugdialog}}, będącego częścią kdebase. <tt>kdebugdialog --fullmode</tt> pozwala określić, gdzie generowany powinien być wynik debugowania. Zazwyczaj nie jest konieczne rejestrowanie numerów obszarów dla samodzielnych aplikacji, chyba że jest to tak skomplikowane, że chcesz podzielić wynik na kilka obszarów.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

Żeby było jasne: NIE używaj <tt>qDebug()</tt>, to nie zostanie wyłączone w releasie. Unikaj także używania <tt>assert()</tt> lub <tt>kFatal()</tt>, które prowadzą do katastrofy, gdy coś pójdzie nie tak - nie jest to miłe doświadczenie dla użytkownika. Lepiej wykryć błąd, wyrzucić <tt>kWarning()</tt> lub <tt>kError()</tt> i odzyskać kontrolę, jeśli to możliwe.

Aby uzyskać znaczniki czasu (timestampy) w wyniku debugowania, które sa przydatne podczas debugowania wielowątkowych, sieciowych i asynchronicznych operacji, użyj <tt>export KDE_DEBUG_TIMESTAMP=1</tt> przed uruchomieniem aplikacji. Działa od KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/38/pl

2012-06-27T21:30:54Z

Aby uzyskać znaczniki czasu (timestampy) w wyniku debugowania, które sa przydatne podczas debugowania wielowątkowych, sieciowych i asynchronicznych operacji, użyj <tt>export KDE_DEBUG_TIMESTAMP=1</tt> przed uruchomieniem aplikacji. Działa od KDE SC 4.5.

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:28:52Z

Toudidel: Created page with "Żeby było jasne: NIE używaj <tt>qDebug()</tt>, to nie zostanie wyłączone w releasie. Unikaj także używania <tt>assert()</tt> lub <tt>kFatal()</tt>, które prowadzą do kat..."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny).

1. Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania.

Jeśli tak, sprawdź Q_OBJECT, czy nazwy parametru nie ma w połączeniu, czy typy parametru są odpowiednie i czy gniazdo jest zdefiniowane oraz czy moc został skompilowany.

1b. Lub możesz sprawdzić, co zwraca connect() mimo, że nie daje żadnego komunikatu o błędzie
2. Upewnij się, że sygnał rzeczywiście jest emitowany
3. Upewnij się, że odbiorca nie jest już skasowany w tym momencie
4. Upewnij się, że emitter->signalsBlocked() zwraca false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

Składnia przypomina cout, możesz używać wiele natywnych typów pomiędzy "<<". Wyświetli to komunikat debugowy, który zostanie automatyczne wyłączony w releasie (poprzez <tt>--disable-debug</tt>). W przypadku, kiedy chcesz, by komunikaty były nadal widoczne także podczas releasu - ponieważ jest to ostrzeżenie lub błąd - użyj <tt>kWarning()</tt> lub <tt>kError()</tt>.

Komponenty i biblioteki powinny używać numerów obszarów debugowania (debug area number) tak, jak w kDebug(1234). Do tego numer musi być zarejestrowany w kdelibs/kdecore/kdebug.areas. Obszary debugowania pozwalają wyłączyć lub włączyć wynik debugowania dla określonych numerów obszarów, używając programu {{program|kdebugdialog}}, będącego częścią kdebase. <tt>kdebugdialog --fullmode</tt> pozwala określić, gdzie generowany powinien być wynik debugowania. Zazwyczaj nie jest konieczne rejestrowanie numerów obszarów dla samodzielnych aplikacji, chyba że jest to tak skomplikowane, że chcesz podzielić wynik na kilka obszarów.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

Żeby było jasne: NIE używaj <tt>qDebug()</tt>, to nie zostanie wyłączone w releasie. Unikaj także używania <tt>assert()</tt> lub <tt>kFatal()</tt>, które prowadzą do katastrofy, gdy coś pójdzie nie tak - nie jest to miłe doświadczenie dla użytkownika. Lepiej wykryć błąd, wyrzucić <tt>kWarning()</tt> lub <tt>kError()</tt> i odzyskać kontrolę, jeśli to możliwe.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/37/pl

2012-06-27T21:28:52Z

Żeby było jasne: NIE używaj <tt>qDebug()</tt>, to nie zostanie wyłączone w releasie. Unikaj także używania <tt>assert()</tt> lub <tt>kFatal()</tt>, które prowadzą do katastrofy, gdy coś pójdzie nie tak - nie jest to miłe doświadczenie dla użytkownika. Lepiej wykryć błąd, wyrzucić <tt>kWarning()</tt> lub <tt>kError()</tt> i odzyskać kontrolę, jeśli to możliwe.

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:25:00Z

Toudidel: Created page with "Komponenty i biblioteki powinny używać numerów obszarów debugowania (debug area number) tak, jak w kDebug(1234). Do tego numer musi być zarejestrowany w kdelibs/kdecore/kdeb..."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny).

1. Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania.

Jeśli tak, sprawdź Q_OBJECT, czy nazwy parametru nie ma w połączeniu, czy typy parametru są odpowiednie i czy gniazdo jest zdefiniowane oraz czy moc został skompilowany.

1b. Lub możesz sprawdzić, co zwraca connect() mimo, że nie daje żadnego komunikatu o błędzie
2. Upewnij się, że sygnał rzeczywiście jest emitowany
3. Upewnij się, że odbiorca nie jest już skasowany w tym momencie
4. Upewnij się, że emitter->signalsBlocked() zwraca false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

Składnia przypomina cout, możesz używać wiele natywnych typów pomiędzy "<<". Wyświetli to komunikat debugowy, który zostanie automatyczne wyłączony w releasie (poprzez <tt>--disable-debug</tt>). W przypadku, kiedy chcesz, by komunikaty były nadal widoczne także podczas releasu - ponieważ jest to ostrzeżenie lub błąd - użyj <tt>kWarning()</tt> lub <tt>kError()</tt>.

Komponenty i biblioteki powinny używać numerów obszarów debugowania (debug area number) tak, jak w kDebug(1234). Do tego numer musi być zarejestrowany w kdelibs/kdecore/kdebug.areas. Obszary debugowania pozwalają wyłączyć lub włączyć wynik debugowania dla określonych numerów obszarów, używając programu {{program|kdebugdialog}}, będącego częścią kdebase. <tt>kdebugdialog --fullmode</tt> pozwala określić, gdzie generowany powinien być wynik debugowania. Zazwyczaj nie jest konieczne rejestrowanie numerów obszarów dla samodzielnych aplikacji, chyba że jest to tak skomplikowane, że chcesz podzielić wynik na kilka obszarów.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/33/pl

2012-06-27T21:24:59Z

Komponenty i biblioteki powinny używać numerów obszarów debugowania (debug area number) tak, jak w kDebug(1234). Do tego numer musi być zarejestrowany w kdelibs/kdecore/kdebug.areas. Obszary debugowania pozwalają wyłączyć lub włączyć wynik debugowania dla określonych numerów obszarów, używając programu {{program|kdebugdialog}}, będącego częścią kdebase. <tt>kdebugdialog --fullmode</tt> pozwala określić, gdzie generowany powinien być wynik debugowania. Zazwyczaj nie jest konieczne rejestrowanie numerów obszarów dla samodzielnych aplikacji, chyba że jest to tak skomplikowane, że chcesz podzielić wynik na kilka obszarów.

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:18:57Z

Toudidel: Created page with "Składnia przypomina cout, możesz używać wiele natywnych typów pomiędzy "<<". Wyświetli to komunikat debugowy, który zostanie automatyczne wyłączony w releasie (poprzez ..."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny).

1. Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania.

Jeśli tak, sprawdź Q_OBJECT, czy nazwy parametru nie ma w połączeniu, czy typy parametru są odpowiednie i czy gniazdo jest zdefiniowane oraz czy moc został skompilowany.

1b. Lub możesz sprawdzić, co zwraca connect() mimo, że nie daje żadnego komunikatu o błędzie
2. Upewnij się, że sygnał rzeczywiście jest emitowany
3. Upewnij się, że odbiorca nie jest już skasowany w tym momencie
4. Upewnij się, że emitter->signalsBlocked() zwraca false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

Składnia przypomina cout, możesz używać wiele natywnych typów pomiędzy "<<". Wyświetli to komunikat debugowy, który zostanie automatyczne wyłączony w releasie (poprzez <tt>--disable-debug</tt>). W przypadku, kiedy chcesz, by komunikaty były nadal widoczne także podczas releasu - ponieważ jest to ostrzeżenie lub błąd - użyj <tt>kWarning()</tt> lub <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/32/pl

2012-06-27T21:18:57Z

Składnia przypomina cout, możesz używać wiele natywnych typów pomiędzy "<<". Wyświetli to komunikat debugowy, który zostanie automatyczne wyłączony w releasie (poprzez <tt>--disable-debug</tt>). W przypadku, kiedy chcesz, by komunikaty były nadal widoczne także podczas releasu - ponieważ jest to ostrzeżenie lub błąd - użyj <tt>kWarning()</tt> lub <tt>kError()</tt>.

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:15:36Z

Toudidel: Created page with "1b. Lub możesz sprawdzić, co zwraca connect() mimo, że nie daje żadnego komunikatu o błędzie 2. Upewnij się, że sygnał rzeczywiście jest emitowany 3. Upewnij się, że ..."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny).

1. Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania.

Jeśli tak, sprawdź Q_OBJECT, czy nazwy parametru nie ma w połączeniu, czy typy parametru są odpowiednie i czy gniazdo jest zdefiniowane oraz czy moc został skompilowany.

1b. Lub możesz sprawdzić, co zwraca connect() mimo, że nie daje żadnego komunikatu o błędzie
2. Upewnij się, że sygnał rzeczywiście jest emitowany
3. Upewnij się, że odbiorca nie jest już skasowany w tym momencie
4. Upewnij się, że emitter->signalsBlocked() zwraca false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/27/pl

2012-06-27T21:15:35Z

1b. Lub możesz sprawdzić, co zwraca connect() mimo, że nie daje żadnego komunikatu o błędzie
2. Upewnij się, że sygnał rzeczywiście jest emitowany
3. Upewnij się, że odbiorca nie jest już skasowany w tym momencie
4. Upewnij się, że emitter->signalsBlocked() zwraca false

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:12:47Z

Toudidel:

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny).

1. Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania.

Jeśli tak, sprawdź Q_OBJECT, czy nazwy parametru nie ma w połączeniu, czy typy parametru są odpowiednie i czy gniazdo jest zdefiniowane oraz czy moc został skompilowany.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/25/pl

2012-06-27T21:12:47Z

Toudidel:

1. Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania.

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:11:50Z

Toudidel: Created page with "Jeśli tak, sprawdź Q_OBJECT, czy nazwy parametru nie ma w połączeniu, czy typy parametru są odpowiednie i czy gniazdo jest zdefiniowane oraz czy moc został skompilowany."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny).


1) Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania.


Jeśli tak, sprawdź Q_OBJECT, czy nazwy parametru nie ma w połączeniu, czy typy parametru są odpowiednie i czy gniazdo jest zdefiniowane oraz czy moc został skompilowany.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/26/pl

2012-06-27T21:11:50Z

Jeśli tak, sprawdź Q_OBJECT, czy nazwy parametru nie ma w połączeniu, czy typy parametru są odpowiednie i czy gniazdo jest zdefiniowane oraz czy moc został skompilowany.

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:08:20Z

Toudidel: Created page with "1) Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny).


1) Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania.


If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/25/pl

2012-06-27T21:08:20Z

Toudidel: Created page with "1) Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania."

1) Upewnij się, że connect() nie wyświetla ostrzeżenia w konsoli podczas działania.

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:07:12Z

Toudidel: Created page with "Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny)."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/24/pl

2012-06-27T21:07:12Z

Toudidel: Created page with "Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny)."

Oto kilka kroków, które można wykorzystać do rozwiązania problemu, dlaczego sygnał/gniazdo nie działa (gniazdo nie odpowiada z jakiejś przyczyny).

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:05:28Z

Toudidel: Created page with "=== Dlaczego mój sygnał i połączenie gniazda nie działa? ==="

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/23/pl

2012-06-27T21:05:28Z

Toudidel: Created page with "=== Dlaczego mój sygnał i połączenie gniazda nie działa? ==="

=== Dlaczego mój sygnał i połączenie gniazda nie działa? ===

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:04:33Z

Toudidel: Created page with "Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować. Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej cz..."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Why isn't my signal and slot connection working? ===

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/20/pl

2012-06-27T21:04:33Z

Musisz zatrzymać się zaraz po załadowaniu symboli z biblioteki. Potem możesz normalnie debugować.
Możesz utworzyć makro gdb, aby zatrzymać się zaraz po załadowanej części. W przypadku kword, na przykład, używam:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:01:32Z

Toudidel: Created page with "===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?==="

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

You must stop just after the main to load the debugging symbols of the shared library. After that, you can debug normally.
One can go as far as creating a gdb macro, to stop right after the part was loaded. For kword, by example, I use:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Why isn't my signal and slot connection working? ===

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/19/pl

2012-06-27T21:01:32Z

Toudidel: Created page with "===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?==="

===Nie mam symbolu debugując aplikację, która używa kpart. Co powinienem zrobić?===

Development/FAQs/Debugging FAQ/pl

2012-06-27T21:00:22Z

Toudidel: Created page with "Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię: {{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}} W gdb możesz wtedy użyć <code>printqstring myqstring</co..."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===I have no symbol when I debug an app that uses kpart, what should I do?===

You must stop just after the main to load the debugging symbols of the shared library. After that, you can debug normally.
One can go as far as creating a gdb macro, to stop right after the part was loaded. For kword, by example, I use:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Why isn't my signal and slot connection working? ===

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/16/pl

2012-06-27T21:00:22Z

Pobierz kdesdk i w pliku ~/.gdbinit dodaj linię:
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
W gdb możesz wtedy użyć <code>printqstring myqstring</code>, aby zobaczyć jego zawartość.
Na przykład <code>QString myqstring = QString::fromLatin1("contents");</code> może zostać prześledzony używając

Development/FAQs/Debugging FAQ/pl

2012-06-27T20:57:48Z

Toudidel: Created page with "*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji. *gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i ..."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Check out kdesdk, and add this line to your ~/.gdbinit :
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
Then in gdb you can do <code>printqstring myqstring</code> to see its contents.
For instance, <code>QString myqstring = QString::fromLatin1("contents");</code> can be examined using

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===I have no symbol when I debug an app that uses kpart, what should I do?===

You must stop just after the main to load the debugging symbols of the shared library. After that, you can debug normally.
One can go as far as creating a gdb macro, to stop right after the part was loaded. For kword, by example, I use:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Why isn't my signal and slot connection working? ===

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/13/pl

2012-06-27T20:57:48Z

*kDebug() (kdDebug() w KDE3) zapewnia prosty, ale efektywny sposób debugowania aplikacji.
*gdb, the GNU debugger, jest najszybszym sposobem śledzenia aplikacji krok po kroku i badania zmiennych (zalecana wersja gdb 6.x lub wyższa)
*Valgrind
*kdbg jest graficznym interfejsem do gdb (z KDE GUI). Wspiera wiele typów Qt (łącznie z QString).
*Monitor wycieków pamięci : See kdesdk/kmtrace. Plik README dostarczy informacji i wszystko wyjaśni.
*qdbus i dbusviewer z pakietu Qt pozwala przeglądać interfejsy DBus i w łatwy sposób tworzy odwołania DBus.

Development/FAQs/Debugging FAQ/pl

2012-06-27T20:50:52Z

Toudidel: Created page with "Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji. W..."

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() in KDE3) calls are a simple but efficient way to debug an application.
*gdb, the GNU debugger, is the quickest way to execute step-by-step and investigate variables (recommended versions are gdb >= 6.x)
*Valgrind
*kdbg is a nice graphical frontend to gdb with a KDE GUI. It has support for many Qt types (including QString).
*Memory leak tracer : See kdesdk/kmtrace. The README explains it all.
*qdbus and dbusviewer from Qt allow to browse DBus interfaces and to easily make DBus calls.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Check out kdesdk, and add this line to your ~/.gdbinit :
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
Then in gdb you can do <code>printqstring myqstring</code> to see its contents.
For instance, <code>QString myqstring = QString::fromLatin1("contents");</code> can be examined using

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===I have no symbol when I debug an app that uses kpart, what should I do?===

You must stop just after the main to load the debugging symbols of the shared library. After that, you can debug normally.
One can go as far as creating a gdb macro, to stop right after the part was loaded. For kword, by example, I use:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Why isn't my signal and slot connection working? ===

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/11/pl

2012-06-27T20:50:52Z

Jeśli już masz plik core, możesz przebadać go przy użyciu gdb. Najbardziej przydatną komendą gdb jest <code>bt</code>, generująca zrzut, ślad po zawieszeniu aplikacji.
Więcej informacji o gdb znajdziesz na [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|tej stronie]].

Thread:User talk:Toudidel/Translating/reply (3)

2012-06-27T20:45:07Z

Toudidel: Reply to Translating

I think a warning box would be a good idea and the better some kind of modal dialog just after start editing.

Development/FAQs/Debugging FAQ/pl

2012-06-27T17:38:56Z

Toudidel: Created page with "W pliku $KDEHOME/share/config/drkonqirc dodaj: <syntaxhighlight lang="ini"> [drkonqi] ConfigName=developer </syntaxhighlight>"

<languages />
==Ogólne==

===Jak mogę uniknąć Dr Konqi?===

Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość)

Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG.

Przykład: 
*Aby uniknąć Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*Aby zobaczyć Dr Konqi:
::<code>unset KDE_DEBUG</code>

===Jak mogę przełączyć Dr Konqi do trybu programisty?===

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===Co to jest plik core? Skąd wziąć plik core?===

Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia.

Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj <code>ulimit -c unlimited</code>.

Once you have a core file for a crash, you can examine it with gdb appname core . This will open gdb on the core file for the given application. Once at the gdb prompt, the most useful command is <code>bt</code> which generates a backtrace of the crash.
For more information about how to use gdb, see [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|this page]]

===Jakich narzędzi można użyć do debuggowania mojej aplikacji?===

*kDebug() (kdDebug() in KDE3) calls are a simple but efficient way to debug an application.
*gdb, the GNU debugger, is the quickest way to execute step-by-step and investigate variables (recommended versions are gdb >= 6.x)
*Valgrind
*kdbg is a nice graphical frontend to gdb with a KDE GUI. It has support for many Qt types (including QString).
*Memory leak tracer : See kdesdk/kmtrace. The README explains it all.
*qdbus and dbusviewer from Qt allow to browse DBus interfaces and to easily make DBus calls.

Sprawdź [[Special:myLanguage/Development/Tools|tę stronę]] i kdesdk, gdzie znajdziesz masę przydatnych skryptów.

===Jak mogę wyświetlić QString w gdb?===

Check out kdesdk, and add this line to your ~/.gdbinit :
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
Then in gdb you can do <code>printqstring myqstring</code> to see its contents.
For instance, <code>QString myqstring = QString::fromLatin1("contents");</code> can be examined using

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.

===I have no symbol when I debug an app that uses kpart, what should I do?===

You must stop just after the main to load the debugging symbols of the shared library. After that, you can debug normally.
One can go as far as creating a gdb macro, to stop right after the part was loaded. For kword, by example, I use:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===Jak debuggować ioslave?===

Zobacz [[Development/Tutorials/Debugging/Debugging IOSlaves|debuggowanie ioslaves]]

=== Why isn't my signal and slot connection working? ===

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==Specyficzne dla KDE 4==

===Czy istnieje preferowana metoda wyświetlania danych z debuggu w stderr?===

Tak, musisz użyć kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

Możliwe jest pominięcie debug area number podczas wywołania kDebug poprzez dodanie następującego kodu do pliku CMakeLists.txt (na najwyższym poziomie):

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

Więcej informacji na ten temat znajdziesz w [http://www.kdedevelopers.org/node/3171 blogu Allena Wintera].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

[[Category:FAQs]]
[[Category:Programming]]

Translations:Development/FAQs/Debugging FAQ/7/pl

2012-06-27T17:38:56Z

Toudidel: Created page with "W pliku $KDEHOME/share/config/drkonqirc dodaj: <syntaxhighlight lang="ini"> [drkonqi] ConfigName=developer </syntaxhighlight>"

W pliku $KDEHOME/share/config/drkonqirc dodaj:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

Thread:User talk:Toudidel/Translating/reply

2012-06-27T17:36:18Z

Toudidel: Reply to Translating

OK, thx for info.

Translations:Edit Markup/2/pl

2012-06-27T14:53:08Z

Toudidel: Created page with "* Typographical_Guidelines systematyzuje znaczniki używane w tłumaczeniu, także oficjalnych podręczników (DocBook) lub na inne języki. Zapoznaj się z tematem, w jaki s..."

* [[Typographical_Guidelines]] systematyzuje znaczniki używane w tłumaczeniu, także oficjalnych podręczników (DocBook) lub na inne języki. Zapoznaj się z tematem, w jaki sposób znacznik może zostać dopasowany do potrzeb tłumacza.