KDE TechBase - User contributions [en]

Development/Tutorials/Plasma/JavaScript/NowPlaying

2013-05-06T19:32:56Z

Neverendingo:

{{TutorialBrowser|

series=JavaScript Plasmoids|

name=Now Playing: Advanced DataEngine Usage|

pre=[[../DataEngine|Getting Data: How to retreive data from a data engine]]|

next=[[../SystemMonitor|System Monitor: How to access systemmonitor data engine]]|

reading=[[../API|JavaScript Plasmoid API reference]], [[../SystemMonitor|How to access systemmonitor data engine]]
}}

== Abstract ==

This will show you some slightly more advanced techniques for dealing with data engines, and give you a useful plasmoid at the end that you can easily edit to display custom information about what your favourite media player is playing (providing, of course, that your favourite media player is supported by the <tt>nowplaying</tt> data engine).

We assume you've read the [[Development/Tutorials/Plasma/JavaScript/DataEngine|JavaScript data engine tutorial]].

== Main script ==

Create a <tt>contents/code/main.js</tt> file with the following contents:

<syntaxhighlight lang="javascript">
layout = new LinearLayout(plasmoid);
layout.orientation = QtVertical;

label = new Label();
layout.addItem(label);
label.text = "No player found";

function firstSource() {
var sources = dataEngine("nowplaying").sources;
if (sources.length) {
return sources[0];
} else {
label.text = "No player found";
return '';
}
}

plasmoid.dataUpdated = function(name, data) {
if (source == name) {
label.text = 'Info:\n';
for (var key in data) {
label.text += key + ': ' + data[key] + '\n';
}
}
}

source = firstSource();

npDataEngine = dataEngine("nowplaying");

npDataEngine.sourceRemoved.connect(function(name) {
if (name == source) {
source = firstSource();
if (source) {
npDataEngine.connect(source, plasmoid, 500);
}
}
});

npDataEngine.sourceAdded.connect(function(name) {
if (!source) {
source = name;
npDataEngine.connect(source, plasmoid, 500);
}
});

if (source) {
npDataEngine.connectSource(source, plasmoid, 500);
}
</syntaxhighlight>

It looks complicated, compared to the two previous tutorials, but there is really only one new thing, and that is that we're watching for sources appearing and disappearing.

The <tt>nowplaying</tt> data engine makes sources appear and disappear as media players come and go. This plasmoid is a little stupid and only ever watches the first source in the list, but that will be enough for us.

The magic is in listening to the <tt>sourceAdded</tt> and <tt>sourceRemoved</tt> signals of the data engine. These, unsuprisingly, are emitted when the <tt>sources</tt> property of the data engine, which lists all known sources, changes. Note that it may be possible to sensibly request sources that are not in the <tt>sources</tt> property of a data engine - for example, the <tt>twitter</tt> data engine has a theoretically infinite number of sources available, one for each possible twitter account, and these cannot possibly be listed in the <tt>sources</tt> property.

You can learn more about using signals and slots in JavaScript in the [http://doc.trolltech.com/latest/qtscript.html QtScript documentation]. Remember that any property, signal or slot and any method tagged with <tt>Q_INVOKABLE</tt> (see the [http://api.kde.org/4.x-api/kdelibs-apidocs/plasma/html/index.html Plasma API documentation] for which methods this applies to) can be called from JavaScript.

== Challenge ==

Modify <tt>plasmoid.dataUpdate</tt> to display the information you care about, rather than all the information provided by the <tt>nowplaying</tt> data engine.

Development/Tutorials/Plasma/JavaScript/CheatSheet

2013-05-06T17:19:02Z

Neverendingo:

{{TutorialBrowser|

series=JavaScript Plasmoids|

name=Getting Data|

name=JavaScript Plasmoid Cheat Sheet|

pre=[[../SystemMonitor|System Monitor: How to access systemmonitor data engine]]|

reading=[[../API|JavaScript Plasmoid API reference]]
}}

== Basics ==

* Everything but the metadata.desktop file goes in a directory named <tt>contents</tt>
* <tt>X-Plasma-MainScript</tt> in the metadata.desktop file should point to the main script, relative to the contents directory
* <tt>X-Plasma-DefaultSize</tt> in the metadata.desktop file specifies the default widget size in width,height format (eg: 200,100)
* <tt>plasmoidviewer</tt> is an immensely useful tool
* To connect to a signal use <tt>object.signalName.connect(function() {});</tt>
* Enumeration values can be used like
<syntaxhighlight lang="javascript">
if (plasmoid.formFactor() == Vertical) {
layout.setOrientation(QtVertical);
} else {
layout.setOrientation(QtHorizontal);
}
</syntaxhighlight>

== Global variables and functions ==

* The <tt>plasmoid</tt> variable contains all the main plasmoid functionality and represents the main plasmoid widget, and corresponds to the <tt>Applet</tt> class in C++
* The <tt>startupArguments</tt> variable contains any arguments that were passed to the plasmoid when it was started (such as when the plasmoid is registered as a handler for a mimetype)
* The <tt>loadui</tt> function can be used to load a Qt UI file. Beware that a relative path is relative to plasma's working directory (in 4.2 at least), and so may not do what you want.
* The <tt>print</tt> function prints debug output
* There are several constructor methods:
** <tt>PlasmaSvg(file, parent)</tt> constructs a <tt>Plasma::Svg</tt>. The second argument is optional.
** <tt>PlasmaFrameSvg(file, parent)</tt> constructs a <tt>Plasma:FrameSvg</tt>. The second argument is optional.
** <tt>QPainter()</tt>
** <tt>QGraphicsItem()</tt>
** <tt>QTimer()</tt>
** <tt>QFont()</tt>
** <tt>QRectF()</tt>
** <tt>QSizeF()</tt>
** <tt>QPoint()</tt>
** <tt>LinearLayout()</tt> constructs a <tt>QGraphicsLinearLayout</tt>
** <tt>Url()</tt> constructs a <tt>KUrl</tt>
* Plus constructors for all the Plasma widgets (eg: <tt>IconWidget()</tt>).

== Languages ==

* The Name and Comment fields in the <tt>metadata.desktop</tt> file can be translated like <tt>Name[nl]=Hallo JavaScript</tt>
* <tt>i18n()</tt> takes a string (in English) as the first argument, and substitutes in the following arguments to replace %1, %2, %3 etc. Eg: <tt>i18n("The file is called %1", fileName);</tt>
* <tt>i18nc()</tt> works just the same, but has an extra argument at the start that provides some context for translators. Eg: <tt>i18nc("Player name - score", "%1 - %2", playerName, score);</tt>
* <tt>i18np()</tt> is for cases where plural forms might be important. Eg: <tt>i18np("One image in album %2", "%1 images in album %2", imageCount, albumName);</tt>
* <tt>i18ncp()</tt> is a combination of the previous two. Eg: <tt>i18ncp("Personal file", "One file", "%1 files", numFiles);</tt>

== DataEngines ==

* Add a <tt>dataUpdate</tt> method to <tt>plasmoid</tt> to receive updates: <tt>plasmoid.dataUpdate = function(name, data) { /* ... */ }</tt> - <tt>data</tt> contains an object mapping keys to values
* <tt>plasmoid.dataEngine("engine name").connectSource("source name", plasmoid, 500);</tt> updates every half second
* <tt>plasmoid.dataEngine("engine name").connectSource("source name", plasmoid);</tt> updates when new data is available
* <tt>plasmaengineexplorer</tt> is your friend

== Services ==

* Prior to KDE 4.4, DO NOT use <tt>plasmoid.dataEngine("engine name").serviceForSource("source name")</tt> - you will get a dummy service back. Instead, use <tt>plasmoid.service("engine name", "source name")</tt>

=== Notifications ===

If you want to use the standard notifications in KDE, you can using Services, with the following code:

<syntaxhighlight lang="javascript">
engine = dataEngine("notifications");
service = engine.serviceForSource("notification");
op = service.operationDescription("createNotification");
op["appName"] = "foo";
op["appIcon"] = "konqueror";
op["summary"] = "this is a summary";
op["body"] = "body of notification";
op["timeout"] = 2000;

service.startOperationCall(op);
</syntaxhighlight>

Development/Tutorials/Plasma/JavaScript/CheatSheet

2013-05-06T17:18:37Z

Neverendingo:

{{TutorialBrowser|

series=JavaScript Plasmoids|

name=Getting Data|

name=JavaScript Plasmoid Cheat Sheet|

pre=[[.../SystemMonitor|System Monitor: How to access systemmonitor data engine]]|

reading=[[../API|JavaScript Plasmoid API reference]]
}}

== Basics ==

* Everything but the metadata.desktop file goes in a directory named <tt>contents</tt>
* <tt>X-Plasma-MainScript</tt> in the metadata.desktop file should point to the main script, relative to the contents directory
* <tt>X-Plasma-DefaultSize</tt> in the metadata.desktop file specifies the default widget size in width,height format (eg: 200,100)
* <tt>plasmoidviewer</tt> is an immensely useful tool
* To connect to a signal use <tt>object.signalName.connect(function() {});</tt>
* Enumeration values can be used like
<syntaxhighlight lang="javascript">
if (plasmoid.formFactor() == Vertical) {
layout.setOrientation(QtVertical);
} else {
layout.setOrientation(QtHorizontal);
}
</syntaxhighlight>

== Global variables and functions ==

* The <tt>plasmoid</tt> variable contains all the main plasmoid functionality and represents the main plasmoid widget, and corresponds to the <tt>Applet</tt> class in C++
* The <tt>startupArguments</tt> variable contains any arguments that were passed to the plasmoid when it was started (such as when the plasmoid is registered as a handler for a mimetype)
* The <tt>loadui</tt> function can be used to load a Qt UI file. Beware that a relative path is relative to plasma's working directory (in 4.2 at least), and so may not do what you want.
* The <tt>print</tt> function prints debug output
* There are several constructor methods:
** <tt>PlasmaSvg(file, parent)</tt> constructs a <tt>Plasma::Svg</tt>. The second argument is optional.
** <tt>PlasmaFrameSvg(file, parent)</tt> constructs a <tt>Plasma:FrameSvg</tt>. The second argument is optional.
** <tt>QPainter()</tt>
** <tt>QGraphicsItem()</tt>
** <tt>QTimer()</tt>
** <tt>QFont()</tt>
** <tt>QRectF()</tt>
** <tt>QSizeF()</tt>
** <tt>QPoint()</tt>
** <tt>LinearLayout()</tt> constructs a <tt>QGraphicsLinearLayout</tt>
** <tt>Url()</tt> constructs a <tt>KUrl</tt>
* Plus constructors for all the Plasma widgets (eg: <tt>IconWidget()</tt>).

== Languages ==

* The Name and Comment fields in the <tt>metadata.desktop</tt> file can be translated like <tt>Name[nl]=Hallo JavaScript</tt>
* <tt>i18n()</tt> takes a string (in English) as the first argument, and substitutes in the following arguments to replace %1, %2, %3 etc. Eg: <tt>i18n("The file is called %1", fileName);</tt>
* <tt>i18nc()</tt> works just the same, but has an extra argument at the start that provides some context for translators. Eg: <tt>i18nc("Player name - score", "%1 - %2", playerName, score);</tt>
* <tt>i18np()</tt> is for cases where plural forms might be important. Eg: <tt>i18np("One image in album %2", "%1 images in album %2", imageCount, albumName);</tt>
* <tt>i18ncp()</tt> is a combination of the previous two. Eg: <tt>i18ncp("Personal file", "One file", "%1 files", numFiles);</tt>

== DataEngines ==

* Add a <tt>dataUpdate</tt> method to <tt>plasmoid</tt> to receive updates: <tt>plasmoid.dataUpdate = function(name, data) { /* ... */ }</tt> - <tt>data</tt> contains an object mapping keys to values
* <tt>plasmoid.dataEngine("engine name").connectSource("source name", plasmoid, 500);</tt> updates every half second
* <tt>plasmoid.dataEngine("engine name").connectSource("source name", plasmoid);</tt> updates when new data is available
* <tt>plasmaengineexplorer</tt> is your friend

== Services ==

* Prior to KDE 4.4, DO NOT use <tt>plasmoid.dataEngine("engine name").serviceForSource("source name")</tt> - you will get a dummy service back. Instead, use <tt>plasmoid.service("engine name", "source name")</tt>

=== Notifications ===

If you want to use the standard notifications in KDE, you can using Services, with the following code:

<syntaxhighlight lang="javascript">
engine = dataEngine("notifications");
service = engine.serviceForSource("notification");
op = service.operationDescription("createNotification");
op["appName"] = "foo";
op["appIcon"] = "konqueror";
op["summary"] = "this is a summary";
op["body"] = "body of notification";
op["timeout"] = 2000;

service.startOperationCall(op);
</syntaxhighlight>

Development/Tutorials/Plasma/JavaScript/NowPlaying

2013-05-06T17:17:29Z

Neverendingo:

{{TutorialBrowser|

series=JavaScript Plasmoids|

name=Now Playing: Advanced DataEngine Usage|

pre=[[../NowPlaying|Getting Data: How to retreive data from a data engine]]|

next=[[../SystemMonitor|System Monitor: How to access systemmonitor data engine]]|

reading=[[../API|JavaScript Plasmoid API reference]], [[../SystemMonitor|How to access systemmonitor data engine]]
}}

== Abstract ==

This will show you some slightly more advanced techniques for dealing with data engines, and give you a useful plasmoid at the end that you can easily edit to display custom information about what your favourite media player is playing (providing, of course, that your favourite media player is supported by the <tt>nowplaying</tt> data engine).

We assume you've read the [[Development/Tutorials/Plasma/JavaScript/DataEngine|JavaScript data engine tutorial]].

== Main script ==

Create a <tt>contents/code/main.js</tt> file with the following contents:

<syntaxhighlight lang="javascript">
layout = new LinearLayout(plasmoid);
layout.orientation = QtVertical;

label = new Label();
layout.addItem(label);
label.text = "No player found";

function firstSource() {
var sources = dataEngine("nowplaying").sources;
if (sources.length) {
return sources[0];
} else {
label.text = "No player found";
return '';
}
}

plasmoid.dataUpdated = function(name, data) {
if (source == name) {
label.text = 'Info:\n';
for (var key in data) {
label.text += key + ': ' + data[key] + '\n';
}
}
}

source = firstSource();

npDataEngine = dataEngine("nowplaying");

npDataEngine.sourceRemoved.connect(function(name) {
if (name == source) {
source = firstSource();
if (source) {
npDataEngine.connect(source, plasmoid, 500);
}
}
});

npDataEngine.sourceAdded.connect(function(name) {
if (!source) {
source = name;
npDataEngine.connect(source, plasmoid, 500);
}
});

if (source) {
npDataEngine.connectSource(source, plasmoid, 500);
}
</syntaxhighlight>

It looks complicated, compared to the two previous tutorials, but there is really only one new thing, and that is that we're watching for sources appearing and disappearing.

The <tt>nowplaying</tt> data engine makes sources appear and disappear as media players come and go. This plasmoid is a little stupid and only ever watches the first source in the list, but that will be enough for us.

The magic is in listening to the <tt>sourceAdded</tt> and <tt>sourceRemoved</tt> signals of the data engine. These, unsuprisingly, are emitted when the <tt>sources</tt> property of the data engine, which lists all known sources, changes. Note that it may be possible to sensibly request sources that are not in the <tt>sources</tt> property of a data engine - for example, the <tt>twitter</tt> data engine has a theoretically infinite number of sources available, one for each possible twitter account, and these cannot possibly be listed in the <tt>sources</tt> property.

You can learn more about using signals and slots in JavaScript in the [http://doc.trolltech.com/latest/qtscript.html QtScript documentation]. Remember that any property, signal or slot and any method tagged with <tt>Q_INVOKABLE</tt> (see the [http://api.kde.org/4.x-api/kdelibs-apidocs/plasma/html/index.html Plasma API documentation] for which methods this applies to) can be called from JavaScript.

== Challenge ==

Modify <tt>plasmoid.dataUpdate</tt> to display the information you care about, rather than all the information provided by the <tt>nowplaying</tt> data engine.

Development/Tutorials/Plasma/JavaScript/NowPlaying

2013-05-06T17:12:37Z

Neverendingo:

{{TutorialBrowser|

series=JavaScript Plasmoids|

name=Now Playing: Advanced DataEngine Usage|

pre=[[../NowPlaying|Getting Data: How to retreive data from a data engine]]|

next=[[../SystemMonitor|System Monitor: How to access systemmonitor data engine]|

reading=[[../API|JavaScript Plasmoid API reference]], [[../SystemMonitor|How to access systemmonitor data engine]]
}}

== Abstract ==

This will show you some slightly more advanced techniques for dealing with data engines, and give you a useful plasmoid at the end that you can easily edit to display custom information about what your favourite media player is playing (providing, of course, that your favourite media player is supported by the <tt>nowplaying</tt> data engine).

We assume you've read the [[Development/Tutorials/Plasma/JavaScript/DataEngine|JavaScript data engine tutorial]].

== Main script ==

Create a <tt>contents/code/main.js</tt> file with the following contents:

<syntaxhighlight lang="javascript">
layout = new LinearLayout(plasmoid);
layout.orientation = QtVertical;

label = new Label();
layout.addItem(label);
label.text = "No player found";

function firstSource() {
var sources = dataEngine("nowplaying").sources;
if (sources.length) {
return sources[0];
} else {
label.text = "No player found";
return '';
}
}

plasmoid.dataUpdated = function(name, data) {
if (source == name) {
label.text = 'Info:\n';
for (var key in data) {
label.text += key + ': ' + data[key] + '\n';
}
}
}

source = firstSource();

npDataEngine = dataEngine("nowplaying");

npDataEngine.sourceRemoved.connect(function(name) {
if (name == source) {
source = firstSource();
if (source) {
npDataEngine.connect(source, plasmoid, 500);
}
}
});

npDataEngine.sourceAdded.connect(function(name) {
if (!source) {
source = name;
npDataEngine.connect(source, plasmoid, 500);
}
});

if (source) {
npDataEngine.connectSource(source, plasmoid, 500);
}
</syntaxhighlight>

It looks complicated, compared to the two previous tutorials, but there is really only one new thing, and that is that we're watching for sources appearing and disappearing.

The <tt>nowplaying</tt> data engine makes sources appear and disappear as media players come and go. This plasmoid is a little stupid and only ever watches the first source in the list, but that will be enough for us.

The magic is in listening to the <tt>sourceAdded</tt> and <tt>sourceRemoved</tt> signals of the data engine. These, unsuprisingly, are emitted when the <tt>sources</tt> property of the data engine, which lists all known sources, changes. Note that it may be possible to sensibly request sources that are not in the <tt>sources</tt> property of a data engine - for example, the <tt>twitter</tt> data engine has a theoretically infinite number of sources available, one for each possible twitter account, and these cannot possibly be listed in the <tt>sources</tt> property.

You can learn more about using signals and slots in JavaScript in the [http://doc.trolltech.com/latest/qtscript.html QtScript documentation]. Remember that any property, signal or slot and any method tagged with <tt>Q_INVOKABLE</tt> (see the [http://api.kde.org/4.x-api/kdelibs-apidocs/plasma/html/index.html Plasma API documentation] for which methods this applies to) can be called from JavaScript.

== Challenge ==

Modify <tt>plasmoid.dataUpdate</tt> to display the information you care about, rather than all the information provided by the <tt>nowplaying</tt> data engine.

Development/Tutorials/Plasma/JavaScript/SystemMonitor

2013-05-06T17:09:08Z

Neverendingo:

{{TutorialBrowser|

series=JavaScript Plasmoids|

name=System Monitor|

pre=[[../NowPlaying|Now Playing: Advanced DataEngine Usage Example]]|

next=[[../CheatSheet|Cheat Sheet: Common gotchas and useful tips]]|

reading=[[../API|JavaScript Plasmoid API reference]]
}}

This example assumes that you are familiar with previous examples such as [[Development/Tutorials/Plasma/JavaScript/NowPlaying|NowPlaying]] (from which this example was adapted).

Following code illustrates how to connect to systemmonitor and how to receive updates from various data sources.

You should have a working plasmoid application from previous examples. Take a copy of the plasmoid and rename it. After this you can replace contents of the <tt>contents/code/main.js</tt> with following:
<syntaxhighlight lang="javascript">
layout = new LinearLayout(plasmoid);

label = new Label();
layout.addItem(label);
label.text = "No connection";

// current values
var systemData = new Array();

function printData() {
label.text = "";
for (var name in systemData) {
var data = systemData[name];
label.text = label.text + name + ": ";
for (var elt in data) {
label.text = label.text + " " + data[elt];
}
label.text = label.text + "\n";
}
}

plasmoid.dataUpdated = function(name, data) {
systemData[name] = data;
printData();
};

smDataEngine = dataEngine("systemmonitor");

smDataEngine.sourceRemoved.connect(function(name) {
// unsubscribe
smDataEngine.disconnectSource(name, plasmoid);
});

smDataEngine.sourceAdded.connect(function(name) {
if (name.toString().match("^mem/physical")) {
// subscribe
smDataEngine.connectSource(name, plasmoid, 500);
}
});

</syntaxhighlight>

In <tt>smDataEngine.sourceAdded.connect()</tt> we give a function to connect to signal. The signal connection function is called by the systemmonitor for each data source. In this example we only connect to physical memory data sources.

After this the <tt>plasmoid.dataUpdate()</tt> receives updates. Update values are stored into an array. The array is printed on every update.

Note that this example is bit inefficient since we call <tt>printData()</tt> on every update. One way to optimize is to update label text only when "mem/physical/free" data source is updated.

Policies/Kdepim Coding Style

2013-03-06T15:51:50Z

Neverendingo: change language from php to bash

{{Construction}}

== Purpose of this document ==

This document describes the recommended coding style for kdepim. Nobody is
forced to use this style, but to have consistent formatting of the source code
files it is strongly recommended to make use of it.

{{Remember|1=In short: Kdepim coding style follows the
[http://techbase.kde.org/Policies/Kdelibs_Coding_Style Kdelibs coding style].}}

== Rules with test and automatic changes ==

*don't use any <TAB>s
*The change script makes a substitution of any <TAB> with eight spaces.
*The change works for the complete source, even within comments and strings.
*That might be too much and change the vertical alignment of the code.
*Trim the lines
*Only single empty lines should be used.

== Migration ==

As discussed at KDEPIM-Treff, Berlin, 3 March 2013, all the files of KDEPIM will
be reviewed to follow the coding style. This will be done over a long time,
directory after directory, for each of the
rules defined above. For each rule, one can find one or two script(s). The
first script is to check a single file or a complete directory for all .h and
.cpp files.

If present, the second script makes the changes for a single file or a complete
directory for all .h and .cpp files. For some complicated situations, the
script makes no change.

=== The scripts ===
*don't use any <TAB>s
*coding-style-check-Tabs.sh
*coding-style-change-Tabs.sh
*The output of the check is:
{{Output|<syntaxhighlight lang="bash" line>
/home/guy-kde/projects/kdepimlibs/ktnef/ktnefparser.cpp
1->308: Tab at 16: stream_ >> i; // i <- attribute type & name
2->311: Tab at 16: stream_ >> i; // i <- data length
3->326: Tab at 22: case attATTACHMENT: // try to get attachment info
4->367: Tab at 16: stream_ >> u; // u <- checksum
</syntaxhighlight>}}

This shows:
* the name of the file which is under test.
* the number of occurence, the line number, the position found and the line
itself.

=== Trim the lines ===

{{Input| <syntaxhighlight lang="bash" line>
coding-style-check-Trim.sh
coding-style-change-Trim.sh
</syntaxhighlight>}}

=== Check for multiple empty lines ===

{{Input| <syntaxhighlight lang="bash" line>
coding-style-check-Twice.sh
coding-style-change-Twice.sh
</syntaxhighlight>}}

The output of the check is:
{{Output| <syntaxhighlight lang="bash" line>
/home/guy-kde/projects/kdepimlibs/syndication/rss2/enclosure.cpp
1->25: next empty line found
2->26: next empty line found
3->30: next empty line found
</syntaxhighlight>}}

This shows:
* the name of the file which is under test.
* the number of occurrences and the line numbers.

Policies

2013-03-06T11:45:02Z

Neverendingo: Protected "Policies" (‎[edit=sysop] (indefinite) ‎[move=sysop] (indefinite))

There are a couple of written and unwritten rules KDE developers usually adhere to. The following documents summarize some of these policies. The list is still incomplete. If you are interested in helping out with formulating the KDE policies or would like to discuss them please use the kde-policies mailing list which was created for this purpose.

== Policies for Developers ==

These policies apply to KDE developers and it is expected that all persons with a KDE SVN account follow these policies. The SVN commit policy is the most important one. Persons working on libraries (kdelibs mostly, but central libraries in other SVN modules fall under this as well) should read the library documentation policy (and the apidox howto as well).

;[[/SVN Commit Policy|SVN Commit Policy]]
:Rules for commits to the KDE SVN repository. The three golden rules (make sure it compiles, follow existing coding style, use descriptive log messages) and 18 more rules to follow to make sure that your SVN commits are the best they can be.

;[[/SVN Guidelines|Application Life Cycle]]
:Learn all about the Life Cycle of a KDE Application. Where you can upload new application, how to get in one of the main KDE modules and what to do when you give up maintainership of your application.

;[[/Licensing Policy|Licensing Policy]]
:Files in KDE SVN cannot be arbitrarily licensed. This policy explains what licenses are allowed where in the repository. In short: use LGPL for libraries, GPL or BSD for everything else.

;[[/Library Documentation Policy|Library Documentation Policy]]
:Libraries for (re)use should be completely documented. This policy explains why as well as how to document things, and what style to follow. The [[Development/Tutorials/API Documentation|apidox howto]] contains more technical information on writing documentation for libraries.

;[[/Library Code Policy|Library Code Policy]]
:KDE Library API and Code should follow some conventions that are explained in this policy.

;[[/Kdelibs Coding Style|Kdelibs Coding Style]]
:This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formating of the source code files it is recommended to make use of it.

;[[/Kdepim Coding Style|Kdepim Coding Style]]
:This document describes the recommended coding style for kdepim. Nobody is forced to use this style, but to have consistent formating of the source code files it is strengly recommended to make use of it.

;[[/New_KDE_Library_API_Policy|Adding New Classes to kdelibs]]
:Recommendations on how to add new classes or libraries to kdelibs.

;[[/CMake Coding Style|CMake Coding Style]]
:This document describes the recommended coding style for CMake files in KDE.

;[[/CMake and Source Compatibility|CMake and Source Compatibility]]
:Keeping future KDE releases CMake-compatible.

;[[/CMake Commit Policy|CMake Commit Policies]]
:Rules to follow when considering a change to the CMake buildsystem.

;[[/Binary Compatibility Issues With C++|Binary Compatibility Issues With C++]] ([http://developer.kde.org/documentation/other/binarycompatibility.html Original])
:A quick overview of issues with binary compatibility with C++. Keep this in mind while altering the API of kdelibs.

;[[/URI & XML Namespaces Policy|URI & XML Namespaces Policy]]
:Sometimes KDE technologies and applications needs URIs, such as for XML formats. This policy describes practices for that, and how to allocate URIs.

;[[/API to Avoid|API to Avoid]]
:There are classes and functions in Qt or other places that should be avoided by KDE applications.

== Procedures ==

Whereas policies are normative for individual developers -- that is, they describe how developers must behave -- procedures describe how 'the KDE project' as a whole has chosen to behave. We describe what we will do under certain circumstances and why.

;[[/Security Policy|Security Policy]]
:How security problems can be reported to [mailto:security@kde.org security@kde.org] and how the security team responds to security issues.

;[[/Packaging Policy|Packaging Policy]]
:This describes KDE's viewpoint on binary packages and elaborates the statement 'KDE provides source.'

;[[/Minor_Point_Release_Policy|Point Release Policy]]
:Discusses KDE policies for minor point releases.
[[Category:Policies]]

Policies

2013-03-05T22:41:07Z

Neverendingo: Removed protection from "Policies"

There are a couple of written and unwritten rules KDE developers usually adhere to. The following documents summarize some of these policies. The list is still incomplete. If you are interested in helping out with formulating the KDE policies or would like to discuss them please use the kde-policies mailing list which was created for this purpose.

== Policies for Developers ==

These policies apply to KDE developers and it is expected that all persons with a KDE SVN account follow these policies. The SVN commit policy is the most important one. Persons working on libraries (kdelibs mostly, but central libraries in other SVN modules fall under this as well) should read the library documentation policy (and the apidox howto as well).

;[[/SVN Commit Policy|SVN Commit Policy]]
:Rules for commits to the KDE SVN repository. The three golden rules (make sure it compiles, follow existing coding style, use descriptive log messages) and 18 more rules to follow to make sure that your SVN commits are the best they can be.

;[[/SVN Guidelines|Application Life Cycle]]
:Learn all about the Life Cycle of a KDE Application. Where you can upload new application, how to get in one of the main KDE modules and what to do when you give up maintainership of your application.

;[[/Licensing Policy|Licensing Policy]]
:Files in KDE SVN cannot be arbitrarily licensed. This policy explains what licenses are allowed where in the repository. In short: use LGPL for libraries, GPL or BSD for everything else.

;[[/Library Documentation Policy|Library Documentation Policy]]
:Libraries for (re)use should be completely documented. This policy explains why as well as how to document things, and what style to follow. The [[Development/Tutorials/API Documentation|apidox howto]] contains more technical information on writing documentation for libraries.

;[[/Library Code Policy|Library Code Policy]]
:KDE Library API and Code should follow some conventions that are explained in this policy.

;[[/Kdelibs Coding Style|Kdelibs Coding Style]]
:This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formating of the source code files it is recommended to make use of it.

;[[/New_KDE_Library_API_Policy|Adding New Classes to kdelibs]]
:Recommendations on how to add new classes or libraries to kdelibs.

;[[/CMake Coding Style|CMake Coding Style]]
:This document describes the recommended coding style for CMake files in KDE.

;[[/CMake and Source Compatibility|CMake and Source Compatibility]]
:Keeping future KDE releases CMake-compatible.

;[[/CMake Commit Policy|CMake Commit Policies]]
:Rules to follow when considering a change to the CMake buildsystem.

;[[/Binary Compatibility Issues With C++|Binary Compatibility Issues With C++]] ([http://developer.kde.org/documentation/other/binarycompatibility.html Original])
:A quick overview of issues with binary compatibility with C++. Keep this in mind while altering the API of kdelibs.

;[[/URI & XML Namespaces Policy|URI & XML Namespaces Policy]]
:Sometimes KDE technologies and applications needs URIs, such as for XML formats. This policy describes practices for that, and how to allocate URIs.

;[[/API to Avoid|API to Avoid]]
:There are classes and functions in Qt or other places that should be avoided by KDE applications.

== Procedures ==

Whereas policies are normative for individual developers -- that is, they describe how developers must behave -- procedures describe how 'the KDE project' as a whole has chosen to behave. We describe what we will do under certain circumstances and why.

;[[/Security Policy|Security Policy]]
:How security problems can be reported to [mailto:security@kde.org security@kde.org] and how the security team responds to security issues.

;[[/Packaging Policy|Packaging Policy]]
:This describes KDE's viewpoint on binary packages and elaborates the statement 'KDE provides source.'

;[[/Minor_Point_Release_Policy|Point Release Policy]]
:Discusses KDE policies for minor point releases.
[[Category:Policies]]

Thread:User talk:Vgezer/Welcome to the Translator Group

2013-01-22T17:11:27Z

Neverendingo: New thread: Welcome to the Translator Group

Welcome to the Translator group. Please check the Translator Help Pages links in the sidebar before starting work. The link for off-line translation is available in the first combibox when you click "Translate this page".

Enjoy!

User talk:Vgezer

2013-01-22T17:11:27Z

Neverendingo: Talk page autocreated when first thread was posted

Translator Account

2013-01-22T17:09:49Z

Neverendingo:

{{Tip|1=''Example (please add your details to the bottom of the list)''

----

User Name: Hans

Language(s): Swedish

(Optional) Do you expect to work off-line?: No}}

----
----

User Name: Droetker

Language(s): German

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group --[[User:Neverendingo|Neverendingo]] 16:32, 29 January 2012 (UTC)
----
User Name: Prototik

Language(s): Russian

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group --[[User:Neverendingo|Neverendingo]] 16:32, 29 January 2012 (UTC)
----
User Name: phoenixlzx

Language(s): Simplified Chinese

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] 11:57, 13 February 2012 (UTC)
----

User Name: Latif

Language(s): Indonesian

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] 11:57, 13 February 2012 (UTC)
----

User Name: Mitsakoz1989

Language(s): Greek

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] 19:05, 11 March 2012 (UTC)
----

User Name: Amachu

Language(s): Tamil

(Optional) Do you expect to work off-line?: Some times.

Welcome to the Translator group [[User:AnneW|Annew]] 15:52, 22 March 2012 (UTC)
----

User Name: Aracele

Language(s): Brazilian Portuguese

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] 12:07, 26 March 2012 (BST)
----

User Name: Torbjoern

Language(s): German

(Optional) Do you expect to work off-line?: Sometimes

Welcome to the Translator group [[User:AnneW|Annew]] 14:06, 7 April 2012 (BST)
----
User Name: Diogoleal

Language(s): Brazilian Portuguese

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group --[[User:Neverendingo|Neverendingo]] 11:20, 29 April 2012 (BST)
----

User Name: Camilaraw

Language(s): Brazilian Portuguese

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group --[[User:Neverendingo|Neverendingo]] 11:20, 29 April 2012 (BST)
----

User Name: vitorboschi

Language(s): Brazilian Portuguese

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group --[[User:Neverendingo|Neverendingo]] 11:20, 29 April 2012 (BST)
----

User Name: Airon90

Language(s): Esperanto

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] 10:02, 17 May 2012 (BST)
----

User Name: RoEn

Language(s): German, Russian

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] 18:45, 4 June 2012 (BST)
----

User Name: polix

Language(s) German,Russian, Ukrainian

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] 18:45, 4 June 2012 (BST)
----

User Name: TOUDIdel

Language(s) Polish

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] 18:25, 20 June 2012 (BST)
----

User Name: dburgoyn

Language(s) German, French

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] 18:25, 25 June 2012 (BST)
----
User Name: Libertypo

Languages: Romanian, Italian

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] 09:59, 27 June 2012 (BST)
----

User Name: Gallaecio

Language(s): Galician

(Optional) Do you expect to work off-line?: Indeed

Welcome to the Translator group [[User:AnneW|Annew]] 09:48, 22 July 2012 (BST)
----

User Name: shantha

Language(s): Tamil

(Optional) Do you expect to work off-line?: Some times.

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 09:42, 10 August 2012 (BST)
----

User Name: Freetznightsoul

Language(s): Russian

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 12:21, 12 August 2012 (BST)
----
User Name: naveenmtp

Language(s): Tamil

(Optional) Do you expect to work off-line?: Some times.

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 19:40, 16 August 2012 (BST)
----
User Name: Abella

Language(s): Catalan

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 17:57, 18 September 2012 (BST)
----
User Name: Olegkuksa

Language(s): Russian

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 10:09, 4 November 2012 (UTC)
----
User Name: Inzuiqiang

Language(s): 简体中文

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 10:09, 4 November 2012 (UTC)
----
User Name: Fredtantini

Language(s): French

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 10:09, 4 November 2012 (UTC)
----
User Name: PanchoS

Language(s): German

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 10:09, 4 November 2012 (UTC)
----
User Name: KireByte

Language(s): Spanish

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 09:52, 7 November 2012 (UTC)
----
User Name: accumulator

Language(s): Dutch

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 14:08, 12 November 2012 (UTC)
----
User Name: Berryboy2012

Language(s): Chinese

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 10:44, 18 November 2012 (UTC)
----
User Name: 6ahodir

Language(s): Uzbek

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 10:44, 18 November 2012 (UTC)
----
User Name: Aroshni

Language(s): Spanish

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] ([[User talk:AnneW|talk]]) 07:42, 27 November 2012 (UTC)
----

User Name: vgezer

Language(s): Turkish

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group --[[User:Neverendingo|Neverendingo]] ([[User talk:Neverendingo|talk]]) 17:09, 22 January 2013 (UTC)

Template:Construction/de

2013-01-04T14:45:33Z

Neverendingo: Created page with "{{Box1|2={{{2|Im Aufbau}}}|3=40px|1='''Dies ist eine neue Seite, momentan im Aufbau!''' }}Category:Under_Construction <noinclude> Zu..."

{{Box1|2={{{2|Im Aufbau}}}|3=[[Image:Under_construction.png|left|40px]]|1='''Dies ist eine neue Seite, momentan im Aufbau!''' }}[[Category:Under_Construction]]
<noinclude>

Zum Benutzen <nowiki>{{Construction}}</nowiki> an der gewünschten Stelle einfügen.

[[Category:Template/de]]
</noinclude>

Template:Being Edited/de

2013-01-04T14:39:40Z

Neverendingo: Created page with "{{Box1|2={{{2|Momentan in Bearbeitung}}}|3=link=|1='''Diese Seite wird momentan bearbeitet.''' Falls dieser Hinweis für einen ungew..."

{{Box1|2={{{2|Momentan in Bearbeitung}}}|3=[[Image:Being_edited.png|left|40px|link=]]|1='''Diese Seite wird momentan bearbeitet.''' Falls dieser Hinweis für einen ungewöhnlichen Zeitraum besteht melden Sie das bitte entweder auf irc.freenode.org #kde-www oder auf [[User_talk:Annewilson|Annewilson's Diskussionsseite]]. }}
<noinclude>
Zum Benutzen fügen Sie <nowiki>{{Being_Edited}}</nowiki> an die Stelle wo es dargestellt werden soll
[[Category:Template/de]]
</noinclude>

Template:Attention/de

2013-01-04T14:34:50Z

Neverendingo: Created page with "{{Box1|2={{{2|Achtung}}}|3=link=|1={{{1}}} }} <noinclude> Category:Template/de </noinclude>"

{{Box1|2={{{2|Achtung}}}|3=[[Image:Warning.png|left|40px|link=]]|1={{{1}}} }}
<noinclude>
[[Category:Template/de]]
</noinclude>

Template:Warning/de

2013-01-04T14:30:04Z

Neverendingo: Created page with "{{Warning|2={{{2|Warnung}}}|1={{{1}}}}} <noinclude> Category:Template/de </noinclude>"

{{Warning|2={{{2|Warnung}}}|1={{{1}}}}}
<noinclude>
[[Category:Template/de]]
</noinclude>

Template:Tip/de

2013-01-04T14:29:19Z

Neverendingo: Created page with "{{Tip|2={{{2|Tipp}}}|1={{{1}}}}} <noinclude> Category:Template/de </noinclude>"

{{Tip|2={{{2|Tipp}}}|1={{{1}}}}}
<noinclude>
[[Category:Template/de]]
</noinclude>

Template:Note/de

2013-01-04T14:28:27Z

Neverendingo: Created page with "{{Note|2={{{2|Hinweis}}}|1={{{1}}}}} <noinclude> Category:Template/de </noinclude>"

{{Note|2={{{2|Hinweis}}}|1={{{1}}}}}
<noinclude>
[[Category:Template/de]]
</noinclude>

Template:Info/de

2013-01-04T14:27:33Z

Neverendingo: Created page with "{{Info|2={{{2|Information}}}|1={{{1}}}}} <noinclude> Category:Template/de </noinclude>"

{{Info|2={{{2|Information}}}|1={{{1}}}}}
<noinclude>
[[Category:Template/de]]
</noinclude>

Category:Template/de

2013-01-04T14:26:09Z

Neverendingo: Created page with "Category:Template"

[[Category:Template]]

Category:Template

2013-01-04T14:24:31Z

Neverendingo:

These pages are templates to be included in other pages. For a quick discussion of templates see [[Template:Template]]. Normally, you will not add a page to this category directly, but use the markup <nowiki><noinclude>{{Template}}</noinclude></nowiki> which will add the page to this category indirectly.

{{Note|2=Note for translators|1=The category of translated templated have been changed to <nowiki>[[Category:Template/xx]]</nowiki>, where ''xx'' is the language code.}}

{{Remember|2=Use language specific category for translated templates|1=This page is for English templates and for templates without language specific information. Please remember to categorize translated and other language specific templates in a localized template category, like this: <nowiki>[[Category:Template/xx]]</nowiki>}}

User:Neverendingo/de

2013-01-04T14:10:34Z

Neverendingo: Created page with "Dies ist ein Tip"

<languages />
This is a test

<code php> echo "Hello World"; </code>

Some boxes:
{{Box1|2=Example|3=[[Image:Dialog-information.png|left|40px|link=]]|1=Dies ist eine Beispielbox|4=alert-error}}

{{Tip|1=Dies ist ein Tip}}

Translations:User:Neverendingo/5/de

2013-01-04T14:10:34Z

Neverendingo: Created page with "Dies ist ein Tip"

Dies ist ein Tip

User:Neverendingo

2013-01-04T14:10:17Z

Neverendingo: Marked this version for translation

<languages />
<translate>

This is a test


<code php> echo "Hello World"; </code>


Some boxes:</translate>
{{Box1|2=Example|3=[[Image:Dialog-information.png|left|40px|link=]]|1=<translate>
This is an example box</translate>|4=alert-error}}

{{Tip|1=<translate>
This is a tip.</translate>}}

User:Neverendingo

2013-01-04T14:09:52Z

Neverendingo:

Translations:User:Neverendingo/4/de

2013-01-04T14:08:14Z

Neverendingo: Created page with "Dies ist eine Beispielbox"

Dies ist eine Beispielbox

User:Neverendingo/de

2013-01-04T14:08:14Z

Neverendingo: Created page with "Dies ist eine Beispielbox"

<languages />
This is a test

<code php> echo "Hello World"; </code>

Some boxes:
{{Box1|2=Example|3=[[Image:Dialog-information.png|left|40px|link=]]|1=Dies ist eine Beispielbox|4=alert-error}}

User:Neverendingo

2013-01-04T14:07:50Z

Neverendingo: Marked this version for translation

User:Neverendingo

2013-01-04T14:07:42Z

Neverendingo:

<languages />
<translate>
This is a test

<code php> echo "Hello World"; </code>

Some boxes:</translate>
{{Box1|2=Example|3=[[Image:Dialog-information.png|left|40px|link=]]|1=<translate>This is an example box</translate>|4=alert-error}}

Development/Architecture/KDE4/Providing Online Help

2013-01-04T13:58:02Z

Neverendingo: Marked this version for translation

<languages />
<translate>

'''KDE Architecture - Providing online help'''


Making a program easy and intuitive to use involves a wide range of
facilities which are usually called online help. Online help has several,
partially conflicting goals: on the one, it should give the user answers
to the question "How can I do a certain task?", on the other hand it
should help the user exploring the application and finding features he
doesn't yet know about. It is important to recognize that this can only
be achieved by offering several levels of help:


*Tooltips are tiny labels that pop up over user interface elements when the mouse remains there longer. They are especially important for tool- bars, where icons are not always sufficient to explain the purpose of a button.
*"What's this?" help is usually a longer and richer explanation of a widget or a menu item. It is also more clunky to use: In dialogs, it can be invoked in two ways: either by pressing Shift-F1 or by clicking on the question mark in the title bar (where the support of the latter depends on the window manager). The mouse pointer then turns into an arrow with a question mark, and the help window appears when a user interfact element has been clicked. "What's this?" help for menu items is usually activated by a button in the toolbar which contains an arrow and a question mark. The problem with this approach is that the user can't see whether a widget provides help or not. When the user activates the question mark button and doesn't get any help window when clicking on a user interface element, he will get frustrated very quickly. The advantage of "What's this?" help windows as provided by Qt and KDE is that they can contain [http://doc.trolltech.com/4.4/richtext.html rich text], i.e. the may contain different fonts, bold and italic text and even images and tables.
[[Image:Qt3-whatsthis.png|frame|center|QWhatsThis screenshot]]
*Finally, every program should have a manual. A manual is normally viewed in khelpcenter by activating the help menu. That means, a complete additional application pops up and diverts the user from his work. Consequently, consulting the manual should only be necessary if other facilities like tooltips and what's this help are not sufficient. Of course, a manual has the advantage that it does not explain single, isolated aspects of the user interface. Instead, it can explain aspects of the application in a greater context. Manuals for KDE are written using the [http://i18n.kde.org DocBook] markup language.


From the programmer's point of view, Qt provides an easy to use API for online
help. To assign a tooltip to widget, simply use its setToolTip() method.</translate>
<syntaxhighlight lang="cpp">
widget->setToolTip(i18n("This widget does something."))
</syntaxhighlight>
<translate>

If the menu bars and tool bars are created using the [[../Action Pattern|action pattern]], the string used as tooltip is derived from the first argument
of the [http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKAction.html KAction] constructor:
</translate>
<syntaxhighlight lang="cpp">
action = new KAction(i18n("&Delete"), "editdelete",
SHIFT+Key_Delete, actionCollection(), "del")
</syntaxhighlight>
<translate>

Here it is also possible to assign a text which is shown in the status bar when the respective menu item is highlighted:
</translate>
<syntaxhighlight lang="cpp">
action->setStatusText(i18n("Deletes the marked file"))
</syntaxhighlight>
<translate>

The API for "What's this?' help is very similar. In dialogs, use the following
code:
</translate>
<syntaxhighlight lang="cpp">
widget->setWhatsThis(i18n("<qt>This demonstrates Qt's"
" rich text engine.<ul>"
"<li>Foo</li>"
"<li>Bar</li>"
"</ul></qt>"))
</syntaxhighlight>
<translate>

For menu items, use
</translate>
<syntaxhighlight lang="cpp">
action->setWhatsThis(i18n("Deletes the marked file"))
</syntaxhighlight>
<translate>

The invocation of khelpcenter is encapsulated in the
[http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html KToolInvocation]
class. In order to show the manual of your application, just use the static method:
</translate>
<syntaxhighlight lang="cpp">
KToolInvocation::invokeHelp()
</syntaxhighlight>
<translate>

This displays the first page with the table of contents. When
you want to display only a certain section of the manual, you
can give an additional argument to invokeHelp() determining
the anchor which the browser jumps to.


''Initial Author:'' [mailto:bernd@kdevelop.org Bernd Gehrmann]
</translate>
<translate>
[[Category:KDE4]]</translate>
<translate>
[[Category:Architecture]]</translate>

Development/Architecture/KDE4/Providing Online Help

2013-01-04T13:55:52Z

Neverendingo: add translate tags

<languages />
<translate>
'''KDE Architecture - Providing online help'''

Making a program easy and intuitive to use involves a wide range of
facilities which are usually called online help. Online help has several,
partially conflicting goals: on the one, it should give the user answers
to the question "How can I do a certain task?", on the other hand it
should help the user exploring the application and finding features he
doesn't yet know about. It is important to recognize that this can only
be achieved by offering several levels of help:

*Tooltips are tiny labels that pop up over user interface elements when the mouse remains there longer. They are especially important for tool- bars, where icons are not always sufficient to explain the purpose of a button.
*"What's this?" help is usually a longer and richer explanation of a widget or a menu item. It is also more clunky to use: In dialogs, it can be invoked in two ways: either by pressing Shift-F1 or by clicking on the question mark in the title bar (where the support of the latter depends on the window manager). The mouse pointer then turns into an arrow with a question mark, and the help window appears when a user interfact element has been clicked. "What's this?" help for menu items is usually activated by a button in the toolbar which contains an arrow and a question mark. The problem with this approach is that the user can't see whether a widget provides help or not. When the user activates the question mark button and doesn't get any help window when clicking on a user interface element, he will get frustrated very quickly. The advantage of "What's this?" help windows as provided by Qt and KDE is that they can contain [http://doc.trolltech.com/4.4/richtext.html rich text], i.e. the may contain different fonts, bold and italic text and even images and tables.
[[Image:Qt3-whatsthis.png|frame|center|QWhatsThis screenshot]]
*Finally, every program should have a manual. A manual is normally viewed in khelpcenter by activating the help menu. That means, a complete additional application pops up and diverts the user from his work. Consequently, consulting the manual should only be necessary if other facilities like tooltips and what's this help are not sufficient. Of course, a manual has the advantage that it does not explain single, isolated aspects of the user interface. Instead, it can explain aspects of the application in a greater context. Manuals for KDE are written using the [http://i18n.kde.org DocBook] markup language.

From the programmer's point of view, Qt provides an easy to use API for online
help. To assign a tooltip to widget, simply use its setToolTip() method.</translate>
<syntaxhighlight lang="cpp">
widget->setToolTip(i18n("This widget does something."))
</syntaxhighlight>
<translate>
If the menu bars and tool bars are created using the [[../Action Pattern|action pattern]], the string used as tooltip is derived from the first argument
of the [http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKAction.html KAction] constructor:
</translate>
<syntaxhighlight lang="cpp">
action = new KAction(i18n("&Delete"), "editdelete",
SHIFT+Key_Delete, actionCollection(), "del")
</syntaxhighlight>
<translate>
Here it is also possible to assign a text which is shown in the status bar when the respective menu item is highlighted:
</translate>
<syntaxhighlight lang="cpp">
action->setStatusText(i18n("Deletes the marked file"))
</syntaxhighlight>
<translate>
The API for "What's this?' help is very similar. In dialogs, use the following
code:
</translate>
<syntaxhighlight lang="cpp">
widget->setWhatsThis(i18n("<qt>This demonstrates Qt's"
" rich text engine.<ul>"
"<li>Foo</li>"
"<li>Bar</li>"
"</ul></qt>"))
</syntaxhighlight>
<translate>
For menu items, use
</translate>
<syntaxhighlight lang="cpp">
action->setWhatsThis(i18n("Deletes the marked file"))
</syntaxhighlight>
<translate>
The invocation of khelpcenter is encapsulated in the
[http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKToolInvocation.html KToolInvocation]
class. In order to show the manual of your application, just use the static method:
</translate>
<syntaxhighlight lang="cpp">
KToolInvocation::invokeHelp()
</syntaxhighlight>
<translate>
This displays the first page with the table of contents. When
you want to display only a certain section of the manual, you
can give an additional argument to invokeHelp() determining
the anchor which the browser jumps to.

''Initial Author:'' [mailto:bernd@kdevelop.org Bernd Gehrmann]
</translate>
<translate>[[Category:KDE4]]</translate>
<translate>[[Category:Architecture]]</translate>

Development/Architecture/KDE4/Akonadi

2013-01-04T13:51:38Z

Neverendingo: Marked this version for translation

<languages />

'''Akonadi'''

<translate>
Communication, calendaring and keeping information about others are fundamental parts of your daily work and private life.
As a provider of an application development framework and of a Free Software desktop runtime environment, KDE addresses this by tightly integrating with the PIM infrastructure provided by [http://www.akonadi-project.org/ Akonadi].


KDE's implementation of an Akonadi client library stack makes it easy to develop both applications using Akonadi as their data source as well as Akonadi agents for the actual access to the data's persistant storage.

== Concepts == 


Akonadi's design follows the principle of separation of concerns, meaning that each component has a small, well defined role to fullfil in order to achieve a fully functional setup.


There are three main categories of components, all of which are implemented as individual processes for increased system stability and implementation independence:


* Akonadi Server
* Akonadi Agents
* Akonadi Applications

=== Akonadi Server === 


The server category consists of two roles: control and cache.


Control is implemented by a process called '''akonadi_control'''. It is the first to start and controls the life cycle of all components other than end user applications.


Cache is implemented by a process called '''akonadiserver'''. It is the hub for the data flow, tracks changes and is responsible for system consistency, e.g. ensures unique identifiers, etc.


All communication with these two roles is implemented in the KDE client libraries for Akonadi and available to developers at different level of abstraction.
</translate>
{{tip|<translate>
Thinking about the server as a proxy-like service helps to avoid misinterpreting its task, e.g. it is caching data on behalf of its clients, not interpreting or permanently storing it.</translate>}}

<translate>
=== Akonadi Agents === 


The agent category describes processes which perform their task without human interaction.
This includes a special role also referred to as Akonadi Resources, agents which transport data between the cache and the data's actual persistant storage locations, e.g. files.


The KDE client libraries for Akonadi provide convenience classes to ease development of generic agents as well as the resource subtype.
The KDE PIM project provides a set of commonly required implementations as part of their runtime module.

=== Akonadi Applications === 


The application category refers to the usual end user visible application, e.g. address book, calendar or e-mail program. Implementations of this category can sometimes be referred to as Akonadi Clients, since agents can be seen as part of the server-like functionality, both from the point of view of users as well as application developers.


The KDE client libraries for Akonadi provide both a low level job based API as well as high level data models, views and standard actions.</translate>

<translate>== Further reading == </translate>
* <translate>
[[Development/Tutorials#Personal Information Management (Akonadi)|Akonadi Tutorials]]</translate>
* [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/index.html Akonadi KDE API Documentation]
* <translate>
[[Projects/PIM/Akonadi|Akonadi Project Wiki]]</translate>

<translate>
[[Category:KDE4]]</translate>
<translate>
[[Category:Architecture]]</translate>
<translate>
[[Category:Akonadi]]</translate>

Development/Architecture/KDE4/Akonadi

2013-01-04T13:51:09Z

Neverendingo: add translate tags

<languages />

'''Akonadi'''

<translate>Communication, calendaring and keeping information about others are fundamental parts of your daily work and private life.
As a provider of an application development framework and of a Free Software desktop runtime environment, KDE addresses this by tightly integrating with the PIM infrastructure provided by [http://www.akonadi-project.org/ Akonadi].

KDE's implementation of an Akonadi client library stack makes it easy to develop both applications using Akonadi as their data source as well as Akonadi agents for the actual access to the data's persistant storage.

== Concepts ==

Akonadi's design follows the principle of separation of concerns, meaning that each component has a small, well defined role to fullfil in order to achieve a fully functional setup.

There are three main categories of components, all of which are implemented as individual processes for increased system stability and implementation independence:

* Akonadi Server
* Akonadi Agents
* Akonadi Applications

=== Akonadi Server ===

The server category consists of two roles: control and cache.

Control is implemented by a process called '''akonadi_control'''. It is the first to start and controls the life cycle of all components other than end user applications.

Cache is implemented by a process called '''akonadiserver'''. It is the hub for the data flow, tracks changes and is responsible for system consistency, e.g. ensures unique identifiers, etc.

All communication with these two roles is implemented in the KDE client libraries for Akonadi and available to developers at different level of abstraction.
</translate>
{{tip|<translate>Thinking about the server as a proxy-like service helps to avoid misinterpreting its task, e.g. it is caching data on behalf of its clients, not interpreting or permanently storing it.</translate>}}

<translate>
=== Akonadi Agents ===

The agent category describes processes which perform their task without human interaction.
This includes a special role also referred to as Akonadi Resources, agents which transport data between the cache and the data's actual persistant storage locations, e.g. files.

The KDE client libraries for Akonadi provide convenience classes to ease development of generic agents as well as the resource subtype.
The KDE PIM project provides a set of commonly required implementations as part of their runtime module.

=== Akonadi Applications ===

The application category refers to the usual end user visible application, e.g. address book, calendar or e-mail program. Implementations of this category can sometimes be referred to as Akonadi Clients, since agents can be seen as part of the server-like functionality, both from the point of view of users as well as application developers.

The KDE client libraries for Akonadi provide both a low level job based API as well as high level data models, views and standard actions.</translate>

<translate>== Further reading ==</translate>
* <translate>[[Development/Tutorials#Personal Information Management (Akonadi)|Akonadi Tutorials]]</translate>
* [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/index.html Akonadi KDE API Documentation]
* <translate>[[Projects/PIM/Akonadi|Akonadi Project Wiki]]</translate>

<translate>[[Category:KDE4]]</translate>
<translate>[[Category:Architecture]]</translate>
<translate>[[Category:Akonadi]]</translate>

Development/Architecture/KDE4/Akonadi

2013-01-04T13:50:14Z

Neverendingo: add translate tags

<languages />

'''Akonadi'''

<translate>Communication, calendaring and keeping information about others are fundamental parts of your daily work and private life.
As a provider of an application development framework and of a Free Software desktop runtime environment, KDE addresses this by tightly integrating with the PIM infrastructure provided by [http://www.akonadi-project.org/ Akonadi].

KDE's implementation of an Akonadi client library stack makes it easy to develop both applications using Akonadi as their data source as well as Akonadi agents for the actual access to the data's persistant storage.

== Concepts ==

Akonadi's design follows the principle of separation of concerns, meaning that each component has a small, well defined role to fullfil in order to achieve a fully functional setup.

There are three main categories of components, all of which are implemented as individual processes for increased system stability and implementation independence:

* Akonadi Server
* Akonadi Agents
* Akonadi Applications

=== Akonadi Server ===

The server category consists of two roles: control and cache.

Control is implemented by a process called '''akonadi_control'''. It is the first to start and controls the life cycle of all components other than end user applications.

Cache is implemented by a process called '''akonadiserver'''. It is the hub for the data flow, tracks changes and is responsible for system consistency, e.g. ensures unique identifiers, etc.

All communication with these two roles is implemented in the KDE client libraries for Akonadi and available to developers at different level of abstraction.
</translate>
{{tip|Thinking about the server as a proxy-like service helps to avoid misinterpreting its task, e.g. it is caching data on behalf of its clients, not interpreting or permanently storing it.}}

<translate>
=== Akonadi Agents ===

The agent category describes processes which perform their task without human interaction.
This includes a special role also referred to as Akonadi Resources, agents which transport data between the cache and the data's actual persistant storage locations, e.g. files.

The KDE client libraries for Akonadi provide convenience classes to ease development of generic agents as well as the resource subtype.
The KDE PIM project provides a set of commonly required implementations as part of their runtime module.

=== Akonadi Applications ===

The application category refers to the usual end user visible application, e.g. address book, calendar or e-mail program. Implementations of this category can sometimes be referred to as Akonadi Clients, since agents can be seen as part of the server-like functionality, both from the point of view of users as well as application developers.

The KDE client libraries for Akonadi provide both a low level job based API as well as high level data models, views and standard actions.</translate>

<translate>== Further reading ==</translate>
* <translate>[[Development/Tutorials#Personal Information Management (Akonadi)|Akonadi Tutorials]]</translate>
* [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/index.html Akonadi KDE API Documentation]
* <translate>[[Projects/PIM/Akonadi|Akonadi Project Wiki]]</translate>

<translate>[[Category:KDE4]]</translate>
<translate>[[Category:Architecture]]</translate>
<translate>[[Category:Akonadi]]</translate>

Development/Architecture/KDE4/Akonadi

2013-01-04T13:49:02Z

Neverendingo: add translate tags

<languages />

'''Akonadi'''

<translate>Communication, calendaring and keeping information about others are fundamental parts of your daily work and private life.
As a provider of an application development framework and of a Free Software desktop runtime environment, KDE addresses this by tightly integrating with the PIM infrastructure provided by [http://www.akonadi-project.org/ Akonadi].

KDE's implementation of an Akonadi client library stack makes it easy to develop both applications using Akonadi as their data source as well as Akonadi agents for the actual access to the data's persistant storage.

== Concepts ==

Akonadi's design follows the principle of separation of concerns, meaning that each component has a small, well defined role to fullfil in order to achieve a fully functional setup.

There are three main categories of components, all of which are implemented as individual processes for increased system stability and implementation independence:

* Akonadi Server
* Akonadi Agents
* Akonadi Applications

=== Akonadi Server ===

The server category consists of two roles: control and cache.

Control is implemented by a process called '''akonadi_control'''. It is the first to start and controls the life cycle of all components other than end user applications.

Cache is implemented by a process called '''akonadiserver'''. It is the hub for the data flow, tracks changes and is responsible for system consistency, e.g. ensures unique identifiers, etc.

All communication with these two roles is implemented in the KDE client libraries for Akonadi and available to developers at different level of abstraction.
</translate>
{{tip|Thinking about the server as a proxy-like service helps to avoid misinterpreting its task, e.g. it is caching data on behalf of its clients, not interpreting or permanently storing it.}}

<translate>
=== Akonadi Agents ===

The agent category describes processes which perform their task without human interaction.
This includes a special role also referred to as Akonadi Resources, agents which transport data between the cache and the data's actual persistant storage locations, e.g. files.

The KDE client libraries for Akonadi provide convenience classes to ease development of generic agents as well as the resource subtype.
The KDE PIM project provides a set of commonly required implementations as part of their runtime module.

=== Akonadi Applications ===

The application category refers to the usual end user visible application, e.g. address book, calendar or e-mail program. Implementations of this category can sometimes be referred to as Akonadi Clients, since agents can be seen as part of the server-like functionality, both from the point of view of users as well as application developers.

The KDE client libraries for Akonadi provide both a low level job based API as well as high level data models, views and standard actions.</translate>

<translate>== Further reading ==</translate>
* <translate>[[Development/Tutorials#Personal Information Management (Akonadi)|Akonadi Tutorials]]</translate>
* [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/index.html Akonadi KDE API Documentation]
* <translate>[[Projects/PIM/Akonadi|Akonadi Project Wiki]]</translate>

[[Category:KDE4]]
[[Category:Architecture]]
[[Category:Akonadi]]

Category:Phonon

2013-01-04T01:19:53Z

Neverendingo: Marked this version for translation

<languages />

==<translate>
Multimedia Unleashed</translate>==
<translate>
With Phonon, KDE developers will be able to write applications with multimedia functionality in a fraction of the time needed with one of the above mentioned media frameworks/libs. This will facilitate the usage of media capabilities in the KDE desktop and applications. </translate>

<translate>
Applications will not be responsible anymore for the configuration of multimedia hardware. The settings will be available in one central place, and especially with the development of Solid, KDE will see a more consistent desktop in this regard.</translate>

<translate>
[[Category:Architecture]]</translate>
<translate>
[[Category:KDE4]]</translate>

Category:Phonon

2013-01-04T01:19:45Z

Neverendingo: add translate tags

<languages />

==<translate>Multimedia Unleashed</translate>==
<translate>With Phonon, KDE developers will be able to write applications with multimedia functionality in a fraction of the time needed with one of the above mentioned media frameworks/libs. This will facilitate the usage of media capabilities in the KDE desktop and applications. </translate>

<translate>Applications will not be responsible anymore for the configuration of multimedia hardware. The settings will be available in one central place, and especially with the development of Solid, KDE will see a more consistent desktop in this regard.</translate>

<translate>[[Category:Architecture]]</translate>
<translate>[[Category:KDE4]]</translate>

Development/Architecture/KDE4/Solid

2013-01-04T01:17:54Z

Neverendingo: Marked this version for translation

<languages />

== <translate>
Seamless Hardware Interaction</translate> ==
<translate>
With Solid, KDE developers are able to easily write applications with hardware interaction features. The necessary abstraction to support
cross-platform application development is provided by Solid's clear and comprehensive API.</translate>

<translate>
Its aim is not the control of the devices (Solid doesn't let you synchronize your mobile phone with your local address book): Solid ''looks for'' devices and gives you access to the information it has about them. This way, you could easily look at the functions of the cpu, or at the driver that handles your camera, or the mount point of your usb pen. In sum: it gives you the possibility of "seeing without touching" your devices.</translate>

<translate>
Now you would ask (at least, I asked myself): "Why should I need this library? I want to control the available hardware, not just see it!"</translate>

<translate>
Well, Solid helps you a lot again: for any device interface, it gives you enough information to easily access it using other libraries or stacks. This way, if you want to manage your camera, you can use Solid to recognize it (you can use Solid::Notifier that will let you know when your camera has been plugged in), and then you can ask Solid to give you the information you need to handle it, for example with GPhoto or any other library you can think of. The same applies for any other plugged device: DVB cards (once recognized, Solid gives you the name of the associated device), audio cards (you can use ALSA, OSS or whatever you want: Solid knows the data to access it), portable media players, network cards, et cetera.
Moreover, it lets you check if you're connected to any network or not, and you can use Solid to tell the system to connect (that is, you can ask Solid: "Give me access to the network, I don't want to care about details").</translate>

<translate>
Anyway, some other things need to be said about network devices and Bluetooth. For these two classes of devices, Solid provides the "Control" namespace: that is, it lets you control them directly, without using external libraries. This means that with Solid, you can even handle your wireless or wired network interfaces, associate them to an essid, and choose ip configuration for them. You can even access your phone through Bluetooth, and so on.</translate>

<translate>
The "listing" part of Solid resides in kdelibs, while the Control namespace is in kdebase.</translate>

== <translate>
Architecture Summary</translate> ==

<translate>
Solid was implemented using a frontend/backend approach aiming portability among platforms like Linux and Windows. The frontend provides the high-level API for developers using Solid and backends deal with the specific hardware issues for the different platforms.</translate>

=== <translate>
Frontend View</translate> ===

<translate>
The frontend classes provide the API for developers and are also wrappers for several kinds of devices. All frontend clases are available in ''kdelibs/solid/solid''.</translate>

==== Solid::DeviceNotifier ====
<translate>
The device notifier is a singleton used to obtain information about the hardware available on the system. It provides to applications the unique entry point for hardware discovery and/or notifications about changes (with the use of Solid::DeviceNotifier::deviceAdded(const QString) and Solid::DeviceNotifier::deviceRemoved(const QString) signals). This class calls the following Solid::DeviceManager.</translate>

==== Solid::DeviceManager ====

<translate>
This (private) class maintains the state of all devices currently available on the system. Through it is possible to get, for example, the list of all devices or a list of device matching with some criteria (using Solid::Predicate).</translate>

==== Solid::Device ====

<translate>
This class represents a general hardware device. A device contains one or more device interfaces (capabilities).</translate>

==== Solid::DeviceInterface ====

<translate>
A device interface represents a certain feature that a device contains. This class is on the top of the device interfaces inheritance tree. All specialized device interfaces implement it.</translate>

==== <translate>
Specialized classes (Solid::Processor, Solid::OpticalDrive, Solid::Battery, etc.)</translate> ====

<translate>
These classes actually represent the capabilities that a device can have. All classes extend Solid::DeviceInterface.</translate>

=== <translate>
Backend View</translate> ===

<translate>
A Solid backend deal with the platform-specific ways of handle devices. Developers using libsolid do not use the backend classes directly. Applications do it through frontend/wrapping classes in the Solid namespace.</translate>

<translate>
All backends have to implement the interfaces in ''kdelibs/solid/solid/ifaces'' (namespace Solid::Ifaces) correspondent to its devices. These interfaces are the basics of which API a given device has to provide to the frontend classes.</translate>

=== <translate>
UML Diagram</translate> ===

<translate>
This diagram shows the relationships between the Solid frontend classes and the platform-specific backend classes (''Foo'' backend).</translate>

[[File:Solid_Class_diagram.png|600px]]

<translate>
[[Category:KDE4]]</translate>
<translate>
[[Category:Architecture]]</translate>
<translate>
[[Category:Solid]]</translate>

Development/Architecture/KDE4/Solid

2013-01-04T01:16:39Z

Neverendingo: add translate tags

<languages />

== <translate>Seamless Hardware Interaction</translate> ==
<translate>With Solid, KDE developers are able to easily write applications with hardware interaction features. The necessary abstraction to support
cross-platform application development is provided by Solid's clear and comprehensive API.</translate>

<translate>Its aim is not the control of the devices (Solid doesn't let you synchronize your mobile phone with your local address book): Solid ''looks for'' devices and gives you access to the information it has about them. This way, you could easily look at the functions of the cpu, or at the driver that handles your camera, or the mount point of your usb pen. In sum: it gives you the possibility of "seeing without touching" your devices.</translate>

<translate>Now you would ask (at least, I asked myself): "Why should I need this library? I want to control the available hardware, not just see it!"</translate>

<translate>Well, Solid helps you a lot again: for any device interface, it gives you enough information to easily access it using other libraries or stacks. This way, if you want to manage your camera, you can use Solid to recognize it (you can use Solid::Notifier that will let you know when your camera has been plugged in), and then you can ask Solid to give you the information you need to handle it, for example with GPhoto or any other library you can think of. The same applies for any other plugged device: DVB cards (once recognized, Solid gives you the name of the associated device), audio cards (you can use ALSA, OSS or whatever you want: Solid knows the data to access it), portable media players, network cards, et cetera.
Moreover, it lets you check if you're connected to any network or not, and you can use Solid to tell the system to connect (that is, you can ask Solid: "Give me access to the network, I don't want to care about details").</translate>

<translate>Anyway, some other things need to be said about network devices and Bluetooth. For these two classes of devices, Solid provides the "Control" namespace: that is, it lets you control them directly, without using external libraries. This means that with Solid, you can even handle your wireless or wired network interfaces, associate them to an essid, and choose ip configuration for them. You can even access your phone through Bluetooth, and so on.</translate>

<translate>The "listing" part of Solid resides in kdelibs, while the Control namespace is in kdebase.</translate>

== <translate>Architecture Summary</translate> ==

<translate>Solid was implemented using a frontend/backend approach aiming portability among platforms like Linux and Windows. The frontend provides the high-level API for developers using Solid and backends deal with the specific hardware issues for the different platforms.</translate>

=== <translate>Frontend View</translate> ===

<translate>The frontend classes provide the API for developers and are also wrappers for several kinds of devices. All frontend clases are available in ''kdelibs/solid/solid''.</translate>

==== Solid::DeviceNotifier ====
<translate>The device notifier is a singleton used to obtain information about the hardware available on the system. It provides to applications the unique entry point for hardware discovery and/or notifications about changes (with the use of Solid::DeviceNotifier::deviceAdded(const QString) and Solid::DeviceNotifier::deviceRemoved(const QString) signals). This class calls the following Solid::DeviceManager.</translate>

==== Solid::DeviceManager ====

<translate>This (private) class maintains the state of all devices currently available on the system. Through it is possible to get, for example, the list of all devices or a list of device matching with some criteria (using Solid::Predicate).</translate>

==== Solid::Device ====

<translate>This class represents a general hardware device. A device contains one or more device interfaces (capabilities).</translate>

==== Solid::DeviceInterface ====

<translate>A device interface represents a certain feature that a device contains. This class is on the top of the device interfaces inheritance tree. All specialized device interfaces implement it.</translate>

==== <translate>Specialized classes (Solid::Processor, Solid::OpticalDrive, Solid::Battery, etc.)</translate> ====

<translate>These classes actually represent the capabilities that a device can have. All classes extend Solid::DeviceInterface.</translate>

=== <translate>Backend View</translate> ===

<translate>A Solid backend deal with the platform-specific ways of handle devices. Developers using libsolid do not use the backend classes directly. Applications do it through frontend/wrapping classes in the Solid namespace.</translate>

<translate>All backends have to implement the interfaces in ''kdelibs/solid/solid/ifaces'' (namespace Solid::Ifaces) correspondent to its devices. These interfaces are the basics of which API a given device has to provide to the frontend classes.</translate>

=== <translate>UML Diagram</translate> ===

<translate>This diagram shows the relationships between the Solid frontend classes and the platform-specific backend classes (''Foo'' backend).</translate>

[[File:Solid_Class_diagram.png|600px]]

<translate>[[Category:KDE4]]</translate>
<translate>[[Category:Architecture]]</translate>
<translate>[[Category:Solid]]</translate>

Development/Architecture/KDE4/KParts

2013-01-04T00:45:45Z

Neverendingo: Marked this version for translation

<languages />

<translate>
'''KParts''' is the name of the component framework for KDE. An individual component is called a '''KPart'''. As an example, Konsole is available as a KPart and is used in applications like Konqueror and Kate. Good examples about how KParts can be used are Konqueror, which (among other things) uses the KWord part to display documents, KMPlayer part to play multimedia, and Kontact, which embeds kdepim applications under one roof.</translate>

<translate>
KParts also provide flexibility in your software selection. For example, the KHTML part which is by default used by Konqueror for HTML rendering can very easily be exchanged by a Webkit KPart.</translate>

===<translate>
Further reading</translate>===
* <translate>
[[Special:myLanguage/Development/Tutorials/Using_KParts|Techbase Tutorial: "Using KParts"]]</translate>
* <translate>
[http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/index.html KParts API Reference]</translate>
* <translate>
[http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/classKParts_1_1Part.html KParts Class Reference]</translate>
* <translate>
[http://www-106.ibm.com/developerworks/library/l-kparts/ Coding with KParts] (from IBM)</translate>

<translate>
[[Category:KDE4]]</translate>

Development/Architecture/KDE4/KParts

2013-01-04T00:45:26Z

Neverendingo: add translate tags

<languages />

<translate>'''KParts''' is the name of the component framework for KDE. An individual component is called a '''KPart'''. As an example, Konsole is available as a KPart and is used in applications like Konqueror and Kate. Good examples about how KParts can be used are Konqueror, which (among other things) uses the KWord part to display documents, KMPlayer part to play multimedia, and Kontact, which embeds kdepim applications under one roof.</translate>

<translate>KParts also provide flexibility in your software selection. For example, the KHTML part which is by default used by Konqueror for HTML rendering can very easily be exchanged by a Webkit KPart.</translate>

===<translate>Further reading</translate>===
* <translate>[[Special:myLanguage/Development/Tutorials/Using_KParts|Techbase Tutorial: "Using KParts"]]</translate>
* <translate>[http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/index.html KParts API Reference]</translate>
* <translate>[http://api.kde.org/4.0-api/kdelibs-apidocs/kparts/html/classKParts_1_1Part.html KParts Class Reference]</translate>
* <translate>[http://www-106.ibm.com/developerworks/library/l-kparts/ Coding with KParts] (from IBM)</translate>

<translate>[[Category:KDE4]]</translate>

Development/Architecture/KDE4/de

2013-01-03T20:31:03Z

Neverendingo:

<languages />

== Entwicklungsframework ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# Benutzeroberfläche
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Online Hilfe verfügbar machen]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|XML Menüs und Werkzeugleisten definieren]]
# Dienste
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|andere Programme starten]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop Suchmaschine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Gemeinsame Daten benutzen]] (könnte hierher von den Projekten verschoben werden)

== Frameworks in anderen KDE Modulen ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/1/de

2013-01-03T20:31:03Z

Neverendingo:

Entwicklungsframework

Development/Architecture/KDE4/de

2013-01-03T20:30:53Z

Neverendingo: Created page with "Frameworks in anderen KDE Modulen"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# Benutzeroberfläche
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Online Hilfe verfügbar machen]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|XML Menüs und Werkzeugleisten definieren]]
# Dienste
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|andere Programme starten]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop Suchmaschine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Gemeinsame Daten benutzen]] (könnte hierher von den Projekten verschoben werden)

== Frameworks in anderen KDE Modulen ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/19/de

2013-01-03T20:30:53Z

Neverendingo: Created page with "Frameworks in anderen KDE Modulen"

Frameworks in anderen KDE Modulen

Development/Architecture/KDE4/de

2013-01-03T20:30:29Z

Neverendingo: Created page with "KNewStuff2 - Gemeinsame Daten benutzen (könnte hierher von den Projekten verschoben werden)"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# Benutzeroberfläche
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Online Hilfe verfügbar machen]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|XML Menüs und Werkzeugleisten definieren]]
# Dienste
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|andere Programme starten]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop Suchmaschine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Gemeinsame Daten benutzen]] (könnte hierher von den Projekten verschoben werden)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/18/de

2013-01-03T20:30:29Z

Neverendingo: Created page with "KNewStuff2 - Gemeinsame Daten benutzen (könnte hierher von den Projekten verschoben werden)"

[[Special:myLanguage/Projects/KNS2|KNewStuff2 - Gemeinsame Daten benutzen]] (könnte hierher von den Projekten verschoben werden)

Development/Architecture/KDE4/de

2013-01-03T20:29:52Z

Neverendingo: Created page with "Strigi - Desktop Suchmaschine"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# Benutzeroberfläche
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Online Hilfe verfügbar machen]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|XML Menüs und Werkzeugleisten definieren]]
# Dienste
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|andere Programme starten]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop Suchmaschine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/17/de

2013-01-03T20:29:52Z

Neverendingo: Created page with "Strigi - Desktop Suchmaschine"

[[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop Suchmaschine]]

Development/Architecture/KDE4/de

2013-01-03T20:29:35Z

Neverendingo: Created page with "andere Programme starten"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# Benutzeroberfläche
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Online Hilfe verfügbar machen]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|XML Menüs und Werkzeugleisten definieren]]
# Dienste
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|andere Programme starten]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/16/de

2013-01-03T20:29:35Z

Neverendingo: Created page with "andere Programme starten"

[[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|andere Programme starten]]

Development/Architecture/KDE4/de

2013-01-03T20:29:11Z

Neverendingo: Created page with "Dienste"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# Benutzeroberfläche
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Online Hilfe verfügbar machen]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|XML Menüs und Werkzeugleisten definieren]]
# Dienste
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/15/de

2013-01-03T20:29:10Z

Neverendingo: Created page with "Dienste"

Dienste

Development/Architecture/KDE4/de

2013-01-03T20:28:52Z

Neverendingo: Created page with "XML Menüs und Werkzeugleisten definieren"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# Benutzeroberfläche
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Online Hilfe verfügbar machen]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|XML Menüs und Werkzeugleisten definieren]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/14/de

2013-01-03T20:28:52Z

Neverendingo: Created page with "XML Menüs und Werkzeugleisten definieren"

[[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|XML Menüs und Werkzeugleisten definieren]]

Development/Architecture/KDE4/de

2013-01-03T20:28:15Z

Neverendingo: Created page with "Online Hilfe verfügbar machen"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# Benutzeroberfläche
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Online Hilfe verfügbar machen]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/13/de

2013-01-03T20:28:15Z

Neverendingo: Created page with "Online Hilfe verfügbar machen"

[[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Online Hilfe verfügbar machen]]

Development/Architecture/KDE4/de

2013-01-03T20:27:41Z

Neverendingo: Created page with "Benutzeroberfläche"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# Benutzeroberfläche
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/12/de

2013-01-03T20:27:41Z

Neverendingo: Created page with "Benutzeroberfläche"

Benutzeroberfläche

Development/Architecture/KDE4/de

2013-01-03T20:27:18Z

Neverendingo: Created page with "Akonadi - Zentralisierte PIM Speicherlösung"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# User Interface
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/11/de

2013-01-03T20:27:18Z

Neverendingo: Created page with "Akonadi - Zentralisierte PIM Speicherlösung"

[[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]

Development/Architecture/KDE4/de

2013-01-03T20:27:01Z

Neverendingo: Created page with "Telepathy - Framework für Echtzeitkommunikation"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/10/de

2013-01-03T20:27:01Z

Neverendingo: Created page with "Telepathy - Framework für Echtzeitkommunikation"

[[Special:myLanguage/Projects/Telepathy|Telepathy - Framework für Echtzeitkommunikation]]

Development/Architecture/KDE4/de

2013-01-03T20:26:52Z

Neverendingo: Created page with "Kommunikation"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Kommunikation
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/9/de

2013-01-03T20:26:52Z

Neverendingo: Created page with "Kommunikation"

Kommunikation

Translations:Development/Architecture/KDE4/8/de

2013-01-03T20:26:40Z

Neverendingo: Created page with "Phonon - Multimedia framework"

[[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]

Development/Architecture/KDE4/de

2013-01-03T20:25:54Z

Neverendingo: Created page with "Solid - Schnittstelle zur Hardware und Netzwerken"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/7/de

2013-01-03T20:25:54Z

Neverendingo: Created page with "Solid - Schnittstelle zur Hardware und Netzwerken"

[[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]

Translations:Development/Architecture/KDE4/6/de

2013-01-03T20:25:21Z

Neverendingo: Created page with "Hardware"

Hardware

Development/Architecture/KDE4/de

2013-01-03T20:25:03Z

Neverendingo: Created page with "KParts - Die KDE Komponentenarchitektur"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/5/de

2013-01-03T20:25:03Z

Neverendingo: Created page with "KParts - Die KDE Komponentenarchitektur"

[[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - Die KDE Komponentenarchitektur]]

Development/Architecture/KDE4/de

2013-01-03T20:24:38Z

Neverendingo: Created page with "Sonnet - Technik zum Rechtschreib- und Grammatikcheck"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - KDE's component architecture]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/4/de

2013-01-03T20:24:38Z

Neverendingo: Created page with "Sonnet - Technik zum Rechtschreib- und Grammatikcheck"

[[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]

Development/Architecture/KDE4/de

2013-01-03T20:24:11Z

Neverendingo: Created page with "Plasma - Der Desktop"

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Spell- and grammar-checking technology]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - KDE's component architecture]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/3/de

2013-01-03T20:24:11Z

Neverendingo: Created page with "Plasma - Der Desktop"

[[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - Der Desktop]]

Translations:Development/Architecture/KDE4/2/de

2013-01-03T20:23:56Z

Neverendingo: Created page with "Desktop"

Desktop

Development/Architecture/KDE4/de

2013-01-03T20:23:40Z

Neverendingo:

<languages />

== Entwicklungssystem ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - The desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Spell- and grammar-checking technology]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - KDE's component architecture]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/1/de

2013-01-03T20:23:40Z

Neverendingo:

Entwicklungssystem

Development/Architecture/KDE4/de

2013-01-03T20:23:08Z

Neverendingo: Created page with "Entwicklungsframework"

<languages />

== Entwicklungsframework ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - The desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Spell- and grammar-checking technology]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - KDE's component architecture]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/1/de

2013-01-03T20:23:08Z

Neverendingo: Created page with "Entwicklungsframework"

Entwicklungsframework

Development/Architecture/KDE4/de

2013-01-03T20:22:44Z

Neverendingo: Created page with "Entwicklung/Architektur/KDE4"

<languages />

== Development Framework ==

# Desktop
#* [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - The desktop]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Spell- and grammar-checking technology]]
#* [[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - KDE's component architecture]]
# Hardware
#* [[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Special:myLanguage/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Translations:Development/Architecture/KDE4/Page display title/de

2013-01-03T20:22:43Z

Neverendingo: Created page with "Entwicklung/Architektur/KDE4"

Entwicklung/Architektur/KDE4

Development/Architecture/KDE4/Plasma

2013-01-03T20:12:33Z

Neverendingo: Marked this version for translation

<languages />

<translate>
Plasma is the name of the new desktop planned to replace KDesktop in KDE4. You may think that 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.</translate>

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

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

* <translate>
'''Corona''': extends [http://doc.trolltech.com/qgraphicsscene.html QGraphicsScene] and provides functionality for adding applets and karamba themes.</translate>
* <translate>
'''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.</translate>
* <translate>
'''Applet''': extends Widget and implements sophisticated functionality as rss display, a clock or system monitoring.</translate>
* <translate>
'''DataEngine''': The common use of a DataEngine is to provide data to an applet for display. This allows a user interface elements to show all sorts of data.</translate>

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

<translate>
[[Category:Architecture]]</translate>
<translate>
[[Category:KDE4]]</translate>

Development/Architecture/KDE4/Plasma

2013-01-03T20:12:17Z

Neverendingo: add translate tags

<languages />

<translate>Plasma is the name of the new desktop planned to replace KDesktop in KDE4. You may think that 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.</translate>

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

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

* <translate>'''Corona''': extends [http://doc.trolltech.com/qgraphicsscene.html QGraphicsScene] and provides functionality for adding applets and karamba themes.</translate>
* <translate>'''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.</translate>
* <translate>'''Applet''': extends Widget and implements sophisticated functionality as rss display, a clock or system monitoring.</translate>
* <translate>'''DataEngine''': The common use of a DataEngine is to provide data to an applet for display. This allows a user interface elements to show all sorts of data.</translate>

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

<translate>[[Category:Architecture]]</translate>
<translate>[[Category:KDE4]]</translate>

Development/Architecture/KDE4

2013-01-03T20:07:45Z

Neverendingo: Marked this version for translation

<languages />

== <translate>
Development Framework</translate> ==

# <translate>
Desktop</translate>
#*<translate> 
[[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - The desktop]]</translate>
#* <translate>
[[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Spell- and grammar-checking technology]]</translate>
#* <translate>
[[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - KDE's component architecture]]</translate>
# <translate>
Hardware</translate>
#* <translate>
[[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]</translate>
#* <translate>
[[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]</translate>
# <translate>
Communication</translate>
#* <translate>
[[Special:myLanguage/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]</translate>
#* <translate>
[[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]</translate>
# <translate>
User Interface</translate>
#* <translate>
[[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]</translate>
#* <translate>
[[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]</translate>
# <translate>
Services</translate>
#* <translate>
[[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]</translate>
#* <translate>
[[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]</translate>
#* <translate>
[[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)</translate>

== <translate>
Frameworks in other KDE modules</translate> ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Development/Architecture/KDE4

2013-01-03T20:07:20Z

Neverendingo: add translate tags

<languages />

== <translate>Development Framework</translate> ==

# <translate>Desktop</translate>
#*<translate> [[Special:myLanguage/Development/Architecture/KDE4/Plasma|Plasma - The desktop]]</translate>
#* <translate>[[Special:myLanguage/Development/Architecture/KDE4/Sonnet|Sonnet - Spell- and grammar-checking technology]]</translate>
#* <translate>[[Special:myLanguage/Development/Architecture/KDE4/KParts|KParts - KDE's component architecture]]</translate>
# <translate>Hardware</translate>
#* <translate>[[Special:myLanguage/Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]</translate>
#* <translate>[[Special:myLanguage/Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]</translate>
# <translate>Communication</translate>
#* <translate>[[Special:myLanguage/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]</translate>
#* <translate>[[Special:myLanguage/Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]</translate>
# <translate>User Interface</translate>
#* <translate>[[Special:myLanguage/Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]</translate>
#* <translate>[[Special:myLanguage/Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]</translate>
# <translate>Services</translate>
#* <translate>[[Special:myLanguage/Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]</translate>
#* <translate>[[Special:myLanguage/Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]</translate>
#* <translate>[[Special:myLanguage/Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)</translate>

== <translate>Frameworks in other KDE modules</translate> ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Contribute

2012-12-28T10:24:29Z

Neverendingo: Reverted edits by JackieEarleHaley (talk) to last revision by Fengchao

<languages />
<translate>

This page intends to give an overview of the different aspects of KDE development in particular for programming related issues. ''The KDE project welcomes anyone willing to help''.


{{Note|There are a lot of ways to get involved in KDE development, which can be summed up in several categories:
:''Documentation, Translation, Development, Usability, Accessibility, Artwork, Promotion
''Not a coder? See KDE's pages on [http://kde.org/community/getinvolved/ how to get involved] to see other ways you can help. Also see: [[Contribute/Bugsquad|Bugsquad]]!''
}}

== News and Mail Sources == 


The general direction of the KDE project is determined by those who do the work - there is no single high level plan for what KDE will look like in the future.


If you want to find out what is currently happening, then there are a number of sources you might like to consider:
; [http://www.kde.org/mailinglists/ Mailing Lists]
: Probably the best way to find out what's going on in KDE development. Archives are available [http://lists.kde.org here]


; [http://commitfilter.kde.org/ CommitFilter]
: Receive notification of commits to the KDE source code repositories in areas that interest you.


; [http://commit-digest.org/ KDE Commit-Digest]
: Weekly summary of commits to projects in the KDE source code repositories.


; [http://dot.kde.org/ The Dot]
: The KDE news site.

== Reporting Bugs == 


The easiest way to contribute to KDE is to [http://userbase.kde.org/Asking_Questions#Reporting_KDE_Bugs report any bugs] you find in KDE using the [https://bugs.kde.org/ KDE Bug Tracking System] (also known as '''Bugzilla''').


If the application you are using crashes then the '''Dr Konqi''' utility will appear and guide you through the process of reporting the crash. Learn more by reading [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports|how to create useful crash reports]].

== Getting Started with Coding == 


Getting started at coding for KDE is a matter of finding something to fix, and fixing it. You may want to consult the module overview to help find what you are looking for; once you have fixed something, you will want to send in a patch. If you do that a few times, you may want to apply for a KDE Contributor account so you can improve things directly.


* [[Contribute/List of KDE Modules|Module overview]]
* [[Contribute/Send Patches|Sending patches]]
* [[Contribute/Get a Contributor Account|Applying for a KDE Contributor Account]]
* [[Contribute/First Steps with your KDE SVN Account|First steps with your new Contributor account]]

=== C++ === 


KDE is mostly written in C++. If you are not familiar with C++, you should do at least some work on it. There are a number of good books on C++ - an excellent source is [http://mindview.net/Books/TICPP/ThinkingInCPP2e.html Bruce Eckel's "Thinking in C++"], which is available both as a free download and as a printed document. It isn't essential to understand everything before you start in KDE, but you do need to understand basic syntax and operations.

=== Qt === 


To become proficient with KDE coding, you should understand the Qt toolkit. If you are not familiar with Qt, you should work through the tutorials included with [http://qt-project.org/doc/latest Qt Reference Documentation].


If you need a gentler introduction to Qt, or would just like an alternative view, then you may wish to look at the [http://www.apress.com/9781590598313 Foundations of Qt Development].


If you prefer to learn Qt by reading a traditional book, take a look at the [http://qt-project.org/books Books about Qt page]. More suggestions on becoming familiar with Qt4 are available [http://qt-project.org/doc/qt-4.8/how-to-learn-qt.html How to Learn Qt page].

=== KDE === 


A range of information on KDE techniques is available in the [[Development/Tutorials|tutorial section]]. Note that some of these tutorials still target KDE3, though they should be at least partly applicable.


You will also find useful information on KDE coding in the [[Development/FAQs|FAQs]] section. This information may also be somewhat dated for KDE4, however much of it is broadly applicable, even outside KDE.


You can also read [[Development/Further Information#Books|KDE coding books]].


Last, but by no means least, KDE comes with extensive class (Application Programmer Interface) documentation. This is available in the
[[Development/Tutorials/API Documentation|KDE API Reference Manuals]] section, which also contains a number of useful links on how to write or update the class documentation. You can also generate these on your own machine, or refer to a more up-to-date online version at [http://api.kde.org/ API Reference].


A more detailed description of the steps above is available in our [http://quality.kde.org/develop/howto/howtohack.php Programming Guide].

==== Context Help: Whatsthis ==== 


Context help is inseparable from the dialogs and widgets, as they are the target of the context help. In fact, in order to write context help, you have to touch programming or programming tools. Indeed, the context help is a property of widgets. In object oriented programming, a property can have different values, and behave differently depending on the value. In Qt/KDE programming, the name of the property is "whatsthis", and its value is the text the context help is going to display.


Fortunately, this task is usually not very difficult, as there are good tools to deal with user interface design, and better, you will use the knowledge acquired here later when dealing with user interface in general. Using the Qt framework (Qt is the base of KDE technology), it is possible to separate code and user interface. You have two basic cases here: the user interface is written with the general code of application (usually .cpp files) or in Qt Designer files (.ui files: it is a XML document). The second case is the best to start with, as it is simpler to work with. If you don't have Qt Designer installed, you can do so by installing the devel package of Qt from your distribution or the Qt Designer package (if your distribution has more fine grained packages).


Here you can find a detailed guide for writing whatsthis using Qt Designer and working directly with the source code: [http://bddf.ca/~aseigo/whatsthis_tutorial/ WhatsThis Tutorial], by Aaron J. Seigo.

== Getting Involved in Bug Hunting and Application Quality == 


There is a large number of applications within KDE, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.


If you are interested in helping out with KDE, but don't know where to start, becoming a member of the KDE Quality Team might appeal to you - see the [http://techbase.kde.org/Contribute/Quality_Team Quality Team website] for more information. Note that you do not need any programming skills to become involved. In particular developers regularly publish so-called [http://community.kde.org/KDE/Junior_Jobs Junior Jobs] to encourage new contributions.


Of course, you can become involved in bug hunting without being part of the KDE Quality Team - just create yourself an account on the KDE [http://bugs.kde.org bug tracking system], and start searching / sorting through the bugs. Again, you don't have to have programming skills - it helps the programmers enormously just to have a procedure that allows a bug to be consistently reproduced.


The [[Contribute/Bugsquad|Bugsquad]] tries to keep track of bugs in KDE software and make sure that valid bugs are noticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the KDE community if you cannot program.

== User Interface == 


User interface is a very wide subject, and very subjective too, as something obvious to someone is absurd to others and vice versa. Therefore, don't assume, argue clearly, stating your logical steps. Your main tool discussing it are objective reasoning and good sense.


It is easy to perform a quick user interface analysis, but it is hard to convince people to change the interface. A good, convincing analysis can gain much if it incorporates information from the KDE guidelines, competing program and operational system analysis, general design principles found in many books, user testing or individual (anecdotal) feedback. It is a volunteer project, and even if everybody agree with you, someone has to implement it.


The [http://mail.kde.org/mailman/listinfo/kde-usability KDE Usability Mailing List] is very active and a good place for discussing your ideas, and their homepage is at http://techbase.kde.org/Projects/Usability. If you are already an usability expert, please check [http://www.openusability.org/ OpenUsability.org], a project that brings open source developers and usability experts together, and is collaborating closely with KDE.


Some documents guiding documents include the [http://developer.kde.org/documentation/standards/kde/style/basics/index.html KDE User Interface Guidelines (design standards)] and [http://developer.kde.org/documentation/design/ui/index.html KDE User Interface Guidelines (design principles)].


Some projects for analysis of user interfaces may include: checking that shortcut keys are coherent across KDE applications, making sure that dialogs are directly relevant to the interaction that the user would expect, and finding users of KDE software to see how they perform common workflows.

==Getting Answers to Your Questions== 


If your question concerns KDE development, your options are pretty much the same general user ones, with some modifications:
<blockquote>
:* '''Read the Developer FAQ'''. Many common developer questions have been answered in the [[Development/FAQs|KDE Developer FAQ]]
:* '''Search/browse KDE websites'''. A lot of questions can also be answered from the KDE websites, and the documentation included on it. You can search all the KDE websites on the homepage. In addition, you can browse the [http://techbase.kde.org KDE TechBase website]. And if possible, help edit it for clarity, and use the talk page if something is unclear.
:* '''Search mailing lists'''. A lot of questions have already been answered on the KDE mailing lists, particular the lists kde-devel, kde2-porting, kde-core-devel, kde-games-devel, kfm-devel and koffice-devel. You can search these lists at [http://lists.kde.org/ lists.kde.org]. You should always search for your answer before asking questions on the mailing lists. When you ask a question on a mailing list you are emailing thousands of people -- please do this only if the answer is not available through a simple search.
:* '''Search engines'''. Do not forget about your favorite search engine. One of the best search engines is Google. With Google you can also [http://groups.google.com/ search] the great bulk of Usenet news sites, which is also particularly helpful, especially for general programming and gcc-related questions.


:* '''Read the source code'''. http://websvn.kde.org and https://projects.kde.org/ are available to help browse code. Read some commit logs and diffs for the code you might want to work with, It adds perspective.
:* '''Ask on KDE mailing lists'''. If you still do not have an answer, try asking your question on one of the KDE mailing lists listed above.
:* For questions relating to core development or third-party KDE development, unless you are particularly interested in [http://konqueror.kde.org/ Konqueror], [http://www.koffice.org/ KOffice], games or Java development, your main choice is [mailto:kde-devel@kde.org kde-devel] [mailto:kde-devel-request@kde.org?subject=subscribe (subscribe)].
:* For questions relating to Konqueror development, your main choice is [mailto:kfm-devel@kde.org kfm-devel] [mailto:kfm-devel@kde.org?subject=subscribe (subscribe)]
:* For questions relating to KOffice development, your main choice is [mailto:koffice-devel@kde.org koffice-devel] [mailto:koffice-devel-request@kde.org?subject=subscribe (subscribe)]
:* For questions relating to games development, your main choice is [mailto:kde-games-devel@kde.org kde-games-devel] [mailto:kde-games-devel-request@kde.org?subject=subscribe (subscribe)]
:* For questions relating to [http://qt.nokia.com/ Qt development], please use the fine [http://lists.trolltech.com/qt-interest/ Qt mailing list].
</blockquote>


A full list of KDE mailing lists is available [http://www.kde.org/mailinglists/ here] and [http://mail.kde.org/mailman/listinfo here].


[[Category:FAQs]]

</translate>

Development/Guidelines/HCI/Checklists/Configuration

2012-12-17T19:28:30Z

Neverendingo:

{{Review|1=
* The link in the first and fourth paragraph appears to be broken
}}

1. Dialog navigation

* A [http://wiki.openusability.org/guidelines/index.php/Image:Grouping.png paged configuration dialog] should be used when there is more than one category of options.
* Tabs should be used as second-level navigation.
* Tree views shouldn't be used in the paged dialog's sidebar.

2. Grouping of options

* The number of categories (pages) should be between 3 and 6.
* The number of tabs on a page should be between 2 and 4.
* The options should be in the visible space so the user doesn't need to scroll. (otherwise it's an indicator that options might be moved to advanced sections or dialogs)
* There shouldn't be "orphaned options" - options which are not related to any other ones.

3. Dialog layout

* The dialog should be resizable. (the latter is important for accessibility)
* The overall size of the dialog shouldn't be bigger than 800x600.
* The dialog should have scrollbars which appear when not all options are visible.

4. Wording

* Keywords used in page title and the label in the left navigation bar should correspond. (In [http://wiki.openusability.org/guidelines/index.php/Image:Grouping.png this example], page title is "Here you can personalize kopete"” while the label is "Behavior". This should be reported and acceptable change would be Behavior -> "Here you can change the behavior of Kopete" OR Personalize -> "Here you can personalize Kopete")

* Obviously technical or otherwise hard to understand wording should be avoided.

Development/Guidelines/HCI/Checklists/Configuration

2012-12-17T19:27:51Z

Neverendingo:

{{Review|1=
* The link in the first and fourth paragraph appears to be broken
}}

1. Dialog navigation

* A [http://wiki.openusability.org/guidelines/index.php/Image:Grouping.png paged configuration dialog] should be used when there is more than one category of options.
* Tabs should be used as second-level navigation.
* Tree views shouldn't be used in the paged dialog's sidebar.

2. Grouping of options

* The number of categories (pages) should be between 3 and 6.
* The number of tabs on a page should be between 2 and 4.
* The options should be in the visible space so the user doesn't need to scroll. (otherwise it's an indicator that options might be moved to advanced sections or dialogs)
* There shouldn't be "orphaned options" - options which are not related to any other ones.

3. Dialog layout

* The dialog should be resizable. (the latter is important for accessibility)
* The overall size of the dialog shouldn't be bigger than 800x600.
* The dialog should have scrollbars which appear when not all options are visible.

4. Wording

* Keywords used in page title and the label in the left navigation bar should correspond.
(In [http://wiki.openusability.org/guidelines/index.php/Image:Grouping.png this example], page title is "Here you can personalize kopete"” while the label is "Behavior". This should be reported and acceptable change would be Behavior -> "Here you can change the behavior of Kopete" OR Personalize -> "Here you can personalize Kopete")

* Obviously technical or otherwise hard to understand wording should be avoided.

Template:Review

2012-12-17T18:28:25Z

Neverendingo:

{{Warning|1=This page needs a review and probably holds information that needs to be fixed.
Parts to be reviewed:
{{{1}}}}}

<noinclude>
This template can be used to mark a page with possibly outdated or wrong/missleading content. It should state which parts of the page need some review.

Usage:
<nowiki>{{Review|
* improve headings
* review part about XXX, seems outdated
}}
</nowiki>
becomes this:

{{Review|
* improve headings
* review part about XXX, seems outdated
}}

Template:Review

2012-12-17T16:40:30Z

Neverendingo: Created page with "{{Warning|1=This page needs a review and probably holds information that needs to be fixed. Parts to be reviewed: 1={{{1}}}}}"

{{Warning|1=This page needs a review and probably holds information that needs to be fixed.
Parts to be reviewed:
1={{{1}}}}}

Template:I18n/Language Navigation Bar

2012-07-21T15:36:24Z

Neverendingo: Reverted edits by Neverendingo (talk) to last revision by AnneW

<noinclude>
{{Template:I18n/Language Navigation Bar|Template:I18n/Language_Navigation_Bar}}
== 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 page. If you want to add a new translation language, add
it here and it will appear on all pages. Untranslated versions will appear
red as usual.
</noinclude>
<includeonly>
=== {{{1}}} ===

<div style="margin:auto;font-size:83.3%;text-align:left">

Languages:
[[{{{1}}}_(ar)|عربي]] |
[[{{{1}}}_(ast)|Asturianu]] |
[[{{{1}}}_(ca)|Català]] |
[[{{{1}}}_(cs)|Česky]] |
[[{{{1}}}_(csb)|Kaszëbsczi]] |
[[{{{1}}}_(da)|Dansk]] |
[[{{{1}}}_(de)|Deutsch]] |
[[{{{1}}}|English]] |
[[{{{1}}}_(eo)|Esperanto]] |
[[{{{1}}}_(es)|Español]] |
[[{{{1}}}_(et)|Eesti]] |
[[{{{1}}}_(fa)|فارسی]] |
[[{{{1}}}_(fi)|Suomi]] |
[[{{{1}}}_(fr)|Français]] |
[[{{{1}}}_(gl)|Galego]] |
[[{{{1}}}_(it)|Italiano]] |
[[{{{1}}}_(ja)|日本語]] |
[[{{{1}}}_(ko)|한국어]] |
[[{{{1}}}_(no)|Norwegian]] |
[[{{{1}}}_(pl)|Polski]] |
[[{{{1}}}_(pt_BR)|Português Brasileiro]] |
[[{{{1}}}_(ro)|Română]] |
[[Добро пожаловать в KDE TechBase (ru)|Русский]] |
[[{{{1}}}_(se)|Svenska]] |
[[{{{1}}}_(sk)|Slovenčina]] |
[[{{{1}}}_(sl)|Slovenščina]] |
[[{{{1}}}_(sr)|српски]] |
[[{{{1}}}_(tr)|Türkçe]] |
[[{{{1}}}_(vi)|Tiếng Việt]] |
[[{{{1}}}_(uk)|Українська]] |
[[{{{1}}}_(zh_CN)|简体中文]] |
[[{{{1}}}_(zh_TW)|繁體中文]]

</div>
</includeonly>

Template:I18n/Language Navigation Bar

2012-07-21T15:28:23Z

Neverendingo: /* {{{1}}} */

Thread:Template talk:I18n/Language Navigation Bar/Outdated translation system

2012-07-02T12:18:39Z

Neverendingo: New thread: Outdated translation system

Please don't use this anymore, there is a new translation system in place that makes using the lang navigation bar obsolete, see [[Translate_a_Page]]

Template talk:I18n/Language Navigation Bar

2012-07-02T12:18:39Z

Neverendingo: Talk page autocreated when first thread was posted

Thread:User talk:MarcinB/Translations in wrong place

2012-07-01T00:24:03Z

Neverendingo: New thread: Translations in wrong place

Hello,

you started to translate, but in the wrong place. if you want to translate to your language you 1. need a translator account and 2. then click on the language link on top of the page. There you can request all strings and translate from there.
What you did was translating the original english version of the page. Please revert the changes.

User talk:MarcinB

2012-07-01T00:24:03Z

Neverendingo: Talk page autocreated when first thread was posted

Translator Account

2012-04-29T10:22:00Z

Neverendingo:

Translator Account

2012-04-29T10:20:43Z

Neverendingo:

User:Neverendingo

2012-04-29T10:16:28Z

Neverendingo:

This is a test

<code php> echo "Hello World"; </code>

Translator Account

2012-01-29T16:32:59Z

Neverendingo:

{{Tip|1=''Example (please add your details to the bottom of the list)''

User Name: Hans

Language(s): Swedish

(Optional) Do you expect to work off-line?: No}}

----
----

User Name: Caig

Language(s): Italian

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group. [[User:Annewilson|Annewilson]] 18:42, 7 July 2011 (BST)
----

User Name: Juanman

Language(s): Spanish

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group. [[User:Annewilson|Annewilson]] 11:54, 9 July 2011 (BST)
----

User Name: Fengchao

Language(s): Simplified Chinese

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group. [[User:Annewilson|Annewilson]] 11:54, 9 July 2011 (BST)
----

User Name: sheedy

Language(s): French

(Optional) Do you expect to work off-line?: No

Welcome to the Translator Group. [[User:Annewilson|Annewilson]] 17:13, 22 July 2011 (BST)
----

User Name: phanect

Language(s): Japanese

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group. [[User:Annewilson|Annewilson]] 19:31, 29 July 2011 (BST)
----

User Name: PingusPepan

Language(s): Czech

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator Group. [[User:Annewilson|Annewilson]] 03 August 2011 (BST)
----

User Name: Fulapol

Language(s): Spanish

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator Group [[User:Annewilson|Annewilson]] 12:09, 5 August 2011 (BST)
----

User Name: Urkud

Language(s): Russian

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:Annewilson|Annewilson]] 12:09, 5 August 2011 (BST)
----
User Name: Mielotxin

Language(s): Basque (Euskera)

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:Annewilson|Annewilson]] 15:49, 10 August 2011 (BST)
----

User Name: RazrFalcon

Language(s): Russian

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:Annewilson|Annewilson]] 12:40, 13 August 2011 (BST)
----

User Name: Centerlink

Language(s): Finnish

(Optional) Do you expect to work off-line?: Yes/No

Welcome to the Translator Group [[User:Annewilson|Annewilson]] 19:58, 20 August 2011 (BST)
----

User Name: Willem1

Language(s): Dutch

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:Annewilson|Annewilson]] 19:45, 30 August 2011 (BST)
----

User Name: JulienM

Language(s): French

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:Annewilson|Annewilson]] 19:45, 30 August 2011 (BST)
----

User Name: fanys12

Language(s): Czech

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:Annewilson|Annewilson]] 19:54, 30 August 2011 (BST)
----

User Name: dicorfu

Language(s): Greek

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group. [[User:AnneW|Anne]] 10:05, 20 September 2011 (BST)
----

User Name: NomadSoul

Languages(s): Turkish

(Optional) Do you expect to work off-line?: No

15:42, 4 October 2011 (BST)

Welcome to the Translator group. --[[User:Neverendingo|Neverendingo]] 23:11, 8 October 2011 (BST)
----

User Name: [[User:Doğan|Doğan]]

Language(s): Turkish

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group. --[[User:Neverendingo|Neverendingo]] 23:11, 8 October 2011 (BST)
----

User Name: Gianvacca

Language(s): Italian

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] 17:50, 19 November 2011 (UTC)

----

User Name: Peremen

Language(s): Korean

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] 17:50, 19 November 2011 (UTC)

----

User Name: Hiraoka Minori

Language(s): Korean

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] 17:50, 19 November 2011 (UTC)

----

User Name: Wizzard

Language(s): Slovak

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] 19:32, 24 November 2011 (UTC)
----

User Name: svvord

Language(s): Russian

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group [[User:AnneW|Annew]] 16:46, 26 November 2011 (UTC)
----

User Name: alejandronova

Language(s): Spanish

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] 16:47, 30 November 2011 (UTC)
----
User Name: kyberdev

Language(s): Slovak

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] 12:13, 15 December 2011 (UTC)
----
User Name: rgallego

Language(s): Spanish

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group [[User:AnneW|Annew]] 11:34, 23 December 2011 (UTC)
----
User Name: Droetker

Language(s): German

(Optional) Do you expect to work off-line?: No

Welcome to the Translator group --[[User:Neverendingo|Neverendingo]] 16:32, 29 January 2012 (UTC)
----
User Name: Prototik

Language(s): Russian

(Optional) Do you expect to work off-line?: Yes

Welcome to the Translator group --[[User:Neverendingo|Neverendingo]] 16:32, 29 January 2012 (UTC)
----