KDE TechBase - Recent changes [en]

Projects/rekonq/Roadmap

2009-11-20T21:21:23Z

← Older revision		Revision as of 21:21, 20 November 2009
Line 15:		Line 15:
	\|-		\|-
	\|Porting to KDEWebKit		\|Porting to KDEWebKit
-	\| rekonq 0.3.10	+	\| rekonq 0.3.10, branch is [http://www.gitorious.org/rekonq/mainline/commits/kderekonq here]
	\|style="background-color:green;" \| DONE		\|style="background-color:green;" \| DONE
	\|adjam		\|adjam
Line 25:		Line 25:
	\|-		\|-
	\|KWallet Support		\|KWallet Support
-	\|	+	\|First code can be found in this [http://www.gitorious.org/rekonq/mainline/commits/KWallet branch]
	\|style="background-color:red;" \| TODO		\|style="background-color:red;" \| TODO
	\|adjam, drf, jonas		\|adjam, drf, jonas

Projects/PIM/Akonadi/Meeting2009-10

2009-11-20T19:50:14Z

Add my meeting notes, only one month late.

← Older revision		Revision as of 19:50, 20 November 2009
Line 220:		Line 220:
	=== Porting status / release planning / app/runtime split ===		=== Porting status / release planning / app/runtime split ===

-	~~TODO~~: ~~Thomas~~	+	*KOrganizer: Not ready for KDE 4.4
		+	*Akonadi OpenSync, KitchenSync: Move to playground for KDE 4.4
		+	*Akonadi SyncML Client Resource: Can be moved to trunk for KDE 4.4
		+	*KJots rewrite: Can be merged for KDE 4.4
		+	*KResource bridges: Using the old KResource API with the bridges causes some problems, thus all applications should be ported to the new Akonadi Contacts API
		+	*KMailCVT: Porting to Akonadi is probably easy. We should get rid of the D-Bus interface to KMail and make it use Akonadi nativly. Target is KDE 4.5. In general, we want to remove all D-Bus controlled stuff and replace it with native Akonadi calls.
		+	*KNotes: Will be replaced by KJots in the future
		+	*KResources: Some KResources which have native Akonadi replacement can be removed. Others however are public API because they are in kdepimlibs
		+	*Wizards: The idea is to use wizards with Kross scripting, so that custom providers can be added easily. That could even be integrated with KNewstuff. Volker has a prototype for this, just missing the servertest stuff.
		+	*Akonadi KCM: Remove for KDE 4.4, not useful for most users, just confusing
		+
		+	Tom blogged about this [http://www.omat.nl/2009/10/17/akonadi-meeting-day-1-discussions-api-review/ here].

	=== Akonadi/Nepomuk/Search and the future ===		=== Akonadi/Nepomuk/Search and the future ===

Getting Started/Build/KDE4/FreeBSD

2009-11-20T19:33:05Z

Required Ports: Remove useless comments

← Older revision		Revision as of 19:33, 20 November 2009
Line 6:		Line 6:
	* devel/dbus		* devel/dbus
	* devel/cmake		* devel/cmake
-	* x11/xorg ~~(Presumably you could do with less... but I haven't done that yet)~~	+	* x11/xorg
	* devel/subversion		* devel/subversion
	* textproc/redland (for support/soprano)		* textproc/redland (for support/soprano)
Line 16:		Line 16:
	* shells/bash (if using kdesvn-build)		* shells/bash (if using kdesvn-build)
	* textproc/libxslt		* textproc/libxslt
-	* (expand as needed, this is a wiki :)

	==Differences from the normal build process==		==Differences from the normal build process==

Projects/KDE on FreeBSD

2009-11-20T19:31:49Z

KDE on FreeBSD: KDE on FreeBSD isn't "very buggy" anymore

← Older revision		Revision as of 19:31, 20 November 2009
Line 8:		Line 8:

	The [http://freebsd.kde.org/ KDE on FreeBSD] website is supposed to be the definitive source of information.		The [http://freebsd.kde.org/ KDE on FreeBSD] website is supposed to be the definitive source of information.
-
-	~~KDE4 builds on FreeBSD, but is still very buggy (if Konsole is all you need, it is fine).~~

	This wiki page will be used to collect compilation hints, debugging tips, etc. Additional information can be found on the [http://wiki.freebsd.org/KDE4 FreeBSD KDE4 Wiki].		This wiki page will be used to collect compilation hints, debugging tips, etc. Additional information can be found on the [http://wiki.freebsd.org/KDE4 FreeBSD KDE4 Wiki].

Getting Started/Build/KDE4/Kubuntu and Debian

2009-11-20T17:33:26Z

My bad, fluffed the XMMS repository link.

← Older revision		Revision as of 17:33, 20 November 2009
(One intermediate revision not shown)
Line 40:		Line 40:
	libpoppler-qt4-dev libspectre-dev		libpoppler-qt4-dev libspectre-dev
	</code>		</code>
		+
		+	Also, 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].

Development/Tutorials (zh TW)

2009-11-20T16:59:47Z

← Older revision		Revision as of 16:59, 20 November 2009
Line 144:		Line 144:
	:''Simple demonstration on how to extend you application menus to execute script files.''		:''Simple demonstration on how to extend you application menus to execute script files.''

-	{{:KOffice/Plugin Tutorials}}	+	=== KOffice 外掛教學 ===
		+
		+	; [[Development/Tutorials/KOffice Overview\|KOffice 】概觀]]
		+	:''This document shows an overview of the different KOffice plugin types and tells you what each of their purpose and strengths are.'' If you are new with KOffice plugins, this is the place to start.
		+
		+	; [[Development/Tutorials/Write a Flake Plugin\|Creating KOffice Flake Plugins]]
		+	:''This tutorial shows you how you can build a plugin for KOffice applications to allow you embed content in ODF documents using Flake.''
		+
		+	; [[Development/Tutorials/KWord Scripting\|KWord 腳本]]
		+	:''This tutorial shows how to script KWord with Python, Ruby or JavaScript using Kross.''
		+
		+	; [[Development/Tutorials/KSpread Scripting\|KSpread 腳本]]
		+	:''This tutorial shows how to script KSpread with Python, Ruby or JavaScript using Kross.''
		+
		+	; [[Development/Tutorials/Krita Scripting\|Krita 腳本]]
		+	:''This tutorial shows how to script Krita with Python, Ruby or JavaScript using Kross.''
		+

	=== SuperKaramba ===		=== SuperKaramba ===

Projects/Tellico/Compiling

2009-11-20T16:58:01Z

Move Tellico compilation page from userbase

New page

= Download Tellico =

To compile [[Projects/Tellico|Tellico]] from the source code, you must [http://tellico-project.org/download download the source package] or get the code from the KDE extragear/office SVN module.

== Source Package ==
If you download the source package, extract all of the files, which should create a directory named ''tellico-2.0/''.
<code>
% tar xjvf tellico-2.0.tar.bz2
% cd tellico-2.0
</code>

{{Note|These instructions use Tellico 2.0 as an example. For other versions, replace 2.0 in the commands below.}}

== Current Development Source ==
Like all KDE applications, the source code is stored in KDE's Subversion system, in the ''extragear/office'' folder. Please refer to [[Getting_Started/Sources/Using_Subversion_with_KDE|the Subversion tutorial for KDE]].
<code>
% svn co svn://anonsvn.kde.org/home/kde/trunk/extragear/office/tellico
% cd tellico
</code>

After that, there are three steps to build and install Tellico.

= Configure =

The compilation environment must be configured to your system first. The tool used to create the configuration is ''[http://www.cmake.org CMake]''. CMake will check that you have all the required development libraries and set up the files for compiling.

In the ''tellico-2.0/'' directory, create a directory for building, named ''build/'', just to keep things clear.
<code>
% mkdir build
% cd build
% cmake .. -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix`
</code>

{{Note|Note the backquotes in the cmake command, they are important.}}

The tells CMake to use the top-level ''tellico-2.0/'' directory as the source directory, and to set the application to install in the same place as other KDE applications. Later, when you install Tellico, you will likely need root access, either through the root password or ''sudo''. To install to a different
location, use change the ''-DCMAKE_INSTALL_PREFIX'' option. Remember, the ''KDEDIRS'' variable must be updated if you install in a nonstandard location.

If you do not have the necessary libraries for building tellico, CMake will fail and show you an error, listing which libraries you lack. Some libraries are required for building. Some are optional for additional functionality. The library packages may have different names, depending on your distribution.

==Options==
In order to include support for using a webcam to scan barcodes, you must have the libv4l library installed and include ''-DENABLE_WEBCAM=true'' when you run cmake.

To include support for debugging Tellico, you should pass the ''-DCMAKE_BUILD_TYPE=debug'' option to cmake. ''-DCMAKE_BUILD_TYPE=release'' is for stripped, non-debugging compilation.

Tellico has many unit tests for checking some parts of the code for problems. The tests can be compiled by using ''-DKDE4_BUILD_TESTS=TRUE'' and then running
<code>% make test</code>
= Compile =

''Make'' is used to actually compile Tellico.
<code>% make</code>

There will likely be some warnings during compilation, but at the end, if you see something like

[100%] Built target tellico

then the compilation completed successfully.
= Install =
To install Tellico alongside other KDE applications, you will likely need to use the ''sudo'' command.
<code>% sudo make install</code>

Enter your password, and Tellico should be installed and should show up in the KDE menu, likely in the Office menu. Or, run it from the command-line.
<code>% tellico</code>
= Enjoy =

You can send questions to the [http://tellico-project.org/mailing-list tellico-users mailing list].

If you need to uninstall Tellico
<code>% sudo make uninstall</code>

Development/Tutorials/Saving and loading (zh TW)

2009-11-20T16:53:13Z

← Older revision		Revision as of 16:53, 20 November 2009
Line 237:		Line 237:
	===加入動作===		===加入動作===

-	~~我們首先要做的是為使用者提供操作介面，使他們能夠告訴應用程式載入和儲存。類似教學 3的~~ <tt>quit</tt> 動作，我們將使用 <tt>KStandardActions</tt>。在37至47行，我們用和 <tt>quit</tt> 動作同樣的方式加入動作。我們將每一項連接到適當的槽，並宣告在標頭檔中。	+	我們首先要做的是為使用者提供操作介面，使他們能夠告訴應用程式載入和儲存。類似教學3的 <tt>quit</tt> 動作，我們將使用 <tt>KStandardActions</tt>。在37至47行，我們用和 <tt>quit</tt> 動作同樣的方式加入動作。我們將每一項連接到適當的槽，並宣告在標頭檔中。

	===創建新文件===		===創建新文件===
Line 317:		Line 317:
	</code>		</code>

-	~~There's nothing exciting or new in this function, just the logic to decide whether or not to show the save dialog. If~~ <tt>fileName</tt> ~~is not empty, then the file is saved to~~ <tt>fileName</tt>~~. But if it is, then the dialog is shown to allow the user to select a file name.~~	+	這個沒有什麼令人興奮的新功能，只是決定是否顯示儲存對話框。如果<tt>fileName</tt>不為空，則該檔案儲存到<tt>fileName</tt>。但是，如果是空的話，該對話框會讓用戶選擇檔案名。

	===載入檔案===		===載入檔案===

-	~~Finally, we get round to being able to load a file from disc. The code for this is all contained in~~ <tt>MainWindow::openFile()</tt>.	+	最後，載入硬碟的檔案的功能。所有程式碼，包含在<tt>MainWindow::openFile()</tt>。

-	~~First we must ask the user for the name of the file they wish to open. We do this using another one of the~~ <tt>KFileDialog</tt> ~~functions, this time~~ <tt>getOpenFileName()</tt>:	+	首先，我們必須詢問使用者他們希望打開的檔案名稱。我們是用另一個<tt>KFileDialog</tt> 的函式，這次用<tt>getOpenFileName()</tt>：
	<code cppqt>		<code cppqt>
	QString fileNameFromDialog = KFileDialog::getOpenFileName();		QString fileNameFromDialog = KFileDialog::getOpenFileName();
	</code>		</code>

-	~~Then we use the~~ KIO ~~library to retrieve our file. This allows us to open the file with~~ QFile ~~even if it's stored in a remote location like an~~ FTP ~~site. We make the following call to~~ {{class\|NetAccess}}'s <tt>download()</tt> ~~function~~	+	然後，我們使用 KIO 函式庫來檢索檔案。這使我們能夠用 QFile 打開檔案，即使它儲存在遠端例如 FTP 網站。我們呼叫 {{class\|NetAccess}} 的 <tt>download()</tt> 函數
	<code cppqt>		<code cppqt>
	KIO::NetAccess::download(fileNameFromDialog, tmpFile, this)		KIO::NetAccess::download(fileNameFromDialog, tmpFile, this)
	</code>		</code>
-	~~The first argument is the name of the file you wish to download. The second is a QString which, after the download is complete, will contain the location of the temporary copy of the file. It~~ is this <tt>tmpFile</tt> we will work with from now on.	+	第一個參數是您要下載檔案的名稱。第二個是僅次於下載完成後的QString，將包含檔案暫時備份的位置。It is this <tt>tmpFile</tt> we will work with from now on.

	The function returns <tt>true</tt> or <tt>false</tt> depending on whether the transfer was successful. If it failed, we display a message box giving the error:		The function returns <tt>true</tt> or <tt>false</tt> depending on whether the transfer was successful. If it failed, we display a message box giving the error:

Development/Tutorials/Collaboration/HotNewStuff/Introduction

2009-11-20T16:46:31Z

Created page with '{{Template:I18n/Language Navigation Bar|Development/Tutorials/Collaboration/HotNewStuff/Introduction}} {{TutorialBrowser| series=HotNewStuff| name=Get Hot New Stuff 3 In...'

New page

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

{{TutorialBrowser|
series=[[../|HotNewStuff]]|
name=Get Hot New Stuff 3 Introduction|
pre=[[Getting_Started|Getting started with KDE development]]|
}}

==Overview==
Here is a small example of an application that asks [http://opendesktop.org openDesktop.org] for wallpapers. It lets the user install them into the system wallpaper directory.

====The Code====
The example consists of just one c++ source file.
<code cppqt>
//khotnewstuff.cpp

#include <kapplication.h>
#include <kdebug.h>
#include <klocale.h>
#include <kcmdlineargs.h>
#include <kaboutdata.h>

#include <knewstuff3/downloaddialog.h>

int main(int argc, char **argv)
{
KAboutData about("khotnewstuff_example", 0, ki18n("KHotNewStuff"), "0.4");
about.setProgramIconName("get-hot-new-stuff");

KApplication i;

KNS3::DownloadDialog dialog(args->arg(0));
dialog.exec();
foreach (const KNS3::Entry& e, dialog.changedEntries()) {
kDebug() << "Changed Entry: " << e.name();
}

return 0;
}
</code>

For this to work, a file that sets up KNewStuff <em>khotnewstuff_example.knsrc</em> is needed. The file has to be in <em>kde/share/config/khotnewstuff_example.knsrc</em>. (The name of the file is taken from the about data).

<code>
[KNewStuff3]
ProvidersUrl=http://download.kde.org/ocs/providers.xml
Categories=KDE Wallpaper 1920x1200,KDE Wallpaper 1600x1200
TargetDir=wallpapers
</code>

Development/Tutorials

2009-11-20T16:34:54Z

Collaboration:

← Older revision		Revision as of 16:34, 20 November 2009
Line 285:		Line 285:

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

-	;[[Development/Tutorials/K Hot New Stuff2\|~~New introduction~~ to Get Hot New Stuff 2]]	+	;[[Development/Tutorials/K Hot New Stuff2\|Introduction to Get Hot New Stuff 2]]
-	:''A short tutorial about how to use KHotNewStuff2 in your application.''	+	:''A short tutorial about how to use KHotNewStuff2 in your application. Deprecated, use version 3''

	*old links for KNS1 content:		*old links for KNS1 content:

Getting Started/Build/Stable Version

2009-11-20T14:57:21Z

konstruct is obsolete.

← Older revision		Revision as of 14:57, 20 November 2009
Line 13:		Line 13:

	===KDE Stable===		===KDE Stable===
-	The ~~current~~ version of KDE stable is 3.5.9. You will want to build KDE stable if you are a maintainer for an OS distribution. Otherwise, you may want to install KDE stable using the tools provided by your OS distribution or vendor.	+	The old stable version of KDE stable is 3.5.10 (current stable version is a 3.4 branch as of 2009/11/20). You will want to build KDE stable if you are a maintainer for an OS distribution. Otherwise, you may want to install KDE stable using the tools provided by your OS distribution or vendor.

-	The ~~current~~ recommended way to install KDE stable is [[Getting Started/Build/Konstruct\|Konstruct]], a build system which ~~helps~~ you to install KDE releases and applications on your system. It downloads defined source tarballs, checks their integrity, decompresses, patches, configures, builds and installs them. A complete KDE installation should be as easy as "cd meta/kde;make install".	+	The recommended way to install KDE stable used to be [[Getting Started/Build/Konstruct\|Konstruct]], a build system which helped you to install KDE releases and applications on your system. It downloads defined source tarballs, checks their integrity, decompresses, patches, configures, builds and installs them. A complete KDE installation should be as easy as "cd meta/kde;make install".

	By default [[Getting Started/Build/Konstruct\|Konstruct]] installs to your home directory, which means you don't have to possess root privileges or risk to damage your system or affect another KDE.		By default [[Getting Started/Build/Konstruct\|Konstruct]] installs to your home directory, which means you don't have to possess root privileges or risk to damage your system or affect another KDE.

-	Currently it ~~gives a complete KDE 3.5.7 or 3.5.8 installation. Optionally you can install additional applications like KOffice 1.6.3. (KDevelop~~ is ~~now distributed as part of KDE, rather than as a separate package)~~.	+	'''Currently it does not work and is not maintained any more.'''

	===Compiling Yourself===		===Compiling Yourself===

Development/Tutorials/Metadata/Nepomuk/NepomukQuery

2009-11-20T10:40:24Z

Created page with '{{Template:I18n/Language Navigation Bar|Development/Tutorials/Metadata/Nepomuk/NepomukQuery}} {{TutorialBrowser| series=Nepomuk| name=The Nepomuk Query API| pre=[[../RDF...'

New page

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

{{TutorialBrowser|
series=[[../|Nepomuk]]|
name=The Nepomuk Query API|
pre=[[../RDFIntroduction|RDF and Ontologies in Nepomuk]]|
next=[[../Resources|Resource Handling with Nepomuk]]|
reading=[[../AdvancedQueries|Advanced Queries with SPARQL]]
}}

==The Nepomuk Query API==

With KDE 4.4 Nepomuk brings a new set of classes which can be found in the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/namespaceNepomuk_1_1Query.html Nepomuk::Query namespace].

They provide a desktop query API which allows to build queries from terms. The possible terms that can be combined into queries are:

* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1Query_1_1AndTerm.html AndTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1Query_1_1OrTerm.html OrTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1Query_1_1NegationTerm.html NegationTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1Query_1_1ComparisonTerm.html ComparisionTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1Query_1_1LiteralTerm.html LiteralTerm]
* [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1Query_1_1ResourceTerm.html ResourceTerm]

The most interesting one is ''ComparisonTerm'' which is used to match properties in resources.

The [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk/html/classNepomuk_1_1Query_1_1Query.html Query] class itself provides some nice ways to deal with the queries:

* toSparqlQuery() - Creates a SPARQL query to be used in Soprano::Model::executeQuery
* toSearchUrl() - Creates a URL that can be listed via KIO.

=== Examples ===

Imagine we wanted to find all files that are tagged with a certain tag:

<code cpp>
Nepomuk::Tag myTag = someFancyMethod();

// term matching the tag
Nepomuk::Query::ResourceTerm tagTerm( myTag );

// term matching tagged resource
Nepomuk::Query::ComparisonTerm term( Soprano::Vocabulary::NAO::hasTag(),
tagTerm,
Nepomuk::Query::ComparisonTerm::Equal );

// build the query
Nepomuk::Query::Query query( term );
</code>

Development/Tutorials/Metadata/Nepomuk

2009-11-20T10:14:39Z

Nepomuk:

← Older revision		Revision as of 10:14, 20 November 2009
Line 15:		Line 15:
	; [[Development/Tutorials/Metadata/Nepomuk/ResourceGenerator\|Using the Nepomuk Resource Generator]]		; [[Development/Tutorials/Metadata/Nepomuk/ResourceGenerator\|Using the Nepomuk Resource Generator]]
	:''Nepomuk includes a resource generator which creates convenience classes for handling metadata.''		:''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]]		; [[Development/Tutorials/Metadata/Nepomuk/AdvancedQueries\|Advanced Queries]]

Development/Tutorials/Metadata/Nepomuk/AdvancedQueries

2009-11-20T10:13:45Z

Full text queries:

← Older revision		Revision as of 10:13, 20 November 2009
Line 120:		Line 120:


-	===Full text queries===	+	=== Full text queries ===

-	~~While SPARQL in theory supports full text queries through the~~ [http://~~www~~.w3.~~org~~/TR/~~rdf-sparql-query~~/~~#funcex-regex ''REGEX FILTER''~~] ~~keywords the~~ storage ~~backends do not have their own real full text index~~. ~~Thus,~~ a full text search ~~using SPARQL FILTER may become very slow if there are many statements to filter~~.	+	With KDE 4.4 Nepomuk depends on [http://soprano.sourceforge.net/apidox/trunk/soprano_backend_virtuoso.html Virtuoso] for data storage. Virtuoso brings a lot of nice [http://docs.openlinksw.com/virtuoso/rdfsparql.html#sparqlextensions extensions to SPARQL]. Most importantly the full text search which is used through the artificial ''bif:contains'' property.

-	That is why in Soprano we have the [http://clucene.sourceforge.net/ CLucene] based [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/namespaceSoprano_1_1Index.html full text index model]. It is stacked on top of the actual storage model within the Nepomuk Server and provides a full text index on all literal object nodes in the repository. Since Soprano does not have a fancy query API yet (using plain strings as queries ~~does not count as ''fancy'')~~ full text queries ~~have still to be performed separately. This may be inconvenient but will hopefully be solved~~ in ~~Soprano 3.~~	+	This allows to combine graph queries with full text queries in a nice way:

-	~~So for now we have to learn a second way to query the repository~~: ~~using the [http~~:~~//lucene~~.~~apache.org~~/~~java/docs/queryparsersyntax.html Lucene Query Language]. But~~ that ~~is much easier~~ in ~~most cases~~.	+	<code>
		+	select ?r where { ?r nao:prefLabel ?label .
		+	?label bif:contains 'nepomuk' . }
		+	</code>
		+
		+	The query above will find any resources that contain ''nepomuk'' in their label.

-	Let us assume that we want to search resources that are related to some literal object that matches the value "nepomuk". In SPARQL this would mean to query for:	+	Of course wildcards are supported, too. However, be aware that when using wildcards the expression itself needs to be enclosed in quotes as follows:
		+
		+	<code>
		+	select ?r where { ?r nao:prefLabel ?label .
		+	?label bif:contains "'nepomuk*'" . }
		+	</code>
		+
		+	For most simple queries (simple queries do not use any back-referencing for example) the [[../NepomukQuery\|Nepomuk desktop query API]] should be sufficient.
		+
		+
		+	=== Full text queries before KDE 4.4 ===
		+
		+	While SPARQL in theory supports full text queries through the [http://www.w3.org/TR/rdf-sparql-query/#funcex-regex ''REGEX FILTER''] keywords the storage backends do not have their own real full text index. Thus, a full text search using SPARQL FILTER may become very slow if there are many statements to filter.
		+
		+	That is why in Soprano we have the [http://clucene.sourceforge.net/ CLucene] based [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/namespaceSoprano_1_1Index.html full text index model]. It is stacked on top of the actual storage model within the Nepomuk Server and provides a full text index on all literal object nodes in the repository. Since Soprano does not have a fancy query API yet (using plain strings as queries does not count as ''fancy'') full text queries have still to be performed separately. This may be inconvenient but will hopefully be solved in Soprano 3.
		+
		+	So for now we have to learn a second way to query the repository: using the [http://lucene.apache.org/java/docs/queryparsersyntax.html Lucene Query Language]. But that is much easier in most cases.
		+
		+	Let us assume that we want to search resources that are related to some literal object that matches the value "nepomuk". In SPARQL this would mean to query for:

	<code>		<code>
Line 134:		Line 157:
	FILTER REGEX(STR(?o),'nepomuk', 'i') .		FILTER REGEX(STR(?o),'nepomuk', 'i') .
	FILTER isLiteral(?o) . }		FILTER isLiteral(?o) . }
-	</code>	+	</code>

-	We convert the object literal into a string and match it to a regular expression ignoring case. This works but may be slow. Using the Soprano lucene full text index we perform this query as follows:	+	We convert the object literal into a string and match it to a regular expression ignoring case. This works but may be slow. Using the Soprano lucene full text index we perform this query as follows:

-	<code cppqt>	+	<code cppqt="cppqt">
	Soprano::QueryResultIterator it =		Soprano::QueryResultIterator it =
	model->executeQuery( "nepomuk",		model->executeQuery( "nepomuk",
Line 147:		Line 170:
	double score = it.binding( "score" ).literal().toDouble();		double score = it.binding( "score" ).literal().toDouble();
	}		}
-	</code>	+	</code>

-	Here we make use of the fact that Soprano allows to add new [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/namespaceSoprano_1_1Query.http user defined query languages]. Also we use the fixed mapping from CLucene query results to Soprano query bindings as defined in [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/classSoprano_1_1Index_1_1IndexFilterModel.html Soprano::Index::IndexFilterModel]:	+	Here we make use of the fact that Soprano allows to add new [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/namespaceSoprano_1_1Query.http user defined query languages]. Also we use the fixed mapping from CLucene query results to Soprano query bindings as defined in [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/classSoprano_1_1Index_1_1IndexFilterModel.html Soprano::Index::IndexFilterModel]:

-	* Binding ''resource'' always gives the matched resource.	+	*Binding ''resource'' always gives the matched resource.
-	* Binding ''score'' always gives the lucene score (between 0 and 1).	+	*Binding ''score'' always gives the lucene score (between 0 and 1).

-	These results can now be reused to perform further SPARQL queries.	+	These results can now be reused to perform further SPARQL queries.

-	Of course it is possible to use the full range of the [http://lucene.apache.org/java/docs/queryparsersyntax.html Lucene Query Language]. Another simple example would be to only match a certain property:	+	Of course it is possible to use the full range of the [http://lucene.apache.org/java/docs/queryparsersyntax.html Lucene Query Language]. Another simple example would be to only match a certain property:

-	<code cppqt>	+	<code cppqt="cppqt">
	QString query =		QString query =
	Soprano::Vocabulary::RDFS::label().toString()		Soprano::Vocabulary::RDFS::label().toString()

Development/Tutorials

2009-11-20T09:59:59Z

Nepomuk:

← Older revision		Revision as of 09:59, 20 November 2009
Line 181:		Line 181:
	; [[Development/Tutorials/Metadata/Nepomuk/ResourceGenerator\|Using the Nepomuk Resource Generator]]		; [[Development/Tutorials/Metadata/Nepomuk/ResourceGenerator\|Using the Nepomuk Resource Generator]]
	:''Nepomuk includes a resource generator which creates convenience classes for handling metadata.''		:''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]]		; [[Development/Tutorials/Metadata/Nepomuk/AdvancedQueries\|Advanced Queries]]

Schedules/KDE4/4.4 Feature Plan

2009-11-20T09:46:51Z

kdebase-runtime:

← Older revision		Revision as of 09:46, 20 November 2009
Line 93:		Line 93:
	{{FeatureTodo\|smb kioslave\|add kwallet support\|brandon.ml@gmail.com\|Carlo Segato}}		{{FeatureTodo\|smb kioslave\|add kwallet support\|brandon.ml@gmail.com\|Carlo Segato}}
	{{FeatureTodo\|Nepomuk\|Remove the ontologies and make kdebase depend on the upcoming shared-ontologies package\|trueg@kde.org\|Sebastian Trueg}}		{{FeatureTodo\|Nepomuk\|Remove the ontologies and make kdebase depend on the upcoming shared-ontologies package\|trueg@kde.org\|Sebastian Trueg}}
-	~~{{FeatureDone\|thumbnail kioslave\|Support for rotated jpegs\|wilderkde@gmail.com\|Jacopo De Simoi}}~~	+	{{FeatureInProgress\|Nepomuk\|Integrate Filesystem service to handle mounting/unmounting of removable devices\|trueg@kde.org\|Sebastian Trueg}} {{FeatureInProgress\|Locale KCM\|Add support for new KLocale features (see kdelibs section) including Currency Code, Decimal Places, Digit Groups, AM/PM, etc. Improvements to usability of existing options.\|john@layt.net\|John Layt}} {{FeatureInProgress\|Device Automounting\|Add support for storage device automounting\|tdfischer@fedoraproject.org\|Trever Fischer}}
-	{{FeatureInProgress\|Nepomuk\|Integrate Filesystem service to handle mounting/unmounting of removable devices\|trueg@kde.org\|Sebastian Trueg}} ~~{{FeatureInProgress\|Nepomuk\|Add nepomuk kio slave which handles all stating of Nepomuk resources\|trueg@kde.org\|Sebastian Trueg}}~~	+
-	{{FeatureInProgress\|Locale KCM\|Add support for new KLocale features (see kdelibs section) including Currency Code, Decimal Places, Digit Groups, AM/PM, etc. Improvements to usability of existing options.\|john@layt.net\|John Layt}} {{FeatureInProgress\|Device Automounting\|Add support for storage device automounting\|tdfischer@fedoraproject.org\|Trever Fischer}}	+
	{{FeatureInProgress\|Oxygen Animated\|Add smooth animations and transitions (e.g. on hover, when switching tabs, etc.) to the oxygen widget style.\|hugo@oxygen-icons.org\|Hugo Pereira Da Costa}}		{{FeatureInProgress\|Oxygen Animated\|Add smooth animations and transitions (e.g. on hover, when switching tabs, etc.) to the oxygen widget style.\|hugo@oxygen-icons.org\|Hugo Pereira Da Costa}}
	{{FeatureDone\|Nepomuk\|Port Nepomuk to Virtuoso: query service, strigi service\|trueg@kde.org\|Sebastian Trueg}}		{{FeatureDone\|Nepomuk\|Port Nepomuk to Virtuoso: query service, strigi service\|trueg@kde.org\|Sebastian Trueg}}
	{{FeatureDone\|thumbnail kioslave\|Support for comic-book cover previews (.cbr, .cbz, .cbt files)\|qwertymaniac@gmail.com\|Harsh J}}		{{FeatureDone\|thumbnail kioslave\|Support for comic-book cover previews (.cbr, .cbz, .cbt files)\|qwertymaniac@gmail.com\|Harsh J}}
		+	{{FeatureDone\|Nepomuk\|Add nepomuk kio slave which handles all stating of Nepomuk resources\|trueg@kde.org\|Sebastian Trueg}}
		+	{{FeatureDone\|thumbnail kioslave\|Support for rotated jpegs\|wilderkde@gmail.com\|Jacopo De Simoi}}
	\|}		\|}

Projects/Skrooge

2009-11-20T09:41:49Z

Link back to userbase

← Older revision		Revision as of 09:41, 20 November 2009
Line 4:		Line 4:
	\|-		\|-
	\| [[Image:SkroogeReport.png\|left]]		\| [[Image:SkroogeReport.png\|left]]
-	\| Skrooge is a personal finances manager for KDE4, aiming at being simple and intuitive. It allows you to keep track of your expenses and incomes, categorize them, and build reports of them.	+	\| Skrooge is a personal finances manager for KDE4, aiming at being simple and intuitive. It allows you to keep track of your expenses and incomes, categorize them, and build reports of them. [http://userbase.kde.org/skrooge Learn more...<br>]
	Skrooge is a part of [http://extragear.kde.org KDE Extragear], in the Office module		Skrooge is a part of [http://extragear.kde.org KDE Extragear], in the Office module

Projects/Kooka

2009-11-20T08:07:10Z

Updated for KDE4 port

← Older revision		Revision as of 08:07, 20 November 2009
Line 10:		Line 10:
	Now would be a good time to introduce myself: Jonathan Marten, the current Kooka maintainer. I was motivated to volunteer for this after having got a new networked scanner (an HP OfficeJet all-in-one) and finding that it didn't work with Kooka, although it did with SANE. Getting it to work with Kooka was a fairly simple fix, but it was obvious that there was a lot more in the application that could be improved.		Now would be a good time to introduce myself: Jonathan Marten, the current Kooka maintainer. I was motivated to volunteer for this after having got a new networked scanner (an HP OfficeJet all-in-one) and finding that it didn't work with Kooka, although it did with SANE. Getting it to work with Kooka was a fairly simple fix, but it was obvious that there was a lot more in the application that could be improved.

-	{{note\|Don't panic! Although Kooka is no longer present in KDE4, scanning is still available via the [[kolourpaint]] and [[KOffice]] applications among others. These use the [[~~libkscan~~]] library which is ~~still present~~ in kdegraphics.}}	+	{{note\|Don't panic! Although Kooka is no longer present in KDE4, scanning is still available via the [[kolourpaint]] and [[KOffice]] applications among others. These use the [[libksane]] library which is included as standard in kdegraphics.
		+	<br><br>There is also the scanning application [[Skanlite]] which is available in extragear.}}

	Any contributions that you can make to Kooka - code, documentation, translation, or artwork -		Any contributions that you can make to Kooka - code, documentation, translation, or artwork -
Line 35:		Line 36:
	will list all of the bugs that have been addressed in the development version.		will list all of the bugs that have been addressed in the development version.

-	== ~~Future Plans~~ ==	+	== KDE4 Porting ==

-	~~Obviously~~ the ~~Kooka~~ application ~~needs~~ to be ported ~~to KDE4~~. The dock widget ~~user~~ interface ~~that it currently uses is not supported in KDE4, as well as being rather unreliable and having usability issues~~ (~~see~~ {{bug\|71252}} and its many duplicates). I'm currently considering changing the user interface to a task oriented system with a tab for the three main tasks ("Scan", "OCR" and "Gallery"). The panes used for each task will be arranged using splitters. All of the sizes and arrangements will be fully configurable, of course.	+	Porting of Kooka to KDE4 has now started. At the moment the application runs, scans and saves. Major areas still to be ported are the image thumbnail view, gallery drag and drop, printing/copying, and OCR spell checking. New features needed include configurability for the user interface layout. The dock widget interface ({{bug\|71252}} and its many duplicates) has gone.

-	~~In addition to that~~, a new KDE scanning ~~application~~ [[Skanlite]] is being developed by Kåre Särs. ~~This includes a new library [[~~libksane~~]] which~~ has a number of advantages over libkscan, including access to all scanner options and 16-bit scanner support. In the long run the aim is to convert Kooka to use this new library.	+	There are some discussion threads ([http://lists.kde.org/?t=125570944700004&r=1&w=2 1],
		+	[http://lists.kde.org/?l=kde-devel&m=125594709527004&w=2 2],
		+	[http://lists.kde.org/?t=125603251000002&r=1&w=2 3]) regarding the KDE4 port and possible future changes. One of these possibilities is the new KDE scanning library [[libksane]], part of [[Skanlite]], being developed by Kåre Särs. libksane has a number of advantages over libkscan, including access to all scanner options and 16-bit scanner support. In the long run the aim is to convert Kooka to use this new library.

-	~~libksane is for KDE4 only, so the port will have to be done before the library conversion.~~	+	When ported to KDE4, Kooka may appear in extragear - or even an official KDE release - one day!
-		+
-	~~Having done all of this and~~ ported to KDE4, Kooka may appear in extragear - or even an official KDE release - one day!	+

	== Running the Development Version ==		== Running the Development Version ==
Line 52:		Line 53:
	[[Getting_Started/Sources/Using Subversion with KDE\|Using Subversion with KDE]] for more information on SVN.		[[Getting_Started/Sources/Using Subversion with KDE\|Using Subversion with KDE]] for more information on SVN.

-	The development version is at <tt>branches/work/kooka-~~kde3~~</tt>, if you just want to browse the files you can do so using the	+	The current development version (the KDE4 port) is at <tt>branches/work/kooka-kde4</tt>, if you just want to browse the files you can do so using the
-	[http://websvn.kde.org/branches/work/kooka-~~kde3~~/ KDE WebSVN].	+	[http://websvn.kde.org/branches/work/kooka-kde4/ KDE WebSVN].
	To check out a copy of the current sources, do the following:		To check out a copy of the current sources, do the following:

	cd [to a suitable place, e.g. your home directory]		cd [to a suitable place, e.g. your home directory]
-	svn co svn://anonsvn.kde.org/home/kde/branches/work/kooka-~~kde3~~	+	svn co svn://anonsvn.kde.org/home/kde/branches/work/kooka-kde4

	This will download the current sources to a subdirectory		This will download the current sources to a subdirectory
-	{{path\|kooka-~~kde3~~}}.	+	{{path\|kooka-kde4}}.
	To compile and install them, do the following:		To compile and install them, do the following:

-	cd kooka-~~kde3~~	+	mkdir kooka-kde4-build
-	~~make~~ -~~f Makefile.cvs~~	+	cd kooka-kde4-build
-	./~~configure~~ [with any options needed, you should not need to use any]	+	cmake ../kooka-kde4 [with any options needed, you should not need to use any]
	make		make

Line 72:		Line 73:
	su root -c 'make install'		su root -c 'make install'

-	This will ~~overwrite your existing~~ Kooka application, its ~~UI file and icons~~. ~~However~~, ~~it will not overwrite the original version of the libkscan library~~ so ~~as not to break any other applications which may use it. The new libkscan library~~ will get ~~installed with a new version number~~. After doing the install, you can run the new Kooka application with the command:	+	This will install the new Kooka application and its support files in the KDE4 install location. There is no Kooka included as standard in KDE4, so nothing will get overwritten. After doing the install, you can run the new Kooka application with the command:

	kooka		kooka
Line 78:		Line 79:
	or from the desktop or K-menu in the usual way.		or from the desktop or K-menu in the usual way.

-	{{tip\|You may need to install some additional software or packages (your distro may call them "development" packages) to obtain SVN, and the ~~autoconf/automake framework that <tt>Makefile.cvs</tt> uses~~.}}	+	{{tip\|You may need to install some additional software or packages (your distro may call them "development" packages) to obtain SVN and cmake, or the autotools needed for the KDE3 version.}}

		+	The KDE3 development version is still available, although it is no longer being updated - any bug fixes or improvements will appear in the KDE4 version only. To check out and build/install this version, do:
		+
		+	svn co svn://anonsvn.kde.org/home/kde/branches/work/kooka-kde3
		+	cd kooka-kde3
		+	make -f Makefile.cvs
		+	./configure [with any options needed]
		+	make
		+	su root -c 'make install'

	== Reporting Bugs or Wishes ==		== Reporting Bugs or Wishes ==
Line 88:		Line 97:

	If your problem is a crash, please try to include a meaningful backtrace - this will be displayed by DrKonqi when the application crashes.		If your problem is a crash, please try to include a meaningful backtrace - this will be displayed by DrKonqi when the application crashes.
-	See [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports]] for information on how to create and submit useful ~~crash~~ reports.	+	See the TechBase article [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports\|How to create useful crash reports]] for information on how to create and submit useful reports.

	Please be aware that a crash may not be a problem with Kooka or anywhere in KDE, it may be caused by the SANE libraries or even the kernel. Unfortunately, it may not be possible to reproduce the problem for investigation unless a developer has the same scanner hardware as you do - even then it may not be possible. You should ensure that you are using a reasonably up-to-date kernel (especially if your scanner is connected via USB) and the latest SANE package. Check the [http://www.sane-project.org/bugs.html SANE bug tracker] if you suspect that the problem may involve SANE.		Please be aware that a crash may not be a problem with Kooka or anywhere in KDE, it may be caused by the SANE libraries or even the kernel. Unfortunately, it may not be possible to reproduce the problem for investigation unless a developer has the same scanner hardware as you do - even then it may not be possible. You should ensure that you are using a reasonably up-to-date kernel (especially if your scanner is connected via USB) and the latest SANE package. Check the [http://www.sane-project.org/bugs.html SANE bug tracker] if you suspect that the problem may involve SANE.

Schedules/KDE4/4.4 Feature Plan

2009-11-19T22:48:30Z

← Older revision		Revision as of 22:48, 19 November 2009
Line 376:		Line 376:
	{{FeatureTodo\|Khtml\|Implement more of DOM3's CSSOM View module\|germain@ebooksfrance.org\|Germain Garand}}		{{FeatureTodo\|Khtml\|Implement more of DOM3's CSSOM View module\|germain@ebooksfrance.org\|Germain Garand}}
	{{FeatureInProgress\|kfile\|Move KMetaDataWidget and KMetaDataConfigurationDialog from Dolphin to kfile\|peter.penz@gmx.at\|Peter Penz}}		{{FeatureInProgress\|kfile\|Move KMetaDataWidget and KMetaDataConfigurationDialog from Dolphin to kfile\|peter.penz@gmx.at\|Peter Penz}}
-	{{~~FeatureInProgress~~\|katepart\|Improve TemplateInterface, i.e. snippet support\|mail@milianw.de\|Milian Wolff}}	+	{{FeatureDone\|katepart\|Improve TemplateInterface, i.e. snippet support\|mail@milianw.de\|Milian Wolff}}
-	{{~~FeatureInProgress~~\|katepart\|Add interface to access highlighting information, port html-export plugin\|mail@milianw.de\|Milian Wolff}}	+	{{FeatureDone\|katepart\|Add interface to access highlighting information, port html-export plugin\|mail@milianw.de\|Milian Wolff}}
	{{FeatureInProgress\|kdecore\|Move event-filter installation out of KApplication and into a new class\|lemma@confuego.org\|Michael Leupold}} {{FeatureInProgress\|kdecore\|Polkit-1 backend for KAuth\|drf@kde.org\|Dario Freddi}}		{{FeatureInProgress\|kdecore\|Move event-filter installation out of KApplication and into a new class\|lemma@confuego.org\|Michael Leupold}} {{FeatureInProgress\|kdecore\|Polkit-1 backend for KAuth\|drf@kde.org\|Dario Freddi}}
	{{FeatureInProgress\|kdeui\|Support floating point font sizes\|christoph@maxiom.de\|Christoph Feck}}		{{FeatureInProgress\|kdeui\|Support floating point font sizes\|christoph@maxiom.de\|Christoph Feck}}

Contribute (pt BR)

2009-11-19T22:28:05Z

Notícias e Fontes de E-mail:

← Older revision		Revision as of 22:28, 19 November 2009
(3 intermediate revisions not shown)
Line 1:		Line 1:
-	Esta página pretende dar uma visão geral dos diferentes aspectos do desenvolvimento do ~~Kde~~, em particular a assuntos ~~relacinados~~ com programação. '''O projeto KDE dá as boas vindas a todos ~~dispotos~~ a ajudar.'''	+	{{Template:I18n/Language Navigation Bar\|Contribute}}
		+	Esta página pretende dar uma visão geral dos diferentes aspectos do desenvolvimento do KDE, em particular a assuntos relacionados com programação. '''O projeto KDE dá as boas vindas a todos dispostos a ajudar.'''
		+
		+	{{note (pt_BR)\|Existem várias maneiras de participar do desenvolvimento do KDE, as quais podem ser divididas em diversas categorias:
		+	:''Documentação, Tradução, Desenvolvimento, Usabilidade, Acessibilidade, Artwork, Promoção
		+	'''Não é um programador? Veja as páginas do KDE em [http://kde.org/getinvolved/ como participar] para conferir outras maneiras que você pode ajudar. Veja também: [[Contribute/Bugsquad\|Bugsquad]]!'''
		+	}}
		+
		+	== Notícias e Fontes de E-mail ==
		+	A direção geral do projeto KDE é determinada por aqueles que fazem o trabalho - não existe nenhum tipo de plano único o qual determine como o KDE irá ser no futuro.
		+
		+	Se você quer saber o que está atualmente acontecendo, então existem um número de fontes de informação as quais você deve considerar:
		+	; [http://www.kde.org/mailinglists/ Listas de e-mail]
		+	: Provavelmente a melhor maneira de encontrar o que está acontecendo no desenvolvimento do KDE. Os arquivos estão disponíveis [http://lists.kde.org aqui].
		+
		+	; [http://commitfilter.kde.org/ CommitFilter]
		+	: Notificação de recebimento de mudanças do [http://en.wikipedia.org/wiki/Subversion SVN] em áreas de seu interesse.
		+
		+	; [http://commit-digest.org/ KDE Commit-Digest]
		+	: Um resumo semanal das mudanças ocorridas no SVN.
		+
		+	; [http://dot.kde.org/ The Dot]
		+	: A página de notícias do KDE.
		+
		+	== Getting Started with Coding ==
		+	Getting started at coding for KDE is a matter of finding something to fix, and fixing it. You may want to consult the module overview to help find what you are looking for; once you have fixed something, you will want to send in a patch. If you do that a few times, you may want to apply for an SVN account so you can fix things directly.
		+	* [[Contribute/List of KDE Modules\|Module overview]]
		+	* [[Contribute/Send Patches\|Sending patches]]
		+	* [[Contribute/Get a SVN Account\|Applying for a KDE SVN Account]]
		+	* [[Contribute/First Steps with your KDE SVN Account\|First steps with your new SVN account]]
		+
		+	=== C++ ===
		+	KDE is mostly written in C++. If you are not familiar with C++, you should do at least some work on it. There are a number of good books on C++ - an excellent source is [http://mindview.net/Books/TICPP/ThinkingInCPP2e.html Bruce Eckel's "Thinking in C++"], which is available both as a free download and as a printed document. It isn't essential to understand everything before you start in KDE, but you do need to understand basic syntax and operations.
		+
		+	=== Qt ===
		+	To become proficient with KDE coding, you should understand the Qt toolkit. If you are not familiar with Qt, you should work through the tutorials included with Qt ([http://doc.trolltech.com/latest/examples.html Qt4 version], [http://doc.trolltech.com/3.3/tutorial.html Qt3 version]).
		+
		+	If you are more into multimedia and videos for a start you might want to spend two amazing minutes on watching [http://www.trolltech.com/trolltech/products/qt/learnmore/video/demos/browser Building a Simple Help Documentation Browser with Qt4 Designer]. If that got your attention you might also want to watch the video introduction [http://www.trolltechvideo.com/video/day1/room_a/a_1_1/video.html Hello Qt] by Mark Summerfield which is part of the [http://www.trolltech.com/company/newsroom/events/allevents/devdays2006/videolinks Trolltech Developer Days 2006 presentations].
		+
		+	If you need a gentler introduction to Qt, or would just like an alternative view, then you may wish to look at the [http://qt4.digitalfanatics.org/tiqt/ The Independent Qt Tutorial] (Currently offline due to book contract).
		+
		+	If you prefer to learn Qt by reading a traditional book, take a look at Trolltechs [http://trolltech.com/developer/documentation/books book page]. More suggestions on becoming familiar with Qt4 are [http://doc.trolltech.com/latest/how-to-learn-qt.html available here as well].
		+
		+	=== KDE ===
		+	A range of information on KDE techniques is available in the [[Development/Tutorials\|tutorial section]]. Note that some of these tutorials still target KDE3, though they should be at least partly applicable.
		+
		+	You will also find useful information on KDE coding in the [[Development/FAQs\|FAQs]] section. This information may also be somewhat dated for KDE4, however much of it is broadly applicable, even outside KDE.
		+
		+	You can also read [[Development/Further Information#Books\|KDE coding books]].
		+
		+	Last, but by no means least, KDE comes with extensive class (Application Programmer Interface) documentation. This is available in the
		+	[[Development/Tutorials/API Documentation\|KDE API Reference Manuals]] section, which also contains a number of useful links on how to write or update the class documentation. You can also generate these on your own machine, or refer to a more up-to-date online version at [http://www.englishbreakfastnetwork.org/apidocs/apidox-kde-4.0/kdelibs-apidocs/ The English Breakfast Network].
		+
		+	A more detailed description of the steps above is available in our [http://quality.kde.org/develop/howto/howtohack.php Programming Guide].
		+
		+	== Getting Involved in Bug Hunting and Application Quality ==
		+
		+	There is a large number of applications within KDE, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.
		+
		+	If you are interested in helping out with KDE, but don't know where to start, visit [http://www.kde.org/getinvolved/ Contribute Website] for more information. Note that you do not need any programming skills to become involved. In particular develpers regurarly publish so-called [[/Junior Jobs\|Junior Jobs]] to encourage new contributions.
		+
		+	Of course, you can become involved in bug hunting without being part of the KDE Quality Team - just create yourself an account on the KDE [http://bugs.kde.org bug tracking system], and start searching / sorting through the bugs. Again, you don't have to have programming skills - it helps the programmers enormously just to have a procedure that allows a bug to be consistently reproduced.
		+
		+	The [[Contribute/Bugsquad\|Bugsquad]] tries to keep track of bugs in KDE software and make sure that valid bugs are noticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the KDE community if you cannot program.
		+
		+	==Conseguir respostas para suas perguntas==
		+	If your question concerns KDE development, your options are pretty much the same general user ones, with some modifications:
		+	::* '''Read the Developer FAQ'''. Many common developer questions have been answered in the [http://developer.kde.org/documentation/other/developer-faq.html KDE Developer FAQ]
		+	::* '''Search/browse KDE websites'''. A lot of questions can also be answered from the KDE websites, and the documentation included on it. You can search all the KDE websites on the homepage. In addition, you can browse the [http://developer.kde.org/ KDE developer website].
		+	::* '''Search mailing lists'''. A lot of questions have already been answered on the KDE mailing lists, particular the lists kde-devel, kde2-porting, kde-core-devel, kde-games-devel, kfm-devel and koffice-devel. You can search these lists either at [http://lists.kde.org/ lists.kde.org]. You should always search for your answer before asking questions on the mailing lists. When you ask a question on a mailing list you are emailing thousands of people -- please do this only if the answer is not available through a simple search.
		+	::* '''Search engines'''. Do not forget about your favorite search engine. One of the best search engines is Google. With Google you can also [http://groups.google.com/ search] the great bulk of Usenet news sites, which is also particularly helpful, especially for general programming and gcc-related questions.
		+	::* '''Ask on KDE mailing lists'''. If you still do not have an answer, try asking your question on one of the KDE mailing lists listed above.
		+	::::* For questions relating to core development or third-party KDE development, unless you are particularly interested in [http://konqueror.kde.org/ Konqueror], KOffice, games or Java development, your main choice is [mailto:kde-devel@kde.org kde-devel] [mailto:kde-devel-request@kde.org?subject=subscribe (subscribe)].
		+	::::* For questions relating to Konqueror development, your main choice is [mailto:kfm-devel@kde.org kfm-devel] [mailto:kfm-devel@kde.org?subject=subscribe (subscribe)]
		+	::::* For questions relating to KOffice development, your main choice is [mailto:koffice-devel@kde.org koffice-devel] [mailto:koffice-devel-request@kde.org?subject=subscribe (subscribe)]
		+	::::* For questions relating to games development, your main choice is [mailto:kde-games-devel@kde.org kde-games-devel] [mailto:kde-games-devel-request@kde.org?subject=subscribe (subscribe)]
		+	::::* For questions relating to Java development with KDE, your main choice is [mailto:kde-java@mail.kde.org kde-java] [mailto:kde-java-request@mail.kde.org?subject=subscribe (subscribe)]
		+	::::* For questions relating to [http://qt.nokia.com/ Qt development], please use the fine [http://lists.trolltech.com/qt-interest/ Qt mailing list].
		+	A full list of KDE mailing lists is available [http://www.kde.org/mailinglists/ here] and [http://mail.kde.org/mailman/listinfo here].
		+
		+	== Historical Sources ==
		+
		+	; [http://www.kerneltraffic.org/kde/archives.html KDE Traffic]
		+	: Summary of the development mailing lists. KDE Traffic ran for 76 issues, from 10 March 2001 until 16 April 2004. The KDE Commit-Digest (described above) is its logical successor.
		+
		+	----
		+
		+	----

Policies/Licensing Policy

2009-11-19T21:53:53Z

add cmake and CC sections

← Older revision		Revision as of 21:53, 19 November 2009
Line 19:		Line 19:
	#* '''FDL''' versions 1.2 as listed in {{path\|kdelibs/COPYING.DOC}} or later versions approved by KDE e.V. with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.		#* '''FDL''' versions 1.2 as listed in {{path\|kdelibs/COPYING.DOC}} or later versions approved by KDE e.V. with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
	#:Documentation may additionally be licensed under any of the terms in section 4 or 5.		#:Documentation may additionally be licensed under any of the terms in section 4 or 5.
		+	# CMake modues must be licenced under the BSD licence listed below
		+	# Standalone media files such as images may be licensed under the Creative Commons Attribution-Share Alike 3.0 Unported licence at http://creativecommons.org/licenses/by-sa/3.0/ . This does not apply to icons or anything which is likely to be mixed with content under our normal (GPL etc) licences.
	# Other data included in KDE's codebase must be licenced under one of the terms in sections 4 or 5.		# Other data included in KDE's codebase must be licenced under one of the terms in sections 4 or 5.
	# Contributors who have signed the Fiduciary License Agreement with KDE e.V. may licence files described in section 3 under LGPL 2.1 & 3 only and may licence other source files under GPL 2 & 3 only.		# Contributors who have signed the Fiduciary License Agreement with KDE e.V. may licence files described in section 3 under LGPL 2.1 & 3 only and may licence other source files under GPL 2 & 3 only.
Line 128:		Line 130:
	THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.		THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
	</pre>		</pre>
		+
		+	[A third requirement is sometimes included: "3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission." The advertising clause must never be included.]

	== X11 License ==		== X11 License ==

Projects/Skrooge

2009-11-19T20:33:08Z

← Older revision		Revision as of 20:33, 19 November 2009
(2 intermediate revisions not shown)
Line 10:		Line 10:

	This page is dedicated to developpers or advanced users who wish to have a deeper understanding of Skrooge.		This page is dedicated to developpers or advanced users who wish to have a deeper understanding of Skrooge.
		+
		+	== Compiling ==
		+
		+	Before we start, please consider using a precompiled package for your distro. You should only be compiling yourself if there is no package yet for your distro, or if you want the latest version, directly from the developpers.
		+
		+	=== Get the Sources ===
		+
		+	First, you will need to get the Skrooge source code. There are two ways to do this.
		+
		+	==== Latest Release ====
		+
		+	You can download the [http://websvn.kde.org/checkout/tags/skrooge/0.5.3/skrooge-0.5.3.tar.bz2 archive file] containing the source code, and extract its content using your favorite extraction tool, such as [http://userbase.kde.org/ark Ark].
		+
		+	==== Development Version ====
		+
		+	Like all KDE applications, the source code is stored in KDE's Subversion system, in the ''extragear/office'' folder. Please refer to [http://techbase.kde.org/Getting_Started/Sources/Using_Subversion_with_KDE the Subversion Tutorial for KDE]. You will need an SVN account to get it from there. <code>svn co svn://anonsvn.kde.org/home/kde/trunk/extragear/office/skrooge</code>
		+
		+	=== Dependencies ===
		+
		+	To be able to compile and run Skrooge, you will need some additional components
		+
		+	==== KDE4 Headers ====
		+
		+	Skrooge being a KDE4 application, it depends on many things in the KDE headers. You can get them from your distribution's packages (name usually contains KDE4+devel, KDE4+headers), or [http://techbase.kde.org/Getting_Started/Sources/Using_Subversion_with_KDE directly from KDE repositories].
		+
		+	==== QCA ====
		+
		+	[http://delta.affinix.com/qca/ Qt Cryptographic Architecture]. Get it from your distribution packages.
		+
		+	==== libofx ====
		+
		+	A [http://libofx.sourceforge.net/ library] to handle import for OFX files. Get it from your distribution packages.
		+
		+	=== Build & Install ===
		+
		+	Place yourself in the directory containing the source code, and create a directory named "build" (This is useful to segregate built files from the source code). Open a [http://userbase.kde.org/konsole Konsole] in this directory, and run the following commands (as a normal user) :
		+
		+	<code>
		+	mkdir build && cd build
		+	cmake .. -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix`
		+	make
		+	</code>
		+
		+	(please note the backquotes in the cmake command, they are important...)
		+
		+	Then, with root privileges :
		+
		+	<code>
		+	make install
		+	</code>
		+
		+	=== Uninstall ===
		+
		+	Tried Skrooge but didn't like it ? Sorry to hear this... You can uninstall it by running this command in the aforementionned "build" directory, with root privileges :
		+
		+	<code>
		+	make uninstall
		+	</code>
		+
		+	<br>

	== Debugging ==		== Debugging ==
Line 57:		Line 117:


-	=== Interactive mode ===	+	=== Interactive mode ===
		+
		+	[[Category:Skrooge]]

User:The-best-goose

2009-11-19T16:47:33Z

created new account User:The-best-goose

New page

Projects/rekonq/Ideas

2009-11-19T15:59:25Z

← Older revision		Revision as of 15:59, 19 November 2009
(One intermediate revision not shown)
Line 9:		Line 9:

	*apturl support for debian systems		*apturl support for debian systems
		+
		+	*Google bookmarks support/sync

Projects/Digikam/CodingSprint2009-summary

2009-11-19T15:41:34Z

← Older revision		Revision as of 15:41, 19 November 2009
Line 67:		Line 67:
	http://farm3.static.flickr.com/2547/4105709488_b341b5eb0a_m.jpg		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~~.	+	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.

-	~~Note~~: All event photos are available on Flickr group given below:	+	http://farm3.static.flickr.com/2719/4112661184_ae24203b66_m.jpg
		+
		+	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. All event photos are available on Flickr group given below:

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

Projects/Digikam/CodingSprint2009-summary

2009-11-19T15:05:36Z

Missing space and downgrade from face recognition to region tagging

← Older revision		Revision as of 15:05, 19 November 2009
Line 58:		Line 58:
	http://farm3.static.flickr.com/2742/4105701938_d25db886e5_m.jpg		http://farm3.static.flickr.com/2742/4105701938_d25db886e5_m.jpg

-	Michael worked on two areas: geolocation and ~~face recognition~~.	+	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, ~~andhow~~ to store such information in image metadata.	+	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		http://farm3.static.flickr.com/2592/4107584246_5f1b2b5065_m.jpg

Projects/Digikam/CodingSprint2009-summary

2009-11-19T14:19:04Z

Projects/Digikam/CodingSprint2009-summary

2009-11-19T12:25:00Z

← Older revision		Revision as of 12:25, 19 November 2009
(3 intermediate revisions not shown)
Line 1:		Line 1:
	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.		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.

-	~~DigiKam~~ developer Gilles Caulier hacked with Kåre on the Acquire Images Kipi plugin and found some problems with the libksane Twain implementation.	+	http://farm3.static.flickr.com/2602/4104932135_3cb3f69536_m.jpg
		+
		+	digiKam developer Gilles Caulier hacked with Kåre 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, 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.		Working on cross-platform support, he reported a lot of problems with digiKam on Windows to Patrick, 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.

Line 16:		Line 18:
	With Michael, 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.		With Michael, 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.		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 Fiestas and Aleix Pol, 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.		Alex Fiestas and Aleix Pol, 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.
Line 29:		Line 33:

	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.		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.		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.

Line 34:		Line 41:

	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.		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.		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		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
Line 44:		Line 55:
	Luka Renko 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		Luka Renko 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.		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 G. Hansen worked on two areas: geolocation and face recognition.		Michael G. Hansen worked on two areas: geolocation and face recognition.
	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, andhow to store such information in image metadata.		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, andhow to store such information in image metadata.

-	Andi Clemens set up a KDE build environment for Windows to finally be able to hunt bugs	+	http://farm3.static.flickr.com/2592/4107584246_5f1b2b5065_m.jpg
-	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.	+	Andi Clemens 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 Wiesweg 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.		Marcel Wiesweg 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-summary

2009-11-19T11:50:03Z

Minor clarifications

← Older revision		Revision as of 11:50, 19 November 2009
Line 1:		Line 1:
	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.		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.

-	DigiKam developer Gilles Caulier hacked with Kåre on the Acquire Images Kipi plugin and found some problems with the libksane implementation.	+	DigiKam developer Gilles Caulier hacked with Kåre 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, 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 ~~computer~~. Some problems in the liblqr library are waiting to be fixed.	+	Working on cross-platform support, he reported a lot of problems with digiKam on Windows to Patrick, 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		http://farm3.static.flickr.com/2624/4112660504_f043577c72_m.jpg

Projects/Digikam/CodingSprint2009-summary

2009-11-19T11:40:47Z

← Older revision		Revision as of 11:40, 19 November 2009
Line 1:		Line 1:
	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.		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.

-	DigiKam developer Gilles Caulier hacked with Kåre on the Acquire Images Kipi plugin and found some problems with the libksane implementation. Working on cross-platform support, he reported a lot of problems with digiKam on Windows to Patrick, 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 computer. Some problems in the liblqr library are waiting to be fixed.	+	DigiKam developer Gilles Caulier hacked with Kåre on the Acquire Images Kipi plugin and found some problems with the libksane implementation.
		+	Working on cross-platform support, he reported a lot of problems with digiKam on Windows to Patrick, 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 computer. 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, Alex and Aleix 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.		In discussions with Luka, Alex and Aleix 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 shared initial thoughts about future image versioning support in digiKam and wishes to support grouping of pictures, Gilles and Andi 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.		Gilles and Marcel shared initial thoughts about future image versioning support in digiKam and wishes to support grouping of pictures, Gilles and Andi 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, 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.		With Michael, 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.
		+
		+
		+
	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.		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.

	Alex Fiestas and Aleix Pol, 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.		Alex Fiestas and Aleix Pol, 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 Särs, 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.		Besides the usual amount of bug hunting and fixing, Kåre Särs, 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.		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.
	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.		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.		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.
Line 20:		Line 39:
	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		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.		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 Renko 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		Luka Renko 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

Contribute/Bugsquad/BugDays/PhononDay/Bugs needing attention from Konqueror developers

2009-11-19T11:36:32Z

Phonon bugs that need attention from developers:

← Older revision		Revision as of 11:36, 19 November 2009
Line 2:		Line 2:
	If anything is in doubt, put it here, and give a description of why you think a developer should look at it.		If anything is in doubt, put it here, and give a description of why you think a developer should look at it.

		+	* {{bug\|170971}} probably listing two different and unrelated issues.[[User:Mamarok\|Mamarok]]
	* {{Bug\|180148}} I was able to reproduce until ~1 week ago. Not sure if it's still there. [[User:jacopods\|wilder]]		* {{Bug\|180148}} I was able to reproduce until ~1 week ago. Not sure if it's still there. [[User:jacopods\|wilder]]
	* {{Bug\|184584}} Weird: kmix / alsamixer does not affect phonon volume [[User:jacopods\|wilder]]		* {{Bug\|184584}} Weird: kmix / alsamixer does not affect phonon volume [[User:jacopods\|wilder]]

Projects/Digikam/CodingSprint2009-summary

2009-11-19T11:22:32Z

tweak

← Older revision		Revision as of 11:22, 19 November 2009
Line 14:		Line 14:
	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.		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.

-	Guillaume Paumier's main goal was to start working on an export plugin to Wikimedia Commons ~~which can be a wonderful tool for Wikimedia photographers~~. 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~~, quite happy to advance so quickly~~. While the current work focuses on a specific wiki (Wikimedia Commons), it could be later extended to a more general MediaWiki library for Qt.	+	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.

	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.		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.

Projects/Digikam/CodingSprint2009-summary

2009-11-19T11:12:58Z

initial revision

New page

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.

DigiKam developer Gilles Caulier hacked with Kåre on the Acquire Images Kipi plugin and found some problems with the libksane implementation. Working on cross-platform support, he reported a lot of problems with digiKam on Windows to Patrick, 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 computer. Some problems in the liblqr library are waiting to be fixed.
In discussions with Luka, Alex and Aleix 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.
Gilles and Marcel shared initial thoughts about future image versioning support in digiKam and wishes to support grouping of pictures, Gilles and Andi 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.
With Michael, 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.
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.

Alex Fiestas and Aleix Pol, 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.

Besides the usual amount of bug hunting and fixing, Kåre Särs, 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.

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.
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.

Guillaume Paumier's main goal was to start working on an export plugin to Wikimedia Commons which can be a wonderful tool for Wikimedia photographers. 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, quite happy to advance so quickly. While the current work focuses on a specific wiki (Wikimedia Commons), it could be later extended to a more general MediaWiki library for Qt.

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.

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.

Luka Renko 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.

Michael G. Hansen worked on two areas: geolocation and face recognition.
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, andhow to store such information in image metadata.

Andi Clemens 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.

Marcel Wiesweg 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.

Projects/rekonq/Ideas

2009-11-19T03:34:13Z

← Older revision		Revision as of 03:34, 19 November 2009
Line 7:		Line 7:

	*Create some kind of dataengine from the "New Tab Page", so that a plasmoid can be made out of it		*Create some kind of dataengine from the "New Tab Page", so that a plasmoid can be made out of it
		+
		+	*apturl support for debian systems

User:Создание сайта москва en4o6mbj3imq31z

2009-11-18T20:48:48Z

blocked [[Создание сайта москва en4o6mbj3imq31z (Talk | contribs)]] with an expiry time of infinite (account creation disabled, e-mail blocked) spm

New page

Development/Tutorials/Collaboration/Attica/Tips

2009-11-18T20:47:33Z

use other template

← Older revision		Revision as of 20:47, 18 November 2009
Line 1:		Line 1:
	= Debugging Attica =		= Debugging Attica =
-	In	+	In {{path\|attica/lib/atticabasejob.cpp}}
-	~~<code>~~attica/lib/atticabasejob.cpp~~</code>~~	+
	you can enable the debug output of all XML the server sends.		you can enable the debug output of all XML the server sends.
	Simply add the qDebug() to the dataFinished function:		Simply add the qDebug() to the dataFinished function:

User:Создание сайта москва en4o6mbj3imq31z

2009-11-18T20:33:45Z

New user account

New page

← Older revision		Revision as of 09:46, 20 November 2009
Line 93:		Line 93:
	{{FeatureTodo\|smb kioslave\|add kwallet support\|brandon.ml@gmail.com\|Carlo Segato}}		{{FeatureTodo\|smb kioslave\|add kwallet support\|brandon.ml@gmail.com\|Carlo Segato}}
	{{FeatureTodo\|Nepomuk\|Remove the ontologies and make kdebase depend on the upcoming shared-ontologies package\|trueg@kde.org\|Sebastian Trueg}}		{{FeatureTodo\|Nepomuk\|Remove the ontologies and make kdebase depend on the upcoming shared-ontologies package\|trueg@kde.org\|Sebastian Trueg}}
-	~~{{FeatureDone\|thumbnail kioslave\|Support for rotated jpegs\|wilderkde@gmail.com\|Jacopo De Simoi}}~~	+	{{FeatureInProgress\|Nepomuk\|Integrate Filesystem service to handle mounting/unmounting of removable devices\|trueg@kde.org\|Sebastian Trueg}} {{FeatureInProgress\|Locale KCM\|Add support for new KLocale features (see kdelibs section) including Currency Code, Decimal Places, Digit Groups, AM/PM, etc. Improvements to usability of existing options.\|john@layt.net\|John Layt}} {{FeatureInProgress\|Device Automounting\|Add support for storage device automounting\|tdfischer@fedoraproject.org\|Trever Fischer}}
-	{{FeatureInProgress\|Nepomuk\|Integrate Filesystem service to handle mounting/unmounting of removable devices\|trueg@kde.org\|Sebastian Trueg}} ~~{{FeatureInProgress\|Nepomuk\|Add nepomuk kio slave which handles all stating of Nepomuk resources\|trueg@kde.org\|Sebastian Trueg}}~~	+
-	{{FeatureInProgress\|Locale KCM\|Add support for new KLocale features (see kdelibs section) including Currency Code, Decimal Places, Digit Groups, AM/PM, etc. Improvements to usability of existing options.\|john@layt.net\|John Layt}} {{FeatureInProgress\|Device Automounting\|Add support for storage device automounting\|tdfischer@fedoraproject.org\|Trever Fischer}}	+
	{{FeatureInProgress\|Oxygen Animated\|Add smooth animations and transitions (e.g. on hover, when switching tabs, etc.) to the oxygen widget style.\|hugo@oxygen-icons.org\|Hugo Pereira Da Costa}}		{{FeatureInProgress\|Oxygen Animated\|Add smooth animations and transitions (e.g. on hover, when switching tabs, etc.) to the oxygen widget style.\|hugo@oxygen-icons.org\|Hugo Pereira Da Costa}}
	{{FeatureDone\|Nepomuk\|Port Nepomuk to Virtuoso: query service, strigi service\|trueg@kde.org\|Sebastian Trueg}}		{{FeatureDone\|Nepomuk\|Port Nepomuk to Virtuoso: query service, strigi service\|trueg@kde.org\|Sebastian Trueg}}
	{{FeatureDone\|thumbnail kioslave\|Support for comic-book cover previews (.cbr, .cbz, .cbt files)\|qwertymaniac@gmail.com\|Harsh J}}		{{FeatureDone\|thumbnail kioslave\|Support for comic-book cover previews (.cbr, .cbz, .cbt files)\|qwertymaniac@gmail.com\|Harsh J}}
		+	{{FeatureDone\|Nepomuk\|Add nepomuk kio slave which handles all stating of Nepomuk resources\|trueg@kde.org\|Sebastian Trueg}}
		+	{{FeatureDone\|thumbnail kioslave\|Support for rotated jpegs\|wilderkde@gmail.com\|Jacopo De Simoi}}
	\|}		\|}

← Older revision		Revision as of 22:48, 19 November 2009
Line 376:		Line 376:
	{{FeatureTodo\|Khtml\|Implement more of DOM3's CSSOM View module\|germain@ebooksfrance.org\|Germain Garand}}		{{FeatureTodo\|Khtml\|Implement more of DOM3's CSSOM View module\|germain@ebooksfrance.org\|Germain Garand}}
	{{FeatureInProgress\|kfile\|Move KMetaDataWidget and KMetaDataConfigurationDialog from Dolphin to kfile\|peter.penz@gmx.at\|Peter Penz}}		{{FeatureInProgress\|kfile\|Move KMetaDataWidget and KMetaDataConfigurationDialog from Dolphin to kfile\|peter.penz@gmx.at\|Peter Penz}}
-	{{~~FeatureInProgress~~\|katepart\|Improve TemplateInterface, i.e. snippet support\|mail@milianw.de\|Milian Wolff}}	+	{{FeatureDone\|katepart\|Improve TemplateInterface, i.e. snippet support\|mail@milianw.de\|Milian Wolff}}
-	{{~~FeatureInProgress~~\|katepart\|Add interface to access highlighting information, port html-export plugin\|mail@milianw.de\|Milian Wolff}}	+	{{FeatureDone\|katepart\|Add interface to access highlighting information, port html-export plugin\|mail@milianw.de\|Milian Wolff}}
	{{FeatureInProgress\|kdecore\|Move event-filter installation out of KApplication and into a new class\|lemma@confuego.org\|Michael Leupold}} {{FeatureInProgress\|kdecore\|Polkit-1 backend for KAuth\|drf@kde.org\|Dario Freddi}}		{{FeatureInProgress\|kdecore\|Move event-filter installation out of KApplication and into a new class\|lemma@confuego.org\|Michael Leupold}} {{FeatureInProgress\|kdecore\|Polkit-1 backend for KAuth\|drf@kde.org\|Dario Freddi}}
	{{FeatureInProgress\|kdeui\|Support floating point font sizes\|christoph@maxiom.de\|Christoph Feck}}		{{FeatureInProgress\|kdeui\|Support floating point font sizes\|christoph@maxiom.de\|Christoph Feck}}

← Older revision		Revision as of 14:19, 19 November 2009
(2 intermediate revisions not shown)
Line 3:		Line 3:
	http://farm3.static.flickr.com/2602/4104932135_3cb3f69536_m.jpg		http://farm3.static.flickr.com/2602/4104932135_3cb3f69536_m.jpg

-	digiKam developer Gilles Caulier hacked with Kåre on the Acquire Images Kipi plugin and found some problems with the libksane Twain implementation.	+	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, 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.	+	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		http://farm3.static.flickr.com/2624/4112660504_f043577c72_m.jpg

-	In discussions with Luka, Alex and Aleix 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.	+	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		http://farm3.static.flickr.com/2677/4105703894_93aa13a157_m.jpg

-	Gilles and Marcel shared initial thoughts about future image versioning support in digiKam and wishes to support grouping of pictures, Gilles and Andi 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.	+	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		http://farm3.static.flickr.com/2697/4105692984_057c594d9c_m.jpg

-	With Michael, 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.	+	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		http://farm3.static.flickr.com/2627/4104946465_95cedd5cd7_m.jpg
Line 24:		Line 24:
	http://farm3.static.flickr.com/2577/4105716638_9028bb4153_m.jpg		http://farm3.static.flickr.com/2577/4105716638_9028bb4153_m.jpg

-	Alex ~~Fiestas~~ and Aleix ~~Pol~~, 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.	+	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		http://farm3.static.flickr.com/2645/4104942389_5aa3ae14cd_m.jpg

-	Besides the usual amount of bug hunting and fixing, Kåre ~~Särs~~, 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.	+	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		http://farm3.static.flickr.com/2670/4106816151_d6762945a6_m.jpg
Line 53:		Line 53:
	http://farm3.static.flickr.com/2593/4105707132_bf43dc25c1_m.jpg		http://farm3.static.flickr.com/2593/4105707132_bf43dc25c1_m.jpg

-	Luka ~~Renko~~ 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	+	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.		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		http://farm3.static.flickr.com/2742/4105701938_d25db886e5_m.jpg

-	Michael ~~G. Hansen~~ worked on two areas: geolocation and face recognition.	+	Michael worked on two areas: geolocation and face recognition.
	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, andhow to store such information in image metadata.		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, andhow to store such information in image metadata.

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

-	Andi ~~Clemens~~ 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.	+	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		http://farm3.static.flickr.com/2547/4105709488_b341b5eb0a_m.jpg

-	Marcel ~~Wiesweg~~ 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.	+	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:		Note: All event photos are available on Flickr group given below:

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