KDE TechBase - User contributions [en]

Schedules/Extragear

2013-01-24T23:23:51Z

Sandsmark: added mangonel

This page is intended to be a central location for Extragear projects to keep users and contributors (translators, packagers, etc.) informed about upcoming releases in a very accessible way.

 

{| border="1"
|-
! Project
! Next release (roughly)
! Next Release Code branch
! Next Release Translation branch
! Comments
|-
| K3b
| 1 March 2010
| [http://websvn.kde.org/trunk/extragear/multimedia/k3b/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-multimedia/ trunk kde4]
| String freeze starting from January 31 2010 (in effect)
|-
| KAudiocreator
|
|
|
|
|-
| Kaffeine
|
|
|
|
|-
| [http://extragear.kde.org/apps/kcoloredit/ KColorEdit]
| KDE release
| [http://websvn.kde.org/trunk/extragear/graphics/kcoloredit/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
|
|-
| [http://www.kde-apps.org/content/show.php/KDE+Partition+Manager?content=89595 KDE Partition Manager]
| Q2/2010
| [http://websvn.kde.org/trunk/extragear/sysadmin/partitionmanager/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-sysadmin/ trunk kde4]
| 
|-
| [http://ww.kdevelop.org KDevelop]
| 1 May 2010
| [http://websvn.kde.org/trunk/extragear/sdk/kdevelop/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-sdk/ trunk kde4]
| string freeze starting 31 March 2010
|-
| KDiff3
| January 31, 2009
| [http://websvn.kde.org/trunk/extragear/utils/kdiff3/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
|
|-
| KFax
| KDE release
|
|
|
|-
| KFTPGrabber
|
|
|
|
|-
| KGrab
| KDE release
|
|
|
|-
| [http://extragear.kde.org/apps/kgraphviewer/ KGraphViewer]
| KDE release
| [http://websvn.kde.org/trunk/extragear/graphics/kgraphviewer/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
|
|-
| KIconedit
| KDE release
|
|
|
|-
| [http://www.kmldonkey.org KMLDonkey]
| KDE release
| [http://websvn.kde.org/trunk/extragear/network/kmldonkey/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
|
|-
| KNemo
| January 17, 2010
| [http://websvn.kde.org/trunk/extragear/network/knemo/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
| String freeze in effect
|-
| KPager
|
|
|
|
|-
| KPhotoalbum
| May 9 2009
| trunk
| trunk
| Message freeze, April 3 2009
|-
| KPlayer
|
|
|
|
|-
| KPovmodeler
| KDE release
|
|
|
|-
| KRecipes
| 2.0, date unknown
| [https://projects.kde.org/projects/extragear/utils/krecipes/repository/?rev=2.0 git 2.0]
| [http://websvn.kde.org/branches/stable/l10n-kde4/templates/messages/extragear-utils/ stable]
| GUI strings frozen, docs ''not'' frozen
|-
| KSig
|
|
|
|
|-
| [http://ktorrent.org/ KTorrent]
| 8 november 2009
| [http://websvn.kde.org/branches/stable/extragear-kde4/network/ktorrent stable kde4]
| [http://websvn.kde.org/branches/stable/l10n-kde4/templates/messages/extragear-network/ stable kde4]
| String freeze in effect
|-
| Kuickshow
|
|
|
|
|-
| Muon Suite
| Final Release: August 2012, pre-releases monthly
|
|
|
|-
| KWlan
|
|
|
|
|-
| RSIBreak
|
|
|
|
|-
| Skanlite
| KDE release
| trunk
|
|
|-
| [http://skrooge.org Skrooge]
| 2010-02-06 (version 0.6.0)
| [http://websvn.kde.org/trunk/extragear/office/skrooge trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze in effect
|-
| Kile
| June 8th, 2011 (Version 2.1)
|
|
| String freeze started 23 May 2011
|-
| [http://www.krusader.org/ Krusader]
| 2.4.0-beta1 released on June 26, 2011.
| [http://websvn.kde.org/trunk/extragear/utils/krusader/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
| String freeze since June 26, 2011 until 2.4.0 release.
|-
| BlueDevil
| 1.0.5 (stable) and 1.1.1 (trunk) released planned on July 15, 2011.
|
| stable, trunk
| String freeze since June 29, 2011 until 1.0.5 and 1.1.1 releases.
|-
| [http://amarok.kde.org/ Amarok]
| Early 2013
| git master
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-multimedia/ trunk kde4]
|
|-
| [http://digikam.org digiKam]
| July 27th 2011 [http://www.digikam.org/drupal/about/releaseplan]
| [https://projects.kde.org/projects/extragear/graphics git master]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-graphics/ trunk kde4]
| String freeze starting June 30th 2011.
|-
| [http://techbase.kde.org/Projects/KMyMoney KMyMoney]
| 4.6.1 from Stable around November 5th, 2011
| [http://websvn.kde.org/trunk/extragear/office/kmymoney/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze started October 22nd, 2011
|-
| massif-visualizer
| 0.3 is planned to be released on September 4, 2011
|
|
| String freeze started on August 8, 2011
|-
| [http://tellico-project.org Tellico]
| 2.3.4
| [http://websvn.kde.org/trunk/extragear/office/tellico/ trunk]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-office/ trunk kde4]
| String freeze: September 5th, 2011 -- September 18th, 2011.
|-
| [http://www.rekonq.sourceforge.net rekonq]
| ~ October 11, 2011 (Version 0.8)
| [http://gitorious.org/rekonq/mainline/trees/master git master]
| [http://gitorious.org/rekonq/mainline/trees/master git master]
| String freeze for 3 weeks starting September 21, 2011 (0.8 release)
|-
| KDE Telepathy
| November 18th, 2011 (version 0.2)
|
|
| String freeze starting October 26th, 2011.
|-
| Calligra
| Calligra 2.6 planned for December 2012
|
|
| String freeze starting October 12th, 2011.
|-
| [http://konversation.kde.org Konversation]
| In the first week of December, 2011
| [http://gitorious.org/konversation/konversation/trees/master git master]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ trunk kde4]
| String freeze started on November 17th, 2011.
|-
| Wicd Client KDE
| 17th of December, 2011 (version 0.3)
|
|
| String freeze started on December 6th, 2011.
|-
| [http://www.kde-apps.org/content/show.php?content=29153 Yakuake]
| Week 42
| [http://quickgit.kde.org/index.php?p=yakuake.git&a=tree master]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-utils/ trunk kde4]
| String freeze started October 8th, 2012
|-
| [http://kde-apps.org/content/show.php/?content=136681 Mangonel]
| February 3. 2012
| [http://quickgit.kde.org/?p=mangonel.git&a=tree master]
| [http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-base/ trunk kde4]
| String freeze started January 24. 2012
|}

Policies/Library Code Policy

2012-12-17T13:09:21Z

Sandsmark: gotcha for qshareddata

This document describes some of the recommended conventions that should be applied in the KDE libraries (not applications). Respecting these guidelines helps create a consistant API and also may help ease maintainence of the libraries later. While these conventions are not mandatory, they are important guidelines, and should be respected unless you have a good reason to disregard them.

As an introduction, you should read the document [http://wiki.qt-project.org/index.php?title=API_Design_Principles Qt-Style C++ API Design Principles].

For kdelibs, it is recommended to follow the [[Policies/Kdelibs_Coding_Style | Kdelibs Coding Style]].

== Naming Conventions ==
In KDE, we basically follow the same naming conventions as Qt.

Class names starts with a capital K. The rest is in camel case. Function names starts with a lower case, but the first letter of each successive word is capitalized.

Unless dealing with central libraries (kdecore, kdeui), classes should be in the library namespace. In that case, it is the namespace which starts with K and the classes inside may not start with it. New libraries should choose their namespace.

The prefix 'set' is used for setters, but the prefix ''''get'''' is not used for accessors. Accessors are simply named with the name of the property they access. The exception is for accessors of a boolean which may start with the prefix ''''is''''.

Acronyms are lowercased too. Example:
<tt>KUrl</tt> instead of <tt>KURL</tt> and <tt>isNssEnabled()</tt> instead of <tt>isNSSEnabled()</tt>

Accessors should usually be <tt>const</tt>.

This example shows some possible functions names
<source lang="cpp-qt">
public:
void setColor(const QColor& c);
QColor color() const;
void setDirty(bool b);
bool isDirty() const;

private Q_SLOTS:
void slotParentChanged();
</source>
Make one public class for every .h file. Add the <tt>_EXPORT</tt> macro related to the library they are in.
Private classes should be declared in the .cpp file, or in a _p.h file.

== D-Pointers ==
In order to more easily maintain binary compatibility, there shouldn't be private members in a public class. For more information about binary compatibility, read [[Policies/Binary_Compatibility_Issues_With_C++|Binary Compatibility Issues With C++]].

By convention, the private class will be named the same as the public class, with <tt>Private</tt> appended to the name.
<source lang="cpp-qt">
class KFooPrivate;
class KFoo
{
public:
/* public members */
private:
const QScopedPointer<KFooPrivate> d;
};
</source>
In the .cpp file:
<source lang="cpp-qt">
class KFooPrivate
{
public:
int someInteger;
};

KFoo::KFoo() : d(new KFooPrivate)
{
/* ... */
}

KFoo::~KFoo()
{
// You must define a non-inline destructor in the .cpp file, even if it is empty
// else, a default one will be built in placed where KFooPrivate is only forward
// declare, leading to error in the destructor of QScopedPointer
}
</source>
Notice that the member d is <tt>const</tt> to avoid modifying it by mistake.

If you are implementing an implicitly shared class, you should consider using {{qt|QSharedData}} and {{qt|QSharedDataPointer}} for d. if you do, remember you need to implement explicit constructors, destructors and assignment operators (operator=).

Sometimes, complex code may be moved to a member method of the Private class itself. Doing this may give the compiler an extra register to optimize the code, since you won't be using "d" all the time. Also, remember to '''inline''' such methods if they are called only from one place.

=== Shared D-Pointers ===

If your class hierarchy is large and/or deep, you may want to try the concept of shared d-pointers. You'll be trading the added complexity for a smaller memory footprint in the main object (there will be only one "d" variable in it). Other advantages include:

:* direct access to the private data of the whole hierarchy (in other words, the Private classes are in fact "protected", not "private")
:* access to the parent's d-pointer methods

The latter advantage is especially useful if your class has moved the code from the main class to the Private class. If that's the case, you should be calling the Private methods instead: since they are not exported, they will create simpler relocations in the final library (or none at all). By simply calling the Private method instead of the public one, you contribute to a faster load-time of your library.

To implement a "shared d-pointer", you need to:
:# define a '''protected''' variable (d_ptr) in the least derived class of your hierarchy
:# in each class of the hierarchy, define a '''private''' function called d_func() that reinterpret_casts that d_ptr to the current class's Private class
:# use Q_D(Foo) at the beginning of the functions to have access to a variable "d"
:# the private classes derive from one another just like the public hierarchy; they also have virtual destructors
:# add one extra, protected constructor that takes the private class as a parameter
:# in each constructor for all derived classes, call the parent's constructor that takes the d pointer as a parameter

There's an example of such a construct in a [[/Shared_D-Pointer_Example|separate page]].

=== Q_DECLARE_PRIVATE ===

This is a handy macro that hides the ugly stuff for you. It creates the <tt>d_func()</tt> function for you, using the variable called <tt>d_ptr</tt>. If yours has that name, you can use this macro. If it has another name, maybe you should create a macro to make your code look nicer.

=== Q-Pointers ===

Q-pointers are like d-pointers, but work in the reverse direction: they are in the Private class and they point to the public class. Needless to say, this is only possible for classes that don't share their d-pointers. Examples of classes that might benefit from q-pointers are all those derived from QObject, while classes with implicit sharing are those that potentially can't use it.

Q-pointers are especially useful if your class has moved most of the code to the Private class as recommended. In that case, you may need to emit signals from the Private class. You would do it as:

<source lang="cpp-qt">
emit q->signalName();
</source>
(You need to declare the Private class a friend of your public one; Q_DECLARE_PRIVATE does that for you)

Q-pointers may also use the a shared q-pointer technique just like [[#Shared D-Pointers|d-pointers]] can. What's more, Qt also provides a macro called <tt>Q_DECLARE_PUBLIC</tt> and one <tt>Q_Q</tt> to hide the ugly parts of the implementation.

== Inline Code ==
For binary compatibility reasons, try to avoid inline code in headers. Specifically no inline constructor or destructor.

If ever you add inline code please note the following:
* Installed headers should compile with the following preprocessor defines: <tt>QT_NO_CAST_FROM_ASCII</tt>, <tt>QT_NO_CAST_TO_ASCII</tt>, <tt>QT_NO_KEYWORD</tt>. So don't forget {{qt|QLatin1String}}.
* No C casts in the header. Use <tt>static_cast</tt> if types are known. Use <tt>qobject_cast</tt> instead of <tt>dynamic_cast</tt> if types are QObject based. dynamic_cast is not only slower, but is also unreliable across shared libraries.
* In general, check your code for [[Development/Tutorials/Common_Programming_Mistakes|common mistakes]].

These recommendations are also true for code that are not in headers.

== Flags ==
Try to avoid meaningless boolean parameters in functions. Example of a bad boolean argument:
<source lang="cpp-qt">
static QString KApplication::makeStdCaption( const QString &caption,
bool withAppName,
bool modified);
</source>

Because when you read code that uses the above function, you can't easily know the significance of the parameters

<source lang="cpp-qt">
window->setCaption(KApplication::makeStdCaption( "Document Foo",
true, true));
</source>

The solution is to use {{qt|QFlags}}. If the options only apply to one function, call the <tt>enum FunctionNameOption</tt> and the QFlags typedef <tt>FunctionNameOptions</tt>. Do that even if there is only one option, this will allow you to add more options later and keep the binary compatibility.

So a better API would be:
<source lang="cpp-qt">
class KApplication
{
public:
/* [...] */
enum StandardCaptionOption {
/**
* Indicates to include the application name
*/
WithApplicationName = 0x01,
/**
* Note in the caption that there is unsaved data
*/
Modified = 0x02
};
Q_DECLARE_FLAGS(StandardCaptionOptions,
StandardCaptionOption)

/**
* Builds a caption using a standard layout.
*
* @param userCaption The caption string you want to display
* @param options a set of flags from MakeStandartCaptionOption
*/
static QString makeStandardCaption(const QString& userCaption,
const StandardCaptionOptions& options = WithApplicationName);
/* [...] */
};
Q_DECLARE_OPERATORS_FOR_FLAGS(KApplication::StandardCaptionOptions)
</source>

== Const References ==
Each object parameter that is not a basic type (int, float, bool, enum, or pointers) should be passed by reference-to-const. This is faster, because it is not required to do a copy of the object. Do that even for object that are already implicitly shared, like QString:

<source lang="cpp-qt">
QString myMethod( const QString& foo,
const QPixmap& bar,
int number );
</source>

'''Note:''' Avoid const references for return types though. Returning for example
<source lang="cpp-qt">
const QList<int> &someProperty() const;
</source>
means exposing the internal data structure for someProperty() and it's very difficult to change it in the future while preserving binary compatibility. Especially for implicitly shared objects the one refcount that one avoids by returning a const reference is often not worth it the exposure of implementation.

There are cases where it makes sense, where performance is absolutely critical and the implementation is very fixed. So think twice about it and consider returning a value instead:
<source lang="cpp-qt">
QList<int> someProperty() const;
</source>

== Signals and Slots ==
In the libraries, use <tt>Q_SIGNALS</tt> and <tt>Q_SLOTS</tt> instead of <tt>signals</tt> and <tt>slots</tt>. They are syntactically equivalent and should be used to avoid conflicts with boost signals, and with python's use of "slots" in its headers.

== Properties ==
Consider using <tt>Q_PROPERTY</tt> for properties. The reason is that properties (especially those marked <tt>SCRIPTABLE</tt>) will be accessible through the javascript interface.

If you follow the propname / setPropname naming scheme, moc sets a special flag for the {{qt|QMetaProperty}}.

== Explicit Constructors ==
For each constructor (other than the copy constructor), check if you should make the constructor <tt>explicit</tt> in order to minimize wrong use of the constructor.

Basically, each constructor that may take only one argument should be marked <tt>explicit</tt> unless the whole point of the constructor is to allow implicit casting.

== Avoid including other headers in headers ==
Try to reduce as much as possible the number of includes in header files. This will generally help reduce the compilation time, especially for developers when just one header has been modified. It may also avoid errors that can be caused by conflicts between headers.

If an object in the class is only used by pointer or by reference, it is not required to include the header for that object. Instead, just add a forward declaration before the class.

In this example, the class KFoo uses KBar by reference, so we do not need to include KBar's header:
<source lang="cpp-qt">
#include <kfoobase.h>
class KBar;
class KFoo : public KFooBase
{
public:
/* [...] */
void myMethod(const KBar& bar);
};
</source>

== Getting #includes right ==

There are two types of #include statements: <tt>#include <foo.h></tt> and <tt>#include "foo.h"</tt>.

Say we have the file <tt>xyz.h</tt> in <tt>/usr/include/mylib/</tt> that contains the following:
<source lang="cpp-qt">
#include <header1.h>
#include "header2.h"
</source>

The preprocessor will search for the file <tt>header1.h</tt> in all the paths given as <tt>-I</tt> arguments and then replace the line with the contents of that file.

For line 2 the preprocessor tries to use the file /usr/include/mylib/header2.h first and if it does not exist search for the file like it did for <tt>header1.h</tt>. The important part to note here is that the preprocessor does not look in the directory of the source file that includes <tt>xyz.h</tt> but in the directory where <tt>xyz.h</tt> resides.

Now, which include statement is the one to use? After all you can specify every directory you want using <tt>-I</tt> (or rather CMake's <tt>include_directories()</tt>) and thus could use <tt>#include <...></tt> everywhere.

=== As application developer ===
* Include headers from '''external''' libraries using '''angle brackets'''.
<source lang="cpp-qt">
#include <iostream>
#include <QtCore/QDate>
#include <zlib.h>
</source>
* Include headers from your '''own project''' using '''double quotes'''.
<source lang="cpp-qt">
#include "myclass.h"
</source>
Rationale: ''The header files of external libraries are obviously not in the same directory as your source files. So you need to use angle brackets.''

''Headers of your own application have a defined relative location to the source files of your application. Using KDE4's cmake macros your source directory is the first include switch to the compiler and therefore there's no difference in using angle brackets or double quotes. If you work with a different buildsystem that does not include the current source directory or disable CMAKE_INCLUDE_CURRENT_DIR then all includes (inside your application) using angle brackets will break.''

''Ideally the buildsystem would not need to specify <tt>-I<source directory></tt> though as that can break with library headers that have the same filename as a header of your project (i.e.: If a library has the header file <tt>foo.h</tt> and your project has a different file with the same filename the compiler will always pick the header from your project instead of the one from the library because the source directory of the project is specified first.)''

=== As library developer ===
* Include headers from '''external''' libraries using '''angle brackets'''.
<source lang="cpp-qt">
#include <iostream>
#include <QtCore/QDate>
#include <zlib.h>
</source>
* Include headers of your '''own library''' and libraries that belong to it using '''double quotes'''.
<source lang="cpp-qt">
#include "xyz.h" // same library and same directory
</source>

Rationale: ''The header files of external libraries are obviously not in a fixed location relative to your source files. So you need to use angle brackets.''

''Headers of your own libraries have a fixed relative location in the filesystem. Therefore you'' can ''use double quotes. You should use double quotes because otherwise the include statement could include a different header file than expected. An example how angle brackets can break the build:''

''<tt>/usr/include/libxyz/xyz.h</tt> includes <tt>foo.h</tt> using angle brackets and expects to have it replaced with the contents of the file <tt>/usr/include/libzyx/foo.h</tt>. Assuming there's another library that also ships a <tt>foo.h</tt> file in the directory <tt>/usr/include/anotherlib/</tt>. If the application that uses both libraries compiles with "<tt>g++ -I/usr/include/libxyz -I/usr/include/anotherlib ...</tt>" libxyz will work as expected. If the application compiles with "<tt>g++ -I/usr/include/anotherlib -I/usr/include/libxyz ...</tt>" the header <tt>xyz.h</tt> will include the file <tt>/usr/include/anotherlib/foo.h</tt> instead of the file that is shipped with libxyz. The same problem can appear if an application has a header file of the same name as a library and specifies <tt>-I./</tt> as the first include directory.''

=== Include order ===

Another important aspect of include management is the include order. Typically, you have a class named Foo, a file foo.h and a file foo.cpp . The rule is :

: ''In your file foo.cpp, you should include "foo.h" as the first include, before the system includes.''

The rationale behind that is to make your header standalone.

Let's imagine that your foo.h looks like this:
<source lang="cpp-qt">
class Foo
{
public:
Bar getBar();

};
</source>

And your foo.cpp looks like this:
<source lang="cpp-qt">
#include "bar.h"
#include "foo.h"
</source>

Your foo.cpp file will compile, but it will not compile for other people using foo.h without including bar.h . Including "foo.h" first makes sure that your foo.h header works for others.

=== Include guards ===
Header files should use guards to protect against possible multiple inclusion.
Your myfoo.h header should look like this:
<source lang="cpp-qt">
#ifndef MYFOO_H
#define MYFOO_H
... <stuff>...
#endif /* MYFOO_H */
</source>

To be even more careful, you may want to encode a namespace or subdirectory name (e.g. KFOO) into the guard macro name, for example: MYFOO_H, KFOO_MYFOO_H, or _KFOO_MYFOO_H_ are all acceptable macro names. By convention, the macro name should be all uppercase; but that is not a firm requirement.

== Static Objects ==
Global static objects in libraries should be avoided. You never know when the constructor will be run or if it will be run at all.
; Wrong
<source lang="cpp-qt">
static QString foo; // wrong - object might not be constructed
static QString bar("hello"); // as above
static int foo = myInitializer(); // myInitializer() might not be called
</source>
In particular, never construct QObject-derived objects this way. On Windows (MS Visual C++) the object's internals will be left uninitialized within a library and will lead to crashes ([http://www.kdedevelopers.org/node/2889 more info]).
<source lang="cpp-qt">
static QFile myFile("abc"); // QFile inherits QObject
</source>
; Correct
<source lang="cpp-qt">
static const int i = 42;
static const int ii[3] = {1, 2, 3};
static const char myString[] = "hello";
static const MyStruct s = {3, 4.4, "hello"};
K_GLOBAL_STATIC(QFile, myFile);
</source>

You can use [http://api.kde.org/4.0-api/kdelibs-apidocs/kdecore/html/group__KDEMacros.html#g75ca0c60b03dc5e4f9427263bf4043c7 <tt>K_GLOBAL_STATIC</tt>] macro (and for QObject-derived objects you should) to create global static objects which will be initialized the first time you use them.

== Signal and Slot Normalization ==
Since <tt>QObject::connect</tt> uses a string-based comparison
of the function signature, it requires some normalization to take
place. It does that automatically for you, but it takes some CPU
time, so, if it doesn't hurt your code's readability, normalize
manually your SIGNAL and SLOT entries.

For example, you may have the following code:
<source lang="cpp-qt">
QObject::connect(this, SIGNAL( newValue(const QString&,
const MyNamespace::Type&) ),
other, SLOT( value(const QString &) ));
</source>
It would be preferable to write as follows:
<source lang="cpp-qt">
QObject::connect(this, SIGNAL(newValue(QString,MyNamespace::Type)),
other, SLOT(value(QString)));
</source>

Note the absence of extra whitespace and the
reduction of pass-by-reference-to-const parameters to simple
pass-by-value ones. The normalization may involve other
transformations, but these are the most common ones. Also note that
types in namespaces should always use the full qualified name.
To be sure what the proper normalization is, read the {{path|.moc}} file
generated for the class.

'''Note''': If you are unsure about the normalization, don't do it. Let
QObject do it for you (the performance penalty is negligible in most cases).

== External Dependencies ==
When a library pulls in a new external dependency due to a new feature or a change in implementation, it is highly preferred to make that dependency optional if at all possible. For some core features in a library this may not be possible, but usually it is even if the cost is a degradation in features when built without that dependency.

All dependencies should be adequately documented in the build system so that they appear in the summary post-configure.

For libraries in the '''kdelibs module''', this is a hard requirement: '''no new non-optional dependencies may be added, all new dependencies must be made optional at configure time'''. Exceptions may be granted for unusual circumstances by sending a request to the kde-core-devel at kde.org mailing list and getting a consensus decision to grant an exception there.

== Documentation ==
Every class and method should be well documented. Read the [[Policies/Library Documentation Policy|KDE Library Documentation Policy]] for the guidelines to follow when documenting your code.

Also don't forget the license headers and copyrights in each file. As stated in the [[Policies/Licensing Policy|Licensing Policy]], kdelibs code must be licensed under the LGPL, BSD, or X11 license.

Author: [mailto:ogoffart@kde.org Olivier Goffart] March 2006

[[Category:Policies]]

Schedules/KDE4/4.10 Feature Plan

2012-10-15T01:35:01Z

Sandsmark: we now have lyrics view in juk

This is a list of planned features for the SC 4.10 release.

See also:

*[[Schedules/KDE4/4.10 Release Schedule]]
*[[Schedules/KDE4/4.9 Feature Plan]] (previous major release)

 Legend:

*todo => not started yet
*in-progress => started, but not completed yet
*done => completed

__TOC__

 

= kdelibs =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact
|}
NO NEW FEATURES ALLOWED
 

= kde-runtime =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|kio-mtp|KIO-Slave for MTP|philschmidt@gmx.net|Philipp Schmidt}}

|}
 

= kde-workspace =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|ksmserver|Merge the new qml based screen locker|mart@kde.org|Marco Martin}}


{{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Lanczos Filter broken after screen size changes ({{bug |296065}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|GHNS support for KWin Scripts ({{bug |296774}}, Review 104877)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|KConf Update Script for KWin 4.9 ({{bug |296775}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for scripted KWin Effects on kde-(look<nowiki>|</nowiki>app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for KWin Scripts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|GHNS support for Window Switching Layouts ({{bug |297636}}, Review 104894)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for Window Switcher Layouts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Update Documentation for Window Switcher Layouts ({{bug |297638}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|ThumbnailItem allows upscaling of Windows ({{bug |297864}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Increase ABI version for KDecorations ({{bug |299140}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}


{{FeatureDone|plasma-wallpapers|Color wallpaper: add listview to display thumbnails for background mode|rshah0385@kireihana.com|Reza Fatahilah Shah}}
{{FeatureInProgress|plasma workspace|Port Notifications applet to QML|mart@kde.org|Marco Martin}}
{{FeatureInProgress|plasma workspace|Port Task Manager applets to QML|hein@kde.org|Eike Hein (Sho_)}}
{{FeatureInProgress|plasma workspace|refresh Air Plasma theme|mart@kde.org|Marco Martin}}
{{FeatureInProgress|plasma workspace|Port Kickoff to qml|yellowcake-@gmx.net|Greg T}}
{{FeatureInProgress|systemsettings|Replace krandr KCM by libkscreen-based one|dvratil@redhat.com|Dan Vrátil}}
{{FeatureInProgress|plasma workspace|Port rssnow to qml|terietor@gmail.com|Giorgos Tsiapaliokas}}
{{FeatureInProgress|various|KActivities/SLC support for most our applications|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|plasma workspace|first desktop SLC applet release|mart@kde.org|Marco Martin}}
|}
 

= kde-baseapps =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureTodo|FolderView|Refactor into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}

{{FeatureTodo|Dolphin|Implement files quick preview feature (named Klook) |evgeniy.augin@osinit.ru|Evgeniy Auzhin}}

{{FeatureDone|print-manager|New Print manager KCM and applet (plasmoid) replacement, using C++ |dantti12@gmail.com|Daniel Nicoletti}}

{{FeatureDone|Kate|Support for Python plugins|srhaque@theiet.org|Shaheed Haque}}

{{FeatureDone|Kate|Advanced gid(1) plugin using both ID files and etags|srhaque@theiet.org|Shaheed Haque}}

|}
 

= kdeedu =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureTodo|Marble|Have support for "repeatX" in the projection classes|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Mars & Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Android|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Rocs|Journal files for projects.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|Revisit graph export/import functionality to fully support: TGF, DOT, GML, GraphML|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Printing and image export of graphs.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|KTouch|Ship ktouch/next|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureDone|Analitza|New plotting framework|percy.camilo.ta@gmail.com|Percy Camilo Triveño Aucahuasi}}
{{FeatureDone|KAlgebra|Splitted the QML Components from KAlgebraMobile|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra|New plotting plasmoid graphs, in QtQuick|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureInProgress|Pairs|Pairs Theme editor|marco.calignano@gmail.com|Marco Calignano}}
|}
 

= kdegames=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|libkdegames|[http://community.kde.org/KDE_Games/API_cleanup Major cleanup and rewrite] (done, except for the new highscore classes) '''Release team:''' please link to the [[Projects/Games/Porting_to_libkdegames_v5|porting instructions]] for third-party developers|stefan.majewsky@googlemail.com|Stefan Majewsky}}
{{FeatureInProgress|KGoldrunner|Use KGameRenderer and QGraphicsView for all graphics: the gameplay is the same as before.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureInProgress|KGoldrunner|Remove the status bar. All scores and status messages are in the viewport now.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KJumpingCube|Allow the displayed speed of moves to be adjusted.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KJumpingCube|Animate multi-stage moves, to make it easier for a human player to follow their progress.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KJumpingCube|Show multi-stage moves in an order that is easier to follow.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KJumpingCube|Validate the loading of saved games and report errors.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KJumpingCube|Rewrite the main AI class and make it use a true Minimax method.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KJumpingCube|Provide a choice of two AI styles, Kepler and Newton, with the possibility to add more.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KJumpingCube|Add settings to choose computer player, AI style and skill level for either or both of players 1 and 2.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KJumpingCube|Add board sizes 3x3 and 4x4, for simplified play.|iandw.au@gmail.com|Ian Wadham}}
|}
 

= kdegraphics=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|libkipi|[http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/dodonvictor/10002 Porting libkipi to KDE-XML GUI]|dodonvictor@gmail.com|Victor Dodon}}

|}
 

= kdemultimedia =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|Juk|[http://community.kde.org/Juk#Porting_plan Port Juk away from kde3support]|martin.sandsmark@kde.org|Martin Sandsmark}}
{{FeatureDone|Juk|Add lyrics view|martin.sandsmark@kde.org|Martin Sandsmark}}

|}
 

= kdenetwork=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kdepim =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact
{{FeatureInProgress|Facebook resource|Include it in default install|martin.klapetek@gmail.com|Martin Klapetek}}
{{FeatureInProgress|Akregator2|Merge in kdepim|montel@kde.org|Montel Laurent}}
{{FeatureInProgress|Knode|Merge in KMail|montel@kde.org|Montel Laurent}}
{{FeatureInProgress|BackupMail|Extend backup to all kdepim apps|montel@kde.org|Montel Laurent}}
{{FeatureInProgress|Sieve|Rewrite dialogbox|montel@kde.org|Montel Laurent}}
{{FeatureInProgress|libs|Move folderview to kdepimlibs/akonadi|montel@kde.org|Montel Laurent}}
|}
 

= kdeplasma-addons =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact
{{FeatureInProgress|Microblog|replace with QML version|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|StackFolder|Add applet for quick browse the stack of folders|ural.mullabaev@rosalab.ru|Ural Mullabaev}}
{{FeatureInProgress|ComicStrip|Replace with QML version|rshah0385@kireihana.com|Reza Fatahilah Shah}}
{{FeatureInProgress|Calculator|Replace with QML version|luizromario@gmail.com|Luiz Romário Santana Rios}}
{{FeatureDone|QML Wallpapers|Make it possible to have animated wallpapers written in QtQuick technologies.|aleixpol@blue-systems.com|Aleix Pol Gonzalez}}
|}
 

= kdesdk =

{| cellspa/cing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Okteta|Add a general KPart adapter to Kasten, than finish port of Okteta KPart to Okteta Kasten|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add global toggle option for the offset display, hex or decimal|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add Kate-like combined dialogs to query for actions on files|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add Okular like embedded notifications|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for memory mapping of files and 64-bit addressing|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Improve the titels of the changes to the bytearray to be more descriptive, best using ids to avoid text string|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Merge row and column widgets into one|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Store bookmarks and other view settings for next load|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}
|}

 

= kdeutils=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}

Schedules/KDE4/4.10 Feature Plan

2012-08-08T19:51:47Z

Sandsmark: porting juk

This is a list of planned features for the SC 4.10 release.

See also:

*[[Schedules/KDE4/4.10 Release Schedule]]
*[[Schedules/KDE4/4.9 Feature Plan]] (previous major release)

 Legend:

*todo => not started yet
*in-progress => started, but not completed yet
*done => completed

__TOC__

 

= kdelibs =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact
|}
NO NEW FEATURES ALLOWED
 

= kde-runtime =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kde-workspace =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|ksmserver|Merge the new qml based screen locker|mart@kde.org|Marco Martin}}


{{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Lanczos Filter broken after screen size changes ({{bug |296065}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|GHNS support for KWin Scripts ({{bug |296774}}, Review 104877)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|KConf Update Script for KWin 4.9 ({{bug |296775}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for scripted KWin Effects on kde-(look<nowiki>|</nowiki>app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for KWin Scripts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|GHNS support for Window Switching Layouts ({{bug |297636}}, Review 104894)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for Window Switcher Layouts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Update Documentation for Window Switcher Layouts ({{bug |297638}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|ThumbnailItem allows upscaling of Windows ({{bug |297864}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Increase ABI version for KDecorations ({{bug |299140}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}


|}
 

= kde-baseapps =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureTodo|FolderView|Refactor into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}

{{FeatureTodo|Dolphin|Implement files quick preview feature (named Klook) |evgeniy.augin@osinit.ru|Evgeniy Auzhin}}

|}
 

= kdeedu =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureTodo|Marble|Have support for "repeatX" in the projection classes|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Mars & Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Android|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Rocs|Journal files for projects.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|Revisit graph export/import functionality to fully support: TGF, DOT, GML, GraphML|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Printing and image export of graphs.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
|}
 

= kdegames=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|libkdegames|[http://community.kde.org/KDE_Games/API_cleanup Major cleanup and rewrite] (done, except for the new highscore classes) '''Release team:''' please link to the [[Projects/Games/Porting_to_libkdegames_v5|porting instructions]] for third-party developers|stefan.majewsky@googlemail.com|Stefan Majewsky}}

|}
 

= kdegraphics=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kdemultimedia =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|Juk|[http://community.kde.org/Juk#Porting_plan Port Juk away from kde3support]|martin.sandsmark@kde.org|Martin Sandsmark}}

|}
 

= kdenetwork=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kdepim =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact
{{FeatureInProgress|Facebook resource|Include it in default install|martin.klapetek@gmail.com|Martin Klapetek}}
|}
 

= kdeplasma-addons =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact
{{FeatureInProgress|Microblog|replace with QML version|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|StackFolder|Add applet for quick browse the stack of folders|ural.mullabaev@rosalab.ru|Ural Mullabaev}}
|}
 

= kdesdk =

{| cellspa/cing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Okteta|Add a general KPart adapter to Kasten, than finish port of Okteta KPart to Okteta Kasten|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add global toggle option for the offset display, hex or decimal|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add Kate-like combined dialogs to query for actions on files|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add Okular like embedded notifications|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for memory mapping of files and 64-bit addressing|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Improve the titels of the changes to the bytearray to be more descriptive, best using ids to avoid text string|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Merge row and column widgets into one|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Store bookmarks and other view settings for next load|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}
|}

 

= kdeutils=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}

Development/Tutorials/KWallet

2012-06-16T00:36:33Z

Sandsmark: /* main.cpp */

{{Template:I18n/Language Navigation Bar|Development/Tutorials/KWallet}}

== Abstract ==
A simple introduction for using the KWallet API, a secure storage framework.

Prerequisites: Basic KDE knowledge, C++.

== Example ==
The API is fun and easy to use, and will guarantee you a long and stable life.

In KWallet, entries are organized in Folders (or think of it as categories), and in them there are ''binary data'', ''maps'', ''passwords'' and a catch-all ''unknown''. Binary entries are application-specific arrays of bytes, maps should be known from QMaps, where a series of ''values'' are accessed by ''keys''. Passwords are simply strings, and ''Unknown'' is for everything else.

===dialog.cpp===
<syntaxhighlight lang="cpp-qt" line>
#include "dialog.h"

#include <QLayout>
#include <QLabel>
#include <QPushButton>
#include <QMap>
#include <QVBoxLayout>
#include <QSpacerItem>

Dialog::Dialog(QWidget *parent) :
QDialog(parent)
{
setLayout(new QVBoxLayout);
m_wallet = Wallet::openWallet(Wallet::NetworkWallet(),
winId(),
Wallet::Asynchronous);

QLabel *explanation = new QLabel("HELLO! "
"Please type in something to save in the wallet! "
"It will be saved in the form data folder, under "
"the entry http://test.com/#form.");
m_statusLabel = new QLabel("Opening wallet...", this);
m_statusLabel->setAlignment(Qt::AlignCenter);
m_keyInput = new QLineEdit(this);
m_valueInput = new QLineEdit(this);
m_launchButton = new QPushButton("Save!", this);
m_launchButton->setDisabled(true);

layout()->addWidget(explanation);
qobject_cast<QVBoxLayout*>(layout())->addStretch();
layout()->addWidget(m_statusLabel);
layout()->addWidget(new QLabel("Key:", this));
layout()->addWidget(m_keyInput);
layout()->addWidget(new QLabel("Value:", this));
layout()->addWidget(m_valueInput);
layout()->addWidget(m_launchButton);

connect(m_launchButton, SIGNAL(clicked()), SLOT(doSave()));
connect(m_wallet, SIGNAL(walletOpened(bool)), SLOT(walletOpened(bool)));
setMinimumSize(500, 200);
}

void Dialog::walletOpened(bool ok)
{

if (ok &&
(m_wallet->hasFolder(KWallet::Wallet::FormDataFolder()) ||
m_wallet->createFolder(KWallet::Wallet::FormDataFolder())) &&
m_wallet->setFolder(KWallet::Wallet::FormDataFolder())) {
m_launchButton->setDisabled(false);
m_statusLabel->setText("Idle.");
} else
m_statusLabel->setText("Error opening wallet!");

}

void Dialog::doSave()
{
if (m_keyInput->text().isEmpty() || m_valueInput->text().isEmpty()) {
m_statusLabel->setText("Empty field!");
return;
}

m_launchButton->setDisabled(true);

m_statusLabel->setText("Saving ...");

QMap<QString, QString> map;
map[m_keyInput->text()] = m_valueInput->text();
if (m_wallet->writeMap("http://test.com/#form", map)) m_statusLabel->setText("Something went wrong!");
else {
m_statusLabel->setText("Saved!");
m_keyInput->clear();
m_valueInput->clear();
}
m_launchButton->setDisabled(false);
}
</syntaxhighlight>

===dialog.h===
<syntaxhighlight lang="cpp-qt" line>
#ifndef DIALOG_H
#define DIALOG_H

#include <QDialog>
#include <QLabel>
#include <QLineEdit>
#include <KWallet/Wallet>

using KWallet::Wallet;

class Dialog : public QDialog
{
Q_OBJECT
public:
Dialog(QWidget *parent = 0);

private slots:
void doSave();
void walletOpened(bool ok);

private:
Wallet *m_wallet;
QLineEdit *m_keyInput;
QLineEdit *m_valueInput;
QLabel *m_statusLabel;
QPushButton *m_launchButton;
};

#endif // DIALOG_H
</syntaxhighlight>

===main.cpp===
<syntaxhighlight lang="cpp-qt" line>
#include "dialog.h"

#include <KAboutData>
#include <KApplication>
#include <KCmdLineArgs>

static KAboutData about(
"KWalletDemoApplication",
"",
ki18n("KWalletDemoApplication"),
"1.0",
ki18n("Demonstrates basic KWallet usage."),
KAboutData::License_LGPL,
ki18n("(C) 2010 Martin Sandsmark"),
KLocalizedString(),
"http://www.mts.ms/");

int main(int argc, char *argv[])
{
about.addAuthor(ki18n("Martin Sandsmark"), ki18n("Maintainer"), "martin.sandsmark@kde.org", "http://iskrembilen.com/");

KCmdLineArgs::init(argc, argv, &about);
KApplication app;

Dialog dialog;
dialog.show();
return app.exec();
}
</syntaxhighlight>

===CMakeLists.txt===
<syntaxhighlight lang="make" line>
project(Importer)

find_package(KDE4 REQUIRED)
add_definitions(${QT_DEFINITIONS} ${KDE4_DEFINITIONS})
include(KDE4Defaults)
include(MacroLibrary)
include_directories(${KDE4_INCLUDES} ${KDE4_INCLUDE_DIR} ${QT_INCLUDES})

set(SRCS main.cpp dialog.cpp)

kde4_add_executable(kwallet-demo ${SRCS})
target_link_libraries(kwallet-demo ${KDE4_KDECORE_LIBS} ${KDE4_KPARTS_LIBS} ${KDE4_KDEUI_LIBS})
install(TARGETS kwallet-demo ${INSTALL_TARGETS_DEFAULT_ARGS})
</syntaxhighlight>

Schedules/KDE4/4.9 Feature Plan

2012-02-27T02:07:39Z

Sandsmark: /* kdemultimedia */ last.fm-stuff in juk

This is a list of planned features for the SC 4.9 release.

See also:

*[[Schedules/KDE4/4.9 Release Schedule]]
*[[Schedules/KDE4/4.8 Feature Plan]] (previous major release)

 Legend:

*todo => not started yet
*in-progress => started, but not completed yet
*done => completed

__TOC__

 

= kdelibs =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kde-runtime =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kde-workspace =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kde-baseapps =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 
= kdeedu =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Android|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}

|}
 

= kdegames=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kdegraphics=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kdemultimedia =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureDone|JuK|last.fm scrobbling|martin.sandsmark@kde.org|Martin Sandsmark}}
{{FeatureDone|JuK|cover-fetching from last.fm|martin.sandsmark@kde.org|Martin Sandsmark}}

|}
 

= kdenetwork=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kdepim =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureTodo|Akonadi Google Resources|Move contacts and calendars resources from Akonadi Google project to kdepim-runtime|dan@progdan.cz|Dan Vratil}}

|}
 

= kdeplasma-addons =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}
 

= kdesdk =

{| cellspa/cing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Okteta|Add a general KPart adapter to Kasten, than finish port of Okteta KPart to Okteta Kasten|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add global toggle option for the offset display, hex or decimal|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add Kate-like combined dialogs to query for actions on files|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add Okular like embedded notifications|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for memory mapping of files and 64-bit addressing|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add view profiles, incl. editor/manager|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Improve the titels of the changes to the bytearray to be more descriptive, best using ids to avoid text string|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Merge row and column widgets into one|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Store bookmarks and other view settings for next load|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}
|}

 

= kdeutils=

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

|}

Projects/MovetoGit

2010-07-04T12:20:09Z

Sandsmark: sandsmark isn't stuck anymore

This is the page for co-ordinating KDE's move to [http://git-scm.com/ Git].

If you're interested in helping, you should join the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest@kde.org] mailinglist and [irc://chat.freenode.net/kde-git #kde-git] on freenode.

Meetings are wednesdays, 19:30 UTC, in #kde-git.

=The Plan=

KDE is, eventually, moving to Git. We will be using gitosis + Redmine + reviewboard on our own servers.

In the summer of 2009, [http://gitorious.org/amarok Amarok] moved to Gitorious to test the waters and find problems that would affect KDE.

After it has been decided in Jun 2010 to use our own servers, Amarok and Konversation moved to git.kde.org/projects.kde.org to test the waters and find problems that would affect KDE.

Once those problems have been solved, all of KDE will be able to switch.

==Why?==

Git offers many advantages over svn, including offline commits and much easier to keep a feature branch up-to-date. Many KDE developers are already using git-svn, but this tool has its limitations. We want to have the full power of Git available, and we have people willing to do the work necessary to migrate.

==How?==

When we move, KDE's svn repository will be migrated into several Git repos, all on git.kde.org. Main modules such as kdelibs and kdebase will each become one repository. Projects in extragear will each have their own repository. The projects.kde.org site will have a list (lists?) of all these repositories using the redmine project wiki. Scripts will be provided for downloading, say, all of extragear, so "moving" a project from kdereview to extragear would simply involve editing a file kept online that defined the location of projects.

A few things will stay in subversion - currently websites, translations and manuals. It's possible they could move to Git later, but they won't be part of the mass migration.

All KDE developers will in principle be able to use their existing "svn" accounts. Developers using HTTPS ideally would request their HTTPS SVN account to be converted to SSH as that makes it easiest for the KDE sysadmins, but alternatively they can also just provide a public key. At some point the KDE sysadmins are going to send everybody with a HTTPS SVN account an email with a link to a web app to collect their key (see http://www.omat.nl/2010/06/13/sysamin-update-your-email-address/).

From the times when gitorious.org was the preferred hosting solution, a procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].
Many points probably still apply, but have to be updated.

=Blockers=

Tasks that need to get done before we can migrate

==Setup git.kde.org==
{{Progress bar|40}}
'''Owner:''' Eike, Jeff, Sysadmin team

'''Status:''' ''Progressing''

: It [http://lists.kde.org/?l=kde-scm-interest&m=127612957219466&w=2 has been decided] to use gitosis + Redmine + reviewboard on our own servers rather than gitorious.org. Sysadmin team is preparing git.kde.org for this.

==Write / update importing rules for svn2git==
{{Progress bar|5}}
'''Owner:''' see below - volunteers needed!

'''Status:''' ''sho: ???, tumaix:started to read the docs, cryos: getting started [2010-01-06]''

:The importer is on gitorious.org as svn2git we have a set of rules to tell the importer what svn dirs turn into which git repos and those need constant updating whenever a new branch or tag or project is created. Currently the rules are mostly a rough draft, as seen by the large amount of rule-editing that had to be done for Konversation and Amarok. This has not been done for quite some time and so someone should rsync the svn repo run svn2git and fix the rules and importer whenever the import stops.

:This is a very big task, too big for one person; it's probably best to tackle it one module at a time

:To get started on a module, read [[Projects/MoveToGit/UsingSvn2Git|Using Svn2Git]]

:TZander has done the koffice ruleset as of 2009-01-06

:Jpwhiting has finished (more or less) the kdeaccessibility ruleset 2010-01-24.

:aavci has done the k3b ruleset as of 2010-01-27

progress details:
{| border="1"
!repo
!owner
!%
!comments
|-
|SC/kdeaccessibility
|jpwhiting
|99
|"more or less"?
|-
|SC/kdeadmin
|
|0
|
|-
|SC/kdeartwork
|
|0
|
|-
|SC/kdebase
|
|0
|
|-
|SC/kdebindings
|
|0
|
|-
|SC/kdeedu
|cryos?
|?
|update me!
|-
|SC/kdeedu/marble
|jmho
|100
|Contains: trunk with moves (playground->kdereview->kdeedu), regular kde branches/tags and the following other branches: marble-0.4, gsoc-2009 and geodata-nt. Checking done: gitk --all, verify-git-from-svn
|-
|SC/kdeexamples
|
|0
|
|-
|SC/kdegames
|jobermayr
|0
|
|-
|SC/kdegraphics
|
|0
|
|-
|SC/kdelibs
|
|0
|
|-
|SC/kdemultimedia
|eean
|0
|
|-
|SC/kdenetwork
| grundleborg
|0
|
|-
|SC/kdepim
|tnyblom
|95
|Needs verification.
|-
|SC/kdepim-runtime
|tnyblom
|95
|Needs verification.
|-
|SC/kdepimlibs
|tnyblom
|95
|Needs verification.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|
|0
|
|-
|SC/kdetoys
|
|0
|
|-
|SC/kdeutils
|
|0
|
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 95
| trunk and branches complete, need to cleanup tags from cvs days.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/sdk/kdevelop-plugins
| nsams
| 100
| done
|-
|extragear/sdk/quanta
| nsams
| 99
| done
|-
|extragear/utils/krecipes
| santa
| 10
|
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|75
|analyzing import history
|-
|kdesupport
|
|0
|
|-
|koffice
|tzander
|85
|All but tags are done
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|90}}
'''Owner:''' Stephen Kelly

'''Status:''' ''Proposed workflow identified. Partially depends on KDE policies regarding branches and merging. Gathering estimates for porting of tooling from svn to git. People unfamiliar with the tool are starting to learn to use it.''

'''Estimated completion date''': End of May.

'''Summary of issues'''

* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time. ''Estimate'' 10 calendar weeks.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

'''Resolved Issues'''

* Branch maintenance workflow '''Resolution: http://thread.gmane.org/gmane.comp.kde.scm-interest/1310'''
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated. ''Estimate'' 1 week to port the tools.
*** Internally used tools have been updated and are now being used to access git repos such as dbus.
* Other commitments
** Project deadlines and other commitments prevent the possibility of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
*** Most of the technical work regarding migration of kdepim repos has been completed by community member Torgny Nyblom.
* Tool knowledge
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
*** Workshops and use of git-svn have been used to bring developers up to speed on how to use git at some level.

=Nice to have before the migration=

==Push log==
{{Progress bar|100}}
'''Owner:''' sysadmin

'''Status:''' finished

It's a push log, similar to a local repository's reflog.

---------------

For every push, log:
- who pushed (not the Unix username, which will be "git")
- which branch heads changed (what from, what to)
- which tags were created
- the state of all other branches and tags

Just use git commit-tree with the empty tree and save everything in the commit
message, one after the other.

-----------

Gitolite includes this functionality inbuilt to itself, although all repositories are logged in the same file - bcooksley

==Script for downloading virtual KDE hierarchies==
{{Progress bar|0}}
'''Owner''':

'''Status:'''

:Let's start over on this.
what we already have: two build scripts for kde; kdesvn-build and build-tool.
what we want: an easy way for people to get large chunks of kde, without thinking about what urls the repos come from or having to look things up.

do kdesvn-build and build-tool satisfy this well enough?
or do we want a computer-readable file listing all the repos too?

btw, scripty has its own list of repos already. it's just in a rather weird bash file.

'''Discussion:'''

As far as I can see, kdesvn-build is able to do it, it should be just a matter of providing a configuration. As I'm not using build-tool, I can't say anything about it. --jmho

'''Links'''
[http://kdesvn-build.kde.org/]
[[Projects/MovetoGit/MassCloneScript]]
[http://rubyforge.org/projects/build-tool/]

==pre-receive hooks==
{{Progress bar|50}}
'''Owner:''' ''volunteers needed!!''

* Line endings and encodings

'''Discussion:'''
this got accidentally marked as done or something, but it's not.

This has now been ported to Git - bcooksley

Note however that it doesn't look for a .gitattributes file yet - patches welcome ( see sysadmin/repo-management on git.kde.org )

'''Notes:'''
> > As for line-endings, be careful because Git is different from Subversion.
>
> different how?

Just ensure that all files are stored as LF only, except if there's a
.gitattributes file saying "-crlf" (i.e., allow it to have CRLF).

==Snapshot to read-only svn==
{{Progress bar|0}}
'''Owner:'''

:It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?

'''Discussion'''

:Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04

:if we leave the docbook stuff in svn, we can avoid this a bit longer. --[[User:Chani|Chani]] 23:21, 12 November 2009 (UTC)

==[[Development/Tutorials/Git|Techbase Documentation]]==
'''Owner:''' Chani, greeneg, - ''please help out!''
{{Progress bar|10}}

:At least minimal documentation about how to checkout, how to request a merge needed, other git documentation and links to other git information would be very useful also.

:see the [[Development/Tutorials/Git|Git Tutorial Page]]. help wanted!!

'''Discussion'''

==Setup git mirrors for cloning==
{{Progress bar|0}}
'''Owner:''' No one (help!)
:Re-purpose the anonsvn servers. This item might be a blocker.
'''Discussion'''

==Local pre-commit hooks==
{{Progress bar|0}}
'''Owner:''' argonel

:A set of recommended local hooks that give useful warnings could be nice to have.

'''Discussion'''
...on the other hand, if we get a lot of bikeshedding about what hooks, then it won't be so nice. so I'd put this in the "very optional" pile. --[[User:Chani|Chani]] 19:10, 16 December 2009 (UTC)

=Post-migration Issues=

==Website Branding==
{{Progress bar|2|text=(initial ideas on the table)}}
'''Owner:''' ruphy

:KDE Gitorious should be branded accordingly, and should be reachable from git.kde.org as well as kde.gitorious.org

'''Discussion'''

Is this section still necessary at all? Perhaps some branding has to be done for redmine or cgit, but I don't know. --jmho

=Unscheduled & Open=

==Allow tagging without involving sysadmins==
{{Progress bar|100}}

'''Owner:''' sysadmin

:Gitolite allows sysadmin to permit certain people on certain repos only to manage both branches and tag without needing force push rights.

'''Discussion'''

==Account setup for Gitolite==
{{Progress bar|0}}

'''Owner:''' ''sysadmin''

:Accounts for existing SVN accounts which use SSH for access have been automatically granted access to Gitolite. Those who are still using HTTPS need to file a sysadmin bug to change their SVN account to SSH and will recieve Git access automatically.

==post-update hooks==
{{Progress bar|90}}
'''Owner:''' ''morice'' ''Ian Monroe''

:* License checker

'''Discussion:'''
We have a fairly complete set of post-update hooks now. See [http://gitorious.org/remotehook remotehook]. However, it would be nice to have a system that lives on the Gitorious server and/or requires less manual maintenance. But its certainly workable and no longer a blocker.

=Completed Tasks=

==Get rid of svn:externals==
{{Progress bar|100}}
'''Owner:''' David Faure

'''Status:''' ''???''

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* playground/utils strigi-chemical/test/ctfr
* playground/devtools kdevelop4-extra-plugins/php/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/python/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/qmake/parser/generated/kdevelop-pg-qt
* playground/devtools kommander-plugins/database3/admin
* playground/devtools kommander-plugins/database/admin
* playground/devtools kommander-plugins/datetimefuncs/admin
* playground/devtools kommander-plugins/htmlpart/admin
* playground/devtools kommander-plugins/httpform/admin
* playground/devtools kommander-plugins/kparts/admin
* playground/devtools kommander-plugins/qtactionproxy/admin
* playground/devtools kommander-plugins/timewidget/admin
* playground/devtools kommander-plugins/webkit3/admin
* playground/devtools kpackagemaker/admin

==EBN==
{{Progress bar|95}}
'''Owner:''' ''drf''

'''Status:''' ''Amarok has EBN checks''

:EBN's krazy checks currently run on kde's svn repo; it needs upgrading to download and check our git repos too.

:This would be easier if there was a repo-list that EBN could parse, as it can no longer just svn up to get everything.

==Talk to people using other distros about git==
{{Progress bar|100}}
'''Owner:''' Sebas, Eike

'''Discussion'''
* Gentoo: They seem to be prepared for moving their live SVN packages to git; their package manager has easily-reusable classes to fetch from an SCM and moving the ebuilds to using the git class rather than the SVN class should be easy. Positive comments to that end from people in #gentoo-kde.
* Fedora: Some unhappyness about git because SVN allows them to remotely produce a diff between two SVN URLs (or two revisions of one and the same URL) without making a checkout first, while git requires making a clone. Kevin Kofler (IRC nick Kevin_Kofler, #fedora-kde) says this will make their packager work harder.
* Debian: Is indifferent about the SCM switch.

==Post Update hooks==
{{Progress bar|100}}
'''Owner:''' ''morice, johan, mattr

:List of scripts needed:
:* BUG/CCMAIL
:* email/CIA

:Gitorious needs to provide a way for hooks to be called; KDE needs to write said hooks.

'''Discussion'''

:There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009
:Same situation as commit emails. I can do it but it doesn't scale well and a Gitorious-supported solution would be nicer. --[[User:Eean|eean]] 16:07, 12 November 2009 (UTC)

==Reviewboard==
{{Progress bar|100}}
'''Owner:''' darktears

This should be easily done with Gitorious web interface and merge requests actually.

'''Discussion'''

:but reviewboard has features gitorious (right now) doesn't, like commenting on specific lines and not having to set up a merge request. --chani
::Also email notifications when someone reviews are needed --thomasz
:We're working on this for someone else right now, so pretty soon --johan-s
:I consider the latest changes to gitorious to finish this. If more reviewboard features are still needed, and git supports reviewboard, I think this is something we can look at doing post-conversion. --Ian Monroe

==Gitorious Needs a feature to disable merge request emails for certain repos==
{{Progress bar|100}}
'''Owner:''' [http://gitorious.org/gitorious Gitorious]

Have a sensible system for merge request emails. This is now in place - you can join groups, chose whether to have emails on a per repo basis, etc.

==SSH blocked in corporations and universities.==
{{Progress bar|100}}
'''Owner:''' ''Unknown''

:Some universities tend to block the SSH port. There should be a workaround to use SSH on some different port. github.com already runs a SSH server on port 443. But that assumes you are using a proxy. It has been found that this hasn't worked with a lot of people, especially those who have a direct connection to the internet ( so some transparent blocking by the ISP ). It would be great if (almost) every KDE developer were to be asked to check if other ports work before KDE made the switch. Otherwise there could be an automated email where the git patches could be sent, and appropriately patched to the right location too.

'''Discussion'''

:http://blog.gitorious.org/2009/10/20/stuck-behind-a-firewall/, and there's always been HTTP cloning (although the current impl. in Git is a bit on the slow side) --johan-s

==Talk to windows guys about git.==
{{Progress bar|100}}
'''Owner:''' aseigo

'''Discussion'''

They aren't huge fans of git, but are using it. They require a single mainline and can't cope with multiple branches. Otherwise, it's workable, even if it will take an adjustment period.

==pre-commit hooks==
{{Progress bar|100}}
'''Owner:''' ''(unknown)''

:acltest, docbook, EOL/UTF-8

:A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every KDE repo.

'''Discussion'''

:gitorious guys said they *might* be willing to allow a few scripts on their server for KDE as a special exception, iirc. --chani

:: Yes, at least for basic things, heavier things like doc building would probably have to be mirrored (goes for pre/post) --johan-s

:It turns out that acl and docbook might not be needed so long as web and docs/ stuff stays in svn.

:: Here's where to find the current scripts - http://websvn.kde.org/trunk/kde-common/svn/hooks/ --[[User:Argonel|Argonel]] 23:06, 11 November 2009 (UTC)

::So: this is actually done because it needs no longer to be done? (boud)

::Apparently, so; moving to complete. (aseigo)

= other notes =

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

==Random==
http://mail.kde.org/pipermail/dot-stories/2005-May/000509.html might be a good guide on what docs we need.

some of this stuff was from the list from GCDS that was in this email [http://markmail.org/message/u6eqfjece7fibfyo http://markmail.org/message/u6eqfjece7fibfyo]

==IRC Meetings==
* [[Projects/MovetoGit/Meeting1111|Minutes]] of meeting 11 November 2009
* [[Projects/MovetoGit/Meeting1118|Next meeting]] 18:00, 25 November 2009 (UTC)

= jobs =
''TODO merge this with the todolists above''

michael jansen: talking to kdesvn-build/mpyne
:--Done? -> http://kdesvn-build.kde.org/releases/kdesvn-build-1.10.php -- Panagiotis Papadopoulos 1 November 2009
::Yes, but the __kdesvn-build-remote used in the impl isn't pleasant for users already on git so it still needs more work for them. [[User:Mpyne|Mpyne]] 20:32, 11 November 2009 (UTC)

jonas: domain name

ML: convert to SSH

chani: techbase docs for scripty

sebas/lydia/leo: communication with teams! tell people! keeping track that
everything is being done.

Development/Tutorials/KWallet

2010-06-21T21:46:03Z

Sandsmark: remember code tags

{{Template:I18n/Language Navigation Bar|Development/Tutorials/KWallet}}

== Abstract ==
A simple introduction for using the KWallet API, a secure storage framework.

Prerequisites: Basic KDE knowledge, C++.

== Example ==
The API is fun and easy to use, and will guarantee you a long and stable life.

In KWallet, entries are organized in Folders (or think of it as categories), and in them there are ''binary data'', ''maps'', ''passwords'' and a catch-all ''unknown''. Binary entries are application-specific arrays of bytes, maps should be known from QMaps, where a series of ''values'' are accessed by ''keys''. Passwords are simply strings, and ''Unknown'' is for everything else.

===dialog.cpp===
<code cppqt n>
#include "dialog.h"

#include <QLayout>
#include <QLabel>
#include <QPushButton>
#include <QMap>
#include <QVBoxLayout>
#include <QSpacerItem>

Dialog::Dialog(QWidget *parent) :
QDialog(parent)
{
setLayout(new QVBoxLayout);
m_wallet = Wallet::openWallet(Wallet::NetworkWallet(),
winId(),
Wallet::Asynchronous);

QLabel *explanation = new QLabel("HELLO! "
"Please type in something to save in the wallet! "
"It will be saved in the form data folder, under "
"the entry http://test.com/#form.");
m_statusLabel = new QLabel("Opening wallet...", this);
m_statusLabel->setAlignment(Qt::AlignCenter);
m_keyInput = new QLineEdit(this);
m_valueInput = new QLineEdit(this);
m_launchButton = new QPushButton("Save!", this);
m_launchButton->setDisabled(true);

layout()->addWidget(explanation);
qobject_cast<QVBoxLayout*>(layout())->addStretch();
layout()->addWidget(m_statusLabel);
layout()->addWidget(new QLabel("Key:", this));
layout()->addWidget(m_keyInput);
layout()->addWidget(new QLabel("Value:", this));
layout()->addWidget(m_valueInput);
layout()->addWidget(m_launchButton);

connect(m_launchButton, SIGNAL(clicked()), SLOT(doSave()));
connect(m_wallet, SIGNAL(walletOpened(bool)), SLOT(walletOpened(bool)));
setMinimumSize(500, 200);
}

void Dialog::walletOpened(bool ok)
{

if (ok &&
(m_wallet->hasFolder(KWallet::Wallet::FormDataFolder()) ||
m_wallet->createFolder(KWallet::Wallet::FormDataFolder())) &&
m_wallet->setFolder(KWallet::Wallet::FormDataFolder())) {
m_launchButton->setDisabled(false);
m_statusLabel->setText("Idle.");
} else
m_statusLabel->setText("Error opening wallet!");

}

void Dialog::doSave()
{
if (m_keyInput->text().isEmpty() || m_valueInput->text().isEmpty()) {
m_statusLabel->setText("Empty field!");
return;
}

m_launchButton->setDisabled(true);

m_statusLabel->setText("Saving ...");

QMap<QString, QString> map;
map[m_keyInput->text()] = m_valueInput->text();
if (m_wallet->writeMap("http://test.com/#form", map)) m_statusLabel->setText("Something went wrong!");
else {
m_statusLabel->setText("Saved!");
m_keyInput->clear();
m_valueInput->clear();
}
m_launchButton->setDisabled(false);
}
</code>

===dialog.h===
<code cppqt n>
#ifndef DIALOG_H
#define DIALOG_H

#include <QDialog>
#include <QLabel>
#include <QLineEdit>
#include <KWallet/Wallet>

using KWallet::Wallet;

class Dialog : public QDialog
{
Q_OBJECT
public:
Dialog(QWidget *parent = 0);

private slots:
void doSave();
void walletOpened(bool ok);

private:
Wallet *m_wallet;
QLineEdit *m_keyInput;
QLineEdit *m_valueInput;
QLabel *m_statusLabel;
QPushButton *m_launchButton;
};

#endif // DIALOG_H
</code>

===main.cpp===
<code cppqt n>
#include "dialog.h"

#include <KAboutData>
#include <KApplication>
#include <KCmdLineArgs>

static KAboutData about(
"KWalletDemoApplication",
"",
ki18n("KWalletDemoApplication"),
"1.0",
ki18n("Demonstrates basic KWallet usage."),
KAboutData::License_LGPL,
ki18n("(C) 2010 Martin Sandsmark"),
KLocalizedString(),
"http://www.mts.ms/");

int main(int argc, char *argv[])
{
about.addAuthor(ki18n("Martin Sandsmark"), ki18n("Maintainer"), "sandsmark@iskrembilen.com", "http://iskrembilen.com/");

KCmdLineArgs::init(argc, argv, &about);
KApplication app;

Dialog dialog;
dialog.show();
return app.exec();
}
</code>

===CMakeLists.txt===
<code cmake n>
project(Importer)

find_package(KDE4 REQUIRED)
add_definitions(${QT_DEFINITIONS} ${KDE4_DEFINITIONS})
include(KDE4Defaults)
include(MacroLibrary)
include_directories(${KDE4_INCLUDES} ${KDE4_INCLUDE_DIR} ${QT_INCLUDES})

set(SRCS main.cpp dialog.cpp)

kde4_add_executable(kwallet-demo ${SRCS})
target_link_libraries(kwallet-demo ${KDE4_KDECORE_LIBS} ${KDE4_KPARTS_LIBS} ${KDE4_KDEUI_LIBS})
install(TARGETS kwallet-demo ${INSTALL_TARGETS_DEFAULT_ARGS})
</code>

Development/Tutorials/KWallet

2010-06-21T21:43:41Z

Sandsmark: first version

{{Template:I18n/Language Navigation Bar|Development/Tutorials/KWallet}}

== Abstract ==
A simple introduction for using the KWallet API, a secure storage framework.

Prerequisites: Basic KDE knowledge, C++.

== Example ==
The API is fun and easy to use, and will guarantee you a long and stable life.

In KWallet, entries are organized in Folders (or think of it as categories), and in them there are ''binary data'', ''maps'', ''passwords'' and a catch-all ''unknown''. Binary entries are application-specific arrays of bytes, maps should be known from QMaps, where a series of ''values'' are accessed by ''keys''. Passwords are simply strings, and ''Unknown'' is for everything else.

===dialog.cpp===
#include "dialog.h"

#include <QLayout>
#include <QLabel>
#include <QPushButton>
#include <QMap>
#include <QVBoxLayout>
#include <QSpacerItem>

Dialog::Dialog(QWidget *parent) :
QDialog(parent)
{
setLayout(new QVBoxLayout);
m_wallet = Wallet::openWallet(Wallet::NetworkWallet(),
winId(),
Wallet::Asynchronous);

QLabel *explanation = new QLabel("HELLO! "
"Please type in something to save in the wallet! "
"It will be saved in the form data folder, under "
"the entry http://test.com/#form.");
m_statusLabel = new QLabel("Opening wallet...", this);
m_statusLabel->setAlignment(Qt::AlignCenter);
m_keyInput = new QLineEdit(this);
m_valueInput = new QLineEdit(this);
m_launchButton = new QPushButton("Save!", this);
m_launchButton->setDisabled(true);

layout()->addWidget(explanation);
qobject_cast<QVBoxLayout*>(layout())->addStretch();
layout()->addWidget(m_statusLabel);
layout()->addWidget(new QLabel("Key:", this));
layout()->addWidget(m_keyInput);
layout()->addWidget(new QLabel("Value:", this));
layout()->addWidget(m_valueInput);
layout()->addWidget(m_launchButton);

connect(m_launchButton, SIGNAL(clicked()), SLOT(doSave()));
connect(m_wallet, SIGNAL(walletOpened(bool)), SLOT(walletOpened(bool)));
setMinimumSize(500, 200);
}

void Dialog::walletOpened(bool ok)
{

if (ok &&
(m_wallet->hasFolder(KWallet::Wallet::FormDataFolder()) ||
m_wallet->createFolder(KWallet::Wallet::FormDataFolder())) &&
m_wallet->setFolder(KWallet::Wallet::FormDataFolder())) {
m_launchButton->setDisabled(false);
m_statusLabel->setText("Idle.");
} else
m_statusLabel->setText("Error opening wallet!");

}

void Dialog::doSave()
{
if (m_keyInput->text().isEmpty() || m_valueInput->text().isEmpty()) {
m_statusLabel->setText("Empty field!");
return;
}

m_launchButton->setDisabled(true);

m_statusLabel->setText("Saving ...");

QMap<QString, QString> map;
map[m_keyInput->text()] = m_valueInput->text();
if (m_wallet->writeMap("http://test.com/#form", map)) m_statusLabel->setText("Something went wrong!");
else {
m_statusLabel->setText("Saved!");
m_keyInput->clear();
m_valueInput->clear();
}
m_launchButton->setDisabled(false);
}

===dialog.h===
#ifndef DIALOG_H
#define DIALOG_H

#include <QDialog>
#include <QLabel>
#include <QLineEdit>
#include <KWallet/Wallet>

using KWallet::Wallet;

class Dialog : public QDialog
{
Q_OBJECT
public:
Dialog(QWidget *parent = 0);

private slots:
void doSave();
void walletOpened(bool ok);

private:
Wallet *m_wallet;
QLineEdit *m_keyInput;
QLineEdit *m_valueInput;
QLabel *m_statusLabel;
QPushButton *m_launchButton;
};

#endif // DIALOG_H

===main.cpp===
#include "dialog.h"

#include <KAboutData>
#include <KApplication>
#include <KCmdLineArgs>

static KAboutData about(
"KWalletDemoApplication",
"",
ki18n("KWalletDemoApplication"),
"1.0",
ki18n("Demonstrates basic KWallet usage."),
KAboutData::License_LGPL,
ki18n("(C) 2010 Martin Sandsmark"),
KLocalizedString(),
"http://www.mts.ms/");

int main(int argc, char *argv[])
{
about.addAuthor(ki18n("Martin Sandsmark"), ki18n("Maintainer"), "sandsmark@iskrembilen.com", "http://iskrembilen.com/");

KCmdLineArgs::init(argc, argv, &about);
KApplication app;

Dialog dialog;
dialog.show();
return app.exec();
}

===CMakeLists.txt===
project(Importer)

find_package(KDE4 REQUIRED)
add_definitions(${QT_DEFINITIONS} ${KDE4_DEFINITIONS})
include(KDE4Defaults)
include(MacroLibrary)
include_directories(${KDE4_INCLUDES} ${KDE4_INCLUDE_DIR} ${QT_INCLUDES})

set(SRCS main.cpp dialog.cpp)

kde4_add_executable(kwallet-demo ${SRCS})
target_link_libraries(kwallet-demo ${KDE4_KDECORE_LIBS} ${KDE4_KPARTS_LIBS} ${KDE4_KDEUI_LIBS})
install(TARGETS kwallet-demo ${INSTALL_TARGETS_DEFAULT_ARGS})

Development/Tutorials

2010-06-21T20:52:23Z

Sandsmark: link to (soon-to-be) kwallet tutorial

{{Template:I18n/Language Navigation Bar|Development/Tutorials}}

Tutorials are the fastest way of finding out what KDE will do for you, and how to do it. Here is a list of currently available tutorials '''for KDE4'''. Material for KDE3 and KDE2 is available on the bottom of this page.

== Introduction To KDE 4 Programming ==
Are you interested in writing applications with KDE 4? This tutorial series is aimed at those completely new to KDE programming.
;[[Development/Tutorials/First program|Hello World]]
:''A preliminary introduction to the very basics of KDE4 programming''

;[[Development/Tutorials/Using KXmlGuiWindow|Creating the Main Window]]
:''This tutorial shows you the magic of an application's most important thing: The main window.''

;[[Development/Tutorials/Using KActions|Using KActions]]
:''How to add actions to the menus and toolbars.''

;[[Development/Tutorials/Saving and loading|Saving and Loading]]
:''Introduces the KIO library while adding loading and saving support to our application.''

;[[Development/Tutorials/KCmdLineArgs|Command line arguments]]
:''Adds the ability to specify which file to open from the command line to our text editor.''

== Basics ==
;[[Development/Tutorials/KDE4 Porting Guide|Porting Your Application]]
:''Help Porting Applications from Qt3/KDE3 to Qt4/KDE4''

;[[Development/Tutorials/CMake|Introduction to CMake]]
:''How to use the CMake build system used by KDE4.''

;[[Development/Tutorials/Common Programming Mistakes|Common Programming Mistakes]]
:''Various common mistakes made while developing Qt and KDE applications and how to avoid them.''

;[[Development/Tutorials/Using Qt Designer|Using Qt Designer to build user interfaces]]
:''How to create UI files with designer, and how to integrate them into a KDE program.''

;[[Development/Tutorials/Using Qt Creator|Using Qt Creator to develop your KDE program]]
:''How to integrate Qt Creator use into KDE development.''

;[[Development/Tutorials/Creating Libraries|Creating Libraries to share code]]
:''How to add the library to the buildsystem and how to prepare the source code.''

;[[Development/Tutorials/Session_Management|Session Management]]
:''Make your application aware of X sessions''

== Testing And Debugging ==

;[[Development/Tutorials/Debugging|Debugging your application]]
:''Tips, tools and techniques to apply when debugging your KDE application''

;[[Development/Tutorials/Unittests|Writing Unittests for Qt4 and KDE4 with QTestLib]] ([http://developer.kde.org/documentation/tutorials/writingunittests/writingunittests.html Original link])
:''Tutorial by [mailto:bradh@frogmouth.net Brad Hards] that describes how to write unit tests using the QTestLib framework. It is presented as an example based tutorial, and is still under development.''

;[[Development/Tutorials/Code_Checking|Semi-automatic ways to detect code errors]]
:''Techniques you can use to detect errors in KDE code''

== Managing Configuration Data With KConfig ==
;[[Development/Tutorials/KConfig|Introduction To KConfig]]
:''An overview of the KConfig classes and how to use them in your application code''

;[[Development/Tutorials/Using KConfig XT|Using KConfig XT]]
:''Tutorial on how to efficiently use the KConfig XT framework.''

;[[Development/Tutorials/Updating KConfig Files|Updating KConfig Files]]
:''Tutorial on how to write an update script to keep changes in your application's config file format in sync with the user's already existing config file''

== Services: Applications and Plugins ==
;[[Development/Tutorials/Services/Introduction|Introduction to the Services Framework]]
:''An overview of the services framework in KDE and what it provides the application developer. Covers the system configuration cache (SyCoCa), the source data files and what the indexed information can be used for.''

;[[Development/Tutorials/Services/Traders|Finding Services Using Trader Queries]]
:''How to find services, such as plugins or mimetypes, that are indexed in the SyCoCa using Trader Query Syntax''

;[[Development/Tutorials/Services/Plugins|Creating and Loading Plugins Using KService]]
:''Learn how to define custom plugin types, find installed plugins (including 3rd party plugins) and load them in an easy and portable fashion using KService.''

== Localization ==
See also [[Localization|Localization portal]].

;[[Development/Tutorials/Localization/Unicode|Introduction To Unicode]]
:''An introduction to what Unicode is as well as how to handle Unicode data in KDE applications.''

; [[Development/Tutorials/Localization/i18n|Writing Applications With Localization In Mind]]
:''This tutorial covers what localization is, why it's important and how to ensure your application is ready to be localized. A must read for all application developers.''

; [[Development/Tutorials/Localization/i18n Mistakes|Avoiding Common Localization Pitfalls]]
:''There are several common mistakes that prevent applications from being properly localized. Find out what they are and how to easily avoid them in this tutorial.''

; [[Development/Tutorials/Localization/Building KDE's l10n Module|Building KDE's Localization Module]]
:''Building and installing language support from KDE's localization (l10n) module is a good idea for those working on applications in the main KDE repository. Doing so will allow you to test your application in another language and spot problem areas. Learn how to do just that in this tutorial.''

; [[Development/Tutorials/Localization/i18n Build Systems|Incorporating i18n Into the Build System]]
:''Once your application is ready to be localized, the next step is to ensure that translation files are built automatically and kept up to date. This tutorial covers the necessary CMakeFiles.txt additions as well the process of distributing the resulting message catalogs with your application.''

; [[Development/Tutorials/Localization/i18n Challenges|Common i18n Challenges and Solutions]]
:''This tutorial covers challenges that you may eventually run into such as translating handbooks and other data that exists outside of the source code, merging and handling obsolete .po files, dealing with freezes, coding in languages other than English and creating independent releases of or moving applications between KDE modules.''

; [[Development/Tutorials/Localization/i18n_Semantics|Semantic Markup of Messages]]
:''To ensure consistent presentation and more meaningful representations of messages in applications, semantic markup can be applied to messages marked for translation using the KUIT system. This tutorial describes how this system works.''

; [[Development/Tutorials/Localization/i18n Krazy|Automated i18n Code Checking]]
:''The Krazy code checker scans KDE's code and reports common i18n mistakes.''

== Documentation ==

;[[Development/Tutorials/API_Documentation|API Documentation]]
:''This tutorial explains how to document your APIs properly.''

;[[Development/Tutorials/Man_Pages|Man Pages]]
:''Writing and Generating Reference Manual Pages.''

== Accessibility ==

;[[Development/Tutorials/Accessibility|Accessibility]]
:''This tutorial will explain how to make your application accessible.''

;[[Development/Tutorials/Text-To-Speech|Text-To-Speech]]
:''How to utilize KDE's text to speech service in your application.''

== Application Automation and Scripting ==

=== D-Bus ===
; [[Development/Tutorials/D-Bus/Introduction|Introduction to D-Bus]]
:''A straight-forward introduction to the core concepts in D-Bus from an application developer's perspective, this tutorial covers what D-Bus is and how it can be used by applications.''
; [[Development/Tutorials/D-Bus/Accessing Interfaces|Accessing D-Bus Interfaces]]
:''A step-by-step guide to calling D-Bus methods and connecting to D-Bus signals using QtDBus.''
; [[Development/Tutorials/D-Bus/Intermediate_D-Bus|Intermediate D-Bus]]
:''Tips to make use of QtDBus when faced with problematic real-world interfaces.''
; [[Development/Tutorials/D-Bus/Creating Interfaces|Creating D-Bus Interfaces]]
:''Learn how to expose functionality in your application by creating and using custom D-Bus interfaces. Covers generating the XML descriptions, instantiating interfaces at run time and setting up the build system with CMake.''
; [[Development/Tutorials/D-Bus/CustomTypes|Using Custom Types with D-Bus]]: ''Learn how to use your own types in classes exported on D-Bus. Covers marhaling and unmarshaling of objects, the integration of custom types into XML descriptions and registering the custom types with the Qt Meta Object system.''
; [[Development/Tutorials/D-Bus/Autostart Services|D-Bus Autostart Services]]
:''Turn your application into a D-Bus autostart service with this tutorial. This D-Bus feature, also known as "D-Bus service activation", will ensure that even when your application isn't running that D-Bus calls made to it will work by relying on the D-Bus daemon itself to start your app if and when needed.''
; [[Development/Tutorials/Porting_to_D-Bus|Porting from DCOP to D-Bus]]
: ''Port your applications from DCOP to D-Bus with this handy guide.''

=== Konqueror ===
; [[Development/Tutorials/Creating Konqueror Service Menus|Creating Konqueror Service Menus]]
:''This tutorial shows you how to create mimetype-specific actions in Konqueror's context menu (aka "servicemenus").''

=== Kross ===
; [[Development/Tutorials/Kross/Introduction|Introduction to Kross]]
:''An introduction to the Kross Scripting Framework.''

; [[Development/Tutorials/Kross/Hello_World|Hello World]]
:''A first application with working kross code.''

; [[Development/Tutorials/Kross/Call_Functions_in_Kross|Calling Functions in Kross]]
:''Simple demonstration of calling scripting functions''

; [[Development/Tutorials/Kross/Connecting_Signals_and_slots_in_Kross|Connecting Signals and Slots in Kross]]
:''Simple demonstration of connecting object signals with script slots''

; [[Development/Tutorials/Kross/Scripts-as-Plugins|Scripts as Plugins with Kross]]
:''This tutorial provides a step-by-step introduction how to integrate scripts as plugins into a KDE application.''

; [[Development/Tutorials/Kross/Script-Actions|Placing script actions in your application menus ]]
:''Simple demonstration on how to extend you application menus to execute script files.''

; [[Development/Tutorials/Kross/ActionCollections|How to use an ActionCollection ]]
:''A small Tutorial on How to use Kross::ActionCollections.''
{{:KOffice/Plugin Tutorials}}

=== SuperKaramba ===
; [[Development/Tutorials/SuperKaramba|SuperKaramba Tutorial]]
:''This tutorial provides an overview of SuperKaramba, theme files and scripting with Python, Ruby and JavaScript.''

=== System Activity ===

: [[Development/Tutorials/SystemActivity/Scripting|Writing script actions for the process's context menu]]
:''This tutorial shows how to add a context menu action to show custom information about a process.

== Plugins and KParts ==

; [[Development/Tutorials/Writing kontact plugins|Writing kontact plugins]]:''Kontact plugins are KParts. This tutorial describes how you can write one.''

; [[Development/Tutorials/Using KParts|Using KParts]]:''Learn how to load a KPart into an application window.''

; [[Development/Tutorials/Writing Qt Designer Plugins|Writing Qt Designer Plugins]]:''Add your widgets to Qt Designer and thus make them usable in UI files.''

== Search and Metadata ==

=== Strigi ===

; [[Development/Tutorials/Writing file analyzers|Writing file analyzers]]
:''File analyzers extract data from files to display in the file dialogs and file managers. The data gathered this way is also used to search for files. KDE4 allows the use of multiple analyzers per file type. This tutorial describes how you can write new analyzers.''

=== [http://nepomuk.kde.org Nepomuk] ===

; [[Development/Tutorials/Metadata/Nepomuk/Quickstart|Nepomuk Quickstart]]
:''How to use Nepomuk resources in a quick and painless way without much fuss.''

; [[Development/Tutorials/Metadata/Nepomuk/RDFIntroduction|RDF and Ontologies in Nepomuk]]
:''An introduction to RDF and the usage of ontologies in Nepomuk.''

; [[Development/Tutorials/Metadata/Nepomuk/DataLayout|Data Layout in Nepomuk]]
:''An overview of which and how data is stored in Nepomuk.''

; [[Development/Tutorials/Metadata/Nepomuk/Resources|Handling Resources with Nepomuk]]
:''Nepomuk is the KDE library which provides easy access to metadata in the Nepomuk system. Learn how to make your application create and read metadata using the Nepomuk system.''

; [[Development/Tutorials/Metadata/Nepomuk/ResourceGenerator|Using the Nepomuk Resource Generator]]
:''Nepomuk includes a resource generator which creates convenience classes for handling metadata.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukQuery|Using the Nepomuk Query API]]
:''Starting with KDE 4.4 Nepomuk provides a desktop query API.''

; [[Development/Tutorials/Metadata/Nepomuk/AdvancedQueries|Advanced Queries]]
:''The real power of Nepomuk can only be exposed when performing fancy queries on the data repository. This tutorial provides an introduction to semantic and full text queries in Nepomuk.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukServer|The Nepomuk Server and the Architecture of the Nepomuk subsystem]]
:''The Nepomuk Server hosts the main Nepomuk data repository and can be accessed directly via a Soprano API.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukServices|Nepomuk Services]]
:''The Nepomuk Server manages a set of Nepomuk services.''
:* [[Development/Tutorials/Metadata/Nepomuk/StorageService|Storage Service]] ''The probably most important service hosts the Nepomuk data repository using [http://soprano.sourceforge.net Soprano].''
:* [[Development/Tutorials/Metadata/Nepomuk/OntologyLoaderService|Ontology Loader]] ''Makes sure installed ontologies such as RDF, RDFS, NRL, or Xesam are loaded into the storage repository.''
:* [[Development/Tutorials/Metadata/Nepomuk/FileWatchService|File Watch Service]] ''Monitors the file system for changes and updates the file resource paths and URIs in Nepomuk.''
:* [[Development/Tutorials/Metadata/Nepomuk/StrigiService|Strigi Service]] ''Controls Strigi, the file indexing tool which extracts metadata from files and stores it into the storage repository.''
:* [[Development/Tutorials/Metadata/Nepomuk/QueryService|Query Service]] ''Provides persistant query folders.''

; [[Development/Tutorials/Metadata/Nepomuk/TipsAndTricks|Nepomuk Tips and Tricks]]
:''A set of tips and tricks for development with Nepomuk and Soprano. This is a must-read if you intend to use Nepomuk in your application or hack on it directly.''

== Hardware Awareness (Solid) ==

;[[Development/Tutorials/Solid_Tutorials|Introduction to Solid]]
:''An introduction to using the Solid hardware discovery and interaction system in KDE applications.''

;[[Development/Tutorials/Solid_Network_Tutorial|Accessing Network Information]]
:''How to use the Solid system to get information about the network''

== Authorization and Privilege escalation (KAuth) ==
; [[Development/Tutorials/KAuth/KAuth_Basics|KAuth Basics]]
:''An overview of concepts and basic knowledge required to understand and use KAuth effectively''
; [[Development/Tutorials/KAuth/KAuth_Actions|Using KAuth actions in your application]]
:''How to execute KAuth actions in your application, and how to integrate them tightly into your UI''
; [[Development/Tutorials/KAuth/Helper_HowTo|Creating a KAuth helper to perform a privileged action]]
:''You will learn how to use KAuth's helpers and escalation facilities, and how to seamlessly make a privileged and non privileged portion of your application interact''
; [[Development/Tutorials/KAuth/KCM_HowTo|Creating a KCM requiring authorization upon saving]]
:''Learn how to use the high level KCModule API to create KCModules handling authorization, and its UI integration, on their own''

== Multimedia (Phonon) ==

;[[Development/Tutorials/Phonon/Introduction|Phonon]]
:''How to start with the multimedia API''

:''How to compile and use Phonon and its GStreamer backend on Linux using Qt 4.3.x''
::''This article gives you a quick brief of how you can use checkout, compile Phonon and its GStreamer backend on GNU/Linux with just Qt 4.3.x. Towards the end, the article also describes how a developer can make use of Phonon to create simple audio and video players. You can read the article [http://www.vcreatelogic.com/oss/docs/CompilingPhononOnLinux.pdf here]. You can download the editable OpenDocumentText file from [http://www.prashanthudupa.com/phonon/CompilingPhononOnLinux.odt here].''

== Plasma ==

See [[Development/Tutorials/Plasma|Plasma tutorials]].

== Communication (Decibel) ==

;[[Development/Tutorials/Decibel/GettingStarted|Getting started with Decibel]]
:''This tutorial describes how to set up Decibel.''

;[[Development/Tutorials/Decibel/Handling_TextChannels|Handling TextChannels]]
:''This tutorial introduces the basics of handling incoming TextChannels by guiding you through building a simple text chat application.''

== Personal Information Management (Akonadi) ==

;[[Development/Tutorials/Akonadi/Application|Using Akonadi in Applications]]
:''Displaying and modifying data provided by Akonadi''

;[[Development/Tutorials/Akonadi/Resources|Developing Akonadi Resources]]
:''Akonadi Resources are agent programs which transport PIM data between Akonadi and a backend (files, servers, etc)''

;[[Development/Tutorials/Akonadi/SerializerPlugin|Using custom data types with Akonadi]]
:''Akonadi can handle arbitrary data as item payloads through the use of a plugin based serialization framework''

;[[Development/AkonadiPorting|Porting Applications which use KResource API]]
:''Applications using KDE's now deprecated KResource APIs, e.g. KABC or KCal, need to be ported to use their Akonadi equivalents''

== Kate / Kwrite ==

;[[Development/Tutorials/Kate/KTextEditor Plugins|Getting started with KTextEditor plugins]]
:''Creating your first KTextEditor plugin''

;[[Development/Tutorials/Kate/KTextEditor_Plugins_Advanced|Developing a plugin with configuration dialog]]
:''Adding a configuration dialog to the Time & Date example''

;[[Development/Tutorials/Kate/KTextEditor_Example|A small Editor]]
:''Create a small application using KTextEditor''

== KDevelop ==

;[[Development/KDevelop-PG-Qt_Introduction|KDevelop-PG-Qt Introduction]]
:''Information on the KDevelop parser generator, useful for language plugins.''

==Printing==

;[[Development/Tutorials/Printing Hello World|Hello World]]
:''Introduction to the KDE printing system''

;[[Development/Tutorials/Printing Print Dialog|Print Dialog]]
:''Using the KDE print dialog''

== kioslaves ==
* [[Development/Tutorials/KIO Slaves/Using KIO Slaves in your Program|Using kioslaves in your Program]]
* [[Development/Tutorials/KIO Slaves/Hello World|Creating a Hello-World kioslave]]

== Collaboration ==

=== Open Collaboration Services (libattica) ===

;[[Development/Tutorials/Collaboration/Attica/Introduction|Introduction to Attica]]
:''In this tutorial a simple widget showing information about a Person on the server is created.''

=== Get Hot New Stuff ===

;[[Development/Tutorials/Collaboration/HotNewStuff/Introduction|Get Hot New Stuff 3 - Download]]
:''How to use KHotNewStuff3 in your application.'' 

;[[Development/Tutorials/Collaboration/HotNewStuff/Updates|Get Hot New Stuff 3 - Checking for Updates]]
:''How to check if updates for installed stuff are available without showing the dialog/widget.'' 

;[[Development/Tutorials/Collaboration/HotNewStuff/Upload|Get Hot New Stuff 3 - Upload]]
:''How to add an upload dialog to your application.'' 

Old links for KNS2 and KNS1 content: 

;[[Development/Tutorials/K Hot New Stuff2|Introduction to Get Hot New Stuff 2]]
:''A short tutorial about how to use KHotNewStuff2 in your application. Deprecated, use version 3''
;[[Development/Tutorials/Introduction to Get Hot New Stuff|Introduction to Get Hot New Stuff]]
:''An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.''

;[[Development/Tutorials/KNewStuffSecure|KNewStuff Secure]] ([http://developer.kde.org/documentation/tutorials/knewstuffsecure/index.html Original Link])
:''Tutorial showing how to share resources in a secured way (KDE 3.4 and later).'' By András Mantia <amantia@kde.org>.

== Goya ==
; [[Development/Tutorials/Introduction to Goya usage|Introduction to Goya usage]]
:''An introduction for the Goya subsystem usage, which allows you to easily add widgets to your itemviews and connect their signals to your code, as they were real widgets.''

; [[Development/Tutorials/Introduction to Goya usage 2|Introduction to Goya usage (part 2)]]
:''The second part of the tutorial, with a slightly more complex example than the first part.''

== Other programming languages ==

=== Python ===

;[http://www.learningpython.com/2008/09/20/an-introduction-to-pyqt/ An Introduction to PyQt]
:''Starting off''

;[http://lateral.netmanagers.com.ar/stories/BBS47.html PyQt by Example]
:''Another introduction to PyQt''

;[[Development/Languages/Python/PyKDE_WebKit_Tutorial|PyKDE WebKit Tutorial]]
:''A simple web browser application in PyKDE''

;[[Development/Tutorials/Python introduction to signals and slots|101 Introduction to signals and slots]]
:''A simple introduction to Qt's signal and slot architecture.''

;[[Development/Languages/Python/PyKDE_DBus_Tutorial|PyKDE DBus Tutorial]]
:''An introduction to DBus communication using PyKDE''

=== Ruby ===

;[http://developer.kde.org/language-bindings/ruby/kde3tutorial/index.html KDE Ruby Korundum tutorial]
:''A ruby version of Antonio Larrosa Jiménez's KDE tutorial by Richard Dale. See the [[Development/Languages/Ruby|Ruby Developers Corner]] for Qt tutorials and other info.''

;[[Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]
:''Nokia's fabulous introductory tutorial to Qt, translated to Ruby.''

;[[Development/Tutorials/Plasma/RubyApplet|Creating a Plasma Widget in Ruby]]
:''Tutorial that shows how to create your first Plasma Applet using the Ruby language.''

;[[Development/Tutorials/Developing_Qt4_Applications_using_Qt_Designer_and_Ruby_on_Kubuntu|Developing Qt4 Applications using Qt Designer and Ruby on Kubuntu]]
:''Tutorial that shows how to design a simple User Interface in Qt Designer and then use the resulting widget in a Qt Ruby application we build from scratch.''

;[[Development/Languages/Ruby/Ruby-Qt/KDE_Book|Ruby-Qt/KDE Book]]
:''There is also an approach to create an Ruby-Qt/KDE Book under a free license. The content will be created in this wiki.''

=== Shell ===

;[[Development/Tutorials/Shell_Scripting_with_KDE_Dialogs|Shell Scripting with KDE dialogs]] ([http://developer.kde.org/documentation/tutorials/kdialog/t1.html Original Link])
:''Tutorial by [mailto:bradh@frogmouth.net Brad Hards] that describes how to use KDE dialogs in shell scripts with kdialog. It is presented as an example based tutorial.''

== Graphics Programming ==

;[[Development/Tutorials/Graphics/Performance|QPainter Perfomance]]
:''Hints on avoiding common mistakes leading to poor performance when using QPainter''

== Using the KDE Games Libraries ==
;[[Development/Tutorials/Games/KStandardGameAction| KStandardGameAction]]
:''Using libkdegames to make your game fit the kdegames standard''
;[[Development/Tutorials/Games/Highscores| Highscores]]
:''Implementing a simple highscore table into your game''
;[[Development/Tutorials/Games/Theme Selector| Theme Selector]]
:''Using the libkdegames theme selection dialog''
;[[Development/Tutorials/Games/Palapeli Patterns| Palapeli Slicers]]
:''Creating a slicer plugin for Palapeli''

=== KGLEngine ===
;[[Development/Tutorials/Games/kglengine/kglengine-simpleBox| installation and your first KGLItem]]
:''start your first kglengine application''
;[[Development/Tutorials/Games/KGLEngine2d| kglpong]]
:''Now use our knowledge to make a pong''

=== KALEngine ===
;[[Development/Tutorials/Games/KALEngine| Play hello word sound]]
:''Using KALEngine for games sound development using openAL''
;[[Development/Tutorials/Games/KALEngine-music| Play music]]
:''Using KALEngine to play music in a stream''

== Using the KDE PIM Libraries ==
;[[Development/Tutorials/PIM/ical| iCalendar functionality]]
:''Using kcal to manage iCalendar files''

== Other tutorials ==

=== 2D Plotting (KPlotWidget) ===
;[[Development/Tutorials/KPlotWidget|Using the KDE data-plotting widget]]
:''This tutorial introduces KPlotWidget, which is used for 2-D data plotting. It includes information on simple usage of the widget (including adding and modifying data sets, and customizing the plot axes and labels), and advanced customization (including extending the widget through sub-classing).''

=== Spelling and Grammar Checking (Sonnet) ===
;[[Development/Tutorials/Sonnet/SonnetTutorial|Adding spell-checking or grammar-checking to KDE applications]]
:''This tutorial introduces Sonnet and how one may use it to add language correction to your KDE application. Sonnet's auxiliary features shall be described in a separate tutorial.''

=== Pixmap cache (KPixmapCache) ===
;[[Development/Tutorials/KPixmapCache|Using the KDE pixmap cache]]
:''This tutorial shows how to use KPixmapCache to cache e.g. pixmaps generated from SVGs or some data.''

=== Using MarbleWidget (Marble) ===
;[[Development/Tutorials/MarbleWidget|Using MarbleWidget]]
:''This short tutorial describes how to use the MarbleWidget in your project''

=== Using local SCM for KDE development ===
;[[Development/Tutorials/Git|Using Git to develop for KDE]]
:''This tutorial shows how to use Git to develop for KDE''

=== Kwin effect tutorial (blog) ===
;[http://blog.martin-graesslin.com/blog/?p=258 blog by Martin Graesslin]
:''This tutorial guides you through the development of a simple KWin effect''

=== Implementing KSysGuard sensors and adding them ===
;[[Development/Tutorials/Sensors]]
:''This tutorial shows how to write and KSysGuard sensor and connect it to the systray.''
Runners

=== Porting an application from KSystemTrayIcon to KStatusNotifierItem ===
;[[Development/Tutorials/PortToKStatusNotifierItem]]
:''This tutorials shows how to port an application using KSystemTrayIcon to KStatusNotifierItem''

=== Using the KDE Wallet API for safe storage ===
;[[Development/Tutorials/KWallet]]
:"Brief introduction to the KWallet API which can be used for storing all kinds of sensitive information."

== KDE2 and KDE3 Materials ==

;[[Development/Tutorials/KDE3|KDE3 Tutorials]]
:''These tutorials cover topics related to KDE3.''

;[[Development/Tutorials/KDE2|KDE2 Tutorials]]
:''These tutorials cover topics related to KDE2.''

[[Category:KDE4]]

Projects/Summer of Code/2009/Projects/Visualization in Phonon

2009-04-23T19:08:58Z

Sandsmark: obligatory Star-Trek reference

==whoami==
'''Name:''' Martin Sandsmark

'''Email Address:''' sandsmark@samfundet.no

'''Freenode IRC Nick:''' sandsmark

'''Location:''' Trondheim, Norway

==Goal==
All media-players using Phonon currently lacks visualizations and analyzers.

Most modern media players today have some form for visualization when playing music, from simple bar displays to scripts drawing on opengl-contexts, and I don't think music players based on phonon should be any different.

==Implementation Details==
First I will either make a custom Phonon::MediaNode or alter the Phonon::AudioOutput class so it makes available raw audio data (PCM), and some pre-processed data, for example Hartley-transforms (reusing code from Amarok 1). All data will be made available on request. The class will most probably always cache at least one frame, so data is always available, but it will not queue up data, so the data displayed is always up to date. Some interpolation could be applied, either in the application or in phonon, to make sure the visualization doesn't get too jumpy.

Then I will implement support for this in the Xine Phonon backend. This should be fairly simple as the data exported is just raw audio data, as it is sent to most audio outputs. If there's time left over after I finish all the required parts of this GSoC, I might look into implementing support in the GStreamer backend too.

Lastly I will implement first some simple visualizations in Amarok, as a demonstration. I have planned two; one like the default baranalyzer found in the default installation of Amarok 1, and a sonogram/spectrogram like the one found in Foobar2000 (and Amarok 1). The first will use the pre-processed data, and the last will use the raw PCM data. If there's time left over, I will implement a “fullscreen”-visualization using projectm (projectm just needs raw PCM data, and already has rather good integration with Qt).

==Tentative Timeline:==
April/May: I will start reading through and playing with the Amarok 1 code for analyzers. I will also read up on domain transformation and other related math, as I don't remember much of it, but still have the books. It isn't strictly necessary for this, but having a basic understanding of what is done should be good.

===May - 4. June===
I will start familiarizing myself with the internal workings of Phonon. I've only used the public API before, not really looking into how things works “behind the scenes”. Also try to get in contact with some Phonon hackers, and decide if I should make a custom MediaNode or not.

===Until June 11.===
I will branch off Phonon, implementing the necessary changes in the API.

===Until July 2.===
I will implement support in the Phonon Xine backend for exporting audio data, and also process the data to get levels, etc.

===Until July 30.===
During this time I will implement the simple analyzers/visualizations in amarok.

===Until August 10.===
Here I will go over my code, polish it, write some extensive documentation, and any time left over will be spent first writing a “fullscreen” visualization for Amarok, and if I still have time left over, I will implement support in the GStreamer backend.

[[Image:Locutus.jpg|frame|Locutus will make sure the deadline is maintained.]]

Contribute/Bugsquad/BugDays/KopeteDay2/Bugs still present in KDE 4

2008-07-20T11:22:36Z

Sandsmark: signing of is a good thing

===Bugs still present in KDE 4===
If a bug is still present in the KDE4 version of Kopete, list it here.

*{{Bug|139307}} Technically, this bug is fixed in KDE4, but a worse behavior has replaced it! (Should be a really easy fix though!) [[User:Kwilliam|kwilliam]]

*{{Bug|147092}} While the file itself is transfered, [[User:sandsmark|sandsmark]] kopete crashed while it finished the filetransfer from his jabber account to mine. Not really sure if this is a jabber issue or not, because msn filetransfers seem to cause crashes too, see {{Bug|162760}}. After some sleep we should be able to tell ;) [[User:brot|brot]]

*{{Bug|144750}} Added informations to the bug itself, joining MUC from the gmail jabber account works with psi, so should be a valid bug [[User:brot|brot]]

*{{Bug|141513}} While [[User:sandsmark|sandsmark]] sees the newly set avatar, i dont see it. Closing the chatwindow and reapplying the style doesnt help, kopete needs to be restarted. [[User:brot|brot]]

*{{Bug|160361}} Length of the password set by windows live (kopete doesnt seem to offer password changing for msn) is limited to 16 characters, and kopete allows to enter more than that while login, so maybe it fails because of that. Should be an easy to fix bug if thats the problem :) [[User:brot|brot]]

*{{Bug|130011}} Still shows animation when it shouldn't. [[User:Sandsmark|Sandsmark]]

Contribute/Bugsquad/BugDays/KopeteDay2/Bugs still present in KDE 4

2008-07-20T11:21:59Z

Sandsmark:

Contribute/Bugsquad/BugDays/KopeteDay2/Bugs no longer present in KDE 4

2008-07-20T11:11:37Z

Sandsmark: unable to reproduce

===Bugs no longer present in KDE 4===
Bugs that cannot be reproduced in the KDE 4 version of Kopete should be listed here.

*{{Bug|140238}} Can't reproduce that bug in 4.1 RC1 [[User:dtritscher|dtritscher]]
*{{Bug|143903}} Can't reproduce that bug in 4.1 RC1 [[User:dtritscher|dtritscher]]
*{{Bug|146102}} Text input box now adjusts correctly to color scheme in 4.1 RC1 [[User:dtritscher|dtritscher]]
*{{Bug|146889}} Can't reproduce that bug in 4.1 RC1 [[User:dtritscher|dtritscher]]
*{{Bug|146102}} Can't reproduce bug with kopete trunk, so should be fixed [[User:Brot|Brot]]
*{{Bug|131799}} Can't reproduce that bug in 4.0.99 [[User:sandsmark|sandsmark]]

Contribute/Bugsquad/BugDays/KopeteDay2/Bugs needing users with particular setups

2008-07-20T10:31:01Z

Sandsmark: Bug needs someone with a bttv card

===Bugs needing users with particular setups===
If a bug requires a particular hardware or software setup to reproduce that you do not have available, please list if here along with details of its requirements.

*{{Bug|135295}} Setup requires an ICQ account and the address book stored on an IMAP server. [[User:Kwilliam|kwilliam]]

*{{Bug|142074}} Need someone with KDE4 kmail or kaddressbook installed. [[User:Kwilliam|kwilliam]]
*{{Bug|141513}} Need someone with MSN Account. [[User:dtritscher|dtritscher]]
*{{Bug|144069}} Need someone with MSN Account. [[User:dtritscher|dtritscher]]
*{{Bug|146102}} Need someone with ICQ Account. [[User:dtritscher|dtritscher]]
*{{Bug|133606}} Need someone with a bttv (or probably any video capture card). [[User:sandsmark|sandsmark]]

Contribute/Bugsquad/BugDays/KopeteDay2

2008-07-20T00:05:37Z

Sandsmark: sign in

==Introduction==

This bug day will take place on Sunday, July 20th 2008, but feel free to start early. The aim of this bug day is to clear out as many Kopete bugs as possible. We are continuing from where we left off after the first Kopete bug day, two weekends ago. Our target for triage is bugs listed in [http://bugs.kde.org bugs.kde.org] under the product Kopete.

Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

You should be working with a KDE 4 version of Kopete, ideally from svn trunk or a beta or more recent version of KDE 4.1.

==Workflow==

* Always remember the golden rule of bug triage: '''Do NOT close bugs in bugzilla.''' List them on this wiki page in the appropriate section so they can be double checked before being closed in the bug tracker.

* First of all, put your IRC nickname in the [[#Sign-in|sign-in section]], along with details of what version of KDE / Kopete you are testing with. Be as specific as possible.

* Choose a group of bugs the [[#Division_of_Labour|division of labour section]]. Put your IRC nickname in the '''IRC Nickname''' column, and remember to keep the '''Status''' column up to date as you work through the group of bugs. There is a link provided in the '''Query''' column which will take you to the list of bugs in that group on bugzilla.

* For each bug in the list, you should try and reproduce it using the information provided in the bug report.

** If you are able to reproduce the bug, add a comment on bugzilla saying what version of Kopete/KDE you are running and that you managed to reproduce the bug. Then add it to the [[#Bugs_still_present_in_KDE_4|Bugs still present in KDE 4 section]].

** If you cannot reproduce the bug, put a comment stating that (with your Kopete/KDE version) on the bug report in bugzilla, and add it to the [[#Bugs_no_longer_present_in_KDE_4|Bugs no longer present in KDE 4 section]].

** If the bug report is not clear or does not provide enough information to reproduce the bug, leave a note asking politely for the information you would need to be able to try and reproduce the bug, and add it to the [[#Bugs_needing_more_information|Bugs needing more information section]].

** There are several other categories below which bugs might fall into. Please look at them for details about when bugs should be put there.
{{Note| If you are unsure about what to do with a bug, please ask on the IRC channel, and someone will help you.}}

{{Warning| '''Always''' write your IRC nickname after each comment on this page. If your techbase username is the same as your IRC nickname, you can do this quickly by typing <nowiki>~~~</nowiki>}}

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below:

{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Grundleborg|Grundleborg]]||svn trunk r831187
|-
|[[User:StormByte|StormByte]]||svn trunk r833536 ||
|-
|[[User:sandsmark|sandsmark]|| 4.0.99 ||
|}
{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Division of Labour==
{|
|-
!Component/Group !! No of bugs !! IRC Nickname !! Status !! Query
|-
| Address Book/1 || 5 || [[User:Kwilliam|kwilliam]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Addressbook+integration&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Chat Window/3 || 10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Chat+Window&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-12-19&chfieldto=2007-07-15&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Chat Window/4 || 12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Chat+Window&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2007-07-15&chfieldto=now&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Chatwindow styles/1 || 12 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Chatwindow+Styles&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Connection Status/1 || 3 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Connection+Status+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Contact List/1 || 10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Contact+list&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| GaduGadu/1 || 11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Gadu-Gadu+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| History/1 || 17 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=History+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Jabber/1 || 10 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Jabber+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2000-01-01&chfieldto=2006-05-30&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Jabber/3 || 15 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Jabber+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2006-12-05&chfieldto=2007-06-23&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Meanwhile/1 || 5 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Meanwhile+plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| MSN/6 || 14 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=MSN+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-01-03&chfieldto=now&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| General/9 || 11 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-05-11&chfieldto=2008-05-27&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| General/14 || 18 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=general&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfield=%5BBug+creation%5D&chfieldfrom=2008-06-28&chfieldto=now&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Notifications/1 || 2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Notifications&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Groupwise/1 || 4 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Novell+GroupWise+Messenger+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| SMS/1 || 1 || [[User:Kwilliam|kwilliam]] || done || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=SMS+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Statistics/1 || 6 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Statistics+plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Translator/1 || 3 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Translator+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Web Presence/1 || 2 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=Web+Presence+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|-
| Winpopup/1 || 5 || || || [http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kopete&component=WinPopup+Plugin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=&chfieldvalue=&order=Reuse+same+sort+as+last+time&cmdtype=doit&newqueryname=&namedcmd=2003-onwards Query]
|}
(Total bugs 176)

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to '''enable section editing''' by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Bugs still present in KDE 4}}

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Bugs no longer present in KDE 4}}

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Bugs needing more information}}

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Bugs in functionality not yet present in KDE 4}}

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Bugs_that_require_a_random_event_to_reproduce}}

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Non english locales}}

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Bugs needing attention from Kopete developers}}

{{:Contribute/Bugsquad/BugDays/KopeteDay2/Bugs that you cant do}}