KDE TechBase - User contributions [en]

Thread:Talk:Policies/Library Code Policy/Tool for normalization of SIGNAL/SLOT names

2011-09-28T20:43:40Z

Mghansen256: New thread: Tool for normalization of SIGNAL/SLOT names

There is a tool included in Qt to either find SIGNAL/SLOT names which are not normalized, or to even automatically correct them. However, you have to compile it on your own:

https://qt.gitorious.org/qt/qt/trees/v4.7.3/util/normalize

Thread:Talk:Policies/Library Code Policy/Include order: private headers

2011-09-28T20:39:59Z

Mghansen256: New thread: Include order: private headers

krazy2 wants a specific order of header/private header and moc file/private header. It would be nice to have some information on this here.

Getting Started/Using Project Neon to contribute to KDE

2011-02-05T10:38:12Z

Mghansen256: kdesvn-build->kdesrc-build

{{Template:I18n/Language Navigation Bar|Getting_Started/Using_Project_Neon_to_contribute_to_KDE}}

{{Note | Project Neon can help you with builds current as of --FIXME--}}

{{Warning | This Page is currently being reworked for the new Project Neon archive - Please disregard the content as long as this note is here!}}

[https://edge.launchpad.net/project-neon Project Neon] is a nightly build of the latest KDE trunk. It is an easy way for new contributors to KDE to get started without having to build the entire KDE-SVN tree and maintain the checkout. Additionally, dependencies are automatically handled and updated. This is suitable for new developers, translators, usability designers, documenters, promoters, bug triagers etc. This process makes the steps detailed on [[Getting_Started/Build/KDE4|this page]], including changes to your [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]] unnecessary.

However, for developers, it may at some point become necessary to build more components from SVN as you become more involved in the project. The [[Getting_Started/Build/kdesvn-build|kdesrc-build]] script is an easy way to build all or parts of KDE SVN.

== Requirements ==

Project neon always requires the latest stable Kubuntu release or development release. Previous versions of Kubuntu are not supported. It is possible to port Project Neon to other distributions, though there are currently no maintainers for other distributions working on the project. OpenSuse provides their own weekly build of KDE trunk. Find instructions on how to use it [[Getting Started/Using OpenSuse KDE unstable packages for development|here]].

== Installing Project Neon ==

To use Project Neon, add the following PPA (Personal Package Archive) to your <tt>sources.list</tt> using your preferred method:

<code bash>
sudo add-apt-repository ppa:neon/ppa
</code>
or
<code bash>
# Project neon nightly KDE4 build
deb http://ppa.launchpad.net/neon/ppa/ubuntu maverick main

#above repository is PGP signed, refer to below link for getting PGP key
https://launchpad.net/~neon/+archive/ppa
</code>

After that, you can simply install the nightly package of whichever modules you want to work on. The full package list is available on

--FIXME--

You can install all of the packages or just the ones you are interested in, depending on what you want to use them for. For example if you want to install the latest KDE Workspace (plasma, kwin etc), install the <tt>project-neon-kdebase</tt> package and <tt>project-neon-kdeplasma-addons</tt> package for extra plasmoids.

<code bash>
sudo apt-get install project-neon-kdebase project-neon-kdeplasma-addons
</code>

If you are only interested in application development in another module, you can install just the module package.

<code bash>
sudo apt-get install project-neon-kdepim
</code>

That command will also install the <tt>kdelibs</tt>, <tt>kdepimlibs</tt> and other dependencies too. In your regular (stable) KDE session you can then run the nightly version of your chosen application by using the full path from the command line after setting up the environment.

<code bash>
. /opt/project-neon/share/project-neon/environment.rc
/opt/project-neon/bin/kmail
</code>

This will correctly use the nightly version of libraries instead of using the stable versions, so no other changes are necessary to your library path etc.

Alternatively, instead of using the full path to the executable, you could add the following to your <tt>.bashrc</tt>

--TODO: NEEDS REWORK--
-- most of the setup is done in environment.rc
<code bash>
_STABLE_PATH=$PATH
function switchtonightly {
export PATH=/opt/kde-nightly/bin:$_STABLE_PATH
}

function switchtostable {
export PATH=$_STABLE_PATH
}
</code>

This will allow you to optionally run unstable applications when you choose to in your session.

<code bash>
# Runs the stable version of kmail
kmail
switchtonightly
# runs the nightly version of kmail
kmail
# runs the nightly version of knode
knode
switchtostable
# runs the stable version of kmail
kmail
</code>
--END TODO--

Note that settings for applications that you run from project neon do not conflict with your regular application settings and data. <tt>.project-neon-kde/</tt> is used instead of <tt>.kde/</tt>

== Using Project Neon for development ==

If you are joining one of the development teams in KDE, you will need a real SVN/GIT checkout in order to contribute your code back to the project and create patches easily.

Some extra tools (<tt>neonmake</tt>) are provided for this purpose in the package <tt>project-neon-utils</tt>.

--NOTE: project-neon-utils doesn't exist yet
<code bash>
sudo apt-get install project-neon-utils
</code>

Debugging Symbols:
The debugging symbols for every package are in it's corresponding -dbg package, so to install the debugging symbols for kdelibs you can use
<code bash>
sudo apt-get install project-neon-kdelibs-dbg
</code>

If you are already using a nightly package of the module you want to develop for, you should remove that, and checkout the development version. For example:

<code bash>
# Remove the packaged nightly version
sudo apt-get purge project-neon-kdepim

# Add below Project Neon source code repository to sources.list if you didn't use add-apt-repository
deb-src http://ppa.launchpad.net/neon/ppa/ubuntu maverick main

# Get the dependencies for building kdepim
sudo apt-get build-dep project-neon-kdepim
cd ~
# You may choose to do your development in a different folder.
cd Development
# Gets the latest version of the kdepim module.
git clone git://anongit.kde.org/kdepim
cd kdepim
# Shortcut provided by Project Neon to make the module
# and install it to the prefix /opt/project-neon/
sudo neonmake
</code>

Note that you should usually checkout a module from KDE, not an application. Most modules contain libraries shared within the module and which are necessary to build the applications in the module.

Also of note is the <tt>neonmake</tt> command. This is a shortcut which temporarily sets some environment variables like the <tt>LD_LIBRARY_PATH</tt>, the install prefix etc, then runs the equivalent of <tt>cmake && make && make install</tt>. It also runs rpath to configure the executable file to use the nightly libraries.

== Using Project Neon for translation ==

The Project Neon nightly packages include English language strings only. Translated packages are not available. However, if you are translating KDE applications, you can install the translations from KDE SVN in your normal workflow.

<code bash>
cd ~
cd Translations
# The -N switch checks out only the top level directory from svn.
svn co -N svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4
cd l10n-kde4
# scripts necessary to build translations.
svn up scripts
# Get the German translations
svn up de
# Generate the build files for the German language pack
./scripts/autogen.sh de
cd de
neonmake
</code>

After building the translations it is possible to either change the language in system settings, or run applications in another language using the environment variable <tt>KDE_LANG</tt>.

<code bash>
switchtonightly
KDE_LANG=de kmail
switchtostable
</code>

== Using Project Neon for documentation ==

The Project Neon nightly source packages include the official KDE User Documentation in English.

TODO: How to build user docs from SVN.

== Using Project Neon for promotion ==

If you are creating screenshots or screencasts of the latest version of KDE, project Neon is a simple and fast way of getting a default KDE4 session.

The KDE Promotion team recommends using the default background, theme, icons etc when preparing official promotional materials (unless the feature you are showing is related to configuring KDE artwork). Project Neon uses the default artwork that comes with KDE4, so it is useful for creating promo materials.

Here is a shortcut to get all available modules from the PPA:

<code bash>
sudo apt-get install project-neon-all
</code>

The application [http://ariya.blogspot.com/2008/06/creating-fancy-screenshots-with.html screenie] is provided since Kubuntu 8.10 as <tt>screenie-qt</tt>.

<code bash>
sudo apt-get install screenie-qt
</code>

== Contact the Team ==

You can reach the Project Neon team on IRC in
<code>
#project-neon on irc.freenode.net
</code>
by mail at
<code>
neon@lists.launchpad.net
</code>
or you can ask a question on [https://answers.launchpad.net/project-neon launchpad]

If you think there is a bug in our packaging of the provided software you can file a bug on [https://bugs.launchpad.net/project-neon launchpad]

[https://wiki.kubuntu.org/Kubuntu/ProjectNeon Team page in the Kubuntu Wiki]

Development/Tutorials/Code Checking

2011-01-02T10:48:45Z

Mghansen256: Update SVN links to gitorious.org links.

==Code Checking==
There are a lot of ways to find bugs in KDE code. Increasingly, KDE developers have started to use automated tools. You can use some of those tools to improve your own code.

===The KDE 'Krazy' Checker===
KDE developers have a simple set of tests that are collectively known as "Krazy". These tests were originally developed to be run as part of a larger set of tests on a machine known as [http://www.englishbreakfastnetwork.org http://www.englishbreakfastnetwork.org], or EBN for short. You can see the results of running the various tests on EBN (at http://www.englishbreakfastnetwork.org/krazy/).

You can also run the tests yourself. To do this, you need to obtain a copy of
the code from [http://gitorious.org/krazy/krazy/trees/master krazy2/install.txt] and install them. You can then test either a single file (using the krazy2 application) or a whole tree, including subdirectories (using the krazy2all application).

====How Krazy works====
The Krazy tests are essentially a form of static analysis - they check the
source code, but not how it runs.

Krazy exists as a framework comprising a number of different test runners, and
a set of plugins. The test runners are called krazy2, krazy2all, and krazy2ebn. The test runners just call one or more plugins on the appropriate code, and
format the results for display.

At this stage, most of the test runners are written in perl, however one is
written in C++ (using Qt) and it is quite possible to add your own tests, or
to modify a test - all sources are provided.

====Installing Krazy====
Krazy needs to be installed before use. Krazy has two different ways to be
installed - you can either modify the {{path|krazy2/install.sh}} script and
run it, or follow the instructions in the [http://gitorious.org/krazy/krazy/trees/master krazy2/install.txt] file. I recommend the second.

You may need to install additional perl modules like XML::LibXML, here is how:
linux-pudb:~/krazy2 # ./install.sh
MakeMaker FATAL: prerequisites not found.
Tie::IxHash not installed
XML::LibXML not installed

Please install these modules first and rerun 'perl Makefile.PL'.
linux-pudb:~/krazy2 # perl -mCPAN -e CPAN::shell
You may have to answer 25 useless questions here. In this case, just press ENTER 25 times. Then you go on like this:
cpan[1]> install XML::LibXML

The Tie::IxHash I installed from the distro repository (libtie-ixhash-perl) and also the perl-doc package is needed to install it.

{{Note|I had a minor problem with the plugin that is built from C++, because that plugin got installed into the wrong directory. If you are missing the passbyvalue plugin, then you may need to move it into the directory that contains the rest of your plugins.}}

====Using Krazy====
Krazy comes with a particularly good man page, which gives you the various
options and a usage example. The file is generated on installation. This is definitely recommended reading!

As noted above, there are three test runners - krazy2, krazy2ebn and krazy2all. If you are trying to check a single file, then krazy2 is the right tool. If you are trying to check a source tree (say, an application or a whole subversion module), then krazy2all is more useful. krazy2all doesn't have a man page, but
you can get a list of the options with krazy2all --help. You can also use krazy2 to get information on the various plugins, which can help you understand more about krazy2all.

krazy2ebn is the tool that runs over the KDE codebase on the [http://www.englishbreakfastnetwork.org EBN] and should not be run locally.
However, please see [[#Controlling Krazy on the EBN|Controlling Krazy on the EBN]] below to learn how you can control which plugins are run, and what files are processed by the krazy2ebn program on the EBN machine.

Remember that Krazy doesn't change your code - it only examines it. So you can safely experiment with running Krazy checks until you are confident that you understand what is happening.

Equally, that means that Krazy doesn't fix problems - it only tries to report them. Understanding what is being reported, and how to fix it, is up to you. You should also remember the KDE commit policy about not committing code that you don't understand. So fixing a spelling error in a comment is pretty safe, but blindly changing code to stop explicit constructor warnings from Krazy is not a good idea.

====In-Code directives====
The Krazy plugins support the following list of in-code directives:
* <tt>//krazy:skip</tt> - no Krazy tests will run on this file.
* <tt>//krazy:excludeall=<name1[,name2,...,nameN]></tt> - the Krazy tests ''name1'', etc will not be run on this file. Multiple occurrences of krazy:excludeall are allowed.
* <tt>//krazy:exclude=<name1[,name2,...,nameN]></tt> - the Krazy tests ''name1'', etc. will not be run on the line where this directive is found (see the [[#Suppressing false-positives|next section]] below for more information).

Note that these directives must be C++ style comments that can be put anywhere in the file desired (except embedded within C-style comments).

====Suppressing false-positives====
The Krazy tests are designed to minimise false positives (that is, alerts that do not represent real problems). However because most of the tests are conducted on a single line, there are some tests that might produce such a false positive. For example, code that does something like:
<code cppqt>
QString mystring;
mystring += "/";
</code>
will be flagged by the doublequote_chars checker, because it is more efficient to add a single char, as shown below:
<code cppqt>
QString mystring;
// note that we are using single quotes
// this is a char, not a char array
mystring += '/';
</code>

That same checker will produce a false positive for code that looks like:
<code cppqt>
std::string mystring;
mystring += "/";
</code>

You can suppress these false positives using a special comment format.
To exclude a particular plugin from being run on a line of code, simply add
a C++ comment containing the string "krazy:exclude=<plugin_name>". The plugins currently available can be found in the
[http://gitorious.org/krazy/krazy/trees/master repository].

Specifically, for this plugin use "krazy:exclude=doublequote_chars".
For example:
<code cppqt>
lenstr = "0" + lenstr;
</code>
becomes
<code cppqt>
lenstr = "0" + lenstr; // krazy:exclude=doublequote_chars
</code>

{{Note|Using c-style (/* */) comments will ''not'' work. You must use C++ style (//) comments when noting tests to be skipped.}}

====Controlling Krazy on the EBN====
This section describes how to use ''.krazy'' files to control the Krazy runs on the [http://www.englishbreakfastnetwork.org EBN]. The ''.krazy'' files are used to tell Krazy to skip over specific sub-directories, or files; or to disable certain plugins within those modules and sub-directories.

To ignore a sub-directory within a module, say {{path|kdepim/kmail}}, use the IGNORESUBS directory within the {{path|kdepim/.krazy}} file, like so:

<code>
IGNORESUBS kmail
</code>

Or you can ignore a set of directories by specifying a comma-separated list:

<code>
IGNORESUBS kmail,kontact,knode
</code>

To ignore files or directories within a module/subdir, specify a regular expression that matches the files to skip together with the SKIP directive.
For example, to skip the directories {{path|kdepimlibs/kcal/libical}}, {{path|kdepimlibs/kcal/versit}}, and the {{path|kdepimlibs/kcal/fred.c}} file, use this directive within the {{path|kdepim/kcal/.krazy}} file:

<code>
SKIP /libical/\|/versit/\|fred\.c
</code>

Use the EXCLUDE directive to disable a list of plugins for all files within a module/subdir:

<code>
EXCLUDE doublequote_chars,qclasses
</code>

To override the EXCLUDE directive set from a {{path|.krazy}} file up in the directory hierarchy, use the CHECK command. For example, the component level {{path|.krazy}} file may EXCLUDE the ''copyright'' and ''license'' plugins, but those plugins can be re-enabled in a module/subdir with the CHECK directive like so:

<code>
CHECK copyright,license
</code>

{{Note|Individual modules can be ignored as well, but this is an EBN administrator duty controlled by component-level ''.krazy'' files within the ''/usr/local/src'' hierarchy. See the [http://wiki.kde.org/English+Breakfast+Network English Breakfast Network wiki] for details.}}

===Krazy Modules===

Risk Ratings:

'''Low:''' Can be fixed by anyone with minimal risk of error.

'''Medium:''' Can be fixed by anyone with appropriate knowledge of C++ features involved, some testing advised.

'''High:''' Should only be fixed by maintainer/owner of code

If you don't understand the code, or you don't understand the fix, then do not fix the code.

Fixing apidox and spelling mistakes only requires a compile before submitting. All other fixes should be tested to an appropriate degree, the standard unit tests are useful for this.

====Module=spelling====

'''Risk from Fixing:''' Low

Spelling errors in comments and strings should be fixed as they may show up later in API documentation, handbooks, etc. Misspelled strings make the translator's job harder. Please use US English.

To exclude all checks in file comment at top of file:
<code>
// krazy:excludeall=spelling
</code>

To exclude an individual check comment at the end of the line:
<code>
// krazy:exclude=spelling
</code>

====Module=doublequote_chars====

'''Risk from Fixing:''' Low

Adding single characters to a QString is faster if the characters are QChars and not QStrings, i.e. use single quotes instead of double quotes around single characters.

The same holds for arguments to QString::startsWith(), QString::endsWith(), QString::remove(), QString::section(), and QString::split().

Use QString::remove() instead of QString::replace(foo,"")

Replace
<code>
QString path = oldpath + "/" + base;
</code>
with
<code>
QString path = oldpath + '/' + base;
</code>

To exclude all checks in file comment at top of file:
<code>
// krazy:excludeall=doublequote_chars
</code>

To exclude an individual check comment at the end of the line:
<code>
// krazy:exclude=doublequote_chars
</code>

====Module=nullstrassign====

'''Risk from Fixing:''' Low

Do not assign QString::null or QString() to a QString. Instead use the .clear() method.

Replace
<code>
fileName = QString::null;
</code>
or
<code>
fileName = QString();
</code>
with
<code>
fileName.clear();
</code>

When returning an empty string from a method use "return QString()" When passing an empty string use "QString()".

To exclude all checks in file comment at top of file:
<code>
// krazy:excludeall=nullstrassign
</code>

To exclude an individual check comment at the end of the line:
<code>
// krazy:exclude=nullstrassign
</code>

====Module=foreach====

'''Message:''' non-const ref iterator

'''Risk from Fixing:''' Low to Medium

When not using POD types (int, double, pointer, ...) you should use const & for your foreach variables. There are two reasons for this: 1) Prevents you from the mistake of writing foreach loops that modify the list, that is 'foreach(Foo f, list) f.a = f.b = f.c = 0;' compiles but does not modify the contents of list 2) Saves a copy constructor call for each of the list elements

Be careful if dealing with pointers? False positive for bool, qlonglong and qulonglong?

http://tsdgeos.blogspot.com/2008/04/qforeach-is-your-friend.html

Replace
<code>
foreach(QString str, stringList) {
</code>
with
<code>
foreach(const QString &str, stringList) {
</code>

'''Message:''' values or keys iteration

'''Risk from Fixing:''' Medium to High

http://tsdgeos.blogspot.com/2009/04/how-to-make-foreach-loops-that-dont.html

To exclude all checks in file comment at top of file:
<code>
// krazy:excludeall=foreach
</code>

To exclude an individual check comment at the end of the line:
<code>
// krazy:exclude=foreach
</code>

====Module=strings====

'''Message:''' QLatin1String issues

'''Risk from Fixing:''' Low to Medium

Some QString methods (like startsWith() and endsWith()) are more efficient if they are passed a QLatin1String, avoiding an implicit conversion from const char *.

Replace
<code>
aString.startsWith("init")
</code>
with
<code>
aString.startsWith(QLatin1String("init"))
</code>

A common false positive is with QByteArray which cannot take a QLatin1String.

To exclude all checks in file comment at top of file:
<code>
// krazy:excludeall=strings
</code>

To exclude an individual check comment at the end of the line:
<code>
// krazy:exclude=strings
</code>

====Module=includes====

See http://techbase.kde.org/Policies/Library_Code_Policy#Getting_.23includes_right.

'''Message:''' duplicate includes

'''Risk from Fixing:''' Low

The same file has been included twice, remove the second occurrence.

'''Message:''' include own header first

'''Message:''' include own _p header first

'''Risk from Fixing:''' Medium

The cpp file should include their own .h and _p.h headers first in the file (but below config.h). Move the includes to the correct position. You may need to adjust includes and forward declarations in other files as a result, the compiler will advise of these.

'''Message:''' missing or improper include guard in header

'''Risk from Fixing:''' Low

Either the include guards are missing, or they are not appropriately encoded macro names, e.g. do not include the class name.

'''Message:'''

Use <..> to include installed headers.

'''Message:'''

To include Qt headers from installed headers.

To exclude all checks in file comment at top of file:
<code>
// krazy:excludeall=includes
</code>

To exclude an individual check comment at the end of the line:
<code>
// krazy:exclude=includes
</code>

====Module=qclasses====

'''Risk from Fixing:''' Medium

Deprecated Qt classes and classes that have a KDE version shouldn't be used. Also KDE versions of some Qt GUI elements provide a consistent look and feel for the KDE desktop. See http://techbase.kde.org/Policies/API_to_Avoid

Some of the K classes don't just add features to the Qt ones and might not even be based on the Qt class. '''Please refer to the API documentation before porting to the K classes.'''

To exclude all checks in file comment at top of file:
<code>
// krazy:excludeall=qclasses
</code>

To exclude an individual check comment at the end of the line:
<code>
// krazy:exclude=qclasses
</code>

==Compiler Warnings==
In addition to the various Krazy tools, you can also get valuable assistance from the warnings that the compiler emits, especially if you enable additional warnings (per the documentation for your compiler), and also if you test with more than one compiler (e.g. if you can test on Linux with both GCC and the Intel compiler; or on Linux with GCC and also on Windows with the Microsoft compiler).

Getting Started/Build/Distributions/Debian

2010-12-25T21:24:10Z

Mghansen256:

{{Template:I18n/Language Navigation Bar|Getting_Started/Build/KDE4/Kubuntu and Debian}}
This page details installation of KDE SC 4 build requirements on any recent Kubuntu or Debian system. That is, if you want to build KDE SC 4 Platform, the required (and some strongly recommended) packages are installed with the commands on this page.

'''If Kubuntu doesn't have QT4.6 yet, you can get it by adding this repository ppa:mapopa/qt4.6 instead of compiling kde-qt'''

== KDE 4.x ==
Install these for any KDE 4.x release, then add specific packages for point releases as below. Then add any optional packages you like, as described below.
<code bash>
sudo aptitude install build-essential xorg-dev cdbs debhelper cmake \
kdesdk-scripts subversion ssh xserver-xephyr doxygen dbus-x11 \
libxml2-dev libxslt1-dev shared-mime-info libical-dev libgif-dev libssl-dev \
libboost-dev libboost-program-options-dev libboost-graph-dev libgpgme11-dev libxine-dev \
libqimageblitz-dev libbz2-dev libdbus-1-dev libpam0g-dev libpcre3-dev \
libkrb5-dev libsm-dev libclucene0ldbl libclucene-dev libjpeg62-dev \
libxtst-dev xsltproc libxrender-dev libfontconfig1-dev automoc librdf0-dev \
libdbusmenu-qt-dev docbook-xsl docbook-xml libattica-dev libqt4-webkit-dev \
shared-desktop-ontologies libphonon-dev

sudo aptitude install libqt4-dev dbus-x11 \
libstreamanalyzer-dev libstrigiqtdbusclient-dev \
libxml2-dev libxslt1-dev shared-mime-info libgif-dev libpcre3-dev \
libjpeg62-dev librdf0-dev libdbusmenu-qt-dev docbook-xsl docbook-xml \
libjasper-dev libopenexr-dev libacl1-dev

sudo aptitude install libgpgme11-dev libsasl2-dev

sudo aptitude install libxine-dev
sudo aptitude install libqimageblitz-dev
</code>

=== 4.6 ===
(Also known as trunk)
This (along with the command for 4.x above) installs all compilation requirements for kde4 (with the exception of qt4) and some strongly recommended packages such as libssl-dev for https support. Further recommended and optional packages are listed below.
<code bash>
sudo aptitude install graphviz libxml2-utils libopenexr-dev libjasper-dev libenchant-dev \
libavahi-common-dev libaspell-dev libasound2-dev libldap2-dev libsasl2-dev \
libsmbclient-dev libxkbfile-dev libxcb1-dev libxklavier-dev libxdamage-dev \
libxcomposite-dev libbluetooth-dev libusb-dev network-manager-dev libsmbclient-dev \
libsensors-dev libnm-util-dev libusb-dev libcfitsio3-dev libnova-dev libeigen2-dev \
libopenbabel-dev libfacile-ocaml-dev libboost-python-dev libsvn-dev libsvncpp-dev \
libqt4-dev libqca2-dev libstreamanalyzer-dev libstrigiqtdbusclient-dev \
libcommoncpp2-dev libidn11 libidn11-dev libpci-dev libxss-dev libxft-dev \
libpolkit-dbus-dev libpolkit-grant-dev libpolkit-dev git libpoppler-qt4-dev \
libspectre-dev
</code>

=== 4.5 ===
<code bash>
sudo aptitude install libv4l-dev # for kdenetworks
sudo aptitude install liblcms1-dev # for kdegraphics
</code>

=== 4.4 ===
(Nothing extra needed)

== kdelibs dependencies ==

=== Optional packages ===
* libasound2-dev - The Alsa sound system
* libaspell-dev - spell checking support (in kwrite etc)
* libavahi-common-dev - avahi/zeroconf service discovery
* libenchant-dev - spell checking wrapper library
* libjasper-dev - image processing library
* libopenexr-dev - image processing library
* libxml2-utils - used to validate generate doc files
<code bash>
sudo aptitude install libasound2-dev libaspell-dev \
libavahi-common-dev libenchant-dev libjasper-dev libopenexr-dev \
libxml2-utils
</code>

== kdepimlibs dependencies ==
There are no additional optional dependencies

== kdebase dependencies ==

=== kdebase-apps optional ===
* libxcb1-dev - X C binding - Used for video widget support in xine
* libxkbfile-dev - keyboard configuration package
* libsmbclient-dev - for samba support in kde4

<code bash>
sudo aptitude install libsmbclient-dev libxkbfile-dev libxcb1-dev
</code>

=== kdebase-workspace optional ===
* libsmbclient-dev - for samba support in kde4
* network-manager-dev - Can be used by solid for network management
* libusb-dev - for usb support in solid
* libbluetooth-dev - for bluetooth support in solid
* libxcomposite-dev - for compositing support in kwin
* libxdamage-dev - for compositing support in kwin
* libxklavier-dev - virtual keyboard
* libsensors-dev - Support for hardware sensors (eg, temperature, fans)
* libpam0g-dev - Authentication module
* libnm-util-dev - needed to build solid with network manager
<code bash>
sudo aptitude install libxklavier-dev libxdamage-dev libxcomposite-dev \
libbluetooth-dev libusb-dev libcaptury-dev network-manager-dev \
libsmbclient-dev libsensors-dev libpam0g-dev libnm-util-dev
</code>

== kdegraphics ==
* libpoppler-qt4-dev - PDF support in Okular
* libspectre-dev - postscript support in Okular
* liblcms1-dev
* libexiv2-dev - to build Gwenview

== kdeedu ==
The following packages are recommended if you intend to use kstars:

* libfacile-ocaml-dev - used by kalzuim.
* libboost-python-dev - optional for kig.
* libreadline-dev - Gives kalgebra a console interface.
* libopenbabel-dev - used by kalzium.
* libeigen2-dev - used by kalzium.
* libusb-dev - Provides KStars INDI support.
* libcfitsio3-dev - Gives KStars support for FITS images.
* libnova-dev - A general purpose, double precision, Celestial Mechanics, Astrometry and Astrodynamics library for KStars.

<code bash>
sudo aptitude install libusb-dev libcfitsio3-dev libnova-dev libeigen2-dev \
libopenbabel-dev libfacile-ocaml-dev libboost-python-dev
</code>

== koffice ==
* libqca2-dev - qt cryptographic support.

== kdepim ==
* libqca2-dev - qt cryptographic support.

== kdenetwork ==
* libqca2-dev - qt cryptographic support. Used for jabber protocol.

== kdevplatform ==
* libsvn-dev
* libboost-serialization-dev

== kdevelop ==
* kdevplatform-dev
* kdebase-workspace-dev

== Other ==
To enable XMMS support for the 'Now Playing' plasma data engine in kdebase, you will need to either compile XMMS from source, or install the package from a [http://www.pvv.ntnu.no/~knuta/xmms/ third-party XMMS package repository].

Return to [[Getting_Started/Build/KDE4#kdelibs|building KDE 4]].

Projects/Digikam/CodingSprint2010

2010-06-07T20:33:53Z

Mghansen256: Polish

== KDE Graphics Coding Sprint 2010 ==

*The KDE Graphics coding sprint 2010 will take place in [http://www.aixenprovencetourism.com/uk Aix en Provence, France], from August 27th to 29th. It's organized by Gilles Caulier.

http://farm5.static.flickr.com/4031/4620818767_5fb7450bc0_m.jpg

=== Location ===

==== Hotel ====

*Hotel Paul, near Aix en provence city center. Look [http://aix-en-provence.com/hotelpaul at this url for details]

*3 nights have been books to this hotel : Thursday 26/Friday 27 ; Friday 27/Saturday 28; Saturday 28/Sunday 29.
*If you want to stay more time in this hotel to visit Aix en provence, let's me hear.

*There is a [http://maps.google.fr/?ie=UTF8&t=h&layer=c&cbll=43.533328,5.445936&panoid=u7_H9GZ7Jv-Vfn-oafCRVQ&cbp=12,76.99,,1,2.48&ll=43.533217,5.445999&spn=0,0.002064&z=20 Street-View link there] to see the front of Hotel Paul.

*For more details, see map from "Coding Location" section.

==== Directions ====

===== By Plane =====

*The closest airport is Marseille/Provence International (MAR).

*There is a regional bus from Marseille airport. The fare is around €7.0. Take a look [http://www.mrsairport.com/eng/acces/acces_train+bus.jsp at this page for details.]

*Text me (Gilles) when you board the bus in Airport or when you have got lost.

*For more details, see map from "Coding Location" section.

===== By Car =====

*Arriving from all directions: A8/E80, exit 30b (Pont de l'Arc)

*For more details, see map from "Coding Location" section.

===== By Train =====

*Main train station is located in Aix en Provence city center. It's a small station where only Train from Marseille Saint Charles station come there.

*For long distance travels, look on TGV transport. There is another big station dedicated for Aix en provence. This is the best way to arrive near than Aix en provence without to pass through Marseille city.

*For more details, see map from "Coding Location" section.

==== Coding Location ====

*[http://www.paysdaixassociations.org/html/maisonasso.htm Maison des Associations Tavan, 1, Rue Emile Tavan, 13100, Aix en Provence, France]

*There is a [http://maps.google.fr/?ie=UTF8&ll=43.530044,5.441438&spn=0,0.002064&t=h&z=20&layer=c&cbll=43.530013,5.441569&panoid=tbmm3CL6WJYZX98q5R1Bxg&cbp=12,62.42,,0,13.95 Street-View link there] to see the front of Maison des Associations Tavan.

*Look [http://maps.google.com/maps/ms?ie=UTF8&msa=0&msid=107588084692678854185.000486f1fd2581b6db153&ll=43.521574,5.439992&spn=0.024708,0.044074&z=15 at this map for details of city center and neighborhood]. The "Maison des Associations Tavan" is draw over the map, and also hotel, train station, and airport.

*Look at [http://www.aixenprovencetourism.com/uk/aix-acces.htm Aix en Provence Tourism desk web site] to see all details and maps to acces on the city.

=== Participants ===

{| border="1" class="wikitable"
|-
! Photo
! Name
! Project
! Arrival
! Departure
! Travel Arrangements
! Hotel Arrangements
|-
| [http://www.digikam.org/drupal/blog/3 http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/cgilles.png]
| Gilles Caulier
| Student mentoring, digiKam Editor Canvas and Preview Widget factoring, QtScript integration.
| ''n/a''
| ''n/a''
| ''n/a''
| ''n/a''
|-
| [http://www.digikam.org/drupal/blog/8 http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/mwiesweg.png]
| Marcel Wiesweg
| Student mentoring, digiKam Face Recognition, Image Versioning and Database schema.
| 26/08/10:17h10 PM - MAR airport
| 29/08/10:17h55 PM - MAR airport
| Plane from Düsseldorf, Germany
| 1 room, 1 person, 3 nights.
|-
| http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/mghansen.png
| Michael G. Hansen
| Student mentoring, GPSSync kipi-plugin, Google maps integration
| 26/08/10:17h10 PM - MAR airport
| 29/08/10:17h55 PM - MAR airport
| Plane from Düsseldorf, Germany
| 1 room, 1 person, 3 nights.
|-
| [http://dev.exiv2.org/projects/activity?user_id=53 http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/ahuggel.png]
| Andreas Huggel
| digiKam and kipi-plugins Metadata management improvements
| 26/08/10:09h35 AM - MAR airport
| 30/08/10:18h45 PM - MAR airport
| Plane from Malaysia
| 1 room, 1 person, 4 nights.
|-
| [http://vardhman.blogspot.com http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/jaiva.png]
| Vardhman Jain
| PicasaWeb and Flickr import/export Kipi-plugins improvements
| PENDING
| PENDING
| Plane from San Francisco, USA (most like via some place)
| 1 room, 1 person, TO DEFINE.
|-
| [http://www.digikam.org/drupal/blog/149 http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/mklapetek.png]
| Martin Klapetek
| GOsC - Non-destructive image editing in digiKam Image Editor
| 25/09/10:23:05 PM - MAR Airport
| 29/09/10:13:00 PM - MAR Airport
| Plane from Czech Republic
| 1 room, 1 person, 4 nights.
|-
| [http://adityabhatt.wordpress.com http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/adityab.png]
| Aditya Bhatt
| GOsC - Face detection ; libface with digiKam
| 26/09/10:21h00 PM - MAR airport
| 30/09/10:05h00 AM - MAR airport
| Plane from India
| 1 room, 1 person, 4 nights.
|-
| [http://www.digikam.org/drupal/blog/150 http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/gvoicu.png]
| Gabriel Voicu
| GOsC - GPSSync kipi-plugins ; Advanced Search Tool in digiKam
| 26/09/10:21h00 PM Aix
| 30/09/10:05h00 AM Aix
| Bus from Roumania - B&B hotel
| 1 room, 2 persons, 4 nights.
|-
| [http://kunalghosh.wordpress.com http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/kunalghosh.png]
| Kunal Ghosh
| GOsC - QtScript Integration in digikam
| PENDING
| PENDING
| Plane from India
| 1 room, 1 person, TO DEFINE
|}

There is also an Open-Office spreadsheet with [http://websvn.kde.org/trunk/extragear/graphics/kipi-plugins/project/CodingSprint2010.ods?view=log private information] about event contributors (e-mail, phone number, travel costs, etc...).

=== Preparation ===

==== To bring ====

*Wifi will be available at Maison des Associations Tavan. For non-wifi computers plan a Network gateway and ethernet cables.
*Plan a video-projector.
*Digital Still Camera (of course).
*Tea and coffee for working hours.

==== To book ====

*Food for Mid-day lunch. There is a nice garden between "Maison des Associations Tavan" and "Beaux Arts" school.
*Restaurant for 28 august, Saturday evening.

=== Common Topics for Discussion and Coding ===

*Geo-location
**[http://community.kde.org/Digikam/GSoC2010/ReverseGeocoding Reverse Geo-coding] ([https://bugs.kde.org/show_bug.cgi?id=150981 BKO #150981] and [https://bugs.kde.org/show_bug.cgi?id=182110 BKO #182110]).
**OpenStreetmap ([https://bugs.kde.org/show_bug.cgi?id=206133 BKO #206133]), Wikimapia ([https://bugs.kde.org/show_bug.cgi?id=233848 BKO #233848]), Google Maps API v3 ([https://bugs.kde.org/show_bug.cgi?id=236533 BKO #236533]), Nokia Ovi.
**Share common widget to a dedicated library, suitable in digiKam and Kipi-plugins.
*Image Versioning
**[http://community.kde.org/Digikam/GSoC2010/NonDestructiveEditing Non destructive editing].
**A format to describe and store editing operations ([https://bugs.kde.org/show_bug.cgi?id=142056 BKO #142056]).
**Storage in database and metadata ([https://bugs.kde.org/show_bug.cgi?id=125387 BKO #125387]).
*Face detection
**Existing solutions / libface, feasibility of task ([https://bugs.kde.org/show_bug.cgi?id=146288 BKO #146288]).
**UI drafts for integration ([https://bugs.kde.org/show_bug.cgi?id=146337 BKO #146337]).
*Scripting Capability
**[http://community.kde.org/Digikam/SoK2010/QtScriptIntegration QT-Script integration] (based on Amarok interface).
**First implementation and test ([https://bugs.kde.org/show_bug.cgi?id=146866 BKO #146866]).
*Model / View
**CameraGui icon-view port.
**Preview and Image Editor canvas factoring.
**Complete Qt4 port everywhere. Remove Qt3 transition classes.
*Database
**Improving current implementation for MySQL.
**[http://community.kde.org/Digikam/GSoC2010/DatabaseChanges Validate new changes in schema introduced with GOsC contributions].
**Talk about the future : Postgresql support ([https://bugs.kde.org/show_bug.cgi?id=127321 BKO #127321]).
*Metadata
**XMP sidecar support for read only files ([https://bugs.kde.org/show_bug.cgi?id=220545 BKO #220545]).
**Background processing in digiKam ([https://bugs.kde.org/show_bug.cgi?id=173632 BKO #173632], [https://bugs.kde.org/show_bug.cgi?id=227814 BKO #227814], [https://bugs.kde.org/show_bug.cgi?id=222401 BKO #222401]).
**Introduce Video files support ([https://bugs.kde.org/show_bug.cgi?id=164442 BKO #164442]).
**Middle-level photo info computation and factoring ([https://bugs.kde.org/show_bug.cgi?id=180322 BKO #180322], [https://bugs.kde.org/show_bug.cgi?id=199461 BKO #199461], [https://bugs.kde.org/show_bug.cgi?id=151685 BKO #151685], [https://bugs.kde.org/show_bug.cgi?id=203733 BKO #203733], [https://bugs.kde.org/show_bug.cgi?id=198406 BKO #198406])
*Flickr and PicasaWeb tools
**Use Multithreading ([https://bugs.kde.org/show_bug.cgi?id=194811 BKO #194811]).
**Share common implementation between tools in libkipiplugins.

=== Food ===

My suggestions:

*There is many possibilities in Aix en provence town (pizza, baggels, sushi, sandwich, etc.)

*Last year in Germany we went to a restaurant for dinner Saturday evening, I enjoyed that quite much. I would suggest us we continue in this tradition this year as well. I know good and not too expensive restaurants in Aix en Provence city center.

*Anyway, let's me hear your food preferences.

 

=== Reimbursements ===

*Only travel costs and hotels can be reimbursed, through KDE-ev sponsorship. Take a look on [http://ev.kde.org/rules/reimbursement_policy.php this page to know the policy].
*The form to be reimbursed can be [http://ev.kde.org/resources/expense_report.pdf downloaded there].

=== Sponsorship ===

*http://www.digikam.org/files/images/ev_large.thumbnail.png The event will be sponsored be [http://ev.kde.org KDE-ev].
*Donations from:
**http://www.sinopictures.com/uploads/pics/logo_lo_02.gif Sino-Pictures, [http://www.sinopictures.com a photo agency from China].
**To become a sponsor, please make a donation following [http://www.digikam.org/drupal/donation this page...]

Projects/Marble/Gsoc2010

2010-06-05T14:06:33Z

Mghansen256: Link to Reverse Geocoding wiki page.

= Marble Gsoc 2010 =

== List of accepted projects ==
[http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/kde/t127230760808 Marble To Go(Navigation Mode) for KDE] by Siddharth Srivastava

[http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/kde/t127230761203 Add Bookmarking and Annotation in marble for KDE] by Gaurav Gupta

[http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/kde/t127230761986 Reverse Geocoding and Improved Map Search for KDE] by Gabriel Voicu - this project is actually for digikam. [http://community.kde.org/Digikam/GSoC2010/ReverseGeocoding There is a wiki page with more information.]

[http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/kde/t127230762558 Implementing Time Support to Marble for KDE] by Harshit Jain

Projects/Digikam/CodingSprint2010

2010-05-30T10:39:49Z

Mghansen256: Travel data for Marcel and Michael

== KDE Graphics Coding Sprint 2010 ==

*The KDE Graphics coding sprint 2010 will take place in [http://www.aixenprovencetourism.com/uk Aix en Provence, France], from August 27th to 29th. It's organized by Gilles Caulier.

http://farm5.static.flickr.com/4031/4620818767_5fb7450bc0_m.jpg

=== Location ===

==== Hotel ====

*Hotel Paul, near Aix en provence city center. Look [http://aix-en-provence.com/hotelpaul at this url for details]

*3 nights have been books to this hotel : Thursday 26/Friday 27 ; Friday 27/Saturday 28; Saturday 28/Sunday 29.
*If you want to stay more time in this hotel to visit Aix en provence, let's me hear.

*There is a [http://maps.google.fr/?ie=UTF8&t=h&layer=c&cbll=43.533328,5.445936&panoid=u7_H9GZ7Jv-Vfn-oafCRVQ&cbp=12,76.99,,1,2.48&ll=43.533217,5.445999&spn=0,0.002064&z=20 Street-View link there] to see the front of Hotel Paul.

*For more details, see map from "Coding Location" section.

==== Directions ====

===== By Plane =====

*The closest airport is Marseille/Provence International (MAR).

*There is a regional bus from Marseille airport. The fare is around €7.0. Take a look [http://www.mrsairport.com/eng/acces/acces_train+bus.jsp at this page for details.]

*Text me (Gilles) when you board the bus in Airport or when you have got lost.

*For more details, see map from "Coding Location" section.

===== By Car =====

*Arriving from all directions: A8/E80, exit 30b (Pont de l'Arc)

*For more details, see map from "Coding Location" section.

===== By Train =====

*Main train station is located in Aix en Provence city center. It's a small station where only Train from Marseille Saint Charles station come there.

*For long distance travels, look on TGV transport. There is another big station dedicated for Aix en provence. This is the best way to arrive near than Aix en provence without to pass through Marseille city.

*For more details, see map from "Coding Location" section.

==== Coding Location ====

*[http://www.paysdaixassociations.org/html/maisonasso.htm Maison des Associations Tavan, 1, Rue Emile Tavan, 13100, Aix en Provence, France]

*There is a [http://maps.google.fr/?ie=UTF8&ll=43.530044,5.441438&spn=0,0.002064&t=h&z=20&layer=c&cbll=43.530013,5.441569&panoid=tbmm3CL6WJYZX98q5R1Bxg&cbp=12,62.42,,0,13.95 Street-View link there] to see the front of Maison des Associations Tavan.

*Look [http://maps.google.com/maps/ms?ie=UTF8&msa=0&msid=107588084692678854185.000486f1fd2581b6db153&ll=43.521574,5.439992&spn=0.024708,0.044074&z=15 at this map for details of city center and neighborhood]. The "Maison des Associations Tavan" is draw over the map, and also hotel, train station, and airport.

*Look at [http://www.aixenprovencetourism.com/uk/aix-acces.htm Aix en Provence Tourism desk web site] to see all details and maps to acces on the city.

=== Participants ===

{| class="wikitable" border="1"
!Photo
!Name
!Project
!Arrival
!Departure
!Travel Arrangements
|-
|[http://www.digikam.org/drupal/blog/3 http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/cgilles.png]
|Gilles Caulier
|Student mentoring, digiKam Editor Canvas and Preview Widget factoring, QtScript integration.
|''n/a''
|''n/a''
|''n/a''
|-
|[http://www.digikam.org/drupal/blog/8 http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/mwiesweg.png]
|Marcel Wiesweg
|Student mentoring, digiKam Face Recognition, Image Versioning and Database schema.
|26/08/10:17h10 - MAR airport
|29/08/10:17h55 - MAR airport
|Plane from Düsseldorf, Germany
|-
|http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/mghansen.png
|Michael G. Hansen
|Student mentoring, GPSSync kipi-plugin, Google maps integration
|26/08/10:17h10 - MAR airport
|29/08/10:17h55 - MAR airport
|Plane from Düsseldorf, Germany
|-
|[http://dev.exiv2.org/projects/activity?user_id=53 http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/ahuggel.png]
|Andreas Huggel
|digiKam and kipi-plugins Metadata management improvements
|pending
|pending
|Plane from Malaysia - MAR airport
|-
|[http://vardhman.blogspot.com http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/jaiva.png]
|Vardhman Jain
|PicasaWeb and Flickr import/export Kipi-plugins improvements
|pending
|pending
|Plane from San Francisco - MAR airport (most like via some place)
|-
|[http://www.digikam.org/drupal/blog/149 http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/mklapetek.png]
|Martin Klapetek
|GOsC - Non-destructive image editing in digiKam Image Editor
|pending
|pending
|Plane from Czech Republic - MAR airport
|-
|[http://adityabhatt.wordpress.com http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/adityab.png]
|Aditya Bhatt
|GOsC - Face detection ; libface with digiKam
|26/09/10:21h00 - MAR airport
|30/09/10:05h00 - MAR airport
|Plane from India
|-
|[http://www.digikam.org/drupal/blog/150 http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/gvoicu.png]
|Gabriel Voicu
|GOsC - GPSSync kipi-plugins ; Advanced Search Tool in digiKam
|26/09/10:21h00 Aix
|30/09/10:05h00 Aix
|Bus from Roumania
|-
|[http://kunalghosh.wordpress.com http://websvn.kde.org/*checkout*/trunk/www/sites/planet/website/hackergotchi/kunalghosh.png]
|Kunal Ghosh
|GOsC - QtScript Integration in digikam
|pending
|pending
|Plane from India - MAR airport
|-
|}

=== Preparation ===

==== To bring ====

* Notebook
* Wifi will be available at Maison des Associations Tavan
* Network gateway and ethernet cables
* Plan a video-projector
* Digital Still Camera (of course)

==== To book ====

* Restaurant for 28 august, Saturday evening

=== Common Topics for Discussion and Coding ===

*Geo-location
** [http://community.kde.org/Digikam/GSoC2010/ReverseGeocoding Reverse Geo-coding] ([https://bugs.kde.org/show_bug.cgi?id=150981 BKO #150981] and [https://bugs.kde.org/show_bug.cgi?id=182110 BKO #182110]).
** OpenStreetmap ([https://bugs.kde.org/show_bug.cgi?id=206133 BKO #206133]), Wikimapia ([https://bugs.kde.org/show_bug.cgi?id=233848 BKO #233848]), Google Maps API v3 ([https://bugs.kde.org/show_bug.cgi?id=236533 BKO #236533]), Nokia Ovi.
** Share common widget to a dedicated library, suitable in digiKam and Kipi-plugins.
* Image Versioning
** [http://community.kde.org/Digikam/GSoC2010/NonDestructiveEditing Non destructive editing].
** A format to describe and store editing operations ([https://bugs.kde.org/show_bug.cgi?id=142056 BKO #142056]).
** Storage in database and metadata ([https://bugs.kde.org/show_bug.cgi?id=125387 BKO #125387]).
*Face detection
** Existing solutions / libface, feasibility of task ([https://bugs.kde.org/show_bug.cgi?id=146288 BKO #146288]).
** UI drafts for integration ([https://bugs.kde.org/show_bug.cgi?id=146337 BKO #146337]).
*Scripting Capability
** [http://community.kde.org/Digikam/SoK2010/QtScriptIntegration QT-Script integration] (based on Amarok interface).
** First implementation and test ([https://bugs.kde.org/show_bug.cgi?id=146866 BKO #146866]).
*Model / View
** CameraGui icon-view port.
** Preview and Image Editor canvas factoring.
** Complete Qt4 port everywhere. Remove Qt3 transition classes.
*Database
** Improving current implementation for MySQL.
** [http://community.kde.org/Digikam/GSoC2010/DatabaseChanges Validate new changes in schema introduced with GOsC contributions].
** Talk about the future : Postgresql support ([https://bugs.kde.org/show_bug.cgi?id=127321 BKO #127321]).
*Metadata
** XMP sidecar support for read only files ([https://bugs.kde.org/show_bug.cgi?id=220545 BKO #220545]).
** Background processing in digiKam ([https://bugs.kde.org/show_bug.cgi?id=173632 BKO #173632]).
** Introduce Video files support ([https://bugs.kde.org/show_bug.cgi?id=164442 BKO #164442]).
*Flickr and PicasaWeb tools
** Use Multithreading ([https://bugs.kde.org/show_bug.cgi?id=194811 BKO #194811]).
** Share common implementation between tools in libkipiplugins.

=== Food ===

My suggestions:
*There is many possibilities in Aix en provence town (pizza, baggels, sushi, sandwich, etc.)

*Last year in Germany we went to a restaurant for dinner Saturday evening, I enjoyed that quite much. I would suggest us we continue in this tradition this year as well. I know good and not too expensive restaurants in Aix en Provence city center.

*Anyway, let's me hear your food preferences.

=== Reimbursements ===

*The event will be sponsored be [http://ev.kde.org KDE-ev].
*Only travel costs and hotels will be reimbursed. Take a look on [http://ev.kde.org/rules/reimbursement_policy.php this page to know the policy].
*The form to be reimbursed can be [http://ev.kde.org/resources/expense_report.pdf downloaded there].

Projects/Marble/MarbleUsedBy

2010-04-23T17:14:56Z

Mghansen256: Add digiKam

==Examples of applications that are making use of the Marble library==

===Distributions===

====Chakra-LiveCD====

Screenshot

[[Image:Tribemarble512.png]]

Description: Marble is integrated to configure Locale & Time inside the Installer of the Chakra Live-CD distribution.

Website: http://chakra-project.org

E-Mail: l.appelhans@gmx.de

===Applications===
====Mumoro====

Screenshot: http://tristramg.eu/multimod.png

Description: Mumoro is a library to compute multimodal paths. The marble widget is used to display the route.

Website: http://github.com/Tristramg/mumoro

E-Mail: tristramg at gmail dot com

==== Cockpit ====
[[Image:Cockpit-with-marble.png|521px|thumb|Visualization of GPS and video data in the Cockpit application.]]
Description: Cockpit is an application for the visualization of sensor data and assistance functions of cognitive systems. The screenshot shows the usage of Marble to visualize the position of the vehicle (orange, GPS position mapped to the nearest road). The camera field of view shown in green in Marble corresponds to the video image on the left. Speed limit signs recognizedin the video are shown in Marble. Marble is also used to seek through sensor data (i.e. clicking on some point in the map seeks the video to the closest position). 
E-Mail: nienhues at fzi dot de

==== Tonatiuh ====
Description: The Tonatiuh project aims to create an open source, cutting-edge, accurate, and easy to use Monte Carlo ray tracer for the optical simulation of solar concentrating systems. It intends to advance the state-of-the-art of the simulation tools available for the design and analysis of solar concentrating systems, and to make those tools freely available to anyone interested in using and improving them. [Source: Tonatiuh website] 
Website: http://code.google.com/p/tonatiuh/

==== fgdash ( Flight Gear Dash ) ====
Description: fgdash is designed to be the next step in flight gear map viewers. It's design is to work simply and effectively as an embedded secondary system while flying. Currently undergoing heavy development. Website: : http://github.com/paultag/fgdash

==== digiKam ====
[[Image:Digikam_using_Marble.png|521px|thumb|Map search in digiKam powered by Marble.]]
Description: digiKam is an advanced digital photo management application for Linux, Windows, and Mac-OSX. It has an integrated map search which allows you to search for your geotagged images and view their positions.

Website: http://www.digikam.org

===Plugins===
====geoshape (Koffice2)====
[[image:Geoshape-simple.png|600px|thumb|alt Marble embedded in KPresenter]]
Description: geoshape is a so called shape, a plugin that can be used in (nearly) any Koffice2 application, like KWord, KPresenter and so on. At the moment it is limited to displaying a simple map, like they can be seen in Marble. Features like displaying adresses from a spreadsheet might follow later but are nowhere near implemented. 
More information: [[Projects/KOffice/Geoshape|geoshape project page]]

File:Digikam using Marble.png

2010-04-23T17:11:49Z

Mghansen256: The map search in Digikam allows you to search for geotagged pictures and uses Marble to show the positions of your images.

The map search in Digikam allows you to search for geotagged pictures and uses Marble to show the positions of your images.

Talk:Development/Tutorials/Localization/i18n

2010-01-10T17:02:05Z

Mghansen256: Question about i18np

I wrote a short I18n text for Flock/Mozilla devs - maybe it'll help you a bit - http://wiki.flock.com/index.php?title=I18n_Flock
-- gandalf

thanks, i used a few of the interesting stats you collected there
-- aseigo

Concerning the 'Plural' section:
Should it not be
i18np("%1 file was deleted", "%1 files were deleted", numFilesDeleted);
because otherwise the singular form can not be used for values like 21,31,etc?
-- mghansen256

Projects/Digikam/CodingSprint2009-summary

2009-11-19T15:05:36Z

Mghansen256: Missing space and downgrade from face recognition to region tagging

The developers of digiKam and the Kipi project came together in Essen, Germany on November 13-15 for the second coding sprint for KDE photography applications. With digiKam preparing for the 1.0 release shortly before Christmas, plans were discussed and work began already in feature branches for the following release. A lot of work was put into polishing Windows support, with collaborative testing and bug fixing. The developers of Kamoso took the opportunity to bring Kipi support to their application. A lot of discussion was centered around a future architecture for Kipi plugins for syncing with web services and how Akonadi could help in this context.

http://farm3.static.flickr.com/2602/4104932135_3cb3f69536_m.jpg

digiKam developer Gilles Caulier hacked with Kåre Särs on the Acquire Images Kipi plugin and found some problems with the libksane Twain implementation.
Working on cross-platform support, he reported a lot of problems with digiKam on Windows to Patrick Spendrin, who immediately went to fix them, shared his experience to compile digiKam under MinGW and MSVC, and tested compilation under Mac OS X on Kåre's borrowed MacBook Air. Some problems in the liblqr library are waiting to be fixed.

http://farm3.static.flickr.com/2624/4112660504_f043577c72_m.jpg

In discussions with Luka Renko, Alex Fiestas and Aleix Pol plans for a common codebase for all import/export Kipi plugins were drafted. The Kipi interface was extended with a new way to export a whole collection using default settings and not starting a dialog.

http://farm3.static.flickr.com/2677/4105703894_93aa13a157_m.jpg

Gilles and Marcel Wiesweg shared initial thoughts about future image versioning support in digiKam and wishes to support grouping of pictures, Gilles and Andi Clemens discussed how to refactor all the preview widgets in digiKam, which are still based on Qt3 support classes and wait for a pure Qt4 port. Features were reviewed and a paper created in SVN.

http://farm3.static.flickr.com/2697/4105692984_057c594d9c_m.jpg

With Michael G. Hansen, Gilles talked about face recognition and tagging of regions in an image. Here as well a proposal paper was created listing leading ideas. Improvements in the camera interface and supporting KDE notification for downloads were discussed.

http://farm3.static.flickr.com/2627/4104946465_95cedd5cd7_m.jpg

When not busy with coding and discussing, he tried to walk around inconspicuously with his camera to take photos of working hackers. But not only to personal pleasure, Gilles used these photos to perform in-deep testing of digiKam's RAW file import tool and revealing some problems. At last, Gilles started to write a new HDR creator plugin based on Qtpfsgui, but code is still under construction.

http://farm3.static.flickr.com/2577/4105716638_9028bb4153_m.jpg

Alex and Aleix, Kamoso developers, adapted the Kipi Plugins architecture to Kamoso, it was changed to provide better communication between the plugins and the host application. Done that, they ported Kamoso to use Kipi, that way Kamoso will be able to take advantage of the whole architecture (and hopefully more people in the future). Also they started the port of the youtube plugin to Kipi so at some point in the near future it will be possible to use it with the rest of Kipi applications.

http://farm3.static.flickr.com/2645/4104942389_5aa3ae14cd_m.jpg

Besides the usual amount of bug hunting and fixing, Kåre, who is author of libksane, moved all the scan operations to separate threads to improve the scanning performance and to improve the responsiveness of the GUI. At the same time he cleaned up the logic a bit to make it easier to follow and implemented small GUI enhancements.

http://farm3.static.flickr.com/2670/4106816151_d6762945a6_m.jpg

Holger Foerster, working on MySQL support for digiKam, brought his feature branch up to date again and, working with Marcel, ensured it is usable as well with the traditional SQLite database. MySQL support marks the start for a multi user digiKam application and other features in future.

http://farm3.static.flickr.com/2537/4104948001_1230c91859_m.jpg

Functionality was tested and bugs fixed. For data conversion between the supported databases, development of a dialog was started where the user can copy the data from one database to another.

http://farm3.static.flickr.com/2682/4105715438_61579fcb67_m.jpg

Guillaume Paumier's main goal was to start working on an export plugin to Wikimedia Commons. By analyzing how the existing Facebook KIPI plugin was made, he was able to create the basis of the communication layer between the plugin and a MediaWiki site, even though not having done any C++/Qt development before. While the current work focuses on a specific wiki (Wikimedia Commons), it could be later extended to a more general MediaWiki library for Qt.

http://farm3.static.flickr.com/2523/4104934891_2f61158455_m.jpg

Tom Albers, Akonadi and Mailody developer, joined in to give a talk and first-hand advice about Akonadi. He worked on an Akonadi resource for images and tried to convince the participating developers about utilizing Akonadi within Digikam. At the end of the meeting, the resource was able to succesfully and recursively list images in a folder and show their thumbnails.

http://farm3.static.flickr.com/2509/4106821429_145c5dc3bf_m.jpg

Johannes Wienke started porting the remaining substantial bits of code in digiKam still based on Q3Support view classes to the Qt model-view concept. At the sprint he started with the left side bar
widgets. Porting the views there, and later the ones for the right side bar and other widgets, includes structural improvements and code simplifications.

http://farm3.static.flickr.com/2593/4105707132_bf43dc25c1_m.jpg

Luka started refactoring of KIPI Facebook Import/Export dialog by integrating all progress dialogs into main dialog. This work will continue in direction of a common UI look and feel for all import/export dialogs in KIPI. Guillaume's new Wikimedia plugin will be based on the
new UI design agreed on during the sprint. Luka also dived into Akonadi resources and KFacebook library: the plan is to extend them to provide virtual albums for Facebook through Akonadi.

http://farm3.static.flickr.com/2742/4105701938_d25db886e5_m.jpg

Michael worked on two areas: geolocation and region tagging.
Michael discussed plans for a more generic geolocation-widget with Marcel and talked about nice-to-have features for better Marble integration with SaroEngels. As already said above, he discussed plans for tagging certain regions of an image as known from popular web services, and how to store such information in image metadata.

http://farm3.static.flickr.com/2592/4107584246_5f1b2b5065_m.jpg

Andi set up a KDE build environment for Windows to finally be able to hunt bugs on the Microsoft platform as well, then took a look at some windows bugs with Patrick. This took some time, so unfortunately time was getting short for talking with Gilles and working on the new image editor layout and widgets planned for digiKam post-1.0. He fixed some bugs in AdvancedRename utility to make it work under Windows, appearing pretty much broken on MS in the current state.

http://farm3.static.flickr.com/2547/4105709488_b341b5eb0a_m.jpg

Marcel organized and hosted the whole event and is now happy that no severe complications arised (only Gilles being rejected to take his intended flight, but arriving the next morning, and Pieter Edelman missing the event due to a flu), and happy that everyone hopefully enjoyed the meeting. On Friday and Sunday he was concerned with picking up and bringing people from and to airport and train station. When started with coding, he worked with Johannes to point to all the code locations needing a model-view port, with Holger to round up the work on MySQL support, and discussed with Michael about geolocation in digiKam, its present problems and ideas for the future. The image metadata library in kdegraphics, libkexiv2, got one long-standing important bug fix requiring extensive changes, some cleanup, and support for accessing embedded previews for KDE 4.4.

Note: All event photos are available on Flickr group given below:

http://www.flickr.com/groups/kde-imaging-codingsprint/pool

Projects/Digikam/CodingSprint2009

2009-11-11T18:11:39Z

Mghansen256:

== KDE Graphics Coding Sprint 2009 ==

The KDE Graphics coding sprint 2009 will take place in Essen, Germany, from November 13th to 15th.

=== Location ===

==== Hotel ====

[http://www.hotel-schoenberger.de/ Hotel Schönberger]
 Laupendahler Weg 18
 42579 Heiligenhaus

==== Directions ====

===== By Plane =====

The closest airport is Düsseldorf International.

There is a regional train from Düsseldorf airport. Go to "Bahnhof Düsseldorf Flughafen Terminal S" which is ''not'' the main train station of the airport ("Bahnhof Düsseldorf Flughafen"). From there, take the S7 direction Solingen. Get off after five minutes in Düsseldorf-Derendorf. From platform 2, take the S6 direction Essen Hbf. Get off at Werden S. The fare is €4.50 ("B").
Text me (Marcel) when you board the train in Derendorf or when you have got lost.

===== By Car =====

* Arriving from the West: A52, exit Essen-Kettwig
* Arriving from the East: A40, change to A52 at Kreuz Essen-Ost, exit the A52 at Rüttenscheid.

From either exit, follow the signs to Werden and Velbert. You will cross southbound the river Ruhr entering the little town of Werden. Follow the main route (B224) staying on the right hand lane. You will pass the basilica, then 1.5km further on you will pass an "Aral" petrol station on the left side. Turn left on the next junction into Fischlaker Straße (turn left before passing the traffic light!). Follow the Fischlaker Straße for 600m, then take the slight left fork into Bernhardstraße. It's house number 12, third on the right side.

===== By Train =====

Main train station is Essen Hauptbahnhof.
From there
*take either express bus SB 19 from Hauptbahnhof (number 7 on [http://efa.vrr.de/download/envmaps/vrr/EHB_Plan_Umbau%20Bussteige_und_Wege.pdf this map]) and get off at the stop "Am Schwarzen".
*or go to platform 12, take the regional train S6 Köln-Nippes. Get off at Werden S.
For either choice the fare is €2.30 ("A2").
Text me (Marcel) when you board the bus or the train to be picked up.

Information about local bus or train schedules is available [http://efa.vrr.de/ here].

==== Coding Location ====

[http://maps.google.de/maps?f=q&source=s_q&hl=de&geocode=&q=Bernhardstra%C3%9Fe+12,+Essen&sll=51.392833,7.024748&sspn=0.006494,0.019119&ie=UTF8&hq=&hnear=Bernhardstra%C3%9Fe+12,+Fischlaken+45239+Essen,+Nordrhein-Westfalen&ll=51.391681,7.026787&spn=0.006494,0.019119&z=16 Bernhardstr. 12, Essen, Germany]

=== Participants ===

{| class="wikitable" border="1"
!Name
!Project
!Arrival
!Travel Arrangements
|-
|Gilles Caulier
|digiKam
|Th night
|DUS, arrival arranged
|-
|Marcel Wiesweg
|digiKam
|''n/a''
|''n/a''
|-
|Andi Clemens
|digiKam
|Fr evening
|car
|-
|Kåre Särs
|ksane
|Fr morning
|DUS, arrival arranged
|-
|Patrick Spendrin
|Marble, KDE/Win
|Th evening
|train
|-
|Luka Renko
|Kipi Plugins
|Th evening
|DUS, arrival arranged
|-
|Pieter Edelman
|digiKam (new contributor)
|Fr morning
|
|-
|Michael G. Hansen
|digiKam (new contributor)
|Fr morning
|car
|-
|Holger Förster
|digiKam (MySQL database backend)
|Fr evening
|train
|-
|Johannes Wienke
|digiKam (new contributor)
|Fr evening
|train
|-
|Guillaume Paumier
|[[commons:User:Guillom/KIPI|KIPI plugin]] (new contributor)
|Th evening
|DUS, arrival arranged
|-
!colspan=4|Special guests:
|-
|Tom Albers
|Mailody and Akonadi developer, giving a presentation about Akonadi
|Saturday
|car
|}
=== Preparation ===

==== To bring ====

* notebook
* network cable

Experience shows that wireless usually breaks down at the beginning of a coding sprint, so ethernet is preferred and we need a
* network hub or switch
** Michael: I will bring two hubs, five ports+uplink each (in spite of 5/5+uplink in my e-mail) and also power extension cords with multiple outlets (at least one 5 port and one 8 port).
** Pieter: router giving three extra ports, old 10MBit 8-port switch
** Luka: I can bring 8-port 1GBit Ethernet switch if needed. Let me know.

=== Common Topics for Discussion and Coding ===

*Marble
** Clustering
** Geo-view: icon view with a map in background?
** OpenStreetmap, Nokia Ovi, Google Maps API v3
*Model / View
** Introduction to the concept?, sharing experience
** Current status in digikam
** porting for 1.1
*Color Management
** ksane + digikam: sharing experience & code?
*MySQL
** Current status of branch
** Merge with HEAD
** Test, make it work
*libkexiv2 - API changes
**[https://bugs.kde.org/show_bug.cgi?id=175224 bug 183171]
**[http://www.exiv2.org/doc/classExiv2_1_1PreviewManager.html Exiv2::PreviewManager]
*Image Versioning
** use cases
** a format to describe and store editing operations
** storage in database and metadata
*Face detection
** existing solutions / libraries, feasibility of task
** UI drafts for integration
*Kipi interface improvements
**Album actions - [https://bugs.kde.org/show_bug.cgi?id=175224 bug 175224]
**Tagging downloaded photos with web IDs - [https://bugs.kde.org/show_bug.cgi?id=181863 bug 181863]
**Load kipi-plugins on demand - [http://mail.kde.org/pipermail/kde-imaging/2009-April/008528.html idea from Aurélien]
**Simplified export API - see [http://mail.kde.org/pipermail/kde-imaging/2009-September/009682.html Kamoso requirements]
*Akonadi and cached web album collections
**Tom Albers joins us Saturday to give a talk about Akonadi and get us on the right track regarding Akonadi support
**[http://mail.kde.org/pipermail/kde-imaging/2008-October/007127.html Colin's proposal]
**[https://bugs.kde.org/show_bug.cgi?id=199848 bug 199848]

=== Food ===

My suggestions:
* semi-self-made Pizza for Friday evening
* Spaghetti for lunch Saturday

Last year in Genoa we went to a restaurant for dinner Saturday evening, I enjoyed that quite much. I would suggest we continue in this tradition this year as well.

Projects/Digikam/CodingSprint2009

2009-10-30T17:46:09Z

Mghansen256: I'm bringing two network hubs

== KDE Graphics Coding Sprint 2009 ==

The KDE Graphics coding sprint 2009 will take place in Essen, Germany, from November 13th to 15th.

=== Location ===

==== Hotel ====

[http://www.hotel-schoenberger.de/ Hotel Schönberger]
 Laupendahler Weg 18
 42579 Heiligenhaus

==== Directions ====

===== By Plane =====

The closest airport is Düsseldorf International.

There is a regional train from Düsseldorf airport. Go to "Bahnhof Düsseldorf Flughafen Terminal S" which is ''not'' the main train station of the airport ("Bahnhof Düsseldorf Flughafen"). From there, take the S7 direction Solingen. Get off after five minutes in Düsseldorf-Derendorf. From platform 2, take the S6 direction Essen Hbf. Get off at Werden S. The fare is €4.50 ("B").
Text me (Marcel) when you board the train in Derendorf or when you have got lost.

===== By Car =====
Get your route from Google Maps
*A52, exit Essen-Kettwig
*A40

===== By Train =====

Main train station is Essen Hauptbahnhof.
From there
*take either express bus SB 19 from Hauptbahnhof (number 7 on [http://efa.vrr.de/download/envmaps/vrr/EHB_Plan_Umbau%20Bussteige_und_Wege.pdf this map]) and get off at the stop "Am Schwarzen".
*or go to platform 12, take the regional train S6 Köln-Nippes. Get off at Werden S.
For either choice the fare is €2.30 ("A2").
Text me (Marcel) when you board the bus or the train to be picked up.

Information about local bus or train schedules is available [http://efa.vrr.de/ here].

==== Coding Location ====

[http://maps.google.de/maps?f=q&source=s_q&hl=de&geocode=&q=Bernhardstra%C3%9Fe+12,+Essen&sll=51.392833,7.024748&sspn=0.006494,0.019119&ie=UTF8&hq=&hnear=Bernhardstra%C3%9Fe+12,+Fischlaken+45239+Essen,+Nordrhein-Westfalen&ll=51.391681,7.026787&spn=0.006494,0.019119&z=16 Bernhardstr. 12, Essen, Germany]

=== Participants ===

{| class="wikitable" border="1"
!Name
!Project
!Arrival
!Travel Arrangements
|-
|Gilles Caulier
|digiKam
|Th night
|DUS, arrival arranged
|-
|Marcel Wiesweg
|digiKam
|''n/a''
|''n/a''
|-
|Andi Clemens
|digiKam
|Fr evening
|car
|-
|Kåre Särs
|ksane
|Fr morning
|DUS
|-
|Patrick Spendrin
|Marble, KDE/Win
|Th evening
|train
|-
|Luka Renko
|Kipi Plugins
|Th evening
|DUS, arrival arranged
|-
|Pieter Edelman
|digiKam (new contributor)
|Fr morning
|
|-
|Michael G. Hansen
|digiKam (new contributor)
|Fr morning
|
|-
|Holger Förster
|digiKam (MySQL database backend)
|Fr evening
|train
|-
|Johannes Wienke
|digiKam (new contributor)
|Fr evening
|train
|-
|Guillaume Paumier
|[[commons:User:Guillom/KIPI|KIPI plugin]] (new contributor)
|Th evening
|DUS, arrival arranged
|}

=== Preparation ===

==== To bring ====

* notebook
* network cable

Experience shows that wireless usually breaks down at the beginning of a coding sprint, so ethernet is preferred and we need a
* network hub or switch
Would be great if someone could bring one.
Michael: I will bring two hubs, five ports+uplink each (in spite of 5/5+uplink in my e-mail) and also power extension cords with multiple outlets (at least one 5 port and one 8 port).

=== Common Topics for Discussion and Coding ===

*Marble
** Clustering
** Geo-view: icon view with a map in background?
** OpenStreetmap, Nokia Ovi, Google Maps API v3
*Model / View
** Introduction to the concept?, sharing experience
** Current status in digikam
** porting for 1.1
*Color Management
** ksane + digikam: sharing experience & code?
*MySQL
** Current status of branch
** Merge with HEAD
** Test, make it work
*Image Versioning
** ideas and drafts
*Face detection
** existing solutions / libraries, feasibility of task
** UI drafts for integration
*Kipi interface improvements
**Album actions - [https://bugs.kde.org/show_bug.cgi?id=175224 bug 175224]
**Tagging downloaded photos with web IDs - [https://bugs.kde.org/show_bug.cgi?id=181863 bug 181863]
**Load kipi-plugins on demand - [http://mail.kde.org/pipermail/kde-imaging/2009-April/008528.html idea from Aurélien]
**Simplified export API - see [http://mail.kde.org/pipermail/kde-imaging/2009-September/009682.html Kamoso requirements]
*Akonadi and cached web album collections
**[http://mail.kde.org/pipermail/kde-imaging/2008-October/007127.html Colin's proposal]
**[https://bugs.kde.org/show_bug.cgi?id=199848 bug 199848]

=== Food ===

Very important topic ;-)
We can do some cooking. My suggestion is semi-self-made Pizza for Friday evening and Spaghetti for lunch Saturday and Sunday. Add any objections or wishes here in the wiki.

Last year in Genoa we went to a restaurant for dinner Saturday evening, I enjoyed that quite much. I would suggest we continue in this tradition this year as well.