KDE TechBase - User contributions [en]

Talk:Development/Tutorials/Session Management

2009-04-11T12:29:05Z

Milliams:

This tutorial really shouldn't be linked under the 'Introduction To KDE 4 Programming' section on [[Development/Tutorials]]. IT doesn't fit in _at all_ with the rest of the series either in terms of flow or in target audience. Perhaps you should find another place to link to it from, otherwise I will move the link myself [[User:Milliams|milliams]] 19:56, 5 April 2009 (UTC)

: When creating the turotial, I've asked at the diskussion page of Development/Turorials (http://techbase.kde.org/index.php?title=Talk:Development/Tutorials&oldid=36921) where to put it because I wasn't shure in which category it fits. Someone has than put it to 'Introduction To KDE 4 Programming'. However, I thing also that this category isn't perfect and I'm fine with another category. You can just move it to another place, where you think it fits better.

::Ok, I've moved it to the '' Basics'' category. [[User:Milliams|milliams]] 12:29, 11 April 2009 (UTC)

Development/Tutorials

2009-04-11T12:27:44Z

Milliams: Move session management tutorial link. This is better but maybe still not perfect

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

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

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

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

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

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

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

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

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

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

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

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

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

== Testing And Debugging ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Documentation ==

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

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

== Application Automation and Scripting ==

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

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

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

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

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

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

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

; [[Development/Tutorials/Kross/Scripts-as-KPlugins|Load Kross Scripts as KPlugins]]
:''This tutorial provides a step-by-step introduction how to load scripts as KPlugins.''

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

{{:KOffice/Plugin Tutorials}}

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

== Plugins and KParts ==

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

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

== Search and Metadata ==

=== Strigi ===

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

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

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

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

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

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

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

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

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

== Hardware Awareness (Solid) ==

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

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

== Privileged Applications (PolicyKit) ==
; [[Development/Tutorials/PolicyKit/Introduction|Introduction to PolicyKit]]
:''A straight-forward introduction to what PolicyKit is, and how it can be useful for your next application requiring super-user privileges or user authentication''
; [[Development/Tutorials/PolicyKit/Helper_HowTo|Using the caller-helper model to perform actions as root]]
:''This tutorial will teach you how to get your application to perform some actions as root in a completely safe and easy manner, if the user is authorized to, by using PolicyKit and the caller-helper technique''
; [[Development/Tutorials/PolicyKit/KCM_HowTo|Getting root privileges in KCM Modules]]
:''This tutorial will teach you how to create KCModules able to save settings as root''

== Multimedia (Phonon) ==

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

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

== Plasma ==

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

== Communication (Decibel) ==

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

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

== Personal Information Management (Akonadi) ==

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

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

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

== Kate / Kwrite ==

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

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

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

==Printing==

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

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

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

== Get Hot New Stuff ==
; [[Development/Tutorials/K_Hot_New_Stuff2|New introduction to Get Hot New Stuff 2]]
:''A short tutorial about how to use KHotNewStuff2 in your application.''

* old links for KNS1 content:
; [[Development/Tutorials/Introduction to Get Hot New Stuff|Introduction to Get Hot New Stuff]]
:''An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.''

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

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

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

== Other programming languages ==

=== Python ===

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

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

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

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

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

=== Ruby ===

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

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

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

=== Shell ===

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

== Graphics Programming ==

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

== Using the KDE Games Libraries ==
;[[Development/Tutorials/Games/KStandardGameAction| KStandardGameAction]]
:''Using libkdegames to make your game fit the kdegames standard''
;[[Development/Tutorials/Games/Highscores| Highscores]]
:''Implementing a simple highscore table into your game''
;[[Development/Tutorials/Games/Theme Selector| Theme Selector]]
:''Using the libkdegames theme selection dialog''
;[[Development/Tutorials/Games/Palapeli Patterns| Palapeli Patterns]]
:''Creating a pattern for Palapeli''
=== KGLEngine ===
;[[Development/Tutorials/Games/kglengine/kglengine-simpleBox| installation and your first KGLItem]]
:''start your first kglengine application''
;[[Development/Tutorials/Games/kglengine/kglengine-motion| item motion]]
:''how to move kglitem''
;[[Development/Tutorials/Games/kglengine/kglengine-collision| collision detection]]
:''how to detect collision and interact ''
;[[Development/Tutorials/Games/kglengine/kglengine-texture| texture and color]]
:''apply texture and color for your items ''
;[[Development/Tutorials/Games/kglengine/kglengine-effects| particles and shadow effects]]
:''add some nice effects ''
;[[Development/Tutorials/Games/KGLEngine2d| kglpong]]
:''Now use our knowledge to make a pong''

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

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

== Other tutorials ==

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

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

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

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

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

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

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

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

[[Category:KDE4]]

Talk:Development/Tutorials/Session Management

2009-04-05T19:56:00Z

Milliams: This tutorial doesn't belong where it is

Projects/Games

2008-08-16T17:31:41Z

Milliams: /* Status */

{{Template:I18n/Language Navigation Bar|Projects/Games}}
Intro to do

== The Game Categories ==
*[[/Arcade Games|Arcade games]]
*[[/Board Games|Board Games]]
*[[/Card Games|Card games]]
*[[Dice Games]]
*[[Logic Games]]
*[[/Tactic and Strategy|Tactic and Strategy]]
*[[Toys]]

==Development==

* [[/Maintainers| Game's maintainers]]
* [[/UI and usability|UI and usability]]
* [[/libkdegames Usage|libkdegames Usage]]
* [[/Ideas| KDEGames Ideas and Proposals]]
* [[/Proposed_Games|Proposed new games]]

==Status==

* [[/Status KDE 4.0|Status KDE 4.0]]
** [[/Documentation_progress|Documentation progress]]
** [[/Icons_ToDo|Icons_ToDo]]
* older pages:
** [[/Status_Ready|Ready]]
** [[/Status_Should_be_Ready|Should be ready]]
** [[/Status_Playground|kdegames playground (kdegame's candidate or unready) ]]
** [[/Status|old status page]]

* [[/Akademy 2008 Notes|Akademy 2008 Notes]]

==Meeting==

===IRC===

We are doing meeting on [irc://irc.kde.org/#kdegames IRC] every month to talk about the games development.

[[/IRC Meeting|Next Meeting : July 1st/2008 20:00 UTC]]

[[Category:KDEGames]]

Projects/Games

2008-08-16T17:23:02Z

Milliams: /* Status */

{{Template:I18n/Language Navigation Bar|Projects/Games}}
Intro to do

== The Game Categories ==
*[[/Arcade Games|Arcade games]]
*[[/Board Games|Board Games]]
*[[/Card Games|Card games]]
*[[Dice Games]]
*[[Logic Games]]
*[[/Tactic and Strategy|Tactic and Strategy]]
*[[Toys]]

==Development==

* [[/Maintainers| Game's maintainers]]
* [[/UI and usability|UI and usability]]
* [[/libkdegames Usage|libkdegames Usage]]
* [[/Ideas| KDEGames Ideas and Proposals]]
* [[/Proposed_Games|Proposed new games]]

==Status==

* [[/Status KDE 4.0|Status KDE 4.0]]
** [[/Documentation_progress|Documentation progress]]
** [[/Icons_ToDo|Icons_ToDo]]
* older pages:
** [[/Status_Ready|Ready]]
** [[/Status_Should_be_Ready|Should be ready]]
** [[/Status_Playground|kdegames playground (kdegame's candidate or unready) ]]
** [[/Status|old status page]]

* [[Akademy 2008 Notes]]

==Meeting==

===IRC===

We are doing meeting on [irc://irc.kde.org/#kdegames IRC] every month to talk about the games development.

[[/IRC Meeting|Next Meeting : July 1st/2008 20:00 UTC]]

[[Category:KDEGames]]

Category:Usability

2008-07-16T18:54:31Z

Milliams:

For pages related to usability. See http://usability.kde.org

See also
* [[:Category:Documentation]]
* [[:Category:Programming]]
* [[:Category:Artwork]]

Projects/Usability/HIG

2008-07-16T18:52:36Z

Milliams: Add to Usability category

__NOTOC__
Please add any guidelines questions or requests to the [[Projects/Usability/HIG_Questions|HIG Questions]] page.

Also see the [http://developer.kde.org/documentation/standards/kde/style/basics/index.html KDE3 User Interface Guidelines] and the draft notes for the [http://wiki.openusability.org/guidelines/ KDE4 Human Interface Guidelines].

==Index==
===C===
* [[Projects/Usability/HIG/Capitalization|Capitalization]]
* [[Projects/Usability/HIG/Check_Box|Check Box]]
* [[Projects/Usability/HIG/Combo_Box|Combo Box]]
===E===
* [[Projects/Usability/HIG/Ellipsis|Ellipsis]]
===K===
* [[Projects/Usability/HIG/Keyboard_Accelerators|Keyboard Accelerators]]
* [[Projects/Usability/HIG/Keyboard_Shortcuts|Keyboard Shortcuts]]
===M===
* [[Projects/Usability/HIG/Menu_Bar|Menu Bar]]
===R===
* [[Projects/Usability/HIG/Radio Buttons|Radio Buttons]]
===S===
* [[Projects/Usability/HIG/Slider|Slider]]
* [[Projects/Usability/HIG/Spin_Box|Spin Box]]
===W===
* [[Projects/Usability/HIG/Warning_and_Error_Messages|Warning and Error Messages]]

[[Category:Usability]]

Projects/Usability

2008-07-16T18:51:33Z

Milliams: Add to Usability category

The KDE Usability Project aims to improve KDE usability and user experience through:

* Educating developers about usability practices
* Conducting usability activities to help gather feedback from users
* Working with projects and help design usable user interfaces

Learn more at the [http://usability.kde.org KDE Usability Project] website.

= [[Projects/Usability/HIG|KDE4 Human Interface Guidelines]] =

If you have questions about guidelines or want to request a missing guideline or change to a guideline, please put it on the [http://techbase.kde.org/Projects/Usability/HIG_Questions HIG Questions] page. We will refer to this page during the [http://season.openusability.org Season of Usability] KDE4 HIG project.

= User Research Profiles =

The purpose of this template is to provide a place to document an application's user research information for reference during development. Top level items are information everyone in the project should be aware of. Some of the details in the lower sections may take some work and discussion within the project to complete.

[http://techbase.kde.org/index.php?title=Projects/Usability/Project_User_Research_Template Project User Research Template]

== Projects ==

These projects have been called to work on their user research profiles:

* [[Projects/Plasma/PURP|Plasma]]
* [[Projects/Okular/User_Research_Profile|Okular]]

[[Category:Usability]]

Talk:Development/Tutorials/Using KXmlGuiWindow

2008-05-28T20:30:35Z

Milliams: /* Example code line numbering */

I had a couple of problems:

In order to make cmake find my installed header files, I needed to specify -DCMAKE_INSTALL_PREFIX=/home/kde-devel/kde

and still it wouldn't compile. I had to change it to use KXmlGuiWindow instead of KMainWindow as it didn't seem to be able to use setupGUI();

/Sune

== Why KXmlGuiWindow??? ==

Hi! I can't understand why KXmlGuiWindow is used. There are no any xml files. And it's used in the tutorial as KMainWindow.
Also the title is "How To Use KMainWindow".
So, from my point of view it needs to be improved.
--[[User:Powerfox|Powerfox]] 00:29, 29 July 2007 (CEST)
: Why? This page is the base for the next part, "using KAction". Giving a correct skeleton now can save some work later. -- [[user:Pino|pino]] 15:52, 29 November 2007 (CET)

== Example code line numbering ==

Hello, I am working through this tutorial and am having a problem cutting and pasting the code from this page to my text-editor. The line number information is copied with each selection. This means that I have to go back through it and delete the numbers 1, 2, 3, 4, 5.... (and extra spaces and such) for each line. the first tutorial IMO seemed to do this in a more copy-paste friendly way. Note I do like having the line numbers, but I would also like to be able to copy-paste the code easily.
:As I answered to a similar post on one of the other tutorials, I can't replicate this problem. With Konqueror 3 and 4, Firefox 2 and Opera I can select the code without selecting the line numbers too. What browser are you using? --[[User:Milliams|milliams]] 22:30, 28 May 2008 (CEST)

Talk:Development/Tools/Automoc4

2008-05-16T18:50:20Z

Milliams: New page: This is probably best suited under Development/Tools or under Projects --~~~~

This is probably best suited under [[Development/Tools]] or under [[Projects]] --[[User:Milliams|milliams]] 20:50, 16 May 2008 (CEST)

Schedules/KDE4/4.1 Feature Plan

2008-05-05T15:15:53Z

Milliams: Update text to reflect current release mode

This is a list of planned features for KDE 4.1. '''The deadline for adding entries to this page has already passed'''.

Any features which are not mentioned on this page must be rescheduled for 4.2 and added to the list at [[Schedules/KDE4/4.2 Feature Plan]].

Please ensure that any entries you have on this page are kept up to date with respect to their status (''todo'', ''in-progress'' or ''done'').

Legend:
* todo => not started yet
* in-progress => started, but not completed yet
* done => completed
__TOC__
= kdelibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|various|[[Projects/Widgets_and_Classes | Classes and Widgets]] that should be moved from others modules up into kdelibs|kde-core-devel@kde.org|The Core Developers}}
{{FeatureDone|kdeui|Add KFadeWidgetEffect to easily add fading UI transitions to KDE applications|kretz@kde.org|Matthias Kretz}}
{{FeatureDone|kdeui|Make icon naming spec compliant 3rd party icon themes like Tango or gnome-icon-theme work correctly.|jpetso@gmx.at|Jakob Petsovits}}
{{FeatureDone|kross|Add QtScript support|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KHTML|Support CSS3 Media Queries|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|KHTML|Efficient smooth scrolling|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|Phonon KCM|More UI feedback|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|VideoWidget snapshot function|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|better integration of pulseaudio|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|make AbstractMediaStream/StreamInterface threadsafe|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|allow backend switching on the fly|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|Phonon|add Port class for fine grained control over data flow between Phonon objects|kretz@kde.org|Matthias Kretz}}
{{FeatureDone|Phonon|subtitle, audio track selection|kretz@kde.org|Matthias Kretz and Ian Monroe}}
{{FeatureTodo|Phonon|DVD menu selection support|imonroe@kde.org|Ian Monroe}}
{{FeatureInProgress|Phonon|"low-level" PCM I/O with at least an ALSA implementation|kretz@kde.org|Matthias Kretz and Ian Monroe}}
{{FeatureTodo|Phonon|update device preference on the fly|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|kdeui|Goya, a framework for inserting controls into itemviews in a really easy and fast way|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureInProgress | kdeui | Rich textedit widget supporting most rich text features. | steveire@gmail.com | Stephen Kelly }}
{{FeatureInProgress|kdeui|Shortcut schemes for KDE applications|adymo@kdevelop.org|Alexander Dymo}}
{{FeatureDone|kmimetypetrader/kbuildsycoca|Replace use of profilerc for ordering applications with new mimeapps.list standard|faure@kde.org|David Faure}}
{{FeatureInProgress|knewstuff|Support caching, and speed up the interface through use of Models/Views and goya|jeremy@scitools.com|Jeremy Whiting}}
{{FeatureInProgress|Phonon KCM|Handle advanced devices|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|KDEPrint|Reintroduce KDEPrint in some form, depending on what Qt4.4 delivers.|john@layt.net|john Layt}}
{{FeatureInProgress|KDEPrint|Add CUPS Options tabs to QPrintDialog to support n-up, page borders, banner pages, page labels, mirror pages, job scheduling, and manual CUPS options.|john@layt.net|John Layt}}
{{FeatureTodo|KDEPrint|Add framework for standard actions for 'Send to...' for e-mail, fax, etc by printing to PDF/PS.|john@layt.net|John Layt}}
{{FeatureTodo|KDEPrint|Migrate FilePrinter class from Okular to enable file printing for all apps via QPrinter, modify to utilise new Qt4.4 features. To be discussed on k-c-d first.|john@layt.net|John Layt}}
{{FeatureInProgress|KIO|speed limits on KIO Transfers|nolis71cu@gmail.com|Manolo Valdes}}
{{FeatureInProgress|kdeui|Printing of shortcuts from the shortcut dialog|apaku@gmx.de|Andreas Pakulat}}
{{FeatureDone|Kate Part|Annotation framework for the editor|apaku@gmx.de|Andreas Pakulat}}
{{FeatureInProgress|KJS|Bytecode interpreter and performance improvements|maksim@kde.org|Maks Orlovich}}
{{FeatureInProgress|KHTML|Sync class and file structure with WebKit to prepare merging|porten@kde.org|Harri Porten}}
{{FeatureInProgress|KHTML|contentEditable/designMode implementation|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|KCalenderSystem|Complete migration of Jalali, Hijri, and Hebrew calendars to new code base.|john@layt.net|John Layt}}
{{FeatureTodo|KCalenderSystem|Add new calendar systems: Indian Civil (Saka), Ethiopean, Chinese, Pure Julian, Pure Gregorian. (Note, not all may live in kdelibs or be available as a global calendar system)|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement KLocale based methods to return weekend days and day of religious observance. Currently KCalendarSystem provides dayOfPray(), but for Gregorian this is not correct in all locales where it is used. Currently KDatePicker hardcodes Saturday and dayOfPray() as weekend days which may not be correct in all locales. To be discussed first on k-c-d and with kdepim.|john@layt.net|John Layt}}
{{FeatureDone|dnssd|Models for service browser and domain browser.|qbast@go2.pl|Jakub Stachowski}}
{{FeatureTodo|KHTML|Adaptable/Scriptable workarounds for broken websites.|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|KHTML|support for borders-* properties from the CSS3 Background and Borders Module|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|KHTML|support for Audio/Video tags from the HTML5 draft specification|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|KHTML|prospective loading of other network resources while waiting for arrival of blocking scripts|germain@ebooksfrance.org|Germain Garand}}
{{FeatureInProgress|KJS|Public API for extensions. Possibly analog to JavaScriptCore's C API.|porten@kde.org|Harri Porten}}
{{FeatureTodo|KTextEditor|Several interface extensions (e.g. open/save filter)|kwrite-devel@kde.org|Kate Developers}}
{{FeatureTodo|KTextEditor|Plugin for basic collaborative editing|kwrite-devel@kde.org|Kate Developers}}
{{FeatureInProgress|Kate Part|Scripting support for indentation and little helpers|kwrite-devel@kde.org|Kate Developers}}
{{FeatureTodo|Kate Part|Input modes to allow e.g. vim-like editing|kwrite-devel@kde.org|Kate Developers}}
{{FeatureDone|KIO|Implement support for inline editing in KFileItemDelegate|fredrik@kde.org|Fredrik Höglund}}
{{FeatureDone|KIO|Add support for drawing text shadows in KFileItemDelegate|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Emoticons lib|An emoticons library so each applications doesn't have to implement the same things over and over again |brandon.ml@gmail.com|Carlo Segato}}
{{FeatureInProgress|KFile|Implement fd.o desktop-bookmark-spec for KFilePlacesModel|nf2@scheinwelt.at|Norbert Frese}}
{{FeatureTodo|kdeui| Support for About Data of libs and modules used by a program |kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|kdeui|Drop-in replacement for QFontComboBox, with more informative previews in non-Latin1 locales|caslav.ilic@gmx.net|Chusslove Illich}}
{{FeatureInProgress|KAboutLicense|Select licenses by keyword, to centralize license info texts for frequent licenses.|caslav.ilic@gmx.net|Chusslove Illich}}
{{FeatureTodo|KIO|KIO::AuthInfo and PasswordDialog: optional fields (like "domain"); optional anonymous switch and flag to suppress KIO's password caching|nf2@scheinwelt.at|Norbert Frese}}
{{FeatureTodo|kdeui|Support for KConfigGroup in KConfigSkeleton|aseigo@kde.org|Aaron Seigo}}
|}

= kdepimlibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Akonadi|Move the Akonadi development library from kdepim.|vkrause@kde.org|Volker Krause}}
{{FeatureInProgress|Akonadi|Item size ([[Projects/PIM/Akonadi#Core|details]])|thomas.mcguire@gmx.net|Thomas McGuire}}
{{FeatureTodo|Akonadi|Payload serialization format versioning ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureTodo|Akonadi|Item streaming in ItemSync/ResourceBase ([[Projects/PIM/Akonadi#Core|details]])|tomalbers@kde.nl|Tom Albers}}
{{FeatureInProgress|Akonadi|API for additional item parts ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org,tokoe@kde.org|Volker Krause/Tobias Koenig}}
{{FeatureInProgress|Akonadi|Infrastructure for showing additional dialogs from agents/resources ([[Projects/PIM/Akonadi#Core|details]])|tomalbers@kde.nl|Tom Albers}}
{{FeatureTodo|Akonadi|Allow to limit ItemFetchJob to current cache content ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureInProgress|Akonadi|Fix API for item/collection modifications ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureTodo|Akonadi|Error reporting ([[Projects/PIM/Akonadi#Core|details]])|tokoe@kde.org|Tobias Koenig}}
{{FeatureTodo|gpgme++2|newly designed gpgme++ (multithreaded, exceptions, less event loop integration: better for Windows)|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureTodo|kpimutils|Change linklocator to use the new emoticon lib|brandon.ml@gmail.com|Carlo Segato}}
|}

= kdebase-apps =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Dolphin|Details-view: Allow to open folders as tree (turned off per default).|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|Dolphin|Refactor view-action handling to a DolphinViewActionHandler to share more code with DolphinPart|faure@kde.org|David Faure}}
{{FeatureDone|Konqueror|Re-implement Copy To / Move To in the popup menu|faure@kde.org|David Faure}}
{{FeatureDone|Konqueror|Separate Home URL settings in konquerorrc and kfmrc; save toolbar settings into the profile automatically|faure@kde.org|David Faure}}
{{FeatureDone|Dolphin|Simplify selecting of files in the single-click mode (based on http://aseigo.blogspot.com/2006/04/icons.html).|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Raptor|The KDE4-Application-Menu}}
{{FeatureInProgress|Dolphin|Provide optional tooltips for files and directories.|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Dolphin|Tabs|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Konqueror|Bring back the large tooltip like in kde3|faure@kde.org|David Faure}}
{{FeatureInProgress|Konqueror|Session management (save/restore session/restore from crash).|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|Konqueror|Support for undo closed window.|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureDone|Konqueror|Allow to configure the Dolphin KPart within the Konquerors settings dialog.|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|KInfocenter|Improve code and usability.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureDone|KInfocenter|Reimplement partitions list.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureDone|KInfocenter|Reimplement memory module.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureDone|KInfocenter|Reimplement PCI module.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureTodo|KInfocenter|Reimplement Network module.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
|}

= kdebase-workspace =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Plasma|Kickoff orientation dependent layout|wstephenson@kde.org|Will Stephenson}}
{{FeatureDone|kmenuedit|Restore menu system|montel@kde.org|Laurent Montel}}
{{FeatureDone|KCM autostart|Configure autostart desktop file|montel@kde.org|Laurent Montel}}
{{FeatureDone|Plasma|improve fail to launch and needs
config|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|ksmserver|UI for selecting WMs|l.lunak@kde.org|Luboš Luňák}}
{{FeatureDone|Plasma|polish kickoff|wstephenson@kde.org|Will Stephenson}}
{{FeatureDone|Plasma|toolbox improvements |aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|GHNS2 plasma themes|jeremy@scitools.com|Jeremy Whiting}}
{{FeatureDone|Plasma|Resizable, relocatable panel|binner@kde.org|Stephan Binner}}
{{FeatureInProgress|Solid|Refactor Solid::Control networking|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|Solid|Backend for NetworkManager 0.7|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|System Settings|Filtering/Lazy load category modules|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|KSysGuard|Monitor process I/O|tapsell@kde.org|John Tapsell}}
{{FeatureInProgress|Plasma|Mac-like menu bar plasmoid|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Color KCM|Add 'smart setting' of extended colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Add KDE3 scheme import|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Query kwin for supported colors; add full set of kwin colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KDEPrint|reintroduce KDEPrint Print Management tools, e.g. KCM, kprinter, kjobviewer, etc. Depends upon progress of kdelibs side of KDEPrint and Qt4.4 feature set.|john@layt.net|john Layt}}
{{FeatureTodo|System Settings|Administrator mode support|wstephenson@kde.org|Will Stephenson}}
{{FeatureTodo|krunner|Revamp GUI.|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Plasma|keyboard shortcuts|Chani Armitage|chanika@gmail.com}}
{{FeatureInProgress|Plasma|webkit widget|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|shared timer in engines|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|welcome plasmoid|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|dashboard widget support|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Plasmagik packaging (and package classes)|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Plasma|Scriptengines|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Plasma|QtScript scriptengine|richmoore44@gmail.com|Richard Moore}}
{{FeatureInProgress|Plasma|Filebrowser Plasmoid|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Plasma|Improve QtScript support|richmoore44@gmail.com|Richard Moore}}
{{FeatureInProgress|Plasma|Zooming User Interface|chanika@gmail.com|Chani Armitage}}
{{FeatureInProgress|Plasma|Multiple Desktop Containments|chanika@gmail.com|Chani Armitage}}
{{FeatureInProgress|Plasma|Networkmanager Plasmoid and DataEngine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureInProgress|Plasma|API changes [[Projects/Plasma/Tokamak1]]|panel-devel@kde.org|Plasma team }}
{{FeatureInProgress|Plasma|Panel Toolbox|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Panel changes to make it work with the new default theme|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Generic folder view applet/containment, that can also be used as the desktop background (showing the desktop folder).|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Krunner|Configuration options for blacklisting, user ranking, runner ranking, learning|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Simple learning|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Simple GUI for above options|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Runners able to share parsing|mumismo@gmail.com|Jordi Polo}}
{{FeatureInProgress|Krunner|Configuration dialog for KRunner|ryan.bitanga@gmail.com|Ryan P. Bitanga}}
{{FeatureTodo|Krunner|Noun-Verb support|ryan.bitanga@gmail.com|Ryan P. Bitanga}}
{{FeatureDone|Plasma|Temperature sensing in the device engine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureDone|Plasma|Video data in the device engine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureTodo|Plasma|New plasma themes|nuno@oxygen-icons.org|Nuno Pinheiro}}
{{FeatureTodo|Plasma|physics-based animator|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Improve the base set of plasmoids|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|New wallpapers|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|New way of handling wallpapers and different sizes (package format, and so on...)|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Top-level windows plasmoids|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureDone|Plasma|change showConfigurationInterfaction to createConfigurationInterface|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Plasma::Service |aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|panel hiding |aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|KWin|non-linear animations also for KWin|sebas@kde.org|Sebastian Kuegler}}
{{FeatureInProgress|KWin|Compiz's wobbly like effect for KWin|cedric.borgese@gmail.com|Cédric Borgese}}
{{FeatureTodo|KDM|Theme KDM (login manager) by default|uwolfer@kde.org|Urs Wolfer}}
{{FeatureTodo|Splash screen|New default splashscreen|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Nepomuk|Simple Desktop Search client based on Nepomuk search|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Plasma|Add a dataengine that implements galago-project Notifications DBus interface and a plasmoid which provides cute visualization of notifications along with nice and easy way to interact with them|dimsuz@gmail.com|Dmitry Suzdalev}}
{{FeatureInProgress|Plasma|loadDefaultSetup from a file, not hardcoded|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|ksmserver|Make the fade-to-gray logout effect work even when composite is disabled|fredrik@kde.org|Fredrik Höglund}}
|}

= kdebase-runtime =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|nepomuk|Service that monitors file rename and delete operations and updates the metadata accordingly. kded module already exists in playground. problem: depends on inotify.|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|KCM emoticons|Adding/editing/removing emoticons theme|brandon.ml@gmail.com|Carlo Segato}}
{{FeatureDone|KCM splash screen|Be able to install splash screen themes via GHNS2|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KCM icons|Be able to install icon themes via GHNS2|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|phonon-xine|snapshots in video widget|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|try to make VideoWidget work on GraphicsView|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|make states compatible to other backends|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|better support for pulseaudio (most work possibly in kdelibs)|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-gstreamer|Make phonon-gstreamer as released with Qt 4.4 fully integrate into KDE and add the features added to libphonon after libphonon 4.1|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|desktop ioslave|Add an ioslave that lists the contents of the desktop folder, and reports the names in the .desktop files instead of the actual file names.|fredrik@kde.org|Fredrik Höglund}}
{{FeatureDone|knotify|Add support for galago-like desktop notifications spec - if knotify will find a certain DBus service on session bus, it'll forward its popup notification events to this service |dimsuz@gmail.com|Dmitry Suzdalev}}
{{FeatureInProgress|Oxygen cursors|Oxygen cursor set|riccardo@kde.org|Riccardo Iaconelli}}
|}

= kdeaccessibility =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KMagnifier|Add color blindness simulation|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KMagnifier|Refactor color menu, re-add invert, add color-shift modes to help people with color blindness|mw_triad@users.sourceforge.net|Matthew Woehlke}}
|}

= kdeadmin =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KSystemLog|KSystemLog, a Log Viewer Tool. Move from kde-apps|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Do some refactoring in KCron|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Improve ergonomy and general interface|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Fix all existing bugs in KCron|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Convert KCron into a KCM Module, to use it in System Settings|nicolas.ternisien@gmail.com}}
{{FeatureInProgress|Environment Variables|Create a environment variables KCM Module|nicolas.ternisien@gmail.com}}
|}

= kdeartwork =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdebindings =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|Smoke2|Move modular Smoke2 to kdebindings-trunk.|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureTodo|PHP-Qt|Move PHP-Qt to kdebindings-trunk.|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureDone|kross|Move krossjava to kdebindings-trunk.|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|General|Wrap some more APIs (at least Akanodi for all languages and Plasma for C#)|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureTodo|Qyoto|Add delegate support for signal/slot connections.|kde-bindings@kde.org|KDE-bindings developers}}
|}

= kdeedu =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Kalzium|Clean up the database. I am syncing with the BlueObelisk data repository again. There we decided to remove the density (not a element property but a compound property. I also removed the mean weight. We think it is better to provide correct data than a lot (but partly wrong) data.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureDone|KAlgebra|Calculator Plasmoid|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|KAlgebra|Vector support|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|Step|A physics simulator, move from playground to kdeedu module |ks.vladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureDone|Kalzium|Update the snapshot of libavogadro to 0.6.1. This introduces a gazillion new possibilities for the 3D renderer and fixes many issues.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|Kalzium|Make use of the new libavogadro-version.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|Kalzium|Expose molecular editing features of libavogadro.|marcus@cryos.org|Marcus D. Hanwell}}
{{FeatureTodo|Kalzium|Port Kalzium's periodic table to use new QGraphicsView.|marcus@cryos.org|Marcus D. Hanwell}}
{{FeatureInProgress|KStars|Tool to predict Conjunctions|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureInProgress|Marble|DGML2 Support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|KDE-Version settings dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Port authors list from the Qt-About dialog to the KDE-About dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Qt-Version settings dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Improved KML support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|OpenStreetMap support using original OSM tiles|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Real Time Cloud-Cover|tackat@kde.org|David Roberts / Torsten Rahn}}
{{FeatureTodo|Marble|Map Contents translation|tackat@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Copy position to clipboard|tackat@kde.org|Torsten Rahn}}
{{FeatureDone|Marble|Create Tiles on compile time|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Mercator Projection|inge@lysator.liu.se|Inge Wallin}}
{{FeatureInProgress|Marble|More generic projection support|inge@lysator.liu.se|Inge Wallin}}
{{FeatureInProgress|Marble|Usage of Marble in non-widgets|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Export map to MxN pixel bitmap|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Support for MarbleWidget::setEnabled( bool )|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Layer Management Class|tokoe@kde.org|Tobias König}}
{{FeatureTodo|Marble|Plugin architecture for map layers|tokoe@kde.org|Tobias König}}
{{FeatureInProgress|KEduca|Rewrite of the classic test writing/taking application|matt@milliams.com|Matt Williams}}
{{FeatureDone|Parley|Redesigned main window|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|Parley|Vocabulary Plasmoid|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|KBruch and KPercentage|Merge in 1 app|pete@pmurdoch.com|Peter Murdoch}}
{{FeatureInProgress|Kalzium|Plasmoid to access Kalzium database|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|Step|Improve GUI for creating gas and softbody|ksvladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureInProgress|KAlgebra|Variables share between calculations|aleixpol@gmail.com|Aleix Pol}}
{{FeatureTodo|KTurtle|Export canvas as image|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Optional rulers/grid for canvas units|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Add command line|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Add a color picker|nielsslot@gmail.com|Niels Slot}}
{{FeatureInProgress|Parley|Declensions|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|Parley|Improved printing support|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureTodo|KLettres|Number support|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Add a Open File action|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Integrate an editor|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Plasmoid|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Visual indicator when letter is wrong|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|Kiten|Link radselect with kiten|jkerian@gmail.com|Joe Kerian}}
{{FeatureInProgress|Kiten|Sort output by dictionary/user selected sorting values|jkerian@gmail.com|Joe Kerian}}
{{FeatureTodo|Step|Use common constraints handling code for collisions|ksvladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureDone|Kig|Cubic-line intersection in case two of the three intersection points are already present|paolini@dmf.unicatt.it|Maurizio Paolini}}
{{FeatureTodo|Kig|Properties dialog for objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve construction of bisect lines.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve feedback when constructing objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|More geometric objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Script objects as macros (to be reused more than once).|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve the Cabri import filter.|pino@kde.org|Pino Toscano}}
|}

= kdegames =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KDiamond|New game, move to kdegames|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|KDiamond|Get themes with KNewStuff|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|KNetWalk|Better scoring system|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureDone|KNetWalk|Add support for loading new themes|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureDone|Kollision|Move to kdereview/kdegames|p.capriotti@gmail.com|Paolo Capriotti}}
{{FeatureDone|Kubrick|New game, 3D OpenGL - move to playground|ianw}}
{{FeatureDone|Kubrick|Polish up the features|ianw}}
{{FeatureDone|Kubrick|Port to Qt4 and KDE4|ianw}}
{{FeatureDone|KBlocks|Finish display of points and level|piacentini@kde.org}}
{{FeatureDone|KBlocks|Implement KNewStuff support|piacentini@kde.org}}
{{FeatureDone|KBlocks|Implement key/action/shortcut configuration|piacentini@kde.org}}
{{FeatureDone|KBlocks|Docbook|piacentini@kde.org}}
{{FeatureInProgress|KGoldRunner|Improved theming and animation|mikelima@cirulla.net}}
{{FeatureInProgress|KGoldRunner|Sound support and theming|mikelima@cirulla.net}}
{{FeatureInProgress|KSquares|Multiplayer support|josef}}
{{FeatureDone|KsirK|New game, move to kdereview|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|KsirK|Make network games work again|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|KBattleship|Bring back Zeroconf support for network games|qbast@go2.pl}}
{{FeatureInProgress|Kubrick|New game, 3D OpenGL - in kdereview|ianw}}
{{FeatureInProgress|KGGZ|Add kggzcore and kggzdmod libraries|josef}}
{{FeatureTodo|KBlocks|Add additional themes|piacentini@kde.org}}
{{FeatureInProgress|KBreakout|Finish it, and move it from playground to kdegames|fela.kde@gmail.com}}
{{FeatureTodo|KGGZ|Add new Qt4-based core client as successor to the old KDE3-based KGGZ|josef (now SoC proposal)}}
{{FeatureTodo|KGGZ|Fire-and-forget highscore submission for single-player games and client-to-client multiplayer games|josef)}}
{{FeatureTodo|KGoldRunner|Also see kdegames/kgoldrunner/TODO|ianw}}
{{FeatureTodo|KGoldRunner|Hot new stuff support for themes and levels|mikelima@cirulla.net}}
{{FeatureTodo|KGoldRunner|Startup screen|mikelima@cirulla.net}}
{{FeatureTodo|KMahjongg|Reimplement the Board Editor|piacentini@kde.org}}
{{FeatureDone|KMines|Add pause actions|eike.lange@kdemail.net}}
{{FeatureDone|KNetWalk|Configurable keyboard support|eike.lange@kdemail.net}}
{{FeatureTodo|KNetWalk|Support for custom and non-square board sizes|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KShisen|Port to KScoreDialog|piacentini@kde.org}}
{{FeatureTodo|Kubrick|See SVN file kubrick/TODO|ianw}}
{{FeatureDone|Kubrick|Move to KDE Games for 4.1|ianw}}
|}

= kdegraphics =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Gwenview|Undo system|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Gwenview|Fullscreen meta information|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Gwenview|Ability to open an image with another application|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Okular|Better Text-To-Speech integration: speech the whole document, the current page or the selection.|pino@kde.org|Pino Toscano}}
{{FeatureDone|Okular|Encryption support for ODF generator|bradh@kde.org}}
{{FeatureInProgress|Okular|Backward direction for text search.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Centralized text & graphics antialias configuration.|pino@kde.org|Pino Toscano}}
{{FeatureDone|Okular|EPub backend.|elylevy@cs.huji.ac.il|Ely Levy}}
{{FeatureInProgress|Okular|Improved form support (add missing types, handle the fields better).|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Gwenview|Support for tagging with Nepomuk|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Thumbnail bar in view and fullscreen modes|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Crop ratio|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|KIPI support|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Red eye correction|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Start page|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Okular|JavaScript support (mostly for PDF documents).|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Improved placement and sizing of the presentation mode: choose the screen to use, adapt to screen size changes.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Caret annotations.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|File attachment annotations (read only for now).|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Sound annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Link annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Improve annotation support: for existing types (rubber stamps, line, note, etc), and for the way they are constructed and handled.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Separate the "view properties" out of the Document, in a View class. Use it for the page view and the presentation mode.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Per-document zoom level.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|libksane|Move libksane to kdegraphics|kare.sars@kolumbus.fi|Kåre Särs}}
{{FeatureTodo|ksaneplugin|Replase libkscan with ksaneplugin|kare.sars@kolumbus.fi|Kåre Särs}}
|}

= kdemultimedia =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Dragon Player|A simple Phonon-based videoplayer application|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|Make Dragon indipendent from Xine|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|File Manager|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|play media dialog|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|slider changes|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|show info while playing audio files|ian.monroe@gmail.com|Ian Monroe}}
|}

= kdenetwork =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KGet|Group-Settings|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Torrent-Support|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Transfer-Settings|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Webinterface|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|Kopete|AIM offline messages|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|OTR Encryption support|michael_zanetti@gmx.net|Michael Zanetti}}
{{FeatureDone|Kopete|Status manager|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|Non-intrusive notification system|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|KGet|MultiSource-Downloading|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|Kopete|Bring back chat style selection via knewstuff2|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Kopete|ICQ 6 status icons|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|Kopete|MSNP15 implementation for MSN|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|UPnp Support|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|Updated contact list interface (uses Qt 4 rather than Qt 3)|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|Use notebook lid for auto away|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureTodo|Kopete|Update Kopete to better support Decibel|kopete-devel@kde.org|Kopete Developers}}
{{FeatureTodo|Kopete|use the new emoticons library|brandon.ml@gmail.com|Carlo Segato}}
{{FeatureInProgress|KGet|Nepomuk-Integration|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|KGet|Support mms://-protocol, see https://launchpad.net/libmms|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Global Speedlimits|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Setup libbtcore from KTorrent in KGet (to avoid dependency to extragear)|uwolfer@kde.org|Urs Wolfer}}
{{FeatureInProgress|KGet|Extend the TransferHistory to use SQLite and XML-Backends and display the information inside a kcategorizedview|jgoday@gmail.com|Javier Goday}}
{{FeatureTodo|Kopete|GroupWise chatroom support|wstephenson@kde.org|Will Stephenson}}
{{FeatureTodo|[http://decibel.kde.org Decibel]|Decibel, a framework for real time communication services. Move from playground/pim|info@basyskom.de|Tobias Hunger}}
{{FeatureDone|KRDC|Optional system tray icon (with quick access to bookmarks)|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Improved behavior of entering special keys for better workflow|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Zeroconf support (detecting remote desktop services in local network)|romnes@stud.ntnu.no|Magnus Romnes}}
{{FeatureInProgress|KRDC|Bookmark dock widget for quick access to bookmars, zero conf detected services and recently used connections|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Support for up- and downscaling VNC remote desktop|uwolfer@kde.org|Urs Wolfer}}
{{FeatureInProgress|Plasma|Network Manager Applet|cblauvelt@gmail.com|Christopher Blauvelt}}
|}

= kdepim =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KAddressbook|Ability to add LDAP search results to distribution lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|Indication of which resource folder a contact belongs to|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|Read-only view for contacts in read-only folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|copy/cut/paste context menu items|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAlarm|Allow use of multiple calendar resources|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Handle time zones and seasonal time changes properly|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Abolish alarm daemon and make kalarm trigger alarms itself|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Replace simple repetitions by recurrence sub-repetitions to reduce confusion|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|New option for display alarm text to be generated by a command|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|New option to specify reminder times in minutes|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Prevent multiple identical error messages accumulating for the same alarm|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Provide "don't show again for this alarm" option for command error messages|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Remember main window show/hide options used when KAlarm closed instead of setting them in Preferences dialog|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Simplification and improvements to alarm edit dialog|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Option to display alarms in centre of screen, with enable delay on buttons to avoid accidental acknowledgement|djarvie@kde.org|David Jarvie}}
{{FeatureDone|Kleopatra|Ability to search in internal and external certificates at the same time|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kleopatra|General UI Server|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|Kleopatra|New, tabbed, mainwindow design|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|KMail|Ability to create hyperlinks in HTML messages|steveire@gmail.com|Stephen Kelly}}
{{FeatureDone|KMail|Ability to easily create todos with reminders from emails|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Ability to open messages from search results when the reader is hidden|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better invitation update emails showing what changed|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better reminder visualization in very small events|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better, natural language search criteria names|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Clickable status columns|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Client side configurability of warnings in shared folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Colored ribbons for indication of signing and encryption status in the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Configuration option for whether invitation emails are automatically deleted or not when having been acted upon|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Copy/paste and drag and drop from/to the mail composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Decryption on demand in reader window|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Display of quota information in foldertree tooltips|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop and copy and paste support in the search result viewer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop from the mail reader window and mime-tree viewer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop of folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Editing of attachments from the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Export and import of filters|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Favorites Folder|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Folder quicksearch|m.koller@surfeu.at|Martin Koller}}
{{FeatureDone|KMail|Harmonization of actions in main and standalone mail reader windows|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|IMAP Server storage of non-standard flags|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Improved TNEF attachment handling|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Improved quota warnings|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Initialize full search from quicksearch on request|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Override font and fontsize for standalone message viewers|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Per-folder identity configurability|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Recursive IMAP cache troubleshooting|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Resizable recipients area in composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for creating new mails based on received mails (Resend)|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for immediate sync of resource folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for soft line breaking|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Tab navigation through groups in the address completion|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Text snippets with shortcuts and variable expansion in the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Warning about active out-of-office scripts|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|lost+found recovery of locally changed folders that lose access rights|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KNotes|Ability to print notes|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KonsoleKalendar|Support "file" and "localdir" resources|winter@kde.org|Allen Winter}}
{{FeatureDone|Kontact|Config option to close despite system tray|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Harmonization of component naming in sidebar, configuration, summary view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Right-aligned component navigation toolbar|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Ubiquitous sync actions|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Ability to have both distribution lists and addresbook extension visible|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Aggregated reminders view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Better default resource colors|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Drag and drop of attachments|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Faster initial loading of kolab resources|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Forwarding and delegation of invitations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Improved coloring of agenda view items|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Improved event printing|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Merge of the attachment view in into the main page|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Merge of the free-busy and attendee views for easier scheduling|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Month view scrolling, paging, mouse-wheeling|tom_t@gmx.at|Thomas Thrainer}}
{{FeatureDone|KOrganizer|More readable Kolab resource folder labels|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Redesigned incidence editor UI|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Side-by-side calendar view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Support for by-value attachments|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Timeline calendar view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Rich text incidence editor|mike@mikearthur.co.uk|Mike Arthur}}
{{FeatureDone|KOrganizer|Hide/Show reminder daemon icon in the systeay|winter@kde.org|Allen Winter}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Column-specific whatsthis-help| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Combined search and add task widget| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Drag&Drop| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|File management (file->load)| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Managing history| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Tracking tasks by active applications| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Whatsthis-help dependent on if a task has been created| |Thorsten Stärk}}
{{FeatureInProgress|Akregator|Support for syncing the feed list with Google Reader |osterfeld@kde.org|Frank Osterfeld}}
{{FeatureInProgress|KAlarm|New option to restrict alarms to working hours|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|Kleopatra|OpenPGP support|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureInProgress|KMail|HTML Signatures|yez@familieschepers.nl|Edwin Schepers}}
{{FeatureInProgress|KNotes|Zeroconf support for sending notes on LAN|qbast@go2.pl|Jakub Stachowski}}
{{FeatureInProgress|Kontact|New Planner summary; combines Appointment+To-do+SpecialDates into 1 pretty summary|winter@kde.org|Allen Winter}}
{{FeatureInProgress|KOrganizer|New To-do View (model/view)|tom_t@gmx.at|Thomas Thrainer}}
{{FeatureInProgress|KOrganizer|New Month View (qgraphicsitem)|bvirlet@kdemail.net|Bruno Virlet}}
{{FeatureInProgress|KPilot|Finish Keyring conduit, base conduit code and test cases, category syncing|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureTodo|Akregator|Basic support for enclosures (Displaying links, mimetype and size)|osterfeld@kde.org|Frank Osterfeld}}
{{FeatureTodo|KAlarm|Option to display alarm only if pre-alarm command succeeded|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application| christian_weilbach@.web.de|Christian Weilbach}}
{{FeatureTodo|Kleopatra|Konqueror and Dolphin Kleopatra plugins|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureTodo|KMail|Aggregated attachment view in the mail header area of the reader window|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KMail|Improved error messages and audit log for cryptographic operations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|Kontact|Support for Kontact wide profiles|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Ability to jump to the right day in the agenda from invitation mails|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Drag and drop in the free-busy view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for comments in replies to invitations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for extended free-busy lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Blog-styled journal view|mike@mikearthur.co.uk|Mike Arthur}}
{{FeatureTodo|KOrganizer|Blogging KResource|mike@mikearthur.co.uk|Mike Arthur}}
{{FeatureTodo|KPilot|Port old conduits to new base conduit architecture and KDE4/Qt4|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureTodo|KMail|Port to use KRichTextEdit|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|KBlogger|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|KNode|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
|}

= kdesdk =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Cervisia|New context menu entry "Add to Ignore List"|christian.loose@hamburg.de|Christian Loose}}
{{FeatureDone|Lokalize|Move this application (formerly known as Kaider) from extragear|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Cervisia|A file view based on KDirModel|christian.loose@hamburg.de|Christian Loose}}
{{FeatureInProgress|Lokalize|various Translation Memory enhancements|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|XLIFF support|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|KBugBuster|Make it work|fabiolocati@gmail.com|Fabio Locati}}
{{FeatureInProgress|KCachegrind|Everything working again|josef.weidendorfer@gmx.de|Josef Weidendorfer}}
{{FeatureInProgress|Kate|Session plasmoid|montel@kde.org|Laurent Montel}}
{{FeatureInProgress|KAppTemplate|Make a GUI for it - in kdereview|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KAppTemplate|Add a PyQt4 template - in kdereview|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KAppTemplate|Add a Ruby template - in kdereview|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KAppTemplate|Add a Plasmoid template - in kdereview|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KAppTemplate|Add DBUS support in templates|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KCachegrind|Better handling of huge symbols|josef.weidendorfer@gmx.de|Josef Weidendorfer}}
{{FeatureTodo|Lokalize|Kross-based scripting|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|QA: glossary checklists|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|kioslave svn|Add Export/Import feature|montel@kde.org|Laurent Montel}}
{{FeatureTodo|Kate App|Improved session management|kwrite-devel@kde.org|Kate Developers}}
|}

= kdetoys =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdeutils =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|printer-applet|Add printer applet for viewing print jobs and printer auto-configuration.|jriddell@ubuntuFIXMEcom|Jonathan Riddell}}
{{FeatureDone|Okteta|binary/hex editor (successor to KHexEdit). Move from playground/utils.|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|enable extract-strings tool and add copy|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|make printing support only selection|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|ask artists for own icon|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for memory mapping of files|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add "Export as"|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|more explicit titels for undo/redo actions, also from filters|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|parameter dialog for "Copy as..."|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for blocking processes like printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|refactor KByteArrayView|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureInProgress|KDiskFree|Use Solid API|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureTodo|KwikDisk|Replace it by a Plasmoid (in the desktop bar and on the desktop|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureInProgress | KJots | Support more rich text features like text formatting, hyperlinks and ordered/unordered lists. | steveire@gmail.com | Stephen Kelly }}
{{FeatureDone | KJots | Add checkmarks to pages. | steveire@gmail.com | Stephen Kelly }}
{{FeatureInProgress | KJots | Port to KRichText widget. | steveire@gmail.com |Stephen Kelly }}
{{FeatureTodo | KJots | Create a Kontact::Plugin to integrate kjots into Kontact. | steveire@gmail.com |Stephen Kelly }}
{{FeatureDone|SuperKaramba|Integrate Kross and be able to write Karambas using Python, Ruby and JavaScript||The SuperKaramba Team}}
{{FeatureDone|SuperKaramba|Integrate into Plasma||The SuperKaramba Team}}
|}

= kdevelop =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdevplatform =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdewebdev =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Kommander|Port the executor to KDE4.|amantia@kde.org|Andras Mantia}}
{{FeatureTodo|Kommander|Create Qt Designer plugins for the editor.|amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|Quanta Plus|Create an upload plugin.| niko.sams@gmail.com|Niko Sams}}
{{FeatureInProgress|Quanta Plus|Create a new, state machine based parser.| amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|Quanta Plus|Port existing functionality to KDevPlatform plugins. Only text mode is targeted.|amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|KXslDbg|Port to KDE4.|keith@kdewebdev.org |
Keith Isdale}}
{{FeatureTodo|KLinkStatus|Aided correction of broken links||}}
{{FeatureDone|KLinkStatus|Site check automation|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureInProgress|KLinkStatus|D-Bus/Scripting interfaces|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureInProgress|KLinkStatus|HTML validation|thesquib@gmail.com|Sam Ryan}}
{{FeatureDone|KLinkStatus|Ability to export only broken links|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Ability to do background search which only update the GUI when finished (much faster))|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Tray Icon and KUniqueApplication|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Scripting Plugin|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Get Hot New Stuff for HTML result stylesheets|Paulo Moura Guedes}}
|}

Schedules/KDE4/4.2 Feature Plan

2008-05-04T15:45:19Z

Milliams: Add kdegames and kscoremanager entry

This is a list of planned features for the 4.2 release.

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

= kdelibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdepimlibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdeutils =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|Power Manager|import either Guidance Power Manager or move kde4powersaver into kdeutils|?|?}}
|}

= kdegames =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|libkdegames|New highscore management system|milliams|Matt Williams}}
|}

Development/Tutorials/Games/Highscores

2008-05-03T21:07:21Z

Milliams: No longer encessary. FindLibKDEGames.cmake is fixed

{{TutorialBrowser|

series=KDE Games|

name=High Scores|

pre=[[Development/Tutorials/Programming_Tutorial_KDE_4|Introduction to KDE4 programming]], [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction Tutorial]]|

next=|

reading={{class|KScoreDialog}}
}}

==Abstract==
This tutorial will explain how to use the high score system built into kdegames in your application.

[[image:Highscore.png|center|thumb|Dialog in KMines]]

==KScoreDialog==
The high score system is provided through the KScoreDialog class. It is intended to be a lightweight solution and offers the following abilities:
#Grouping of scores (for different difficulty levels etc.)
#Standard fields: Name, Level, Date, Time, Score
#Custom fields (e.g. number of moves)

==Displaying Scores==
To display the high score table, it's as simple as two lines of code.
<code cppqt n>
#include <KScoreDialog>

void showHighscores()
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.exec();
}
</code>
This will display the highscore table showing, by default, the 'Name' and 'Score' columns.

In order to comply with the kdegames standards, you should use a {{class|KStandardGameAction}} to launch this function. This will set up the icons and toolbars correctly. See the [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction tutorial]] for more information on this.
<code cppqt n>
#include <KStandardGameAction>
void setupActions()
{
KStandardGameAction::highscores(this,
SLOT(showHighscores()),
actionCollection());
setupGUI();
}
</code>

==Adding Scores==
===Simplest way to add a score===
The simplest way to add a new score to the table is as follows:
<code cppqt n>
#include <KScoreDialog>

void newHighscore(int playersScore)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.addScore(playersScore);
ksdialog.exec();
}
</code>
This will add the score <tt>playersScore</tt> to the high score table and then launch the dialog. If it is the first score to be entered on the table, a blank line-edit will be provided for the player to enter their name, otherwise the line-edit will still be provided but the player's name will be automatically filled in.

However, you will notice that the dialog is shown every time, even if the player didn't manage to get onto the table. If you only want to show the table if the player achieved a high score, place an <tt>if()</tt> command around the <tt>KScoreDialog::addScore()</tt> call:
<code cppqt>
if(ksdialog.addScore(playersScore))
ksdialog.exec();
</code>

===Passing name by code===
If you want to suggest a name programatically you can do so by using the <tt>KScoreDialog::FieldInfo</tt> type. It's easy to use, for example:
<code cppqt n>
#include <KScoreDialog>

void newHighscore(int score, const QString& name)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = name;
scoreInfo[KScoreDialog::Score].setNum(score);

ksdialog.addScore(scoreInfo);
}
</code>

And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:
<code cppqt n>
#include <KScoreDialog>

void newHighscore(int score, const QString& name, int level)
{
KScoreDialog ksdialog(KScoreDialog::Name |
KScoreDialog::Level, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = name;
scoreInfo[KScoreDialog::Score].setNum(score);
scoreInfo[KScoreDialog::Level].setNum(level);

ksdialog.addScore(scoreInfo);
}
</code>
===Custom fields===
Since there are only a set number of standatd fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function.
<code cppqt n>
#include <KScoreDialog>

void newHighscore(int score, const QString& name, int numMoves)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = "Matt";
scoreInfo[KScoreDialog::Score].setNum(playersScore);

ksdialog.addField(KScoreDialog::Custom1,
i18n("Num of Moves"), "moves");
scoreInfo[KScoreDialog::Custom1].setNum(numMoves);

ksdialog.addScore(scoreInfo);
}
</code>
The first argument to <tt>KScoreDialog::addField()</tt> must be from <tt>KScoreDialog::Custom1</tt> to <tt>KScoreDialog::Custom5</tt>, the second is the text that will appear on the high score table at the head of the column (and must therefore be i18n'd) and the last argument is a unique identifier for the field. After that, it is added to your <tt>KScoreDialog::FieldInfo</tt> in the same way as before.

==Grouping Scores==
Your game may have different levels of difficulty and so you don't want to put the scores for the 'Hard' level on the same table as the 'Easy' table. Grouping scores is easy to achieve using the <tt>KScoreDialog::setConfigGroup()</tt> function:
<code cppqt n>
#include <KScoreDialog>

void newHighscore(int playersScore)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.setConfigGroup(I18N_NOOP("Easy"));
ksdialog.addScore(playersScore);
ksdialog.exec();
}
</code>
Each group will show up as a tab on the high score table dialog. If you don't specify a group, the score will be added to the generic 'High Score' tab.

A very important point to remember is to pass the untranslated group name through <tt>I18N_NOOP()</tt> otherwise the group name will not be translated properly and will cause bugs.

==Advanced Features==
===Hiding Fields===
In some special cases you won't want to display a score as such but rather just the time the player took to complete the level.

While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, ity is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.
<code cppqt n>
#include <KScoreDialog>

// timeString is a nicely formatted string
// e.g. "1:24" used for display
void newHighscore(const QString& timeString, int seconds)
{
KScoreDialog ksdialog(KScoreDialog::Name |
KScoreDialog::Time, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Time] = timeString;
scoreInfo[KScoreDialog::Score].setNum(seconds);
ksdialog.hideField(KScoreDialog::Score);
ksdialog.addScore(scoreInfo, KScoreDialog::LessIsMore)
ksdialog.exec();
}
</code>

[[Category:C++]]
[[Category:KDEGames]]

Development/Tutorials/Games/KStandardGameAction

2008-05-03T21:06:17Z

Milliams: No longer encessary. FindLibKDEGames.cmake is fixed

{{TutorialBrowser|

series=KDE Games|

name=KStandardGameAction|

pre=[[Development/Tutorials/Programming_Tutorial_KDE_4|Introduction to KDE4 programming]]|

next=[[Development/Tutorials/Games/Highscores|High Scores Tutorial]]|

reading={{class|KStandardGameAction}}, {{class|KStandardAction}}
}}

==Abstract==
This tutorial will explain the usage of <tt>KStandardGameAction</tt>s in libkdegames.

== KStandardGameAction ==
This class is an extension to the usual <tt>KStandardAction</tt> class which provides easy access to often used KDE actions.

Using these actions helps maintaining consistency among the games.

Games often use different menu entries than other programs, e.g. games use
the menu "game" instead of "file". This class provides the entries which
differ from the usual KStandardAction entries.

== Usage ==
Add some code like this to your action setup code.
<code cppqt n>
#include <KStandardGameAction>

void setupActions()
{
// Game
KStandardGameAction::gameNew(this,
SLOT(newGame()),
actionCollection());
KStandardGameAction::highscores(this,
SLOT(showHighscores()),
actionCollection());
KStandardGameAction::quit(this,
SLOT(close()),
actionCollection());

// Move
KStandardGameAction::undo(this,
SLOT(undoMove()),
actionCollection());
KStandardGameAction::redo(this,
SLOT(redoMove()),
actionCollection());

// Settings
KStandardGameAction::configureHighscores(this,
SLOT(configureHighscores()),
actionCollection());

setupGUI();
}
</code>

[[Category:C++]]
[[Category:KDEGames]]

Development/Tutorials/KConfig

2008-05-03T15:16:05Z

Milliams: Add 'further reading' link

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

series=KConfig|

name=Introduction to KConfig|

next=[[../Using_KConfig_XT|Using KConfig XT]]|

reading={{Class|KConfig}} apidocs

}}

== Abstract ==

This tutorial looks at the KDE configuration data system, starting with an overview of the design fundamentals from an application developer's point of view. It then looks at the classes relevant to application development one by one before moving on to kiosk (user and group profiles) integration.

== Design Essentials ==

KConfig is designed to abstract away the concept of actual storage and retrieval of configuration settings behind an API that allows easy fetching and setting of information. Where and in what format the data is stored is not relevant to an application using KConfig. This keeps all KDE applications consistent in their handling of configurations while alleviating each and every application author to build such a system on their own from scratch, which can be a highly error prone exercise.

A KConfig object represents a single configuration object. Each configuration object is referenced by its unique name and may be actually read from multiple local or remote files or services. Each application has a default configuration object associated with it and there is also a global configuration object.

These configuration objects are broken down into a two level hierarchy: groups and keys. A configuration object can have any number of groups and each group can have one or more keys with associated values.

Values stored may be of any number of data types. They are stored and retreived as the objects themselves. For example, a {{qt|QObject}} object is passed to a config object directly when storing a color value and when retreived a {{qt|QObject}} object is returned. Applications themselves therefore generally do not have to perform serialization and deserialization of objects themselves.

== The KConfig Class ==

The {{class|KConfig}} object is used to access a given configuration object. There are a number of ways to create a config object:

<code cppqt n>
// a plain old read/write config object
KConfig config("myapprc");

// a specific file in the filesystem
// currently must be an INI style file
KConfig fullPath("/etc/kderc");

// not merged with global values
KConfig globalFree( "localsrc", KConfig::NoGlobals );

// not merged with globals or the $KDEDIRS hierarchy
KConfig simpleConfig( "simplerc", KConfig::SimpleConfig );

// config specific to a component, in this case a plugin
KConfig pluginConfig( componentData(), "pluginrc" );

// outside the standard config resource
KConfig dataResource( "data", "myapp/somefile" );
</code>

The KConfig object create on line 2 is a regular config object. We can read values from it, write new entries and ask for various properties of the object. This object will be loaded from the config resource as determined by {{class|KStandardDirs}}, meaning that every instance of the <tt>myapprc</tt> object in each of the directories in the config resource hierarchy will be merged to create the values seen in this object. This is how system wide and per-user/group profiles are generated and supported and it all happens transparently to the application itself.

{{tip|For more information on how the merging works, see the [[KDE System Administration/KDE_Filesystem_Hierarchy|KDE Filesystem Hierarchy]] article.}}

On line 6 we open a specific local file, this case {{path|/etc/kderc}}. This performs no merging of values and expects an INI style file.

Line 9 sees the creation of a configuration object that is not merged with the global <tt>kdeglobals</tt> configuration object, while the configuration file on line 12 is additionally not merged with any files in the <tt>$KDEDIRS</tt> hierarchy. This can noticeably improve performance in the case where one is simply reading values out of a simple configuration for which global values are not meaningful.

Line 15 creates a configuration object using the {{class|KComponentData}} object that belongs to a plugin or other component. The plugin may have a different set of directories defined in its {{class|KStandardDirs}} and this is a way of ensuring that {{class|KConfig}} respects this.

Finally on line 18 we see the creation of a configuration object that does not exist in the <tt>config</tt> resource but rather in the application <tt>data</tt> resource. You may use any resource that {{class|KStandardDirs}} is aware of, including ones that are added at runtime.

=== Special Configuration Objects ===

Each application has its own configuration object that uses the name provided to {{class|KAboutData}} appended with "rc" as its name. So an app named "myapp" would have the default configuration object of "myapprc". This configuration file can be retrieved in this way:

<code cppqt n>
#include <KComponentData>
#include <KConfig>
#include <KGlobal>

MyClass::MyClass()
{
// note that this is actually a KSharedConfig
// more on that class in a bit!
KConfig* config = KGlobal::config();
}
</code>

The default configuration object for the application is accessed when no name is specified when creating a {{class|KConfig}} object. So we could also do this instead:

<code cppqt n>
#include <KConfig>

MyClass::MyClass()
{
KConfig config;
}
</code>

Additionally, each component may have its own configuration object. This is generally accessed via the plugin's <tt>componentData()</tt> rather than <tt>{{class|KGlobal}}::mainComponent()</tt>.

Finally there is a global configuration object, <tt>kdeglobals</tt>, that is shared by every application. It holds such information as the default application shortcuts for various actions. It is "blended" into the configuration object if the <tt>KConfig::IncludeGlobals</tt> flag is passed to the {{class|KConfig}} constructor, which is the default.

=== Commonly Useful Methods ===

To save the current state of the configuration object we call the <tt>sync()</tt> method. This method is also called when the object is destroyed. If no changes have been made or the resource reports itself as non-writable (such as in the case of the user not having write permissions to the file) then no disk activity occurs. <tt>sync()</tt> merges changes performed concurrently by other processes - local changes have priority, though.

If we want to make sure that we have the latest values from disk we can call <tt>reparseConfiguration()</tt> which calls <tt>sync()</tt> and then reloads the data from disk.

If we need to prevent the config object from saving already made modifications to disk we need to call <tt>markAsClean()</tt>. A particular use case for this is rolling back the configuration to the on-disk state by calling <tt>markAsClean()</tt> followed by <tt>reparseConfiguration()</tt>.

Listing all groups in a configuration object is as simple as calling <tt>groupList()</tt> as in this code snippet:

<code cppqt n>
KConfig* config = KGlobal::mainComponent().config();

foreach ( const QString& group, config.groupList() ) {
kDebug() << "next group:" << group;
}
</code>

== KSharedConfig ==

The {{class|KSharedConfig}} class is a reference counted version of {{class|KConfig}}. It thus provides a way to reference the same configuration object from multiple places in your application without the extra overhead of separate objects or concerns about syncronizing writes to disk even if the configuration object is updated from multiple code paths.

Accessing a {{class|KSharedConfig}} object is as easy as this:

<code cppqt n>
KSharedConfigPtr config = KSharedConfig::openConfig();
</code>

<tt>openConfig()</tt> take the same parameters as {{class|KConfig}}'s constructors do, allowing one to define which configuration file to open, flags to control merging and non-<tt>config</tt> resources.

{{class|KSharedConfig}} is generally recommended over using {{class|KConfig}} itself, and the object returned from {{class|KComponentData}} is indeed a {{class|KSharedConfig}} object.

== KConfigGroup ==

Now that we have a configuration object, the next step is to actually use it. The first thing we must do is to define which group of key/value pairs we wish to access in the object. We do this by creating a KConfigGroup object:

<code cppqt n>
KConfig config;
KConfigGroup generalGroup( &config, "General" );
KConfigGroup colorsGroup = config.group( "Colors" ); // ... or a bit differently ...
</code>

You can pass {{class|KConfig}} or {{class|KSharedConfig}} objects to {{class|KConfigGroup}}.

Config groups can be nested as well:

<code cppqt n>
KConfigGroup subGroup1( &generalGroup, "LessGeneral" );
KConfigGroup subGroup2 = colorsGroup.group( "Dialogs" );
</code>

== Reading Entries ==

With a {{class|KConfigGroup}} object in hand reading entries is now quite straight forward:

<code cppqt n>
QString accountName = generalGroup.readEntry( "Account",
QString() );
QColor color = colorsGroup.readEntry( "background",
Qt::white );
QStringList list = generalGroup.readEntry( "List",
QStringList() );
QString path = generalGroup.readPathEntry( "SaveTo",
defaultPath );
</code>

As can be seen from the above, you can mix reads from different {{class|KConfigGroup}} objects created on the same {{class|KConfig}} object. The read methods take the key, which is case sensitive, as the first argument and the default value as the second argument. This argument controls what kind of data, e.g. a color in line 3 above, is to be expected as well as the type of object returned. The returned object is wrapped in a {{qt|QVariant}} to make this magic happen.

There are a couple of special read methods, including <tt>readPathEntry</tt> which returns a file system path. It is vital that one uses <tt>readPathEntry</tt> if it is a path as this enables such features as roaming profiles to work properly.

If no such key currently exists in the configuration object, the default value is returned instead. If there is a localized (e.g. translated into another language) entry for the key that matches the current locale, that is returned.

== Writing Entries ==

Setting new values is similarly straightforward:

<code cppqt n>
generalGroup.writeEntry( "Account", accountName );
generalGroup.writePathEntry( "SaveTo", savePath );
colorGroup.writeEntry( "background", color );
generalGroup.config()->sync();
</code>

Note the use of <tt>writePathEntry</tt> and how the type of object we use, such as {{qt|QColor}} on line 3, dictates how the data is serialized. Additionally, once we are done writing entries, <tt>sync()</tt> must be called on the config object for it to be saved to disk. We can also simply wait for the object to be destroyed, which triggers an automatic <tt>sync()</tt> if necessary.

== KDesktopFile: A Special Case ==

When is a configuration file not a configuration file? When it is a [http://freedesktop.org/wiki/Standards_2fdesktop_2dentry_2dspec desktop file]. These files, which are essentially configuration files at their heart, are used to describe entries for application menus, mimetypes, plugins and various services.

When accessing a .desktop file, one should instead use the {{class|KDesktopFile}} class which, while a {{class|KConfig}} class offering all the capabilities described above, offers a set of methods designed to make accessing standard attributes of these files consistent and reliable.

== Kiosk: Lockdown and User/Group Profiles ==

KConfig provides a powerful set of lockdown and configuration definition capabilities, collectively known as "Kiosk", that many system administrators and system integrators rely on. While most of this framework is provided transparently to the application, there is occassion when an application will want to check on the read/write status of a configuration object.

Entries in configuration objects that are locked down using the kiosk facilities are said to be ''immutable''. An application can check for immutability of entire configuration objects, groups or keys as shown in this example:

<code cppqt n>
KConfig* config = KGlobal::config();

if ( config->isImmutable() ) {
kDebug() << "configuration object is immutable";
}

KConfigGroup group(config, "General");
if ( group.isImmutable() ) {
kDebug() << "group General is immutable";
}

if ( group.entryIsImmutable("URL") ) {
kDebug() << "URL entry in group General is immutable";
}
</code>

This can be useful in particular situations where an action should be taken when an item is immutable. For instance, the KDE panels will not offer configuration options to the user or allow them to otherwise change the order of applets and icons when the panel's configuration object is marked as immutable.

== KConfig XT ==

There is a way to make certain use cases of KConfig easier, faster and more reliable: KConfig XT. In particular, for main application or plugin configuration objects and when syncing configuration dialogs and other interfaces with these values, KConfig XT can help immensely. It also simultaneously documents the configuration options available, which makes every sys admin and system integrator that uses KDE that much more happy.

[[../Using_KConfig_XT|The next tutorial in the KConfig series covers what KConfig XT is and how to use it.]]

User talk:Dukat

2008-05-03T14:30:32Z

Milliams:

Your page [[Standard Shortcuts]] doesn't belong here (see [[Help:Wiki Structure]]). Techbase is for technical documentation and tutorials, not for random discussion. This is best carried out on the kde-core-devel@kde.org mailing list or placed on the [http://wiki.kde.org kde wiki]. I'll probably be back to delete the page at some point. --[[User:Milliams|milliams]] 17:49, 2 May 2008 (CEST)
:Okay, I've moved the page to [[Projects/Usability/HIG Questions/Standard Shortcuts]] since that fits in with our scheme of using subdirectories. Feel free to continue to edit it there and add other pages in the same manner if you need. --[[User:Milliams|milliams]] 16:30, 3 May 2008 (CEST)

Projects/Usability/HIG Questions

2008-05-03T14:28:22Z

Milliams: /* KDE4 HIG Questions and Requests */

= KDE4 HIG Questions and Requests =

Developer, please use this page to add questions and requests about the KDE4 Human Interface Guidelines (HIG)

* Please list questions about the KDE4 HIG here
* Also include your name/IRC nick/email if you want to be contacted for follow up questions
* Be as specific as possible and include a screenshot if applicable. [http://lists.kde.org/?l=kde-usability&m=120955187622753&w=2 This email on the kde-usability mailing list] is a '''good''' example of a HIG question/request.

* Which buttons have icons and when should we use/not use icons on buttons?
* The growth policy: are widgets supposed to grow and take all the available (horizontal) space, even in case of widgets that don't have a size policy for expanding?
* Should the horizontal alignment of the layout be left- or center-? (eg: [http://img186.imageshack.us/img186/33/formlayoutalignxv0.png sample screenshot])

* Some musing about [[Projects/Usability/HIG_Questions/Standard_Shortcuts | Standard Shortcuts]]

Projects/Usability/HIG Questions/Standard Shortcuts

2008-05-03T14:26:52Z

Milliams: Standard Shortcuts moved to Projects/Usability/HIG Questions/Standard Shortcuts: We use subdirectories in techbase.

I believe the [http://wiki.openusability.org/guidelines/index.php/Appendices:Keyboard_Shortcuts KDE Standard Shortcuts ] are by far from perfect and have several consistency problems. A lot of these problems mostly due to be legacy problems.

I'll list here some thought to start a discussion - I haven't thought it out completely by myself.

The bisggest problem I see is the inconsitent usage of the modifier keys - there's no clear vision here

* Nearly all modern keyboards have four modifier keys (SHIFT, CTRL, ALT, SYSTEM (SYSTEM is not defined: Win key on PC, Apple Key on Mac, Meta key on other) - so let's start use it!

* Currently (aka KDE 3), do modifiers have a clear context meaning? By far not! Currently it looks something like this
** SHIFT changes case in Input fields (good) modifies some other modifier keys, to change its meaning like Save / Save As -> CTRL-S / SHIFT-CTRL-S, (good), but can be also used as a general shortcut key without any relation (New Text Document in Krusader -> SHIFT-F4) (bad)
** CTRL is supposed to be the standard shortcut key within applications, like CTRL-P, CTRL-S, etc - this is done quite well most of the time in KDE (good), however, a lot of System shortcuts (i.e. shortcuts with global scope) are also used with CTRL, like CTRL-Fx for Desktop Switching. Even better, some other are used in combination with ALT, like CTRL-ALT-left, again for Desktop switching.
** ALT is what? I seems to be used as the unversal do-all... Initially, its usage was to define Mouse-less control, so ALT-F would open the file menu. However, ALT is now used as general application shortcuts (Kruader Disk Usage -> ALT-D), Global navigation (ALT-TAB for application switching, yes I know this is legacy, or ALF-F1 for the main menu), ...
** SYSTEM is largely unused, and if used, sometimes in more than strage locations (sorry about the Krusader reference, but I use it that often -> List sort by name - WIN+1 ????????), maybe also a lot in Global Shortcuts

So, I propose a consistent scheme, something like this

* Use the System key! If there are still (some older) keyboards that don't have it, it can normally easily be mapped to another key (maybe to CAPS-LOCK, which is useless anyway). Or have an Escape key, somethig like CTRL-ALT-ESC = Win. But use this key (and consistently)
* SHIFT is only used to change another modifier, and not a shortcut modifier by itself
* The System key is used for global scope only (That's why it's called system key)!, So switch between applications-> SYS-TAB. Change Desktop: SYS+Fx, or SYS-left. Task Menu -> SYS-ESC. Something in this direction.
* SYS-CTRL combinations are for Global Shortcuts only. So, e.g. SYS-CTRL-V could be the Klipper clipboard menu, or used for quicklaunching applications (SYS-CTRL-C to lauch a Console)
* CTRL is used solely for application shortcuts. No Global Shortcuts. maybe, CTRL-ALT would be ok, to have more options.
* ALT is solely used for keyboard navigation. No dedicated shortcuts start with ALT.
* What about F-keys. Have to think about

With this, it would be immediately clear, that when I press a CTRL or ALT key, the effect would only be for the current application, while the SYS key is to control the whole user environment.

This is just a starting point, there might be inconsistencies. Feel free to add your comments.

(TechBase user: dukat, mailto:gul@gmx.li)

Standard Shortcuts

2008-05-03T14:26:52Z

Milliams: Standard Shortcuts moved to Projects/Usability/HIG Questions/Standard Shortcuts: We use subdirectories in techbase.

#REDIRECT [[Projects/Usability/HIG Questions/Standard Shortcuts]]

User talk:Dukat

2008-05-02T15:49:12Z

Milliams: New page: Your page Standard Shortcuts doesn't belong here (see Help:Wiki Structure). Techbase is for technical documentation and tutorials, not for random discussion. This is best carried o...

Projects/Release Team

2008-04-30T21:14:08Z

Milliams: /* Coordinator List */ I'm now the kdegames release coordinator

= The KDE Release Team Project Page =

== Purpose ==
The purpose of the KDE Release Team is to define and execute the official software releases of KDE.

The Release Team is responsible for setting release schedules for the official KDE releases. This includes release dates, deadlines for individual release steps and restrictions for code changes.

The Release Team coordinates release dates with the marketing and press efforts of KDE.

== Members ==
The Release Team is composed of Module Coordinators, Marketing Team liaison (sebas), and the people who actually do the work of tagging and creating the releases (dirk).

As is our tradition, decision making is an open and public process and we welcome input from all concerned parties, including our partners, the packagers, and the distros.

== Contact ==
Please contact the Release Team by [mailto:release-team@kde.org email] or join our public [https://mail.kde.org/mailman/listinfo/release-team mailing list].

== Current Activities ==

* The 4.0 branch is in bugfixing mode, preparing for 4.0.4 to be tagged by the end of April 2008. Bugfix / translation updates are being shipped on a monthly schedule.
* Trunk is open for new features, new strings, bugfixing, and new artwork in preparation for 4.1.0 expected in Jul-Aug 2008

== Module Coordinators ==
=== Functions ===
Module coordinators perform the following duties:
* primary point of contact for the Release Team concerning issues with the module
* help determine release schedules
* communicate release schedules with the module developers
* provide feedback from developers to the Release Team
* review new applications for inclusion in the module
* review old, unmaintained applications for removal from the modules and help find new maintainers
* review external dependencies for the module
* help set and review goals for major and feature releases
* help with release preparation (eg. update application version numbers)

=== Coordinator List ===

{| border="1"
|-
! Module !! Description !! Release Coordinator
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdelibs kdelibs] || KDE foundational libraries || help wanted
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdepimlibs kdepimlibs] || KDE personal information libraries || [mailto:winter@kde.org Allen Winter]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdebase/runtime kdebase-runtime] ||Applications required by KDE apps to function properly at runtime, such as a help browser, framework (e.g. phonon, solid) backends, and certain configuration modules || [mailto:ogoffart@kde.org Olivier Goffart]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdebase/workspace kdebase-workspace] || the UNIX/Linux desktop shell || help wanted
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdebase/apps kdebase-apps] || Essential apps needed to complement a desktop shell for basic functionality (web browser, file manager, ...) || help wanted
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdeaccessibility kdeaccessibility] || Accessibility applications || [mailto:gunnar@schmi-dt.de Gunnar Schmi Dt]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdeartwork kdeartwork] || Additional icons, styles, etc. || help wanted
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdeadmin kdeadmin] || Tools for system administration || [mailto:nicolas.ternisien@gmail.com Nicolas Ternisien]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdeedu kdeedu] || Applications with educational content ||[mailto:annma@kde.org Anne-Marie Mahfouf]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdegames kdegames] || Entertainment || [mailto:matt@milliams.com Matt Williams]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdegraphics kdegraphics] || Graphics viewing and editing || [mailto:aseigo@kde.org Aaron Seigo]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdemultimedia kdemultimedia] || Audio and video applications || [mailto:kretz@kde.org Matthias Kretz]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdenetwork kdenetwork] || Network-centric apps (IM, remote desktop, etc) || [mailto:uwolfer@kde.org Urs Wolfer]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdepim kdepim] || Groupware || [mailto:winter@kde.org Allen Winter]
|- valign=top
| [http://websvn.kde.org/trunk/kdereview kdereview] || Staging area || [mailto:tomalbers@kde.nl Tom Albers]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdesdk kdesdk] || Tools for software development || [mailto:mattr@kde.org Matt Rogers]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdetoys kdetoys] || Fun distractions || [mailto:kde@hilefoks.org Stefan Böhmann]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdeutils kdeutils] || Miscellaneous utilities || [mailto:kossebau@kde.org Friedrich W. H. Kossebau]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdevplatform kdevplatform] || KDE Development Applications Platform libraries || [mailto:mattr@kde.org Matt Rogers]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdevelop kdevelop] || IDE || [mailto:mattr@kde.org Matt Rogers]
|- valign=top
| [http://websvn.kde.org/trunk/KDE/kdewebdev kdewebdev] || Web development tool suite || [mailto:amantia@kde.org Andras Mantia]
|- valign=top
| [http://websvn.kde.org/trunk/extragear extragear] || Extragear || [mailto:helio@kde.org Helio Chissini de Castro]
|- valign=top
| [http://websvn.kde.org/trunk/l10n-kde4 l10n-kde4] || Localization || [mailto:aacid@kde.org Albert Astals Cid]
|- valign=top
| [http://websvn.kde.org/trunk/koffice koffice] || KOffice || [mailto:boud@valdyas.org Boudewijn Rempt]
|}

Projects/Games

2008-04-29T12:32:14Z

Milliams: /* The Game Categories */ Cleanup unnecessary links

{{Template:I18n/Language Navigation Bar|Projects/Games}}
Intro to do

== The Game Categories ==
*[[/Arcade Games|Arcade games]]
*[[/Board Games|Board Games]]
*[[/Card Games|Card games]]
*[[Dice Games]]
*[[Logic Games]]
*[[/Tactic and Strategy|Tactic and Strategy]]
*[[Toys]]

==Development==

* [[/Maintainers| Game's maintainers]]
* [[/UI and usability|UI and usability]]
* [[/libkdegames Usage|libkdegames Usage]]
* [[/Ideas| KDEGames Ideas and Proposals]]

==Status==

* [[/Status KDE 4.0|Status KDE 4.0]]
** [[/Documentation_progress|Documentation progress]]
** [[/Icons_ToDo|Icons_ToDo]]
* older pages:
** [[/Status_Ready|Ready]]
** [[/Status_Should_be_Ready|Should be ready]]
** [[/Status_Playground|kdegames playground (kdegame's candidate or unready) ]]
** [[/Status|old status page]]

==Meeting==

===IRC===

We are doing meeting on [irc://irc.kde.org/#kdegames IRC] every month to talk about the games development.

[[/IRC Meeting|Next Meeting : April 30th/2008 20:00 UTC]]

[[Category:KDEGames]]

Category:KDEGames

2008-04-28T20:47:22Z

Milliams: New page: Pages relating to the kdegames module

Pages relating to the kdegames module

Projects/Games

2008-04-28T20:45:45Z

Milliams:

{{Template:I18n/Language Navigation Bar|Projects/Games}}
Intro to do

== The Game Categories ==
*[[/Arcade Games|Arcade games]]
*[[/Board Games|Board Games]]
*[[/Card Games|Card games]]
*[[Dice Games]]
*[[Logic Games]]
*[[/Tactic and Strategy|Tactic and Strategy]]
*[[Toys]]

===See also===
* [http://doc.trolltech.com/4.2/qsvgrenderer.html QSvgRenderer Class Reference]
* [http://developer.kde.org/documentation/library/cvs-api/kdelibs-apidocs/kdecore/html/classKSvgRenderer.html KSvgRenderer Class Reference]
* [http://websvn.kde.org/trunk/KDE/kdegames/katomic/ KAtomic KDE4 code in websvn]
* [[Schedules/KDE4/4.0 Release Schedule]]

==Development==

* [[/Maintainers| Game's maintainers]]
* [[/UI and usability|UI and usability]]
* [[/libkdegames Usage|libkdegames Usage]]
* [[/Ideas| KDEGames Ideas and Proposals]]

==Status==

* [[/Status KDE 4.0|Status KDE 4.0]]
** [[/Documentation_progress|Documentation progress]]
** [[/Icons_ToDo|Icons_ToDo]]
* older pages:
** [[/Status_Ready|Ready]]
** [[/Status_Should_be_Ready|Should be ready]]
** [[/Status_Playground|kdegames playground (kdegame's candidate or unready) ]]
** [[/Status|old status page]]

==Meeting==

===IRC===

We are doing meeting on [irc://irc.kde.org/#kdegames IRC] every month to talk about the games development.

[[/IRC Meeting|Next Meeting : April 30th/2008 20:00 UTC]]

[[Category:KDEGames]]

Development/Tutorials/Games/KStandardGameAction

2008-04-28T20:45:32Z

Milliams:

{{TutorialBrowser|

series=KDE Games|

name=KStandardGameAction|

pre=[[Development/Tutorials/Programming_Tutorial_KDE_4|Introduction to KDE4 programming]]|

next=[[Development/Tutorials/Games/Highscores|High Scores Tutorial]]|

reading={{class|KStandardGameAction}}, {{class|KStandardAction}}
}}

==Abstract==
This tutorial will explain the usage of <tt>KStandardGameAction</tt>s in libkdegames.

== KStandardGameAction ==
This class is an extension to the usual <tt>KStandardAction</tt> class which provides easy access to often used KDE actions.

Using these actions helps maintaining consistency among the games.

Games often use different menu entries than other programs, e.g. games use
the menu "game" instead of "file". This class provides the entries which
differ from the usual KStandardAction entries.

== Usage ==
Add some code like this to your action setup code.
<code cppqt n>
#include <KDE/KStandardGameAction>

void setupActions()
{
// Game
KStandardGameAction::gameNew(this,
SLOT(newGame()),
actionCollection());
KStandardGameAction::highscores(this,
SLOT(showHighscores()),
actionCollection());
KStandardGameAction::quit(this,
SLOT(close()),
actionCollection());

// Move
KStandardGameAction::undo(this,
SLOT(undoMove()),
actionCollection());
KStandardGameAction::redo(this,
SLOT(redoMove()),
actionCollection());

// Settings
KStandardGameAction::configureHighscores(this,
SLOT(configureHighscores()),
actionCollection());

setupGUI();
}
</code>

[[Category:C++]]
[[Category:KDEGames]]

Development/Tutorials/Games/Highscores

2008-04-28T20:45:24Z

Milliams:

{{TutorialBrowser|

series=KDE Games|

name=High Scores|

pre=[[Development/Tutorials/Programming_Tutorial_KDE_4|Introduction to KDE4 programming]], [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction Tutorial]]|

next=|

reading={{class|KScoreDialog}}
}}

==Abstract==
This tutorial will explain how to use the high score system built into kdegames in your application.

[[image:Highscore.png|center|thumb|Dialog in KMines]]

==KScoreDialog==
The high score system is provided through the KScoreDialog class. It is intended to be a lightweight solution and offers the following abilities:
#Grouping of scores (for different difficulty levels etc.)
#Standard fields: Name, Level, Date, Time, Score
#Custom fields (e.g. number of moves)

==Displaying Scores==
To display the high score table, it's as simple as two lines of code.
<code cppqt n>
#include <KDE/KScoreDialog>

void showHighscores()
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.exec();
}
</code>
This will display the highscore table showing, by default, the 'Name' and 'Score' columns.

In order to comply with the kdegames standards, you should use a {{class|KStandardGameAction}} to launch this function. This will set up the icons and toolbars correctly. See the [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction tutorial]] for more information on this.
<code cppqt n>
#include <KDE/KStandardGameAction>
void setupActions()
{
KStandardGameAction::highscores(this,
SLOT(showHighscores()),
actionCollection());
setupGUI();
}
</code>

==Adding Scores==
===Simplest way to add a score===
The simplest way to add a new score to the table is as follows:
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int playersScore)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.addScore(playersScore);
ksdialog.exec();
}
</code>
This will add the score <tt>playersScore</tt> to the high score table and then launch the dialog. If it is the first score to be entered on the table, a blank line-edit will be provided for the player to enter their name, otherwise the line-edit will still be provided but the player's name will be automatically filled in.

However, you will notice that the dialog is shown every time, even if the player didn't manage to get onto the table. If you only want to show the table if the player achieved a high score, place an <tt>if()</tt> command around the <tt>KScoreDialog::addScore()</tt> call:
<code cppqt>
if(ksdialog.addScore(playersScore))
ksdialog.exec();
</code>

===Passing name by code===
If you want to suggest a name programatically you can do so by using the <tt>KScoreDialog::FieldInfo</tt> type. It's easy to use, for example:
<code cppqt n>
#include <KScoreDialog>

void newHighscore(int score, const QString& name)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = name;
scoreInfo[KScoreDialog::Score].setNum(score);

ksdialog.addScore(scoreInfo);
}
</code>

And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int score, const QString& name, int level)
{
KScoreDialog ksdialog(KScoreDialog::Name |
KScoreDialog::Level, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = name;
scoreInfo[KScoreDialog::Score].setNum(score);
scoreInfo[KScoreDialog::Level].setNum(level);

ksdialog.addScore(scoreInfo);
}
</code>
===Custom fields===
Since there are only a set number of standatd fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function.
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int score, const QString& name, int numMoves)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = "Matt";
scoreInfo[KScoreDialog::Score].setNum(playersScore);

ksdialog.addField(KScoreDialog::Custom1,
i18n("Num of Moves"), "moves");
scoreInfo[KScoreDialog::Custom1].setNum(numMoves);

ksdialog.addScore(scoreInfo);
}
</code>
The first argument to <tt>KScoreDialog::addField()</tt> must be from <tt>KScoreDialog::Custom1</tt> to <tt>KScoreDialog::Custom5</tt>, the second is the text that will appear on the high score table at the head of the column (and must therefore be i18n'd) and the last argument is a unique identifier for the field. After that, it is added to your <tt>KScoreDialog::FieldInfo</tt> in the same way as before.

==Grouping Scores==
Your game may have different levels of difficulty and so you don't want to put the scores for the 'Hard' level on the same table as the 'Easy' table. Grouping scores is easy to achieve using the <tt>KScoreDialog::setConfigGroup()</tt> function:
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int playersScore)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.setConfigGroup(I18N_NOOP("Easy"));
ksdialog.addScore(playersScore);
ksdialog.exec();
}
</code>
Each group will show up as a tab on the high score table dialog. If you don't specify a group, the score will be added to the generic 'High Score' tab.

A very important point to remember is to pass the untranslated group name through <tt>I18N_NOOP()</tt> otherwise the group name will not be translated properly and will cause bugs.

==Advanced Features==
===Hiding Fields===
In some special cases you won't want to display a score as such but rather just the time the player took to complete the level.

While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, ity is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.
<code cppqt n>
#include <KDE/KScoreDialog>

// timeString is a nicely formatted string
// e.g. "1:24" used for display
void newHighscore(const QString& timeString, int seconds)
{
KScoreDialog ksdialog(KScoreDialog::Name |
KScoreDialog::Time, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Time] = timeString;
scoreInfo[KScoreDialog::Score].setNum(seconds);
ksdialog.hideField(KScoreDialog::Score);
ksdialog.addScore(scoreInfo, KScoreDialog::LessIsMore)
ksdialog.exec();
}
</code>

[[Category:C++]]
[[Category:KDEGames]]

Projects/GitoriousKDE

2008-04-28T12:38:51Z

Milliams: Contribute/GitoriousKDE moved to Projects/GitoriousKDE: This definitely shouldn't be under Contribute. If anywhere it should be in Projects.

= Goal =

'''Improve and adapt the [http://gitorious.org Gitorious Web Application] for its use in the development of KDE'''

= Process and development of the project =

Evaluate the current peculiarities of Gitorious and the process or politics of the KDE development to define the new modifications needed to obtain the best integration with Gitorious.

=KDE repository structure=

First we need to study the KDE repository structure with Git.
KDE is an umbrella of many big projects, each of them is made of several smaller parts that are projects of their own.
What seems to be the current agreement is that KDE big projects would be git supermodules and KDE sub-projects would be git submodules.

'''This is what it looks like''':

==Supermodules==

kdelibs.git
README/TODO/CMake/...
includes
doc
...
kdecore.git (module)
kdeui.git (module)
kio.git (module)
knewstuff.git (module)
...

kdebase.git
README/TODO/CMake/...
includes
doc
...
plasma.git (module)
ruphy-plasma.git
notmart-plasma.git
chani-plasma.git
someone-plasma.git
...
kdm.git (module)
...

=KDE commit politic=

KDE has a history of being developer friendly and easily giving svn accounts to most people that apply for them. Git makes this even easier as anybody can commit to his/her own branch.

That being said, KDE is more or less a meritocracy and some developers have more power than others when it comes to administration. This is necessary but SVN can make the administration painful for admins and frustrating for wanna-be developers as they have to wait before they can commit.

Given that, we have thought of a simple user/role organization (no complicated rwx type of permissions system that nobody gets and uses).

==Type of users and their abilities==

===regular users===
* ability to create clones and commit to their clones
* ability to make merge request to mainline
* ability to apply for developer status
* ability to request for the creation of a new supermodule/submodule
* ability to make bug reports/whishes
===KDE developers===
* ability to make commits to mainline
* ability to accept or reject appliances for developer status (see question 2)
* ability to request for the creation of a new supermodule/submodule
===Administrator===
* ability to create (and remove?) supermodules and submodule
* ability to move submodule from one supermodule to another supermodule (ex: kdeplayground=>kdeedu )
* ability to accept creation of new projects inside of supermodules

This is what we have so far.

=We have a few questions too=

1) What's the use of private clones?

2) The question is to know if each submodule of a supermodule will have one or several admin or if every developers of a submodule will have the ability to accept or reject new developers?

3) If there are submodules admins, who does grant them there role? the supermodule admin?

4) Gitorious would be a websvn replacement only or will it be a bugzilla replacement too? Gitorious devs are implementing ticket tracking as of this document writing.

5) is it necesary to implement "applying for developer status" or will it continue to happen by mail as it does now?

=Suggestions=

1) suggestion: anybody will be able to create projects/repositories/forks without any permissions, those projects will be moved to kdeplayground/<submodule> with the submodule created by the superadmin. The project creator could choose the submodule by him/herself. This seems to be in the spirit of kde playground, what do you think?

2) Playground module for each supermodule(kdelibs, kdebase):

kdelibs.git
...
playground/
project1.git
project2.git
...

kdebase.git
...
playground/
project3.git
project4.git
...

playground/ (is a supermodule)
project5.git
project.6git
...
3) knewstuff2 server (git repo => knewstuff2 => user )

=Sum up of the evaluation=

==What needs to be done==

* adapt Gitorious to include roles for project members. Those would be developers and admins. For now, gitorious has the concept of "committers" who can commit to mainline (or a clone), those would be KDE developers.

* it is necessary to implement the concept and managment of supermodules in Gitorious (those supermodules would be KDE super projects such as kdelibs, kdebase, kdeedu...). This functionality is already on the TODO list of Gitorious.

* the visibility of a project's clone will be modifiable by its creator, ability that only developers will have

* migration scripts to migrate bugzilla db to gitorious (suggestion)

* adapt gitorious design to KDE web style

* Annex: create plasmoids that will make use of the Gitorious web service api.

Talk:Projects/GitoriousKDE

2008-04-28T12:38:51Z

Milliams: Talk:Contribute/GitoriousKDE moved to Talk:Projects/GitoriousKDE: This definitely shouldn't be under Contribute. If anywhere it should be in Projects.

== Wrong place for this ==

This isn't really techbase material but if anywhere, if should go under [[Projects]]. I'll move it there now --[[User:Milliams|milliams]] 14:37, 28 April 2008 (CEST)

Contribute/GitoriousKDE

2008-04-28T12:38:51Z

Milliams: Contribute/GitoriousKDE moved to Projects/GitoriousKDE: This definitely shouldn't be under Contribute. If anywhere it should be in Projects.

#REDIRECT [[Projects/GitoriousKDE]]

Talk:Contribute/GitoriousKDE

2008-04-28T12:38:51Z

Milliams: Talk:Contribute/GitoriousKDE moved to Talk:Projects/GitoriousKDE: This definitely shouldn't be under Contribute. If anywhere it should be in Projects.

#REDIRECT [[Talk:Projects/GitoriousKDE]]

Talk:Projects/GitoriousKDE

2008-04-28T12:37:40Z

Milliams: Wrong place for this

== Wrong place for this ==

This isn't really techbase material but if anywhere, if should go under [[Projects]]. I'll move it there now --[[User:Milliams|milliams]] 14:37, 28 April 2008 (CEST)

User talk:Danimo

2008-04-28T12:34:16Z

Milliams: /* More readable URLs */ Thanks

==CAPTCHAs that won't go away==
Aseigo [[Talk:Main_Page#Something_wrong_with_the_CAPTCHAs|suggested]] that I ask you about this. Everytime I make an edit, it claims that I am adding a URL, and wants me to do some math. Is it even supposed to do this to registered users? In any case, ''most'' times I am not adding a url at all, and I tire of the systems inordinate appetite for elementary arithmetic. Can this be fixed? Thanks. --[[User:Axiom|Axiom]] 20:27, 28 March 2007 (CEST)

== <nowiki>{{file}}</nowiki> ==

As you asked me, I removed all the occurrences of <nowiki>{{file}}</nowiki> with <nowiki>{{path}}</nowiki>, and removed the obsolete template <nowiki>{{file}}</nowiki>. -- [[user:Pino|pino]] 02:16, 29 May 2007 (CEST)

:There is also a template called <nowiki>{{module}}</nowiki> for KDE modules (kdelibs, kdebase), etc. I initially used path here, too, and thought that's enough. It's not widely used, only by 2 articles. Maybe we should replace it by path again? What do you think? --[[User:Dhaumann|Dhaumann]] 09:14, 29 May 2007 (CEST)

::I agree. --[[User:Danimo|Danimo]] 09:28, 29 May 2007 (CEST)

::Or maybe link it to the module page in the apidocs (e.g [http://api.kde.org/4.0-api/kdelibs-apidocs/ kdelibs])? --[[User:Milliams|milliams]] 14:47, 29 May 2007 (CEST)

:::Good idea, <nowiki>{{kdelibs}}, {{kdebase}}</nowiki> etc... +1 from my side :) --[[User:Dhaumann|Dhaumann]] 15:11, 29 May 2007 (CEST)

::::Sounds good. Or how about <nowiki>{{module|foo}}</nowiki> linking to http://api.kde.org/4.0-api/foo-apidocs/? I don't know how flexible this method is though? --[[User:Milliams|milliams]] 19:41, 29 May 2007 (CEST)

:::::+1 on [[User:Milliams|milliams]]' idea --[[user:Pino|pino]] 21:35, 29 May 2007 (CEST)

==Assistance needed for new contributor to Techbase==
Hi. My name is Thor, I am a new contributor to KDE and I am looking to provide some help with regard to one of the KDE Games, KTuberling (The Potato dude). I am a Polyglot, and work in many different languages, and I have noticed on issues of KTuberling that even with correct software in place, certain speech selections do not function (Notably; Serbian and Danish). I have been working on these for a while and would like to obtain source code for the Tuberling to try and correct the error. Could you tell me please how I find out who is working on what, and what they are doing to it? Thanks and Regards. [[User:ThunderGod|ThunderGod]] 15:40, 30 December 2007 (CET)
:The best place to find assistance with this is by visiting the #kdegames or #kde-edu channels on irc.freenode.org or by sending an joining the KDE Games mailing list at [https://mail.kde.org/mailman/listinfo/kde-games-devel https://mail.kde.org/mailman/listinfo/kde-games-devel]. I believe tsdgeos (Albert Astals Cid) is the best person to speak to. --[[User:Milliams|milliams]] 17:13, 30 December 2007 (CET)

== More readable URLs ==

At the moment all links on this site are in the form [http://techbase.kde.org/index.php?title=Development/Tutorials http://techbase.kde.org/index.php?title=Development/Tutorials]. I think it would make the site much more readable to convert these links into something like [http://techbase.kde.org/Development/Tutorials http://techbase.kde.org/Development/Tutorials]. Now, as you can see, if you click on that link it does indeed work and takes you to the same page (so you've obviously got mod_rewrite working correctly) so the problem is that mediawiki itself isn't formatting it's links to take advantage of this. I think you basically need to do step 2 from [http://www.mediawiki.org/wiki/Manual:Short_URL#Setup_steps here]. --[[User:Milliams|milliams]] 14:53, 18 April 2008 (CEST)
:It seems this is working now. Thanks a lot :) --[[User:Milliams|milliams]] 14:34, 28 April 2008 (CEST)

== Remove my account ==

Please remove my account; i'd like to choose another username. Thank you. [[User:Krf|KRF]]

:Mediawiki has no concept of user account deletion, since that would mess up the history. Just create a new user and add redirects from your current user accounts user page. --[[User:Danimo|Danimo]] 17:55, 20 April 2008 (CEST)

Schedules/KDE4/4.1 Feature Plan

2008-04-28T01:25:21Z

Milliams: /* kdegames */ Kubrick is now in kdegames

This is a list of planned features. The deadline for adding entries here for the 4.1 release is '''20 April 2008'''.

Entries added after that date will be scheduled for the 4.2 release.

Legend:
* todo => not started yet
* in-progress => started, but not completed yet
* done => completed
__TOC__
= kdelibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|various|[[Projects/Widgets_and_Classes | Classes and Widgets]] that should be moved from others modules up into kdelibs|kde-core-devel@kde.org|The Core Developers}}
{{FeatureDone|kdeui|Add KFadeWidgetEffect to easily add fading UI transitions to KDE applications|kretz@kde.org|Matthias Kretz}}
{{FeatureDone|kdeui|Make icon naming spec compliant 3rd party icon themes like Tango or gnome-icon-theme work correctly.|jpetso@gmx.at|Jakob Petsovits}}
{{FeatureDone|kross|Add QtScript support|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KHTML|Support CSS3 Media Queries|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|KHTML|Efficient smooth scrolling|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|Phonon KCM|More UI feedback|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|VideoWidget snapshot function|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|better integration of pulseaudio|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|make AbstractMediaStream/StreamInterface threadsafe|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|allow backend switching on the fly|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|Phonon|add Port class for fine grained control over data flow between Phonon objects|kretz@kde.org|Matthias Kretz}}
{{FeatureDone|Phonon|subtitle, audio track selection|kretz@kde.org|Matthias Kretz and Ian Monroe}}
{{FeatureTodo|Phonon|DVD menu selection support|imonroe@kde.org|Ian Monroe}}
{{FeatureInProgress|Phonon|"low-level" PCM I/O with at least an ALSA implementation|kretz@kde.org|Matthias Kretz and Ian Monroe}}
{{FeatureTodo|Phonon|update device preference on the fly|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|kdeui|Goya, a framework for inserting controls into itemviews in a really easy and fast way|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureInProgress | kdeui | Rich textedit widget supporting most rich text features. | steveire@gmail.com | Stephen Kelly }}
{{FeatureInProgress|kdeui|Shortcut schemes for KDE applications|adymo@kdevelop.org|Alexander Dymo}}
{{FeatureDone|kmimetypetrader/kbuildsycoca|Replace use of profilerc for ordering applications with new mimeapps.list standard|faure@kde.org|David Faure}}
{{FeatureInProgress|knewstuff|Support caching, and speed up the interface through use of Models/Views and goya|jeremy@scitools.com|Jeremy Whiting}}
{{FeatureInProgress|Phonon KCM|Handle advanced devices|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|KDEPrint|Reintroduce KDEPrint in some form, depending on what Qt4.4 delivers.|john@layt.net|john Layt}}
{{FeatureInProgress|KDEPrint|Add CUPS Options tabs to QPrintDialog to support n-up, page borders, banner pages, page labels, mirror pages, job scheduling, and manual CUPS options.|john@layt.net|John Layt}}
{{FeatureTodo|KDEPrint|Add framework for standard actions for 'Send to...' for e-mail, fax, etc by printing to PDF/PS.|john@layt.net|John Layt}}
{{FeatureTodo|KDEPrint|Migrate FilePrinter class from Okular to enable file printing for all apps via QPrinter, modify to utilise new Qt4.4 features. To be discussed on k-c-d first.|john@layt.net|John Layt}}
{{FeatureInProgress|KIO|speed limits on KIO Transfers|nolis71cu@gmail.com|Manolo Valdes}}
{{FeatureInProgress|kdeui|Printing of shortcuts from the shortcut dialog|apaku@gmx.de|Andreas Pakulat}}
{{FeatureDone|Kate Part|Annotation framework for the editor|apaku@gmx.de|Andreas Pakulat}}
{{FeatureInProgress|KJS|Bytecode interpreter and performance improvements|maksim@kde.org|Maks Orlovich}}
{{FeatureInProgress|KHTML|Sync class and file structure with WebKit to prepare merging|porten@kde.org|Harri Porten}}
{{FeatureInProgress|KHTML|contentEditable/designMode implementation|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|KCalenderSystem|Complete migration of Jalali, Hijri, and Hebrew calendars to new code base.|john@layt.net|John Layt}}
{{FeatureTodo|KCalenderSystem|Add new calendar systems: Indian Civil (Saka), Ethiopean, Chinese, Pure Julian, Pure Gregorian. (Note, not all may live in kdelibs or be available as a global calendar system)|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement KLocale based methods to return weekend days and day of religious observance. Currently KCalendarSystem provides dayOfPray(), but for Gregorian this is not correct in all locales where it is used. Currently KDatePicker hardcodes Saturday and dayOfPray() as weekend days which may not be correct in all locales. To be discussed first on k-c-d and with kdepim.|john@layt.net|John Layt}}
{{FeatureDone|dnssd|Models for service browser and domain browser.|qbast@go2.pl|Jakub Stachowski}}
{{FeatureTodo|KHTML|Adaptable/Scriptable workarounds for broken websites.|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|KHTML|support for borders-* properties from the CSS3 Background and Borders Module|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|KHTML|support for Audio/Video tags from the HTML5 draft specification|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|KHTML|prospective loading of other network resources while waiting for arrival of blocking scripts|germain@ebooksfrance.org|Germain Garand}}
{{FeatureInProgress|KJS|Public API for extensions. Possibly analog to JavaScriptCore's C API.|porten@kde.org|Harri Porten}}
{{FeatureTodo|KTextEditor|Several interface extensions (e.g. open/save filter)|kwrite-devel@kde.org|Kate Developers}}
{{FeatureTodo|KTextEditor|Plugin for basic collaborative editing|kwrite-devel@kde.org|Kate Developers}}
{{FeatureInProgress|Kate Part|Scripting support for indentation and little helpers|kwrite-devel@kde.org|Kate Developers}}
{{FeatureTodo|Kate Part|Input modes to allow e.g. vim-like editing|kwrite-devel@kde.org|Kate Developers}}
{{FeatureDone|KIO|Implement support for inline editing in KFileItemDelegate|fredrik@kde.org|Fredrik Höglund}}
{{FeatureDone|KIO|Add support for drawing text shadows in KFileItemDelegate|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Emoticons lib|An emoticons library so each applications doesn't have to implement the same things over and over again |brandon.ml@gmail.com|Carlo Segato}}
{{FeatureInProgress|KFile|Implement fd.o desktop-bookmark-spec for KFilePlacesModel|nf2@scheinwelt.at|Norbert Frese}}
{{FeatureTodo|kdeui| Support for About Data of libs and modules used by a program |kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|kdeui|Drop-in replacement for QFontComboBox, with more informative previews in non-Latin1 locales|caslav.ilic@gmx.net|Chusslove Illich}}
{{FeatureInProgress|KAboutLicense|Select licenses by keyword, to centralize license info texts for frequent licenses.|caslav.ilic@gmx.net|Chusslove Illich}}
{{FeatureTodo|KIO|KIO::AuthInfo and PasswordDialog: optional fields (like "domain"); optional anonymous switch and flag to suppress KIO's password caching|nf2@scheinwelt.at|Norbert Frese}}
{{FeatureTodo|kdeui|Support for KConfigGroup in KConfigSkeleton|aseigo@kde.org|Aaron Seigo}}
|}

= kdepimlibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Akonadi|Move the Akonadi development library from kdepim.|vkrause@kde.org|Volker Krause}}
{{FeatureInProgress|Akonadi|Item size ([[Projects/PIM/Akonadi#Core|details]])|thomas.mcguire@gmx.net|Thomas McGuire}}
{{FeatureTodo|Akonadi|Payload serialization format versioning ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureTodo|Akonadi|Item streaming in ItemSync/ResourceBase ([[Projects/PIM/Akonadi#Core|details]])|tomalbers@kde.nl|Tom Albers}}
{{FeatureInProgress|Akonadi|API for additional item parts ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org,tokoe@kde.org|Volker Krause/Tobias Koenig}}
{{FeatureInProgress|Akonadi|Infrastructure for showing additional dialogs from agents/resources ([[Projects/PIM/Akonadi#Core|details]])|tomalbers@kde.nl|Tom Albers}}
{{FeatureTodo|Akonadi|Allow to limit ItemFetchJob to current cache content ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureInProgress|Akonadi|Fix API for item/collection modifications ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureTodo|Akonadi|Error reporting ([[Projects/PIM/Akonadi#Core|details]])|tokoe@kde.org|Tobias Koenig}}
{{FeatureTodo|gpgme++2|newly designed gpgme++ (multithreaded, exceptions, less event loop integration: better for Windows)|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureTodo|kpimutils|Change linklocator to use the new emoticon lib|brandon.ml@gmail.com|Carlo Segato}}
|}

= kdebase-apps =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Dolphin|Details-view: Allow to open folders as tree (turned off per default).|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|Dolphin|Refactor view-action handling to a DolphinViewActionHandler to share more code with DolphinPart|faure@kde.org|David Faure}}
{{FeatureDone|Konqueror|Re-implement Copy To / Move To in the popup menu|faure@kde.org|David Faure}}
{{FeatureTodo|Konqueror|Separate konquerorrc and kfmrc (at least useful for home URL and toolbar settings)|faure@kde.org|David Faure and Emanuele Tamponi}}
{{FeatureDone|Dolphin|Simplify selecting of files in the single-click mode (based on http://aseigo.blogspot.com/2006/04/icons.html).|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Raptor|The KDE4-Application-Menu}}
{{FeatureInProgress|Dolphin|Provide optional tooltips for files and directories.|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Dolphin|Tabs|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Konqueror|Bring back the large tooltip like in kde3|faure@kde.org|David Faure}}
{{FeatureInProgress|Konqueror|Session management (save/restore session/restore from crash).|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|Konqueror|Support for undo closed window.|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureDone|Konqueror|Allow to configure the Dolphin KPart within the Konquerors settings dialog.|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|KInfocenter|Improve code and usability.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureDone|KInfocenter|Reimplement partitions list.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureDone|KInfocenter|Reimplement memory module.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureDone|KInfocenter|Reimplement PCI module.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureTodo|KInfocenter|Reimplement Network module.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
|}

= kdebase-workspace =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Plasma|Kickoff orientation dependent layout|wstephenson@kde.org|Will Stephenson}}
{{FeatureDone|kmenuedit|Restore menu system|montel@kde.org|Laurent Montel}}
{{FeatureDone|KCM autostart|Configure autostart desktop file|montel@kde.org|Laurent Montel}}
{{FeatureDone|Plasma|improve fail to launch and needs
config|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|ksmserver|UI for selecting WMs|l.lunak@kde.org|Luboš Luňák}}
{{FeatureDone|Plasma|polish kickoff|wstephenson@kde.org|Will Stephenson}}
{{FeatureDone|Plasma|toolbox improvements |aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|GHNS2 plasma themes|jeremy@scitools.com|Jeremy Whiting}}
{{FeatureDone|Plasma|Resizable, relocatable panel|binner@kde.org|Stephan Binner}}
{{FeatureInProgress|Solid|Refactor Solid::Control networking|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|Solid|Backend for NetworkManager 0.7|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|System Settings|Filtering/Lazy load category modules|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|KSysGuard|Monitor process I/O|tapsell@kde.org|John Tapsell}}
{{FeatureInProgress|KDEPrint|Add printer applet for viewing print jobs and printer auto-configuration.|jriddell @ubuntu.com|Jonathan Riddell}}
{{FeatureInProgress|Plasma|Mac-like menu bar plasmoid|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Color KCM|Add 'smart setting' of extended colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Add KDE3 scheme import|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Query kwin for supported colors; add full set of kwin colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KDEPrint|reintroduce KDEPrint Print Management tools, e.g. KCM, kprinter, kjobviewer, etc. Depends upon progress of kdelibs side of KDEPrint and Qt4.4 feature set.|john@layt.net|john Layt}}
{{FeatureTodo|System Settings|Administrator mode support|wstephenson@kde.org|Will Stephenson}}
{{FeatureTodo|krunner|Revamp GUI.|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Plasma|keyboard shortcuts|Chani Armitage|chanika@gmail.com}}
{{FeatureInProgress|Plasma|webkit widget|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|shared timer in engines|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|welcome plasmoid|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|dashboard widget support|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Plasmagik packaging (and package classes)|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Plasma|Scriptengines|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Plasma|QtScript scriptengine|richmoore44@gmail.com|Richard Moore}}
{{FeatureInProgress|Plasma|Filebrowser Plasmoid|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Plasma|Improve QtScript support|richmoore44@gmail.com|Richard Moore}}
{{FeatureInProgress|Plasma|Zooming User Interface|chanika@gmail.com|Chani Armitage}}
{{FeatureInProgress|Plasma|Multiple Desktop Containments|chanika@gmail.com|Chani Armitage}}
{{FeatureInProgress|Plasma|Networkmanager Plasmoid and DataEngine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureInProgress|Plasma|API changes [[Projects/Plasma/Tokamak1]]|panel-devel@kde.org|Plasma team }}
{{FeatureInProgress|Plasma|Panel Toolbox|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Panel changes to make it work with the new default theme|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Generic folder view applet/containment, that can also be used as the desktop background (showing the desktop folder).|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Krunner|Configuration options for blacklisting, user ranking, runner ranking, learning|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Simple learning|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Simple GUI for above options|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Runners able to share parsing|mumismo@gmail.com|Jordi Polo}}
{{FeatureInProgress|Krunner|Configuration dialog for KRunner|ryan.bitanga@gmail.com|Ryan P. Bitanga}}
{{FeatureTodo|Krunner|Noun-Verb support|ryan.bitanga@gmail.com|Ryan P. Bitanga}}
{{FeatureDone|Plasma|Temperature sensing in the device engine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureDone|Plasma|Video data in the device engine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureTodo|Plasma|New plasma themes|nuno@oxygen-icons.org|Nuno Pinheiro}}
{{FeatureTodo|Plasma|physics-based animator|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Improve the base set of plasmoids|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|New wallpapers|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|New way of handling wallpapers and different sizes (package format, and so on...)|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Top-level windows plasmoids|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureDone|Plasma|change showConfigurationInterfaction to createConfigurationInterface|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Plasma::Service |aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Keyboard shortcuts |aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|panel hiding |aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|panel toolbox |aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|KWin|non-linear animations also for KWin|sebas@kde.org|Sebastian Kuegler}}
{{FeatureInProgress|KWin|Compiz's wobbly like effect for KWin|cedric.borgese@gmail.com|Cédric Borgese}}
{{FeatureTodo|KDM|Theme KDM (login manager) by default|uwolfer@kde.org|Urs Wolfer}}
{{FeatureTodo|Splash screen|New default splashscreen|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Nepomuk|Simple Desktop Search client based on Nepomuk search|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Plasma|Add a dataengine that implements galago-project Notifications DBus interface and a plasmoid which provides cute visualization of notifications along with nice and easy way to interact with them|dimsuz@gmail.com|Dmitry Suzdalev}}
{{FeatureInProgress|Plasma|loadDefaultSetup from a file, not hardcoded|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|ksmserver|Make the fade-to-gray logout effect work even when composite is disabled|fredrik@kde.org|Fredrik Höglund}}
|}

= kdebase-runtime =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|nepomuk|Service that monitors file rename and delete operations and updates the metadata accordingly. kded module already exists in playground. problem: depends on inotify.|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|KCM emoticons|Adding/editing/removing emoticons theme|brandon.ml@gmail.com|Carlo Segato}}
{{FeatureInProgress|phonon-xine|snapshots in video widget|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|try to make VideoWidget work on GraphicsView|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|make states compatible to other backends|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|better support for pulseaudio (most work possibly in kdelibs)|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-gstreamer|Make phonon-gstreamer as released with Qt 4.4 fully integrate into KDE and add the features added to libphonon after libphonon 4.1|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|desktop ioslave|Add an ioslave that lists the contents of the desktop folder, and reports the names in the .desktop files instead of the actual file names.|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|knotify|Add support for galago desktop notifications spec - if knotify will find a certain DBus service on session bus, it'll forward its popup notification events to this service |dimsuz@gmail.com|Dmitry Suzdalev}}
{{FeatureInProgress|Oxygen cursors|Oxygen cursor set|riccardo@kde.org|Riccardo Iaconelli}}
|}

= kdeaccessibility =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KMagnifier|Add color blindness simulation|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KMagnifier|Refactor color menu, re-add invert, add color-shift modes to help people with color blindness|mw_triad@users.sourceforge.net|Matthew Woehlke}}
|}

= kdeadmin =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KSystemLog|KSystemLog, a Log Viewer Tool. Move from kde-apps|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Do some refactoring in KCron|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Improve ergonomy and general interface|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Fix all existing bugs in KCron|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Convert KCron into a KCM Module, to use it in System Settings|nicolas.ternisien@gmail.com}}
{{FeatureInProgress|Environment Variables|Create a environment variables KCM Module|nicolas.ternisien@gmail.com}}
|}

= kdeartwork =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdebindings =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|Smoke2|Move Smoke2 to kdebindings-trunk.|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureTodo|PHP-Qt|Move PHP-Qt to kdebindings-trunk.|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureTodo|kross|Move krossjava to kdebindings-trunk.|mail@dipe.org|Sebastian Sauer}}
{{FeatureTodo|General|Wrap some more APIs (at least Akanodi for all languages and Plasma for C#)|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureTodo|Qyoto|Add delegate support for signal/slot connections.|kde-bindings@kde.org|KDE-bindings developers}}
|}

= kdeedu =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Kalzium|Clean up the database. I am syncing with the BlueObelisk data repository again. There we decided to remove the density (not a element property but a compound property. I also removed the mean weight. We think it is better to provide correct data than a lot (but partly wrong) data.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureDone|KAlgebra|Calculator Plasmoid|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|KAlgebra|Vector support|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|Step|A physics simulator, move from playground to kdeedu module |ks.vladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureDone|Kalzium|Update the snapshot of libavogadro to 0.6.1. This introduces a gazillion new possibilities for the 3D renderer and fixes many issues.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|Kalzium|Make use of the new libavogadro-version.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|Kalzium|Expose molecular editing features of libavogadro.|marcus@cryos.org|Marcus D. Hanwell}}
{{FeatureTodo|Kalzium|Port Kalzium's periodic table to use new QGraphicsView.|marcus@cryos.org|Marcus D. Hanwell}}
{{FeatureInProgress|KStars|Tool to predict Conjunctions|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureInProgress|Marble|DGML2 Support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|KDE-Version settings dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Port authors list from the Qt-About dialog to the KDE-About dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Qt-Version settings dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Improved KML support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|OpenStreetMap support using original OSM tiles|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Real Time Cloud-Cover|tackat@kde.org|David Roberts / Torsten Rahn}}
{{FeatureTodo|Marble|Map Contents translation|tackat@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Copy position to clipboard|tackat@kde.org|Torsten Rahn}}
{{FeatureDone|Marble|Create Tiles on compile time|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Mercator Projection|inge@lysator.liu.se|Inge Wallin}}
{{FeatureInProgress|Marble|More generic projection support|inge@lysator.liu.se|Inge Wallin}}
{{FeatureInProgress|Marble|Usage of Marble in non-widgets|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Export map to MxN pixel bitmap|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Support for MarbleWidget::setEnabled( bool )|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Layer Management Class|tokoe@kde.org|Tobias König}}
{{FeatureTodo|Marble|Plugin architecture for map layers|tokoe@kde.org|Tobias König}}
{{FeatureInProgress|KEduca|Rewrite of the classic test writing/taking application|matt@milliams.com|Matt Williams}}
{{FeatureDone|Parley|Redesigned main window|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|Parley|Vocabulary Plasmoid|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|KBruch and KPercentage|Merge in 1 app|pete@pmurdoch.com|Peter Murdoch}}
{{FeatureInProgress|Kalzium|Plasmoid to access Kalzium database|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|Step|Improve GUI for creating gas and softbody|ksvladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureInProgress|KAlgebra|Variables share between calculations|aleixpol@gmail.com|Aleix Pol}}
{{FeatureTodo|KTurtle|Export canvas as image|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Optional rulers/grid for canvas units|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Add command line|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Add a color picker|nielsslot@gmail.com|Niels Slot}}
{{FeatureInProgress|Parley|Declensions|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|Parley|Improved printing support|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureTodo|KLettres|Number support|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Add a Open File action|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Integrate an editor|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Plasmoid|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Visual indicator when letter is wrong|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Kiten|Link radselect with kiten|jkerian@gmail.com|Joe Kerian}}
{{FeatureInProgress|Kiten|Sort output by dictionary/user selected sorting values|jkerian@gmail.com|Joe Kerian}}
{{FeatureTodo|Step|Use common constraints handling code for collisions|ksvladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureDone|Kig|Cubic-line intersection in case two of the three intersection points are already present|paolini@dmf.unicatt.it|Maurizio Paolini}}
{{FeatureTodo|Kig|Properties dialog for objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve construction of bisect lines.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve feedback when constructing objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|More geometric objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Script objects as macros (to be reused more than once).|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve the Cabri import filter.|pino@kde.org|Pino Toscano}}
|}

= kdegames =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KDiamond|New game, move to kdegames|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|KDiamond|Get themes with KNewStuff|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|KNetWalk|Better scoring system|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureDone|KNetWalk|Add support for loading new themes|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureDone|Kollision|Move to kdereview/kdegames|p.capriotti@gmail.com|Paolo Capriotti}}
{{FeatureDone|Kubrick|New game, 3D OpenGL - move to playground|ianw}}
{{FeatureDone|Kubrick|Polish up the features|ianw}}
{{FeatureDone|Kubrick|Port to Qt4 and KDE4|ianw}}
{{FeatureDone|KBlocks|Finish display of points and level|piacentini@kde.org}}
{{FeatureDone|KBlocks|Implement KNewStuff support|piacentini@kde.org}}
{{FeatureDone|KBlocks|Implement key/action/shortcut configuration|piacentini@kde.org}}
{{FeatureDone|KBlocks|Docbook|piacentini@kde.org}}
{{FeatureInProgress|KGoldRunner|Improved theming and animation|mikelima@cirulla.net}}
{{FeatureInProgress|KGoldRunner|Sound support and theming|mikelima@cirulla.net}}
{{FeatureInProgress|KSquares|Multiplayer support|josef}}
{{FeatureDone|KsirK|New game, move to kdereview|kleag@free.fr|Gaël de Chalendar}}
{{FeatureInProgress|KsirK|Make network games work again|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|KBattleship|Bring back Zeroconf support for network games|qbast@go2.pl}}
{{FeatureInProgress|Kubrick|New game, 3D OpenGL - in kdereview|ianw}}
{{FeatureInProgress|KGGZ|Add kggzcore and kggzdmod libraries|josef}}
{{FeatureTodo|KBlocks|Add additional themes|piacentini@kde.org}}
{{FeatureInProgress|KBreakout|Finish it, and move it from playground to kdegames|fela.kde@gmail.com}}
{{FeatureTodo|KGGZ|Add new Qt4-based core client as successor to the old KDE3-based KGGZ|josef (now SoC proposal)}}
{{FeatureTodo|KGGZ|Fire-and-forget highscore submission for single-player games and client-to-client multiplayer games|josef)}}
{{FeatureTodo|KGoldRunner|Also see kdegames/kgoldrunner/TODO|ianw}}
{{FeatureTodo|KGoldRunner|Hot new stuff support for themes and levels|mikelima@cirulla.net}}
{{FeatureTodo|KGoldRunner|Startup screen|mikelima@cirulla.net}}
{{FeatureTodo|KMahjongg|Reimplement the Board Editor|piacentini@kde.org}}
{{FeatureDone|KMines|Add pause actions|eike.lange@kdemail.net}}
{{FeatureDone|KNetWalk|Configurable keyboard support|eike.lange@kdemail.net}}
{{FeatureTodo|KNetWalk|Support for custom and non-square board sizes|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KShisen|Port to KScoreDialog|piacentini@kde.org}}
{{FeatureTodo|Kubrick|See SVN file kubrick/TODO|ianw}}
{{FeatureDone|Kubrick|Move to KDE Games for 4.1|ianw}}
|}

= kdegraphics =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Gwenview|Undo system|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Gwenview|Fullscreen meta information|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Gwenview|Ability to open an image with another application|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Okular|Better Text-To-Speech integration: speech the whole document, the current page or the selection.|pino@kde.org|Pino Toscano}}
{{FeatureDone|Okular|Encryption support for ODF generator|bradh@kde.org}}
{{FeatureInProgress|Okular|Backward direction for text search.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Centralized text & graphics antialias configuration.|pino@kde.org|Pino Toscano}}
{{FeatureDone|Okular|EPub backend.|elylevy@cs.huji.ac.il|Ely Levy}}
{{FeatureInProgress|Okular|Improved form support (add missing types, handle the fields better).|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Gwenview|Support for tagging with Nepomuk|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Thumbnail bar in view and fullscreen modes|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Crop ratio|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|KIPI support|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Red eye correction|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Start page|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Okular|JavaScript support (mostly for PDF documents).|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Improved placement and sizing of the presentation mode: choose the screen to use, adapt to screen size changes.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Caret annotations.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|File attachment annotations (read only for now).|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Sound annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Link annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Improve annotation support: for existing types (rubber stamps, line, note, etc), and for the way they are constructed and handled.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Separate the "view properties" out of the Document, in a View class. Use it for the page view and the presentation mode.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Per-document zoom level.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|libksane|Move libksane to kdegraphics|kare.sars@kolumbus.fi|Kåre Särs}}
{{FeatureTodo|ksaneplugin|Replase libkscan with ksaneplugin|kare.sars@kolumbus.fi|Kåre Särs}}
|}

= kdemultimedia =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Dragon Player|A simple Phonon-based videoplayer application|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|Make Dragon indipendent from Xine|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|File Manager|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|play media dialog|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|slider changes|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|show info while playing audio files|ian.monroe@gmail.com|Ian Monroe}}
|}

= kdenetwork =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KGet|Group-Settings|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Torrent-Support|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Transfer-Settings|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Webinterface|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|Kopete|AIM offline messages|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|OTR Encryption support|michael_zanetti@gmx.net|Michael Zanetti}}
{{FeatureDone|Kopete|Status manager|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|Non-intrusive notification system|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|KGet|MultiSource-Downloading|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|Kopete|Bring back chat style selection via knewstuff2|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Kopete|ICQ 6 status icons|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|Kopete|MSNP15 implementation for MSN|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|UPnp Support|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|Updated contact list interface (uses Qt 4 rather than Qt 3)|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|Use notebook lid for auto away|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureTodo|Kopete|Update Kopete to better support Decibel|kopete-devel@kde.org|Kopete Developers}}
{{FeatureTodo|Kopete|use the new emoticons library|brandon.ml@gmail.com|Carlo Segato}}
{{FeatureInProgress|KGet|Nepomuk-Integration|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|KGet|Support mms://-protocol, see https://launchpad.net/libmms|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Global Speedlimits|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Setup libbtcore from KTorrent in KGet (to avoid dependency to extragear)|uwolfer@kde.org|Urs Wolfer}}
{{FeatureInProgress|KGet|Extend the TransferHistory to use SQLite and XML-Backends and display the information inside a kcategorizedview|jgoday@gmail.com|Javier Goday}}
{{FeatureTodo|Kopete|GroupWise chatroom support|wstephenson@kde.org|Will Stephenson}}
{{FeatureTodo|[http://decibel.kde.org Decibel]|Decibel, a framework for real time communication services. Move from playground/pim|info@basyskom.de|Tobias Hunger}}
{{FeatureDone|KRDC|Optional system tray icon (with quick access to bookmarks)|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Improved behavior of entering special keys for better workflow|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Zeroconf support (detecting remote desktop services in local network)|romnes@stud.ntnu.no|Magnus Romnes}}
{{FeatureInProgress|KRDC|Bookmark dock widget for quick access to bookmars, zero conf detected services and recently used connections|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Support for up- and downscaling VNC remote desktop|uwolfer@kde.org|Urs Wolfer}}
{{FeatureInProgress|Plasma|Network Manager Applet|cblauvelt@gmail.com|Christopher Blauvelt}}
|}

= kdepim =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KAddressbook|Ability to add LDAP search results to distribution lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|Indication of which resource folder a contact belongs to|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|Read-only view for contacts in read-only folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|copy/cut/paste context menu items|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAlarm|Allow use of multiple calendar resources|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Handle time zones and seasonal time changes properly|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Abolish alarm daemon and make kalarm trigger alarms itself|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Replace simple repetitions by recurrence sub-repetitions to reduce confusion|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|New option for display alarm text to be generated by a command|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|New option to specify reminder times in minutes|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Prevent multiple identical error messages accumulating for the same alarm|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Provide "don't show again for this alarm" option for command error messages|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Remember main window show/hide options used when KAlarm closed instead of setting them in Preferences dialog|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Simplification and improvements to alarm edit dialog|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Option to display alarms in centre of screen, with enable delay on buttons to avoid accidental acknowledgement|djarvie@kde.org|David Jarvie}}
{{FeatureDone|Kleopatra|Ability to search in internal and external certificates at the same time|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kleopatra|General UI Server|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|Kleopatra|New, tabbed, mainwindow design|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|KMail|Ability to create hyperlinks in HTML messages|steveire@gmail.com|Stephen Kelly}}
{{FeatureDone|KMail|Ability to easily create todos with reminders from emails|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Ability to open messages from search results when the reader is hidden|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better invitation update emails showing what changed|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better reminder visualization in very small events|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better, natural language search criteria names|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Clickable status columns|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Client side configurability of warnings in shared folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Colored ribbons for indication of signing and encryption status in the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Configuration option for whether invitation emails are automatically deleted or not when having been acted upon|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Copy/paste and drag and drop from/to the mail composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Decryption on demand in reader window|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Display of quota information in foldertree tooltips|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop and copy and paste support in the search result viewer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop from the mail reader window and mime-tree viewer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop of folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Editing of attachments from the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Export and import of filters|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Favorites Folder|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Folder quicksearch|m.koller@surfeu.at|Martin Koller}}
{{FeatureDone|KMail|Harmonization of actions in main and standalone mail reader windows|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|IMAP Server storage of non-standard flags|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Improved TNEF attachment handling|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Improved quota warnings|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Initialize full search from quicksearch on request|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Override font and fontsize for standalone message viewers|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Per-folder identity configurability|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Recursive IMAP cache troubleshooting|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Resizable recipients area in composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for creating new mails based on received mails (Resend)|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for immediate sync of resource folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for soft line breaking|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Tab navigation through groups in the address completion|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Text snippets with shortcuts and variable expansion in the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Warning about active out-of-office scripts|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|lost+found recovery of locally changed folders that lose access rights|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KNotes|Ability to print notes|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KonsoleKalendar|Support "file" and "localdir" resources|winter@kde.org|Allen Winter}}
{{FeatureDone|Kontact|Config option to close despite system tray|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Harmonization of component naming in sidebar, configuration, summary view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Right-aligned component navigation toolbar|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Ubiquitous sync actions|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Ability to have both distribution lists and addresbook extension visible|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Aggregated reminders view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Better default resource colors|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Drag and drop of attachments|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Faster initial loading of kolab resources|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Forwarding and delegation of invitations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Improved coloring of agenda view items|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Improved event printing|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Merge of the attachment view in into the main page|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Merge of the free-busy and attendee views for easier scheduling|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Month view scrolling, paging, mouse-wheeling|tom_t@gmx.at|Thomas Thrainer}}
{{FeatureDone|KOrganizer|More readable Kolab resource folder labels|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Redesigned incidence editor UI|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Side-by-side calendar view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Support for by-value attachments|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Timeline calendar view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Rich text incidence editor|mike@mikearthur.co.uk|Mike Arthur}}
{{FeatureDone|KOrganizer|Hide/Show reminder daemon icon in the systeay|winter@kde.org|Allen Winter}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Column-specific whatsthis-help| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Combined search and add task widget| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Drag&Drop| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|File management (file->load)| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Managing history| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Tracking tasks by active applications| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Whatsthis-help dependent on if a task has been created| |Thorsten Stärk}}
{{FeatureInProgress|Akregator|Support for syncing the feed list with Google Reader |osterfeld@kde.org|Frank Osterfeld}}
{{FeatureInProgress|KAlarm|New option to restrict alarms to working hours|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|Kleopatra|OpenPGP support|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureInProgress|KMail|HTML Signatures|yez@familieschepers.nl|Edwin Schepers}}
{{FeatureInProgress|KNotes|Zeroconf support for sending notes on LAN|qbast@go2.pl|Jakub Stachowski}}
{{FeatureInProgress|Kontact|New Planner summary; combines Appointment+To-do+SpecialDates into 1 pretty summary|winter@kde.org|Allen Winter}}
{{FeatureInProgress|KOrganizer|New To-do View (model/view)|tom_t@gmx.at|Thomas Thrainer}}
{{FeatureInProgress|KOrganizer|New Month View (qgraphicsitem)|bvirlet@kdemail.net|Bruno Virlet}}
{{FeatureInProgress|KPilot|Finish Keyring conduit, base conduit code and test cases, category syncing|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureTodo|Akregator|Basic support for enclosures (Displaying links, mimetype and size)|osterfeld@kde.org|Frank Osterfeld}}
{{FeatureTodo|KAlarm|Option to display alarm only if pre-alarm command succeeded|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application| christian_weilbach@.web.de|Christian Weilbach}}
{{FeatureTodo|Kleopatra|Konqueror and Dolphin Kleopatra plugins|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureTodo|KMail|Aggregated attachment view in the mail header area of the reader window|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KMail|Improved error messages and audit log for cryptographic operations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|Kontact|Support for Kontact wide profiles|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Ability to jump to the right day in the agenda from invitation mails|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Drag and drop in the free-busy view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for comments in replies to invitations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for extended free-busy lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Blog-styled journal view|mike@mikearthur.co.uk|Mike Arthur}}
{{FeatureTodo|KOrganizer|Blogging KResource|mike@mikearthur.co.uk|Mike Arthur}}
{{FeatureTodo|KPilot|Port old conduits to new base conduit architecture and KDE4/Qt4|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureTodo|KMail|Port to use KRichTextEdit|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|KBlogger|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|KNode|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
|}

= kdesdk =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Cervisia|New context menu entry "Add to Ignore List"|christian.loose@hamburg.de|Christian Loose}}
{{FeatureDone|Lokalize|Move this application (formerly known as Kaider) from extragear|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Cervisia|A file view based on KDirModel|christian.loose@hamburg.de|Christian Loose}}
{{FeatureInProgress|Lokalize|various Translation Memory enhancements|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|XLIFF support|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|KBugBuster|Make it work|fabiolocati@gmail.com|Fabio Locati}}
{{FeatureInProgress|KCachegrind|Everything working again|josef.weidendorfer@gmx.de|Josef Weidendorfer}}
{{FeatureInProgress|Kate|Session plasmoid|montel@kde.org|Laurent Montel}}
{{FeatureInProgress|KAppTemplate|Make a GUI for it - in playground/devtools|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KAppTemplate|Add a PyQt4 template|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KAppTemplate|Add a Ruby template|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KAppTemplate|Add a Plasmoid template|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KAppTemplate|Add DBUS support in templates|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KCachegrind|Better handling of huge symbols|josef.weidendorfer@gmx.de|Josef Weidendorfer}}
{{FeatureTodo|Lokalize|Kross-based scripting|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|QA: glossary checklists|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|kioslave svn|Add Export/Import feature|montel@kde.org|Laurent Montel}}
{{FeatureTodo|Kate App|Improved session management|kwrite-devel@kde.org|Kate Developers}}
|}

= kdetoys =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdeutils =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Okteta|binary/hex editor (successor to KHexEdit). Move from playground/utils.|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|make printing support only selection|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|ask artists for own icon|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for memory mapping of files|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add "Export as"|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|enable extract-strings tool and add copy|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|more explicit titels for undo/redo actions, also from filters|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|parameter dialog for "Copy as..."|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for blocking processes like printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|refactor KByteArrayView|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureInProgress|KDiskFree|Use Solid API|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureTodo|KwikDisk|Replace it by a Plasmoid (in the desktop bar and on the desktop|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureInProgress | KJots | Support more rich text features like text formatting, hyperlinks and ordered/unordered lists. | steveire@gmail.com | Stephen Kelly }}
{{FeatureDone | KJots | Add checkmarks to pages. | steveire@gmail.com | Stephen Kelly }}
{{FeatureInProgress | KJots | Port to KRichText widget. | steveire@gmail.com |Stephen Kelly }}
{{FeatureTodo | KJots | Create a Kontact::Plugin to integrate kjots into Kontact. | steveire@gmail.com |Stephen Kelly }}
|}

= kdevelop =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdevplatform =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdewebdev =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Kommander|Port the executor to KDE4.|amantia@kde.org|Andras Mantia}}
{{FeatureTodo|Kommander|Create Qt Designer plugins for the editor.|amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|Quanta Plus|Create an upload plugin.| niko.sams@gmail.com|Niko Sams}}
{{FeatureInProgress|Quanta Plus|Create a new, state machine based parser.| amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|Quanta Plus|Port existing functionality to KDevPlatform plugins. Only text mode is targeted.|amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|KXslDbg|Port to KDE4.|keith@kdewebdev.org |
Keith Isdale}}
{{FeatureTodo|KLinkStatus|Aided correction of broken links||}}
{{FeatureDone|KLinkStatus|Site check automation|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureInProgress|KLinkStatus|D-Bus/Scripting interfaces|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureInProgress|KLinkStatus|HTML validation|thesquib@gmail.com|Sam Ryan}}
{{FeatureDone|KLinkStatus|Ability to export only broken links|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Ability to do background search which only update the GUI when finished (much faster))|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Tray Icon and KUniqueApplication|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Scripting Plugin|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Get Hot New Stuff for HTML result stylesheets|Paulo Moura Guedes}}
|}

Development/Tutorials/Games/Highscores

2008-04-27T16:20:09Z

Milliams: /* Grouping Scores */

{{TutorialBrowser|

series=KDE Games|

name=High Scores|

pre=[[Development/Tutorials/Programming_Tutorial_KDE_4|Introduction to KDE4 programming]], [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction Tutorial]]|

next=|

reading={{class|KScoreDialog}}
}}

==Abstract==
This tutorial will explain how to use the high score system built into kdegames in your application.

[[image:Highscore.png|center|thumb|Dialog in KMines]]

==KScoreDialog==
The high score system is provided through the KScoreDialog class. It is intended to be a lightweight solution and offers the following abilities:
#Grouping of scores (for different difficulty levels etc.)
#Standard fields: Name, Level, Date, Time, Score
#Custom fields (e.g. number of moves)

==Displaying Scores==
To display the high score table, it's as simple as two lines of code.
<code cppqt n>
#include <KDE/KScoreDialog>

void showHighscores()
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.exec();
}
</code>
This will display the highscore table showing, by default, the 'Name' and 'Score' columns.

In order to comply with the kdegames standards, you should use a {{class|KStandardGameAction}} to launch this function. This will set up the icons and toolbars correctly. See the [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction tutorial]] for more information on this.
<code cppqt n>
#include <KDE/KStandardGameAction>
void setupActions()
{
KStandardGameAction::highscores(this,
SLOT(showHighscores()),
actionCollection());
setupGUI();
}
</code>

==Adding Scores==
===Simplest way to add a score===
The simplest way to add a new score to the table is as follows:
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int playersScore)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.addScore(playersScore);
ksdialog.exec();
}
</code>
This will add the score <tt>playersScore</tt> to the high score table and then launch the dialog. If it is the first score to be entered on the table, a blank line-edit will be provided for the player to enter their name, otherwise the line-edit will still be provided but the player's name will be automatically filled in.

However, you will notice that the dialog is shown every time, even if the player didn't manage to get onto the table. If you only want to show the table if the player achieved a high score, place an <tt>if()</tt> command around the <tt>KScoreDialog::addScore()</tt> call:
<code cppqt>
if(ksdialog.addScore(playersScore))
ksdialog.exec();
</code>

===Passing name by code===
If you want to suggest a name programatically you can do so by using the <tt>KScoreDialog::FieldInfo</tt> type. It's easy to use, for example:
<code cppqt n>
#include <KScoreDialog>

void newHighscore(int score, const QString& name)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = name;
scoreInfo[KScoreDialog::Score].setNum(score);

ksdialog.addScore(scoreInfo);
}
</code>

And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int score, const QString& name, int level)
{
KScoreDialog ksdialog(KScoreDialog::Name |
KScoreDialog::Level, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = name;
scoreInfo[KScoreDialog::Score].setNum(score);
scoreInfo[KScoreDialog::Level].setNum(level);

ksdialog.addScore(scoreInfo);
}
</code>
===Custom fields===
Since there are only a set number of standatd fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function.
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int score, const QString& name, int numMoves)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = "Matt";
scoreInfo[KScoreDialog::Score].setNum(playersScore);

ksdialog.addField(KScoreDialog::Custom1,
i18n("Num of Moves"), "moves");
scoreInfo[KScoreDialog::Custom1].setNum(numMoves);

ksdialog.addScore(scoreInfo);
}
</code>
The first argument to <tt>KScoreDialog::addField()</tt> must be from <tt>KScoreDialog::Custom1</tt> to <tt>KScoreDialog::Custom5</tt>, the second is the text that will appear on the high score table at the head of the column (and must therefore be i18n'd) and the last argument is a unique identifier for the field. After that, it is added to your <tt>KScoreDialog::FieldInfo</tt> in the same way as before.

==Grouping Scores==
Your game may have different levels of difficulty and so you don't want to put the scores for the 'Hard' level on the same table as the 'Easy' table. Grouping scores is easy to achieve using the <tt>KScoreDialog::setConfigGroup()</tt> function:
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int playersScore)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.setConfigGroup(I18N_NOOP("Easy"));
ksdialog.addScore(playersScore);
ksdialog.exec();
}
</code>
Each group will show up as a tab on the high score table dialog. If you don't specify a group, the score will be added to the generic 'High Score' tab.

A very important point to remember is to pass the untranslated group name through <tt>I18N_NOOP()</tt> otherwise the group name will not be translated properly and will cause bugs.

==Advanced Features==
===Hiding Fields===
In some special cases you won't want to display a score as such but rather just the time the player took to complete the level.

While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, ity is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.
<code cppqt n>
#include <KDE/KScoreDialog>

// timeString is a nicely formatted string
// e.g. "1:24" used for display
void newHighscore(const QString& timeString, int seconds)
{
KScoreDialog ksdialog(KScoreDialog::Name |
KScoreDialog::Time, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Time] = timeString;
scoreInfo[KScoreDialog::Score].setNum(seconds);
ksdialog.hideField(KScoreDialog::Score);
ksdialog.addScore(scoreInfo, KScoreDialog::LessIsMore)
ksdialog.exec();
}
</code>

[[Category:C++]]

User talk:Danimo

2008-04-18T12:53:25Z

Milliams: /* More readable URLs */ new section

Schedules/KDE4/4.1 Feature Plan

2008-04-14T18:10:37Z

Milliams: /* kdegames */

This is a list of planned features. The deadline for adding entries here for the 4.1 release is '''20 April 2008'''.

Entries added after that date will be scheduled for the 4.2 release.

Legend:
* todo => not started yet
* in-progress => started, but not completed yet
* done => completed
__TOC__
= kdelibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|kdeui|Add KFadeWidgetEffect to easily add fading UI transitions to KDE applications|kretz@kde.org|Matthias Kretz}}
{{FeatureDone|kdeui|Make icon naming spec compliant 3rd party icon themes like Tango or gnome-icon-theme work correctly.|jpetso@gmx.at|Jakob Petsovits}}
{{FeatureDone|kross|Add QtScript support|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KHTML|Support CSS3 Media Queries|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|Phonon KCM|More UI feedback|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|VideoWidget snapshot function|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|better integration of pulseaudio|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|make AbstractMediaStream/StreamInterface threadsafe|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|allow backend switching on the fly|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|Phonon|add Port class for fine grained control over data flow between Phonon objects|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|subtitle, audio track selection|kretz@kde.org|Matthias Kretz and Ian Monroe}}
{{FeatureInProgress|Phonon|"low-level" PCM I/O with at least an ALSA implementation|kretz@kde.org|Matthias Kretz and Ian Monroe}}
{{FeatureTodo|Phonon|update device preference on the fly|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|kdeui|Goya, a framework for inserting controls into itemviews in a really easy and fast way|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureInProgress|kdeui|Shortcut schemes for KDE applications|adymo@kdevelop.org|Alexander Dymo}}
{{FeatureDone|kmimetypetrader/kbuildsycoca|Replace use of profilerc for ordering applications with new mimeapps.list standard|faure@kde.org|David Faure}}
{{FeatureInProgress|knewstuff|Support caching, and speed up the interface through use of Models/Views and goya|jeremy@scitools.com|Jeremy Whiting}}
{{FeatureInProgress|Phonon KCM|Handle advanced devices|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|KDEPrint|Reintroduce KDEPrint in some form, depending on what Qt4.4 delivers.|john@layt.net|john Layt}}
{{FeatureInProgress|KDEPrint|Add CUPS Options tabs to QPrintDialog to support n-up, page borders, banner pages, page labels, mirror pages, job scheduling, and manual CUPS options.|john@layt.net|John Layt}}
{{FeatureTodo|KDEPrint|Add framework for standard actions for 'Send to...' for e-mail, fax, etc by printing to PDF/PS.|john@layt.net|John Layt}}
{{FeatureTodo|KDEPrint|Migrate FilePrinter class from Okular to enable file printing for all apps via QPrinter, modify to utilise new Qt4.4 features. To be discussed on k-c-d first.|john@layt.net|John Layt}}
{{FeatureInProgress|KIO|speed limits on KIO Transfers|nolis71cu@gmail.com|Manolo Valdes}}
{{FeatureInProgress|kdeui|Printing of shortcuts from the shortcut dialog|apaku@gmx.de|Andreas Pakulat}}
{{FeatureDone|Kate Part|Annotation framework for the editor|apaku@gmx.de|Andreas Pakulat}}
{{FeatureInProgress|KJS|Bytecode interpreter and performance improvements|maksim@kde.org|Maks Orlovich}}
{{FeatureInProgress|KHTML|Sync class and file structure with WebKit to prepare merging|porten@kde.org|Harri Porten}}
{{FeatureInProgress|KHTML|contentEditable/designMode implementation|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|KCalenderSystem|Complete migration of Jalali, Hijri, and Hebrew calendars to new code base.|john@layt.net|John Layt}}
{{FeatureTodo|KCalenderSystem|Add new calendar systems: Indian Civil (Saka), Ethiopean, Chinese, Pure Julian, Pure Gregorian. (Note, not all may live in kdelibs or be available as a global calendar system)|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement KLocale based methods to return weekend days and day of religious observance. Currently KCalendarSystem provides dayOfPray(), but for Gregorian this is not correct in all locales where it is used. Currently KDatePicker hardcodes Saturday and dayOfPray() as weekend days which may not be correct in all locales. To be discussed first on k-c-d and with kdepim.|john@layt.net|John Layt}}
{{FeatureDone|dnssd|Models for service browser and domain browser.|qbast@go2.pl|Jakub Stachowski}}
{{FeatureTodo|KHTML|Adaptable/Scriptable workarounds for broken websites.|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|KHTML|support for borders-* properties from the CSS3 Background and Borders Module|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|KHTML|Efficient smooth scrolling|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|KHTML|support for Audio/Video tags from the HTML5 draft specification|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|KHTML|merge support for speculative preloading of network resources|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|KHTML|CSS3 module: Web Fonts|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|KJS|Public API for extensions. Possibly analog to JavaScriptCore's C API.|porten@kde.org|Harri Porten}}
{{FeatureTodo|KTextEditor|Several interface extensions (e.g. open/save filter)|kwrite-devel@kde.org|Kate Developers}}
{{FeatureTodo|KTextEditor|Plugin for basic collaborative editing|kwrite-devel@kde.org|Kate Developers}}
{{FeatureInProgress|Kate Part|Scripting support for indentation and little helpers|kwrite-devel@kde.org|Kate Developers}}
{{FeatureTodo|Kate Part|Input modes to allow e.g. vim-like editing|kwrite-devel@kde.org|Kate Developers}}
{{FeatureDone|KIO|Implement support for inline editing in KFileItemDelegate|fredrik@kde.org|Fredrik Höglund}}
{{FeatureDone|KIO|Add support for drawing text shadows in KFileItemDelegate|fredrik@kde.org|Fredrik Höglund}}
{{FeatureTodo|Emoticons lib|An emoticons library so each applications doesn't have to implement the same things over and over again |brandon.ml@gmail.com|Carlo Segato}}
{{FeatureInProgress|KFile|Implement fd.o desktop-bookmark-spec for KFilePlacesModel|nf2@scheinwelt.at|Norbert Frese}}
{{FeatureTodo|kdeui| Support for About Data of libs and modules used by a program |kossebau@kde.org|Friedrich W. H. Kossebau}}
|}

= kdepimlibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Akonadi|Move the Akonadi development library from kdepim.|vkrause@kde.org|Volker Krause}}
{{FeatureInProgress|Akonadi|Item size ([[Projects/PIM/Akonadi#Core|details]])|thomas.mcguire@gmx.net|Thomas McGuire}}
{{FeatureTodo|Akonadi|Payload serialization format versioning ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureTodo|Akonadi|Item streaming in ItemSync/ResourceBase ([[Projects/PIM/Akonadi#Core|details]])|tomalbers@kde.nl|Tom Albers}}
{{FeatureInProgress|Akonadi|API for additional item parts ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org,tokoe@kde.org|Volker Krause/Tobias Koenig}}
{{FeatureInProgress|Akonadi|Infrastructure for showing additional dialogs from agents/resources ([[Projects/PIM/Akonadi#Core|details]])|tomalbers@kde.nl|Tom Albers}}
{{FeatureTodo|Akonadi|Allow to limit ItemFetchJob to current cache content ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureInProgress|Akonadi|Fix API for item/collection modifications ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureTodo|Akonadi|Error reporting ([[Projects/PIM/Akonadi#Core|details]])|tokoe@kde.org|Tobias Koenig}}
{{FeatureTodo|gpgme++2|newly designed gpgme++ (multithreaded, exceptions, less event loop integration: better for Windows)|marc@kdab.net|Marc Mutz (Gpg4win)}}
|}

= kdebase-apps =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Dolphin|Details-view: Allow to open folders as tree (turned off per default).|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|Dolphin|Refactor view-action handling to a DolphinViewActionHandler to share more code with DolphinPart|faure@kde.org|David Faure}}
{{FeatureDone|Konqueror|Re-implement Copy To / Move To in the popup menu|faure@kde.org|David Faure}}
{{FeatureTodo|Konqueror|Separate konquerorrc and kfmrc (at least useful for home URL and toolbar settings)|faure@kde.org|David Faure and Emanuele Tamponi}}
{{FeatureDone|Dolphin|Simplify selecting of files in the single-click mode (based on http://aseigo.blogspot.com/2006/04/icons.html).|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Raptor|The KDE4-Application-Menu}}
{{FeatureInProgress|Dolphin|Provide optional tooltips for files and directories.|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Dolphin|Tabs|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Konqueror|Bring back the large tooltip like in kde3|faure@kde.org|David Faure}}
{{FeatureTodo|Konqueror|Session management (save/restore session/restore from crash).|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|Konqueror|Support for undo closed window.|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureDone|Konqueror|Allow to configure the Dolphin KPart within the Konquerors settings dialog.|peter.penz@gmx.at|Peter Penz}}
|}

= kdebase-workspace =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Plasma|Kickoff orientation dependent layout|wstephenson@kde.org|Will Stephenson}}
{{FeatureDone|kmenuedit|Restore menu system|montel@kde.org|Laurent Montel}}
{{FeatureDone|KCM autostart|Configure autostart desktop file|montel@kde.org|Laurent Montel}}
{{FeatureDone|Plasma|improve fail to launch and needs
config|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Solid|Refactor Solid::Control networking|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|Solid|Backend for NetworkManager 0.7|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|System Settings|Filtering/Lazy load category modules|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|KSysGuard|Monitor process I/O|tapsell@kde.org|John Tapsell}}
{{FeatureInProgress|KDEPrint|Add printer applet for viewing print jobs and printer auto-configuration.|jriddell @ubuntu.com|Jonathan Riddell}}
{{FeatureTodo|Plasma|Mac-like menu bar plasmoid|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Color KCM|Add 'smart setting' of extended colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Add KDE3 scheme import|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Query kwin for supported colors; add full set of kwin colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KDEPrint|reintroduce KDEPrint Print Management tools, e.g. KCM, kprinter, kjobviewer, etc. Depends upon progress of kdelibs side of KDEPrint and Qt4.4 feature set.|john@layt.net|john Layt}}
{{FeatureTodo|System Settings|Administrator mode support|wstephenson@kde.org|Will Stephenson}}
{{FeatureTodo|krunner|Revamp GUI.|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|ksmserver|UI for selecting WMs|l.lunak@kde.org|Luboš Luňák}}
{{FeatureDone|Plasma|polish kickoff|wstephenson@kde.org|Will Stephenson}}
{{FeatureDone|Plasma|toolbox improvements |aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|GHNS2 plasma themes|jeremy@scitools.com|Jeremy Whiting}}
{{FeatureDone|Plasma|Resizable, relocatable panel|binner@kde.org|Stephan Binner}}
{{FeatureInProgress|Plasma|webkit widget|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|shared timer in engines|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|welcome plasmoid|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|dashboard widget support|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Plasmagik packaging|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Plasma|Scriptengines|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Plasma|QtScript scriptengine|richmoore44@gmail.com|Richard Moore}}
{{FeatureInProgress|Plasma|Filebrowser Plasmoid|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Plasma|Improve QtScript support|richmoore44@gmail.com|Richard Moore}}
{{FeatureInProgress|Plasma|Zooming User Interface|chanika@gmail.com|Chani Armitage}}
{{FeatureInProgress|Plasma|Multiple Desktop Containments|chanika@gmail.com|Chani Armitage}}
{{FeatureInProgress|Plasma|Networkmanager Plasmoid and DataEngine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureTodo|Plasma|Temperature sensing in the device engine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureTodo|Plasma|Video data in the device engine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureTodo|Plasma|New plasma theme|nuno@oxygen-icons.org|Nuno Pinheiro}}
{{FeatureTodo|Plasma|physics-based animator|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Top-level windows plasmoids|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|change showConfigurationInterfaction to createConfigurationInterface|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Plasma::Service |aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Keyboard shortcuts |aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|panel hiding |aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|panel toolbox |aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|KWin|non-linear animations also for KWin|sebas@kde.org|Sebastian Kuegler}}
{{FeatureInProgress|Plasma|Generic folder view applet/containment, that can also be used as the desktop background (showing the desktop folder).|fredrik@kde.org|Fredrik Höglund}}
{{FeatureTodo|KDM|Theme KDM (login manager) by default|uwolfer@kde.org|Urs Wolfer}}
{{FeatureInProgress|Nepomuk|Simple Desktop Search client based on Nepomuk search|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Plasma|Add a dataengine that implements galago-project Notifications DBus interface and a plasmoid which provides cute visualization of notifications along with nice and easy way to interact with them|dimsuz@gmail.com|Dmitry Suzdalev}}
|}

= kdebase-runtime =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|nepomuk|Service that monitors file rename and delete operations and updates the metadata accordingly. kded module already exists in playground. problem: depends on inotify.|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|KCM emoticons|Adding/editing/removing emoticons theme|brandon.ml@gmail.com|Carlo Segato}}
{{FeatureInProgress|phonon-xine|snapshots in video widget|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|try to make VideoWidget work on GraphicsView|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|make states compatible to other backends|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|better support for pulseaudio (most work possibly in kdelibs)|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-gstreamer|Make phonon-gstreamer as released with Qt 4.4 fully integrate into KDE and add the features added to libphonon after libphonon 4.1|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|desktop ioslave|Add an ioslave that lists the contents of the desktop folder, and reports the names in the .desktop files instead of the actual file names.|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|knotify|Add support for galago desktop notifications spec - if knotify will find a certain DBus service on session bus, it'll forward its popup notification events to this service |dimsuz@gmail.com|Dmitry Suzdalev}}
|}

= kdeaccessibility =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KMagnifier|Add color blindness simulation|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KMagnifier|Refactor color menu, re-add invert, add color-shift modes to help people with color blindness|mw_triad@users.sourceforge.net|Matthew Woehlke}}
|}

= kdeadmin =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KSystemLog|KSystemLog, a Log Viewer Tool. Move from kde-apps|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Do some refactoring in KCron|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Improve ergonomy and general interface|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Fix all existing bugs in KCron|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Convert KCron into a KCM Module, to use it in System Settings|nicolas.ternisien@gmail.com}}
{{FeatureInProgress|Environment Variables|Create a environment variables KCM Module|nicolas.ternisien@gmail.com}}
|}

= kdeartwork =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdebindings =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|Smoke2|Move Smoke2 to kdebindings-trunk.|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureTodo|PHP-Qt|Move PHP-Qt to kdebindings-trunk.|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureTodo|kross|Move krossjava to kdebindings-trunk.|mail@dipe.org|Sebastian Sauer}}
{{FeatureTodo|General|Wrap some more APIs (at least Akanodi for all languages and Plasma for C#)|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureTodo|Qyoto|Add delegate support for signal/slot connections.|kde-bindings@kde.org|KDE-bindings developers}}
|}

= kdeedu =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Kalzium|Clean up the database. I am syncing with the BlueObelisk data repository again. There we decided to remove the density (not a element property but a compound property. I also removed the mean weight. We think it is better to provide correct data than a lot (but partly wrong) data.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureDone|KAlgebra|Calculator Plasmoid|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|KAlgebra|Vector support|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|Step|A physics simulator, move from playground to kdeedu module |ks.vladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureDone|Kalzium|Update the snapshot of libavogadro to 0.6.1. This introduces a gazillion new possibilities for the 3D renderer and fixes many issues.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|Kalzium|Make use of the new libavogadro-version.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|Marble|DGML2 Support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|KDE-Version settings dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Port authors list from the Qt-About dialog to the KDE-About dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Qt-Version settings dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Improved KML support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|OpenStreetMap support using original OSM tiles|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Real Time Cloud-Cover|tackat@kde.org|David Roberts / Torsten Rahn}}
{{FeatureTodo|Marble|Map Contents translation|tackat@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Copy position to clipboard|tackat@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Create Tiles on compile time|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Mercator Projection|inge@lysator.liu.se|Inge Wallin}}
{{FeatureInProgress|Marble|More generic projection support|inge@lysator.liu.se|Inge Wallin}}
{{FeatureInProgress|Marble|Usage of Marble in non-widgets|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Export map to MxN pixel bitmap|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Support for MarbleWidget::setEnabled( bool )|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Layer Management Class|tokoe@kde.org|Tobias König}}
{{FeatureTodo|Marble|Plugin architecture for map layers|tokoe@kde.org|Tobias König}}
{{FeatureInProgress|KEduca|Rewrite of the classic test writing/taking application|matt@milliams.com|Matt Williams}}
{{FeatureInProgress|Parley|Redesigned main window|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|Parley|Vocabulary Plasmoid|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|KBruch and KPercentage|Merge in 1 app|pete@pmurdoch.com|Peter Murdoch}}
{{FeatureInProgress|Kalzium|Plasmoid to access Kalzium database|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|Step|Improve GUI for creating gas and softbody|ksvladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureTodo|KAlgebra|Variables share between calculations|aleixpol@gmail.com|Aleix Pol}}
{{FeatureTodo|KTurtle|Export canvas as image|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Optional rulers/grid for canvas units|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Add command line|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Add a color picker|nielsslot@gmail.com|Niels Slot}}
{{FeatureTodo|Parley|Declensions|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureTodo|Parley|Rewrite of practice|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureTodo|KLettres|Number support|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Add a Open File action|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Integrate an editor|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Plasmoid|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Kiten|Link radselect with kiten|jkerian@gmail.com|Joe Kerian}}
{{FeatureInProgress|Kiten|Sort output by dictionary/user selected sorting values|jkerian@gmail.com|Joe Kerian}}
{{FeatureTodo|Step|Use common constraints handling code for collisions|ksvladimir@gmail.com|Vladimir Kuznetsov}}
|}

= kdegames =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KDiamond|New game, move to kdegames|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|KDiamond|Get themes with KNewStuff|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|KNetWalk|Better scoring system|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureDone|KNetWalk|Add support for loading new themes|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureDone|Kollision|Move to kdereview/kdegames|p.capriotti@gmail.com|Paolo Capriotti}}
{{FeatureDone|Kubrick|New game, 3D OpenGL - move to playground|ianw}}
{{FeatureDone|Kubrick|Polish up the features|ianw}}
{{FeatureDone|Kubrick|Port to Qt4 and KDE4|ianw}}
{{FeatureDone|KBlocks|Finish display of points and level|piacentini@kde.org}}
{{FeatureDone|KBlocks|Implement KNewStuff support|piacentini@kde.org}}
{{FeatureDone|KBlocks|Implement key/action/shortcut configuration|piacentini@kde.org}}
{{FeatureDone|KBlocks|Docbook|piacentini@kde.org}}
{{FeatureInProgress|KGoldRunner|Improved theming and animation|mikelima@cirulla.net}}
{{FeatureInProgress|KGoldRunner|Sound support and theming|mikelima@cirulla.net}}
{{FeatureInProgress|KSquares|Multiplayer support|josef}}
{{FeatureInProgress|KBattleship|Bring back Zeroconf support for network games|qbast@go2.pl}}
{{FeatureInProgress|Kubrick|New game, 3D OpenGL - in kdereview|ianw}}
{{FeatureInProgress|KGGZ|Add kggzcore and kggzdmod libraries|josef}}
{{FeatureTodo|KBlocks|Add additional themes|piacentini@kde.org}}
{{FeatureInProgress|KBreakout|Finish it, and move it from playground to kdegames|fela.kde@gmail.com}}
{{FeatureTodo|KGGZ|Add new Qt4-based core client as successor to the old KDE3-based KGGZ|josef (now SoC proposal)}}
{{FeatureTodo|KGGZ|Fire-and-forget highscore submission for single-player games and client-to-client multiplayer games|josef)}}
{{FeatureTodo|KGoldRunner|Also see kdegames/kgoldrunner/TODO|ianw}}
{{FeatureTodo|KGoldRunner|Hot new stuff support for themes and levels|mikelima@cirulla.net}}
{{FeatureTodo|KGoldRunner|Startup screen|mikelima@cirulla.net}}
{{FeatureTodo|KMahjongg|Reimplement the Board Editor|piacentini@kde.org}}
{{FeatureTodo|KMines|Add pause actions|piacentini@kde.org}}
{{FeatureTodo|KNetWalk|Configurable keyboard support|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KShisen|Port to KScoreDialog|piacentini@kde.org}}
{{FeatureTodo|Kubrick|See SVN file kubrick/TODO|ianw}}
{{FeatureTodo|Kubrick|Move to KDE Games for 4.1|ianw}}
|}

= kdegraphics =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Gwenview|Undo system|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Gwenview|Fullscreen meta information|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Gwenview|Ability to open an image with another application|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Okular|Better Text-To-Speech integration: speech the whole document, the current page or the selection.|pino@kde.org|Pino Toscano}}
{{FeatureDone|Okular|Encryption support for ODF generator|bradh@kde.org}}
{{FeatureInProgress|Okular|Backward direction for text search.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Centralized text & graphics antialias configuration.|pino@kde.org|Pino Toscano}}
{{FeatureDone|Okular|EPub backend.|elylevy@cs.huji.ac.il|Ely Levy}}
{{FeatureInProgress|Okular|Improved form support (add missing types, handle the fields better).|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Gwenview|Support for tagging with Nepomuk|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Thumbnail bar in view and fullscreen modes|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Crop ratio|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|KIPI support|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Red eye correction|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Okular|JavaScript support (mostly for PDF documents).|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Improved placement and sizing of the presentation mode: choose the screen to use, adapt to screen size changes.|pino@kde.org|Pino Toscano}}
|}

= kdemultimedia =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Dragon Player|A simple Phonon-based videoplayer application|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|Make Dragon indipendent from Xine|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|File Manager|David Edmunson}}
|}

= kdenetwork =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KGet|Group-Settings|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Torrent-Support|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Transfer-Settings|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Webinterface|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|Kopete|AIM offline messages|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|OTR Encryption support|michael_zanetti@gmx.net|Michael Zanetti}}
{{FeatureDone|Kopete|Status manager|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|KGet|MultiSource-Downloading|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|Kopete|Bring back chat style and emoticon selection via knewstuff2|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Kopete|ICQ 6 status icons|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|Kopete|MSNP15 implementation for MSN|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|Non-intrusive notification system|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|Kopete|UPnp Support|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|Updated contact list interface (uses Qt 4 rather than Qt 3)|mattr@kde.org|Matt Rogers}}
{{FeatureTodo|Kopete|Update Kopete to better support Decibel|kopete-devel@kde.org|Kopete Developers}}
{{FeatureInProgress|KGet|Nepomuk-Integration|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|KGet|Support mms://-protocol, see https://launchpad.net/libmms|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Global Speedlimits|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Setup libbtcore from KTorrent in KGet (to avoid dependency to extragear)|uwolfer@kde.org|Urs Wolfer}}
{{FeatureInProgress|KGet|Extend the TransferHistory to use SQLite and XML-Backends and display the information inside a kcategorizedview|jgoday@gmail.com|Javier Goday}}
{{FeatureTodo|Kopete|GroupWise chatroom support|wstephenson@kde.org|Will Stephenson}}
{{FeatureTodo|[http://decibel.kde.org Decibel]|Decibel, a framework for real time communication services. Move from playground/pim|info@basyskom.de|Tobias Hunger}}
{{FeatureDone|KRDC|Optional system tray icon (with quick access to bookmarks)|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Improved behavior of entering special keys for better workflow|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Zeroconf support (detecting remote desktop services in local network)|romnes@stud.ntnu.no|Magnus Romnes}}
{{FeatureInProgress|KRDC|Bookmark dock widget for quick access to bookmars, zero conf detected services and recently used connections|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Support for up- and downscaling VNC remote desktop|uwolfer@kde.org|Urs Wolfer}}
|}

= kdepim =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KAddressbook|Ability to add LDAP search results to distribution lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|Indication of which resource folder a contact belongs to|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|Read-only view for contacts in read-only folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|copy/cut/paste context menu items|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Ability to create hyperlinks in HTML messages|steveire@gmail.com|Stephen Kelly}}
{{FeatureDone|KMail|Ability to easily create todos with reminders from emails|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Ability to open messages from search results when the reader is hidden|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better invitation update emails showing what changed|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better reminder visualization in very small events|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better, natural language search criteria names|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Clickable status columns|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Client side configurability of warnings in shared folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Colored ribbons for indication of signing and encryption status in the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Configuration option for whether invitation emails are automatically deleted or not when having been acted upon|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Copy/paste and drag and drop from/to the mail composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Decryption on demand in reader window|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Display of quota information in foldertree tooltips|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop and copy and paste support in the search result viewer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop from the mail reader window and mime-tree viewer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop of folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Editing of attachments from the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Export and import of filters|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Favorites Folder|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Folder quicksearch|m.koller@surfeu.at|Martin Koller}}
{{FeatureDone|KMail|Harmonization of actions in main and standalone mail reader windows|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|IMAP Server storage of non-standard flags|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Improved TNEF attachment handling|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Improved quota warnings|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Initialize full search from quicksearch on request|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Override font and fontsize for standalone message viewers|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Per-folder identity configurability|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Recursive IMAP cache troubleshooting|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Resizable recipients area in composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for creating new mails based on received mails (Resend)|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for immediate sync of resource folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for soft line breaking|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Tab navigation through groups in the address completion|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Text snippets with shortcuts and variable expansion in the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Warning about active out-of-office scripts|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|lost+found recovery of locally changed folders that lose access rights|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KNotes|Ability to print notes|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Ability to have both distribution lists and addresbook extension visible|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Aggregated reminders view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Better default resource colors|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Drag and drop of attachments|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Faster initial loading of kolab resources|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Forwarding and delegation of invitations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Improved coloring of agenda view items|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Improved event printing|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Merge of the attachment view in into the main page|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Merge of the free-busy and attendee views for easier scheduling|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Month view scrolling, paging, mouse-wheeling|tom_t@gmx.at|Thomas Thrainer}}
{{FeatureDone|KOrganizer|More readable Kolab resource folder labels|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Redesigned incidence editor UI|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Side-by-side calendar view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Support for by-value attachments|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Timeline calendar view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kleopatra|Ability to search in internal and external certificates at the same time|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kleopatra|General UI Server|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|Kleopatra|New, tabbed, mainwindow design|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|KonsoleKalendar|Support "file" and "localdir" resources|winter@kde.org|Allen Winter}}
{{FeatureDone|Kontact|Config option to close despite system tray|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Harmonization of component naming in sidebar, configuration, summary view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Right-aligned component navigation toolbar|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Ubiquitous sync actions|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Column-specific whatsthis-help| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Combined search and add task widget| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Drag&Drop| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|File management (file->load)| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Managing history| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Tracking tasks by active applications| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Whatsthis-help dependant on if a task has been created| |Thorsten Stärk}}
{{FeatureDone|KOrganizer|Rich text incidence editor|mike@mikearthur.co.uk|Mike Arthur}}
{{FeatureInProgress|KMail|HTML Signatures|yez@familieschepers.nl|Edwin Schepers}}
{{FeatureInProgress|KPilot|Finish Keyring conduit, base conduit code and test cases, category syncing|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureInProgress|Kleopatra|OpenPGP support|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureInProgress|KNotes|Zeroconf support for sending notes on LAN|qbast@go2.pl|Jakub Stachowski}}
{{FeatureInProgress|Kontact|New Planner summary; combines Appointment+To-do+SpecialDates into 1 pretty summary|winter@kde.org|Allen Winter}}
{{FeatureTodo|KAlarm|New option to specify reminder times in minutes|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|KAlarm|Prevent multiple identical error messages accumulating for the same alarm|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|KAlarm|Remember main window show/hide options used when KAlarm closed instead of setting them in Preferences dialog|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|KAlarm|Remove alarm daemon and do all scheduling in kalarm itself|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|KAlarm|Replace simple repetitions by recurrence sub-repetitions to reduce confusion|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|KAlarm|Simplification and improvements to alarm edit dialog|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|KMail|Aggregated attachment view in the mail header area of the reader window|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KMail|Improved error messages and audit log for cryptographic operations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Ability to jump to the right day in the agenda from invitation mails|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Drag and drop in the free-busy view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for comments in replies to invitations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for extended free-busy lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KPilot|Port old conduits to new base conduit architecture and KDE4/Qt4|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureTodo|Kleopatra|Konqueror and Dolphin Kleopatra plugins|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureTodo|Kontact|Support for Kontact wide profiles|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application| christian_weilbach@.web.de|Christian Weilbach}}
{{FeatureTodo|KOrganizer|Blog-styled journal view|mike@mikearthur.co.uk|Mike Arthur}}
{{FeatureTodo|KOrganizer|Blogging KResource|mike@mikearthur.co.uk|Mike Arthur}}
{{FeatureInProgress|KOrganizer|New To-do View (model/view)|tom_t@gmx.at|Thomas Thrainer}}
{{FeatureInProgress|KOrganizer|New Month View (qgraphicsitem)|bvirlet@kdemail.net|Bruno Virlet}}
{{FeatureDone|KOrganizer|Hide/Show reminder daemon icon in the systeay|winter@kde.org|Allen Winter}}
|}

= kdesdk =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Cervisia|New context menu entry "Add to Ignore List"|christian.loose@hamburg.de|Christian Loose}}
{{FeatureDone|Lokalize|Move this application (formerly known as Kaider) from extragear|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Cervisia|A file view based on KDirModel|christian.loose@hamburg.de|Christian Loose}}
{{FeatureInProgress|Lokalize|various Translation Memory enhancements|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|XLIFF support|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|KBugBuster|Make it work|fabiolocati@gmail.com|Fabio Locati}}
{{FeatureInProgress|KCachegrind|Everything working again|josef.weidendorfer@gmx.de|Josef Weidendorfer}}
{{FeatureInProgress|Kate|Session plasmoid|montel@kde.org|Laurent Montel}}
{{FeatureInProgress|KAppTemplate|Make a GUI for it - in playground/devtools|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KAppTemplate|Add a PyQt4 template|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KAppTemplate|Add a Ruby template|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KAppTemplate|Add a Plasmoid template|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KAppTemplate|Add DBUS support in templates|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KCachegrind|Better handling of huge symbols|josef.weidendorfer@gmx.de|Josef Weidendorfer}}
{{FeatureTodo|Lokalize|Kross-based scripting|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|QA: glossary checklists|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|kioslave svn|Add Export/Import feature|montel@kde.org|Laurent Montel}}
{{FeatureTodo|Kate App|Improved session management|kwrite-devel@kde.org|Kate Developers}}
|}

= kdetoys =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdeutils =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Okteta|bytelevel editor (successor to KHexEdit). Move from playground/utils.|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|make printing support only selection|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|ask artists for own icon|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for memory mapping of files|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add "Export as"|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|enable extract-strings tool and add copy|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|more explicit titels for undo/redo actions, also from filters|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|parameter dialog for "Copy as..."|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for blocking processes like printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureInProgress|KDiskFree|Use Solid API|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureTodo|KwikDisk|Replace it by a Plasmoid (in the desktop bar and on the desktop|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
|}

= kdevelop =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdevplatform =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdewebdev =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Kommander|Port the executor to KDE4.|amantia@kde.org|Andras Mantia}}
{{FeatureTodo|Kommander|Create Qt Designer plugins for the editor.|amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|Quanta Plus|Create an upload plugin.| niko.sams@gmail.com|Niko Sams}}
{{FeatureInProgress|Quanta Plus|Create a new, state machine based parser.| amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|Quanta Plus|Port existing functionality to KDevPlatform plugins. Only text mode is targeted.|amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|KXslDbg|Port to KDE4.|keith@kdewebdev.org |
Keith Isdale}}
{{FeatureTodo|KLinkStatus|Aided correction of broken links||}}
{{FeatureDone|KLinkStatus|Site check automation|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureInProgress|KLinkStatus|D-Bus/Scripting interfaces|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureInProgress|KLinkStatus|HTML validation|thesquib@gmail.com|Sam Ryan}}
{{FeatureDone|KLinkStatus|Ability to export only broken links|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Ability to do background search which only update the GUI when finished (much faster))|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Tray Icon and KUniqueApplication|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Scripting Plugin|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Get Hot New Stuff for HTML result stylesheets|Paulo Moura Guedes}}
|}

Talk:Development/Tutorials/Saving and loading

2008-04-14T14:02:59Z

Milliams: /* Solution for "undefined reference to `vtable for MainWindow'" */

== Compiling failed due to 'undefined reference to vtable ...' ==
When compiling, cmake failed during the linking process.
<code>
undefined reference to `vtable for MainWindow'
</code>

I received this error, after making one tiny mistake: I named my headerfile
<code>mainwindow.hpp</code>
instead of
<code>mainwindow.h</code>
Once renamed, everything should work fine.

Tiny hint: if you quickly want to copy the source displayed in this tutorial, but are as annoyed as I am about the line numbering which is copied as well, use the edit function of this site to access the (barebone) sourcecode.
: I just tested this with Konq, Firefox and Opera and none of them copied the line numbering. What browser are you using? --[[User:Milliams|milliams]] 15:00, 22 March 2008 (CET)

== Solution for "undefined reference to `vtable for MainWindow'" ==

When I tried to compile the code, I got the same error:

<code>undefined reference to `vtable for MainWindow'</code>

This is because you have to change CMakeLists.txt in order to generate .moc files. Just add this line:

<code>qt4_automoc(${tutorial4_SRCS})</code>

Then you also have to add this line at the bottom of mainwindow.cpp:

<code>#include "mainwindow.moc"</code>

This fixed the problem for me. Please try this and post your results so I can correct the tutorial.

: You shouldn't need to use <tt>qt4_automoc()</tt> at all. With the code copied verbatim from the tutorial it builds just fine. The <tt>kde4_add_executable()</tt> does all that magic itself. According to Thiago, "If kde4automoc [which is called by kde4_add_executable() I believe] finds a header with Q_OBJECT whose .moc isn't included anywhere, it'll include that from a .cpp" --[[User:Milliams|milliams]] 16:02, 14 April 2008 (CEST)

Development/Tutorials/Games/Highscores

2008-04-12T22:32:40Z

Milliams: Correct include path

{{TutorialBrowser|

series=KDE Games|

name=High Scores|

pre=[[Development/Tutorials/Programming_Tutorial_KDE_4|Introduction to KDE4 programming]], [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction Tutorial]]|

next=|

reading={{class|KScoreDialog}}
}}

==Abstract==
This tutorial will explain how to use the high score system built into kdegames in your application.

[[image:Highscore.png|center|thumb|Dialog in KMines]]

==KScoreDialog==
The high score system is provided through the KScoreDialog class. It is intended to be a lightweight solution and offers the following abilities:
#Grouping of scores (for different difficulty levels etc.)
#Standard fields: Name, Level, Date, Time, Score
#Custom fields (e.g. number of moves)

==Displaying Scores==
To display the high score table, it's as simple as two lines of code.
<code cppqt n>
#include <KDE/KScoreDialog>

void showHighscores()
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.exec();
}
</code>
This will display the highscore table showing, by default, the 'Name' and 'Score' columns.

In order to comply with the kdegames standards, you should use a {{class|KStandardGameAction}} to launch this function. This will set up the icons and toolbars correctly. See the [[Development/Tutorials/Games/KStandardGameAction|KStandardGameAction tutorial]] for more information on this.
<code cppqt n>
#include <KDE/KStandardGameAction>
void setupActions()
{
KStandardGameAction::highscores(this,
SLOT(showHighscores()),
actionCollection());
setupGUI();
}
</code>

==Adding Scores==
===Simplest way to add a score===
The simplest way to add a new score to the table is as follows:
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int playersScore)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.addScore(playersScore);
ksdialog.exec();
}
</code>
This will add the score <tt>playersScore</tt> to the high score table and then launch the dialog. If it is the first score to be entered on the table, a blank line-edit will be provided for the player to enter their name, otherwise the line-edit will still be provided but the player's name will be automatically filled in.

However, you will notice that the dialog is shown every time, even if the player didn't manage to get onto the table. If you only want to show the table if the player achieved a high score, place an <tt>if()</tt> command around the <tt>KScoreDialog::addScore()</tt> call:
<code cppqt>
if(ksdialog.addScore(playersScore))
ksdialog.exec();
</code>

===Passing name by code===
If you want to suggest a name programatically you can do so by using the <tt>KScoreDialog::FieldInfo</tt> type. It's easy to use, for example:
<code cppqt n>
#include <KScoreDialog>

void newHighscore(int score, const QString& name)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = name;
scoreInfo[KScoreDialog::Score].setNum(score);

ksdialog.addScore(scoreInfo);
}
</code>

And in this same way you can display other default fields by passing them to the <tt>KScoreDialog</tt> constructor and adding the information to your <tt>KScoreDialog::FieldInfo</tt>. For example, to display the level the player got to:
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int score, const QString& name, int level)
{
KScoreDialog ksdialog(KScoreDialog::Name |
KScoreDialog::Level, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = name;
scoreInfo[KScoreDialog::Score].setNum(score);
scoreInfo[KScoreDialog::Level].setNum(level);

ksdialog.addScore(scoreInfo);
}
</code>
===Custom fields===
Since there are only a set number of standatd fields it is possible to add you own custom fields. For example you may want to put the number of moves the player made on the table. This is done through the <tt>KScoreDialog::addField()</tt> function.
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int score, const QString& name, int numMoves)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Name] = "Matt";
scoreInfo[KScoreDialog::Score].setNum(playersScore);

ksdialog.addField(KScoreDialog::Custom1,
i18n("Num of Moves"), "moves");
scoreInfo[KScoreDialog::Custom1].setNum(numMoves);

ksdialog.addScore(scoreInfo);
}
</code>
The first argument to <tt>KScoreDialog::addField()</tt> must be from <tt>KScoreDialog::Custom1</tt> to <tt>KScoreDialog::Custom5</tt>, the second is the text that will appear on the high score table at the head of the column (and must therefore be i18n'd) and the last argument is a unique identifier for the field. After that, it is added to your <tt>KScoreDialog::FieldInfo</tt> in the same way as before.

==Grouping Scores==
Your game may have different levels of difficulty and so you don't want to put the scores for the 'Hard' level on the same table as the 'Easy' table. Grouping scores is easy to achieve using the <tt>KScoreDialog::setConfigGroup()</tt> function:
<code cppqt n>
#include <KDE/KScoreDialog>

void newHighscore(int playersScore, const QString& difficulty)
{
KScoreDialog ksdialog(KScoreDialog::Name, this);
ksdialog.setConfigGroup(difficulty);
ksdialog.addScore(playersScore);
ksdialog.exec();
}
</code>
Each group will show up as a tab on the high score table dialog. If you don't specify a group, the score will be added to the generic 'High Score' tab.

==Advanced Features==
===Hiding Fields===
In some special cases you won't want to display a score as such but rather just the time the player took to complete the level.

While you're not going to display the 'Score' field in your table you must always submit a value to 'Score' field since it is used for sorting the scores. In fact, the 'Score' field is always present in a <tt>KScoreDialog</tt> object even if you didn't pass it to the constructor. However, ity is possible to hide the 'Score' field (and in fact any field) from display using the <tt>KScoreDialog::hideField()</tt> function. It takes a Field flag from the same set that the constructor takes.
<code cppqt n>
#include <KDE/KScoreDialog>

// timeString is a nicely formatted string
// e.g. "1:24" used for display
void newHighscore(const QString& timeString, int seconds)
{
KScoreDialog ksdialog(KScoreDialog::Name |
KScoreDialog::Time, this);

KScoreDialog::FieldInfo scoreInfo;
scoreInfo[KScoreDialog::Time] = timeString;
scoreInfo[KScoreDialog::Score].setNum(seconds);
ksdialog.hideField(KScoreDialog::Score);
ksdialog.addScore(scoreInfo, KScoreDialog::LessIsMore)
ksdialog.exec();
}
</code>

[[Category:C++]]

Development/Tutorials/Games/KStandardGameAction

2008-04-12T22:31:51Z

Milliams: /* Usage */ Correct include path

{{TutorialBrowser|

series=KDE Games|

name=KStandardGameAction|

pre=[[Development/Tutorials/Programming_Tutorial_KDE_4|Introduction to KDE4 programming]]|

next=[[Development/Tutorials/Games/Highscores|High Scores Tutorial]]|

reading={{class|KStandardGameAction}}, {{class|KStandardAction}}
}}

==Abstract==
This tutorial will explain the usage of <tt>KStandardGameAction</tt>s in libkdegames.

== KStandardGameAction ==
This class is an extension to the usual <tt>KStandardAction</tt> class which provides easy access to often used KDE actions.

Using these actions helps maintaining consistency among the games.

Games often use different menu entries than other programs, e.g. games use
the menu "game" instead of "file". This class provides the entries which
differ from the usual KStandardAction entries.

== Usage ==
Add some code like this to your action setup code.
<code cppqt n>
#include <KDE/KStandardGameAction>

void setupActions()
{
// Game
KStandardGameAction::gameNew(this,
SLOT(newGame()),
actionCollection());
KStandardGameAction::highscores(this,
SLOT(showHighscores()),
actionCollection());
KStandardGameAction::quit(this,
SLOT(close()),
actionCollection());

// Move
KStandardGameAction::undo(this,
SLOT(undoMove()),
actionCollection());
KStandardGameAction::redo(this,
SLOT(redoMove()),
actionCollection());

// Settings
KStandardGameAction::configureHighscores(this,
SLOT(configureHighscores()),
actionCollection());

setupGUI();
}
</code>

[[Category:C++]]

Development/Tutorials/First program

2008-03-22T14:02:23Z

Milliams: /* The Code */ Add bracket

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

series=Beginner Tutorial|

name=Hello World|

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [http://www.trolltech.com/products/qt/ Qt], [[Getting_Started/Build/KDE4|KDE4 development environment]]|

next=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]]|

reading=[[Development/Tutorials/CMake|CMake]]
}}

==Abstract==
Your first program shall greet the world with a friendly "Hello World", what else? For that, we will use a {{class|KMessageBox}} and customise one of the buttons.
[[image:introtokdetutorial1.png|frame|center]]

{{tip|To get more information about any class you come across, Konqueror offers a quick shortcut. So to look for information about KMessageBox, just type "kde:kmessagebox" into Konqueror and you'll be taken to the documentation.}}

{{tip|
You might want to use KDevelop for your projects, which does many nice things like code completion, easy access to API documentation or debugging support.

Read [[Getting_Started/Set_up_KDE_4_for_development#KDevelop|this tutorial]] to set up KDevelop correctly for this task. You probably want to check if the setup is working by testing opening an existing KDE 4 application with KDevelop first.

You still need to edit the CMake files by hand though.
}}

==The Code==
All the code we need will be in one file, <tt>main.cpp</tt>. Create that file with the code below:
<code cppqt>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>
#include <KMessageBox>

int main (int argc, char *argv[])
{
KAboutData aboutData(
// The program name used internally.
"tutorial1",
// The message catalog name
// If null, program name is used instead.
0,
// A displayable program name string.
ki18n("Tutorial 1"),
// The program version string.
"1.0",
// Short description of what the app does.
ki18n("Displays a KMessageBox popup"),
// The license this code is released under
KAboutData::License_GPL,
// Copyright Statement
ki18n("(c) 2007"),
// Optional text shown in the About box.
// Can contain any information desired.
ki18n("Some text..."),
// The program homepage string.
"http://tutorial.com",
// The bug report email address
"submit@bugs.kde.org");

KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;
KGuiItem yesButton( i18n( "Hello" ), QString(),
i18n( "This is a tooltip" ),
i18n( "This is a WhatsThis help text." ) );
KMessageBox::questionYesNo( 0, i18n( "Hello World" ),
i18n( "Hello" ), yesButton );
}
</code>
The first KDE specific code we come across in this program is {{class|KAboutData}}. This is the class used to store information about the program such as a short description, authors or license information. Pretty much every KDE application should use this class.

Then we come to {{class|KCmdLineArgs}}. This is the class one would use to specify command line switches to, for example, open the program with a specific file. However, in this tutorial, we simply initialise it with the {{class|KAboutData}} object we created so we can use the <tt>--version</tt> or <tt>--author</tt> switches.

Then we create a {{class|KApplication}} object. This needs to be done exactly once in each program since it is needed for things such as [[Development/Tutorials/Localization/i18n|i18n]].

Now we've done all the necessary KDE setup, we can move on to doing interesting things with our application. We're going to create a popup box but we're going to customise one of the buttons. To do this customisation, we need to use a {{class|KGuiItem}} object. The first argument in the {{class|KGuiItem}} constructor is the text that will appear on the item (in our case, a button). Then we have an option of setting an icon for the button but we don't want one so we just give it <tt>QString()</tt>. We then set the tooltip (what appears when you hover over an item) and finally the "What's This?" (accessed through right-clicking or Shift-F1) text.

Now we have our item, we can create our popup. We call the <tt>{{class|KMessageBox}}::questionYesNo()</tt> function which, by default, creates a message box with a "Yes" and a "No" button. The second argument is the text that will appear in the message box above the buttons. The third is the caption the window will have and finally we set the KGuiItem for (what would normally be) the "Yes" button to the <tt>KGuiItem guiItem</tt> we created.

Note that all user-visible text is passed through the i18n() function; this is necessary for the UI to be translatable. More information on localization can be found in the [[Development/Tutorials/Localization/i18n|localization tutorial]].

We're all done as far as the code is concerned. Now to build it and try it out.

==Build==
If you set up your environment as described in [[Getting Started/Build/KDE4]], you can compile this code with

g++ main.cpp -o tutorial1 \
-I$QTDIR/include/Qt \
-I$QTDIR/include/QtCore \
-I$QTDIR/include \
-I$KDEDIR/include/KDE \
-I$KDEDIR/include \
-L$KDEDIR/lib \
-L$QTDIR/lib -lQtCore -lQtGui -lkdeui -lkdecore
and then run it with
dbus-launch ./tutorial1

on some platforms the libraries might have to be linked with -lQtCore4 and -lQtGui4.

===Using CMake===
If that worked, you may want to use [[Development/Tutorials/CMake|CMake]], just like the rest of KDE. This will automatically locate the libraries and headers for KDE, Qt etc. and will allow you to easily build your applications on other computers.
====CMakeLists.txt====
Create a file named CMakeLists.txt in the same directory as main.cpp with this content:
<code ini n>
project (tutorial1)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial1_SRCS main.cpp)

kde4_add_executable(tutorial1 ${tutorial1_SRCS})
target_link_libraries(tutorial1 ${KDE4_KDEUI_LIBS})
</code>
The <tt>find_package()</tt> function locates the package that you ask it for (in this case KDE4) and sets some variables describing the location of the package's headers and libraries. In this case we will use the <tt>KDE4_INCLUDES</tt> variable which contains the path to the KDE4 header files.

In order to allow the compiler to find these files, we pass that variable to the <tt>include_directories()</tt> function which adds the KDE4 headers to the header search path.

Next we create a variable called <tt>tutorial1_SRCS</tt> using the <tt>set()</tt> function. In this case we simply set it to the name of our only source file.

Then we use <tt>kde4_add_executable()</tt> to create an executable called <tt>tutorial1</tt> from the source files listed in our <tt>tutorial1_SRCS</tt> variable. Finally we link our executable to the KDE4 kdeui library using <tt>target_link_libraries()</tt> and the <tt>KDE4_KDEUI_LIBS</tt> variable which was set by the <tt>find_package()</tt> function.

====Make And Run====
Again, if you set up your environment as described in [[Getting_Started/Build/KDE4|Getting Started/Build/KDE4]], you can compile this code with:
cmakekde

Or if you did not:

mkdir build && cd build
cmake ..
make

And launch it with:
./tutorial1

==Moving On==
Now you can move on to [[Development/Tutorials/Using_KXmlGuiWindow|using KXmlGuiWindow]].

[[Category:C++]]

Talk:Development/Tutorials/Saving and loading

2008-03-22T14:00:28Z

Milliams: /* Compiling failed due to 'undefined reference to vtable ...' */

Schedules/KDE4/4.1 Feature Plan

2008-02-02T22:09:56Z

Milliams: /* kdeedu */ KEduca

__NOTOC__
= Instructions =

Deadline for adding entries here for the 4.1 release is '''31 March 2008'''. 
Entries added after that date will be scheduled for the 4.2 release.

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

= kdelibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|kdeui|Goya, a framework for inserting controls into itemviews in a really easy and fast way|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureDone|kross|Add QtScript support|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|knewstuff|Support caching, and speed up the interface through use of Models/Views and goya|jeremy@scitools.com|Jeremy Whiting}}
|}

= kdepimlibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|Akonadi|Move the Akonadi development library from kdepim.|vkrause@kde.org|Volker Krause}}
|}

= kdebase-apps =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Dolphin|simplify selecting of files in the single-click mode (based on http://aseigo.blogspot.com/2006/04/icons.html)|peter.penz@gmx.at|Peter Penz}}

{{FeatureInProgress|Raptor|The KDE4-Application-Menu}}
|}

= kdebase-workspace =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdebase-runtime =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdeaccessibility =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdeadmin =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|KSystemLog|KSystemLog, a Log Viewer Tool. Move from kde-apps|nicolas.ternisien@gmail.com}}
|}

= kdeartwork =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdebindings =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdeedu =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|KBruch and KPercentage|Merge in 1 app|annma@kde.org}}
{{FeatureTodo|Step|A physics simulator, move from playground to kdeedu module|ks.vladimir@gmail.com}}
{{FeatureInProgress|KEduca|Rewrite of the classic test writing/taking application|matt@milliams.com|Matt Williams}}
|}

= kdegames =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|KGoldRunner|Startup screen|mikelima@cirulla.net}}
{{FeatureTodo|KGoldRunner|Sound support and theming|mikelima@cirulla.net}}
{{FeatureTodo|KGoldRunner|Hot new stuff support for themes and levels|mikelima@cirulla.net}}
{{FeatureInProgress|KGoldRunner|Improved theming and animation|mikelima@cirulla.net}}
{{FeatureInProgress|KBlocks|Finish display of points and level (waiting for Qt4.4 with WidgetsOnCanvas to land in qt-copy) and move to kdereview/kdegames|piacentini@kde.org}}
{{FeatureTodo|KNetWalk|Better scoring system|fela.kde@gmail.com}}
{{FeatureTodo|KNetWalk|New graphic system|fela.kde@gmail.com}}
{{FeatureTodo|KNetWalk|Add support for loading new themes|fela.kde@gmail.com}}
{{FeatureTodo|KBreakout|Finish it, and move it from playground to kdegames|fela.kde@gmail.com}}
|}

= kdegraphics =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdemultimedia =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Dragon Player|A simple Phonon-based videoplayer application|ian.monroe@gmail.com}}
|}

= kdenetwork =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|KGet|MultiSource-Downloading|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|KGet|Group-Settings|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Torrent-Support|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|Kopete|OTR Encryption support|michael_zanetti@gmx.net|Michael Zanetti}}
{{FeatureInProgress|Kopete|Bring back chat style and emoticon selection via knewstuff2|earthwings@gentoo.org|Dennis Nienhüser}}
|}

= kdepim =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|[http://decibel.kde.org Decibel]|Decibel, a framework for real time communication services. Move from playground/pim|info@basyskom.de|Tobias Hunger}}
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application| christian_weilbach@.web.de|Christian Weilbach}}
{{FeatureInProgress|KMail|HTML Signatures|yez@familieschepers.nl|Edwin Schepers}}
{{FeatureDone|KMail|Folder quicksearch|m.koller@surfeu.at|Martin Koller}}
{{FeatureDone|KMail|Favorites Folder|vkrause@kde.org|Volker Krause}}
{{FeatureDone|KonsoleKalendar|Support "file" and "localdir" resources|winter@kde.org|Allen Winter}}
{{FeatureTodo|KAlarm|Remove alarm daemon and do all scheduling in kalarm itself|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|Kontact|New Planner summary; combines Appointment+To-do+SpecialDates into 1 pretty summary|winter@kde.org|Allen Winter}}
|}

= kdesdk =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Lokalize|Move this application (formerly known as Kaider) from extragear|shafff@ukr.net}}
{{FeatureTodo|Cervisia|A file view based on KDirModel|christian.loose@hamburg.de|Christian Loose}}
{{FeatureInProgress|Cervisia|New context menu entry "Add to Ignore List"|christian.loose@hamburg.de|Christian Loose}}
|}

= kdetoys =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdeutils =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|Okteta|bytelevel editor (successor to KHexEdit). Move from playground/utils.|kossebau@kde.org|Friedrich W. H. Kossebau}}
|}

= kdevelop =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdevplatform =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdewebdev =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

Projects/Games

2008-01-31T11:15:20Z

Milliams: /* IRC */ Update meeting time

{{Template:I18n/Language Navigation Bar|Projects/Games}}
Intro to do

== The Game Categories ==
*[[/Arcade Games|Arcade games]]
*[[/Board Games|Board Games]]
*[[/Tactic and Strategy|Tactic and Strategy]]
*[[/Card Games|Card games]]

===See also===
* [http://doc.trolltech.com/4.2/qsvgrenderer.html QSvgRenderer Class Reference]
* [http://developer.kde.org/documentation/library/cvs-api/kdelibs-apidocs/kdecore/html/classKSvgRenderer.html KSvgRenderer Class Reference]
* [http://websvn.kde.org/trunk/KDE/kdegames/katomic/ KAtomic KDE4 code in websvn]
* [[Schedules/KDE4/4.0 Release Schedule]]

==Development==

* [[/Maintainers| Game's maintainers]]
* [[/UI and usability|UI and usability]]
* [[/libkdegames Usage|libkdegames Usage]]
* [[/Ideas| KDEGames Ideas and Proposals]]

==Status==

* [[/Status KDE 4.0|Status KDE 4.0]]
** [[/Documentation_progress|Documentation progress]]
** [[/Icons_ToDo|Icons_ToDo]]
* older pages:
** [[/Status_Ready|Ready]]
** [[/Status_Should_be_Ready|Should be ready]]
** [[/Status_Playground|kdegames playground (kdegame's candidate or unready) ]]
** [[/Status|old status page]]

==Meeting==

===IRC===

We are doing meeting on [irc://irc.kde.org/#kdegames IRC] every month to talk about the games development.

[[/IRC Meeting|Next Meeting : 2 February 12:00UTC]]

Talk:Development/Tutorials/First program

2008-01-25T19:47:21Z

Milliams: /* Build */

Adding authors to wiki pages seems counterintuitive to me. The wiki is editable by everybody. Why does it matter who the author of a tutorial is? IMHO the only thing that matters is that the tutorial is kept up to date. --[[User:Mattr|Mattr]] 03:31, 4 January 2007 (CET)

: I agree with Matt. I usually add a ''Initial Author:'' at the bottom for pages from the old developer wiki code, because they wrote it with often no explicit copyright information. See also [[Talk:Development/Architecture|this page]] --[[User:Dhaumann|Dhaumann]] 17:36, 4 January 2007 (CET)

== ‘ki18n’ was not declared in this scope ==

I don't know if this is the place to post this, but I tried to follow this tutorial and get an "error: ‘ki18n’ was not declared in this scope", when trying to compile using the big command gcc main.cpp ...

:Well I change a little the code so it now compiles under KDE4, it seems that the constructor of KAboutDate was changed...

== Build ==

Does the g++ command work for you as described?
I needed to add -lQtXml, lQtSvg and lQtNetwork.

: I'm getting a 'huge' string of error messages in the underlying include/ files, things like
<code>
include/KDE/../kmessagebox.h:1128: error: expected constructor, destructor, or type conversion before ‘(’ token
</code>
but hundreds, possibly thousands of errors apparently affecting nearly every header.
::I personally haven't tried the g++ method, that was added by someone else. Does linking against those libraries fix the errors? Does it work for you with the cmake method? --[[User:Milliams|milliams]] 20:47, 25 January 2008 (CET)

Development/Tutorials/Kate/KTextEditor Plugins

2008-01-18T10:48:38Z

Milliams: /* The resource contents file */ XML highlighting

{{TutorialBrowser|

series=Kate Plugin Tutorial|

name=Creating your first Kate Plugin|

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [http://www.trolltech.com/products/qt/ Qt], [[Getting_Started/Build/KDE4|KDE4 development environment]]|

next=[[Development/Tutorials/Kate/KTextEditor_Plugins_Advanced|Add a configuration dialog for it]]|

reading=[[Development/Tutorials/CMake|CMake]], [http://websvn.kde.org/trunk/KDE/kdelibs/kate/plugins/timedate The actual plugin code]
}}
==Abstract==
We are going to create a dummy plugin for Kate in this tutorial. Our plugin will be able to insert current Date & Time. For now, our plugin will add on the cursor position on the active document the next information:

* MM-DD-YYYY HH:MM (something like "08-22-2007 23:45")

On the next chapter we will learn how to customize this output string creating a configuration dialog for this plugin.

== The Code ==
=== The .desktop file ===
Every plugin needs a .desktop file that describes it.

'''ktexteditor_timedate.desktop'''
<code ini>
[Desktop Entry]
Encoding=UTF-8
X-KDE-Library=ktexteditor_timedate
X-KDE-PluginInfo-Author=Konqui the Dragon
X-KDE-PluginInfo-Email=konqui@kde.org
X-KDE-PluginInfo-Name=ktexteditortimedate
X-KDE-PluginInfo-Version=0.1
X-KDE-PluginInfo-Website=http://kate.kde.org
X-KDE-PluginInfo-Category=Editor
X-KDE-PluginInfo-Depends=
X-KDE-PluginInfo-License=GPL
X-KDE-PluginInfo-EnabledByDefault=false
X-KDE-ParentApp=kate
X-KDE-Version=4.0
ServiceTypes=KTextEditor/Plugin
Type=Service
Icon=korganizer
Name=Time & Date
Comment=Insert current Time & Date
</code>

There are important parts on this file:

* '''X-KDE-Library''': will define the library that provides this plugin. It is _really_ important that this variable matches exactly the same with the actual name of the library being built. You will understand this better when getting to the finish of this tutorial on the part "Building it all, the CMakeLists.txt".
* '''X-KDE-PluginInfo-Name''': no special characters. The name of the plugin.
* '''X-KDE-PluginInfo-Category''': important when the plugin selector loads it. Usually here you want always to put "Editor".
* '''X-KDE-PluginInfo-Depends''': if your plugin depends on another, write here the corresponding X-KDE-PluginInfo-Name that is needed to be loaded too when loading this plugin.
* '''X-KDE-PluginInfo-EnabledByDefault''': whether the plugin is enabled by default. Applied when clicking on "Defaults" button on the plugin selector.
* '''X-KDE-ParentApp''': you want here always "kate".
* '''X-KDE-Version''': KWrite/Kate does a check for only loading 4 series plugins.
* '''ServiceTypes''': you will always need here "KTextEditor/Plugin".
* '''Type''': in order to load it properly this is needed as "Service".

=== The resource contents file ===
This file is the one that will let our plugin merge with the Kate environment (toolbars and/or menubars). In this case when our plugin is loaded this file tells the KDE XML classes that it will add a separator, and that there is an action named "tools_insert_timedate". We will need to interact with this action later.

'''timedateui.rc'''
<code xml>
<!DOCTYPE kpartgui>
<kpartplugin name="ktexteditor_timedate" library="ktexteditor_timedate" version="2">
<MenuBar>
<Menu name="tools"><Text>&Tools</Text>
<separator group="tools_operations" />
<Action name="tools_insert_timedate" group="tools_operations"/>
</Menu>
</MenuBar>
</kpartplugin>
</code>

=== The header file ===
'''timedate.h'''
<code cppqt>
// Avoid multiple header inclusion
#ifndef TIMEDATE_H
#define TIMEDATE_H

// Include the basics
#include <ktexteditor/plugin.h>
#include <ktexteditor/view.h>
#include <kxmlguiclient.h>
#include <klocalizedstring.h>

#include <QtCore/QEvent>
#include <QtCore/QObject>
#include <QtCore/QList>

/**
* This is the plugin class. There will be only one instance of this class.
* We always want to inherit KTextEditor::Plugin here.
*/
class TimeDatePlugin
: public KTextEditor::Plugin
{
public:
// Constructor
explicit TimeDatePlugin(QObject *parent,
const QVariantList &args);
// Destructor
virtual ~TimeDatePlugin();

// Overriden methods
// This method is called when a plugin has to be added to a view. As there
// is only one instance of this plugin, but it is possible for plugins to
// behave in different ways in different opened views where it is loaded, in
// Kate plugins are added to views. For that reason we have the plugin itself
// (this class) and then the plugin view class.
// In this methods we have to create/remove TimeDatePluginView classes.
void addView (KTextEditor::View *view);
void removeView (KTextEditor::View *view);

void readConfig();
void writeConfig();

private:
QList<class TimeDatePluginView*> m_views;
};

/**
* This is the plugin view class. There can be as much instances as views exist.
*/
class TimeDatePluginView
: public QObject, public KXMLGUIClient
{
Q_OBJECT

public:
explicit TimeDatePluginView(KTextEditor::View *view = 0);
~TimeDatePluginView();

private Q_SLOTS:
void slotInsertTimeDate();

private:
KTextEditor::View *m_view;
};

#endif // TIMEDATE_H
</code>

=== The source file ===
'''timedate.cpp'''
<code cppqt>
// Own includes
#include "timedate.h"

// Include the basics
#include <ktexteditor/document.h>

#include <kpluginfactory.h>
#include <kpluginloader.h>
#include <klocale.h>
#include <kaction.h>
#include <kactioncollection.h>
#include <kdatetime.h>

// This macro defines a KPluginFactory subclass named TimeDatePluginFactory. The second
// argument to the macro is code that is inserted into the constructor of the class.
// I our case all we need to do is register one plugin. If you want to have more
// than one plugin in the same library then you can register multiple plugin classes
// here. The registerPlugin function takes an optional QString parameter which is a
// keyword to uniquely identify the plugin then (it maps to X-KDE-PluginKeyword in the
// .desktop file).
K_PLUGIN_FACTORY(TimeDatePluginFactory,
registerPlugin<TimeDatePlugin>();
)

// With the next macro call, the library exports version information about the
// Qt and KDE libraries being used and (most important) the entry symbol to get at
// the factory we defined above.
// The argument this macro takes is the constructor call of the above factory which
// provides two constructors. One which takes a KAboutData* and another one
// that takes two (optional) const char* parameters (Same as for KComponentData
// constructors).
// We put there the X-KDE-LibraryName.
// Is important to provide as last parameter "ktexteditor_plugins".
K_EXPORT_PLUGIN(TimeDatePluginFactory("ktexteditor_timedate", "ktexteditor_plugins")

// Constructor
TimeDatePlugin::TimeDatePlugin(QObject *parent, const QVariantList &args)
: KTextEditor::Plugin(parent)
{
// Avoid warning on compile time because of unused argument
Q_UNUSED(args);
}

// Destructor
TimeDatePlugin::~TimeDatePlugin()
{
}

// Create the plugin view class and add it to the views list
void TimeDatePlugin::addView(KTextEditor::View *view)
{
TimeDatePluginView *nview = new TimeDatePluginView(view);
m_views.append(nview);
}

// Find the view where we want to remove the plugin from, and remove it.
// Do not forget to free the memory.
void TimeDatePlugin::removeView(KTextEditor::View *view)
{
for (int z = 0; z < m_views.size(); z++)
{
if (m_views.at(z)->parentClient() == view)
{
TimeDatePluginView *nview = m_views.at(z);
m_views.removeAll(nview);
delete nview;
}
}
}

// We do nothing on this methods since our plugin is not configurable yet
void TimeDatePlugin::readConfig()
{
}

void TimeDatePlugin::writeConfig()
{
}

// Plugin view class
TimeDatePluginView::TimeDatePluginView(KTextEditor::View *view)
: QObject(view)
, KXMLGUIClient(view)
, m_view(view)
{
setComponentData(TimeDatePluginFactory::componentData());

KAction *action = new KAction(i18n("Insert Time && Date"), this);
// Here we need as first parameter the same we declared at the resource
// contents file (timedateui.rc). We named the action "tools_insert_timedate".
// Here is where we connect it to an actual KDE action.
actionCollection()->addAction("tools_insert_timedate", action);
action->setShortcut(Qt::CTRL + Qt::Key_D);
// As usual, we connect the signal triggered() to a slot here. When the menu
// element is clicked, we go to the slot slotInsertTimeDate().
connect(action, SIGNAL(triggered()), this, SLOT(slotInsertTimeDate()));

// This is always needed, tell the KDE XML GUI client that we are using
// that file for reading actions from.
setXMLFile("timedateui.rc");
}

// Destructor
TimeDatePluginView::~TimeDatePluginView()
{
}

// The slot that will be called when the menu element "Insert Time & Date" is
// clicked.
void TimeDatePluginView::slotInsertTimeDate()
{
QString localizedTimeDate = i18nc("This is a localized string for default time & date printing on kate document."
"%e means day in XX format."
"%m means month in XX format."
"%Y means year in XXXX format."
"%H means hours in XX format."
"%M means minutes in XX format."
"Please, if in your language time or date is written in a different order, change it here",
"%m-%e-%Y %H:%M");

// We create a KDateTime object with the current time & date.
KDateTime dt(QDateTime::currentDateTime());
// We insert the information in the document at the current cursor position
// with the default string declared on the header.
m_view->document()->insertText(m_view->cursorPosition(), dt.toString(localizedTimeDate));
}

// We need to include the moc file since we have declared slots and we are using
// the Q_OBJECT macro on the TimeDatePluginView class.
#include "timedate.moc"
</code>

=== Building it all, the CMakeLists.txt ===
Finally, to put everything together you need to build everything, to tell cmake what needs to go where there is the CMakeLists.txt file.

For more details on CMake please read [[Development/Tutorials/CMake]]

<code bash>
# We are calling our plugin "ktexteditor_timedate", and it contains only
# one source file: timedate.cpp.
kde4_add_plugin(ktexteditor_timedate timedate.cpp)

# We need to link our plugin against kdecore libs, as well as ktexteditor
target_link_libraries(ktexteditor_timedate ${KDE4_KDECORE_LIBS} ktexteditor)

# Well, we want to install our plugin on the plugin directory
install(TARGETS ktexteditor_timedate DESTINATION ${PLUGIN_INSTALL_DIR})

# We also want to install the resource contents file on the data directory, at
# the subdirectory of our plugin name, so it does not mix up with other resource
# contents files.
install(FILES timedateui.rc DESTINATION ${DATA_INSTALL_DIR}/ktexteditor_timedate)

# We want to install the desktop file that describes our plugin too. It will go
# on the services directory.
install(FILES ktexteditor_timedate.desktop DESTINATION ${SERVICES_INSTALL_DIR})
</code>

=== The next part ===
Now you are ready for adding to this plugin a configuration dialog that lets the user customize the way the string is printed out on the screen.

[[Development/Tutorials/Kate/KTextEditor_Plugins_Advanced|Take me to the next part of this tutorial !!]]

Development/Tutorials/Kate/KTextEditor Plugins Advanced

2008-01-18T10:48:34Z

Milliams: /* The resource contents file */ XML highlighting

{{TutorialBrowser|

series=Kate Plugin Tutorial (2nd part)|

name=Creating your first Kate Plugin with configuration dialog|

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [http://www.trolltech.com/products/qt/ Qt], [[Getting_Started/Build/KDE4|KDE4 development environment]]|

reading=[[Development/Tutorials/CMake|CMake]], [http://websvn.kde.org/trunk/KDE/kdelibs/kate/plugins/timedate The actual plugin code]
}}

==Abstract==
The plugin that we developed on the previous part of this tutorial was nice, but probably not enough. We also need it to be configurable, because the user might want to only add to his/her document the date or the time, not both. We are going to create a configuration dialog for the plugin, and make the output form of our time & date configurable by the user.

== The Code ==
=== The .desktop files ===
Every plugin needs a .desktop file that describes it. Same for each configuration page/widget. As we only need a page/widget for this plugin, we will only have two desktop files: one for the plugin itself, and another one for configuration the page/widget.

'''ktexteditor_timedate.desktop'''
<code ini>
[Desktop Entry]
Encoding=UTF-8
X-KDE-Library=ktexteditor_timedate
X-KDE-PluginKeyword=ktexteditor_timedate
X-KDE-PluginInfo-Author=Konqui the Dragon
X-KDE-PluginInfo-Email=konqui@kde.org
X-KDE-PluginInfo-Name=ktexteditortimedate
X-KDE-PluginInfo-Version=0.1
X-KDE-PluginInfo-Website=http://kate.kde.org
X-KDE-PluginInfo-Category=Editor
X-KDE-PluginInfo-Depends=
X-KDE-PluginInfo-License=GPL
X-KDE-PluginInfo-EnabledByDefault=false
X-KDE-ParentApp=kate
X-KDE-Version=4.0
ServiceTypes=KTextEditor/Plugin
Type=Service
Icon=korganizer
Name=Time & Date
Comment=Insert current Time & Date
</code>

'''ktexteditor_timedate_config.desktop'''
<code ini>
[Desktop Entry]
Type=Service
X-KDE-ServiceTypes=KCModule
X-KDE-Library=ktexteditor_timedate
X-KDE-PluginKeyword=ktexteditor_timedate_config
X-KDE-FactoryName=ktexteditor_timedate_config
X-KDE-ParentComponents=ktexteditortimedate
Name=Format of Time & Date insertion
</code>

* '''X-KDE-ServiceTypes''': configuration widgets are always KCModule's.
* '''X-KDE-Library''': you need to specify which library provides this configuration dialog. In this case we are shipping on the same library "ktexteditor_timedate.so" both the plugin itself and its configuration dialog.
* '''X-KDE-PluginKeyword''': since we have two entry points on the library at this time: one for the plugin and another one for the configuration dialog we need to specify which keyword has each one. As you can see I also added this entry to the ktexteditor_timedate.desktop file. Of course they have to be different if we want to see it working.

=== The resource contents file ===
This file is the one that will let our plugin merge with the Kate environment (toolbars and/or menubars). In this case when our plugin is loaded this file tells the KDE XML classes that it will add a separator, and that there is an action named "tools_insert_timedate". We will need to interact with this action later.

'''timedateui.rc'''
<code xml>
<!DOCTYPE kpartgui>
<kpartplugin name="ktexteditor_timedate" library="ktexteditor_timedate" version="2">
<MenuBar>
<Menu name="tools"><Text>&Tools</Text>
<separator group="tools_operations" />
<Action name="tools_insert_timedate" group="tools_operations"/>
</Menu>
</MenuBar>
</kpartplugin>
</code>

=== The header file of the plugin ===
'''timedate.h'''
<code cppqt>
#ifndef TIMEDATE_H
#define TIMEDATE_H

#include <ktexteditor/plugin.h>
#include <ktexteditor/view.h>
#include <kxmlguiclient.h>
#include <klocalizedstring.h>
#include <kpluginfactory.h>

#include <QtCore/QEvent>
#include <QtCore/QObject>
#include <QtCore/QList>
#include <QtCore/QVariantList>

static QString localizedTimeDate = QString();

class TimeDatePlugin
: public KTextEditor::Plugin
{
public:
explicit TimeDatePlugin(QObject *parent = 0,
const QVariantList &args = QVariantList());
virtual ~TimeDatePlugin();

static TimeDatePlugin *self() { return plugin; }

void addView (KTextEditor::View *view);
void removeView (KTextEditor::View *view);

void readConfig();
void writeConfig();

virtual void readConfig (KConfig *) {}
virtual void writeConfig (KConfig *) {}

void setFormat(const QString &format);
QString format() const;

private:
static TimeDatePlugin *plugin;
QList<class TimeDatePluginView*> m_views;
QString m_string;
};

class TimeDatePluginView
: public QObject, public KXMLGUIClient
{
Q_OBJECT

public:
explicit TimeDatePluginView(const QString &string,
KTextEditor::View *view = 0);
~TimeDatePluginView();

void setFormat(const QString &format);
QString format() const;

private Q_SLOTS:
void slotInsertTimeDate();

private:
KTextEditor::View *m_view;
QString m_string;
};

K_PLUGIN_FACTORY_DECLARATION(TimeDatePluginFactory)

#endif // TIMEDATE_H
</code>

=== The source file of the plugin ===
'''timedate.cpp'''
<code cppqt>
#include "timedate.h"
#include "timedate_config.h"

#include <ktexteditor/document.h>

#include <kpluginfactory.h>
#include <kpluginloader.h>
#include <klocale.h>
#include <kaction.h>
#include <kactioncollection.h>
#include <kdatetime.h>
#include <kconfiggroup.h>

TimeDatePlugin *TimeDatePlugin::plugin = 0;

K_PLUGIN_FACTORY_DEFINITION(TimeDatePluginFactory,
registerPlugin<TimeDatePlugin>("ktexteditor_timedate");
registerPlugin<TimeDateConfig>("ktexteditor_timedate_config");
)
K_EXPORT_PLUGIN(TimeDatePluginFactory("ktexteditor_timedate", "ktexteditor_plugins"))

TimeDatePlugin::TimeDatePlugin(QObject *parent, const QVariantList &args)
: KTextEditor::Plugin(parent)
{
Q_UNUSED(args);

if (localizedTimeDate.isNull())
{
localizedTimeDate = i18nc("This is a localized string for default time & date printing on kate document."
"%d means day in XX format."
"%m means month in XX format."
"%Y means year in XXXX format."
"%H means hours in XX format."
"%M means minutes in XX format."
"Please, if in your language time or date is written in a different order, change it here",
"%d-%m-%Y %H:%M");
}

plugin = this;
readConfig();
}

TimeDatePlugin::~TimeDatePlugin()
{
plugin = 0;
}

void TimeDatePlugin::addView(KTextEditor::View *view)
{
TimeDatePluginView *nview = new TimeDatePluginView(m_string, view);
m_views.append(nview);
}

void TimeDatePlugin::removeView(KTextEditor::View *view)
{
for (int z = 0; z < m_views.size(); z++)
{
if (m_views.at(z)->parentClient() == view)
{
TimeDatePluginView *nview = m_views.at(z);
m_views.removeAll(nview);
delete nview;
}
}
}

void TimeDatePlugin::readConfig()
{
KConfigGroup cg(KGlobal::config(), "TimeDate Plugin");
m_string = cg.readEntry("string", localizedTimeDate);
}

void TimeDatePlugin::writeConfig()
{
KConfigGroup cg(KGlobal::config(), "TimeDate Plugin" );
cg.writeEntry("string", m_string );
}

void TimeDatePlugin::setFormat(const QString &format)
{
m_string = format;

// If the property has been set for the plugin in general, let's set that
// property to that value on all views where the plugin has been loaded.
foreach (TimeDatePluginView *pluginView, m_views)
{
pluginView->setFormat(format);
}
}

QString TimeDatePlugin::format() const
{
return m_string;
}

TimeDatePluginView::TimeDatePluginView(const QString &string,
KTextEditor::View *view)
: QObject(view)
, KXMLGUIClient(view)
, m_view(view)
, m_string(string)
{
setComponentData(TimeDatePluginFactory::componentData());

KAction *action = new KAction(i18n("Insert Time && Date"), this);
actionCollection()->addAction("tools_insert_timedate", action);
action->setShortcut(Qt::CTRL + Qt::Key_D);
connect(action, SIGNAL(triggered()), this, SLOT(slotInsertTimeDate()));

setXMLFile("timedateui.rc");
}

TimeDatePluginView::~TimeDatePluginView()
{
}

void TimeDatePluginView::setFormat(const QString &format)
{
m_string = format;
}

QString TimeDatePluginView::format() const
{
return m_string;
}

void TimeDatePluginView::slotInsertTimeDate()
{
KDateTime dt(QDateTime::currentDateTime());
m_view->document()->insertText(m_view->cursorPosition(), dt.toString(m_string));
}

#include "timedate.moc"
</code>

=== The header file of the configuration dialog ===
'''timedate_config.h'''
<code cppqt>
#ifndef TIMEDATE_CONFIG_H
#define TIMEDATE_CONFIG_H

#include <kcmodule.h>

class KLineEdit;

class TimeDateConfig
: public KCModule
{
Q_OBJECT

public:
explicit TimeDateConfig(QWidget *parent = 0, const QVariantList &args = QVariantList());
virtual ~TimeDateConfig();

virtual void save();
virtual void load();
virtual void defaults();

private Q_SLOTS:
void slotChanged();

private:
KLineEdit *format;
};

#endif // TIMEDATE_CONFIG_H
</code>

=== The source file of the configuration dialog ===
'''timedate_config.cpp'''
<code cppqt>
#include "timedate_config.h"
#include "timedate.h"

#include <QtGui/QLabel>
#include <QtGui/QBoxLayout>

#include <klocale.h>
#include <kpluginfactory.h>
#include <kpluginloader.h>
#include <klineedit.h>
#include <kconfiggroup.h>

TimeDateConfig::TimeDateConfig(QWidget *parent, const QVariantList &args)
: KCModule(TimeDatePluginFactory::componentData(), parent, args)
{
QVBoxLayout *layout = new QVBoxLayout(this);

QLabel *info = new QLabel(i18n(
"%y\t2-digit year excluding century (00 - 99)\n"
"%Y\tfull year number\n"
"%:m\tmonth number, without leading zero (1 - 12)\n"
"%m\tmonth number, 2 digits (01 - 12)\n"
"%b\tabbreviated month name\n"
"%B\tfull month name\n"
"%e\tday of the month (1 - 31)\n"
"%d\tday of the month, 2 digits (01 - 31)\n"
"%a\tabbreviated weekday name\n"
"%A\tfull weekday name\n"
"\n"
"%H\thour in the 24 hour clock, 2 digits (00 - 23)\n"
"%k\thour in the 24 hour clock, without leading zero (0 - 23)\n"
"%I\thour in the 12 hour clock, 2 digits (01 - 12)\n"
"%l\thour in the 12 hour clock, without leading zero (1 - 12)\n"
"%M\tminute, 2 digits (00 - 59)\n"
"%S\tseconds (00 - 59)\n"
"%P\t\"am\" or \"pm\"\n"
"%p\t\"AM\" or \"PM\"\n"));

// It is possible that the plugin has not been loaded yet, and the
// configuration dialog has been asked to be shown. In that case, it is our
// turn to set the static string to the correct value.
if (localizedTimeDate.isNull())
{
localizedTimeDate = i18nc("This is a localized string for default time & date printing on kate document."
"%d means day in XX format."
"%m means month in XX format."
"%Y means year in XXXX format."
"%H means hours in XX format."
"%M means minutes in XX format."
"Please, if in your language time or date is written in a different order, change it here",
"%d-%m-%Y %H:%M");
}

QHBoxLayout *hlayout = new QHBoxLayout(this);
QLabel *lformat = new QLabel(i18n("Format"));
format = new KLineEdit(this);
hlayout->addWidget(lformat);
hlayout->addWidget(format);

layout->addWidget(info);
layout->addLayout(hlayout);

setLayout(layout);

load();

QObject::connect(format, SIGNAL(textChanged(QString)), this, SLOT(slotChanged()));
}

TimeDateConfig::~TimeDateConfig()
{
}

void TimeDateConfig::save()
{
if (TimeDatePlugin::self())
{
TimeDatePlugin::self()->setFormat(format->text());
TimeDatePlugin::self()->writeConfig();
}
else
{
KConfigGroup cg(KGlobal::config(), "TimeDate Plugin");
cg.writeEntry("string", format->text());
}

emit changed(false);
}

void TimeDateConfig::load()
{
if (TimeDatePlugin::self())
{
TimeDatePlugin::self()->readConfig();
format->setText(TimeDatePlugin::self()->format());
}
else
{
KConfigGroup cg(KGlobal::config(), "TimeDate Plugin" );
format->setText(cg.readEntry("string", localizedTimeDate));
}

emit changed(false);
}

void TimeDateConfig::defaults()
{
format->setText(localizedTimeDate);

emit changed(true);
}

void TimeDateConfig::slotChanged()
{
emit changed(true);
}

#include "timedate_config.moc"
</code>

=== Building it all, the CMakeLists.txt ===
Finally, to put everything together you need to build everything, to tell cmake what needs to go where there is the CMakeLists.txt file.

For more details on CMake please read [[Development/Tutorials/CMake]]

<code bash>
set(ktexteditor_timedate_PART_SRCS timedate.cpp timedate_config.cpp )

kde4_add_plugin(ktexteditor_timedate ${ktexteditor_timedate_PART_SRCS} )

target_link_libraries(ktexteditor_timedate ${KDE4_KDECORE_LIBS} ktexteditor )

install(TARGETS ktexteditor_timedate DESTINATION ${PLUGIN_INSTALL_DIR} )

install(FILES timedateui.rc DESTINATION ${DATA_INSTALL_DIR}/ktexteditor_timedate )

install(FILES ktexteditor_timedate.desktop
ktexteditor_timedate_config.desktop DESTINATION ${SERVICES_INSTALL_DIR} )
</code>

Projects/Games

2008-01-16T16:13:09Z

Milliams: /* IRC */

Development/Tutorials

2008-01-15T18:35:41Z

Milliams: /* Basics */ Page is deleted

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

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

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

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

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

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

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

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

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

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

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

== Testing And Debugging ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Documentation ==

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

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

== Application Automation and Scripting ==

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

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

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

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

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

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

=== KOffice ===
; [[Development/Tutorials/KOffice Overview|KOffice Overview]]
:''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 Scripting]]
:''This tutorial shows how to script KWord with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/KSpread Scripting|KSpread Scripting]]
:''This tutorial shows how to script KSpread with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/Krita Scripting|Krita Scripting]]
:''This tutorial shows how to script Krita with Python, Ruby or JavaScript using Kross.''

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

== Search and Metadata ==

=== Strigi ===

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

=== Nepomuk ===

; [[Development/Tutorials/Metadata/KMetaData first steps|Nepomuk first steps]]
:''Nepomuk is the KDE library which provides easy access to metadata in the [http://nepomuk-kde.semanticdesktop.org Nepomuk-KDE] system. Learn how to make your application create and read metadata using the Nepomuk system.''

== Hardware Awareness (Solid) ==

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

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

== Multimedia (Phonon) ==

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

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

== Plasma ==

;[[Development/Tutorials/Plasma/GettingStarted|Getting Started With Plasmoids]]
:''Creating your first Plasma widget, or Plasmoid, in C++ with an SVG background, an icon and some text''

;[[Development/Tutorials/Plasma/DataEngines|Writing A DataEngine]]
:''DataEngines provide a standardized interface to various data sources for visualizations to use. Learn what a DataEngine is and how to write one of your own.''

;[[Development/Tutorials/Plasma/UsingDataEngines|Using DataEngines in Plasmoids]]
:''With a DataEngine, it is possible to retrieve data for display in a simple and standard way. This tutorial covers the topic of how to use DataEngines for this purpose in Plasmoids.''

;[[Development/Tutorials/Plasma/AbstractRunner|Creating Runners]]
:''Runners are plugins that provide action-based search functionality in the Plasma workspace "run command" dialog. These plugins can be used by any application that links again libplasma.''

== Kate / Kwrite ==

;[[Development/Tutorials/Kate/KTextEditor Plugins|Getting Started With KTextEditor Plugins]]
:''Creating your first KTextEditor plugin''

==Printing==

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

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

== Get Hot New Stuff ==
; [[Development/Tutorials/Introduction to Get Hot New Stuff|Introduction to Get Hot New Stuff]]
:''An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.''

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

== Rapid Application Development ==

=== Python ===

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

=== Ruby ===

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

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

=== Shell ===

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

== Other tutorials ==

=== Using the KDE Games Library ===
;[[Development/Tutorials/Games/KStandardGameAction| KStandardGameAction]]
:''Using libkdegames to make your game fit the kdegames standard''
;[[Development/Tutorials/Games/Highscores| Highscores]]
:''Implementing a simple highscore table into your game''
;[[Development/Tutorials/Games/Theme Selector| Theme Selector]]
:''Using the libkdegames theme selection dialog''

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

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

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

== KDE2 and KDE3 Materials ==

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

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

[[Category:KDE4]]

User talk:Danimo

2007-12-30T16:13:04Z

Milliams: /* Assistance needed for new contributor to Techbase */

Development/Tutorials/Using KActions

2007-12-27T22:07:49Z

Milliams: /* KStandardAction */ Don't use classmapper

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=How To Use KActions and XMLGUI|

pre=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]], Basic XML knowledge|

next=[[Development/Tutorials/Saving_and_loading|Tutorial 4 - Saving and loading]]|

reading=None
}}

==Abstract==
This tutorial introduces the concept of actions. Actions are a unified way of supplying the user with ways to interact with your program.

For example, if we wanted to let the user of [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 ]] clear the text box by clicking a button in the toolbar, from an option in the File menu or through a keyboard shortcut, it could all be done with one {{class|KAction}}.

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

==KAction==
A {{class|KAction}} is an object which contains all the information about the icon and shortcuts that is associated with a certain action. The action is then connected to a [http://doc.trolltech.com/latest/signalsandslots.html slot] which carries out the work of your action.

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial3", "tutorial3",
ki18n("Tutorial 3"), "1.0",
ki18n("A simple text area using KAction etc."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
This time, very little has changed in <tt>main.cpp</tt>, only the KAboutData constructor has been updated to show that we are now on tutorial 3.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
void setupActions();
};

#endif
</code>
Only a function <tt>void setupActions()</tt> has been added which will do all the work setting up the KActions.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent)
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

setupGUI();
}
</code>

==Explanation==
This builds upon the KXmlGuiWindow code from [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2]]. Most of the changes are to <tt>mainwindow.cpp</tt>, an important structural change being that the constructor for MainWindow now calls <tt>setupActions()</tt> instead of <tt>setupGUI()</tt>. <tt>setupActions()</tt> is where the new KAction code goes before finally calling <tt>setupGUI()</tt> itself.

===Creating the KAction object===
The KAction is built up in a number of steps. The first is including the <tt>KAction</tt> library and then creating the KAction:
<code cppqt>
#include <KAction>
...
KAction* clearAction = new KAction(this);
</code>
This creates a new KAction called <tt>clearAction</tt>.

===Setting KAction Properties===
====Text====
Now we have our KAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and under the <tt>KAction</tt>'s icon in the toolbar.
<code cppqt>clearAction->setText(i18n("Clear"));</code>
Note that the text is passed through the i18n() function; this is necessary for the UI to be translatable (more information on this can be found in the [[Development/Tutorials/Localization/i18n|i18n tutorial]]).

====Icon====
If the action is going to be displayed in a toolbar, it's nice to have an icon depicting the action. The following code sets the icon to the standard KDE <tt>document-new</tt> icon through the use of the <tt>setIcon()</tt> function:
<code cppqt>clearAction->setIcon(KIcon("document-new"));</code>

====Keyboard Shortcut====
Setting a keyboard shortcut to perform our action is equally simple:
<code cppqt>clearAction->setShortcut(Qt::CTRL + Qt::Key_W);</code>
This associates Ctrl+W with the KAction.

===Adding to the Collection===
In order for the action to be accessed by the XMLGUI framework (explained in depth later) it must be added to the application's ''action collection''. The action collection is accessed via the <tt>actionCollection()</tt> function like this:
<code cppqt>
actionCollection()->addAction("clear", clearAction);
</code>
Here, the <tt>clearAction</tt> KAction is added to the collection and given a name of ''clear''. This name (''clear'') is used by the XMLGUI framework to refer to the action.

====Connecting the action====
Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the <tt>clear()</tt> action belonging to a KTextEdit (which, unsurprisingly, clears the KTextEdit)
<code cppqt>
connect( clearAction, SIGNAL( triggered(bool) ),
textArea, SLOT( clear() ) );
</code>
This is the same as it would be done in Qt with a {{qt|QAction}}.

===KStandardAction===

For actions which would likely appear in almost every KDE application such as 'quit', 'save', and 'load' there are pre-created convenience KActions, accessed through [http://api.kde.org/4.0-api/kdelibs-apidocs/kdeui/html/namespaceKStandardAction.html KStandardAction].

They are very simple to use. Once the library has been included (<tt>#include <KStandardAction></tt>), simply supply it with what you want the function to do and which KActionCollection to add it to. For example:
<code cppqt>KStandardAction::quit(kapp, SLOT(quit()), actionCollection());</code>
This creates a KAction with the correct icon, text and shortcut and even adds it to the File menu.

==Adding the action to menus and toolbars==
At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.

{{note|In a later version of KDE4, XMLGUI, may be replaced with a new framework called liveui. For now, XMLGUI, is the only and correct way to set up the UI.}}

==XMLGUI==

The <tt>setupGUI()</tt> function in {{class|KXmlGuiWindow}} depends on the XMLGUI system to construct the GUI, which XMLGUI does by parsing an XML file description of the interface.

The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.

==''appname''ui.rc File==

Since the description of the UI is defined with XML, the layout must follow strict rules. This tutorial will not go into great depth on this topic, but for more information, see the [[Development/Architecture/KDE4/XMLGUI_Technology|detailed XMLGUI page]].

===tutorial3ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial3" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>

The <tt><Toolbar></tt> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name ''mainToolBar'' and its user visible name set to ''Main Toolbar'' using the <tt><text></tt> tag. The clear action is added to the toolbar using the <tt><Action></tt> tag, the name parameter in this tag being the string that was passed to the KActionCollection with <tt>addAction()</tt> in <tt>mainwindow.cpp</tt>.

Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the ''File'' menu of the <tt>MenuBar</tt> the same way it was added to the toolbar.

Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update.

==CMake==
Finally, the <tt>tutorial3ui.rc</tt> needs to go somewhere where KDE can find it (can't just leave it in the source directory!). '''This means the project needs to be installed somewhere.'''
===CMakeLists.txt===
<code ini n>
project(tutorial3)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial3_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial3 ${tutorial3_SRCS})

target_link_libraries(tutorial3 ${KDE4_KDEUI_LIBS})

install(TARGETS tutorial3 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial3ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial3)
</code>

This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.

===Make, Install And Run===
If you don't have write access to where your KDE4 installation directory, you can install it to a folder in your home directory.

To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:
mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial3
which will create a KDE-like directory structure in your user's home directory directory and will install the executable to {{path|$HOME/bin/tutorial3}}.

==Moving On==
Now you can move on to [[Development/Tutorials/Saving_and_loading|saving and loading]].

[[Category:C++]]

Talk:Development/Tutorials/Using KActions

2007-12-27T22:07:30Z

Milliams: /* Broken tutorial (kdelibs have changed) */

2007/3/18:
The .ui file isn't working with trunk from svn

I fixed it by using this instead:

----

<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<kpartgui version="2" name="tutorial3">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<text>&File</text>
<Action name="clear" />
</Menu>
</MenuBar>
</kpartgui>

---

I'm not shure why.
Should this be added to the tutorial?

--
Jonarne

----

Let's wait, to my experience this is repaired quickly --[[User:Tstaerk|Tstaerk]] 21:12, 18 March 2007 (CET)

----

after creating the files i get this error message after starting the tutorial 3 application (through dbus-launch ./tutorial3):

tutorial3: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file tutorial3ui.rc

but this file exists in the current directory... any hint? thx --[[User:Stefon|Stefon]] 21:41, 16 April 2007 (CEST)

:It tells you in the CMake section that you must install the application in order to get it to work. --[[User:Milliams|milliams]] 22:38, 16 April 2007 (CEST)

----
sorry. you are right. maybe we can stress this difference out a little more?

--[[User:Stefon|Stefon]] 00:31, 18 April 2007 (CEST)

== Broken tutorial (kdelibs have changed) ==

KAction has no constructor which takes a KActionCollection and a QString as stated in the tutorial. Also, moments later in the "final" code section, this constructor is not used.

A QAction is also being used! :@

--[[User:Gavinbeatty|Gavinbeatty]] 22:50, 19 June 2007 (CEST)

Well it seems that KActionCollection extends QAction, so I doubt it's even possible or sane to use a KAction here. Not to mention that if you use QAction you depend a little less on the kdelibs. The problem is that knowing that, you learn basically nothing about KAction in this Tutorial.

--fabiank2

:Where possible, K* classes should be used in place of Q* classes. I've fixed the tutorial to correctly use KAction. --[[User:Milliams|milliams]] 17:26, 28 June 2007 (CEST)

The link on KStandardAction is dead, it should lead to http://api.kde.org/4.0-api/kdelibs-apidocs/kdeui/html/namespaceKStandardAction.html but leads to classmapper, which doesn't find it. 12/27/07

--shaga
:It's really a problem with classmapper that it doesn't search for namespace matches. Nonetheless, I've changed it now to hard-link to the url. Thanks for pointing this out. --[[User:Milliams|milliams]] 23:07, 27 December 2007 (CET)

Development/Tutorials/KCmdLineArgs

2007-12-27T16:16:39Z

Milliams: mainwindow.h/cpp

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Command line arguments (Under construction [[User:milliams]])|

pre=[[Development/Tutorials/Saving and loading|Tutorial 4 - Loading and saving]]|

next=[[Development/Tutorials/###|Tutorial 6 - ###]] (TODO [[User:milliams]])|

reading={{class|KCmdLineArgs}} {{class|KCmdLineOptions}}
}}

==Abstract==

Now that we have a text editor which can open and save files. We will now make the editor act more like a desktop application by enabling it to open files from command line arguments or even using ''Open with'' from within Dolphin.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>
#include <KUrl> //new

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial5", "tutorial5",
ki18n("Tutorial 5"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KCmdLineOptions options; //new
options.add("+[file]", ki18n("Document to open")); //new
KCmdLineArgs::addCmdLineOptions(options); //new

KApplication app;

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

KCmdLineArgs *args = KCmdLineArgs::parsedArgs(); //new
if(args->count()) //new
{
window->openFile(args->url(0).url()); //new
}

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

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT

public:
MainWindow(QWidget *parent=0);
void openFile(const QString &inputFileName); //new

private:
KTextEdit* textArea;
void setupActions();
QString fileName;

private slots:
void newFile();
void openFile();
void saveFile();
void saveFileAs();
void saveFileAs(const QString &outputFileName);
};

#endif
</code>

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog>
#include <KMessageBox>
#include <KIO/NetAccess>
#include <KSaveFile>
#include <QTextStream>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString())
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection());

KStandardAction::save(this, SLOT(saveFile()),
actionCollection());

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection());

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection());

setupGUI();
}

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile() //changed
{
openFile(KFileDialog::getOpenFileName());
}

void MainWindow::openFile(const QString &inputFileName) //new
{
QString tmpFile;
if(KIO::NetAccess::download(inputFileName, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = inputFileName;

KIO::NetAccess::removeTempFile(tmpFile);
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial5" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to the <tt>tutorial''x''ui.rc</tt> from the last two tutorials except <tt>tutorial''x''</tt> is now <tt>tutorial5</tt>.

==Explanation==

===mainwindow.h===

Here we have done nothing but add a new <tt>openFile</tt> function which takes a <tt>QString</tt>
<code cppqt>
void openFile(const QString &inputFileName);
</code>

===mainwindow.cpp===

There's no new code here, only rearranging. Everything from <tt>void openFile()</tt> has been moved into <tt>void openFile(const QString &inputFileName)</tt> except the call to <tt>KFileDialog::getOpenFileName()</tt>.

This way, we can call <tt>openFile()</tt> if we want to display a dialog, or we can call <tt>openFile(QString)</tt> if we know the name of the file already.

===main.cpp===

This is where all the {{class|KCmdLineArgs}} magic happens.

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial5)

find_package(KDE4 REQUIRED)
include_directories( ${KDE4_INCLUDES} )

set(tutorial5_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial5 ${tutorial5_SRCS})

target_link_libraries(tutorial5 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial5 DESTINATION ${BIN_INSTALL_DIR})
install( FILES tutorial5ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial5 )
</code>

With this file, the tutorial can built and run in the same way as tutorial 3 and 4. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial5

==Moving On==
Now you can move on to the ### (TODO [[User:milliams]]) tutorial.

[[Category:C++]]

File:Introtokdetutorial5.png

2007-12-27T15:00:13Z

Milliams: uploaded a new version of "Image:Introtokdetutorial5.png": Let's put it in a Konsole window

File:Introtokdetutorial5.png

2007-12-27T14:54:11Z

Milliams:

File:Introtokdetutorial4.png

2007-12-27T14:54:02Z

Milliams:

File:Introtokdetutorial3.png

2007-12-27T14:53:03Z

Milliams: uploaded a new version of "Image:Introtokdetutorial3.png": Use Oxygen theme and windec

File:Introtokdetutorial2.png

2007-12-27T14:52:44Z

Milliams: uploaded a new version of "Image:Introtokdetutorial2.png": Use Oxygen theme and windec

File:Introtokdetutorial1.png

2007-12-27T14:52:21Z

Milliams: uploaded a new version of "Image:Introtokdetutorial1.png": Use Oxygen theme and windec

This is what you should get once the program is done.

Development/Tutorials

2007-12-27T14:34:41Z

Milliams: /* Introduction To KDE 4 Programming */ Add link to latest tutorial

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

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

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

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

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

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

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

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

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

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

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

;[[Development/Tutorials/Command-Line Options|Using Command-line Options]]
:''Processing and accessing command-line arguments the easy way with KDE's command line arguments classes.''

== Testing And Debugging ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Documentation ==

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

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

== Application Automation and Scripting ==

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

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

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

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

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

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

=== KOffice ===
; [[Development/Tutorials/KOffice Overview|KOffice Overview]]
:''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 Scripting]]
:''This tutorial shows how to script KWord with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/KSpread Scripting|KSpread Scripting]]
:''This tutorial shows how to script KSpread with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/Krita Scripting|Krita Scripting]]
:''This tutorial shows how to script Krita with Python, Ruby or JavaScript using Kross.''

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

== Search and Metadata ==

=== Strigi ===

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

=== Nepomuk ===

; [[Development/Tutorials/Metadata/KMetaData first steps|Nepomuk first steps]]
:''Nepomuk is the KDE library which provides easy access to metadata in the [http://nepomuk-kde.semanticdesktop.org Nepomuk-KDE] system. Learn how to make your application create and read metadata using the Nepomuk system.''

== Hardware Awareness (Solid) ==

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

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

== Multimedia (Phonon) ==

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

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

== Plasma ==

;[[Development/Tutorials/Plasma/GettingStarted|Getting Started With Plasmoids]]
:''Creating your first Plasma widget, or Plasmoid, in C++ with an SVG background, an icon and some text''

;[[Development/Tutorials/Plasma/DataEngines|Writing A DataEngine]]
:''DataEngines provide a standardized interface to various data sources for visualizations to use. Learn what a DataEngine is and how to write one of your own.''

;[[Development/Tutorials/Plasma/UsingDataEngines|Using DataEngines in Plasmoids]]
:''With a DataEngine, it is possible to retrieve data for display in a simple and standard way. This tutorial covers the topic of how to use DataEngines for this purpose in Plasmoids.''

;[[Development/Tutorials/Plasma/AbstractRunner|Creating Runners]]
:''Runners are plugins that provide action-based search functionality in the Plasma workspace "run command" dialog. These plugins can be used by any application that links again libplasma.''

== Kate / Kwrite ==

;[[Development/Tutorials/Kate/KTextEditor Plugins|Getting Started With KTextEditor Plugins]]
:''Creating your first KTextEditor plugin''

==Printing==

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

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

== Get Hot New Stuff ==
; [[Development/Tutorials/Introduction to Get Hot New Stuff|Introduction to Get Hot New Stuff]]
:''An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.''

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

== Rapid Application Development ==

=== Python ===

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

=== Ruby ===

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

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

=== Shell ===

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

== Other tutorials ==

=== Using the KDE Games Library ===
;[[Development/Tutorials/Games/KStandardGameAction| KStandardGameAction]]
:''Using libkdegames to make your game fit the kdegames standard''
;[[Development/Tutorials/Games/Highscores| Highscores]]
:''Implementing a simple highscore table into your game''
;[[Development/Tutorials/Games/Theme Selector| Theme Selector]]
:''Using the libkdegames theme selection dialog''

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

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

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

== KDE2 and KDE3 Materials ==

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

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

[[Category:KDE4]]

Development/Tutorials/KCmdLineArgs

2007-12-27T14:25:43Z

Milliams: /* Abstract */ ++

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Command line arguments (Under construction [[User:milliams]])|

pre=[[Development/Tutorials/Saving and loading|Tutorial 4 - Loading and saving]]|

next=[[Development/Tutorials/###|Tutorial 6 - ###]] (TODO [[User:milliams]])|

reading={{class|KCmdLineArgs}} {{class|KCmdLineOptions}}
}}

==Abstract==

Now that we have a text editor which can open and save files. We will now make the editor act more like a desktop application by enabling it to open files from command line arguments or even using ''Open with'' from within Dolphin.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>
#include <KUrl> //new

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial5", "tutorial5",
ki18n("Tutorial 5"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KCmdLineOptions options; //new
options.add("+[file]", ki18n("Document to open")); //new
KCmdLineArgs::addCmdLineOptions(options); //new

KApplication app;

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

KCmdLineArgs *args = KCmdLineArgs::parsedArgs(); //new
if(args->count()) //new
{
window->openFile(args->url(0).url()); //new
}

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

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT

public:
MainWindow(QWidget *parent=0);
void openFile(const QString &inputFileName); //new

private:
KTextEdit* textArea;
void setupActions();
QString fileName;

private slots:
void newFile();
void openFile();
void saveFile();
void saveFileAs();
void saveFileAs(const QString &outputFileName);
};

#endif
</code>

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog>
#include <KMessageBox>
#include <KIO/NetAccess>
#include <KSaveFile>
#include <QTextStream>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString())
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection());

KStandardAction::save(this, SLOT(saveFile()),
actionCollection());

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection());

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection());

setupGUI();
}

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile() //changed
{
openFile(KFileDialog::getOpenFileName());
}

void MainWindow::openFile(const QString &inputFileName) //new
{
QString tmpFile;
if(KIO::NetAccess::download(inputFileName, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = inputFileName;

KIO::NetAccess::removeTempFile(tmpFile);
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial5" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to the <tt>tutorial''x''ui.rc</tt> from the last two tutorials except <tt>tutorial''x''</tt> is now <tt>tutorial5</tt>.

==Explanation==

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial5)

find_package(KDE4 REQUIRED)
include_directories( ${KDE4_INCLUDES} )

set(tutorial5_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial5 ${tutorial5_SRCS})

target_link_libraries(tutorial5 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial5 DESTINATION ${BIN_INSTALL_DIR})
install( FILES tutorial5ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial5 )
</code>

With this file, the tutorial can built and run in the same way as tutorial 3 and 4. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial5

==Moving On==
Now you can move on to the ### (TODO [[User:milliams]]) tutorial.

[[Category:C++]]

Development/Tutorials/First program

2007-12-27T14:16:45Z

Milliams: /* The Code */ Remove unncecessary headers

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

series=Beginner Tutorial|

name=Hello World|

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [http://www.trolltech.com/products/qt/ Qt], [[Getting_Started/Build/KDE4|KDE4 development environment]]|

next=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]]|

reading=[[Development/Tutorials/CMake|CMake]]
}}

==Abstract==
Your first program shall greet the world with a friendly "Hello World", what else? For that, we will use a {{class|KMessageBox}} and customise one of the buttons.
[[image:introtokdetutorial1.png|frame|center]]

{{tip|To get more information about any class you come across, Konqueror offers a quick shortcut. So to look for information about KMessageBox, just type "kde:kmessagebox" into Konqueror and you'll be taken to the documentation.}}

{{tip|
You might want to use KDevelop for your projects, which does many nice things like code completion, easy access to API documentation or debugging support.

Read [[Getting_Started/Set_up_KDE_4_for_development#KDevelop|this tutorial]] to set up KDevelop correctly for this task. You probably want to check if the setup is working by testing opening an existing KDE 4 application with KDevelop first.

You still need to edit the CMake files by hand though.
}}

==The Code==
All the code we need will be in one file, <tt>main.cpp</tt>. Create that file with the code below:
<code cppqt>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>
#include <KMessageBox>

int main (int argc, char *argv[])
{
KAboutData aboutData("tutorial1", // The program name used internally.
0, // The message catalog name, use program name if null.
ki18n("Tutorial 1"), // A displayable program name string.
"1.0", // The program version string.
ki18n("KMessageBox popup"), // A short description of what the program does.
KAboutData::License_GPL, // License identifier
ki18n("(c) 2007"), // Copyright Statement
ki18n("Some text..."), // Some free form text, that can contain any kind of information.
"http://tutorial.com", // The program homepage string.
"submit@bugs.kde.org"); // The bug report email address string.

KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;
KGuiItem guiItem( QString( "Hello" ), QString(),
QString( "this is a tooltip" ),
QString( "this is a whatsthis" ) );
KMessageBox::questionYesNo( 0, "Hello World", "Hello", guiItem );
}
</code>
The first KDE specific code we come across in this program is {{class|KAboutData}}. This is the class used to store information about the program such as a short description, authors or license information. Pretty much every KDE application should use this class.

Then we come to {{class|KCmdLineArgs}}. This is the class one would use to specify command line switches to, for example, open the program with a specific file. However, in this tutorial, we simply initialise it with the {{class|KAboutData}} object we created so we can use the <tt>--version</tt> or <tt>--author</tt> switches.

Then we create a {{class|KApplication}} object. This needs to be done exactly once in each program since it is needed for things such as [[Development/Tutorials/Localization/i18n|i18n]].

Now we've done all the necessary KDE setup, we can move on to doing interesting things with our application. We're going to create a popup box but we're going to customise one of the buttons. To do this customisation, we need to use a {{class|KGuiItem}} object. The first argument in the {{class|KGuiItem}} constructor is the text that will appear on the item (in our case, a button). Then we have an option of setting an icon for the button but we don't want one so we just give it <tt>QString()</tt>. Finally we set the tooltip (what appears when you hover over an item) and finally the "What's This?" (accessed through right-clicking or Shift-F1) text.

Now we have our item, we can create our popup. We call the <tt>{{class|KMessageBox}}::questionYesNo()</tt> function which, by default, creates a message box with a "Yes" and a "No" button. The second argument is the text that will appear in the middle of the popup box. The third is the caption the window will have and finally we set the KGuiItem for (what would normally be) the "Yes" button to the <tt>KGuiItem guiItem</tt> we created.

We're all done as far as the code is concerned. Now to build it and try it out.

==Build==
If you set up your environment as described in [[Getting Started/Build/KDE4]], you can compile this code with

g++ main.cpp -o tutorial1 \
-I$QTDIR/include/Qt \
-I$QTDIR/include/QtCore \
-I$QTDIR/include \
-I$KDEDIR/include/KDE \
-I$KDEDIR/include \
-L$KDEDIR/lib \
-L$QTDIR/lib -lQtCore -lQtGui -lkdeui -lkdecore
and then run it with
dbus-launch ./tutorial1

===Using CMake===
If that worked, you may want to use [[Development/Tutorials/CMake|CMake]], just like the rest of KDE. This will automatically locate the libraries and headers for KDE, Qt etc. and will allow you to easily build your applications on other computers.
====CMakeLists.txt====
Create a file named CMakeLists.txt in the same directory as main.cpp with this content:
<code ini n>
project (tutorial1)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial1_SRCS main.cpp)

kde4_add_executable(tutorial1 ${tutorial1_SRCS})
target_link_libraries(tutorial1 ${KDE4_KDEUI_LIBS})
</code>
The <tt>find_package()</tt> function locates the package that you ask it for (in this case KDE4) and sets some variables describing the location of the package's headers and libraries. In this case we will use the <tt>KDE4_INCLUDES</tt> variable which contains the path to the KDE4 header files.

In order to allow the compiler to find these files, we pass that variable to the <tt>include_directories()</tt> function which adds the KDE4 headers to the header search path.

Next we create a variable called <tt>tutorial1_SRCS</tt> using the <tt>set()</tt> function. In this case we simply set it to the name of our only source file.

Then we use <tt>kde4_add_executable()</tt> to create an executable called <tt>tutorial1</tt> from the source files listed in our <tt>tutorial1_SRCS</tt> variable. Finally we link our executable to the KDE4 kdeui library using <tt>target_link_libraries()</tt> and the <tt>KDE4_KDEUI_LIBS</tt> variable which was set by the <tt>find_package()</tt> function.

====Make And Run====
Again, if you set up your environment as described in [[Getting_Started/Build/KDE4|Getting Started/Build/KDE4]], you can compile this code with:
cmakekde

Or if you did not:

mkdir build && cd build
cmake ..
make

And launch it with:
./tutorial1

==Moving On==
Now you can move on to [[Development/Tutorials/Using_KXmlGuiWindow|using KXmlGuiWindow]].

[[Category:C++]]

Development/Tutorials/Saving and loading

2007-12-27T14:08:31Z

Milliams: Remove TODOs for the navigation

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=[[Development/Tutorials/KCmdLineArgs|Tutorial 5 - Using KCmdLineArgs]]|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful. At the most basic, a text editor needs to be able to load files from disc, save files that you've created/edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we declare a <tt>{{qt|QString}} fileName</tt>.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream> //new

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile(tmpFile);
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

Okay, now to implement the code that will do the loading and saving. This will all be happening in <tt>mainwindow.cpp</tt>

The first thing we do is add
<code cppqt>
fileName(QString())
</code>
to the <tt>MainWindow</tt> constructor list on line 16. This makes sure that <tt>fileName</tt> is empty right from the beginning.

===Adding the actions===

The first thing we are going to do is provide the outward interface for the user so they can tell the application to load and save. Like with the <tt>quit</tt> action in tutorial 3, we will use <tt>KStandardActions</tt>. On lines 37 to 47 we add the actions in the same way as for the <tt>quit</tt> action. For each one, we connect it to the appropriate slot that we declared in the header file.

===Creating a new document===

The first function we create is the <tt>newFile()</tt> function.
<code cppqt>
void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}
</code>
<tt>fileName.clear()</tt> sets the <tt>fileName</tt> QString to be empty to reflect the fact that this document does not yet have a presence on disc. <tt>textArea->clear()</tt> then clears the central text area using the same function that we connected the <tt>clear</tt> <tt>KAction</tt> to in tutorial 3.

===Saving a file===

====saveFileAs(QString)====

Now we get onto our first file handling code. We're going to implement a function which will save the contents of the text area to the file name given as a parameter. KDE provides a class for safely saving a file called {{class|KSaveFile}} which is derived from Qt's {{qt|QFile}}.

The function's prototype is
<code cppqt>
void MainWindow::saveFileAs(const QString &outputFileName)
</code>

We then create our <tt>KSaveFile</tt> object and open it with
<code cppqt>
KSaveFile file(outputFileName);
file.open();
</code>

Now that we have our file to write to, we need to format the text in the text area to a format which can be written to file. For this, we create a {{qt|QByteArray}} and fill it with the plain text version of whatever is in the text area:
<code cppqt>
QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
</code>
Now that we have our <tt>QByteArray</tt>, we use it to write to the file with <tt>KSaveFile::write()</tt>. If we were using a normal <tt>QFile</tt>, this would make the changes immediately. However, if a problem occurred partway through writing, the file would become corrupted. For this reason, <tt>KSaveFile</tt> works by first writing to a temporary file and then, when you call <tt>KSaveFile::finalize()</tt> the changes are made to the actual file.
<code cppqt>
file.write(outputByteArray);
file.finalize();
file.close();
</code>
Finally, we set <tt>MainWindows</tt>'s <tt>fileName</tt> member to point to the file name we just saved to.
<code cppqt>
fileName = outputFileName;
</code>

====saveFileAs()====

This is the function that the <tt>saveAs</tt> slot is connected to. It simply calls the generic <tt>saveFileAs(QString)</tt> function and passes the file name returned by <tt>{{class|KFileDialog}}::[http://api.kde.org/4.0-api/kdelibs-apidocs/kio/html/classKFileDialog.html#8891356c249c5911e1ab15cc2739a89b getSaveFileName()]</tt>.

<code cppqt>
void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}
</code>

This our first actual use of the KIO library. {{class|KFileDialog}} provides a number of static functions for displaying the common file dialog that is used by all KDE applications. Calling <tt>KFileDialog::getSaveFileName()</tt> will display a dialog where the user can select the name of the file to save to or choose a new name. The function returns the full file name, which we then pass to <tt>saveFileAs(QString)</tt>.

====saveFile()====

<code cppqt>
void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}
</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.

===Loading a file===

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

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>:
<code cppqt>
QString fileNameFromDialog = KFileDialog::getOpenFileName();
</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
<code cppqt>
KIO::NetAccess::download(fileNameFromDialog, tmpFile, this)
</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.

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:
<code cppqt>
KMessageBox::error(this, KIO::NetAccess::lastErrorString());
</code>

Otherwise, we continue with opening the file.

We create a QFile by passing the temporary file created by <tt>NetAccess::download()</tt> to its constructor and then open it in read-only mode
<code cppqt>
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
</code>

In order to display the contents of the file, we must use a {{class|QTextStream}}. We create one by passing the contents of our file to its constructor and then call QFile's <tt>readAll()</tt> function to get the text from the file. This is then passed to the <tt>setPlainText()</tt> function of our text area.

<code cppqt>
textArea->setPlainText(QTextStream(&file).readAll());
</code>

We then store the path of the file we just opened:
<code cppqt>
fileName = fileNameFromDialog;
</code>
and finally, we remove the temporary file that was created by <tt>NetAccess::download()</tt>:
<code cppqt>
KIO::NetAccess::removeTempFile(tmpFile);
</code>

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

==Moving On==
Now you can move on to the [[Development/Tutorials/KCmdLineArgs|KCmdLineArgs]] tutorial.

[[Category:C++]]

Development/Tutorials/KCmdLineArgs

2007-12-27T14:06:52Z

Milliams: All the code's in. This should be shorter than the last tutorial

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Command line arguments (Under construction [[User:milliams]])|

pre=[[Development/Tutorials/Saving and loading|Tutorial 4 - Loading and saving]]|

next=[[Development/Tutorials/###|Tutorial 6 - ###]] (TODO [[User:milliams]])|

reading={{class|KCmdLineArgs}} {{class|KCmdLineOptions}}
}}

==Abstract==

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>
#include <KUrl> //new

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial5", "tutorial5",
ki18n("Tutorial 5"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KCmdLineOptions options; //new
options.add("+[file]", ki18n("Document to open")); //new
KCmdLineArgs::addCmdLineOptions(options); //new

KApplication app;

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

KCmdLineArgs *args = KCmdLineArgs::parsedArgs(); //new
if(args->count()) //new
{
window->openFile(args->url(0).url()); //new
}

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

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT

public:
MainWindow(QWidget *parent=0);
void openFile(const QString &inputFileName); //new

private:
KTextEdit* textArea;
void setupActions();
QString fileName;

private slots:
void newFile();
void openFile();
void saveFile();
void saveFileAs();
void saveFileAs(const QString &outputFileName);
};

#endif
</code>

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog>
#include <KMessageBox>
#include <KIO/NetAccess>
#include <KSaveFile>
#include <QTextStream>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString())
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection());

KStandardAction::save(this, SLOT(saveFile()),
actionCollection());

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection());

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection());

setupGUI();
}

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile() //changed
{
openFile(KFileDialog::getOpenFileName());
}

void MainWindow::openFile(const QString &inputFileName) //new
{
QString tmpFile;
if(KIO::NetAccess::download(inputFileName, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = inputFileName;

KIO::NetAccess::removeTempFile(tmpFile);
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial5" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to the <tt>tutorial''x''ui.rc</tt> from the last two tutorials except <tt>tutorial''x''</tt> is now <tt>tutorial5</tt>.

==Explanation==

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial5)

find_package(KDE4 REQUIRED)
include_directories( ${KDE4_INCLUDES} )

set(tutorial5_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial5 ${tutorial5_SRCS})

target_link_libraries(tutorial5 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial5 DESTINATION ${BIN_INSTALL_DIR})
install( FILES tutorial5ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial5 )
</code>

With this file, the tutorial can built and run in the same way as tutorial 3 and 4. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial5

==Moving On==
Now you can move on to the ### (TODO [[User:milliams]]) tutorial.

[[Category:C++]]

Development/Tutorials/Saving and loading

2007-12-27T01:11:42Z

Milliams: Add links to the next (as yet unwritten tutorial)

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=[[Development/Tutorials/KCmdLineArgs|Tutorial 5 - Using KCmdLineArgs]] (TODO [[User:milliams]])|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful. At the most basic, a text editor needs to be able to load files from disc, save files that you've created/edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we declare a <tt>{{qt|QString}} fileName</tt>.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream> //new

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile(tmpFile);
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

Okay, now to implement the code that will do the loading and saving. This will all be happening in <tt>mainwindow.cpp</tt>

The first thing we do is add
<code cppqt>
fileName(QString())
</code>
to the <tt>MainWindow</tt> constructor list on line 16. This makes sure that <tt>fileName</tt> is empty right from the beginning.

===Adding the actions===

The first thing we are going to do is provide the outward interface for the user so they can tell the application to load and save. Like with the <tt>quit</tt> action in tutorial 3, we will use <tt>KStandardActions</tt>. On lines 37 to 47 we add the actions in the same way as for the <tt>quit</tt> action. For each one, we connect it to the appropriate slot that we declared in the header file.

===Creating a new document===

The first function we create is the <tt>newFile()</tt> function.
<code cppqt>
void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}
</code>
<tt>fileName.clear()</tt> sets the <tt>fileName</tt> QString to be empty to reflect the fact that this document does not yet have a presence on disc. <tt>textArea->clear()</tt> then clears the central text area using the same function that we connected the <tt>clear</tt> <tt>KAction</tt> to in tutorial 3.

===Saving a file===

====saveFileAs(QString)====

Now we get onto our first file handling code. We're going to implement a function which will save the contents of the text area to the file name given as a parameter. KDE provides a class for safely saving a file called {{class|KSaveFile}} which is derived from Qt's {{qt|QFile}}.

The function's prototype is
<code cppqt>
void MainWindow::saveFileAs(const QString &outputFileName)
</code>

We then create our <tt>KSaveFile</tt> object and open it with
<code cppqt>
KSaveFile file(outputFileName);
file.open();
</code>

Now that we have our file to write to, we need to format the text in the text area to a format which can be written to file. For this, we create a {{qt|QByteArray}} and fill it with the plain text version of whatever is in the text area:
<code cppqt>
QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
</code>
Now that we have our <tt>QByteArray</tt>, we use it to write to the file with <tt>KSaveFile::write()</tt>. If we were using a normal <tt>QFile</tt>, this would make the changes immediately. However, if a problem occurred partway through writing, the file would become corrupted. For this reason, <tt>KSaveFile</tt> works by first writing to a temporary file and then, when you call <tt>KSaveFile::finalize()</tt> the changes are made to the actual file.
<code cppqt>
file.write(outputByteArray);
file.finalize();
file.close();
</code>
Finally, we set <tt>MainWindows</tt>'s <tt>fileName</tt> member to point to the file name we just saved to.
<code cppqt>
fileName = outputFileName;
</code>

====saveFileAs()====

This is the function that the <tt>saveAs</tt> slot is connected to. It simply calls the generic <tt>saveFileAs(QString)</tt> function and passes the file name returned by <tt>{{class|KFileDialog}}::[http://api.kde.org/4.0-api/kdelibs-apidocs/kio/html/classKFileDialog.html#8891356c249c5911e1ab15cc2739a89b getSaveFileName()]</tt>.

<code cppqt>
void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}
</code>

This our first actual use of the KIO library. {{class|KFileDialog}} provides a number of static functions for displaying the common file dialog that is used by all KDE applications. Calling <tt>KFileDialog::getSaveFileName()</tt> will display a dialog where the user can select the name of the file to save to or choose a new name. The function returns the full file name, which we then pass to <tt>saveFileAs(QString)</tt>.

====saveFile()====

<code cppqt>
void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}
</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.

===Loading a file===

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

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>:
<code cppqt>
QString fileNameFromDialog = KFileDialog::getOpenFileName();
</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
<code cppqt>
KIO::NetAccess::download(fileNameFromDialog, tmpFile, this)
</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.

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:
<code cppqt>
KMessageBox::error(this, KIO::NetAccess::lastErrorString());
</code>

Otherwise, we continue with opening the file.

We create a QFile by passing the temporary file created by <tt>NetAccess::download()</tt> to its constructor and then open it in read-only mode
<code cppqt>
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
</code>

In order to display the contents of the file, we must use a {{class|QTextStream}}. We create one by passing the contents of our file to its constructor and then call QFile's <tt>readAll()</tt> function to get the text from the file. This is then passed to the <tt>setPlainText()</tt> function of our text area.

<code cppqt>
textArea->setPlainText(QTextStream(&file).readAll());
</code>

We then store the path of the file we just opened:
<code cppqt>
fileName = fileNameFromDialog;
</code>
and finally, we remove the temporary file that was created by <tt>NetAccess::download()</tt>:
<code cppqt>
KIO::NetAccess::removeTempFile(tmpFile);
</code>

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

==Moving On==
Now you can move on to the [[Development/Tutorials/KCmdLineArgs|KCmdLineArgs]] (TODO [[User:milliams]]) tutorial.

[[Category:C++]]

Development/Tutorials/Saving and loading

2007-12-27T01:00:47Z

Milliams: Remove 'under construction' signs since it's mostly complete

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=KCmdLineArgs (TODO [[User:milliams]])|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful. At the most basic, a text editor needs to be able to load files from disc, save files that you've created/edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we declare a <tt>{{qt|QString}} fileName</tt>.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream> //new

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile(tmpFile);
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

Okay, now to implement the code that will do the loading and saving. This will all be happening in <tt>mainwindow.cpp</tt>

The first thing we do is add
<code cppqt>
fileName(QString())
</code>
to the <tt>MainWindow</tt> constructor list on line 16. This makes sure that <tt>fileName</tt> is empty right from the beginning.

===Adding the actions===

The first thing we are going to do is provide the outward interface for the user so they can tell the application to load and save. Like with the <tt>quit</tt> action in tutorial 3, we will use <tt>KStandardActions</tt>. On lines 37 to 47 we add the actions in the same way as for the <tt>quit</tt> action. For each one, we connect it to the appropriate slot that we declared in the header file.

===Creating a new document===

The first function we create is the <tt>newFile()</tt> function.
<code cppqt>
void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}
</code>
<tt>fileName.clear()</tt> sets the <tt>fileName</tt> QString to be empty to reflect the fact that this document does not yet have a presence on disc. <tt>textArea->clear()</tt> then clears the central text area using the same function that we connected the <tt>clear</tt> <tt>KAction</tt> to in tutorial 3.

===Saving a file===

====saveFileAs(QString)====

Now we get onto our first file handling code. We're going to implement a function which will save the contents of the text area to the file name given as a parameter. KDE provides a class for safely saving a file called {{class|KSaveFile}} which is derived from Qt's {{qt|QFile}}.

The function's prototype is
<code cppqt>
void MainWindow::saveFileAs(const QString &outputFileName)
</code>

We then create our <tt>KSaveFile</tt> object and open it with
<code cppqt>
KSaveFile file(outputFileName);
file.open();
</code>

Now that we have our file to write to, we need to format the text in the text area to a format which can be written to file. For this, we create a {{qt|QByteArray}} and fill it with the plain text version of whatever is in the text area:
<code cppqt>
QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
</code>
Now that we have our <tt>QByteArray</tt>, we use it to write to the file with <tt>KSaveFile::write()</tt>. If we were using a normal <tt>QFile</tt>, this would make the changes immediately. However, if a problem occurred partway through writing, the file would become corrupted. For this reason, <tt>KSaveFile</tt> works by first writing to a temporary file and then, when you call <tt>KSaveFile::finalize()</tt> the changes are made to the actual file.
<code cppqt>
file.write(outputByteArray);
file.finalize();
file.close();
</code>
Finally, we set <tt>MainWindows</tt>'s <tt>fileName</tt> member to point to the file name we just saved to.
<code cppqt>
fileName = outputFileName;
</code>

====saveFileAs()====

This is the function that the <tt>saveAs</tt> slot is connected to. It simply calls the generic <tt>saveFileAs(QString)</tt> function and passes the file name returned by <tt>{{class|KFileDialog}}::[http://api.kde.org/4.0-api/kdelibs-apidocs/kio/html/classKFileDialog.html#8891356c249c5911e1ab15cc2739a89b getSaveFileName()]</tt>.

<code cppqt>
void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}
</code>

This our first actual use of the KIO library. {{class|KFileDialog}} provides a number of static functions for displaying the common file dialog that is used by all KDE applications. Calling <tt>KFileDialog::getSaveFileName()</tt> will display a dialog where the user can select the name of the file to save to or choose a new name. The function returns the full file name, which we then pass to <tt>saveFileAs(QString)</tt>.

====saveFile()====

<code cppqt>
void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}
</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.

===Loading a file===

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

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>:
<code cppqt>
QString fileNameFromDialog = KFileDialog::getOpenFileName();
</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
<code cppqt>
KIO::NetAccess::download(fileNameFromDialog, tmpFile, this)
</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.

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:
<code cppqt>
KMessageBox::error(this, KIO::NetAccess::lastErrorString());
</code>

Otherwise, we continue with opening the file.

We create a QFile by passing the temporary file created by <tt>NetAccess::download()</tt> to its constructor and then open it in read-only mode
<code cppqt>
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
</code>

In order to display the contents of the file, we must use a {{class|QTextStream}}. We create one by passing the contents of our file to its constructor and then call QFile's <tt>readAll()</tt> function to get the text from the file. This is then passed to the <tt>setPlainText()</tt> function of our text area.

<code cppqt>
textArea->setPlainText(QTextStream(&file).readAll());
</code>

We then store the path of the file we just opened:
<code cppqt>
fileName = fileNameFromDialog;
</code>
and finally, we remove the temporary file that was created by <tt>NetAccess::download()</tt>:
<code cppqt>
KIO::NetAccess::removeTempFile(tmpFile);
</code>

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

==Moving On==
Now you can move on to KCmdLineArgs (TODO [[User:milliams]]).

[[Category:C++]]

Development/Tutorials/Saving and loading

2007-12-27T00:49:35Z

Milliams: How to open files. This tutorial is structurally complete now!

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files (Under construction [[User:milliams]])|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=KCmdLineArgs (TODO [[User:milliams]])|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful. At the most basic, a text editor needs to be able to load files from disc, save files that you've created/edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we declare a <tt>{{qt|QString}} fileName</tt>.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream> //new

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile(tmpFile);
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

Okay, now to implement the code that will do the loading and saving. This will all be happening in <tt>mainwindow.cpp</tt>

The first thing we do is add
<code cppqt>
fileName(QString())
</code>
to the <tt>MainWindow</tt> constructor list on line 16. This makes sure that <tt>fileName</tt> is empty right from the beginning.

===Adding the actions===

The first thing we are going to do is provide the outward interface for the user so they can tell the application to load and save. Like with the <tt>quit</tt> action in tutorial 3, we will use <tt>KStandardActions</tt>. On lines 37 to 47 we add the actions in the same way as for the <tt>quit</tt> action. For each one, we connect it to the appropriate slot that we declared in the header file.

===Creating a new document===

The first function we create is the <tt>newFile()</tt> function.
<code cppqt>
void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}
</code>
<tt>fileName.clear()</tt> sets the <tt>fileName</tt> QString to be empty to reflect the fact that this document does not yet have a presence on disc. <tt>textArea->clear()</tt> then clears the central text area using the same function that we connected the <tt>clear</tt> <tt>KAction</tt> to in tutorial 3.

===Saving a file===

====saveFileAs(QString)====

Now we get onto our first file handling code. We're going to implement a function which will save the contents of the text area to the file name given as a parameter. KDE provides a class for safely saving a file called {{class|KSaveFile}} which is derived from Qt's {{qt|QFile}}.

The function's prototype is
<code cppqt>
void MainWindow::saveFileAs(const QString &outputFileName)
</code>

We then create our <tt>KSaveFile</tt> object and open it with
<code cppqt>
KSaveFile file(outputFileName);
file.open();
</code>

Now that we have our file to write to, we need to format the text in the text area to a format which can be written to file. For this, we create a {{qt|QByteArray}} and fill it with the plain text version of whatever is in the text area:
<code cppqt>
QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
</code>
Now that we have our <tt>QByteArray</tt>, we use it to write to the file with <tt>KSaveFile::write()</tt>. If we were using a normal <tt>QFile</tt>, this would make the changes immediately. However, if a problem occurred partway through writing, the file would become corrupted. For this reason, <tt>KSaveFile</tt> works by first writing to a temporary file and then, when you call <tt>KSaveFile::finalize()</tt> the changes are made to the actual file.
<code cppqt>
file.write(outputByteArray);
file.finalize();
file.close();
</code>
Finally, we set <tt>MainWindows</tt>'s <tt>fileName</tt> member to point to the file name we just saved to.
<code cppqt>
fileName = outputFileName;
</code>

====saveFileAs()====

This is the function that the <tt>saveAs</tt> slot is connected to. It simply calls the generic <tt>saveFileAs(QString)</tt> function and passes the file name returned by <tt>{{class|KFileDialog}}::[http://api.kde.org/4.0-api/kdelibs-apidocs/kio/html/classKFileDialog.html#8891356c249c5911e1ab15cc2739a89b getSaveFileName()]</tt>.

<code cppqt>
void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}
</code>

This our first actual use of the KIO library. {{class|KFileDialog}} provides a number of static functions for displaying the common file dialog that is used by all KDE applications. Calling <tt>KFileDialog::getSaveFileName()</tt> will display a dialog where the user can select the name of the file to save to or choose a new name. The function returns the full file name, which we then pass to <tt>saveFileAs(QString)</tt>.

====saveFile()====

<code cppqt>
void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}
</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.

===Loading a file===

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

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>:
<code cppqt>
QString fileNameFromDialog = KFileDialog::getOpenFileName();
</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
<code cppqt>
KIO::NetAccess::download(fileNameFromDialog, tmpFile, this)
</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.

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:
<code cppqt>
KMessageBox::error(this, KIO::NetAccess::lastErrorString());
</code>

Otherwise, we continue with opening the file.

We create a QFile by passing the temporary file created by <tt>NetAccess::download()</tt> to its constructor and then open it in read-only mode
<code cppqt>
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
</code>

In order to display the contents of the file, we must use a {{class|QTextStream}}. We create one by passing the contents of our file to its constructor and then call QFile's <tt>readAll()</tt> function to get the text from the file. This is then passed to the <tt>setPlainText()</tt> function of our text area.

<code cppqt>
textArea->setPlainText(QTextStream(&file).readAll());
</code>

We then store the path of the file we just opened:
<code cppqt>
fileName = fileNameFromDialog;
</code>
and finally, we remove the temporary file that was created by <tt>NetAccess::download()</tt>:
<code cppqt>
KIO::NetAccess::removeTempFile(tmpFile);
</code>

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

==Moving On==
Now you can move on to KCmdLineArgs (TODO [[User:milliams]]).

[[Category:C++]]

Template talk:Module

2007-12-26T23:56:15Z

Milliams: Should this template link to API docs?

== Should this template link to API docs? ==

Should this be linking to http://api.kde.org/4.0-api/{{{1}}}-apidocs/ as discussed at [[User_talk:Danimo]]?

Contribute/Bugsquad/KrushDays

2007-12-26T23:26:53Z

Milliams: A link is more visible than just text.

{{Box|KDE4 Krush Days|Join us Saturdays on irc in the #kde4-krush channel to work out release critical issues for KDE 4.0. Testers, artists, documenters and programmers are all welcome and encouraged to join in on the fun. Issues that are identified and being worked on will be added to this community scratchpad page.}}{{note|
* Please attach you nickname in irc when you add a bug to this page.
* Move fixed bugs to KrushDaysFixed and mention the revision number(s) of this fix.
* Please use <nowiki>{{bug|xxxxx}}</nowiki> to give links to bugs.
* Please always file new bugs noticed to '''[http://bugs.kde.org/ bugs.kde.org]'''. Many subprojects will not look at this page. Include all relevant information there. Do not link bug reports to external files.
* Do not report wishes here, use bugs.kde.org.}}{{Box|Crash Backtraces|
Do not use <nowiki>http://rafb.net/paste/</nowiki> for your crash backtraces, because those paste URLs there will expire after 24 hours.

Please use [http://pastebin.ca/ http://pastebin.ca/] for crash backtraces and add a link to your paste when you add the crash to the list below.

A backtrace is generally very helpful for developers to identify the reason for the crash. To get good backtraces, read [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports|this article]].
}}

== Build issues ==
* In kdebase on OS X 10.5 the build WITH_XKB = OFF variable is not respected resulting in failure of the build. (build process info found at http://techbase.kde.org/Getting_Started/Build/KDE4/Mac_OS_X_10.5_issues) Sorry it's so wordy, but I initially wrote it up for personal use.
* Kdepim don't build,error at 11% http://pastebin.com/mbfd8870 (Meskalamdug)

== kdeaccessibility ==

==== General things ====
* The 'Do you really want to activate "Slow keys"?' dialog is not obvious. You have a combobox down there where you can deactivate all accessx features & gestures, but it's a bit unclear should I press yes or no to deactivate the features... (teprrr)

==== KMag ====
* There is no magnification shown but some garbage fractal-like patterns ([[User:Icwiener|Icwiener]] 03:34, 10 November 2007 (CET))

== kdebase ==
==== Screen Locker (krunner_lock) ====
* running krunner_lock as a command seems to garble the screen but not actually lock it. (frank95com, jstubbs and mutlu_inek (rev. 743425 and 745228))
* A 'Leave Message' function like GNOME introduced it recently would be very handy. Patch for KDE 3.5.x: http://www.kde-apps.org/content/show.php/Leave+Message+clone+from+gnome-2.20?content=66631 GNOME implementation: http://www.gnome.org/start/2.20/notes/C/index.html#rnusers-login-and-screensaver (eliasp)

==== KRunner ====
* When clicking "options" on the krunner dialog (the alt-f2 dialog), all of the text is invisible (black on black I'm assuming). (level1)
** Opened a bug report with a patch: {{bug|154457}} (azuriel)

==== Konsole ====

* With compositing enabled, a 100% transparent background at is always black. KWin bug? (jstubbs) (confirmed by annma) (confirmed by TunaTom)
** Yes, the ARGB visual code is disabled in Konsole. Because ARGB and QWidget::scroll don't like each other. Here's a patch I'm using to enable ARGB and work around the bug QWidget::scroll hits: http://pastebin.ca/794952 (Vir)
* With compositing enabled, the selection foreground is the configured background color with no transparency and the selection background is the configured foreground with configured background transparency. Transparancy should switch with the colors or be disabled altogether for selections. (jstubbs)
* None of the Top-Level Alt+<letter> menu shortcuts work when the terminal has focus. When a menu is opened, the shortcuts inside work. (TunaTom)
** I can confirm it (FiNeX)
* Wish: can the New Tab icon be back?
** Please add your nick if you want it back! (annma, SSJ_GZ, frank95com, Tyl3r, yuriy, yojoe, winterz, FiNeX, tmcguire, JohnFlux, csh, gmartyn, eliasp)
** Add your nick here if you don't want it because it's wasting precious space for the tabs (and if you think that double clicking the empty space, shortcut and menu are enough options). (Vir, mutlu_inek)
** How about let the user decide by him/herself. (Carutsu)
* Wish: Make a right-clickable context menu so that tabs can be closed other than by shortcut or the main menu. (mutlu_inek)
* <s>Clicking on a split URL will cut off everything after the split(SSJ_GZ). See</s>
** <s>Confirmed by mutlu_inek (rev. 743425 and 745228)</s> Fixed in revision 751696 (mutlu_inek)
*** However, not all of the link will be underlined. mutlu_inek (rev. 751696)
* If you delselect the "show menu bar in new windows" option from the "edit profile" dialog and you click "Apply" (or "ok") the menubar will be hidden even in the current konsole window. The result is the opposite in the contrary situation (you have the menubar not visible and you select "show menu bar..."). When you hide the menubar in this way, the popup menu with the right click doesn't show the menuitem for show the menubar. If you hide the menubar with the option on the menu (EDIT->HIDE MENU BAR), the popup will have the option "SHOW MENU BAR". See {{bug|152253}} (FiNeX)
* <s>When copying several lines of text and pasteing into another application, all newlines in the copied text are missing (jstubbs)</s>
** Works fine for me (mutlu_inek (rev. 743425))
* When several tabs are open and I attempt to close the app, it offers me to close the app altogether or just the active tab. Selecting "Close Current Tab" sometimes closes the current tab and sometimes crashes Konsole. (mutlu_inek, rev. 743425 and 745228)
** I added a backtrace (non-KDE debugging symbols are missing, though): http://pastebin.ca/831868 (mutlu_inek, rev. 752605)
* If i launch a shell script with an application cli(for example vdr) all new konsole session launched start vdr,this happen only if shell script is launched from plasma desktop (Meskalamdug)

==== Dolphin ====
* <s>The "Desktop" and "Root" icons in dolphin have a completely different style than the usual folder icon. (mbiebl)</s> (can't reproduce with r745359 at kdebase [ereslibre])
* Select icon in folder/file properties doesn't show the icons of the selected categories at first. Only after changing the combobox the icons are loaded. (bbroeksema)(I can confirmed that [TunaTom r732119])
* "Empty Trash" does not show up in the file menu when viewing the trash (yuriy)
** Application menus should never be changed dynamically. So an option would be showing "Empty Trash" always. From my point of view using the context menu is enough (at least I'm not aware about any file manager that has "Empty Trash" as part of the file-menu). For further discussions please mail me directly (peter.penz@gmx.at) or just use the kfm-devel mailing list. Thanks! (Peter Penz)
** How about showing a colored bar on the top of the filelist with button "empty trash", like OS X has? Imho it would make it clearer that you're in a special folder and it'd make it easier to empty your trash from there. (teprrr)
** May just be me but I don't see the point of a move to trash entry when I'm in the trash. I don't see why that can't be changed to Remove Item. And if we are then going to change we might as well have a Empty trash option underneath it :) (DaSkreech)
* Several of the F1-F11 do not show up in the "Configure Shortcuts" dialog (e.g. F4) (gissi)
* <s>Inconsistency (IMHO): F4 in dolphin behaves different than in Konqueror (terminal panel vs. terminal in new window) (gissi)</s>
** I've moved this entry to the Konqi-issue-list, as the Konqi behavior should be fixed (Peter Penz)

* It can only configure mimetype associations individually via properties on a file, and later clicking on a small settings button. To configure mimetypes globally, and not file related, it has to be done with Konqueror settings, as there is no such entry in SystemSettings. IMHO Dolphin or SystemSettings should also get the Konqueror's File association settings panel. (q3xr2).
** I Completely agree! This settings should be accesible even from the systemsettings! (FiNeX)
** {{bug|151781}} -- [[user:Pino|pino]]

* Dolphin don't exec the shell scripts,of course syntax is good and those scripts has correct perms,double click and open scripts with kwrite instead of exec it.(Meskalamdug)
* Dolphin don't open the asc files,kgpg "small icon" appear but kpgp don't run for ask pass and decrypt the file,same thing on konqueror (Meskalamdug)
* Dolphin does not show (unless you manually refresh the view) changes to a files:
- Modification time 
- Permissions 
- Size (e.g. when watching a folder where a file is being downloaded) 
(and obviously, neither does Konqueror), leading to stale information being presented as current. This is a feature that used to work way back in KDE3.3. I think we have all the infrastructure now, so it would be nice to see this regression fixed for KDE4 :)
** Yes, this is even the case if you leave a folder and enter it again. All those values seem to be cached and are therefore displayed incorrectly. I don't think that this is acceptable for KDE's default file manager. (mutlu_inek, rev. 752605)
* Cannot edit Volume names in "Places" sidebar in Dolphin, while it's possible for folders. (Tyl3r)
* <s>When you rename any file or directory to something _really_ long (I tested with >70 letters), dolphin behaves weird directly after renaming. When you leave and re-enter the directory in which the file/directory is, it is painted correctly. (gissi, confirmed by jstubbs and teprrr)</s>
** Works fine for me. (mutlu_inek, rev. 743425) I think this is a very old bug. If you still have it, please undo the strikethrough format. mutlu_inek (rev. 751696)
* Trash icon should change between trash is empty or full, so we know if the trash folder have some file or not inside it. (teddy)
* In konqueror 3.5.x you can navigate files using the keyboard arrows. In dolphin you can do it too, but when you reach the last icon of a row, pressing "right" button doesn't select the first icon of the next row instead. In konqueror you can do it (in the 3.5.x). See {{bug|152985}} (FiNeX)
* <s>File names in Dolphin don't use the global KDE colour settings and can be hard to read. Upon further testing I found that the right colour was used after Dolphin re-starts. Still I don't see why everything else in Dolphin changes immediately according to colour changes and not the file names. (open_)</s> (has been fixed [ereslibre]) (image removed to save space as the description is detailed enough [open_])

==== Plasma ====

Critical issues:

* can't move panel plasmoids. (logixoul)
* <s>MinimizeAnimation doesn't animates correctly to the taskbar, with Kicker it works fine (Plasma should tell KWin where the taskbar-entry is) (boom1992)</s> Fixed. (mutlu_inek, rev. 746964)
* <strike><s>Colorpicker and Kickoff plasmoid don't have context menu, so they can't be removed. (TunaTom)</s></strike>
** context menus are going to be replaced by hover-action-icons (ivan)
*** It's very anoying (and ugly), that the hover-action-icons show up whenever you hover a plasmoid, they should only show up when a button is hold too, e.g. ALT (yojoe)
**** Right-click on the desktop and select "lock widgets" so you won't have this problem anymore (Tyl3r)
** Lancelot now has context menu and is (re)movable (emilsedgh) patch already being reviewed on panel-devel
* If you move the mouse too quickly over a large plasmoid, it happens that the plasmoid doesn't receive or process the mouse-out event, which causes the hover-options frame + buttons to stay there for ever. Unless you hover the plasmoid again, wait some seconds and move the mouse pointer off the plasmoid. (yojoe)
** I can confirm this. (mutlu_inek, rev. 743425 and 745228)
* The date format is not affected by the settings in KControl.<JRT>

* Configuration dialogs do not appear on the current desktop, they only do in the desktop where plasma has been started on. (ruphy)
*When selecting a background image the file dialog blocks all of plasma (fregl)
** I can confirm this. This includes even plasma applets on the panel. (mutlu_inek, rev. 743425)
* <s>When one drags a file/folder from dolphin to the desktop, and tries to resize it _a lot_, the plasmoid disappears.</s>
** It seems to work fine for me. Maybe you dropped the plasmoid off the screen? (mutlu_inek, rev. 743425) I simply can't reproduce this. (mutlu_inek, rev. 746964)
* Plasma crash when dragging a file icon onto the desktop. First time this happened the background and KickOff disappeared. I deleted the .kde4/config/plasma* files and caused the same crash, but second time the background and KickOff survived. Backtrace from crash - http://www.pastebin.ca/797047 (open_)
* Plasma crash upon closing 3D Earth Model (with no direct rendering) backtrace: http://pastebin.ca/797306 (scroll down for crash handle info) (kakalto)
** Another plasma crash upon closing the 3D Earth Model, or rather closing the widget that told me I didn't have the necessary OpenGL shaders. I had rotated the widget before closing it. Backtrace: http://pastebin.ca/799330 (open_)
* Plasma crashed and didn't return when trying to close the Lancelot applet. Also the Lancelot applet wasn't wide enough when it appeared to show the whole applet's contents. Unfortunately there was no crash dialog window for a backtrace. (open_)
** I can confirm this. Plasma crashes and leaves me in a white, empty and unusable screen. (mutlu_inek, rev. 743425)
* Sometime the digital clock in the panel disappear but it reappear when i move the mouse over it
http://img122.imageshack.us/img122/9417/plasmaclockhu3.png
* Panel is half hidden on certain xinerama setups. http://images.smileaf.org/img:b1abe8ded856571ed771c105c977dc8d.png (smileaf)
* Plasma crashes when clicking on a taskbar element while the window's info popup is being displayed. (lucianolev, using Kde4Daily, rev. 752454)

Unprioritized:
* The network plasmoid does not automatically select the active network connection (It uses eth0 by default, but I use wlan0 mostly) (mbiebl)
** A list of physical devices (Solid?) would be nice here, but it should be also possible to select a userdefined virtual interface (like tunnel devices). (eliasp)
** Even when I change the device to eth1 manually (eth1 is my net interface), it reports "not connected" after applying (kakalto)
** <s>It simply does not work for me at all. I use eth0 (and it is correctly set to it), but it reports "disconnected". (mutlu_inek, rev. 743425)</s>
**** It works for me if I use the new Intel wireless iwl3945 driver. This driver assigns a wlan0 interface. If I use the old ipw3945 driver, then I get either eth0 or eth1 as my wireless interface and the plasmoid does not work at all. (mutlu_inek, rev. 745228 and 746964)
***** Still doesn't work here (eliasp, rev. 746127)
* The Lock/Logout Widget has rectangular buttons -- should have square? <strike>IAC, icons should be centered on buttons.</strike> <JRT>
* notes applet should be resized when the text is bigger that current size (emilsedgh)
* Further to the above: the "Note size" configuration option for notes appears to be non-functional.
* The dictionary plasmoid doesn't show the results. (Mogger)
** Looks like fixed in r732655, shows the result, but first changes the box with animation, then changes the result text, also its a bit slow (emilsedgh)
*** The plasmoid works really well for me. emilsedgh, are you sure it is not a network connection issue for you? Everything in reasonably quick here. (mutlu_inek, rev. 743425)
**** My connection is slow.this is why this looked slow to me.but the problem is still there, when i hit enter, the animation executes, but after a few seconds the text inside it gets changes
*Is there a way to reset the orientation of a plasma applet I have rotated? Would be nice if you could rotate an applet in predefined steps (e.g. 45°) by holding a key (e.g. Shift) like it is common in graphic editing applications. (yojoe)
* <s>It should not be possible to move plasma applets off the screen. There's no way to ever get them back! This might result in active applets consuming resources, the user is not aware off, because they were moved off-screen by accident. (yojoe)</s>
** <s>I second this. Alternatively, they could be at least accessible via a list or smth. (mutlu_inek)</s> This is resolved by Chani. The "Add Widget" dialog now shows running plasmoids which can be summoned back to the center of the screen. :) (mutlu_inek, rev. 746964)
*The "Widgets I Have Used Before" filter does not work (in the Add Widget dialog box). (yojoe)
<strike>*Weather applet, configure --> search for auckland, comes up with empty "found places" dialogue for BBC weather service. Other weather services come up with "the place auckland is not valid. The data source is not able to find this place" (kakalto)</strike> You should see two places for Auckland now. The other behavour is not a bug. he other data sources do not know about Auckland :-) (spstarr)
*The "show desktop" applet don't work (Meskalamdug)
Glitches in playground:
*Welcome to KDE widget causes graphical glitches [http://mrk.homelinux.net/krush/welcome.png] and crashes plasma when removed[http://mrk.homelinux.net/krush/welcome.backtrace] with kDebug output "Plasma::LayoutItem::setLayout: layout removed from under us. expect crashes". (All other widgets behave normally)
* When an app has a show/hide tray icon (like Amarok, KMix etc.) and their window is not-maximized, each time you hide/show the app by clicking the tray icon, it's window is drawn about 20px lower, this stops when the panel finally gets in it's way. (dkarlovi)
*If you right click on a task in the taskbar, there is a paint issue if you hover over "Advanced" or "To Desktop".
**Can't see that here. Seems to be fixed. Can someone confirm? (amp)
* In the Taskbar, the window icons for many non-KDE apps such as YaST, acroread are corrupted.
* Hardware info plasmoid shouldn't use lspci to get GPU info as this is located in /usr/sbin on some systems. (smileaf)

Silly:

* Analog Clock: add text & seconds indicator. Change size to 400. Is so SLOW that it easily skips 3 seconds per redraw! (Core2 Duo 2.20GHz, Quadro FX 570M, nvidia binary drivers, Thinkpad T61p) (BCoppens)
** is this the equivalent of "it hurts when i do this, doctor?" ;)
* <strike>Time Zone list should be redundant in configuration since the TZ should be set in KControl. All that is needed is an option to display it. Note, I think that this is the standard timezone list. If what is wanted is an option to display a TZ other than the user's TZ, this should be a separate context menu item. <JRT></strike>
** of course you need a list of timezones what if you want to show timezones other than the one you are in or extra ones set elsewhere in kde?
**What about UTC+ and UTC- Regions avaliable in the timezones to pick from, i hate to search for a "close" city if I know perfectly what UTC zone I want.
**Why not adding a 'quick filter' line to the TZ select dialog like it's available in the dialog for adding plasma applets. Would make it much more faster and easier finding the needed city/location. (eliasp)
*When I logout of a KDE4 session and relogin again, all plasmoids I had ever added are instantiated again, even the ones that I closed in the previous session. (yojoe)
*When I logout and relogin to a KDE4 session my plasmoids are not scaled and rotated like I left them in the previous session. (yojoe)
*If i change the plasmoid size as soon as i leave the plasmoid area the size gets back to its "normal" size, and the position change dramatically (I can't really say how the position change). (Carutsu)
* The 'Disk Monitor' applet seems to have some serious problems retrieving the free disk space. Isn't it possible retrieving the free disk space from solid (eliasp)?
http://eliasprobst.eu/~elias/stuff/screenshots/kde4-issues/dolphin-plasma-free-diskspace.png
** On mine I have a partition with an unknown name and 16,777,216,0TiB All other partitions have the correct size. (smileaf)
* When the Fifteen Puzzle is resized the pieces inside remain the same size and the puzzle itself remains it's original size inside the larger widget rendering resizing pointless (open_)
* The settings buttions: Add Widget, Zoom in, Zoom out.. is too willing to hide. If you put your cursor between the buttons, it'll go to hide, then open up over and over and over... (smileaf)

==== Plasma - Kickoff 'Start Menu' ====

* <s>leave -> logout opens a dialog with several options, instead of logging out or asking for confirmation - ({{bug|152486}}) (fred)</s>
** You can change this behaviour in systemsettings. Should be default in 4.0 (amp)
* <s>Unable to resize the kickoff menu. (mbiebl)</s>
** <s>I confirm it. (FiNeX)</s> Right click opens a context menu now. (mutlu_inek, rev. 752605)
* <s>Kickoff opens konqueror when clicking on an entry under "My Computer". (mbiebl)</s>
** <s>Seems to be fixed... Can anyone confirm that, please? (r 735451). (frank95com)</s>
*** <s>confirmed. (r 740861) (kakalto)</s>
*** I still get konqueror open when clicked storage device under "My Computer", building KDE from SVN November 28.
**** I still get konqueror, too. (mutlu_inek, rev. 743425 and 745228)
* When opened by clicking on a link in "Storage" for example, Konqueror shows the contents of "/" in an unnamed tab. Right of that tab is another one showing the correct location. If you click that tab, konqeuror crashes. (goliath23)
* Kickoff: Clicking the applications tab, when the tab is open should return it to top-level.Current catalog-memory is a good feature however, so keep that aswell. (eirik_)
* Kickoff crash plasma desktop after open application/desktop(Meskalamdug)
** If this is referring to the crash upon opening utilities->desktop, it is a qt bug which has been fixed in qt-copy and presumably upstream as well (jstubbs)
*** No problems with new qt-4.3.3 (Meskalamdug)

*German umlauts ("Ü" and such) are not properly displayed in menu items if they occour at the beginning of a word. This is the case in Development->Translation (Entwicklung->Übersetzung) which is "Ubersetzung" then. If the menu item is chosen, the title of the next page is correctly written as "Übersetzung" but the menu items again are "Ubersetzungswerkzeug" and such. {{bug|153995}} ([[User:Icwiener|Icwiener]] 13:51, 17 November 2007 (CET))

*Plasma crash when clicking on a recently used item from kickoff - attached backtrace here: http://pastey.net/77802 (null__)

*Switch user from kickoff exec "launch application" (Meskalamdug)
** Confirmed (kakalto)
** Confirmed (mikkoc)

* Handling of storage devices needs some loving:
** When clicking on an unmounted storage device, nothing happens (eliasp)
** When right-clicking -> eject on a device that is mounted by another user nothing happens - KDE3.5/Dolphin4 displays at least the HAL error message about being unable to umount it due to missing privileges. (eliasp)
** The bars representing the disk usage should have a little more space on the right side. They currently seem to be cropped: http://eliasprobst.eu/~elias/stuff/screenshots/kde4-issues/kick-off-storage-devices.png (eliasp)
* When scrolling, the category name should stay on top instead of scrolling together with the content:
http://eliasprobst.eu/~elias/stuff/screenshots/kde4-issues/plasma-kickoff-category-name.png (eliasp)
* <s>The Kickoff button does a hover animation the first time I hover it, but then the new picture stays. (amp)</s>
** Not reproducible any more. (amp)
* I had an issue where the menu would always switch to the Leave section almost immediately after my mouse rolled over any of the other icons for different sections. When I logged back in it was back to normal (open_)
** Does "I had an issue" mean it is not reproducible? (mutlu_inek)
* Kickoff : clicking "LEAVE" tab -> Shutdown and restart menu item no have icons (teddy_)

==== System Settings ====
* Missing "get root rights" button on pages like Date/Time, thus its impossible to change such settings (apaku) (#151669)
** Confirmed by FiNeX, Tyl3r and mutlu_inek (rev. 743425 and 745228)
* <s>no settings to be changed for keyboard shortcuts - everything is empty (nixternal, mactalla) (#135282)</s> Fixed. (mutlu_inek, rev. 752265)
* <s>When clicking e.g. "Appearance", the System Settings window doesn't get resized. This causes very ugly (horizontal and vertical) scrollbars (gissi) (#153283)</s>
** <s>Layouts are awful in general, Regional & Language for example is unusable. (annma) Improved Language tab svn r738336 (annma)</s> This is much better now and going to be polished a bit more thanks to Aurelien. (mutlu_inek, rev. 752265)
* <s>Default size for the text beneath the icons is too small. I see stuff like 'ppearanc' instead of 'Appearance' and 'ccesibilit'. Some other texts are wide enough, like 'Splash Screen'. (BCoppens) (#153285)</s> Fixed. (mutlu_inek, rev. 752265)
* Changing the style to Oxygen changes all windows, EXCEPT the System Settings (BCoppens) (seems to be every other style change takes effect: #135287)
** I have the oxygen style also in systemsettings. Try to check again, please. (frank95com)
*** Hmmm, now that the default style is oxygen and I try to switch to good old plastik, I have the same issue: everything switches to plastik except the system settings. Strange (BCoppens)
*** I can confirm it: when you change the style and click to "apply" the style is not applied to the system settings window. (FiNeX)
* systemsettings has no menu - there is no way (for normal users) to start the help for it. (fregl)
* The systemsettings toolbar can be hidden but there is no way to get it back. (fregl) (#151667)
* I don't find where to set the default Spelling dictionary (annma)
** Missing Spelling module [[User:Bille]]
* Need a real fix for [http://websvn.kde.org/trunk/KDE/kdebase/workspace/systemsettings/kcmultiwidget.cpp?r1=709212&r2=737094 http://websvn.kde.org/trunk/.../kcmultiwidget.cpp?r1=709212&r2=737094] which is only a workaround. Uncomment the Q_ASSERT to see the problem.
* The string on the "Accessibility" Info tab is too long. It cause the window be too wide. (FiNeX)
* The "Search" LineEdit is malplaced if the toolbar is moved to the sides.
* Every time i log in,kde create in $HOME/.kde4/share/config a gtkrc-2.0 file wich overwrite my gtk settings(colors,theme),text file said " If you do not want KDE to override your GTK settings, select Appearance & Themes -> Colors in the Control Center and disable the checkbox "Apply colors to non-KDE applications" ".But this checkbox is already disabled. (Meskalamdug)
* <s>If you click on Notifications and then System Notifications there will be no events listed within the table, though the event source is Kopete leading a user to believe that Kopete has no events. If you click on the drop down Event source list and click on Kopete the events will be shown. Either start with a 'None' event source option or list the sources of the application when System Notifications is clicked. I prefer the None option as it will load faster and chances of a user editing the event sources of the first application in the list are slim (open_)</s>
** Fixed in System Settings (r746614 by me), cannot reproduce with Kopete. -- [[user:Pino|pino]] 18:21, 9 December 2007 (CET); Yes, this is fixed. (mutlu_inek, rev. 752265)
* Regional & Language doesn't use kde color scheme
http://www.uploadgeek.com/uploads456/1/ss.png
* <s>The "general" tab should precede (be left of) the "advanced" tab. It also should have the focus be default. (mutlu_inek, rev. 752605)</s> Wow! Someone is doing an amazing job: fixed in SVN commit 752816 by ereslibre. (mutlu_inek)
* <s>I guess this is more of a question to think about: should the system settings gui should honor its own settings, i.e. whether to open programs (that is, KCMs) with single or double click? (mutlu_inek, rev. 752605)</s> This has just been resolved by ereslibre in SVN commit 752784. (mutlu_inek)

==== KWin ====
* KWin tryes to activate compositioning on my VIA card, and thus, freezes everything , no backtrace since everything hangs. (tomaz)
* Windows are not fully redrawn when minimizing and then restoring with OpenGL compositing in use (jstubbs)
** I've rebuilt with qt-copy and left a week between testing, but this seems partially fixed? my only issue now is that the last frame drawn is sometimes a transitional frame, when either minimizing or restoring. iow, the window is shown smaller than it really is upon restoring (until a paint is forced) and it is also sometimes still visible when minimizing (again, until a paint is forced) (jstubbs)
* the compositing KCM should provide an easy way to enable the COMPOSITE extension (logixoul)
* Sometimes (tested with Konsole, X.org 7.3, latest nvidia drivers and a Geforce 5900XT), the clicked menus are not displayed and KWin crashes. Backtrace : [http://rafb.net/p/zmYj1980.html] (idem)
**Backtrace is not there anymore. rafb removes pastes after some time. Please ude pastebin.ca ([[User:Icwiener|Icwiener]] 03:42, 10 November 2007 (CET))
* After a while the alt-tab window list is completely missing though I can still switch between windows with alt+tab (apaku)
* alt+tab only allows to switch between windows on the same screen in a multihead setup, its impossible to activate a window on another screen (though its on the same virtual X11 desktop) (apaku)
* KWin does not detect compositing ability on my pc with a GeForce 7600 GS (driver version 100.14.19) (goliath23)
** Are you sure your KWin has compositing support compiled in? Desktop effects kcm now shows the reason why compositing cannot be enabled, please check this (rivo)
* 'Scale In' effect also scales in Menus and Dropdown boxes from the 'middle' of their target area, this is ugly. Either don't do that for such windows, or let them scale in from their topleft corner (BCoppens)
* Alt+Shift+Tab for backwards scrolling through Alt+Tab shortcut is not assigned, but I can't remember if this was the case in KDE3 as well or not... (BCoppens)
** Now when I click Alt+Shit+Tab my keyboard doesn't respond anymore and I don't know how to get it back, the only solution is to logout with the mouse , which still works. (q3xr2)
*** I filled a bug about it: {{bug|153211}} (q3xr2)
* Moving windows with "Display Content" turned off does not display an empty frame. (using an OpenSource driver)<JRT>
* Alt+Tab crashes KWin here, when pressed too fast several times in a row. Backtrace: http://pastebin.ca/767870 ([[User:Icwiener|Icwiener]] 03:42, 10 November 2007 (CET))
* Composite effects make video playback really slow(Meskalamdug)
** Maybe you should use vo=gl in your settings. I use it in my /etc/mplayer/mplayer.conf and it works fine. (amp)
*** Using vo=gl..same thing,is slow (Meskalamdug)
* When switching between users (alt+f7 and alt+f8) the entire screen in black until I force a redraw by clicking somewhere (jstubbs)
* KWin 'locks up' when trying to create a screenshot using ALT+Print. Now you're not able anymore clicking things - the only thing you can do now is moving windows around. It's like ALT is constantly pushed. The only way to get rid of this is restarting X (CTRL+ALT+Backspace is due to the lock-up not possible). You can only click things when first pushing RMB, keeping it pushed, then LMB too. While keeping RMB down, you're able to click things. Now you can quit the session using ''Logout'' from the Kickoff menu. (eliasp).
** Confirmed here. (q3xr2)
** Confirmed by me, too. However, the problem is slightly less serious for me since I can still open apps from kickoff, close apps and even log out. But I cannot use the keyboard, any menus or click any buttons. (mutlu_inek, rev. 743425 and 745228)
* kwin does not maximize windows corretly on my MacBook (intel xorg driver). See https://bugzilla.novell.com/show_bug.cgi?id=335530 for more information. xrandr output is at http://pastebin.ca/796053. _fm_
* If composite is activated when you first load a menu it's first displayed as an untuned TV, i mean the picture gets all messed up, then it gets normal, that happens only the first time, the image is cached later (i guess) and doesn't happen if you reopen it. I have an Intel chipset so that shouldn't be the problem. (Carutsu)
* <s>Show the windows (ctrl+f10) then writte something, the icons on the lower right corner of the window gets blank. (Carutsu)</s>
** Fixed in revision 749354. (Carutsu)
* 'Show Windows'/'Expose' should never scale windows bigger as the actually are. Makes them looking blurry and ugly. (eliasp)
* After changing the cursor theme the cursor shape may be wrong when resizing by dragging the corners. {{bug|153683}} (alecs1_)
* The Blur compositing plugin causes the screen to go black except for a observable(and moveable) mouse on a ATI Xpress1100 with the 7.11 (AIGLX) drivers . (nosrednaekim)
** The Blur compositing plugin works for me, but causes artifacts when for example switching between desktops (NVidia 7600 with proprietary driver x11-video-nvidia-1.0.9631-0.1) (shaga)
* Windows can start hidden in certain xinerama setups. example: smaller left screen and positioned lower than the right. (smileaf)
* Windows don't maximize to 1 screen on xinerama setups. (smileaf)

==== Konqueror ====
* <s>Autocomplete in Konqueror forms doesn't allow to type words starting with the same letter of a previous entry. Example: if you search the word "wall" on google and then you try to search for "wireless" it doesn't work. (Tyl3r)(confirmed jpwhiting, jakub)</s>
** <s>Confirmed by me, too. When Konqueror displays the autocomplete hint, I cannot enter or delete more than one character. (mutlu_inek, rev. 743425)</s>
*** <s>You have to click again at the input field for each of the following characters until there are no more autocomplete suggestions. It seems the focus is changing to the autocompletion suggestions as soon as you type something. (eliasp)</s> This has been resolved. (mutlu_inek, rev. 747385)
* <s>Website http://kriptopolis.org it is really bad rendered, however it is fine with Konqueror 3.5.7. (q3xr2)</s>
** <s>Confirmed by me. (mutlu_inek, rev. 743425)</s> Works now. (mutlu_inek, rev. 746963)
* After changing the arrangement of the address bar while several tabs are open, switching to another tab deletes the changes or messes up konqueror so that it needs to be restarted. (r743536)(glenner) and (mutlu_inek, rev. 743425)
* Nothing in View -> Sort By, Additional Information, <s>Panels, Navigation Bar</s> submenus (yuriy)
**Confirmed here(SSJ_GZ).
**Confirmed here for the former, but no panels, navigation bar submenus (kakalto)
* <s>Nothing except "home folder" in home folder sidebar (yuriy) (mutlu_inek, rev. 743425)</s> The side bar is populated since quite a while now. (mutlu_inek, rev. 751696)
* $HOME in the desktop entry doesn't seem to get evaluated (yuriy)
** Error is The File or Folder $HOME does not exist. This also mean we cannot get a tree view rooted at ~(SSJ_GZ)
* Some favicons do not appear in Konqueror's nav bar to titlebar. google.com and kubuntu.org works. kde.org, cnn.com and slashdot.org do not work. (JustinNoel)
** Bug #153049 (Quique)
* pressing ctrl+a when focus is on addressbar selects whole webpage instead of the text that is written in the addressbar (only on webpages: khtmlpart?) (emilsedgh) (mutlu_inek, rev. 743425)
** The same for text input fields in the displayed page. CTRL+A selects the text of the page, not of the input field. (eliasp)
* In file management mode it can't show hidden files, it doesn't have this option in the View menu, neither there is a shorcut available. (q3xr2)
* In HTML forms (such as the textbox to edit this wikipage with, or the username box), the initial fontsize is small. Once I click on the form, the font suddenly enlargens. Especially annoying with this editbox, since the place where you think you clicked changes after fontsize change (BCoppens)
* <s>Clicking on a link to an in-page 'tag' (the a href=#tag thing, like there are lots of in the index of this wiki page), results in konqueror showing the 'Drag link' mouse cursor (BCoppens)</s>
** <s>Yes, this really disturbs the browsing experience since no interaction with konqueror is possible until the mouse is clicked. (mutlu_inek, rev. 743425)</s> Fixed. (mutlu_inek, rev. 751696)
* With Konqui becoming webbrowser as primary task, it would make sense to redesign the start page altogether and remove stuff like Storage media, Trash etc. Show something like "Search the web" which points to a search engine, like Google, yahoo,...
* <s>(Different from the one above) Start Konq. Enter '~'. Make a new tab (CtrlShift+N). Enter '/'. Switch back to the first tab. It's caption suddenly changes from '/home/kde4/' to 'kde4'! Switching to the second tab, removes the '/' and makes that tab nameless) (BCoppens)</s> This seems fixed. (mutlu_inek, rev. 743425)
* Tabs are nameless if in file browsing mode and the root folder is displayed. (mutlu_inek, rev. 743425)
* Printing a html file from konqueror. The "HTML Settings" tab has an odd layout. It seems to miss a proper border. (mbiebl)
* The search button in the upper left corner of techbase.kde.org does not draw correctly (no text). (glenner)
** Not only that, also some other buttons. (frank95com)
* <s>For some pages the text in buttons is not shown in full, for example gmail. (talavis)</s> This works well now. (mutlu_inek, rev. 743425)
* The height in konqueror address bar is too small (sergiof)
* Flash animations don't show in webpages (ex: www.motorcyclenews.com).Konqueror has the right path to flash plugin (sergiof)
** The flash plugin doesn't work here. (auxsvr)
*** I confirm,flash plugin doesn't work atm(Meskalamdug)
*** We can confirm that flash doesn't work either while it's well configured (carutsu and mutlu_inek (rev. 743425))
**** Flash works fine now (Meskalamdug)
***** Not for me. It is configured correctly and works in Firefox and Opera. I use version 9.0.48. (mutlu_inek, rev. 751696)
* Crashes when activating adblock->hide filtered images (see {{bug|152107}} ) (TunaTom, reproduced by shaga)
* Drag and drop a file/URI from konqueror (web browsing), konqueror (file browsing with the dolphin part) and dolphin to a textfield in a webpage in konqueror doesn't work. Bug #152126 (FiNeX)
* The close buttons in the tabs don't work. (auxsvr)
* (wish) add an accelerator to "Save image as" on popup menu in khtml. See: http://pastebin.ca/768638 (FiNeX)
* Alt text frames are not large enough to show all of the text, e.g. "Comic 2" is displayed only as "Comic ". Also happens in kde3. (hdh)
* If you have a very long shortcut in the "Web shortcuts" configuration dialog on konqueror, the window will be resized over 1024px. If an user have such resolution he cannot view all the window. The combo box for the "default search engine" is resized for displaying all the text and this make all the window resize. Actually there is a schortcut called "Great Dictionary of the Catalan Language" who make this happen. See bug {{bug|152374}} (FiNeX)
* URL editor does not show browsing history when dropped down. It only shows the current page's URL. (JustinNoel)
* Import bookmark of mozilla(esported as mozilla bookmarks from konqueror 3x) doesn't work,no replace,no new folder (Meskalamdug)
* Inconsistency (IMHO): F4 in Konqueror behaves different than in Dolphin (terminal panel vs. terminal in new window) (gissi)
* Drag and Drop in dolphin part in konqueror doesn't work. See {{bug|152706}} (FiNeX)
* Edit bookmark crash,no backtrace generated (Meskalamdug)
** Now works fine (Meskalamdug)
* Copy then paste an existing bookmark crashes it. Backtrace: http://pastebin.ca/796786 (kakalto)
*Error loading dolphin part. By clicking in konqueror on systemsettings:/ ( in the main page.. "conqueror your desktop", i get this error:
There was an error loading the module Dolphin Part.
The diagnostics is:
QLibrary::load_sys: Cannot load /home/KDE4/kde/lib/kde4/dolphinpart.so (/home/KDE4/kde/lib/kde4/libdolphinpart.so: cannot open shared object file: No such file or directory)
I click ok and then:
There was an error loading the module Cervisia.
The diagnostics is:
Library not found
I click ok and then:
There was an error loading the module kdesvn.
The diagnostics is:
Library not found
i click ok and then:
There appears to be a configuration error. You have associated Konqueror with inode/directory, but it cannot handle this file type.
Systemsettings don't open.. if you try to launch another konqueror those error appears. ( The file dolphinpart.so exist and is placed in the right directory. The file libdolphinpart doesn't exist ( and it has never existed )). ( LinusV2 )
** I don't get this error; I get "An error occurred while loading settings:/: Unknown settings folder (kakalto)
* Konqueror doesn't show the ''Add RSS Feed to Akregator'' button in the lower left corner when a website provides a feed (eliasp)
* Konqueror crashes while trying to go to /home it crashed exactly at /hom (when there were no other choices I guess) backtrace http://pastebin.ca/796683 i tried several times with same result. (carutsu)
**It looks like some problem in text completion in the URL bar. It happens very often although I did not find a way to reproduce it (ergroot)
* If you open konqueror and immediately split the window in two (CTRL+SHIFT+R), the right pane loads "about:konqueror", instead of cloning the current page (expected and normal behaviour at any other path) (kakalto)
* Konqueror doesn't split windows evenly (kakalto)
* If you split the window left/right, then click in the left pane, split the window left/right again, then close active view once (in either of the left two panes), it resizes one of the remaining panes to full window size, hiding the other pane. (kakalto)
** This also happens with the upper two panes if you split top/bottom twice, or with combinations of split top/bottom and left/right
* <s>"Storage Media" link in konqueror broken (kakalto)</s> http://img.photobucket.com/albums/v221/Kakalto/Screenshots/media_notsupported.jpg media ioslave was removed in kde4 (smileaf)
* konqueror crashes on exit, backtrace: http://pastebin.ca/796825 (kakalto)
** Had the same thing happen here, backtrace: http://pastebin.ca/799318 (open_)
** If i try to open a unexistant kioprotocol, konqueror crashes on exit but only on a kde4 session, from kde3 it doesn't, backtrace: http://pastebin.com/f7729b262
** same here. I only get the crash if I've visited an external website - if you open local html pages only and then close there is no crash. (matt__)
** me too. But if I launch Konqueror with Konsole and with an URL (for example konqueror www.kde.org) it doesn't crash on exit (toma222).
** seemsU** The fixed now rev 746168
* <s>If I have some addresses in browsing history and start to type one, eg: google.com, and then change so something else (eg: typing goo then an S or some other letter) it brings konqueror to a crash. Maybe something related with the combobox?</s> (jcalado)
* Copying files to a samba location stalls for anything more than a few hundred KiB (No problems under konq3) (kakalto)
* <s>If I open a link in a new tab in konqueror by pressing the middle mouse button, the address bar of the former pages and its thumbnail change to the html address and the thumbnail of the new tab (this does not happen when right-clicking the link and choosing "open in new tab"). (mutlu_inek, rev. 743425)</s> Works well now. (mutlu_inek, rev. 751696)
* if I open the link http://techbase.kde.org/Contribute/Bugsquad/KrushDays konqueror crash. Backtrace: http://pastebin.ca/805725 (mancausoft)
* The bar at the bottom below where the scrollbar appears is inordinately large for what it displays.
* A KDE developer's blog does not render legibly at all: http://www.bramschoenmakers.nl/ (mutlu_inek, rev. 747385)
* After starting a download from konqueror,select folder,kget crash (Meskalamdug)
* This url http://sourceforge.net/project/downloading.php?group_id=46509&use_mirror=dfn&filename=openrdf-sesame-2.0-rc2-onejar.jar&54070129 crash konqueror (Meskalamdug)
** I can confirm this. There is a really bad backtrace here: http://pastebin.ca/829287 (mutlu_inek, rev. 751696)
* <s>Konqueror provides View->enlarge Font and View->shrink Font. If I select 75% in the shrink Font menu, the enlarge Font menu show 100% to me. So I get the impression the font size I am looking at is 100%. Even worse I am not able to select 100% in the enlarge View menu again. I think the two menues should be aware of each other and indicate what the current font size really is. For bugreport see: http://bugs.kde.org/show_bug.cgi?id=154121 (confirmed: TunaTom r748790)</s> Fixed by ggarand in commit 752352. (mutlu_inek)
* Wish: add reload/stop button instead of the two buttons, add a button for replacing the menu bar (like this https://addons.mozilla.org/en-US/firefox/addon/3722 ) & create config for the look of the tab-bar (position, toogle add & close tab buttons ...)

==== Kate ====
* Endless loop when executing the following steps: create a new file, save it with the .py extension, press enter, up, closed parenthesis, enter (paolo)
** I can confirm it, and I'll take a look at it. (mstocker)
** I have a fix for it, but I'm not sure if doesn't cause other problems: http://pastebin.ca/778318 (mstocker)
*** see http://lists.kde.org/?l=kwrite-devel&m=119789215123897&w=2 (tfry)
* Word Completion - flickering suggestion popup when mouse pointer is inside the popup area. ([[User:Hilefoks|Hilefoks]]) <s>Works now. (mutlu_inek, rev. 743425)</s>
** I still have this bug. ([[User:Hilefoks|Hilefoks]] rev. 748314)
*** Do you use compositing? Which graphics card do you have? And which drivers do you use? (mutlu_inek, rev. 751699)
**** With and without composite and also when I run kate in KDE3. I have a NVidia GF 8800 and using the binary driver. ([[User:Hilefoks|Hilefoks]])
* <s>Ctrl + a only selects everything up to the cursor (csh)</s> Works now. (mutlu_inek, rev. 743425)
** <s>I still have this bug. Revision 744890. (Carutsu)</s> Solved in revision 746184.

==== KWrite ====
* traceback after "file has changed, what will you do?" and clicking reload - however, i couldn't reproduce it. http://pastebin.ca/778564 (jstubbs)
** I used this feature a lot and it never crashed on me. (mutlu_inek, rev. 751699)
* kwrite word completion plugin (This problem is also highlighted in the KATE section) - enabled, when completing a word the popup flickers madly ONLY for the first word, but works for completion for the next word onwards. Attached kwrite output and bt - http://pastey.net/77535 and http://pastey.net/77536 - hmm dont think the bt is of any use (null__)
** Can you still reproduce this? It works perfectly for me. Do you use compositing? Which graphics card do you have? And which drivers do you use? (mutlu_inek, rev. 751699)
* <s>If you open a text file with kwrite, click on a line and press CTRL+A to select all, visually it only displays that line and all prior lines being selected, but if you copy to clipboard, it copies everything. When you switch programs or maximise kwrite, it refreshes and shows all as selected. Also affects Kate. (kakalto)</s>
** <s>We could fix this by calling repaintText(false); in KateView::selectAll() after setSelection(...)... ? (mstocker)</s>
** I was able to confirm this a week ago, but it is fixed for me now in r746830 (firmo). Same here (uwolfer).
*If i open a binary-text file(for example nvidia-driver) kwrite use all ram and cause a out of memory (Meskalamdug)
** It works for me at revision 751699, could you check again? (mutlu_inek)
*** Still don't work,preview ok but when i try to open the files i have the memory problem (Meskalamdug)

==== Login Manager KCM ====
* There are numbers on the tabs (yuriy)
** yes - the kcm is too big to have non-clashing letter shortcuts.

==== KFontChooser ====
*It doesn't work correctly for the bit mapped fonts Fixed[Misc] & Fixed[Sony] which come with X11 are the best example of this since they might be used in Konsole. This is mainly a Konsole issue. <JRT>
**There should be only 2 sizes of Fixed[Sony] which works correctly in KDE3 it displays only two sizes. I'm not 100% clear on how this works if you have a screen resolution other than 75 or 100, but xfontsel lists two point sizes for 100 dpi: 12 & 17 and this agrees with the KFontSel dialog. But in KDE4 it lists the usual list of sizes from 4 to 64.
**There are several sizes of Fixed[Misc], according to xfonsel they are: 5, 6, 7, 8, 10, 11, 12, & 14. KDE has this fairly close to correct -- close enough that it works OK. It also lists 4 which may be a 75 dpi font and it lists 9 but not 12. Could these be rounding errors? IAC, KDE4 is the same as with Fixed[Sony], it has the standard list of 4 to 64.
**We need to first ask if this is a Qt bug/error as are other font issues.
***The Fixed{Misc} fonts are not a uniform set of fonts and I don't think that there is any way that Qt can deal with this issue.

=== Icons KCM ===
* Forces you to a manual reboot if you try to change icon theme :-) (ruphy)
=== KNetattach ===
* After finishing the KNetattach wizard, it opens up a Konqueror window using the newly created connection instead of Dolphin. (eliasp)

=== Klipper ===
* Not a bug per se but "Clear clipboard History"'s icon (right click in the systray icon of Klipper) is a sand clock, while the methaphor is (i think) reseting history it is just confusing IMHO, couldn't it be the clipboard with an eraser or something? (Carutsu)

== kdeedu ==
==== kalgebra ====
* Crash when entering "t->(1..100,t)" as a 2d graph function (astromme) (backtrace: http://pastebin.ca/796378)
- Fixed (apol)
--> it still crashes here (svn 750124) (pvandewyngaerde ) backtrace http://pastebin.ca/827632

==== KHangMan ====
* After typing an already typed letter, the focus is left on the guess "button", which means I have to press tab to get back to the letter entry field. If we enable the focus back before tooltip is hidden, it means the tooltip has to be hidden when a new letter is entered. (jstubbs)
** annma: intented behaviour is that the input is impossible why popup is shown. To leave the kid the time to understand what he is doing. Messing with the tooltip now seems bad to me. It's a WON'T FIX until we have it tested with kids ;) sorry jstubbs!
* <s>See if the font progressbar can disappear after first run (jstubbs)</s>
** annma: Removing your ~/.fonts/d dustismo_roman.ttf will make the bug go away. The font will reinstall and then it'll be found. Not sure why it happened...
** jstubbs: the above does not work for me
* Test what happens for the fonts when no internet connection (annma)
* <s>Wish: when using the Special chars toolbar, letters should go immediatly in the word or in Missed. Annma is not sure this would work with kids, they maybe won't understand what happens. (jstubbs)</s>
** annma: maybe a config option for KDE 4.1 as we are in feature freeze now.
* Language combo in toolbar does not resize correctly when adding a language with a longer name than those already present. (jstubbs)
* <s>Right-clicking "Type accented letters" does not offer the context sensitive help when the option is disabled. (jstubbs)</s>
** annma: this is from Qt, it's default behaviour for QWhatsThis help.
** jstubbs: Using the "what's this" button from the title bar and then clicking on it gives the help. Perhaps this should be sent upstream? At the moment, it is not clear what the option does or under what situations it would become enabled...

==== Kiten ====
* Searching for "one" takes a long time to process, during which the application blocks without any feedback. (jstubbs)
* "Filter Rare" does not seem to work (jstubbs)
* From the Search menu, selecting Search {with Beginning of Word, Anywhere}, Grade or Strokes does not seem to have any affect (jstubbs)
* Selecting Verb or Noun from the grammatical element dropdown does not seem to have any affect (jstubbs)
* When searching for something that has no results, the results pane continues to display the previous results until a refresh is forced (jstubbs)
* Can't copy text when right clicking on selected text in the results pane (jstubbs)
* Disabling "match only whole english word" still only matches whole words (jstubbs)

==== KBruch ====
* In fraction tasks, the denominators used sometimes exceed the max denominator that is set. (jstubbs) r732343 attempted to fixe it but not totally

==== KGeography ====
* With KWin's dimming of inactive windows, it is difficult to relate the colors signfying right/wrong answers back to the map (jstubbs)

==== KmPlot ====
* <s>Editing function does not work as if Enter is not doing anything (rivo, gissi and idem-kde4) Annma cannot reproduce.</s>
**Note by gissi: For me, only editing a cartesian plot doesn't work, the others work as expected. Don't know wether that's the same for rivo and idem.
***I confirm this too, i also confirm that it is a regression, it worked just fine few month ago (ELV13)
****Should be fixed on r750188 (aacid) (confirmed pvandewyngaerde)
* The cursor disappear when a dialog is open and the mouse go over the plot visualizer section
* zoom in/out buttons do not work (pvandewyngaerde)
* opening the "constants editor" from the "equation editor", does not work before you close the "equation editor" (pvandewyngaerde)

==== Marble ====
* <s>Navigate to Minneapolis (search is quick) and then zoom in until "saint paul" appears. Rotating up and down will now cause the text "saint paul" to jump around. (jstubbs)</s> Works now. (mutlu_inek, rev. 751699)
* <s>In full screen mode, clicking in the right half of the globe doesn't work. It seems that plasma is getting the events? (jstubbs)</s> Works now. (mutlu_inek, rev. 751699)
* Marble has to be restarted for the newly downloaded maps (KHotNewStuff2) to be integrated into the sidebar and therefore usable. (mutlu_inek, rev. 751699)

== kdegames ==

==== Kolf ====
* The colors chosen for the balls are not displayed. They're white (without compositing). (frank95com).

==== Patience ====
* Some graphical glitches in Klondike with compiz enabled(Meskalamdug)

== kdegraphics ==

==== Gwenview ====
* Random crashes when navigating to directories, or when editing the path manually. Backtrace http://pastebin.ca/760077 (luca_b)
* Gwenview is noticeably slower while loading the images than the stable 1.4.2 version (on the same system). It seems that the new version load entirely the image before showing it. Gwenview 1.4.2 show the image little by little that is better for the user experience. See bug report: {{bug|152275}} (mar nov 13 22:40:35 CET 2007, FiNeX)
* In the "view" mode, if the "zoom to fit option" is enabled and the gwenview window is smaller than the monitor resolution, when you navigate through images with "next" and "previous" buttons, the gwenview window will be resized to the max size for displaying the image. See bug {{bug|152276}} (mar nov 13 23:09:03 CET 2007, FiNeX)
* Problems while loading files without having read permissions. For a long description and some examples see: {{bug|152398}} (FiNeX)
* When rotating an image there are sometimes parts of the last rotation still visible and the image doesn't return to the centre of the window.http://img522.imageshack.us/img522/9755/gwenviewrotatecc9.th.jpg (open_)
** Confirmed, using r745387. (lucianolev)

==== KSnapshot ====

* Snapshots are saved with permissions 0600 rather than the current umask (jstubbs)

==== okular ====
* Reviews cannot be removed from the Reviews sidebar using delete key.(lucianolev)

==== Kolourpaint ====
* <s>Fonts look weird</s> Fonts are fine for me. (mutlu_inek, rev. 743425)
* <s>urrent image size doesn't stand out - white on white background</s>

== kdelibs ==

==== Phonon ====
* Can't get any sound to work. Chosen backend is xine. Tried to play an mp3 in juk. juk says its playing, but I get no sound. (mbiebl)
** Have you already tried to configure different main output from kcm_phonon to music category? Changing dev=0 output worked for me.. (teprrr)
* In the Phonon kcm module, dragging of devices in the priority list works, but it is not possible dropping them (eliasp)
** That's a bug in Qt, fixed in qt-copy patch 0194. See also http://trolltech.com/developer/task-tracker/index_html?id=181413&method=entry It still works (IIRC) if you press the SHIFT key while dragging.

==== Oxygen - Style ====

* <s>konsole, Oxygen: the arrows of the right scrollbar are not visible (black on black). (mbiebl)</s> Seems to be fixed. (mutlu_inek, rev. 743425)
* Too little contrast in the window-list from alt-tab shortcut, people with only slight visual problems won't be able to see the difference between selected/not selected (apaku)
* Missing widgets / invisible text in the side bar off application like marble or kalzium
* Close/minimize/maximise/make independant button in title bar and panel qt container are not similar. In panel container when they are highlighted, a square is painted over them. In title bar it is a circle. To get more coherence, both should be the same (square are nicer in my opinion).
* Oxygen window decoration is missing "keep above others" and "keep below others" functionality. (and possibly icons for them, too) (teprrr)
* Tabbar scroll buttons, when the tabs exceed the space available for the widget, are drawn on top of the rightmost tab: [[Image:Kopete_yahooconfig_oxygen_tab_bug.png]]
** Already reported: {{bug|152327}} (FiNeX)
** Fixed on latest revisions (FiNeX)
*** This still does not work for me at all. Does anyone else have this bug, too? (mutlu_inek, rev. 751699)
* There's an obvious flaw in the drawing of progress bars, which is only visible during the first 15% of the progress bar being filled. After a progress bar is filled up to 20% it looks nice. To reproduce, start a large download with Kget for example and you'll notice the flaw. (yojoe)
** Same here (_Brandon_) http://www.uploadgeek.com/uploads456/0/schermata3.png
*** already reported, {{bug|152640}}
*Too litte textbox in konqueror using 1152*864 resolution. The text is cut up and down, same for dolphin
* Konsole tabbar look odd and ugly (teddy)
* Menu mouse-over in menubar still missing (teddy)

==== Oxygen - Icons ====

* Chanel icons in KMix could use some Oxygenification (JLP)
* systemsettings: in Network & Connectivity group every item has the same icon. (teprrr)
* Juk is missing guess tags from filename icon (teprrr)
* A lot of missing icons in kinfocenter (FiNeX)
* List of missing icons with screenshots:
** http://www.finex.org/missing_icons/ (FiNeX)
* No icon in krandrtray on systray (Meskalamdug)
* Some missing icons in Korganizer (Meskalamdug)

==== Nepomuk ====

* When you add ratings/comments to a file through Nepomuk and then you rename this file, the ratings/comments disappear. (Tyl3r)
** Reproducible also for me. ([[User:frank95com|frank95com]])
* Nepomuk won't start, I have enabled it with kcmshell4 kcm_nepomuk but it does not start. Every time I start kcmshell4 kcm_nepomuk, "Enable Nepomuk..." is unchecked again. (Meskalamdug)
** Reproducible also for me. However, according to the Service Manager in System Settings, the Nepomuk Server is automatically started and currently running. Also, Dolphin does not complain about Nepomuk not running. It offers that I can rate and tag files, but the entries are not actually recorded. (mutlu_inek, rev. 743425)
* Dolphin doesn't tag nothing. When yuo change file the tag\rating, etc.. disappears. Nepomuk and strigi are started and seems running.(Linusv2)

==== KNS ====
* Sometimes KNS dialog is under Settings dialog (Kanagram and KStars) modal/non-modal issue when KNS is invoked from a Config dialog (jstubbs)

==== KDElibs - Misc ====
* kbuildsycoca4 crashes on startup. Backtrace windows is displayed below splashscreen. After a while - everything goes down. Couldn't save backtrace, but last KDE entry was vfolder_menu.cpp:488. Next was qdebug. Using rev 741332 (macson_g)
* cannot write Right-To-Left...in kde3 when you start a line with a character of an rtl language, the line goes rtl automatically (emilsedgh)
** Well, for me it does write RTL, but the text is not right-aligned as in KDE3, but left-aligned which is indeed a bug. (mutlu_inek, rev. 743425)
* Configure shortcuts dialog is too small at start: I cannot see the action name at all (it says stuff like 'C...' instead of 'Close'). Furthermore, and much worse: I cannot change the width of the columns at all to try to make the action names readable! (BCoppens)
* I can reproduce this behaviour e.g. with okular or kbounce, but not whith kwin4 or kgouldrunner: open okular, resize it, close it -- when reopened it will have the same size as before. Now maximize the window and close the app. When you restart the app it has it's default size. (Trigger7)
** I can confirm this. (mutlu_inek, rev. 743425)
** This bug seems to be related with {{bug|137108}}. Don't know a person but me which can reproduce it right now - please speak up if you can! Pinotree thinks this is a kdelibs bug and no bug in the applications. You can find an very ugly screen cast shich shows the problem here: http://alioth.debian.org/~trigger-guest/resizing-windows.ogg (Trigger7)
** I can reproduce this here. kpdf in KDE3 will restart maximized, however if you click the restore button, it returns to the default window size, which is too small. (auxsvr)
* When you make an application's toolbar locked, the next time you start the application the toolbar is not locked. (brumgabrasch) {{bug|152263}}
* When you make an application's toolbar float, the next time you start the application the toolbar becomes a glitch.
*** Test case: http://www.mediafire.com/?5xjgdxttclt
*** Screenshot: http://img256.imageshack.us/img256/3091/glitchxi2.png
*** Steps to reproduce:
**** Run KWrite
**** Make the toolbar float
**** Exit it and run it again
*** Might be related:
**** The floating toolbars no longer have a title bar or a border
**** The "Toolbar Menu->Orientation" menu no longer have "flat" or "floating"
** I can confirm this. (mutlu_inek, rev. 743425)
** Mek: using Qt 4.4 snapshot this is fixed
* <s>When trying to hear an audio preview (Right click on an audio file -> Properties -> Preview) the UI appears completely messed up (luca_b).</s>
** <s>Should be fixed. Please confirm. (Vir)</s>
*** Works. (teprrr and eliasp)
* The now fixed audio preview dialog could use some further improvements. Currently, it's very hard doing a seek on a long track due to the really short seek bar. Here's a quick'n'dirty mockup how it could be done: http://eliasprobst.eu/~elias/stuff/screenshots/kde4-issues/kfileaudiopreview-seekbar-redesign.png (eliasp)
* <s>Invisible menu bar disable shortcuts:</s> {{bug|152519}} (FiNeX) Fixed on 744418
* The items in the "select folder" dialogue are not sorted. (rabauke)
* Double-clicking folders on the "select folder" dialogue does not expand them. (rabauke)
* Playing an audio preview (rightclick → properties → preview), the audio preview is played using the ''Video'' channel defined in Phonon's settings. The preview component should be able to decide, based on the MIME type (audio or video), whether to do the play the sound using the ''Video'' or ''Music'' channel of Phonon. It's easy to reproduce if you have more than one soundcard. (eliasp)
** Vir added a 'fix' to do the playback using the ''NoCategory'' Phonon channel. Now we're waiting, until NoCategory is configurable using kcm phonon ;-) (eliasp)
* Filedialog: It should be possible jumping to the address bar using F6/the default shortcut, like it's possible in Konqueror. (eliasp)
* In Kfind if you start deleting something that you have found while search is in progress, the delete progress window appear, but it don't want to stay in top of kfind. Kfind always stays on top with this window.(Linusv2)

==== IO-slaves ====
* smb:/ ioslave causes crash (nixternal) (kakalto) - {{bug|152838}}
* smb:/ ioslave does not work with shares that need authentication. Console output: http://pastebin.ca/760196 (luca_b)
* The sftp:/ (scp:/ and others probably too) display '%2F' instead of '/' at the end of a path during autocompletion. Screenshot: http://eliasprobst.eu/~elias/stuff/screenshots/kde4-issues/sftp-auto-completion.png (eliasp)
* Setting permissions (rwx) of a file via sftp:/ doesn't work. It just doesn't change anything. (eliasp)
* file transfer from smb-shares stalls, {{bug|153054}}

==== KHTML ====
* There is no real font shrinking and enlarging available in apps that use khtml (I tested Konqueror and Akregator), only full page shrink/enlarge. This '''must''' be there in 4.0, IMO this is absolutely a release blocker. (If this functionality is available in KHTML and apps only don't use it, this bug note should be moved to all apps needing font shrink/enlarge but currently not implementing it) (gissi)
* Using full page shrink causes some graphical glitches (e.g. extremely unsharp font, displaced items). See [http://www.picupload.net/f-445754ac45c90a8218f6851003895e49.png Screenshot]. (gissi)

==== Directory Browser ====
The directory browser (e.g. Rightclick on Desktop → Configure Desktop → Slideshow → Add Directory) doesn't have the option to display hidden directories (rightclick in the browser → show hidden directories). So it's not possible adding ~/.kde/share/wallpapers to the Slideshow in this case. (eliasp)

== kdemultimedia ==

==== Juk ====
* Too much columns in default setting. Not a bug but a bad looking thing. (frank95com)
* When retrieving covers from the internet, a lot of 'transfer dialog' windows pop up and covering the whole screen for a moment. (eliasp)
** I can confirm this. (mutlu_inek, rev. 743425)
* Also, the cover is not actually shown in the "cover" column (instead there is a placeholder pic). (mutlu_inek, rev. 743425)
* JuK needs to be restarted to apply a changed output device of the Phonon 'Music' channel. (eliasp)

==== KMix ====
* The kmix icon in the system tray always shows 0% volume and doesn't respond to mouse wheel movement. (auxsvr)
** This happens when the default master channel is PCM. Trying to change to front it shows the volume percentage. (frank95com)
** I have an USB soundcard that only provides PCM, nothing else... I'd like to be able using volume change on scrolling + showing volume percentage. It worked in KDE 3.5.x. (eliasp)
*** I have a "solution" for this bug:select other master channel(whateveryouwant) then reselect pcm,then close and reopen kmix,you will find the volume in tray working. (Meskalamdug)
* wish: the checkbox to mute/unmute and output/input isn't very intuitive. Can I suggest something like this? (http://www.box.net/shared/quc0dkrx8t). (frank95com)
** vote++ (eliasp)
* The default layout of the KMix window should be changed at some points (eliasp): <s>has been fixed.</s> Didn't change at all ;-( (Yes, I've deleted my config-files..!) (eliasp)
http://eliasprobst.eu/~elias/stuff/screenshots/kde4-issues/kmix-window-layout.png
** The window height should be increased or a minimal value should be set as it is currently not obvious, that the lower buttons are volume sliders - they look just like a button you can't click.
** There's a lot of unused space on the bottom.
** The default window width should be slightly increased - it looks a little bit squeezed.
* don't change the master channel: http://www.mancausoft.org/kmix_4.png (mancausoft)

==== kscd ====
* crashes when inserting a CD. Problem is an assert thats hit http://pastebin.ca/769076 (apaku)
* another backtrace for above (looks different) http://pastebin.ca/768571 (yuriy)
* Eject button doesn't work (Meskalamdug)

== kdenetwork ==

==== Kopete ====
* Kopete crashes while connecting to my GTalk account (shortly after the contact list is loaded). See {{bug|152874}}
* When creating an account in Kopete I chose to use KWallet to store my passwords. After which KWallet brings up it's dialog to enter the password, but the Kopete settings window switches to being the window that's on top (but not focused) when interacting with the KWallet dialog, and vice versa, KWallet is on top when clicking on the settings window. (open_)
* In the Settings drop-down menu there are tickable options which change from Show to Hide whether they are ticked or unticked. Personally it looks like the program is malfunctioning if Hide Offline Users is ticked and I can see offline users. (open_)
** Confirmed. The text shouldn't change for ToggleActions in the menu, and the tooltip for the Show All button always displays the wrong tooltip. (Earthwings)
* Adding a msn contact(valid) produce..nothing (Meskalamdug)

==== Akregator ====
* Akregrator provides currently no tabbing functionality at all. Neither is it possible to open an article using 'Rightclick -> Open in tab' nor using 'Middleclick' (when having it configured this way). It is only possible opening articles in an external browser. (eliasp).

*<s>Marking feeds or messages as Read does not work. Even when reading a message, it is not marked as read. ([[User:Kleag|Kleag]] 23:46, 7 November 2007 (CET))</s> - fixed in [http://websvn.kde.org/?view=rev&revision=734910 734910]
** Marking feeds as Read is still broken for me. (yuriy)
*If a feed is deleted, the feed tree view is folded up completely. ([[User:Icwiener|Icwiener]] 03:48, 10 November 2007 (CET))
**Confirmed. Tree view is currently reset when something has changed. -- [[User:Eckhart|Eckhart]] 14:19, 10 November 2007 (CET)

*Shortcuts for increasing and decreasing font size in View menu are not shown completely (here "Ctrl+" for both) ([[User:Icwiener|Icwiener]] 13:11, 17 November 2007 (CET))
**Confirmed, same thing also in "Go" menu. -- [[User:Eckhart|Eckhart]] 12:57, 18 November 2007 (CET)

*Doesn't remember the width of the columns in the feed list panel and the "article" column in the article list panel cannot be resized. See {{bug|152702}} (FiNeX)

*When Multiple articles are highlighted and ^U is pressed only one has it's flag changed to unread. (DaSkreech)

* When using 'Mark Feed as Read' the 'Unread' value in the feed list on the left isn't updated until clicking somewhere else again. (eliasp)
** Confirmed. -- [[User:Eckhart|Eckhart]] 12:40, 25 November 2007 (CET)

* There is no visual feedback, whether a feed still contains unread articles (e.g. bold feed name in feed list) (eliasp)
** Confirmed. -- [[User:Eckhart|Eckhart]] 12:40, 25 November 2007 (CET)

* When trying to delete an article the selected count is three times bigger than the selected articles. (msoeken) {{bug|152949}}
** Confirmed. -- [[User:Eckhart|Eckhart]] 01:01, 26 November 2007 (CET)

* After deleting an article a list entry with no text is left. (msoeken) {{bug|152949}}
** Confirmed. -- [[User:Eckhart|Eckhart]] 01:01, 26 November 2007 (CET)

* When marking an article as important and then clicking on other articles, the flags are changing from one article to other ones. (msoeken)
** Confirmed. -- [[User:Eckhart|Eckhart]] 12:40, 25 November 2007 (CET)

*In the context menu (right click) of an article the icon for the option "Mark as important" is an envelope. (Carutsu)

==== KGet ====
* Again the corrupt download problem:i try http://fpdownload.macromedia. com/get/flashplayer/current/install_flash_player_9_linux.tar.gz and i get a corrupted file (Meskalamdug)
** Are you saying that a previous problem crept in again? I tried the link and it worked for me. (mutlu_inek, rev. 752265)
*** Ok,solved now.Works fine (Meskalamdug)

== KDEPIM ==

Please report bugs to [http://bugs.kde.org the KDE bugtracker]. There is not enough space here for meaningful reports, and it is hard to discuss or track them here.

Make sure you include enough details in your reports.

For crashes, read [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports|this article]] first. 
For normal bugs, read [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html this article].

== kdeutils ==

==== Ark ====
* <s>Ark support only zip and raw cd images (Meskalamdug)</s> This is fixed now. Thanks a lot! :) (mutlu_inek, rev. 752605)
* Adding files to archives does not work. (mutlu_inek, rev. 752605)
* If I select several files that reside in an archive and unselect them, they are still selected in the "size" column. (mutlu_inek, rev. 752605)
* Drag & drop does not work. (mutlu_inek, rev. 752605)
* Deleting files in archives does not work. (mutlu_inek, rev. 752605)
* If the files in the archive reside inside a folder, the folder is ignored and the files are extracted directly into the target folder. (mutlu_inek, rev. 752605)
* Ark open tar.gz ok,but create only zip archives or raw cd (Meskalamdug)

==== Kinfocenter ====
* Most of the Items are empty (emilsedgh)

==== KCalc ====
* <s>Under Settings->Configure KCalc...->General->Precision there is a spin box labelled "Maximum number of digits:". You can type numbers from 0-99 in it but it can be rotated (with the arrow buttons) up to 200. ([[User:Icwiener|Icwiener]] 03:34, 10 November 2007 (CET))</s> Fixed. (mutlu_inek, rev. 752265)
* <s>The window becomes way too wide when chosen high precicion. It's what the user wants if he sets the precision that high, but couldn't there be another solution than expanding the window beyond the screen borders? ([[User:Icwiener|Icwiener]] 03:34, 10 November 2007 (CET))</s> I have a small screen (1024x768) and it does not even fill half of it. I condider this fixed. (mutlu_inek, rev. 752265)
* <s>The dialog "Configure KCalc" is way too tall, and the space is not even needed. (Carutsu)</s> Fixed. (mutlu_inek, rev. 752265)
* <s>After enabling some buttons under Settings (such as Science buttons or Statistic buttons) when you disable them the application doesn't resize back to the smaller size it needs now. (Carutsu)</s> Fixed. (mutlu_inek, rev. 752265)

==== KHexEdit ====
* In Settings->Configure KHexEdit...->Files there is an option "Do not save 'Recent' document list on exit". This is a negative option. "Yes, I do not want to have them saved" <- odd ([[User:Icwiener|Icwiener]] 03:34, 10 November 2007 (CET))

==== KRegExpEditor ====
* On the info page on startup, the "littler than" sign '<' for the email address at the end of the page is not drawn. ([[User:Icwiener|Icwiener]] 03:34, 10 November 2007 (CET))
* When typing "a+" (without quote chars), KRegExpEditor crashes ([http://pastebin.ca/768287 backtrace]) -- [[User:Eckhart|Eckhart]] 15:09, 10 November 2007 (CET)
** confirmed in revision 737446 (FiNeX)

==== kgpg ====
* Gpg-agent won't start,i put it in .kde4/Autostart but at every kde start..kgpg said "The use of GnuPG Agent is enabled in GnuPG's configuration file (/home/giuseppe/.gnupg/gpg.conf).However, the agent does not seem to be running. This could result in problems with signing/decryption.Please disable GnuPG Agent from KGpg settings, or fix the agent" my script syntax is "#!/bin/sh eval "$(gpg-agent --daemon)" (Meskalamdug)
** Probably is a Konsole problem,gpg-agent is running but no $GPG_AGENTINFO like kde3 (Meskalamdug)
* Kpgp don't generate keys if under 1024 (Meskalamdug)

== fileshare module ==
* file share config dialog crash adding shared folders. See {{bug|152989}} (FiNeX)

Development/Tutorials/Saving and loading

2007-12-26T21:19:18Z

Milliams: Finish up the file saving stuff. Loading coming next...

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files (Under construction [[User:milliams]])|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=KCmdLineArgs (TODO [[User:milliams]])|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful. At the most basic, a text editor needs to be able to load files from disc, save files that you've created/edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we declare a <tt>{{qt|QString}} fileName</tt>.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream> //new

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile( tmpFile );
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

Okay, now to implement the code that will do the loading and saving. This will all be happening in <tt>mainwindow.cpp</tt>

The first thing we do is add
<code cppqt>
fileName(QString())
</code>
to the <tt>MainWindow</tt> constructor list on line 16. This makes sure that <tt>fileName</tt> is empty right from the beginning.

===Adding the actions===

The first thing we are going to do is provide the outward interface for the user so they can tell the application to load and save. Like with the <tt>quit</tt> action in tutorial 3, we will use <tt>KStandardActions</tt>. On lines 37 to 47 we add the actions in the same way as for the <tt>quit</tt> action. For each one, we connect it to the appropriate slot that we declared in the header file.

===Creating a new document===

The first function we create is the <tt>newFile()</tt> function.
<code cppqt>
void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}
</code>
<tt>fileName.clear()</tt> sets the <tt>fileName</tt> QString to be empty to reflect the fact that this document does not yet have a presence on disc. <tt>textArea->clear()</tt> then clears the central text area using the same function that we connected the <tt>clear</tt> <tt>KAction</tt> to in tutorial 3.

===Saving a file===

====saveFileAs(QString)====

Now we get onto our first file handling code. We're going to implement a function which will save the contents of the text area to the file name given as a parameter. KDE provides a class for safely saving a file called {{class|KSaveFile}} which is derived from Qt's {{qt|QFile}}.

The function's prototype is
<code cppqt>
void MainWindow::saveFileAs(const QString &outputFileName)
</code>

We then create our <tt>KSaveFile</tt> object and open it with
<code cppqt>
KSaveFile file(outputFileName);
file.open();
</code>

Now that we have our file to write to, we need to format the text in the text area to a format which can be written to file. For this, we create a {{qt|QByteArray}} and fill it with the plain text version of whatever is in the text area:
<code cppqt>
QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
</code>
Now that we have our <tt>QByteArray</tt>, we use it to write to the file with <tt>KSaveFile::write()</tt>. If we were using a normal <tt>QFile</tt>, this would make the changes immediately. However, if a problem occurred partway through writing, the file would become corrupted. For this reason, <tt>KSaveFile</tt> works by first writing to a temporary file and then, when you call <tt>KSaveFile::finalize()</tt> the changes are made to the actual file.
<code cppqt>
file.write(outputByteArray);
file.finalize();
file.close();
</code>
Finally, we set <tt>MainWindows</tt>'s <tt>fileName</tt> member to point to the file name we just saved to.
<code cppqt>
fileName = outputFileName;
</code>

====saveFileAs()====

This is the function that the <tt>saveAs</tt> slot is connected to. It simply calls the generic <tt>saveFileAs(QString)</tt> function and passes the file name returned by <tt>{{class|KFileDialog}}::[http://api.kde.org/4.0-api/kdelibs-apidocs/kio/html/classKFileDialog.html#8891356c249c5911e1ab15cc2739a89b getSaveFileName()]</tt>.

<code cppqt>
void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}
</code>

This our first actual use of the KIO library. {{class|KFileDialog}} provides a number of static functions for displaying the common file dialog that is used by all KDE applications. Calling <tt>KFileDialog::getSaveFileName()</tt> will display a dialog where the user can select the name of the file to save to or choose a new name. The function returns the full file name, which we then pass to <tt>saveFileAs(QString)</tt>.

====saveFile()====

<code cppqt>
void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}
</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.

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

==Moving On==
Now you can move on to KCmdLineArgs (TODO [[User:milliams]]).

[[Category:C++]]

Development/Tutorials/Saving and loading

2007-12-26T19:50:59Z

Milliams: Proofreading

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files (Under construction [[User:milliams]])|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=KCmdLineArgs (TODO [[User:milliams]])|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful. At the most basic, a text editor needs to be able to load files from disc, save files that you've created/edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we declare a <tt>{{qt|QString}} fileName</tt>.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream> //new

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile( tmpFile );
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

Okay, now to implement the code that will do the loading and saving. This will all be happening in <tt>mainwindow.cpp</tt>

The first thing we do is add
<code cppqt>
fileName(QString())
</code>
to the <tt>MainWindow</tt> constructor list on line 16. This makes sure that <tt>fileName</tt> is empty right from the beginning.

===Adding the actions===

The first thing we are going to do is provide the outward interface for the user so they can tell the application to load and save. Like with the <tt>quit</tt> action in tutorial 3, we will use <tt>KStandardActions</tt>. On lines 37 to 47 we add the actions in the same way as for the <tt>quit</tt> action. For each one, we connect it to the appropriate slot that we declared in the header file.

===Creating a new document===

The first function we create is the <tt>newFile()</tt> function.
<code cppqt>
void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}
</code>
<tt>fileName.clear()</tt> sets the <tt>fileName</tt> QString to be empty to reflect the fact that this document does not yet have a presence on disc. <tt>textArea->clear()</tt> then clears the central text area using the same function that we connected the <tt>clear</tt> <tt>KAction</tt> to in tutorial 3.

===Saving a file===

Now we get onto our first file handling code. We're going to implement a function which will save the contents of the text area to the file name given as a parameter. KDE provides a class for safely saving a file called {{class|KSaveFile}} which is derived from Qt's {{qt|QFile}}.

The function's prototype is
<code cppqt>
void MainWindow::saveFileAs(const QString &outputFileName)
</code>

We then create our <tt>KSaveFile</tt> object and open it with
<code cppqt>
KSaveFile file(outputFileName);
file.open();
</code>

Now that we have our file to write to, we need to format the text in the text area to a format which can be written to file. For this, we create a {{qt|QByteArray}} and fill it with the plain text version of whatever is in the text area:
<code cppqt>
QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
</code>
Now that we have our <tt>QByteArray</tt>, we use it to write to the file with <tt>KSaveFile::write()</tt>. If we were using a normal <tt>QFile</tt>, this would make the changes immediately. However, if a problem occurred partway through writing, the file would become corrupted. For this reason, <tt>KSaveFile</tt> works by first writing to a temporary file and then, when you call <tt>KSaveFile::finalize()</tt> the changes are made to the actual file.
<code cppqt>
file.write(outputByteArray);
file.finalize();
file.close();
</code>
Finally, we set <tt>MainWindows</tt>'s <tt>fileName</tt> member to point to the file name we just saved to.
<code cppqt>
fileName = outputFileName;
</code>

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

==Moving On==
Now you can move on to KCmdLineArgs (TODO [[User:milliams]]).

[[Category:C++]]

User:Milliams

2007-12-26T19:34:01Z

Milliams:

Currently working on [http://websvn.kde.org/trunk/playground/games/ksquares/ KSquares], various parts of KDE Games and a new version of KEduca.

Website/blog found at [http://milliams.com milliams.com].

I'm responsible for the '''Introduction To KDE 4 Programming''' tutorial series on [[Development/Tutorials]].

Development/Tutorials/Saving and loading

2007-12-26T19:32:03Z

Milliams: A bit of planning ahead

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files (Under construction [[User:milliams]])|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=KCmdLineArgs (TODO [[User:milliams]])|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful.At the most basic a text editor needs to be able to load files from disc, save files that you've created or edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we create a <tt>{{qt|QString}} fileName</tt>.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream> //new

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile( tmpFile );
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

Okay, now to implement the code that will do the loading and saving.

The first thing we do is add
<code cppqt>
fileName(QString())
</code>
to the <tt>MainWindow</tt> constructor list on line 16. This makes sure that <tt>fileName</tt> is empty right from the beginning.

===Adding the actions===

The first thing we are going to do is provide the outward interface for the user so they can tell the application to load and save. Like with the <tt>quit</tt> action in tutorial 3, we will use <tt>KStandardActions</tt>. On lines 37 to 47 we add the actions in the same way as for the <tt>quit</tt> action. For each one, we connect it to the appropriate slot that we declared in the header file.

===Creating a new document===

The first function we create is the <tt>newFile()</tt> function.
<code cppqt>
void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}
</code>
<tt>fileName.clear()</tt> sets the <tt>fileName</tt> QString to be empty to reflect the fact that this document does not yet have a presence on disc. <tt>textArea->clear()</tt> then clears the central text area using the same function that we connected the <tt>clear</tt> <tt>KAction</tt> to in tutorial 3.

===Saving a file===

Now we get onto our first file handling code. We're going to implement a function which will save the contents of the text area to the file name given as a parameter. KDE provides a class for safely saving a file called {{class|KSaveFile}} which is derived from Qt's {{qt|QFile}}.

The function's prototype is
<code cppqt>
void MainWindow::saveFileAs(const QString &outputFileName)
</code>

We then create our <tt>KSaveFile</tt> object and open it with
<code cppqt>
KSaveFile file(outputFileName);
file.open();
</code>

Now that we have out file to write to, we need to format the text in the text area to a format which can be written to file. For this, we create a {{qt|QByteArray}} and fill it with the plain text version of whatever is in the text area:
<code cppqt>
QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
</code>
Now that we have our <tt>QByteArray</tt>, we use it to write to the file with <tt>KSaveFile::write()</tt>. If we were using a normal <tt>QFile</tt>, this would make the changes immediately. However, if a problem occurred partway through writing, the file would become corrupted. For this reason, <tt>KSaveFile</tt> works by first writing to a temporary file and then, when you call <tt>KSaveFile::finalize()</tt> the changes are made to the actual file.
<code cppqt>
file.write(outputByteArray);
file.finalize();
file.close();
</code>
Finally, we set <tt>MainWindows</tt>'s <tt>fileName</tt> member to point to the file name we just saved to.

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

==Moving On==
Now you can move on to KCmdLineArgs (TODO [[User:milliams]]).

[[Category:C++]]

Development/Tutorials/Saving and loading

2007-12-26T19:18:35Z

Milliams: All the info on KSaveFile

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=TODO (milliams)|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful.At the most basic a text editor needs to be able to load files from disc, save files that you've created or edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we create a <tt>{{qt|QString}} fileName</tt>.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream> //new

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile( tmpFile );
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

Okay, now to implement the code that will do the loading and saving.

The first thing we do is add
<code cppqt>
fileName(QString())
</code>
to the <tt>MainWindow</tt> constructor list on line 16. This makes sure that <tt>fileName</tt> is empty right from the beginning.

===Adding the actions===

The first thing we are going to do is provide the outward interface for the user so they can tell the application to load and save. Like with the <tt>quit</tt> action in tutorial 3, we will use <tt>KStandardActions</tt>. On lines 37 to 47 we add the actions in the same way as for the <tt>quit</tt> action. For each one, we connect it to the appropriate slot that we declared in the header file.

===Creating a new document===

The first function we create is the <tt>newFile()</tt> function.
<code cppqt>
void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}
</code>
<tt>fileName.clear()</tt> sets the <tt>fileName</tt> QString to be empty to reflect the fact that this document does not yet have a presence on disc. <tt>textArea->clear()</tt> then clears the central text area using the same function that we connected the <tt>clear</tt> <tt>KAction</tt> to in tutorial 3.

===Saving a file===

Now we get onto our first file handling code. We're going to implement a function which will save the contents of the text area to the file name given as a parameter. KDE provides a class for safely saving a file called {{class|KSaveFile}} which is derived from Qt's {{qt|QFile}}.

The function's prototype is
<code cppqt>
void MainWindow::saveFileAs(const QString &outputFileName)
</code>

We then create our <tt>KSaveFile</tt> object and open it with
<code cppqt>
KSaveFile file(outputFileName);
file.open();
</code>

Now that we have out file to write to, we need to format the text in the text area to a format which can be written to file. For this, we create a {{qt|QByteArray}} and fill it with the plain text version of whatever is in the text area:
<code cppqt>
QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
</code>
Now that we have our <tt>QByteArray</tt>, we use it to write to the file with <tt>KSaveFile::write()</tt>. If we were using a normal <tt>QFile</tt>, this would make the changes immediately. However, if a problem occurred partway through writing, the file would become corrupted. For this reason, <tt>KSaveFile</tt> works by first writing to a temporary file and then, when you call <tt>KSaveFile::finalize()</tt> the changes are made to the actual file.
<code cppqt>
file.write(outputByteArray);
file.finalize();
file.close();
</code>
Finally, we set <tt>MainWindows</tt>'s <tt>fileName</tt> member to point to the file name we just saved to.

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

Development/Tutorials

2007-12-26T19:04:56Z

Milliams: /* Introduction To KDE 4 Programming */ Add newest tutorial to main page

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

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

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

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

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

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

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

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

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

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

;[[Development/Tutorials/Command-Line Options|Using Command-line Options]]
:''Processing and accessing command-line arguments the easy way with KDE's command line arguments classes.''

== Testing And Debugging ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Documentation ==

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

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

== Application Automation and Scripting ==

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

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

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

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

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

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

=== KOffice ===
; [[Development/Tutorials/KOffice Overview|KOffice Overview]]
:''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 Scripting]]
:''This tutorial shows how to script KWord with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/KSpread Scripting|KSpread Scripting]]
:''This tutorial shows how to script KSpread with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/Krita Scripting|Krita Scripting]]
:''This tutorial shows how to script Krita with Python, Ruby or JavaScript using Kross.''

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

== Search and Metadata ==

=== Strigi ===

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

=== Nepomuk ===

; [[Development/Tutorials/Metadata/KMetaData first steps|Nepomuk first steps]]
:''Nepomuk is the KDE library which provides easy access to metadata in the [http://nepomuk-kde.semanticdesktop.org Nepomuk-KDE] system. Learn how to make your application create and read metadata using the Nepomuk system.''

== Hardware Awareness (Solid) ==

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

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

== Multimedia (Phonon) ==

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

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

== Plasma ==

;[[Development/Tutorials/Plasma/GettingStarted|Getting Started With Plasmoids]]
:''Creating your first Plasma widget, or Plasmoid, in C++ with an SVG background, an icon and some text''

;[[Development/Tutorials/Plasma/DataEngines|Writing A DataEngine]]
:''DataEngines provide a standardized interface to various data sources for visualizations to use. Learn what a DataEngine is and how to write one of your own.''

;[[Development/Tutorials/Plasma/UsingDataEngines|Using DataEngines in Plasmoids]]
:''With a DataEngine, it is possible to retrieve data for display in a simple and standard way. This tutorial covers the topic of how to use DataEngines for this purpose in Plasmoids.''

;[[Development/Tutorials/Plasma/AbstractRunner|Creating Runners]]
:''Runners are plugins that provide action-based search functionality in the Plasma workspace "run command" dialog. These plugins can be used by any application that links again libplasma.''

== Kate / Kwrite ==

;[[Development/Tutorials/Kate/KTextEditor Plugins|Getting Started With KTextEditor Plugins]]
:''Creating your first KTextEditor plugin''

==Printing==

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

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

== Get Hot New Stuff ==
; [[Development/Tutorials/Introduction to Get Hot New Stuff|Introduction to Get Hot New Stuff]]
:''An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.''

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

== Rapid Application Development ==

=== Python ===

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

=== Ruby ===

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

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

=== Shell ===

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

== Other tutorials ==

=== Using the KDE Games Library ===
;[[Development/Tutorials/Games/KStandardGameAction| KStandardGameAction]]
:''Using libkdegames to make your game fit the kdegames standard''
;[[Development/Tutorials/Games/Highscores| Highscores]]
:''Implementing a simple highscore table into your game''
;[[Development/Tutorials/Games/Theme Selector| Theme Selector]]
:''Using the libkdegames theme selection dialog''

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

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

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

== KDE2 and KDE3 Materials ==

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

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

[[Category:KDE4]]

Development/Tutorials/Using KXmlGuiWindow

2007-12-26T17:15:32Z

Milliams:

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

series=Beginner Tutorial|

name=How To Use KXmlGuiWindow|

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

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

reading={{class|KXmlGuiWindow}}
}}

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

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

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

==KXmlGuiWindow==

{{class|KXmlGuiWindow}} provides a full main window view with menubars, toolbars, a statusbar and a main area in the centre for a large widget. Most KDE applications will derive from this class as it provides an easy way to define menu and toolbar layouts through XML files (this technology is called XMLGUI). While we will not be using XMLGUI in ''this'' tutorial, we will use it in the next.

In order to have a useful KXmlGuiWindow, we must subclass it. So we create two files, a <tt>mainwindow.cpp</tt> and a <tt>mainwindow.h</tt> which will contain our code.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
};

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

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

And finally we declare a pointer to the object that will make up the bulk of our program. {{class|KTextEdit}} is a generic richtext editor with some KDE niceties like cursor auto-hiding.

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

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

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

Finally, KXmlGuiWindow::setupGUI() is called which does a lot of behind-the-scenes stuff and creates the default menu bars (Settings, Help).

==Back to main.cpp==
In order to actually run this window, we need to add a few lines in main.cpp:
===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial2", 0,
ki18n("Tutorial 2"), "1.0",
ki18n("A simple text area"),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KApplication app;

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

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

==CMake==
The best way to build the program is to use CMake. All that's changed since tutorial 1 is that <tt>mainwindow.cpp</tt> has been added to the sources list and any <tt>tutorial1</tt> has become <tt>tutorial2</tt>.
===CMakeLists.txt===
<code ini n>
project (tutorial2)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial2_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial2 ${tutorial2_SRCS})
target_link_libraries(tutorial2 ${KDE4_KDEUI_LIBS})
</code>

===Compile it===
To compile, link and run it, use:
mkdir build && cd build
cmake ..
make
./tutorial2

==Moving On==
Now you can move on to [[Development/Tutorials/Using_KActions|using KActions]].

[[Category:C++]]

Development/Tutorials/First program

2007-12-26T17:15:29Z

Milliams: /* Make And Run */

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

series=Beginner Tutorial|

name=Hello World|

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [http://www.trolltech.com/products/qt/ Qt], [[Getting_Started/Build/KDE4|KDE4 development environment]]|

next=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]]|

reading=[[Development/Tutorials/CMake|CMake]]
}}

==Abstract==
Your first program shall greet the world with a friendly "Hello World", what else? For that, we will use a {{class|KMessageBox}} and customise one of the buttons.
[[image:introtokdetutorial1.png|frame|center]]

{{tip|To get more information about any class you come across, Konqueror offers a quick shortcut. So to look for information about KMessageBox, just type "kde:kmessagebox" into Konqueror and you'll be taken to the documentation.}}

{{tip|
You might want to use KDevelop for your projects, which does many nice things like code completion, easy access to API documentation or debugging support.

Read [[Getting_Started/Set_up_KDE_4_for_development#KDevelop|this tutorial]] to set up KDevelop correctly for this task. You probably want to check if the setup is working by testing opening an existing KDE 4 application with KDevelop first.

You still need to edit the CMake files by hand though.
}}

==The Code==
All the code we need will be in one file, <tt>main.cpp</tt>. Create that file with the code below:
<code cppqt>
#include <QString>
#include <KApplication>
#include <KAboutData>
#include <KMessageBox>
#include <KCmdLineArgs>
#include <KLocalizedString>

int main (int argc, char *argv[])
{
KAboutData aboutData("tutorial1", // The program name used internally.
0, // The message catalog name, use program name if null.
ki18n("Tutorial 1"), // A displayable program name string.
"1.0", // The program version string.
ki18n("KMessageBox popup"), // A short description of what the program does.
KAboutData::License_GPL, // License identifier
ki18n("(c) 2007"), // Copyright Statement
ki18n("Some text..."), // Some free form text, that can contain any kind of information.
"http://tutorial.com", // The program homepage string.
"submit@bugs.kde.org"); // The bug report email address string.

KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;
KGuiItem guiItem( QString( "Hello" ), QString(),
QString( "this is a tooltip" ),
QString( "this is a whatsthis" ) );
KMessageBox::questionYesNo( 0, "Hello World", "Hello", guiItem );
}
</code>
The first KDE specific code we come across in this program is {{class|KAboutData}}. This is the class used to store information about the program such as a short description, authors or license information. Pretty much every KDE application should use this class.

Then we come to {{class|KCmdLineArgs}}. This is the class one would use to specify command line switches to, for example, open the program with a specific file. However, in this tutorial, we simply initialise it with the {{class|KAboutData}} object we created so we can use the <tt>--version</tt> or <tt>--author</tt> switches.

Then we create a {{class|KApplication}} object. This needs to be done exactly once in each program since it is needed for things such as [[Development/Tutorials/Localization/i18n|i18n]].

Now we've done all the necessary KDE setup, we can move on to doing interesting things with our application. We're going to create a popup box but we're going to customise one of the buttons. To do this customisation, we need to use a {{class|KGuiItem}} object. The first argument in the {{class|KGuiItem}} constructor is the text that will appear on the item (in our case, a button). Then we have an option of setting an icon for the button but we don't want one so we just give it <tt>QString()</tt>. Finally we set the tooltip (what appears when you hover over an item) and finally the "What's This?" (accessed through right-clicking or Shift-F1) text.

Now we have our item, we can create our popup. We call the <tt>{{class|KMessageBox}}::questionYesNo()</tt> function which, by default, creates a message box with a "Yes" and a "No" button. The second argument is the text that will appear in the middle of the popup box. The third is the caption the window will have and finally we set the KGuiItem for (what would normally be) the "Yes" button to the <tt>KGuiItem guiItem</tt> we created.

We're all done as far as the code is concerned. Now to build it and try it out.

==Build==
If you set up your environment as described in [[Getting Started/Build/KDE4]], you can compile this code with

g++ main.cpp -o tutorial1 \
-I$QTDIR/include/Qt \
-I$QTDIR/include/QtCore \
-I$QTDIR/include \
-I$KDEDIR/include/KDE \
-I$KDEDIR/include \
-L$KDEDIR/lib \
-L$QTDIR/lib -lQtCore -lQtGui -lkdeui -lkdecore
and then run it with
dbus-launch ./tutorial1

===Using CMake===
If that worked, you may want to use [[Development/Tutorials/CMake|CMake]], just like the rest of KDE. This will automatically locate the libraries and headers for KDE, Qt etc. and will allow you to easily build your applications on other computers.
====CMakeLists.txt====
Create a file named CMakeLists.txt in the same directory as main.cpp with this content:
<code ini n>
project (tutorial1)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial1_SRCS main.cpp)

kde4_add_executable(tutorial1 ${tutorial1_SRCS})
target_link_libraries(tutorial1 ${KDE4_KDEUI_LIBS})
</code>
The <tt>find_package()</tt> function locates the package that you ask it for (in this case KDE4) and sets some variables describing the location of the package's headers and libraries. In this case we will use the <tt>KDE4_INCLUDES</tt> variable which contains the path to the KDE4 header files.

In order to allow the compiler to find these files, we pass that variable to the <tt>include_directories()</tt> function which adds the KDE4 headers to the header search path.

Next we create a variable called <tt>tutorial1_SRCS</tt> using the <tt>set()</tt> function. In this case we simply set it to the name of our only source file.

Then we use <tt>kde4_add_executable()</tt> to create an executable called <tt>tutorial1</tt> from the source files listed in our <tt>tutorial1_SRCS</tt> variable. Finally we link our executable to the KDE4 kdeui library using <tt>target_link_libraries()</tt> and the <tt>KDE4_KDEUI_LIBS</tt> variable which was set by the <tt>find_package()</tt> function.

====Make And Run====
Again, if you set up your environment as described in [[Getting_Started/Build/KDE4|Getting Started/Build/KDE4]], you can compile this code with:
cmakekde

Or if you did not:

mkdir build && cd build
cmake ..
make

And launch it with:
./tutorial1

==Moving On==
Now you can move on to [[Development/Tutorials/Using_KXmlGuiWindow|using KXmlGuiWindow]].

[[Category:C++]]

Development/Tutorials/Using KActions

2007-12-26T17:14:03Z

Milliams: CMakeLists.txt

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=How To Use KActions and XMLGUI|

pre=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]], Basic XML knowledge|

next=[[Development/Tutorials/Saving_and_loading|Tutorial 4 - Saving and loading]]|

reading=None
}}

==Abstract==
This tutorial introduces the concept of actions. Actions are a unified way of supplying the user with ways to interact with your program.

For example, if we wanted to let the user of [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 ]] clear the text box by clicking a button in the toolbar, from an option in the File menu or through a keyboard shortcut, it could all be done with one {{class|KAction}}.

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

==KAction==
A {{class|KAction}} is an object which contains all the information about the icon and shortcuts that is associated with a certain action. The action is then connected to a [http://doc.trolltech.com/latest/signalsandslots.html slot] which carries out the work of your action.

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial3", "tutorial3",
ki18n("Tutorial 3"), "1.0",
ki18n("A simple text area using KAction etc."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
This time, very little has changed in <tt>main.cpp</tt>, only the KAboutData constructor has been updated to show that we are now on tutorial 3.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
void setupActions();
};

#endif
</code>
Only a function <tt>void setupActions()</tt> has been added which will do all the work setting up the KActions.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent)
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

setupGUI();
}
</code>

==Explanation==
This builds upon the KXmlGuiWindow code from [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2]]. Most of the changes are to <tt>mainwindow.cpp</tt>, an important structural change being that the constructor for MainWindow now calls <tt>setupActions()</tt> instead of <tt>setupGUI()</tt>. <tt>setupActions()</tt> is where the new KAction code goes before finally calling <tt>setupGUI()</tt> itself.

===Creating the KAction object===
The KAction is built up in a number of steps. The first is including the <tt>KAction</tt> library and then creating the KAction:
<code cppqt>
#include <KAction>
...
KAction* clearAction = new KAction(this);
</code>
This creates a new KAction called <tt>clearAction</tt>.

===Setting KAction Properties===
====Text====
Now we have our KAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and under the <tt>KAction</tt>'s icon in the toolbar.
<code cppqt>clearAction->setText(i18n("Clear"));</code>
Note that the text is passed through the i18n() function; this is necessary for the UI to be translatable (more information on this can be found in the [[Development/Tutorials/Localization/i18n|i18n tutorial]]).

====Icon====
If the action is going to be displayed in a toolbar, it's nice to have an icon depicting the action. The following code sets the icon to the standard KDE <tt>document-new</tt> icon through the use of the <tt>setIcon()</tt> function:
<code cppqt>clearAction->setIcon(KIcon("document-new"));</code>

====Keyboard Shortcut====
Setting a keyboard shortcut to perform our action is equally simple:
<code cppqt>clearAction->setShortcut(Qt::CTRL + Qt::Key_W);</code>
This associates Ctrl+W with the KAction.

===Adding to the Collection===
In order for the action to be accessed by the XMLGUI framework (explained in depth later) it must be added to the application's ''action collection''. The action collection is accessed via the <tt>actionCollection()</tt> function like this:
<code cppqt>
actionCollection()->addAction("clear", clearAction);
</code>
Here, the <tt>clearAction</tt> KAction is added to the collection and given a name of ''clear''. This name (''clear'') is used by the XMLGUI framework to refer to the action.

====Connecting the action====
Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the <tt>clear()</tt> action belonging to a KTextEdit (which, unsurprisingly, clears the KTextEdit)
<code cppqt>
connect( clearAction, SIGNAL( triggered(bool) ),
textArea, SLOT( clear() ) );
</code>
This is the same as it would be done in Qt with a {{qt|QAction}}.

===KStandardAction===

For actions which would likely appear in almost every KDE application such as 'quit', 'save', and 'load' there are pre-created convenience KActions, accessed through {{class|KStandardAction}}.

They are very simple to use. Once the library has been included (<tt>#include <KStandardAction></tt>), simply supply it with what you want the function to do and which KActionCollection to add it to. For example:
<code cppqt>KStandardAction::quit(kapp, SLOT(quit()), actionCollection());</code>
This creates a KAction with the correct icon, text and shortcut and even adds it to the File menu.

==Adding the action to menus and toolbars==
At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.

{{note|In a later version of KDE4, XMLGUI, may be replaced with a new framework called liveui. For now, XMLGUI, is the only and correct way to set up the UI.}}

==XMLGUI==

The <tt>setupGUI()</tt> function in {{class|KXmlGuiWindow}} depends on the XMLGUI system to construct the GUI, which XMLGUI does by parsing an XML file description of the interface.

The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.

==''appname''ui.rc File==

Since the description of the UI is defined with XML, the layout must follow strict rules. This tutorial will not go into great depth on this topic, but for more information, see the [[Development/Architecture/KDE4/XMLGUI_Technology|detailed XMLGUI page]].

===tutorial3ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial3" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>

The <tt><Toolbar></tt> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name ''mainToolBar'' and its user visible name set to ''Main Toolbar'' using the <tt><text></tt> tag. The clear action is added to the toolbar using the <tt><Action></tt> tag, the name parameter in this tag being the string that was passed to the KActionCollection with <tt>addAction()</tt> in <tt>mainwindow.cpp</tt>.

Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the ''File'' menu of the <tt>MenuBar</tt> the same way it was added to the toolbar.

Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update.

==CMake==
Finally, the <tt>tutorial3ui.rc</tt> needs to go somewhere where KDE can find it (can't just leave it in the source directory!). '''This means the project needs to be installed somewhere.'''
===CMakeLists.txt===
<code ini n>
project(tutorial3)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial3_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial3 ${tutorial3_SRCS})

target_link_libraries(tutorial3 ${KDE4_KDEUI_LIBS})

install(TARGETS tutorial3 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial3ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial3)
</code>

This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.

===Make, Install And Run===
If you don't have write access to where your KDE4 installation directory, you can install it to a folder in your home directory.

To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:
mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial3
which will create a KDE-like directory structure in your user's home directory directory and will install the executable to {{path|$HOME/bin/tutorial3}}.

==Moving On==
Now you can move on to [[Development/Tutorials/Saving_and_loading|saving and loading]].

[[Category:C++]]

Development/Tutorials/Saving and loading

2007-12-26T17:13:58Z

Milliams: CMakeLists.txt

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=TODO (milliams)|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful.At the most basic a text editor needs to be able to load files from disc, save files that you've created or edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we create a <tt>{{qt|QString}} fileName</tt>.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile( tmpFile );
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

==Make, Install And Run==

===CMakeLists.txt===
<code ini n>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS}
${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

Development/Tutorials/Using KXmlGuiWindow

2007-12-26T17:13:53Z

Milliams: CMakeLists.txt

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

series=Beginner Tutorial|

name=How To Use KXmlGuiWindow|

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

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

reading={{class|KXmlGuiWindow}}
}}

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

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

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

==KXmlGuiWindow==

{{class|KXmlGuiWindow}} provides a full main window view with menubars, toolbars, a statusbar and a main area in the centre for a large widget. Most KDE applications will derive from this class as it provides an easy way to define menu and toolbar layouts through XML files (this technology is called XMLGUI). While we will not be using XMLGUI in ''this'' tutorial, we will use it in the next.

In order to have a useful KXmlGuiWindow, we must subclass it. So we create two files, a <tt>mainwindow.cpp</tt> and a <tt>mainwindow.h</tt> which will contain our code.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
};

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

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

And finally we declare a pointer to the object that will make up the bulk of our program. {{class|KTextEdit}} is a generic richtext editor with some KDE niceties like cursor auto-hiding.

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

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

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

Finally, KXmlGuiWindow::setupGUI() is called which does a lot of behind-the-scenes stuff and creates the default menu bars (Settings, Help).

==Back to main.cpp==
In order to actually run this window, we need to add a few lines in main.cpp:
===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial2", 0,
ki18n("Tutorial 2"), "1.0",
ki18n("A simple text area"),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KApplication app;

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

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

==CMake==
The best way to build the program is to use CMake. All that's changed since tutorial 1 is that <tt>mainwindow.cpp</tt> has been added to the sources list and any <tt>tutorial1</tt> has become <tt>tutorial2</tt>.
===CMakeLists.txt===
<code ini n>
project (tutorial2)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial2_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial2 ${tutorial2_SRCS})
target_link_libraries(tutorial2 ${KDE4_KDEUI_LIBS})
</code>

===Compile it===
To compile, link and run it, use:
mkdir build && cd build
cmake .. && make
./tutorial2

==Moving On==
Now you can move on to [[Development/Tutorials/Using_KActions|using KActions]].

[[Category:C++]]

Development/Tutorials/First program

2007-12-26T17:13:44Z

Milliams: CMakeLists.txt

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

series=Beginner Tutorial|

name=Hello World|

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [http://www.trolltech.com/products/qt/ Qt], [[Getting_Started/Build/KDE4|KDE4 development environment]]|

next=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]]|

reading=[[Development/Tutorials/CMake|CMake]]
}}

==Abstract==
Your first program shall greet the world with a friendly "Hello World", what else? For that, we will use a {{class|KMessageBox}} and customise one of the buttons.
[[image:introtokdetutorial1.png|frame|center]]

{{tip|To get more information about any class you come across, Konqueror offers a quick shortcut. So to look for information about KMessageBox, just type "kde:kmessagebox" into Konqueror and you'll be taken to the documentation.}}

{{tip|
You might want to use KDevelop for your projects, which does many nice things like code completion, easy access to API documentation or debugging support.

Read [[Getting_Started/Set_up_KDE_4_for_development#KDevelop|this tutorial]] to set up KDevelop correctly for this task. You probably want to check if the setup is working by testing opening an existing KDE 4 application with KDevelop first.

You still need to edit the CMake files by hand though.
}}

==The Code==
All the code we need will be in one file, <tt>main.cpp</tt>. Create that file with the code below:
<code cppqt>
#include <QString>
#include <KApplication>
#include <KAboutData>
#include <KMessageBox>
#include <KCmdLineArgs>
#include <KLocalizedString>

int main (int argc, char *argv[])
{
KAboutData aboutData("tutorial1", // The program name used internally.
0, // The message catalog name, use program name if null.
ki18n("Tutorial 1"), // A displayable program name string.
"1.0", // The program version string.
ki18n("KMessageBox popup"), // A short description of what the program does.
KAboutData::License_GPL, // License identifier
ki18n("(c) 2007"), // Copyright Statement
ki18n("Some text..."), // Some free form text, that can contain any kind of information.
"http://tutorial.com", // The program homepage string.
"submit@bugs.kde.org"); // The bug report email address string.

KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;
KGuiItem guiItem( QString( "Hello" ), QString(),
QString( "this is a tooltip" ),
QString( "this is a whatsthis" ) );
KMessageBox::questionYesNo( 0, "Hello World", "Hello", guiItem );
}
</code>
The first KDE specific code we come across in this program is {{class|KAboutData}}. This is the class used to store information about the program such as a short description, authors or license information. Pretty much every KDE application should use this class.

Then we come to {{class|KCmdLineArgs}}. This is the class one would use to specify command line switches to, for example, open the program with a specific file. However, in this tutorial, we simply initialise it with the {{class|KAboutData}} object we created so we can use the <tt>--version</tt> or <tt>--author</tt> switches.

Then we create a {{class|KApplication}} object. This needs to be done exactly once in each program since it is needed for things such as [[Development/Tutorials/Localization/i18n|i18n]].

Now we've done all the necessary KDE setup, we can move on to doing interesting things with our application. We're going to create a popup box but we're going to customise one of the buttons. To do this customisation, we need to use a {{class|KGuiItem}} object. The first argument in the {{class|KGuiItem}} constructor is the text that will appear on the item (in our case, a button). Then we have an option of setting an icon for the button but we don't want one so we just give it <tt>QString()</tt>. Finally we set the tooltip (what appears when you hover over an item) and finally the "What's This?" (accessed through right-clicking or Shift-F1) text.

Now we have our item, we can create our popup. We call the <tt>{{class|KMessageBox}}::questionYesNo()</tt> function which, by default, creates a message box with a "Yes" and a "No" button. The second argument is the text that will appear in the middle of the popup box. The third is the caption the window will have and finally we set the KGuiItem for (what would normally be) the "Yes" button to the <tt>KGuiItem guiItem</tt> we created.

We're all done as far as the code is concerned. Now to build it and try it out.

==Build==
If you set up your environment as described in [[Getting Started/Build/KDE4]], you can compile this code with

g++ main.cpp -o tutorial1 \
-I$QTDIR/include/Qt \
-I$QTDIR/include/QtCore \
-I$QTDIR/include \
-I$KDEDIR/include/KDE \
-I$KDEDIR/include \
-L$KDEDIR/lib \
-L$QTDIR/lib -lQtCore -lQtGui -lkdeui -lkdecore
and then run it with
dbus-launch ./tutorial1

===Using CMake===
If that worked, you may want to use [[Development/Tutorials/CMake|CMake]], just like the rest of KDE. This will automatically locate the libraries and headers for KDE, Qt etc. and will allow you to easily build your applications on other computers.
====CMakeLists.txt====
Create a file named CMakeLists.txt in the same directory as main.cpp with this content:
<code ini n>
project (tutorial1)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial1_SRCS main.cpp)

kde4_add_executable(tutorial1 ${tutorial1_SRCS})
target_link_libraries(tutorial1 ${KDE4_KDEUI_LIBS})
</code>
The <tt>find_package()</tt> function locates the package that you ask it for (in this case KDE4) and sets some variables describing the location of the package's headers and libraries. In this case we will use the <tt>KDE4_INCLUDES</tt> variable which contains the path to the KDE4 header files.

In order to allow the compiler to find these files, we pass that variable to the <tt>include_directories()</tt> function which adds the KDE4 headers to the header search path.

Next we create a variable called <tt>tutorial1_SRCS</tt> using the <tt>set()</tt> function. In this case we simply set it to the name of our only source file.

Then we use <tt>kde4_add_executable()</tt> to create an executable called <tt>tutorial1</tt> from the source files listed in our <tt>tutorial1_SRCS</tt> variable. Finally we link our executable to the KDE4 kdeui library using <tt>target_link_libraries()</tt> and the <tt>KDE4_KDEUI_LIBS</tt> variable which was set by the <tt>find_package()</tt> function.

====Make And Run====
Again, if you set up your environment as described in [[Getting_Started/Build/KDE4|Getting Started/Build/KDE4]], you can compile this code with:
cmakekde

Or if you did not:

mkdir build
cd build
cmake .. && make

And launch it as:
./tutorial1.shell

==Moving On==
Now you can move on to [[Development/Tutorials/Using_KXmlGuiWindow|using KXmlGuiWindow]].

[[Category:C++]]

Development/Tutorials/Saving and loading

2007-12-26T17:05:55Z

Milliams: mainwindow.h++

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=TODO (milliams)|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful.At the most basic a text editor needs to be able to load files from disc, save files that you've created or edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutorial 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new from tutorial3

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>
Since we want to add the ability to load and save files, we must add the functions which will do the work. Since the functions will be called through Qt's [http://doc.trolltech.com/latest/signalsandslots.html signal/slot] mechanism we must specify that these functions are slots as we do on line 19. Since we are using slots in this header file, we must also add the [http://doc.trolltech.com/latest/qobject.html#Q_OBJECT <tt>Q_OBJECT</tt>] macro.

We also want to keep track of the filename of the currently opened file so we create a <tt>{{qt|QString}} fileName</tt>.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

//New from here on

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::openFile()
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile( tmpFile );
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

==Make, Install And Run==

===CMakeLists.txt===
<code>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS} ${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

Development/Tutorials/Saving and loading

2007-12-26T16:47:36Z

Milliams: Abstract++

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=Loading and saving files|

pre=[[Development/Tutorials/Using_KActions|Tutorial 3 - KActions]]|

next=TODO (milliams)|

reading=KIO::{{class|NetAccess}} {{qt|QFile}}
}}

==Abstract==

Now that we have a basic text editor interface, it's time to make it do something useful.At the most basic a text editor needs to be able to load files from disc, save files that you've created or edited and create new files.

KDE provides a number of classes for working with files which make life a lot easier for developers. The KIO library allows you to easily access files through network-transparent protocols as well as providing standard file dialogs.

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

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial4", "tutorial4",
ki18n("Tutorial 4"), "1.0",
ki18n("A simple text area which can load and save."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
<tt>main.cpp</tt> hasn't changed from tutoral 3 except to change any reference to tutorial 3 to tutorial 4.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

class MainWindow : public KXmlGuiWindow
{
Q_OBJECT //new

public:
MainWindow(QWidget *parent=0);

private:
KTextEdit* textArea;
void setupActions();
QString fileName; //new

private slots: //new
void newFile(); //new
void openFile(); //new
void saveFile(); //new
void saveFileAs(); //new
void saveFileAs(const QString &outputFileName); //new
};

#endif
</code>

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
#include <KFileDialog> //new
#include <KMessageBox> //new
#include <KIO/NetAccess> //new
#include <KSaveFile> //new
#include <QTextStream>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent),
fileName(QString()) //new
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

KStandardAction::open(this, SLOT(openFile()),
actionCollection()); //new

KStandardAction::save(this, SLOT(saveFile()),
actionCollection()); //new

KStandardAction::saveAs(this, SLOT(saveFileAs()),
actionCollection()); //new

KStandardAction::openNew(this, SLOT(newFile()),
actionCollection()); //new

setupGUI();
}

void MainWindow::newFile()
{
fileName.clear();
textArea->clear();
}

void MainWindow::openFile() //new
{
QString fileNameFromDialog = KFileDialog::getOpenFileName();

QString tmpFile;
if(KIO::NetAccess::download(fileNameFromDialog, tmpFile,
this))
{
QFile file(tmpFile);
file.open(QIODevice::ReadOnly);
textArea->setPlainText(QTextStream(&file).readAll());
fileName = fileNameFromDialog;

KIO::NetAccess::removeTempFile( tmpFile );
}
else
{
KMessageBox::error(this,
KIO::NetAccess::lastErrorString());
}
}

void MainWindow::saveFile()
{
if(!fileName.isEmpty())
{
saveFileAs(fileName);
}
else
{
saveFileAs();
}
}

void MainWindow::saveFileAs()
{
saveFileAs(KFileDialog::getSaveFileName());
}

void MainWindow::saveFileAs(const QString &outputFileName)
{
KSaveFile file(outputFileName);
file.open();

QByteArray outputByteArray;
outputByteArray.append(textArea->toPlainText());
file.write(outputByteArray);
file.finalize();
file.close();

fileName = outputFileName;
}
</code>

===tutorial4ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial4" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>
This is identical to <tt>tutorial3ui.rc</tt> from tutorial 3 except the <tt>name</tt> has changed to 'tutorial4'. We do not need to add any information about any of the <tt>KStandardAction</tt>s since the placement of those actions is handled automatically by KDE.

==Explanation==

==Make, Install And Run==

===CMakeLists.txt===
<code>
project(tutorial4)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial4_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial4 ${tutorial4_SRCS})

target_link_libraries(tutorial4 ${KDE4_KDEUI_LIBS} ${KDE4_KIO_LIBS})

install(TARGETS tutorial4 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial4ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial4)
</code>
Since we are now using the KIO library, we must tell CMake to link against it. We do this by passing <tt>${KDE4_KIO_LIBS}</tt> to the <tt>target_link_libraries()</tt> function.

With this file, the tutorial can built and run in the same way as tutorial 3. For more information, see tutorial 3.

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial4

Development/Tutorials/Using KActions

2007-12-26T15:55:20Z

Milliams: Add links to new tutorial

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=How To Use KActions and XMLGUI|

pre=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]], Basic XML knowledge|

next=[[Development/Tutorials/Saving_and_loading|Tutorial 4 - Saving and loading]]|

reading=None
}}

==Abstract==
This tutorial introduces the concept of actions. Actions are a unified way of supplying the user with ways to interact with your program.

For example, if we wanted to let the user of [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 ]] clear the text box by clicking a button in the toolbar, from an option in the File menu or through a keyboard shortcut, it could all be done with one {{class|KAction}}.

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

==KAction==
A {{class|KAction}} is an object which contains all the information about the icon and shortcuts that is associated with a certain action. The action is then connected to a [http://doc.trolltech.com/latest/signalsandslots.html slot] which carries out the work of your action.

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial3", "tutorial3",
ki18n("Tutorial 3"), "1.0",
ki18n("A simple text area using KAction etc."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
This time, very little has changed in <tt>main.cpp</tt>, only the KAboutData constructor has been updated to show that we are now on tutorial 3.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
void setupActions();
};

#endif
</code>
Only a function <tt>void setupActions()</tt> has been added which will do all the work setting up the KActions.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent)
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

setupGUI();
}
</code>

==Explanation==
This builds upon the KXmlGuiWindow code from [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2]]. Most of the changes are to <tt>mainwindow.cpp</tt>, an important structural change being that the constructor for MainWindow now calls <tt>setupActions()</tt> instead of <tt>setupGUI()</tt>. <tt>setupActions()</tt> is where the new KAction code goes before finally calling <tt>setupGUI()</tt> itself.

===Creating the KAction object===
The KAction is built up in a number of steps. The first is including the <tt>KAction</tt> library and then creating the KAction:
<code cppqt>
#include <KAction>
...
KAction* clearAction = new KAction(this);
</code>
This creates a new KAction called <tt>clearAction</tt>.

===Setting KAction Properties===
====Text====
Now we have our KAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and under the <tt>KAction</tt>'s icon in the toolbar.
<code cppqt>clearAction->setText(i18n("Clear"));</code>
Note that the text is passed through the i18n() function; this is necessary for the UI to be translatable (more information on this can be found in the [[Development/Tutorials/Localization/i18n|i18n tutorial]]).

====Icon====
If the action is going to be displayed in a toolbar, it's nice to have an icon depicting the action. The following code sets the icon to the standard KDE <tt>document-new</tt> icon through the use of the <tt>setIcon()</tt> function:
<code cppqt>clearAction->setIcon(KIcon("document-new"));</code>

====Keyboard Shortcut====
Setting a keyboard shortcut to perform our action is equally simple:
<code cppqt>clearAction->setShortcut(Qt::CTRL + Qt::Key_W);</code>
This associates Ctrl+W with the KAction.

===Adding to the Collection===
In order for the action to be accessed by the XMLGUI framework (explained in depth later) it must be added to the application's ''action collection''. The action collection is accessed via the <tt>actionCollection()</tt> function like this:
<code cppqt>
actionCollection()->addAction("clear", clearAction);
</code>
Here, the <tt>clearAction</tt> KAction is added to the collection and given a name of ''clear''. This name (''clear'') is used by the XMLGUI framework to refer to the action.

====Connecting the action====
Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the <tt>clear()</tt> action belonging to a KTextEdit (which, unsurprisingly, clears the KTextEdit)
<code cppqt>
connect( clearAction, SIGNAL( triggered(bool) ),
textArea, SLOT( clear() ) );
</code>
This is the same as it would be done in Qt with a {{qt|QAction}}.

===KStandardAction===

For actions which would likely appear in almost every KDE application such as 'quit', 'save', and 'load' there are pre-created convenience KActions, accessed through {{class|KStandardAction}}.

They are very simple to use. Once the library has been included (<tt>#include <KStandardAction></tt>), simply supply it with what you want the function to do and which KActionCollection to add it to. For example:
<code cppqt>KStandardAction::quit(kapp, SLOT(quit()), actionCollection());</code>
This creates a KAction with the correct icon, text and shortcut and even adds it to the File menu.

==Adding the action to menus and toolbars==
At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.

{{note|In a later version of KDE4, XMLGUI, may be replaced with a new framework called liveui. For now, XMLGUI, is the only and correct way to set up the UI.}}

==XMLGUI==

The <tt>setupGUI()</tt> function in {{class|KXmlGuiWindow}} depends on the XMLGUI system to construct the GUI, which XMLGUI does by parsing an XML file description of the interface.

The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.

==''appname''ui.rc File==

Since the description of the UI is defined with XML, the layout must follow strict rules. This tutorial will not go into great depth on this topic, but for more information, see the [[Development/Architecture/KDE4/XMLGUI_Technology|detailed XMLGUI page]].

===tutorial3ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial3" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>

The <tt><Toolbar></tt> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name ''mainToolBar'' and its user visible name set to ''Main Toolbar'' using the <tt><text></tt> tag. The clear action is added to the toolbar using the <tt><Action></tt> tag, the name parameter in this tag being the string that was passed to the KActionCollection with <tt>addAction()</tt> in <tt>mainwindow.cpp</tt>.

Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the ''File'' menu of the <tt>MenuBar</tt> the same way it was added to the toolbar.

Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update.

==CMake==
Finally, the <tt>tutorial3ui.rc</tt> needs to go somewhere where KDE can find it (can't just leave it in the source directory!). '''This means the project needs to be installed somewhere.'''
===CMakeLists.txt===
<code>
project(tutorial3)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial3_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial3 ${tutorial3_SRCS})

target_link_libraries(tutorial3 ${KDE4_KDEUI_LIBS})

install(TARGETS tutorial3 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial3ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial3)
</code>

This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.

===Make, Install And Run===
If you don't have write access to where your KDE4 installation directory, you can install it to a folder in your home directory.

To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:
mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial3
which will create a KDE-like directory structure in your user's home directory directory and will install the executable to {{path|$HOME/bin/tutorial3}}.

==Moving On==
Now you can move on to [[Development/Tutorials/Saving_and_loading|saving and loading]].

[[Category:C++]]

Development/Tutorials/Using KXmlGuiWindow

2007-12-26T15:54:23Z

Milliams:

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

series=Beginner Tutorial|

name=How To Use KXmlGuiWindow|

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

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

reading={{class|KXmlGuiWindow}}
}}

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

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

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

==KXmlGuiWindow==

{{class|KXmlGuiWindow}} provides a full main window view with menubars, toolbars, a statusbar and a main area in the centre for a large widget. Most KDE applications will derive from this class as it provides an easy way to define menu and toolbar layouts through XML files (this technology is called XMLGUI). While we will not be using XMLGUI in ''this'' tutorial, we will use it in the next.

In order to have a useful KXmlGuiWindow, we must subclass it. So we create two files, a <tt>mainwindow.cpp</tt> and a <tt>mainwindow.h</tt> which will contain our code.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
};

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

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

And finally we declare a pointer to the object that will make up the bulk of our program. {{class|KTextEdit}} is a generic richtext editor with some KDE niceties like cursor auto-hiding.

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

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

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

Finally, KXmlGuiWindow::setupGUI() is called which does a lot of behind-the-scenes stuff and creates the default menu bars (Settings, Help).

==Back to main.cpp==
In order to actually run this window, we need to add a few lines in main.cpp:
===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial2", 0,
ki18n("Tutorial 2"), "1.0",
ki18n("A simple text area"),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KApplication app;

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

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

==CMake==
The best way to build the program is to use CMake. All that's changed since tutorial 1 is that <tt>mainwindow.cpp</tt> has been added to the sources list and any <tt>tutorial1</tt> has become <tt>tutorial2</tt>.
===CMakeLists.txt===
<code ini>
project (tutorial2)

find_package(KDE4 REQUIRED)
include_directories( ${KDE4_INCLUDES} )

set(tutorial2_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial2 ${tutorial2_SRCS})
target_link_libraries( tutorial2 ${KDE4_KDEUI_LIBS})
</code>

===Compile it===
To compile, link and run it, use:
mkdir build && cd build
cmake .. && make
./tutorial2

==Moving On==
Now you can move on to [[Development/Tutorials/Using_KActions|using KActions]].

[[Category:C++]]

Development/Tutorials/Using KActions

2007-12-26T15:49:44Z

Milliams:

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=How To Use KActions and XMLGUI|

pre=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]], Basic XML knowledge|

next=TODO (milliams)|

reading=None
}}

==Abstract==
This tutorial introduces the concept of actions. Actions are a unified way of supplying the user with ways to interact with your program.

For example, if we wanted to let the user of [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 ]] clear the text box by clicking a button in the toolbar, from an option in the File menu or through a keyboard shortcut, it could all be done with one {{class|KAction}}.

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

==KAction==
A {{class|KAction}} is an object which contains all the information about the icon and shortcuts that is associated with a certain action. The action is then connected to a [http://doc.trolltech.com/latest/signalsandslots.html slot] which carries out the work of your action.

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial3", "tutorial3",
ki18n("Tutorial 3"), "1.0",
ki18n("A simple text area using KAction etc."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
This time, very little has changed in <tt>main.cpp</tt>, only the KAboutData constructor has been updated to show that we are now on tutorial 3.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
void setupActions();
};

#endif
</code>
Only a function <tt>void setupActions()</tt> has been added which will do all the work setting up the KActions.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent)
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

setupGUI();
}
</code>

==Explanation==
This builds upon the KXmlGuiWindow code from [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2]]. Most of the changes are to <tt>mainwindow.cpp</tt>, an important structural change being that the constructor for MainWindow now calls <tt>setupActions()</tt> instead of <tt>setupGUI()</tt>. <tt>setupActions()</tt> is where the new KAction code goes before finally calling <tt>setupGUI()</tt> itself.

===Creating the KAction object===
The KAction is built up in a number of steps. The first is including the <tt>KAction</tt> library and then creating the KAction:
<code cppqt>
#include <KAction>
...
KAction* clearAction = new KAction(this);
</code>
This creates a new KAction called <tt>clearAction</tt>.

===Setting KAction Properties===
====Text====
Now we have our KAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and under the <tt>KAction</tt>'s icon in the toolbar.
<code cppqt>clearAction->setText(i18n("Clear"));</code>
Note that the text is passed through the i18n() function; this is necessary for the UI to be translatable (more information on this can be found in the [[Development/Tutorials/Localization/i18n|i18n tutorial]]).

====Icon====
If the action is going to be displayed in a toolbar, it's nice to have an icon depicting the action. The following code sets the icon to the standard KDE <tt>document-new</tt> icon through the use of the <tt>setIcon()</tt> function:
<code cppqt>clearAction->setIcon(KIcon("document-new"));</code>

====Keyboard Shortcut====
Setting a keyboard shortcut to perform our action is equally simple:
<code cppqt>clearAction->setShortcut(Qt::CTRL + Qt::Key_W);</code>
This associates Ctrl+W with the KAction.

===Adding to the Collection===
In order for the action to be accessed by the XMLGUI framework (explained in depth later) it must be added to the application's ''action collection''. The action collection is accessed via the <tt>actionCollection()</tt> function like this:
<code cppqt>
actionCollection()->addAction("clear", clearAction);
</code>
Here, the <tt>clearAction</tt> KAction is added to the collection and given a name of ''clear''. This name (''clear'') is used by the XMLGUI framework to refer to the action.

====Connecting the action====
Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the <tt>clear()</tt> action belonging to a KTextEdit (which, unsurprisingly, clears the KTextEdit)
<code cppqt>
connect( clearAction, SIGNAL( triggered(bool) ),
textArea, SLOT( clear() ) );
</code>
This is the same as it would be done in Qt with a {{qt|QAction}}.

===KStandardAction===

For actions which would likely appear in almost every KDE application such as 'quit', 'save', and 'load' there are pre-created convenience KActions, accessed through {{class|KStandardAction}}.

They are very simple to use. Once the library has been included (<tt>#include <KStandardAction></tt>), simply supply it with what you want the function to do and which KActionCollection to add it to. For example:
<code cppqt>KStandardAction::quit(kapp, SLOT(quit()), actionCollection());</code>
This creates a KAction with the correct icon, text and shortcut and even adds it to the File menu.

==Adding the action to menus and toolbars==
At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.

{{note|In a later version of KDE4, XMLGUI, may be replaced with a new framework called liveui. For now, XMLGUI, is the only and correct way to set up the UI.}}

==XMLGUI==

The <tt>setupGUI()</tt> function in {{class|KXmlGuiWindow}} depends on the XMLGUI system to construct the GUI, which XMLGUI does by parsing an XML file description of the interface.

The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.

==''appname''ui.rc File==

Since the description of the UI is defined with XML, the layout must follow strict rules. This tutorial will not go into great depth on this topic, but for more information, see the [[Development/Architecture/KDE4/XMLGUI_Technology|detailed XMLGUI page]].

===tutorial3ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial3" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>

The <tt><Toolbar></tt> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name ''mainToolBar'' and its user visible name set to ''Main Toolbar'' using the <tt><text></tt> tag. The clear action is added to the toolbar using the <tt><Action></tt> tag, the name parameter in this tag being the string that was passed to the KActionCollection with <tt>addAction()</tt> in <tt>mainwindow.cpp</tt>.

Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the ''File'' menu of the <tt>MenuBar</tt> the same way it was added to the toolbar.

Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update.

==CMake==
Finally, the <tt>tutorial3ui.rc</tt> needs to go somewhere where KDE can find it (can't just leave it in the source directory!). '''This means the project needs to be installed somewhere.'''
===CMakeLists.txt===
<code>
project(tutorial3)

find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})

set(tutorial3_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial3 ${tutorial3_SRCS})

target_link_libraries(tutorial3 ${KDE4_KDEUI_LIBS})

install(TARGETS tutorial3 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial3ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial3)
</code>

This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.

===Make, Install And Run===
If you don't have write access to where your KDE4 installation directory, you can install it to a folder in your home directory.

To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:
mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial3
which will create a KDE-like directory structure in your user's home directory directory and will install the executable to {{path|$HOME/bin/tutorial3}}.

==Moving On==
TODO

[[Category:C++]]

Development/Tutorials/Saving and loading

2007-12-26T15:47:58Z

Milliams: Add code and skellington text for my latest tutorial. More to come very soon...

Development/Tutorials/Using KActions

2007-12-25T22:52:21Z

Milliams: Proofreading. Remove all the crap that's been added over time to make the article more focused.

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=How To Use KActions and XmlGui|

pre=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]], Basic XML knowledge|

next=TODO (milliams)|

reading=None
}}

==Abstract==
This tutorial introduces the concept of actions. Actions are a unified way of supplying the user with ways to interact with your program.

For example, if we wanted to let the user of [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 ]] clear the text box by clicking a button in the toolbar, from an option in the File menu or through a keyboard shortcut, it could all be done with one {{class|KAction}}.

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

==KAction==
A {{class|KAction}} is an object which contains all the information about the icon and shortcuts that is associated with a certain action. The action is then connected to a [http://doc.trolltech.com/latest/signalsandslots.html slot] which carries out the work of your action.

== The Code ==

===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial3", "tutorial3",
ki18n("Tutorial 3"), "1.0",
ki18n("A simple text area using KAction etc."),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;

MainWindow* window = new MainWindow();
window->show();
return app.exec();
}
</code>
This time, very little has changed in <tt>main.cpp</tt>, only the KAboutData constructor has been updated to show that we are now on tutorial 3.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
void setupActions();
};

#endif
</code>
Only a function <tt>void setupActions()</tt> has been added which will do all the work setting up the KActions.

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

#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>

MainWindow::MainWindow(QWidget *parent)
: KXmlGuiWindow(parent)
{
textArea = new KTextEdit;
setCentralWidget(textArea);

setupActions();
}

void MainWindow::setupActions()
{
KAction* clearAction = new KAction(this);
clearAction->setText(i18n("Clear"));
clearAction->setIcon(KIcon("document-new"));
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
actionCollection()->addAction("clear", clearAction);
connect(clearAction, SIGNAL(triggered(bool)),
textArea, SLOT(clear()));

KStandardAction::quit(kapp, SLOT(quit()),
actionCollection());

setupGUI();
}
</code>

==Explanation==
This builds upon the KXmlGuiWindow code from [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2]]. Most of the changes are to <tt>mainwindow.cpp</tt>, an important structural change being that the constructor for MainWindow now calls <tt>setupActions()</tt> instead of <tt>setupGUI()</tt>. <tt>setupActions()</tt> is where the new KAction code goes before finally calling <tt>setupGUI()</tt> itself.

===Creating the KAction object===
The KAction is built up in a number of steps. The first is including the <tt>KAction</tt> library and then creating the KAction:
<code cppqt>
#include <KAction>
...
KAction* clearAction = new KAction(this);
</code>
This creates a new KAction called <tt>clearAction</tt>.

===Setting KAction Properties===
====Text====
Now we have our KAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and under the <tt>KAction</tt>'s icon in the toolbar.
<code cppqt>clearAction->setText(i18n("Clear"));</code>
Note that the text is passed through the i18n() function; this is necessary for the UI to be translatable (more information on this can be found in the [[Development/Tutorials/Localization/i18n|i18n tutorial]]).

====Icon====
If the action is going to be displayed in a toolbar, it's nice to have an icon depicting the action. The following code sets the icon to the standard KDE <tt>document-new</tt> icon through the use of the <tt>setIcon()</tt> function:
<code cppqt>clearAction->setIcon(KIcon("document-new"));</code>

====Keyboard Shortcut====
Setting a keyboard shortcut to perform our action is equally simple:
<code cppqt>clearAction->setShortcut(Qt::CTRL + Qt::Key_W);</code>
This associates Ctrl+W with the KAction.

===Adding to the Collection===
In order for the action to be accessed by the XMLGUI framework (explained in depth later) it must be added to the application's ''action collection''. The action collection is accessed via the <tt>actionCollection()</tt> function like this:
<code cppqt>
actionCollection()->addAction("clear", clearAction);
</code>
Here, the <tt>clearAction</tt> KAction is added to the collection and given a name of ''clear''. This name (''clear'') is used by the XMLGUI framework to refer to the action.

====Connecting the action====
Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the <tt>clear()</tt> action belonging to a KTextEdit (which, unsurprisingly, clears the KTextEdit)
<code cppqt>
connect( clearAction, SIGNAL( triggered(bool) ),
textArea, SLOT( clear() ) );
</code>
This is the same as it would be done in Qt with a {{qt|QAction}}.

===KStandardAction===

For actions which would likely appear in almost every KDE application such as 'quit', 'save', and 'load' there are pre-created convenience KActions, accessed through {{class|KStandardAction}}.

They are very simple to use. Once the library has been included (<tt>#include <KStandardAction></tt>), simply supply it with what you want the function to do and which KActionCollection to add it to. For example:
<code cppqt>KStandardAction::quit(kapp, SLOT(quit()), actionCollection());</code>
This creates a KAction with the correct icon, text and shortcut and even adds it to the File menu.

==Adding the action to menus and toolbars==
At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.

{{note|In a later version of KDE4, XMLGUI, may be replaced with a new framework called liveui. For now, XMLGUI, is the only and correct way to set up the UI.}}

==XMLGUI==

The <tt>setupGUI()</tt> function in {{class|KXmlGuiWindow}} depends on the XMLGUI system to construct the GUI, which XMLGUI does by parsing an XML file description of the interface.

The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.

==''appname''ui.rc File==

Since the description of the UI is defined with XML, the layout must follow strict rules. This tutorial will not go into great depth on this topic, but for more information, see the [[Development/Architecture/KDE4/XMLGUI_Technology|detailed XMLGUI page]].

===tutorial3ui.rc===
<code xml n>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<gui name="tutorial3" version="1">
<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>
<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>
</gui>
</code>

The <tt><Toolbar></tt> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name ''mainToolBar'' and its user visible name set to ''Main Toolbar'' using the <tt><text></tt> tag. The clear action is added to the toolbar using the <tt><Action></tt> tag, the name parameter in this tag being the string that was passed to the KActionCollection with <tt>addAction()</tt> in <tt>mainwindow.cpp</tt>.

Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the ''File'' menu of the <tt>MenuBar</tt> the same way it was added to the toolbar.

Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update.

==CMake==
Finally, the <tt>tutorial3ui.rc</tt> needs to go somewhere where KDE can find it (can't just leave it in the source directory!). '''This means the project needs to be installed somewhere.'''
===CMakeLists.txt===
<code>
project(tutorial3)

find_package(KDE4 REQUIRED)
include_directories( ${KDE4_INCLUDES} )

set(tutorial3_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial3 ${tutorial3_SRCS})

target_link_libraries(tutorial3 ${KDE4_KDEUI_LIBS})

install(TARGETS tutorial3 DESTINATION ${BIN_INSTALL_DIR})
install( FILES tutorial3ui.rc
DESTINATION ${DATA_INSTALL_DIR}/tutorial3 )
</code>

This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.

===Make, Install And Run===
If you don't have write access to where your KDE4 installation directory, you can install it to a folder in your home directory.

To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:
mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial3
which will create a KDE-like directory structure in your user's home directory directory and will install the executable to {{path|$HOME/bin/tutorial3}}.

==Moving On==
TODO

[[Category:C++]]

Development/Tutorials/Using KXmlGuiWindow

2007-12-25T22:11:32Z

Milliams: More proofreading, increased consistency and a better introduction to KXmlGuiWindow

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

series=Beginner Tutorial|

name=How To Use KXmlGuiWindow|

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

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

reading={{class|KXmlGuiWindow}}
}}

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

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

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

==KXmlGuiWindow==

{{class|KXmlGuiWindow}} provides a full main window view with menubars, toolbars, a statusbar and a main area in the centre for a large widget. Most KDE applications will derive from this class as it provides an easy way to define menu and toolbar layouts through XML files (this technology is called XMLGUI). While we will not be using XMLGUI in ''this'' tutorial, we will use it in the next.

In order to have a useful KXmlGuiWindow, we must subclass it. So we create two files, a <tt>mainwindow.cpp</tt> and a <tt>mainwindow.h</tt> which will contain our code.

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

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
};

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

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

And finally we declare a pointer to the object that will make up the bulk of our program. {{class|KTextEdit}} is a generic richtext editor with some KDE niceties like cursor auto-hiding.

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

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

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

Finally, KXmlGuiWindow::setupGUI() is called which does a lot of behind-the-scenes stuff and creates the default menu bars (Settings, Help).

==Back to main.cpp==
In order to actually run this window, we need to add a few lines in main.cpp:
===main.cpp===
<code cppqt n>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial2", 0,
ki18n("Tutorial 2"), "1.0",
ki18n("A simple text area"),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KApplication app;

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

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

==CMake==
The best way to build the program is to use CMake. All that's changed since tutorial 1 is that <tt>mainwindow.cpp</tt> has been added to the sources list and any <tt>tutorial1</tt> has become <tt>tutorial2</tt>.
===CMakeLists.txt===
<code ini>
project (tutorial2)

find_package(KDE4 REQUIRED)
include_directories( ${KDE4_INCLUDES} )

set(tutorial2_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial2 ${tutorial2_SRCS})
target_link_libraries( tutorial2 ${KDE4_KDEUI_LIBS})
</code>

===Compile it===
To compile, link and run it, use:
mkdir build && cd build
cmake .. && make
./tutorial2

==Moving On==
Now you can move on to [[Development/Tutorials/Using_KActions|using KActions]].

[[Category:C++]]

Development/Tutorials/First program

2007-12-25T21:55:24Z

Milliams: Some proofreading

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

series=Beginner Tutorial|

name=Hello World|

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [http://www.trolltech.com/products/qt/ Qt], [[Getting_Started/Build/KDE4|KDE4 development environment]]|

next=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]]|

reading=[[Development/Tutorials/CMake|CMake]]
}}

==Abstract==
Your first program shall greet the world with a friendly "Hello World", what else? For that, we will use a {{class|KMessageBox}} and customise one of the buttons.
[[image:introtokdetutorial1.png|frame|center]]

{{tip|To get more information about any class you come across, Konqueror offers a quick shortcut. So to look for information about KMessageBox, just type "kde:kmessagebox" into Konqueror and you'll be taken to the documentation.}}

{{tip|
You might want to use KDevelop for your projects, which does many nice things like code completion, easy access to API documentation or debugging support.

Read [[Getting_Started/Set_up_KDE_4_for_development#KDevelop|this tutorial]] to set up KDevelop correctly for this task. You probably want to check if the setup is working by testing opening an existing KDE 4 application with KDevelop first.

You still need to edit the CMake files by hand though.
}}

==The Code==
All the code we need will be in one file, <tt>main.cpp</tt>. Create that file with the code below:
<code cppqt>
#include <QString>
#include <KApplication>
#include <KAboutData>
#include <KMessageBox>
#include <KCmdLineArgs>
#include <KLocalizedString>

int main (int argc, char *argv[])
{
KAboutData aboutData("tutorial1", // The program name used internally.
0, // The message catalog name, use program name if null.
ki18n("Tutorial 1"), // A displayable program name string.
"1.0", // The program version string.
ki18n("KMessageBox popup"), // A short description of what the program does.
KAboutData::License_GPL, // License identifier
ki18n("(c) 2007"), // Copyright Statement
ki18n("Some text..."), // Some free form text, that can contain any kind of information.
"http://tutorial.com", // The program homepage string.
"submit@bugs.kde.org"); // The bug report email address string.

KCmdLineArgs::init( argc, argv, &aboutData );
KApplication app;
KGuiItem guiItem( QString( "Hello" ), QString(),
QString( "this is a tooltip" ),
QString( "this is a whatsthis" ) );
KMessageBox::questionYesNo( 0, "Hello World", "Hello", guiItem );
}
</code>
The first KDE specific code we come across in this program is {{class|KAboutData}}. This is the class used to store information about the program such as a short description, authors or license information. Pretty much every KDE application should use this class.

Then we come to {{class|KCmdLineArgs}}. This is the class one would use to specify command line switches to, for example, open the program with a specific file. However, in this tutorial, we simply initialise it with the {{class|KAboutData}} object we created so we can use the <tt>--version</tt> or <tt>--author</tt> switches.

Then we create a {{class|KApplication}} object. This needs to be done exactly once in each program since it is needed for things such as [[Development/Tutorials/Localization/i18n|i18n]].

Now we've done all the necessary KDE setup, we can move on to doing interesting things with our application. We're going to create a popup box but we're going to customise one of the buttons. To do this customisation, we need to use a {{class|KGuiItem}} object. The first argument in the {{class|KGuiItem}} constructor is the text that will appear on the item (in our case, a button). Then we have an option of setting an icon for the button but we don't want one so we just give it <tt>QString()</tt>. Finally we set the tooltip (what appears when you hover over an item) and finally the "What's This?" (accessed through right-clicking or Shift-F1) text.

Now we have our item, we can create our popup. We call the <tt>{{class|KMessageBox}}::questionYesNo()</tt> function which, by default, creates a message box with a "Yes" and a "No" button. The second argument is the text that will appear in the middle of the popup box. The third is the caption the window will have and finally we set the KGuiItem for (what would normally be) the "Yes" button to the <tt>KGuiItem guiItem</tt> we created.

We're all done as far as the code is concerned. Now to build it and try it out.

==Build==
If you set up your environment as described in [[Getting Started/Build/KDE4]], you can compile this code with

g++ main.cpp -o tutorial1 \
-I$QTDIR/include/Qt \
-I$QTDIR/include/QtCore \
-I$QTDIR/include \
-I$KDEDIR/include/KDE \
-I$KDEDIR/include \
-L$KDEDIR/lib \
-L$QTDIR/lib -lQtCore -lQtGui -lkdeui -lkdecore
and then run it with
dbus-launch ./tutorial1

===Using CMake===
If that worked, you may want to use [[Development/Tutorials/CMake|CMake]], just like the rest of KDE. This will automatically locate the libraries and headers for KDE, Qt etc. and will allow you to easily build your applications on other computers.
====CMakeLists.txt====
Create a file named CMakeLists.txt in the same directory as main.cpp with this content:
<code>
project (tutorial1)

find_package(KDE4 REQUIRED)
include_directories( ${KDE4_INCLUDES} )

set(tutorial1_SRCS main.cpp)

kde4_add_executable(tutorial1 ${tutorial1_SRCS})
target_link_libraries(tutorial1 ${KDE4_KDEUI_LIBS})
</code>
The <tt>find_package()</tt> function locates the package that you ask it for (in this case KDE4) and sets some variables describing the location of the package's headers and libraries. In this case we will use the <tt>KDE4_INCLUDES</tt> variable which contains the path to the KDE4 header files.

In order to allow the compiler to find these files, we pass that variable to the <tt>include_directories()</tt> function which adds the KDE4 headers to the header search path.

Next we create a variable called <tt>tutorial1_SRCS</tt> using the <tt>set()</tt> function. In this case we simply set it to the name of our only source file.

Then we use <tt>kde4_add_executable()</tt> to create an executable called <tt>tutorial1</tt> from the source files listed in our <tt>tutorial1_SRCS</tt> variable. Finally we link our executable to the KDE4 kdeui library using <tt>target_link_libraries()</tt> and the <tt>KDE4_KDEUI_LIBS</tt> variable which was set by the <tt>find_package()</tt> function.

====Make And Run====
Again, if you set up your environment as described in [[Getting_Started/Build/KDE4|Getting Started/Build/KDE4]], you can compile this code with:
cmakekde

Or if you did not:

mkdir build
cd build
cmake .. && make

And launch it as:
./tutorial1.shell

==Moving On==
Now you can move on to [[Development/Tutorials/Using_KXmlGuiWindow|using KXmlGuiWindow]].

[[Category:C++]]

KDE TechBase:Contributors

2007-12-21T14:36:47Z

Milliams: /* Reviewers and Article Writers */

Welcome to the contributors page.

'''This site contains a list of ''active'' contributors. It should help to build teams which maintain KDE TechBase's content. If you have questions about KDE TechBase you can ask/email the corresponding person.'''

Please add yourself to the list where appropriate. If you are inactive, please remove yourself again.

== Administrators ==

This is a list of KDE TechBase administrators.

* [[User:Danimo|Danimo]]
* [[User:Dhaumann|Dhaumann]], <dhaumann at kde dot org>

== Reviewers and Article Writers ==

If you are continuously reviewing KDE TechBase changes or writing articles add yourself to the list.

* [[User:Dhaumann|Dhaumann]], <dhaumann at kde dot org>
* [[User:Milliams|Milliams]]
* name, <email>

== Translation Teams ==

KDE TechBase is [[Help:Wiki Translation|translated]] into many languages. If you translate pages please add yourself to the right translation team.

=== Chinese(simplified) Team ===
* [[User:Liangqi|Liangqi]], cavendish.qi at gmail dot com
* name, <email>

=== German Team ===
* DrSlowDecay, kde at metalhorde dot de
* name, <email>

=== Italian Team ===
* [[User:Thunder Teaser|Thunder Teaser]], totokid at gmail dot com
* name, <email>

=== ... Team ===
* name, <email>

Projects/KDE Relicensing

2007-11-24T17:13:50Z

Milliams: /* Current Reply List */ Add name to relicensing

== KDE GPL v2.0 Relicensing effort ==

=== Why does it matter ? ===

A couple of KDE dependent projects or even libraries have moved or are going to move to GPLv3 ([http://gpl3.palamida.com:8080/ State of GPLv3 movement]).

Unfortunately, GPL v3 is incompatible with GPL v2. This means that it is not possible to create a project linking GPL v2 and v3 code together. There is no problem for projects which are licensed GPLv2+ (version 2 or above).

A few parts of KDE are currently licensed as GPLv2 only. So far we have no reason to believe that this was something other than an oversight. However, we still need to validate with the individual copyright holders that a relicense to GPLv2+ or GPLv2+v3 is okay with them.

Therefore, in an effort we're trying to identify the contributors that have contributed under the terms of GPLv2 and where the "+" part was not explicitly mentioned. If we know that all contributors agreed to a relicense, we can go ahead and flip the license of the individual source file.

== How can I help ? ==

By identifying a contributor who as contributed under the terms of GPLv2 (use '''kdesdk/scripts/relicensecheck.pl''' on the file in question or the [http://toma.kovoks.nl/kde/ Relicense Status Page]), and contacting him if he wasn't already contacted. Ask him the following questions:

* Are you okay with relicensing your contributions done under GPLv2 to GPLv2+?

* Are you okay with relicensing your contributions done under GPLv2 to GPLv2 or GPLv3 ?

* Are you okay with relicensing your contributions done under LGPLv2 to LGPLv2+?

* Are you okay with relicensing your contributions done under LGPLv2 to LGPLv2 or LGPLv3?

* Are you okay with the KDE e.V. deciding on a future licensing change to your code, should that be necessary?

=== Whats next? ===

# you checkout relicensecheck.pl from trunk/KDE/kdesdk/scripts
# you run it on the file or directory in question
# you interpret the result. check each commit that is being complained about carefully. Try to get the copyright's holder's permission. if you get it, update the whitelist in the script.
# review the list of declared copyright holders in the file.
# if you're all clear, change the license to the most liberal license possible. Document your change verbosely in the SVN commit log.

== Current Reply List ==

* Please keep the list sorted by family name!
* Please only use "YES" or "NO"

{| border="1"
! Name !! GPLv2->GPLv2+ !! LGPLv2 -> LGPLv2+ !! GPLv2 -> GPLv2+v3 !! LGPLv2 -> LGPLv2+LGPLv3 || KDE e.V. decides
|-
|Adam, Till || YES || YES || YES || YES || NO
|-
|Alsina, Roberto || YES || YES || YES || YES || YES
|-
|Armitage, Chani || YES || YES || YES || YES || YES
|-
|Bastian, Waldo || NO || NO || YES || YES || YES
|-
|Boemann, Casper || YES || YES || YES || YES || YES
|-
|Broadstone, Matt || NO || NO || YES || YES || YES
|-
|Connell, Charles || YES || YES || YES || YES || NO
|-
|Cullmann, Christoph || NO || NO || YES || YES || NO
|-
|Drummond, Craig || YES || YES || YES || YES || YES
|-
|Dymo, Alexander || YES || YES || YES || YES || NO
|-
|Edghill, Gregg || YES || YES || YES || YES || NO
|-
|Faure, David || YES || YES || YES || YES || YES
|-
|Granroth, Kurt || YES || YES || YES || YES || YES
|-
|Hausmann, Simon || YES || YES || YES || YES || YES
|-
|Hoeglund, Fredrik || NO || NO || YES || YES ||
|-
|Kainhofer, Reinhold || YES || YES || YES || YES || YES
|-
|Kellet, Alexander || YES || YES || YES || YES || YES
|-
|Knight, Robert || YES || YES || YES || YES || YES
|-
|Kretz, Matthias || NO || NO || YES || YES || NO
|-
|Kulow, Stephan || YES || YES || YES || YES || NO
|-
|Lunak, Lubos || YES || YES || YES || YES || NO
|-
|Mac-Vicar, Duncan || YES || YES || YES || YES || NO
|-
|Macieira, Thiago || YES || YES || YES || YES || YES
|-
|Mantia, Andras || NO || NO || YES || YES || YES
|-
|Martyn, Greg || YES || YES || YES || YES || YES
|-
|McGuire, Thomas || YES || YES || YES || YES || NO
|-
|Molkentin, Daniel || YES || YES || YES || YES || NO
|-
|Montel, Laurent || YES || YES || YES || YES || YES
|-
|Moore, Richard || NO || NO || YES || YES || YES
|-
|Mueller, Dirk || YES || YES || YES || YES || NO
|-
|Mutz, Marc || YES || YES || NO || NO || NO
|-
|Ottens, Kevin || YES || YES || YES || YES || YES
|-
|Pyne, Michael || YES || YES || YES || YES || YES
|-
|Raabe, Frerich || NO || NO || YES || YES || NO
|-
|Riddell, Jonathan || YES || YES || YES || YES || YES
|-
|Sand, Espen || YES || YES || || || YES
|-
|Schlaeger, Chris || NO || NO || YES || YES || NO
|-
|Schumacher, Cornelius || YES || YES || YES || YES || YES
|-
|Seigo, Aaron || YES || YES || YES || YES || YES
|-
|Soeken, Mathias || YES || YES || YES || YES || NO
|-
|Stephenson, Will || YES || YES || YES || YES || YES
|-
|Tapsell, John || YES || YES || YES || YES || YES
|-
|Toscano, Pino || YES || YES || YES || YES || YES
|-
|Trueg, Sebastian (Exception: K3b) || YES || YES || YES || YES || YES
|-
|Ventura-Whiting, Ian || YES || YES || YES || YES || YES
|-
|Wallin, Inge || YES || YES || YES || YES ||
|-
|Williams, Matt || YES || YES || YES || YES || YES
|-
|Wolfer, Urs || YES || YES || YES || YES || YES
|-
|Zachmann, Thorsten || YES || YES || YES || YES || NO
|-
|}

== Current TODO List ==

* KDAB
* Tobias Koenig
* Matthew Woehlke
* Daniel Teske
* Dawit Alemayehu
* Alex Zepeda
* Thomas Leitner
* Lars Knoll
* Kevin Ottens
* Maksim Orlovich
* Sirtaj Singh Kang
* Karol Szwed
* Thorsten Roeder
* Joseph Wenninger

== Current list of problematic Files ==

Tom Albers has written a webfrontend to '''relicensecheck.pl''', which makes it really easy to find files that can already be relicensed, or for those that can not it is possible to easily see (via tooltip) which commits are preventing it.

[http://toma.kovoks.nl/kde/ Visit the Relicensing Status Page]

== Relicensing progress ==

http://www.suse.de/~dmueller/licensing/files_KDE1.png

Projects/Games

2007-11-11T16:09:27Z

Milliams: /* IRC */ Update for next month

{{Template:I18n/Language Navigation Bar|Projects/Games}}
Intro to do

== The Game Categories ==
*[[/Arcade Games|Arcade games]]
*[[/Board Games|Board Games]]
*[[/Tactic and Strategy|Tactic and Strategy]]
*[[/Card Games|Card games]]

===See also===
* [http://doc.trolltech.com/4.2/qsvgrenderer.html QSvgRenderer Class Reference]
* [http://developer.kde.org/documentation/library/cvs-api/kdelibs-apidocs/kdecore/html/classKSvgRenderer.html KSvgRenderer Class Reference]
* [http://websvn.kde.org/trunk/KDE/kdegames/katomic/ KAtomic KDE4 code in websvn]
* [[Schedules/KDE4/4.0 Release Schedule]]

==Development==

* [[/Maintainers| Game's maintainers]]
* [[/UI and usability|UI and usability]]
* [[/libkdegames Usage|libkdegames Usage]]

==Status==

* [[/Status KDE 4.0|Status KDE 4.0]]
** [[/Documentation_progress|Documentation progress]]
** [[/Icons_ToDo|Icons_ToDo]]
* older pages:
** [[/Status_Ready|Ready]]
** [[/Status_Should_be_Ready|Should be ready]]
** [[/Status_Playground|kdegames playground (kdegame's candidate or unready) ]]
** [[/Status|old status page]]

==Meeting==

===IRC===

We are doing meeting on [irc://irc.kde.org/#kdegames IRC] every month to talk about the games development.

[[/IRC Meeting|Next Meeting : 1 December 20:00UTC]]

Projects/KDE on Windows/Installation

2007-11-06T11:35:21Z

Milliams: /* Download needed packages */ Fix link text

{{note|Perhaps actual developers should summarize status of KDE4 on Windows here, while we encourage users to describe their experiences on the [[Talk:{{PAGENAME}}|Talk page?]]}}

== KDE Installer for Windows ==
You can use this installer to download and install the
various binary packages that you need to run KDE applications on MS Windows.
KDE is free and open source so you can build all the applications "from scratch" from their source code;
but as a convenience for others,
volunteers create these precompiled packages and make them available on the Internet.

'''Disclaimer''' These are early days for KDE4 on Windows,
some programs work better than others and some fail to run altogether.

You can also use the KDE Installer for Windows to install source code and the packages that you need to ''build'' KDE4 on Windows
(although if you are building KDE4 on Windows you may prefer to use the emerge system to build KDE and its requirements from latest source);
see [[Getting Started/Build/KDE4/Windows]].

=== Summary of Steps ===
* Visit http://download.cegit.de/kde-windows/installer
* Download and save the latest version to a directory, e.g. <tt>C:\KDE4</tt>
* Run the installer, download what you need (see [[#Download needed packages]] below).
* Add your lib directory, e.g. <tt>C:\KDE4\lib</tt> to your Windows %PATH%. (Start > Control Panel > System > Advanced > Environment Variables, double-click the Path System Variable and this to your path separated by semicolon.)
* Add a KDEDIRS environment variable (Start > Control Panel > System > Advanced > Environment Variables, click [New] User variable and create Variable name <tt>KDEDIRS</tt> with Variable value the directory where you installed KDE4, e.g. <tt>C:\KDE4</tt>).
* Try running a Qt application in the <tt>bin</tt> directory, such as linguist.exe
* If that works, try running a KDE application such as <tt>kruler.exe</tt>.

=== Download needed packages ===
A single program in the The K Desktop Environment depends on many other libraries and packages; that is why each .exe is comparatively small.
The KDE Installer for Windows has some awareness of dependencies,
but not complete.
So, the first few times you try to run an application you may see alerts about missing DLLs.

If you do not intend to build from source, do not click "all" and do not click "src", as you do not need to download the source for each package. ''Unclear whether you need lib for each''.

There are two development systems for KDE on Windows,
Microsoft's Visual C and [http://en.wikipedia.org/wiki/MinGW MinGW].
Even if you are only running binaries and do not intend to build KDE4 yourself,
you need to choose between these.
As of October 2007, the former is more stable, so when you have a choice of packages in the KDE Installer for Windows, prefer the -msvc version.

The KDE programs themselves are organized into several groups: kdeedu, kdegames, and kdegraphics.

Here are some of the minimal packages you need to run a KDE application:
: dbus-msvc, kdewin32-msvc, qt-msvc, vcredist, ??

The Dependencies tab for a particular package lists some of the additional packages it needs.
However, the dependency checking currently only works for first-level dependencies
Other dependencies are not easy to determine in advance.
For example, if you install kdegames only with its dependencies,
you will not be able to start it because you also need libstreamanalyze
(for which you have to install the strigi package).

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries]] is a more complete list of libraries that a full installation needs.

If a download fails, then the KDE Installer fails.
If you have a broken file, you need to delete it
and then restart the KDE Installer to download it again.
You can also download and unpack files manually.

== Testing your installation ==
Navigate to the <tt>bin</tt> directory.

See if you can run the Qt program assistant.exe.
Qt programs have fewer dependencies than a full-blown KDE application.

If that works, try running a simple KDE application, such as kruler.exe from the kdegraphics package.

The first KDE application you run will start a console window in order to run the [http://en.wikipedia.org/wiki/D-Bus D-Bus daemon].

== Status ==

Using the kdewin-installer-gui-0.8.1-2.exe to install packages, dbus-daemon.exe starts up, and many games run.

It seems running kbuildsycoca4.exe by hand helps applications like KStars and Okular to run.

There are problems with the file open dialog:
* Besides I/O errors if you do not have KDEDIRS set (see elsewhere), you may see "Windows - No Disk" exceptions for each empty removable drive on your computer (floppy disk, CD-ROM, etc.). Click [Continue] for each one.

[[Category: MS Windows]]

Projects/Oxygen/Missing Icons

2007-11-04T14:22:42Z

Milliams: /* KDE main modules */ Remove duplicate ksquares

The page will help Oxygen team to track and produce icons that are currently missing in KDE4. Additionally it will help developers to make requests for icons that they need for KDE4 related projects.

= Instructions to fill out the request =

* This page, being a wiki, obviously does not validate your request. Please take care when providing information about the icons. Note that this page is mainly for the team to know where is mostly needed the work, we'll do our best to fullfill your requests for 4.0 but however we can't guarantee that. =)

* When providing icon names please try to make them compatible with the actual naming scheme.

* Please provide clear but short descriptions about the icons, it needs to help the artists in imagining a good metaphore to make your icon. '''This point is extremely important'''. You may obviously also link your description if it's going to be lengthy. This will help us to manage icon requests, and check if there are any possible duplicates. The most descriptive you are, the best it is for us.

* Screenshots are sometimes a better way to easily show the usage of the icon. Provide metaphores when possible this will help the artist to visualize our reqest faster and give a better understanding of the reqest.

* As someone already noted, this is not the right page to complain or make suggestions about existing icon, this is just to know the remaining work.

* Please sort by module/application/priority

= Missing Icons Table =

== General purpose icons ==
For icons like the folder, or the desktop.

{|rules="all" cellpadding="2" cellspacing="0" align=center style="border:1px solid #999; border-right:2px solid #999; border-bottom:2px solid #999;" width="100%"
|+
! style="background:#efefef;" | Icon Name
! style="background:#efefef;" | Description / Where can be found?
! style="background:#efefef;" | Done?
! style="background:#efefef;" | Assigned To
|-----
|| image-resize || an icon for an image resize action. || Done (See disscusion page) || dmiller
|-----
|| move || move action [[http://websvn.kde.org/branches/KDE/3.5/kdelibs/pics/crystalsvg/cr16-action-move.png?revision=438982&view=markup]] || No ||
|-----
|| application-javascript || Icon for *.js (application/javascript) files just like we have them for e.g. Python and Ruby. || No ||
|-----
|| application-x-php || Icon for *.php (application/x-php). || No ||
|-----
|| idea || KStandardAction for "Tip of the Day", for example seen in the help menu of KMail || No ||
|-----
|| item-locked || icon to show that an item or ui element is locked and will not move or disappear, such as a toolbar in a fullscreen window || No || Pinheiro
|-----
|| item-unlocked || icon to show that an item or ui element is unlocked and will move or disappear, such as a toolbar in a fullscreen window || No || Pinheiro
|-----
|| general-plugin || icon to show that there are plugins to enable, for example in a configuration dialog || ||
|-----
|-----
|| ordered-list || icon for indicating the creation of an ordered i.e. numbered list. Qt rich-text classes mean this will probably be used more often || ||
|-----
|| unordered-list || icon for indicating the creation of an unordered i.e. bulleted list. Qt rich-text classes mean this will probably be used more often || ||
|-----
|}

== KDE main modules ==
For apps in trunk/KDE/

{|rules="all" cellpadding="2" cellspacing="0" align=center style="border:1px solid #999; border-right:2px solid #999; border-bottom:2px solid #999;" width="100%"
|+
! style="background:#efefef;" | Module
! style="background:#efefef;" | Application
! style="background:#efefef;" | Icon Name
! style="background:#efefef;" | Description / Where can be found?
! style="background:#efefef;" | Done?
! style="background:#efefef;" | Assigned To
|-----
|| kdebase || konqueror || filetypes-association || konqueror configuration dialog File Associations || Done || Pinheiro
|-----
|| kdebase || konqueror || filter-page || konqueror configuration dialog AdBlock Filters || Done || Pinheiro
|-----
|| kdebase || konqueror || enhanced_browsing || konqueror configuration dialog Web Shortcuts || Done || Pinheiro
|-----
|| kdebase || konqueror || cache || konqueror configuration dialog Cache || Done || Pinheiro
|-----
|| kdebase || konqueror || proxy || konqueror configuration dialog Proxy || In progress || Pinheiro
|-----
|| kdebase || konqueror || fonts || konqueror configuration dialog Fonts || Done || Pinheiro
|-----
|| kdebase || konqueror || stylesheets || konqueror configuration dialog Stylesheets || Done || Pinheiro
|-----
|| kdebase || konqueror || cookies || konqueror configuration dialog Cookies || Done || Pinheiro
|-----
|| kdebase || konqueror || browser_identification || konqueror configuration dialog Browser Identification || Done 3/4 || Pinheiro
|-----
|| kdebase || konqueror || text_to_speech || Konqueror text-to-speech plugin || Done || Pinheiro
|-----
|| kdebase || kwin|| kwin-effect || Generic effect icon || In progress || Pinheiro
|-----
|| kdebase || kwin|| preferences-desktop-effects || Desktop effects config module || No ||
|-----
|| kdebase || kwin|| kwin-effect-boxswitch || Boxswitch (alt-tab) effect (low priority) || No ||
|-----
|| kdebase || kwin|| kwin-effect-desktopgrid || Desktopgrid (desktop switcher) effect (low priority) || No ||
|-----
|| kdebase || kwin|| kwin-effect-presentwindows || Presentwindows effect (low priority) || No ||
|-----
|| kdebase || kwin|| kwin-effect-shadow || Shadow effect (low priority) || No ||
|-----
|| kdebase || kwrite || kwrite || Previously existed, recently removed from SVN. See Misc requests below for details || Yes (renamed accessories-text-editor)||
|-----
|| kdebase || kwrite|| insert_file || KWrite insert file plugin || No ||
|-----
|| kdebase || kwrite || word_completion || KWrite word completion plugin || No ||
|-----
|| kdebase || systemsettings || preferences-desktop-color || Desktop colour settings configuration module || No ||
|-----
|| kdebase || systemsettings || preferences-desktop-icons || Desktop icon settings configuration module || No ||
|-----
|| kdebase || systemsettings || preferences-desktop-theme-manager || Desktop theme selector module || No ||
|-----
|| kdebase || systemsettings || preferences-desktop || Desktop configuration category || No ||
|-----
|| kdebase || systemsettings || preferences-system-network-sharing || Network shares config module || No ||
|-----
|| kdebase || systemsettings || preferences-desktop-launch-feedback || Launch feedback config module || No ||
|-----
|| kdebase || systemsettings || preferences-desktop-login || KDM/login manager config module || Done - named preferences-system-login [[User:Djmdave|Djmdave]] 14:27, 1 November 2007 (CET) || Dmiller
|-----
|| kdebase
|| kopete (misc) || (various) || Emoticons for Kopete, See http://techbase.kde.org/index.php?title=Projects/Oxygen/Missing_Emoticons || No ||
|-----
|| kdemultimedia || kmix|| kmix icons || KMix icons || No ||
|-----
|| koffice
|| (all)
|colspan="4"| See http://wiki.koffice.org/index.php?title=Icons
|-----
|| kdeedu || kalgebra || application || Application Icon kdeedu/kalgebra/icons || No ||
|-----
|| kdeedu || kig || application || Application Icon kdeedu/kig/kig || No ||
|-----
|| kdepim || kmail || identity || KMail configuration dialog for managing identities (I beleive actions/contact is meant for this - [[User:Djmdave|Djmdave]] 11:59, 28 October 2007 (CET))|| Done ||
|-----
|| kdepim || kmail || misc || KMail configuration dialog for miscellaneous configurations || No ||
|-----
|| kdepim || kmail || ? (goto-page was used before) || Action to mark all currently unread mails in one folder as read ("Mark All Messages as Read"), can be found in the "Folder" menu of KMail || No ||
|-----
|| kdepim || kmail || folder-sent-mail || Icon for folder where successfully sent mails are stored, as found on the left pane in KMail. || No ||
|-----
|| kdepim || kmail || mail_custom_reply || Reply to the currently selected message with a custom (user-created) template message. Found in the "Message->Reply Special" menu entry in KMail. || No ||
|-----
|| kdepim || kmail || mail_custom_reply_all || Reply to the currently selected message with a custom (user-created) template message, and send the message to every addressee (All which are in To, From and CC headers). Found in the "Message->Reply Special" menu entry in KMail. || No ||
|-----
|| kdepim || kmail || mail_custom_forward || Forward the currently selected message, using a custom (user-created) template message. Found in the "Message->Forward" menu entry in KMail. || No ||
|-----
|| kdepim || kmail || mail_post_to || Creates a new message, which will have the mailing list of the current folder as the recepient. Can be found in the context menu of a folder in KMail, but only after activating "Folder->Mailing List Management". || No ||
|-----
|| kdepim || kmail || mail_send_via ||"Send Queued Messages Via", sends all mails which currently are queued in the outbox, but pops up a menu first asking the user which of his outgoing accounts (SMTP servers) he wants to use. Can be found in the "File" menu of KMail. || No ||
|-----
|| kdepim || kalarm || kalarm || System tray icon, indicating alarms are enabled. Current icon is still the hicolor one. || No ||
|-----
|| kdepim || kalarm || kalarm_disabled || System tray icon, indicating alarms are disabled. Current icon still is the hicolor one. || No ||
|-----
|| kdepim || korganizer || timespent || Doesn't exist yet. an icon representing the new timespent view. || No || dmiller
|-----
|| kdepim || korganizer || timeline || Doesn't exist yet. an icon representing the new timeline view. || Done || dmiller
|-----
|| kdepim || korganizer || view-calendar-journal || Doesn't exist yet. an icon representing KOrganizer's journal view. || New ||
|-----
|| kdepim || korganizer || view-freebusy || Doesn't exist yet. an icon representing freebusy time in a calendar || New ||
|-----
|| kdesupport || strigi || strigi || Doesn't exist yet. It should be an owl.|| No ||
|-----
|| kdegames || bovo || bovo || Apps main icon || done || johann_ol
|-----
|| kdegames || katomic || katomic || Apps main icon || No ||
|-----
|| kdegames || kbattleship || kbattleship || Apps main icon || No ||
|-----
|| kdegames || kblackbox || kblackbox || Apps main icon || No ||
|-----
|| kdegames || kbounce || kbounce || Apps main icon || No ||
|-----
|| kdegames || kgoldrunner || kgoldrunner || Apps main icon || No ||
|-----
|| kdegames || kiriki || kiriki || Apps main icon || No ||
|-----
|| kdegames || kjumpingcube || kjumpingcube || Apps main icon || No ||
|-----
|| kdegames || klines || klines || Apps main icon || No ||
|-----
|| kdegames || kmahjongg || kmahjongg || Apps main icon || No ||
|-----
|| kdegames || kmines || kmines || Apps main icon || No ||
|-----
|| kdegames || knetwalk || knetwalk || Apps main icon || done || johann_ol & trouvnez
|-----
|| kdegames || kolf || kolf || Apps main icon || No ||
|-----
|| kdegames || konquest || konquest || Apps main icon || No ||
|-----
|| kdegames || kpat || kpat || Apps main icon || No ||
|-----
|| kdegames || kreversi || kreversi || Apps main icon || No ||
|-----
|| kdegames || ksame || ksame || Apps main icon || No ||
|-----
|| kdegames || kshisen || kshisen || Apps main icon || No ||
|-----
|| kdegames || kspaceduel || kspaceduel || Apps main icon || No ||
|-----
|| kdegames || ksquares || ksquares || Apps main icon || No ||
|-----
|| kdegames || ksudoku || ksudoku || Apps main icon || done || johann_ol
|-----
|| kdegames || ktuberling || ktuberling || Apps main icon || No ||
|-----
|| kdegames || kwin4 || kwin4 || Apps main icon || No ||
|-----
|| kdegames || lskat || lskat || Apps main icon || No ||
|-----
|| kdegames || libkdegames || games-config-options || Old ChooseGameType action, used in configuration panes, to specify game types, variations or options|| Done || piacentini
|-----
|| kdegames || libkdegames || games-solve || Solve action for games, used to be a wizard's wand|| Done || piacentini
|-----
|| kdegames || libkmahjongg || games-config-tiles || Configuration pane icon, used to select the tileset in kmahjongg and kshisen. Could be possibly created from the tilesets SVG graphics in kdegames/libkmahjongg/tilesets|| Done || piacentini
|-----
|| kdegames || libkmahjongg || games-config-background || Configuration pane icon, used to select the field background in kmahjongg and kshisen. Could be reused by other games as a generic background icon|| Done || piacentini
|-----
|| kdegames || libkmahjongg || games-config-board || Configuration pane icon, used to select the board layout in kmahjongg and kshisen. Could be reused by other games as a generic configure levels/boards icon|| Done || piacentini
|-----
|| kdegames || libkdegames || games-config-theme || Configuration pane icon, used to select the KGameTheme to be used|| Done || piacentini
|-----
|| kdegames || libkdegames || games-config-custom || Configuration pane icon, used to configure custom game options, or complex settings|| Done || piacentini
|-----
|| kdegames || libkdegames || games-endturn || End turn checkmark|| Done || piacentini
|-----
|| kdenetwork || krdc || krdc-viewonly || Toggles the remote view viewonly / view-control mode. Viewonly means, that the remote desktop shows all updates, but the client does not send actions back to the server. At the moment the kgpg-sign-kgpg is used there. --[[User:Uwolfer|Uwolfer]] 23:11, 28 October 2007 (CET) || No ||
|-----
|| kdenetwork || kget || connect-creating || Shown while trying to connect to a server. --[[User:Uwolfer|Uwolfer]] 21:05, 29 October 2007 (CET) || No ||
|-----
|| kdenetwork || kopete || kopeteavailable || Icon representing the user in an online state. Used to set status to online || No ||
|-----
|| kdenetwork || kopete || kopeteaway || Icon representing the user in an away state. Used to set status to away. NB for this and the following kopetebusy there are overlay icons (small clock faces etc) in kdenetwork/kopete/icons that are used to generate contact status icons at runtime. It would be good if these icons were consistent with the overlay icons || No ||
|-----
|| kdenetwork || kopete || kopetebusy || Icon representing the user in an away state. Used to set status to busy || No ||
|-----
|| kdenetwork || kopete || metacontact_away || Icon representing an IM contact in an away state. Used in the contact list || No ||
|-----
|| kdenetwork || kopete || metacontact_online || Icon representing an IM contact in an online state. Used in the contact list || No ||
|-----
|| kdenetwork || kopete || metacontact_offline || Icon representing an IM contact in an offline state. Used in the contact list || No ||
|-----
|| kdenetwork || kopete || metacontact_unknown || Icon representing the user in an unknown state. Used in the contact list || No ||
|-----
|| kdenetwork || kopete || kopete_plugin || Generic icon for extensions - please no literal 'plug' icon as we use this already for network connections || No ||
|-----
|| kdenetwork || kopete || kopete_privacy || Configuring privacy settings || No ||
|-----
|| kdenetwork || kopete || kopete_texteffect || Configuring text formatting special effects || No ||
|-----
|| kdenetwork || kopete || kopete_autoreplace || Configuring text autocorrect rules || No ||
|-----
|| kdenetwork || kopete || highlight || Configuring text highlighting - icon exists but only in a low resolution || No ||
|-----
|| kdenetwork || kopete || urlpicpreview || icon exists but only in a low resolution || No ||
|-----
|| kdenetwork || kopete || newmsg || icon flashed in system tray when new messages are received || No ||
|-----
|| kdeutils || kwalletmanager || wallet_open|| kwalletmanager system tray icon when a wallet is open || No ||
|-----
|| kdeutils || kwalletmanager || wallet_closed || kwalletmanager system tray icon when a wallet is close || No ||
|-----
|| kdeutils || kwalletmanager || kwalletmanager || kwalletmanager application icon || No ||
|-----
|}

== Other 3rd party Application Icons ==
For all the other applications

{|rules="all" cellpadding="2" cellspacing="0" align=center style="border:1px solid #999; border-right:2px solid #999; border-bottom:2px solid #999;" width="100%"
|+
! style="background:#efefef;" | Application
! style="background:#efefef;" | Icon Name
! style="background:#efefef;" | Description / Where can be found?
! style="background:#efefef;" | Done?
! style="background:#efefef;" | Assigned To
|-----
|| KSystemlog || KSystemLog icon || [http://websvn.kde.org/trunk/playground/sysadmin/ksystemlog/src/hi128-app-ksystemlog.png?view=markup App icon] - Made by a non-graphic designer developer ;-) || Done (utilites-log-viewer) || dmiller
|-----
|| Tagua || tagua || [http://www.tagua-project.org/chrome/site/banner.png Tagua logo] || Done (in apps) || dmiller
|-----
|| Tagua || tagua-movelist || toggle [http://www.tagua-project.org/attachment/wiki/Screenshots/nested1.png movelist] Suggestion: I beleive the actions/history.png icon would be most suitable? - [[User:Djmdave|Djmdave]] 19:13, 26 October 2007 (CEST)|| Yes - Use actions/history.png ||
|-----
|| Amarok || amarok ||
[http://websvn.kde.org/trunk/extragear/multimedia/amarok/src/images/amarok_icon.svg App icon]. Needs Oxygen colors, we don't really want to change design.
|| No
||
|-----
|| Firefox || firefox || [http://en.www.mozilla.com/img/products/firefox-title.jpg Firefox logo] || No ||
|-----
|| GIMP || gimp || [http://upload.wikimedia.org/wikipedia/commons/5/55/GIMP_Icon.png GIMP logo] || No ||
|-----
|}

= Misc Icon Requests =
* Please see my request on http://www.nabble.com/Suggestion-for-Oxygen:-Highlight-difference-between-Kate-and-KWrite-t4447769.html and the bug report to help you track this wish at: https://bugs.kde.org/show_bug.cgi?id=138170.
Update:Thanks Djmdave, for moving this here. Now the KWrite icon is totally missing. See: http://websvn.kde.org/trunk/KDE/kdebase/runtime/pics/oxygen/128x128/apps/kwrite.png?view=markup and other corresponding directories (scalable 64x64 etc). My request for two distinct icons for Kate and KWrite stands. Please see bug for more details and discussion.

Projects/Oxygen/Missing Icons

2007-10-26T18:13:10Z

Milliams: /* KDE main modules */

Development/Tutorials/Using KXmlGuiWindow (ru)

2007-08-04T14:53:34Z

Milliams: KMainWindow → KXmlGuiWindow

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

series=Beginner Tutorial|

name=Использование KXmlGuiWindow|

pre=[[Development/Tutorials/First_program|Урок 1 - Hello World]]|

next=[[Development/Tutorials/Using_KActions|Урок 3 - KActions and XmlGui]]|

reading={{class|KXmlGuiWindow}}
}}

==Введение==
Это продолжение [[Development/Tutorials/First_program|урока по созданию первой программы]], здесь представлена базовая информация по классу {{class|KXmlGuiWindow}}.

В предыдущем уроке рассказывалось как создать всплывающее диалоговое окно, теперь мы сделаем первые шаги по созданию полноценного функционального приложения.

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

==Использование KXmlGuiWindow==

Чтобы получить пользу on KXmlGuiWindow, следует создать производный от него класс. Наш код находится в двух файлах: <tt>mainwindow.cpp</tt> и <tt>mainwindow.h</tt>. Класс KXmlGuiWindow выбран базовым, так как с помощью него можно использовать XML, например, чтобы определить структуру меню нашего приложения.

===mainwindow.h===
<code cppqt>
#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
};

#endif
</code>
Сначала в строке 7 мы объявляем производный от KXmlGuiWindow класс: <tt>class MainWindow : public KXmlGuiWindow</tt>, а затем - конструктор <tt>MainWindow(QWidget *parent=0);</tt>.

И наконец, объявляем указатель на объект, который станет главной частью нашей программы. {{class|KTextEdit}} является базовым редактором текста в формате richtext, поддерживающем некоторые вкусности KDE, как, например, автоматическое скрытие курсора.

===mainwindow.cpp===
<code cppqt>
#include "mainwindow.h"

MainWindow::MainWindow(QWidget *parent) : KXmlGuiWindow(parent)
{
textArea = new KTextEdit;
setCentralWidget(textArea);
setupGUI();
}
</code>
Сначала, конечно же, в строке 1 мы включаем заголовочный файл, содержащий объявление класса.

В строке 5 создаётся объект нашего текстового редактора. Затем в строке 6 мы используем встроенную функцию setCentralWidget(), указывающую KXmlGuiWindow, что должно находиться в центральной секции нашего окна.

Наконец, вызывается функция KXmlGuiWindow::setupGUI(), фоново выполняющая много различных действий по инициализации GUI и создающая панель меню по умолчанию (Settings, Help).

==Создание main.cpp==
Чтобы завершить создание приложение, нужно написать пару строк в main.cpp:
===main.cpp===
<code cppqt>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial2", 0,
ki18n("Tutorial 2"), "1.0",
ki18n("A simple text area"),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KApplication app;

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

return app.exec();
}
</code>
Новыми (по сравнению с Уроком 1) являются только строки 18 и 19. В строке 18 мы создаём объект MainWindow и в строке 17 делаем его видимым.

==CMake==
Наилучший способ собрать наше приложение - использовать CMake. Все изменения по сравнению с уроком 1 заключаются в добавлении файла <tt>mainwindow.cpp</tt> в список исходников и смене названия <tt>tutorial1</tt> на <tt>tutorial2</tt>.

===CMakeLists.txt===
<code ini>
project (tutorial2)

find_package(KDE4 REQUIRED)
include_directories( ${KDE4_INCLUDES} )

set(tutorial2_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial2 ${tutorial2_SRCS})
target_link_libraries( tutorial2 ${KDE4_KDEUI_LIBS})
</code>

===Компиляция===
Чтобы скомпилировать, слинковать и запустить приложение, выполните:
cmake . && make && ./tutorial2

==Продолжим изучение==
Теперь можно перейти к статье о [[Development/Tutorials/Using_KActions|KActions]].

[[Category:C++]]

Development/Tutorials/Using KXmlGuiWindow

2007-08-04T14:52:36Z

Milliams: KMainWindow → KXmlGuiWindow

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

series=Beginner Tutorial|

name=How To Use KXmlGuiWindow|

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

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

reading={{class|KXmlGuiWindow}}
}}

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

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

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

==Using KXmlGuiWindow==

In order to have a useful KXmlGuiWindow, we must subclass it. So we create two files, a <tt>mainwindow.cpp</tt> and a <tt>mainwindow.h</tt> which will contain our code. Our class inherits from KXmlGuiWindow because it uses XML e.g. to define the application's menu structure.

===mainwindow.h===
<code cppqt>
#ifndef MAINWINDOW_H
#define MAINWINDOW_H

#include <KXmlGuiWindow>
#include <KTextEdit>

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

private:
KTextEdit* textArea;
};

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

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

And finally we declare a pointer to the object that will make up the bulk of our program. {{class|KTextEdit}} is a generic richtext editor with some KDE niceties like cursor auto-hiding.

===mainwindow.cpp===
<code cppqt>
#include "mainwindow.h"

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

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

Finally, KXmlGuiWindow::setupGUI() is called which does a lot of behind-the-scenes stuff and creates the default menu bars (Settings, Help).

==Back to main.cpp==
In order to actually run this window, we need to add a few lines in main.cpp:
===main.cpp===
<code cppqt>
#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>

#include "mainwindow.h"

int main (int argc, char *argv[])
{
KAboutData aboutData( "tutorial2", 0,
ki18n("Tutorial 2"), "1.0",
ki18n("A simple text area"),
KAboutData::License_GPL,
ki18n("Copyright (c) 2007 Developer") );
KCmdLineArgs::init( argc, argv, &aboutData );

KApplication app;

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

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

==CMake==
The best way to build the program is to use CMake. All that's changed since tutorial 1 is that <tt>mainwindow.cpp</tt> has been added to the sources list and any <tt>tutorial1</tt> has become <tt>tutorial2</tt>.
===CMakeLists.txt===
<code ini>
project (tutorial2)

find_package(KDE4 REQUIRED)
include_directories( ${KDE4_INCLUDES} )

set(tutorial2_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial2 ${tutorial2_SRCS})
target_link_libraries( tutorial2 ${KDE4_KDEUI_LIBS})
</code>

===Compile it===
To compile, link and run it, use:
cmake . && make && ./tutorial2

==Moving On==
Now you can move on to [[Development/Tutorials/Using_KActions|using KActions]].

[[Category:C++]]