KDE TechBase - User contributions [en]

Development/Further Information

2007-09-02T00:53:12Z

Repinc: /* English */

{{Template:I18n/Language Navigation Bar|Development/Further Information}}
== Web Sites ==
* [http://www.KDE.org KDE Home]
* [http://dot.kde.org KDE Dot News]
* [http://www.planetkde.org Planet KDE]

==Blogs==

== Books ==
Below are a list of books associated with KDE 4 development. These may be specific to applications, using the Qt Toolkit, or specifically KDE 4 books.

===KDE 4 Development Books===

[mailto:manishchaks@gmail.com Manish Chakravarty ] from [http://kde.in KDE India] is working on a KDE 4 programming book.
The scheduled release date is the the 15th of August 2007

===Qt 4 Development Books===

==== English ====

[http://www.qt4-book.com/ The Book of Qt 4: The Art of Building Qt Applications] by Daniel Molkentin

[http://www.phptr.com/bookstore/product.asp?isbn=0131879057&rl=1 An Introduction to Design Patterns in C++ with Qt 4] by Alan Ezust, Paul Ezust

[http://www.phptr.com/bookstore/product.asp?isbn=0131872494&rl=1 C++ GUI Programming with Qt 4] by Jasmin Blanchette, Mark Summerfield

==== German ====

[https://www.opensourcepress.de/index.php?26&backPID=15&tt_products=23 Qt 4: Einführung in die Applikationsentwicklung von Daniel Molkentin]

== IRC Channels ==
In general, IRC channels mentioned here are available on FreeNode. Connect to irc.kde.org, and check these channels out for further information.

*KDE 4 Development - [irc://irc.kde.org:6667/kde4-devel #kde4-devel]
*KDE Development - [irc://irc.kde.org:6667/kde-devel #kde-devel]
*KDevelop - [irc://irc.kde.org:6667/kdevelop #kdevelop]
*Phonon - [irc://irc.kde.org:6667/phonon #phonon]
*Decibel - [irc://irc.kde.org:6667/decibel #decibel]
*Solid - [irc://irc.kde.org:6667/solid #solid]

== Newsgroups ==
== Forums ==
== Events ==
== Courses and Certifications ==
== Audio and Video Casts ==
== Source Code Repositories ==

Development/Architecture/KDE4/Plasma

2007-07-26T18:21:14Z

Repinc:

Plasma is the name of the new desktop planned to replace KDesktop in KDE4. You can think it is a union of [http://netdragon.sf.net SuperKaramba] and KDesktop. But it's more. It's a whole concept of functionality and beauty.

Its implementation is based on the Qt [http://doc.trolltech.com/graphicsview.html Graphics View Framework] introduced in Qt 4.2.

From a developer point of view there are some classes in libplasma who play central roles.

* '''Corona''': extends [http://doc.trolltech.com/qgraphicsscene.html QGraphicsScene] and provides functionality for adding applets and karamba themes.
* '''Widget''': extends [http://doc.trolltech.com/qgraphicsitem.html QGraphicsItem] and works as simple elements in the desktop. There are some built-in in libplasma as icons or buttons.
* '''Applet''': extends Widget and implements sophisticated functionality as rss display, a clock or system monitoring.
* '''DataEngine''': The common use of a DataEngine is to provide data to a applet for display. This allows a user interface elements to show all sorts of data.

===Further reading===
* [http://plasma.kde.org Plasma homesite]
* [http://api.kde.org/4.0-api/kdebase-apidocs/workspace/plasma/html/index.html Plasma API]
* [http://techbase.kde.org/Projects/Plasma Plasma techbase page]

Welcome to KDE TechBase (sl)

2007-07-21T16:09:44Z

Repinc:

{{DISPLAYTITLE:Dobrodošli na KDE TechBase}}

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

'''Pomnite:''' Prevajanje teh Wiki strani je še v teku. Nekatere strani so trenutno na voljo samo v angleščini. Potrudili se bomo, da jih čimprej in čimveč prevedemo v slovenščino. Že v naprej hvala za razumevanje. Vsaka pomoč je dobrodošla.

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;[[Getting Started (sl)|Postavitev okolja za razvoj KDE-ja]]
:Naučite se kako dobiti, zgraditi in poganjati KDE in programe zanj.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;[[Development|Razvoj s KDE]]
:[[Development/Tutorials|Vodiči]] | [http://api.kde.org Dokumentacija API-ja] | [[Development/FAQs|PZV]] in več.
:''Sorodno'': [[Schedules|Urniki izdaj in načrtovane značilnosti]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;[[SysAdmin|Sistemska administracija KDE-ja]]
:Informacije za sistemske administratorje, ki upravljajo z namestitvami KDE-ja.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;[[Contribute|Pridružite se ekipi KDE-ja in prispevajte]]
:Prispevajte popravke, ostanite v stiku in se pridružite eni izmed najboljših odprtokodnih skupnosti.
:''Sorodno:'' [[Policies|Pravila projekta KDE]] | [http://www.kde.org/support/support.php Kako prispevati finančno]
|-
| style="padding-left: 50px;"|[[Image:Action_contents.svg|noframe|left|40px]] ||
;[[ISV|Informacije za ISV-je]]
:Razvijalske informacije za neodvisne prodajalce programske opreme.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;[[Projects|Projekti znotraj KDE-ja]]
:Povezave do razvijalskih Wiki strani, seznamov opravil, itd. za razne projekte znotraj KDE-ja.
|}

Getting Started/Build/KDE4 (sl)

2007-07-21T16:04:26Z

Repinc: Začetek slovenskega prevoda

{{Template:I18n/Language Navigation Bar|Getting_Started/Build/KDE4}}

{{TutorialBrowser|

series=Kako začeti|

name=Grajenje KDE 4 iz izvorne kode|

pre=[[../../Sources/Anonymous_SVN|Hitri vodnik po anonimnem SVN-ju]]|

next=[[../../Set_up_KDE_4_for_development|Nastavitev KDE 4 za razvoj]]|

reading=[http://kdesvn-build.kde.org/ kdesvn-build: orodje za grajenje KDE-ja iz Subversion-a]<br>[[../../Increased_Productivity_in_KDE4_with_Scripts|Povečanje storilnosti v KDE 4 z uporabo skriptov]]<br>[[Development/Tutorials/CMake |Uvod v CMake]]<br>[[../KDE4/FreeBSD|Opombe za FreeBSD]]<br>[[../KDE4/Mac OS X|Navodila za Mac OS X]]<br>[[../KDE4/Windows|Navodila za MS Windows]]|
}}

== Povzetek ==

Ta vodnik prikazuje enega izmed načinov, kako pripraviti KDE iz razvojnega debla, da bo tekel na sistemih Linux in BSD. Na voljo so tudi vodniki za [[/FreeBSD|FreeBSD]], [http://www.kdelibs.com/ Windows], [[/Mac OS X|Mac OS X]] in [http://solaris.kde.org/ Solaris]. Vse skozi vodnik bomo uporabljali ukazno lupino bash.

{{warning|V '''ponedeljek''' lahko pričakujete večje število napak pri gradnji. Takrat se namreč vnaša spremembe v kdelibs. [http://developer.kde.org/~dirk/dashboard/ Dashboard] poroča o nepričakovanih napakah. Spodbudili bi vas radi, da popravite module, ki imajo napake pri gradnji.
}}

== Potrebna programska oprema ==

Da bi uspešno zaključili ta vodnik, morate najprej namestiti sledeče:
* gcc in g++ iz projekta GCC, najbolje različico 4.1 ali višjo
* svn, odjemalec Subversion za nadzor nad revizijami
* pkg-config
* razvijalske knjižnice in datoteke z glavo za X11, OpenGL (mesa-common-dev and libglu1-mesa-dev), libjpeg, libpng, libungif, [http://clucene.sourceforge.net/index.php/Downloads libclucene], [http://download.librdf.org/source/ librdf], libxml2 and libxslt
* skript <tt>makeobj</tt>, ki je del modula kdesdk. Skript lahko naložite kot del paketa kdesdk (kdesdk-scripts na Debian-u), ali pa ga prenesete neposredno [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/makeobj s SVN-ja].
* [http://freedesktop.org/wiki/Software/shared-mime-info paket shared-mime-info], ki je MIME standard organizacije freedesktop.org in ga KDE sedaj uporablja
* [http://boost.org/ boost], ki ga potrebuje kdebase. Da bo CMake našel Boost, mora biti Boost-ova mapa, ki vsebuje podmapo include navedena v spremenljivki CMAKE_INCLUDE_PATH, ali pa morate nastaviti okoljsko spremenljivko BOOST_ROOT, ki kaže na mapo z Boost-om.

=== Kubuntu ===

Da namestite vse potrebne pakete v Kubuntu 7.04 (Feisty Fawn) poženite sledeči ukaz:
<code bash>
sudo aptitude install build-essential cdbs debhelper cmake \
libxml2-dev libxslt1-dev libbz2-dev libclucene-dev librdf-dev \
shared-mime-info libgl1-mesa-dev libglu1-mesa-dev mesa-common-dev \
libxext-dev libjpeg-dev libpng-dev subversion libsm-dev libxinerama-dev \
libxrender-dev libfontconfig-dev libboost-dev libxcursor-dev doxygen \
libungif4-dev libdbus-1-dev libgpgme11-dev libssl-dev libgpgme11-dev \
libasound2-dev
</code>

Ročno nameščanje CMake 2.4.6 in DBus lahko preskočite z:
<code bash>
sudo aptitude install libdbus-1-dev cmake
</code>

Za polno delujočo dokumentacijo programskega vmesnika (API-ja):
<code bash>
sudo aptitude install graphviz
</code>

=== openSUSE ===

V openSUSE 10.2 in novejših lahko pakete namestite z orodjem
[http://en.opensuse.org/Zypper Zypper]:
<code bash>
sudo zypper install <ime-paketa>
</code>

V starejših različicah lahko uporabite YaST:
<code bash>
su
yast -i <ime-paketa>
</code>

'''Potrebni paketi'''

Paketi, ki jih morate namestiti, so:
<code>
xorg-x11-devel
libxml2-devel
kdesdk3
clucene-core-devel
boost-devel
libjpeg-devel
liblrdf-devel
libpng-devel
libxslt-devel
libredland-devel
Mesa-devel
giflib-devel
subversion
gcc
gcc-c++
</code>

'''Neobvezni paketi'''

Ročno nameščanje Qt 4.3, CMake 2.4.6 in DBus lahko preskočite tako, da med vire za nameščanje dodate skladišče KDE4 storitve openSUSE Build.

V openSUSE 10.2 in novejših:
<code>
sudo zypper service-add http://software.opensuse.org/download/KDE:/KDE4/openSUSE_10.2 KDE4-102
</code>

V starejših različicah:
<code>
su
installation_sources -a http://software.opensuse.org/download/KDE:/KDE4/<različica-vašega-suse-linuxa>
</code>

Po tem, ko dodate vir, namestite sledeče pakete (in odvisnosti):
<code>
cmake
dbus-1-devel
libqt4-devel
</code>

Za polno delujočo dokumentacijo programskega vmesnika (API-ja):
<code>
graphviz
</code>

Paketi CMake za openSUSE so na voljo prek [http://software.opensuse.org/download/devel:/tools:/building/ storitve openSUSE Build].

=== Gentoo ===

==== Ročna namestitev ====

Uporabite lahko stabilne ebuilde. Preden začnete ne pozabiti pognati »emerge --sync«.

Nekatere ebuilde je potrebno odmaskirati, ali pa zagotoviti uporabo starejše različice:
<code bash>
# echo 'x11-libs/qt' >> /etc/portage/package.keywords
# echo 'dev-util/cmake' >> /etc/portage/package.keywords
# echo 'dev-cpp/clucene' >> /etc/portage/package.keywords
# echo '>dev-cpp/clucene-0.9.16a' >> /etc/portage/package.mask
</code>

To so ebuildi, ki jih bo potrebno namestiti. Nekateri so morda že nameščeni, zato lahko uporabite možnost »-u«.
<code bash>
$ emerge -avu ebuild/ime
</code>

<code>
sys-devel/gcc
dev-util/subversion
dev-util/pkgconfig
x11-base/xorg-x11
media-libs/glut
media-libs/mesa
media-libs/jpeg
media-libs/libpng
media-libs/giflib
dev-cpp/clucene
dev-util/cppunit
media-libs/liblrdf
dev-libs/libxml2
dev-libs/libxslt
x11-misc/shared-mime-info
kde-base/kdesdk-scripts
dev-libs/boost
x11-libs/qt
dev-util/cmake
sys-apps/dbus
dev-libs/redland
</code>

Če ste namestili vse te ebuilde, lahko preskočite ročno prevajanje in nadaljujete s poglavjem [[Getting_Started/Build/KDE4_(sl)#kdesupport|kdesupport]]

==== Z uporabo sistema portage ====

Pakete za KDE 4 lahko namestite tudi neposredno z:
<code bash>
emerge -a <packagename>
</code>

Najprej [http://gentoo-wiki.com/TIP_Overlays#Layman namestite orodje layman] in si nato prenesite overlay KDE, ki vsebuje poskusne ebuilde za KDE.
<code bash>
layman -a kde
</code>

Za KDE 4 je potrebno nastaviti še določene zastavice USE in povedati sistemu portage naj namesto ebuildov za KDE 3 uporablja ebuilde za KDE 4. Na ta način bo lahko portage sledil vsem odvisnostim.

Podrobna navodila za grajenje KDE 4 v Gentoo-ju lahko najdete na [http://overlays.gentoo.org/proj/kde/wiki Wikiju overlaya za KDE]. O njih se razpravlja na forumu v temi [http://forums.gentoo.org/viewtopic-t-530111-postdays-0-postorder-asc-start-0.html Monolitski ebuildi za KDE 4].

== Ustvarite uporabniški račun za razvoj KDE 4 ==

{{Note|

}}

Getting Started (sl)

2007-07-20T22:43:30Z

Repinc:

{{DISPLAYTITLE:Kako začeti}}
{{Template:I18n/Language Navigation Bar|Getting_Started}}
{{Box|Kako dobiti izvorno kodo|
[[Image:Action_down.svg|right|32px]]
KDE-jeva izvorna koda je na voljo na različne načine:
* [[Getting Started/Sources/Anonymous SVN|Hitri vodnik po anonimnem SVN-ju]]
* [[Getting Started/Sources/Using Subversion with KDE|Uporaba Subversion-a s KDE-jem]] ''Bolj poglobljena predstavitev dostopanja do izvorne kode KDE-ja z uporabo Subversion-a. Vključuje pregled strukture skladišča ter opis dela z revizijami in popravki.''
* [http://websvn.kde.org/ Brskajte po kodi s spletnim brskalnikom]
* [[Getting Started/Sources/Snapshots|Dnevni posnetki]]
|100%}}

{{Box|Kako zgraditi KDE|
[[Image:Action_tool.svg|right|32px]]
Obstaja več vej KDE-ja. Za vsakodnevno uporabo priporočamo stabilno različico KDE-ja.
* [[Getting Started/Build/KDE4|KDE 4 (razvojna različica, trunk)]]
* [[Getting Started/Build/Stable Version|KDE 3.5 (stabilna različica)]]
* [[Getting Started/Build|Druge različice in PZV]] ''Vključuje informacije za gradnjo na sistemih, ki niso Linux.''
|100%}}

{{Box|Nastavitev okolja|
[[Image:Action_pen.svg|right|32px]]
Ko je KDE zgrajen, bo prav prišel dober način poganjanja programov in opravljanja običajnih razvijalskih opravil:
* [[Getting Started/Increased Productivity in KDE4 with Scripts|Povečanje storilnosti v KDE 4 z uporabo skriptov]]
* [[Getting Started/Set up KDE 4 for development|Nastavitev KDE 4 za razvoj]]
|100%}}
[[Category:Build KDE]]

Welcome to KDE TechBase (sl)

2007-07-20T22:26:42Z

Repinc: Povezava do slovenskega prevoda Getting Started

{{DISPLAYTITLE:Dobrodošli na KDE TechBase}}

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

'''Pomnite:''' Prevajanje teh Wiki strani je še v teku. Nekatere strani so trenutno na voljo samo v angleščini. Potrudili se bomo, da jih čimprej in čimveč prevedemo v slovenščino. Vsaka pomoč je dobrodošla. Že v naprej hvala za razumevanje.

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;[[Getting Started (sl)|Postavitev okolja za razvoj KDE-ja]]
:Naučite se kako dobiti, zgraditi in poganjati KDE in programe zanj.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;[[Development|Razvoj s KDE]]
:[[Development/Tutorials|Vodiči]] | [http://api.kde.org Dokumentacija API-ja] | [[Development/FAQs|PZV]] in več.
:''Sorodno'': [[Schedules|Urniki izdaj in načrtovane značilnosti]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;[[SysAdmin|Sistemska administracija KDE-ja]]
:Informacije za sistemske administratorje, ki upravljajo z namestitvami KDE-ja.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;[[Contribute|Pridružite se ekipi KDE-ja in prispevajte]]
:Prispevajte popravke, ostanite v stiku in se pridružite eni izmed najboljših odprtokodnih skupnosti.
:''Sorodno:'' [[Policies|Pravila projekta KDE]] | [http://www.kde.org/support/support.php Kako prispevati finančno]
|-
| style="padding-left: 50px;"|[[Image:Action_contents.svg|noframe|left|40px]] ||
;[[ISV|Informacije za ISV-je]]
:Razvijalske informacije za neodvisne prodajalce programske opreme.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;[[Projects|Projekti znotraj KDE-ja]]
:Povezave do razvijalskih Wiki strani, seznamov opravil, itd. za razne projekte znotraj KDE-ja.
|}

Getting Started (sl)

2007-07-20T22:25:12Z

Repinc: Prvi prevod v slovenščino

{{DISPLAYTITLE:Kako začeti}}
{{Template:I18n/Language Navigation Bar|Getting_Started}}

{{Box|Kako dobiti izvorno kodo|
[[Image:Action_down.svg|right|32px]]
KDE-jeva izvorna koda je na voljo na različne načine:
* [[Getting Started/Sources/Anonymous SVN|Hitri vodnik po anonimnem SVN-ju]]
* [[Getting Started/Sources/Using Subversion with KDE|Uporaba Subversion-a s KDE-jem]] ''Bolj poglobljena predstavitev dostopanja do izvorne kode KDE-ja z uporabo Subversion-a. Vključuje pregled strukture skladišča ter opis dela z revizijami in popravki.''
* [http://websvn.kde.org/ Brskajte po kodi s spletnim brskalnikom]
* [[Getting Started/Sources/Snapshots|Dnevni posnetki]]
|100%}}

{{Box|Kako zgraditi KDE|
[[Image:Action_tool.svg|right|32px]]
Obstaja več vej KDE-ja. Za vsakodnevno uporabo priporočamo stabilno različico KDE-ja.
* [[Getting Started/Build/KDE4|KDE 4 (razvojna različica, trunk)]]
* [[Getting Started/Build/Stable Version|KDE 3.5 (stabilna različica)]]
* [[Getting Started/Build|Druge različice in PZV]] ''Vključuje informacije za gradnjo na sistemih, ki niso Linux.''
|100%}}

{{Box|Nastavitev okolja|
[[Image:Action_pen.svg|right|32px]]
Ko je KDE zgrajen, bo prav prišel dober način poganjanja programov in opravljanja običajnih razvijalskih opravil:
* [[Getting Started/Increased Productivity in KDE4 with Scripts|Povečanje storilnosti v KDE 4 z uporabo skriptov]]
* [[Getting Started/Set up KDE 4 for development|Nastavitev KDE 4 za razvoj]]
|100%}}
[[Category:Build KDE]]

Template:I18n/Language Navigation Bar

2007-07-20T21:48:52Z

Repinc: Adding Slovenian language

<noinclude>
== How to use ==

This template needs to be included in all translations of one page.
Let's assume we have page called "Foo". The translations are called
Foo (de), Foo (fr), etc.

In all translations you _must_ insert the following line:

<nowiki>{{Template:I18n/Language_Navigation_Bar|Foo}}</nowiki>

This will create a correctly linked bar that allows to switch between all translations of a site. If you want to add a new translation language, add
it here and it will appear on all sites. Untranslated versions will appear
red as usual.
</noinclude>
<div style="margin:auto;font-size:83.3%;text-align:left">
<b>Languages:</b>
<span lang="en">[[{{{1}}}|English]]</span> |
<span lanf="da">[[{{{1}}}_(da)|Dansk]]</span> |
<span lang="de">[[{{{1}}}_(de)|Deutsch]]</span> |
<span lang="fr">[[{{{1}}}_(fr)|Français]]</span> |
<span lang="ru">[[{{{1}}}_(ru)|Русский]]</span> |
<span lang="sl">[[{{{1}}}_(sl)|Slovenščina]]</span> |
<span lang="zh_CN">[[{{{1}}}_(zh_CN)|简体中文]]</span>
</div>

Welcome to KDE TechBase (sl)

2007-07-20T21:41:53Z

Repinc: Prvi prevod v slovenščino

{{DISPLAYTITLE:Dobrodošli na KDE TechBase}}

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

'''Pomnite:''' Prevajanje teh Wiki strani je še v teku. Nekatere strani so trenutno na voljo samo v angleščini. Potrudili se bomo, da jih čimprej in čimveč prevedemo v slovenščino. Vsaka pomoč je dobrodošla. Že v naprej hvala za razumevanje.

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;[[Getting Started|Postavitev okolja za razvoj KDE-ja]]
:Naučite se kako dobiti, zgraditi in poganjati KDE in programe zanj.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;[[Development|Razvoj s KDE]]
:[[Development/Tutorials|Vodiči]] | [http://api.kde.org Dokumentacija API-ja] | [[Development/FAQs|PZV]] in več.
:''Sorodno'': [[Schedules|Urniki izdaj in načrtovane značilnosti]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;[[SysAdmin|Sistemska administracija KDE-ja]]
:Informacije za sistemske administratorje, ki upravljajo z namestitvami KDE-ja.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;[[Contribute|Pridružite se ekipi KDE-ja in prispevajte]]
:Prispevajte popravke, ostanite v stiku in se pridružite eni izmed najboljših odprtokodnih skupnosti.
:''Sorodno:'' [[Policies|Pravila projekta KDE]] | [http://www.kde.org/support/support.php Kako prispevati finančno]
|-
| style="padding-left: 50px;"|[[Image:Action_contents.svg|noframe|left|40px]] ||
;[[ISV|Informacije za ISV-je]]
:Razvijalske informacije za neodvisne prodajalce programske opreme.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;[[Projects|Projekti znotraj KDE-ja]]
:Povezave do razvijalskih Wiki strani, seznamov opravil, itd. za razne projekte znotraj KDE-ja.
|}

Projects/Summer of Code/2007/Projects/KAider

2007-07-20T20:41:33Z

Repinc: /* KBabel features NOT to be implemented */

KAider is a computer-aided translation system that focuses on productivity and performance. Translator does only creative work (of delivering message in his/her mother language in laconic and easy to understand form). KAider implies parapgraph-by-paragrah translation approach (when translating documentation) and message-by-message approach (when translating GUI).
See [[Projects/Summer_of_Code/2007/Projects/KAider/Introduction|KAider/Introduction]]

==Current state==
Already has:
* syntax highlighting
* spellcheck (problems with dividing filter:doesnt check the last word)
* search-n-replace, ignoring accel marks
* small features like quick tag insert, placing text cursor right after the tag in the beginning (e.g. '<qt>|foobar</qt>' where "|" is a cursor)
* entry bookmarks
* viewer of the difference between current msgid and previous one (i.e. msgid translation of which current msgstr really is -- for fuzzies generated with --previous gettext option)
* merge mode for editors (QA) or when several translators work on the same file [http://kv-53.narod.ru/kaider2.png screenshot]
* basic projectmanager functionality [http://kv-53.narod.ru/kaider1.png screenshot]
* glossary with basic [http://www.lisa.org/standards/tbx/ tbx] format support. KAider displays relevant entries on-the-fly and provides shortcuts to insert them. also, you can add new glossary terms via context menu of the glossary [http://kv-53.narod.ru/kaider3.png screenshot]
* webquery view, flexible thanks to kross

==Compiling==
After you [[Getting_Started/Build/KDE4|set kde env up]] (compiling kdelibs is enough):
cd trunk
svn up playground/devtools/kaider
su kde-devel
mkdir playground/devtools/kaider/build
cd playground/devtools/kaider/build
cmakekde ..

as a root, run sshd and then from the usual shell:
ssh -XC kde-devel@localhost
kaider

==Roadmap==
*[basic framework DONE] project management -- 1-2 weeks
*[DONE] context glossary -- 0.5-1 week
*translation DB (QtSql) -- 2 weeks
*[DONE] mode for merging translations for editors (QA) -- 1 week
*scripting API + sipping on google translate for live glossary (kross) - 2 weeks
*the remaining time is for perfection/polishing/small improvements and xliff+qt-linguist support

==What i'm doing these days==
*kross WebQuery framework - testing, final refinements
*impovements on ProjectView (dbus, etc), Glossary

==Ideas==
Current:
* Webquery scripts for close languages;
* project-wise and program-wise: webquery scripts, glossaries, TMs
* Glossary editing usability

Further work:
* Research on dividing into sentences rules (e.g. srx)
* Automate submitting translation suggestions to translate.google.com [Kross action]

Not for KDE:
* Be complete computer-aided translation system by providing e.g. actions to import+export openoffice, txt and documents of other formats by calling appropriate scripts/commands. Define for that general kross actions interface.
* Make nice windoze package for the windowzerz

==KBabel features to be implemented==
...in the smarter way :). After or during the summer.
* Character selection tool integration (kdelibs rule); sort by the frequency
* persistent bookmarks for messages in a file saved in the project
* extended marking of .po and .pot files (e.g. translator that currently works on the file and cince when) saved in the project
* Search/Replace functions in multiple files at once.
* Spellchecking of multiple files at once.
* Opening source code by references in message comments [Kross action]
* A plugin framework for validation tools for consistency checks [Kross action triggered on saving]
* Sending the file using email [Kross (project) action]
* Automatic syntax check with msgfmt when saving and, if an error occured, easy navigation to messages, which contain errors. == Syntax check (msgfmt --statistics) for existing files to control if the translated files will compile and, accordingly, work when distributed [Kross (project) action]
* CVS and SVN support [Kross project action] (is 'svn ci' so hard?)
* Automatic comparisons and statistics of POT and PO files for a quick overview which and how many files are translated (or not) and which files may be obsolete + [Kross (project) action] that merges translations with updated template
* PO File Header change [Kross action (+triggered on saving)]
* Printing of selected messages (eg fuzzy ) [Kross action]

==KBabel features NOT to be implemented==
* Automatic ("rough" in kbabel terms) translation. Pure machine translation is a joke. All machine-made translations must be verified by human (and let it be a translator rather than a user).

Why? because sometimes one English string may have two or more different translations depending on the context.

What I'm going to do is implement _interactive_ (or message-by-message) rough translation. If the message is already translated somewhere else, it suggests the translations (several, not one!) and displays them in the helper window. Translator may then choose one of the translation suggestions by pressing ctrl+1, ctrl+2, .. or ctrl+9, which will immediately insert it into msgstr (replacing the old translation if it exists).

What old rough translation didn't provide is the ability to choose.

==Setup==
* Create project, saving *.ktp file to l10n-kde4/<LangCode>
* That's all. Begin populating Glossary via GlossaryView context menu, and .tbx file will be created automatically for you.

User:Danimo/Wiki Scenarios

2007-07-08T11:19:43Z

Repinc: /* Vote */ JLP votes

== Possible Scenarios for future Wiki use on *.kde.org ==

The suggestions below are the outcome of a BoF during Akademy 2007 in Glasgow. We'd especially like to inquire the opinions of the subproject maintainers. Please add your opinions into the discussion page of this page or contact me on IRC. --[[User:Danimo|Danimo]] 12:28, 8 July 2007 (CEST)

=== wiki.kde.org with namespaces ===
'''Note:''' wiki.kde.org will then run mediawiki

*Pros
** Easy to maintain

*Cons
** Might grow very big
** Requires namespaces
** No obvious structure
** No homogenous target audience

Unattractive for subprojects

=== n /wiki per site ===

*Pros
** Very flexible for projects

*Cons
** Sharing templates impossible
** Sharing files quite hard
** Interwiki-Links are of limited use
** n databases

=== n role-based wiki sites ===
'''Description:''' Wikis on domains that target the supposed audience, e.g. users.kde.org.

Possible compromise between the two suggestions above.

*Pros
** Less wiki instances than one per site

*Cons
** Sharing templates impossible
** Sharing files quite hard
** Interwiki-Links are of limited use
** n databases

== Action items ==

* Investigate OpenID
* Investigate which target audiences we/the projects want
* Talk to subprojects
** What solution do they prefer?
** To what extend would they go with whatever we do?
** Whats the additional value for them to join the effort?
* How and where to migrate the contents of the current wikis?

== Vote ==

Please put sign underneath either bullet point that you want to vote for.
Anonymous votes will not be counted.
'''Example:''' <nowiki>**--~~~~</nowiki>

* wiki.kde.org with namespaces
x
* n /wiki per site
* n role-based wiki sites
**--[[User:Repinc|JLP]] 13:19, 8 July 2007 (CEST)

User:Repinc

2007-01-20T20:16:04Z

Repinc: Add link to Parsek developer documentation

I'm '''Jure Repinc''' from Bohinjska Bistrica, Slovenia. Besides being a passionate KDE user I'm also an active translator of KDE into Slovenian language.

When it comes to KDE and Qt development I'm currently just a beginner. To improve my programming skills and have fun at the same time I'm currently (slowly) working on a KDE 4 client for [http://www.thousandparsec.net/tp/ Thousand Parsec] game project. The client is called [http://www.thousandparsec.net/tp/dev/documents/parsek/ Parsek] and with it you will be able to play 4X (eXplore, eXpand, eXploit and eXterminate) space empire building games similar to Stars! and Galactic Civilizations.

You can find more about me on my blog: [http://jlp.holodeck1.com/blog/ JLP's Blog].

Development/Tutorials/KDE3/Qt Designer and KDevelop 3.0 for Beginners

2007-01-10T05:11:12Z

Repinc: /* Introduction */ Fix link to KDevelop

{{improve}}
{{KDE3}}

==Introduction==
To get us started doing something useful with [http://www.trolltech.com/products/qt/features/designer Qt Designer], we are going to build a simple program that will show you the power of Qt Designer and [http://www.kdevelop.org/ KDevelop]. I hope that this will help you to create your first "real" KDE application.

[http://www.kdevelop.org/ KDevelop] will help you to build a complete KDE application. The KDE project uses the autoconf and automake tools for KDE 3.x, and [http://www.kdevelop.org/ KDevelop] will provide you with all the necessary files (admin directory, Makefile.cvs, Makefile.am,...).

==Requirements==

===How to Get Qt Designer===
====From your Distribution====
Qt Designer is part of the qt-3.2.x package and above. If you have an older Qt on your system, you should get at least this version. At the time of writing, Qt latest version is 3.3.2.

Please remember to check if you have all the qt-related packages installed. You need the qt headers in order to compile this tutorial application. These headers usually come in the ''devel'' package. You also need to be sure you have designer. In some distributions, it comes in a separate package.

To check if you have everything, do a:

<code>locate qstring.h</code>

If you get something like ''/usr/lib/qt3/include/qstring.h'' then you can set your ''QTDIR'' variable to ''/usr/lib/qt3/''. In bash environment, this is done by typing:

<code>export QTDIR= /usr/lib/qt3</code>

====Tarball or Anonymous Subversion====
You can download the tarball from the [http://www.trolltech.com/download/qt/x11.html Trolltech website], or get the ''qt-copy'' module from SVN. Please note that Qt for [http://www.kernel.org/ Linux] is [http://www.gnu.org/copyleft/gpl.html GPL].

For an explanation for how to use anonymous SVN, get the ''qt-copy'' and ''kde'' modules and compile them, please see a great documentation at [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]].

You must then set the ''QTDIR'' environment variable. This should point to the directory into which you installed Qt. In bash, for example, you would type:

<code>export QTDIR= /usr/local/qt</code>

provided that ''/usr/local/qt'' is the directory into which you installed Qt. Please read the INSTALL file for more details.

You then compile by issuing the following commands, here is the recommended compile line:

<code>./configure -system-zlib -qt-gif -system-libpng -system-libjpeg \
-plugin-imgfmt-mng -thread -no-exceptions -debug -fast
make</code>

The command ''make install'' is not needed.

Qt Designer is located in the ''bin'' directory of your Qt installation directory. You can run it by typing:
<code>/usr/local/qt/bin/designer</code>
in a console.

To compile Qt from source, please see [http://www.trolltech.com/ Trolltech]'s [http://www.trolltech.com/developer/downloads/qt/x11 Qt/X11 Open Source Edition] page.

===How to get KDevelop 3===
====From your Distribution====
KDevelop 3 should be part of your distribution. Pre 3 versions of KDevelop were nicknamed Gideon, but they are obsolete now.

====From Tarball====
KDevelop can be downloaded from the [http://www.kdevelop.org KDevelop website], under the '''Quick download''' heading.

To compile KDevelop 3, you need qt-3.1.0 or higher and kdelibs-3.1.0 or higher. The environment variables ''QTDIR'' and ''KDEDIR'' should point to those directories.

Don't forget to set up the KDE and Qt paths. The most common errors while using KDevelop come from the environment variables not set up properly. Check in a console by issuing the command '''set''' to see all your environment variables. You should set your ''PATH'' variable as follow as well as your ''LD_LIBRARY_PATH'':

<code>export PATH=$QTDIR/bin:$KDEDIR/bin:$PATH
export LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH</code>

If you have any problem getting KDevelop running, please refer to the [http://www.kdevelop.org/phorum5/ KDevelop Forum] to find the answer to your problem.

If you never used KDevelop before, try to create a new project and to compile it to get used to the interface and the icons.

====KDevelop 3.4====
Please refer to [http://www.kdevelop.org/index.html?filename=3.4/download.html Downloading KDevelop 3.4] and [http://www.kdevelop.org/index.html?filename=3.4/branches_compiling.html Compiling KDevelop 3.4].

===Lexicon===
* '''Widget''': a widget is an element of an graphical interface such as a container window, a button or a field for entering text.
* '''Layout management''': this term describes the way in which widgets are arranged in a window. In its simplest form, an element may be placed at a specific position and given a specific height and width. But when the user resizes the window, the widgets should stay in their position and change their size accordingly. Linux allows to do that by using layouts to place the widgets in.
* '''Signal and Slots''': Signals and slots are used for communication between objects. The signal/slot mechanism is a central feature of Qt. Signals are emitted by objects when they change their state in a way that may be interesting to the outside world. Slots can be used for receiving signals, but they are normal member functions. You can connect as many signals as you want to a single slot, and a signal can be connected to as many slots as you desire. Please see the [http://doc.trolltech.com/3.3/signalsandslots.html TrollTech documentation on signals and slots] for more details. In the excellent online documentation that comes with Qt, you'll find the signals and the public slots that go with each class. You can then implement your own slots.

==Creating the Application==
===Starting the project===
====Creating the framework with KDevelop====

The framework in which our program will sit in (i.e. the main window) can be done easily and quickly by using KDevelop. Start KDevelop and select ''New Project'' in the Project menu. The Application Wizard appears then. Choose a ''C++ -> KDE -> Simple KDE Application''. Fill in the blank lines with the project name '''SigCreate''', your name as author, and your email. Refer to [[:Image:KDevelop3-CreateNewProject.png|this screen shot]] as a reference.

Click on ''Next''. Have a look to the CVS option and the header templates. Then click on ''Finish'' on the last screen. KDevelop creates all the files that you need to compile your project. You can use the file selector to view the code of the 3 files which are main.cpp, sigcreate.cpp and sigcreate.h, as shown [[:Image:KDevelop3-FileSelector.png|here]].

Once the ''Application Wizard'' has created your application, compile it to ensure that everything is fine. To do that, select '''Build -> Run automake & friends''' then '''Build -> Run configure'''. The ''Messages output window'' should say

<code>" Good - your configure finished. Start make now
*
* *** Success ***</code>

so you can run ''make'' with '''Build -> Build Project''' (or using the F8 shortcut). Then '''Build -> Install'''. Then '''Build -> Execute program''' (or F9). The result is shown [[:Image:KDevelop-SigCreate.png|here]].

*'''NOTE''' - If KDevelop does not recognize your ''QTDIR'' and ''KDEDIR'' variables, you can set them in '''Project -> Project Options...''' in ''Configure Options'', as [[:Image:KDevelop3-ConfigureOptions.png|shown]].

====Using Qt Designer====
Qt Designer is a tool for designing and implementing user interfaces. It helps you arranging your widgets on a form and adding a proper layout so your interface can be resized properly. I recommend that you read the [http://doc.trolltech.com/3.3/designer-manual.html Qt Designer manual] to know everything about Qt Designer. Qt Designer includes a code editor but we'll use KDevelop to edit and modify all code.

We will now create the interface of our application using Qt Designer. A form from Qt Designer is saved with a .ui extension because it is then processed by the uic program to generate a .h and .cpp files. KDevelop takes care of that, the only thing we need to do is to create the form.

* '''Note''' - Each time you add or remove a file (now we will add a .ui file) in your KDevelop project, the Makefile.am will be changed. KDevelop does that itself but you will need to ''Run automake & friends'' after such changes.

In KDevelop, click on '''File -> New''' and fill the dialog window that appears. First write the file name: ''sigcreatedlg'' and select what new file you want in the combobox: here we want a ''Widget (.ui)''. Please be sure that '''Add to project''' is checked, this ensures that the Makefile.am is updated. Refer to [[:Image:KDevelop3-NewFile-Widget.png|this screen shot]].

Click the ''OK'' button. The [[:Image:KDevelop3-AutomakeManagerDialog.png|Automake manager dialog]] then pops up. Click the ''OK'' button for this dialog as well.

If the new file ''sigcreatedlg.ui'' is not open in Qt Designer, open the ''Automake Manager'', right-click on the file and select ''Open With'', then ''Qt Designer''. Qt Designer will open.

* '''Note''' - About the names: it is a good idea to finish a dialog name or a form name by ''dlg'' to ensure a nice visibility for people who want to have a look at the code. ''sigcreatedlg'' says that it is a dialog, i.e an interface class, only.

The [[:Image:QtDesigner3-Interface.png|Qt Designer interface]] is essentially split into three areas. On the left is the '''toolbox''', where you can select your widgets. On the right, several dialogs can be selected. I'll keep only the '''Property Editor''' dialog (I close the 2 others). Your widgets can be fine tuned to behave how you want them to. You can choose the size of the widget, its background color (palette), and so on. Between those 2 windows is the '''Form''', your program window, within which you will design your user interface.

* '''Note''' - After adding the ''sigcreatedlg.ui'' file, you will have to run ''Automake & friends'' and ''Run configure'' before building the program. This ensures that the updated ''Makefile.am'' is now read.

===Designing the Program===

Each time you want to use Qt Designer, you should have a precise visual idea of the design of your interface. You can see in [[:Image:KDevelop3-SigCreateDialog.png|this picture]] what the program will be like. It is a window with a number of different items (or widgets) on it, designed so that the user puts the right information in the right boxes. You should always design your program from the user's point of view, as it must be easy to use.

This application creates an email signature, which is then displayed on the screen. The user should enter her/his name, email address, and then select one of three comments. When you click the '''Create!''' button, the generated signature is shown in a ''MultiLineEdit''. When you click '''Cancel''', the program quits.

* '''Note''' - Note that this project is meant as a tutorial, so this is somewhat far away from practical use.

Go back to the Qt Designer window with the new dialog open. You will see that the property editor has been filled with details about the form you have created. The first line in the '''Property Editor''' [[:Image:QtDesigner3-PropertyEditor.png|shows]] the name of the form which is Form1. Click on the field with this name to change it and type SigCreateDlg. This will form the class name of the dialog so you should name it something useful.

To change properties, select the property you wish to change, then alter its setting on the right. Change the '''Caption''' property to "SigCreateDlg v.01". We will now begin to add widgets on our dialog.

===Adding Widgets===

To start, we will insert the text at the top of the program window, which can be seen [[:Image:KDevelop3-NewFile-Widget.png|here]]. This text tells the user how to operate the program. This type of widget is called a ''Label'' and you can put one on your program like this:

# Select the dialog in ToolBox called '''Common Widgets->TextLabel''', or from the menubar '''Tools->Display->TextLabel'''
# The cursor will become a crosshair over the form. Draw a box for the label, just as you would in a paint program, and you will see that the label is created with some dummy text in it.
# To change this text, double click on the label and type in the text, instead of ''TextLabel1''. The text you should type is ''This program will create an email signature for you. Just fill in the boxes and hit the Create! button.'' Select '''Align Center'' to have the text positioned nicely. Refer to this [[:Image:QtDesigner3-TextEditDialog.png|screenshot]].
# Finally, resize the widget using the handles so it is the correct size and at the top of the box. Try to center the label by moving it with the mouse. This is just a temporary measure. Later on we will look at a more elegant layout management technique. You may refer to [[:Image:QtDesigner3-ResizingBox.png|this screenshot]].

You follow pretty much the same procedure for embedding any type of widget that is supported by Qt Designer; select it, drag it, and finally, change its properties and size.

An interesting concept in Qt Designer is that widgets can act as containers for other widgets. This will be demonstrated in our next task, which is to create the input fields inside the frame. You can see that in Picture 8 we have a bunch of labels and text boxes inside a frame. This frame is called a Group Box and acts as a container for the labels and text boxes inside it. Let's first create the frame by selecting the GroupBox in the '''Toolbox dialog->Containers''' or '''Tools->Containers->GroupBox''' from the menubar. You can drag the mouse to create the box just below the Label you put before. In the ''Property Editor'' you can change the title property to alter the text in the frame. Put ''Details'' in the title text field. You may notice a + symbol in this entry in the ''Property Editor''. This indicates that the property has subproperties that can also be changed.

Once you have created the frame (i.e the GroupBox), create three more labels as before but when you draw them, draw them inside the GroupBox frame. You can then see in the Object Explorer box ('''Windows menu -> Views -> Object Explorer''') to the right that the labels have become children of the GroupBox frame. See [[:Image:QtDesigner3-EditingTheDialog.png|this image]].

Change the text of labels by double-clicking on it.

Once you have done this you can then create the text boxes. They will allow the user to type in text like his(her) name and email address. We use the simplest type of text boxes: a widget called QLineEdit which allows the user to enter one line of text only. You have to create two QLineEdit widgets for the name and the email address. You choose the menu Tools then the entry Input then LineEdit and you draw it beside the 'Your Name' Label. Do the same below for the address.

The witty comment will be selected by the user. We use a ComboBox which will present the user with three comments. Click on the ComboBox icon or select it via the Tools-> Input-> ComboBox menu. Draw it beside the Witty Comment label. Then double-click on it. You will be presented with a box into which you can add the contents of the combo box. Click on the 'New Item' button and type in your comment in the text box at the right. Then click again on 'New Item' for the second and third comments. Click on OK when you have finished.

Adjust the size of the different widgets so they are nicely placed.

Up to now, we have not named any of the widgets that are being placed in our program. It is useful to set an internal name for widgets so we can call them after in the program. Labels don't perform any action so they don't need to be named but other widgets do. It is the case now for our text boxes. We'll need to manipulate the data from the three input widgets (i.e. read the text) so we should give them a name. Names should be easily recognized later and they should make sense. The names are assigned via the name property on the top of the Property Editor. We name the top LineEdit nameBox and the second one mailBox. We name the ComboBox commBox. This will allow us to access the comments. So click on each LineEdit and then besides Name in the Property Editor write nameBox and mailBox. Then click on the ComboBox and name it commBox.

We finish the graphical design by adding a label with 'Generated Signature' as text. Below it, we put a TextEdit ('''Tools->Input->TextEdit'''') where the generated signature will be displayed. We name it 'sigBox'. And then we add two PushButtons at the bottom ('Create!' and 'Cancel'). They don't need names but you can give them some if you want.

Save your form. You can now have a quick preview by selecting the menu '''Preview-> Preview Form'''. [[:Image:QtDesigner3-BeforeLayoutManagement.png|This]] is the form ''before'' layout management.

===Getting Spaced Out===
This section describes the layout management. If you resize the preview window you will then notice that the widgets do not adjust appropriately. They are not resized. To improve things, we need to use a feature in Qt called spacers. Spacers are like virtual springs that push the widgets on each side apart.
* '''Note''' - Having a good layout is essential for your application, as when the strings are translated, they might be longer than the English ones and they need to fit on your widgets. The geometry of the widgets has to be nice if the user can resize your window application. Layouts are done by trial and error so use '''Preview->Preview Form''' to see the result of your layout management and to achieve the best layout.

The use of spacers and layout management is a skill that is developed through trial and error. The main thing to remember when dealing with spacers is that you work horizontally first and then vertically.

We will first use spacers to center the text in the top box. Resize your label so that it only get the size of the text. Then we add two spacers, one at each side. Choose the 'spring' icon or menu '''Layout-> Add Spacer'''. You adjust each of the spacers horizontally. Click the space to the left of the text and the blue spacer will appear . Repeat the same procedure for the right. Then add a spacer on the right of the 'Generated Signature' label, and a last one on the left of the the 'Create!' pushbutton. Please use [[:Image:QtDesigner3-AddingTheSpacers.png|this image]] as a reference.

Now that we have spacers to fill blank space, we need a proper layout management. This will allow the widgets to be nicely resized whenever the main window is resized. It is really compulsory to have good layout management. Again, try to resize several times to see if everything is in place. We can use Vertical or horizontal layout or grid management. The top row of widget is horizontal (spacer + label + spacer) so we need Horizontal management. We need to select the three widgets alltogether: click on the first spring, then click on the label while holding down ''Shift'', then on the second spring while holding down ''Shift''. Then click on the Horizontal Layout icon or menu '''Layout-> Lay Out Horizontally'''. You will then see a resizable red line around the three objects to indicate that their layout is being managed. Resize the red box if it needs to.

We can now repeat this procedure for the three labels inside the GroupBox, this time using vertical layout management. The same vertical management for the two LineEdit and the ComboBox. It is better to use vertical management to keep the object aligned. If we use horizontal management for each label + text box then they will not stay aligned and equally sized. Horizontal management is needed for the label with the spacer and another one for the two pushbuttons and the spacer.

To finish the layout, we need to let the form look after the laid-out boxes. We put everything in a grid. This is done by right clicking the form and selecting "Lay Out in a Grid" from the menu. The final design with layout lines should resemble something similar to [[:Image:QtDesigner3-CompleteLayoutManagement.png|this image]].

===Signals and Slots===

[http://doc.trolltech.com/3.0/signalsandslots.html Signals and Slots] are used for communication between Qt objects. The signal/slot mechanism is a central feature of Qt and probably the part that differs most from other toolkits which often use callbacks. In Qt, a signal is emitted by a widget when a particular event occurs, very often triggered by the user like for example pressing a button or writing something in a LineEdit. A slot is simply a function that is called in reponse to a particular signal.

Now the widgets are implemented and the layout is arranged the final thing we need to do in the design stage of the form is to create the signal/slot connections. To do this manually requires a ''connect()'' function but Qt Designer provides a simple yet effective solution. To create the signal/slot connections we need to use the connecting tool. To do this either select the icon (it looks like a red arrow going into a green square) or select '''Tools-> Connect Signals/Slots''' from the menu (or use the F3 shortcut key). To create a connection, click on the form on the widget that is going to be dealing with the slot, drag the line off the form and release the mouse button.

Let's deal first with the Create! button. Click first on the '''Connect Signal/Slot''' icon or select it from the Tools menu or use the F3 key. Then click on the Create! button with the crosshair and drag the line off the form completely. When you have released the mouse button you will see the connections tool shown [[:Image:QtDesigner3-CreateSlot.png|here]].

What we want to do is to create a slot that will create our signature when the user clicks on the Create! button. The signal will be clicked() (you may choose among five signals for a QPushButton) and we need to create the slot then make the connection.

To create the slot we need to click on the '''Edit Slots''' button. The slot creation box then appears. See [[:Image:QtDesigner3-CreateSlot.png|this example]]. Now click on the '''New Function''' button and a slot will appear in the box. Instead of ''new_slot()'' rename it to ''slotCreateSig()'' and leave the access specifier as public. When you click on ''OK'' you will be returned to the connections box and you will see your new slot in the Slots section of the box.

To [[:Image:QtDesigner3-ViewandEditConnections.png|make a connection]] you simply select the appropriate signal (which is ''clicked()'' in our case) and then select the slot (which is our new slot ''slotCreateSig()''). When you have selected both signal and slot you will see the connection made at the bottom of the screen. After you are finished click OK.

Repeat the procedure for the Cancel button by using the clicked() signal and the close() slot. You are now done with the signals and slots.
* '''Warning''' - Don't forget to save your form!

===Generating the Source===

In this tutorial, we use KDevelop subclassing tool in Automake Manager. If you have KDevelop version which has not that capability, then please go to Chapter 7 where I explain this step without the subclass tool.

Here we start with the KDE simple project named SigCreate and the sigcreatedlg.ui that we have added in our project. In the Automake Manager, in the section sigcreate (Program in bin) you must have three files: sigcreatedlg.ui, sigcreate.cpp and main.cpp. The project must compile and give the main window as in picture 3 (creating.html).

As the sigcreate class is no use for us, we will remove it and use it for subclassing the sigcreatedlg.ui file. In the Automake Manager, right click on sigcreate.cpp and select Remove and a dialog pops up. Please check 'Also Remove it from disk'. Then do the same with sigcreate.h. This is the way to remove obsolete files from your project and the Makefile.am will be updated. Remember to run automake & friends and configure before compiling your project again. We will not do it right now because we will make other changes. We will now use the class name SigCreate for the subclass.

In the Automake Manager, in sigcreate (program in bin), right click on sigcreatedlg.ui and choose Subclass Widget... from the context menu that appears. Then fill in the subclass name which is SigCreate. Check the box: Reformat source and click on OK. Say No then about adding these files in cvs as we did not enable this in our project.
Note
You can see that the slot we created in designer is listed here and checked, the method will be implemented in the generated files. If you uncheck it, the code will not be generated in your class.

(The subclass dialog Image)

We have to suppress some lines in main.cpp as the KDE simple project template refers to a KMainWindow which is usually the base class used. But here, SigCreate is based on QWidget. You have to remove all the lines between KApplication app; and return app.exec(); except the ones I keep here:

<code>SigCreate *mainWin = 0;

mainWin = new SigCreate();
app.setMainWidget( mainWin );
mainWin->show();
</code>

===Implementing the Slot===

Then you implement the slot by adding the following lines in the parenthesis of:

<code>
void SigCreate::slotCreateSig()
{}</code>

to implement the slot
<code>
sigBox->append("\n--");
sigBox->append(nameBox->text());
sigBox->append(mailBox->text());
sigBox->append(commBox->currentText());
</code>
and also the corresponding headers of course:
<code>
#include <qlineedit.h>
#include <qcombobox.h>
#include <qmultilineedit.h>
</code<
Run ''Build -> Run automake & friends'', ''Build-> Run Configure'', ''Build -> Build Project'', ''Build -> Install'' (or ''Build->Install as root user''), ''Build -> Execute Program''. That's it! The program is working!

(Picture 20)

A few more words about signals and slots. The signals and slots mechanism is type safe: the signature of a signal must match the signature of the receiving slot (for example, you will connect valueChanged(int) with a slot having an int as argument). And another thing to keep in mind is that all classes that inherit from QObject or one of its subclasses (e.g. QWidget) can contain signals and slots.

All the strings used in KDE program must be wrapped in the i18n() function (klocale.h as header) because all KDE projects are translated. Please see the KDE Translation HowTo to learn more about i18n to make translations for an application.

==In Short==

This is a short resume on how to work with KDevelop and QtDesigner.
* In the KDevelop menu File->New, select a Widget (.ui) file and give it a name (kprojectdlg for that example), check add to Project. Click OK.
* Qt Designer starts. Work on your form in Qt Designer then save your file and close designer. The designer file appears then in KDevelop under User Interface (kprojectdlg.ui).
* Create a new class (KProject as name for example) (Project menu then New class...) that inherits from your dialog file (kprojectdlg) and is a QWidget-childclass.
* Add your slots and others signals or member functions in the inherited class KProject.

== Make the Translations for a Simple KDE Project==

When your own project is finished, you may like to have one or several translations for the GUI. Here is how you can do that.

=== Install gettext Patched for KDE ===

Install a patched gettext that you can find on developer.kde.org and install it in your home directory. The patched gettext can be found there : http://public.kde.planetmirror.com/pub/kde/devel/gettext-kde/

<code>
$ tar xvzf gettext-0.10.35-kde.tar.gz
$ cd gettext-0.10.35-kde
$ ./configure
$ make
$ mkdir -p ~/bin
$ cp src/gettext src/xgettext ~/bin # copy gettext and xgettext into your HOME/bin directory
$ export PATH=~/bin:$PATH
<code>

=== Prepare the Translations ===

Then, go into your project directory :

<code>
$ cd /path/to/myproject
</code>

Set KDEDIR to match your kde installation - on my Mandrake it is /usr This path can also be found by doing "kde-config --prefix"
<code>
$ export KDEDIR=`kde-config --prefix` # or export KDEDIR=/usr
</code>

Then create the translations files :
<code>
$ make -f admin/Makefile.common package-messages
</code>

=== Make the Translations ===

Translate the .po files using kbabel These files are in the po directory of your project.
* Warning - Do not touch the .pot file!

=== Compile and Install the Translations Files ===
<code>
$ make package-messages
$ sudo make install
</code>

==General Tips==
===General Hints===
==== Your Application Name ====

KDE application names generally start with the letter K followed by a name suggesting what the program does. For example, KMail is very simple and tells the user that this is indeed a KDE application and about email. A good practice is to choose an english name for the name that follows the K. Of course, this is just an indication and you are free to do what you want. But a good name can help to get your program known quicker.

* Note - Run a search in Google (in Konqueror, write gg:your_app_name) to see if the name you want to use is not the name of a copyrighted program. If this is the case or if in doubt, change it.

==== Coding Practice ====

Comments should be in English as it is really easier if someone else has a look at your code.

Class names usually are also in English and the names must indicate what the class does. Good examples: TopLevel, CursorInterface, TaskManager. Note the upper case letters and remember that C++ is case-sensitive.

Function names usually begin with a lower case letter and here are examples of good names:

<code>
void activateRaiseOrIconify();
void toDesktop(int);
void windowAdded(WId);
</code>
Code indentation can be whatever you like as long as the code is visible for other developers. Always keep in mind that other people will have a look in your code and try to make it easy to read.

=== Importing your project in KDE CVS ===

Your program interests people, you feel you have time to really work on it, you need more feedback and help for improving it. You also agree to release it under the GPL license or equivalent. You can ask for a cvs account to import it in kdenonbeta. The kdenonbeta module is quite big and is not distributed with the official KDE. It is not packaged nor translated and feature freeze does not apply to kdenonbeta. Its purpose is to allow other developers to work on your application and to test it. Of course, you will need qt-copy, arts and kdelibs from cvs HEAD at least. Please see a tutorial here on how to get started for compiling KDE from cvs HEAD.
Note
When your application has the most important features, when it's totally KDE compatible (i18n, xml GUI, ect.), you will be able to ask for moving it in a KDE official package.

In order to get a cvs account, please follow theses instructions. Send a mail to sysadmin (at) office (dot) kde (dot) org to justify why you need cvs access. Tell that you want to import your application (app_name) in the kdenonbeta module. Make sure to specify your full name and e-mail address, if the From field in your mails doesn't specify them. You can also choose a nickname for your user login. You can currently choose between the standard non-encrypted CVS protocol (pserver) and the encrypted CVS-over-ssh. If you choose pserver, send also an encrypted password (for instance using useradd dummy ; passwd dummy ; grep dummy /etc/passwd /etc/shadow). If you choose CVS-over-ssh, send a public ssh key (e.g. ~/.ssh/id_dsa.pub).

Wait for the answer from a KDE sysadmin.

Once you have compiled at least qt-copy, arts and kdelibs, you need to check out kdenonbeta files. Log in the cvs server with your login user and password.
<code>
$ cvs co -l kdenonbeta
$ cd kdenonbeta
$ cvs co admin (or ln -s ../kde-common/admin .admin)
</code>
You copy your project main dir with everything in kdenonbeta and then, in your project main dir, you issue a:
<code>
$ make disclean
</code>
All the .o files must be gone. You can also remove by hand all Makefile, Makefile.in (not Makefile.am) and all kdevelop related files. Remove the admin, autom4te.cache, debug, doc, po and templates folders. You must just keep some files and the src subdir. Then, you cd .. to go back in kdenonbeta and you type:
<code>
$ make -f Makefile.cvs
$ ./configure --prefix=$KDEDIR
$ cd your_project_name
$ make
$ su -c 'make install'
</code>

All these steps must go well. If there are errors, you should be able to correct them by carefully reading the error message. If you are really stuck, please go to IRC and ask on #kde or #kde-devel, someone will help you.

then, in kdenonbeta dir:

<code>
$ cvs add your_project_name
$ cvs add your_project_name/*
$ cvs add your_project_name/src
$ cvs add your_project_name/src/*
$ cvs commit
</code>

You get the window (vi editor as default) where you can log your message. It's a good practice to note what your commit is about. In your case, you will say (type i first if you are in vi to get in edit mode):

First import of your_app_name which does this and that.

Check if all the files are added correctly. If not, cvs add filename and cvs commit.

Each time you want to work on your project, don't forget to log in the kde server with your user login and password and do a:
<code>
$ cvs up
</code>
to be sure you have the latest version.

Development/Tutorials/KNewStuffSecure

2007-01-10T02:31:04Z

Repinc: /* Resource sharing */ Fix links

{{Improve}}

== Resource sharing ==
Many applications work with external resources which gives them the freedom to change or extend the behavior without requiring to change the application code itself. Others are extensible with the help of binary plugins. All these external resources should be provided in a way to the user, and the most common way is to put them on the homepage of the application, which works, but it is not so convenient to the final user to get the updates. It is much easier to get them from inside the application. Luckily KDE has the corresponding technology called KNewStuff which not only makes possible to download updates and resources, but if the application supports it, it is even possible to share a resource created by the user with other users. KNewStuff has a weak point though, that you cannot really know who created a resource when downloading, nor the maintainer of the resource repository can know who created the resource that was uploaded, and there is no corruption checking either.

Starting with KDE 3.4 and with the introduction of the KNewStuffSecure class this problems are solved. With this technology the resources can be digitally signed, an md5sum is calculated for them, so both the uploaded and downloaded resources can be verified whether they come from a safe source and person or not.

This tutorial will explain how to use KNewStuffSecure in your application to enable downloading and uploading secured resources. It will not explain the usage of KNewStuff itself and how you can set up a resource repository on the server. These informations can be found in the KNewStuff [http://developer.kde.org/documentation/library/cvs-api/knewstuff/html/ API documentation], in the [http://www.kstuff.org/docs/tutorial/ KNewStuff tutorial] and in the sources: <strong>[http://webcvs.kde.org/kdelibs/knewstuff/README.knewstuff?view=markup kdelibs/knewstuff/README.knewstuff]</strong> and <strong>[http://webcvs.kde.org/kdelibs/knewstuff/data kdelibs/knewstuff/data]</strong> .

<hr />

<h2>General information</h2>

<p>Using KNewStuff itself is quite simple, and I tried to make KNewStuffSecure not
more complicated. The only extra requirement is to have <strong>gpg</strong> installed in your
path, and for uploading of course it is preferred if you already have a GPG key
that you can use for resource signing.</p>

<p>As <strong>gpg</strong> is not a compilation time requirement, it is suggested that you check on application startup for its presence and warn the user what he misses without it. Of course the check is performed by KNewStuffSecure as well, but I find it muchnicer to check for runtime dependencies on startup.</p>

<hr />
<h2>Downloading resources</h2>
<p>The first thing you must to is to subclass the KNewStuffSecure class and implement the installResource method, which is a pure virtual method in KNewStuffSecure. Here is an example of what you should put in a header file:</p>
<div class="codeBox">
<pre>
#include <knewstuff/knewstuffsecure.h>
class MyNewStuff: public KNewStuffSecure
{
Q_OBJECT

public:
MyNewStuff(const QString &type, QWidget *parentWidget=0)
:KNewStuffSecure(type, parentWidget){};
~MyNewStuff() {};

private:
virtual void installResource();
};
</pre>
</div>
<p>In order to know what you should do in installResource() it is important to understand the structure of the resource you get via KNewStuffSecure. The resource is a gzipped tarball, let's call it resource.tar.gz. The resource.tar.gz contains three files:
</p>
<table frame="border" border="1">
<thead>
<tr>
<th>Filename</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>data.tar.gz</td>
<td>another tarball containing the actual data to be installed. The
name is not fixed, it can be anything like cards.tgz,
greetings.tar.gz or whatever.</td>
</tr>
<tr>
<td>signature</td>
<td>holds the signature for data.tar.gz</td>
</tr>
<tr>
<td>md5sum</td>
<td>holds the MD5 sum for the data.tar.gz</td>
</tr>
</tbody>
</table>
<p>In the implementation file you have to process the data.tar.gz only, the rest is
handled by KNewStuffSecure. If installing the resource means that you put the
downloaded file(s) from data.tar.gz into a directory, the implementation of
MyNewStuff looks like:
</p>
<div class="codeBox">
<pre>
void MyNewStuff::installResource()
{
bool ok = true;
KTar tar(m_tarName, "application/x-gzip" );
if (tar.open(IO_ReadOnly))
{
const KArchiveDirectory *directory = tar.directory();
QString resDir =KGlobal::dirs()->saveLocation("data" ) + "appname/stuff/";
directory->copyTo(resDir, true);
tar.close();
} else
ok = false;

if (!ok)
KMessageBox::error(parentWidget(), i18n("There was an error with the
downloaded resource tarball file. Possible causes are damaged archive or
invalid directory structure in the archive." ),
i18n("Resource Installation Error" ));
}
</pre>
</div>
<p>As you can see the name of the resource tarball you have to install is in
"m_tarName". The above code installs the files from m_tarName to
<strong>$KDEHOME/share/appname/stuff</strong>. Of course, you must provide the real appname there.
</p>
<p>You are free to do other installation methods, depending on your needs. In some
cases it may be just enough to copy the resource tarball somewhere. This part
of the code depends completely on the type of the resource and your application.
</p>
<p>Now how to initiate a download? You have to do three things:
</p>
<ul>
<li>create a MyNewStuff object</li>
<li>connect the signal installFinished() to a slot to do things what you want after the install is done</li>
<li>call downloadResource() for the MyNewStuff object</li>
</ul>
<p>Example:
</p>
<div class="codeBox">
<pre>
void MyApp::slotDownloadResource()
{
if (!m_newStuff)
{
m_newStuff = new MyNewStuff("appname/resourcetype", this);
connect(m_newStuff, SIGNAL(installFinished()), this, SLOT(slotResourceInstalled()));
}
m_newStuff->downloadResource();
}
</pre>
</div>
<p>Just a note: <em>"appname/resourcetype"</em> is in free form, it identifies the type of the resource. See the standard KNewStuff documentation for details.
</p>

<hr />
<h2>Uploading resources</h2>
<p>Uploading is simple as well. You just have to create
the data.tar.gz (which is specific for your application) and call uploadResource(fileName), where fileName points to the created data tarball.
</p>
<p>Example:</p>
<div class="codeBox">
<pre>
void MyApp::slotUploadResource()
{
QString fileName = createUploadResource();
if (!m_newStuff)
m_newStuff = new MyNewStuff("application/resourcetype", this);
m_newStuff->uploadResource(fileName);
}
</pre>
</div>
<p>Here createUploadResource() creates the data tarball and returns the name with path to the created tarball.
</p>
<p>That is all. I hope you will find this tutorial useful.</p>

Development/Tutorials/Using KXmlGuiWindow

2007-01-08T02:16:40Z

Repinc: Corrected some typos

{{TutorialBrowser|

series=Beginner Tutorial|

name=How To Use KMainWindow|

pre=[[Development/Tutorials/Programming_Tutorial_KDE_4/First_program|Tutorial 1 - Hello World]]|

next=[[Development/Tutorials/Programming_Tutorial_KDE_4/Using_KActions|Tutorial 3 - KActions and XmlGui]]|

reading={{class|KMainWindow}}
}}

==Abstract==
This tutorial carries on from [[Development/Tutorials/Programming_Tutorial_KDE_4/First_program|First Program Tutorial]] and will introduce the {{class|KMainWindow}} class.

In the previous tutorial, the program caused a dialog box to pop up but we're going to take steps towards a functioning application.

[[image:introtokdetutorial2.png|frame|center]]

==Using KMainWindow==

In order to have a useful KMainWindow, we must sub class it. So we create two files, a <tt>MainWindow.cpp</tt> and a <tt>MainWindow.h</tt> which will contain our code.

===MainWindow.h===
<code cppqt n>
#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <KMainWindow>
#include <KTextEdit>

class MainWindow : public KMainWindow
{
public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
};

#endif
</code>
First we Subclass KMainWindow on line 7 with with <tt>class MainWindow : public KMainWindow</tt>.

Then we declare the constructor with <tt>MainWindow(QWidget *parent=0);</tt>.

And finally we declare a pointer to the object that will make up the bulk of our program. {{class|KTextEdit}} is a generic richtext editor with some KDE niceties like cursor auto-hiding.
===MainWindow.cpp===
<code cppqt n>
#include "mainwindow.h"

MainWindow::MainWindow(QWidget *parent) : KMainWindow(parent)
{
textArea = new KTextEdit;
setCentralWidget(textArea);
setupGUI();
}
</code>
First, of course, on line 1 we have to include the header file containing the class declaration.

On line 5, we initialise our text editor with an object. Then on line 6 we use the built-in setCentralWidget() function which tells the KMainWindow what should appear in the central section of the window.

Finally, KMainWindow::setupGUI() is called which does a lot of behind the scene's stuff and creates the default menu bars (Settings, Help).
==Back to main.cpp==
In order to actually run this window, we need to add a few lines in main.cpp:
===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial2",
"Tutorial2", "1.0", "A simple text area",
KAboutData::License_GPL, "(c) 2006" );
KCmdLineArgs::init( argc, argv, &aboutData );

KApplication app;

MainWindow* window = new MainWindow();
window->show();

return app.exec();
}
</code>
The only new lines here (compared to Tutorial 1) are 16 and 17. On line 16, we create our MainWindow object and then on line 17, we display it.

==CMake==
The best way to build the program is to use CMake. All that's changed since tutorial 1 is that <tt>mainwindow.cpp</tt> has been added to the sources list and any <tt>tutorial1</tt> has become <tt>tutorial2</tt>.
===CMakeLists.txt===
<code ini n>
project (tutorial2)
find_package(KDE4 REQUIRED)
include_directories( ${KDE4_INCLUDES} )
set(tutorial2_SRCS
main.cpp
mainwindow.cpp
)
kde4_add_executable(tutorial2 ${tutorial2_SRCS})
target_link_libraries( tutorial2 ${KDE4_KDEUI_LIBS})
</code>
==Moving On==
Now you can move on to [[Development/Tutorials/Programming_Tutorial_KDE_4/Using_KActions|using KActions]].

[[Category:C++]]

User:Repinc

2006-12-24T16:47:28Z

Repinc: Create my personal page

I'm '''Jure Repinc''' from Bohinjska Bistrica, Slovenia. Besides being a passionate KDE user I'm also an active translator of KDE into Slovenian language.

When it comes to KDE and Qt development I'm currently just a beginner. To improve my programming skills and have fun at the same time I'm currently (slowly) working on a KDE 4 client for [http://www.thousandparsec.net/tp/ Thousand Parsec] game project. The client is called '''Parsek''' and with it you will be able to play 4X (eXplore, eXpand, eXploit and eXterminate) space empire building games similar to Stars! and Galactic Civilizations.

You can find more about me on my blog: [http://jlp.holodeck1.com/blog/ JLP's Blog].

Development/Tutorials/Programming Tutorial KDE 4

2006-12-23T17:16:55Z

Repinc: /* Your lessons */ It would be nice to have CMake tutorial. Is the one for Makefiles still neded here?

This is a tutorial to learn KDE programming by examples. It assumes you are working with KDE 4, not KDE 3.

==Overview==
===Basics===
KDE heavily depends on Qt. Many KDE classes inherit from Qt classes. KDE 4 is based on Qt 4, KDE 3 is based on Qt 3. When this tutorial introduces a new Qt class, you're also learning KDE programming.
===Getting Help===
====Finding documentation====
Whenever you have a KDE class and want the API documentation for it (KApplication, for example), point a konqueror window to

<code>kde: KApplication</code>

Be aware that the <tt>kde:</tt> konqueror shortcut only works for classes in kdelibs. If you ask for a class outside of kdelibs or a class that the API search software doesn't know about, you'll be redirected to the main API documentation page. You will need to navigate from there to find the class you're looking for.

If you need to look up the Qt API documentation for a class, you can point a Konqueror window to

<code>qt: QApplication</code>

This can be done in addition to browsing the Qt documentation locally, or using Qt Assistant.

====Finding other developers====
=====Mailing lists=====
There are two main development mailing lists:
*The [http://mail.kde.org/mailman/listinfo/kde-devel kde-devel mailing list] for general development issues
*The [http://mail.kde.org/mailman/listinfo/kde-core-devel kde-core-devel mailing list] for development issues specific to kdelibs, kdebase, and other central development issues

Many other mailing lists for certain applications also existing. Before posting a question, it's always best to make sure you direct it to the right list. Emailing your question to the right list can help you get an answer faster. You can get an overview of the various available mailing lists at http://www.kde.org/mailinglists

=====IRC=====
If you're looking for something a bit more in the instant gratification department, then feel free to ask your question on IRC. KDE uses the [http://www.freenode.org Freenode] network and the easiest way to get on IRC is to point your favorite IRC client to irc.kde.org. There are several IRC clients available for KDE such as konversation and ksirc. There are two main channels for KDE development:
*The [irc://irc.kde.org/kde-devel #kde-devel] channel for general KDE development questions
*The [irc://irc.kde.org/kde4-devel #kde4-devel] channel for questions specific to KDE 4 development

As with mailing lists, many applications have their own IRC channel. However, there currently is not a list of common IRC channels available. If you need to ask a question about a specific application, check that application's home page to see if there's an IRC channel available specifically for that application. If a channel is not listed, it's best to ask your question on one of the above two general development discussion channels.

In order to get the most out of your IRC experience, it's best to follow these guidelines when asking questions:

* If you have a question, just ask it. There's no need to ask if you can ask your question.
* Be prepared to wait for an answer. Even though IRC is more real-time mode of communication, there may not be anyone available to answer your question immediately after you ask it. In general, if you don't receive a response on IRC in about an hour, it's best to send an email.
* Don't ask the question more than once. Even though the channel is active, the right person may not be available to provide an answer. If you are told to wait for a certain person to come online, be sure to ask again when you see them come online. Again, if you don't receive a response to your question in about an hour, it's best to send an email.

==Your lessons==
* [[/First program|First program]]
* [[/How to write an HTML parser|How to write an HTML parser]]
* [[/How to load and save configuration|How to load and save configuration]]
* [[/How to use CMake build system|How to use CMake build system]]
* [http://developer.kde.org/documentation/other/makefile_am_howto/en/index.html How to write Makefile.am]s
* [[/Drag-and-drop|Drag-and-drop]]
* [[/command-line-options|Command line options]]
* [http://edu.kde.org/development/tips.php#HowtodealwithsoundwhencodingaKDEapplication How to write sound programs]
* [[/printing|Printing]]
* [[/rc files|RC files]]
* [[/How to write Kontact plugins|How to write Kontact plugins]]
* [[/Exceptions|How to work with Exceptions]]

==Suggested readings==
http://edu.kde.org/development/tips.php