KDE TechBase - User contributions [en]

Schedules/KDE4/4.10 Feature Plan

2012-11-22T19:20:12Z

Rhabacker: /* kdesdk */

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

See also:

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

 Legend:

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

__TOC__

 

= kdelibs =

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

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

= kde-runtime =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|kio-mtp|KIO-Slave for MTP|philschmidt@gmx.net|Philipp Schmidt}}
{{FeatureDone|QML Containments|Making it possible to do full-featured containments in QML|sebas@kde.org|Sebastian Kügler}}
{{FeatureDone|nepomuk-indexer|New Nepomuk Indexer|me@vhanda.in|Vishesh Handa}}
{{FeatureDone|nepomukbackup|Nepomuk Backup rewritten from scratch|me@vhanda.in|Vishesh Handa}}
{{FeatureDone|nepomukcleaner|An application to port/clean invalid/legacy data in Nepomuk|me@vhanda.in|Vishesh Handa}}
{{FeatureDone|nepomuk KCM|Rewrite the Nepomuk KCM|me@vhanda.in|Vishesh Handa}}
{{FeatureDone|nepomuk tags|Nepomuk Tags KIO Slave|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomuk filemetadatawidget|Nepomuk Metadata Widget|me@vhanda.in|Vishesh Handa}}
|}
 

= kde-workspace =

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

! Status
! Project
! Description
! Contact

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


{{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Medium focus stealing prevention should also prevent focus stealing when the timestamp on the active window is uncertain ({{bug |304746}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Usability issue: "Attach as tab to" menu can be empty ({{bug |306451}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Display application menu and title bar side by side for maximized windows ({{bug |102607}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Add support for appmenu-qt ({{bug |266596}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Import Scripted Effect from All Effets Tab ({{bug |296772}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|GHNS support for Scripted Effects ({{bug |296773}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|Remove legacy window decorations ({{bug |299144}}, Review 104281)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Get rid of "Display borders on maximized windows" setting ({{bug |299245}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Cube animation on border approach should not be used unless the electric borders are actually in use and the config should be disabled, align or hint the electric border configuration ({{bug |299901}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Make ShaderManager act as a real stack ({{bug |300349}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|clientPopup: "'More actions' and "Attach as tab to" lack mnemonics ({{bug |302833}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Make KWin compile with C++11 ({{bug |303313}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Copy all useful Client properties to Deleted ({{bug |303916}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Display content of resizing/moving windows: KDE-Help shows obsolete instructions ({{bug |305297}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Mouse action support for sending window to different activity ({{bug |305758}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Windows list icon does not show up in "Walk Through Desktop List" ({{bug |306187}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Game mode ({{bug |306448}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Animate Window Maximize/Restore ({{bug |308990}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Common animation settings for effects of same type ({{bug |308991}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Use Resize Area in Aurorae ({{bug |308992}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Configurable quick tile area config GUI ({{bug |308993}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Move ExtendedBorderRegion to stable API ({{bug |308994}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Support shortened titles like in bespin in all decorations ({{bug |308995}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|Mouse Click effect ({{bug |309006}}, Review 105780)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Decorations not visible ({{bug |305875}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|drag-and-drop between windows by cover switch alt-tab causes apps to crash ({{bug |179077}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add a rule to select the screen ({{bug |183996}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: Need Mouse navigation in flip switch mode ({{bug |244439}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Request category for scripted KWin Effects on kde-(look<nowiki>|</nowiki>app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Request category for KWin Scripts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Request category for Window Switcher Layouts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Allow direct rendering with fglrx ({{bug |301103}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Don't use OpenGL matrix stack in OpenGL 2 backend ({{bug |303093}}, Review 105455)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Refactor Screen/Window PaintData ({{bug |303314}}, Review 105141)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Rapid flickering in locked screen -- makes it difficult to unlock ({{bug |303579}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|double click menu to close needs GUI config ({{bug |305738}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Toplevel::windowType() needs performance improvements ({{bug |306384}}, Review 106349)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|GLPlatform should recommend either OpenGL1 or OpenGL2 compositing ({{bug |306436}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Zoom effect broken in master ({{bug |307609}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|kwin fails to build when the GLES support is disabled ({{bug |307866}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|[JJ] Some effect authors are listed as "Name1 & Name2" ({{bug |307928}}, Review 106880)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add screen management actions to window context menus ({{bug |269207}}, Review 106065)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Move Workspace's compositing functionality to own class Compositor ({{bug |299277}}, Review 102420)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Option to disable close on double click in Aurorae ({{bug |301327}}, Review 106160)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Remove Tiling Support From KWin ({{bug |303090}}, Review 105546)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Allow Scripts to add menus to useractions menu ({{bug |303756}}, Review 106285)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Generic QML support for Aurorae Themes ({{bug |303810}}, Review 105768)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Split out Useractions Menu from Workspace ({{bug |305832}}, Review 106085)|mgraesslin@kde.org}}


{{FeatureDone|kwin|Implement color correction|skeletk13@gmail.com|Casian Andrei}}
{{FeatureDone|oxygen decoration|Implement ExtendedBorderRegion support, to resize windows outside of their actual borders|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureDone|oxygen style|Implement BlurBehind semi-transparent tooltips when available|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureDone|plasma-wallpapers|Color wallpaper: add listview to display thumbnails for background mode|rshah0385@kireihana.com|Reza Fatahilah Shah}}
{{FeatureDone|plasma workspace|Port Notifications applet to QML|mart@kde.org|Marco Martin}}
{{FeatureInProgress|plasma workspace|Port Task Manager applets to QML|hein@kde.org|Eike Hein (Sho_)}}
{{FeatureInProgress|plasma workspace|refresh Air Plasma theme|mart@kde.org|Marco Martin}}
{{FeatureInProgress|plasma workspace|Port Kickoff to qml|yellowcake-@gmx.net|Greg T}}
{{FeatureTodo|systemsettings|Replace krandr KCM by libkscreen-based one|dvratil@redhat.com|Dan Vrátil}}
{{FeatureInProgress|plasma workspace|Port rssnow to qml|terietor@gmail.com|Giorgos Tsiapaliokas}}
{{FeatureInProgress|various|KActivities/SLC support for most our applications|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|plasma workspace|first desktop SLC applet release|mart@kde.org|Marco Martin}}
{{FeatureDone|System Tray|System tray with interface in QML|dmitry.ashkadov@gmail.com|Dmitry Ashkadov}}
{{FeatureTodo|plasma workspace|Top-rated documents for Task Manager|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|systemsettings|Keyboard layout preview|amourphious1992@gmail.com|Shivam Makkar}}
{{FeatureInProgress|window manager|Rework and optimize vertex specification|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|window manager|Dynamic shader generation|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|window manager|Partial port to xcb|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|window manager|New launch feedback effect|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|activities|Encrypted activities|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|powerdevil|Overhaul powerdevil notifications|kde@privat.broulik.de|Kai Uwe Broulik}}
{{FeatureInProgress|powerdevil|Improve profile error handling (DPMS)|kde@privat.broulik.de|Kai Uwe Broulik}}
{{FeatureTodo|plasma workspace|Social Feed|mklapetek@kde.org|Martin Klapetek}}
|}
 

= kde-baseapps =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|FolderView|Split into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}
{{FeatureTodo|FolderView|Port to QML|ignat.semenov@blue-systems.com|Ignat Semenov}}

{{FeatureTodo|Dolphin|Implement files quick preview feature (named Klook) |evgeniy.augin@osinit.ru|Evgeniy Auzhin}}
{{FeatureDone|Dolphin|Implement parallel sort algorithm|emmanuelpescosta099@gmail.com|Emmanuel Pescosta}}
{{FeatureDone|Dolphin|Add GUI option for the "Rename Inline" setting|frank78ac@googlemail.com|Frank Reininghaus}}
{{FeatureDone|Dolphin|Add "Icon Size" submenu to the Places Panel context menu|frank78ac@googlemail.com|Frank Reininghaus}}

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

{{FeatureDone|Kate|Support for Python plugins|srhaque@theiet.org|Shaheed Haque}}
{{FeatureDone|Kate|Advanced gid(1) plugin using both ID files and etags|srhaque@theiet.org|Shaheed Haque}}
{{FeatureTodo|Kate|As-you-type search for the search plugin|kare.sars@iki.fi|Kåre Särs}}
{{FeatureTodo|Kate|Session name API for plugins + automatic ctags database naming|kare.sars@iki.fi|Kåre Särs}}
{{FeatureInProgress|Kate|Add optional document "minimap" to the Symbols view plugin|kare.sars@iki.fi|Kåre Särs}}
{{FeatureInProgress|Kate|Vim Mode Macro support|kdedevel@etothepiplusone.com|Simon St James}}
{{FeatureDone|Kate|Built-in quick open (Ctrl+Alt+o)|kwrite-devel@kde.org|Christoph Cullmann}}
{{FeatureDone|Kate|[http://kate-editor.org/2012/11/02/using-the-projects-plugin-in-kate/ New Project Plugin]|kwrite-devel@kde.org|Christoph Cullmann}}
{{FeatureDone|Kate Part|[http://kate-editor.org/2012/11/06/passive-notifications-in-kate-part/ Passive Notification System]|kwrite-devel@kde.org|Dominik Haumann}}
{{FeatureDone|Kate Part|[http://kate-editor.org/2012/11/05/loading-remote-files/ Loading Remote File Notification]|kwrite-devel@kde.org|Christoph Cullmann}}

{{FeatureDone|Kate Part|[http://kate-editor.org/2012/10/28/show-line-while-scrolling/ Show line while scrolling]|kwrite-devel@kde.org|D. Haumann/J. Wenninger}}
{{FeatureDone|Kate Part|[http://kate-editor.org/2012/10/27/remove-trailing-spaces/ Improved remove trailing spaces on save]|kwrite-devel@kde.org|Dominik Haumann}}
{{FeatureDone|Kate Part|[http://kate-editor.org/2012/11/07/default-color-schemas/ Predefined color schemes]|kwrite-devel@kde.org|C. Cullmann/D. Haumann}}
{{FeatureDone|Kate Part|[http://kate-editor.org/2012/11/06/kate-scripting-updates-zen-like-quick-coding/ Improved Scripting Support]|kwrite-devel@kde.org|C. Cullmann/D. Haumann}}

{{FeatureTodo|Kdialog|Add support for detailedsorry/detailederror messages|kde@privat.broulik.de|Kai Uwe Broulik}}

{{FeatureTodo|Konsole|Improve the search filter bar|francesco.cecconi@gmail.com|Francesco Cecconi}}
{{FeatureTodo|Konsole|Add the --separate cmdline option for running in new process|adaptee@gmail.com|Jekyll Wu}}
{{FeatureTodo|Konsole|Make the d&d popup menu optional|adaptee@gmail.com|Jekyll Wu}}

{{FeatureTodo|Konqueror|Settings for WebKit Part|sandfeld@kde.org|Allan Sandfeld}}
|}
 

= kdeedu =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|Marble|Have support for "repeatX" in the projection classes|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Mars & Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Foursquare plugin|utkuaydin34@gmail.com|Utku Aydın}}
{{FeatureTodo|Marble|Marble Touch on Android (including SOK branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|OSM vector rendering (GSOC branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Zoom to content of geo file after loading (at least on start-up)|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Marble|Geo files thumbnailer|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Marble|Geo files metadata extractor|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Rocs|Improve project handling: load/save dialogs, add project journal.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Support TGF (trivial graph format) documents for import/export.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Support core features for DOT/Graphvis documents for import/export.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Add TikZ/PGF graphic export.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Main Window UI Reorganization: Editor Toolbar, dialogs, Information Panel|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Configuration Dialog Optimizations: Code-Editor, Graph Editor|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Data Structure Backend wise iconsets and preconfigurations for types|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Printing and image export of graphs.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Data Structure Snapshot and Recovery.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Visual Graph Editor Handling: copy&paste, data structure focus, property display|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|KTouch|Ship ktouch/next|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureDone|KTouch|Smart resizing of training screen with aligned vertical lines|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureDone|KTouch|Prominent hint during training if the user makes repeatedly errors|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureDone|KTouch|Show course descriptions in course selector|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureDone|KTouch|Show a message when keyboard layout visualization isn't available due missing data|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureDone|Analitza|New plotting framework|percy.camilo.ta@gmail.com|Percy Camilo Triveño Aucahuasi}}
{{FeatureDone|KAlgebra|Splitted the QML Components from KAlgebraMobile|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra|New plotting plasmoid graphs, in QtQuick|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|Pairs|Pairs Theme editor|marco.calignano@gmail.com|Marco Calignano}}
{{FeatureInProgress|Cantor|Python backend|filipe@kde.org|Filipe Saraiva}}
{{FeatureInProgress|Kig|Mark right angles|david.narvaez@computer.org|David E. Narváez}}
|}
 

= kdegames=

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

! Status
! Project
! Description
! Contact

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

= kdegraphics=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|libkipi|[http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/dodonvictor/10002 Porting libkipi to KDE-XML GUI]|dodonvictor@gmail.com|Victor Dodon}}
{{FeatureInProgress|okular|Tiled rendering|okular-devel@kde.org|Okular Developers}}
{{FeatureDone|Gwenview|Recursive importer|agateau@kde.org|Aurélien Gâteau}}
{{FeatureDone|Gwenview|Color profile support|agateau@kde.org|Aurélien Gâteau}}

|}
 

= kdemultimedia =

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

! Status
! Project
! Description
! Contact

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

|}
 

= kdenetwork=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|KGet|Metalink/HTTP Support|dahalaishraj@gmail.com|Aish Raj Dahal}}

|}
 

= kdepim =

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

! Status
! Project
! Description
! Contact
{{FeatureTodo|Facebook resource|Include it in default install|martin.klapetek@gmail.com|Martin Klapetek}}
{{FeatureInProgress|Akregator2|Merge in kdepim|montel@kde.org|Montel Laurent}}
{{FeatureInProgress|Knode|Merge in KMail|montel@kde.org|Montel Laurent}}
{{FeatureInProgress|BackupMail|Extend backup to all kdepim apps|montel@kde.org|Montel Laurent}}
{{FeatureInProgress|Sieve|Rewrite dialogbox|montel@kde.org|Montel Laurent}}
{{FeatureInProgress|libs|Move folderview to kdepimlibs/akonadi|montel@kde.org|Montel Laurent}}
{{FeatureInProgress|kolab-resource|Make Kolab 3.0 option available|mollekopf@kolabsys.com|Christian Mollekopf}}
{{FeatureDone|KAlarm|Add command line and D-Bus option to output list of scheduled alarms|djarvie@kde.org|David Jarvie}}
|}
 

= kdeplasma-addons =

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

! Status
! Project
! Description
! Contact
{{FeatureInProgress|Microblog|replace with QML version|sebas@kde.org|Sebastian Kügler}}
{{FeatureTodo|StackFolder|Add applet for quick browse the stack of folders|ural.mullabaev@rosalab.ru|Ural Mullabaev}}
{{FeatureDone|ComicStrip|Replace with QML version|rshah0385@kireihana.com|Reza Fatahilah Shah}}
{{FeatureDone|Calculator|Replace with QML version|luizromario@gmail.com|Luiz Romário Santana Rios}}
{{FeatureDone|QML Wallpapers|Make it possible to have animated wallpapers written in QtQuick technologies.|aleixpol@blue-systems.com|Aleix Pol Gonzalez}}
{{FeatureDone|Dictionary KRunner|Look up words in the dictionary by typing in 'define {word}' in krunner. [http://blog.zx2c4.com/808 Blog]|Jason@zx2c4.com|Jason A. Donenfeld}}
{{FeatureInProgress|Eyes|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|FifteenPuzzle|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|Luna|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|Timer|replace with QML version|bettio@kde.org|Davide Bettio}}
|}
 

= kdesdk =

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

 

= kdeutils=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|Ark|Make it possible to disable internal previewer|kde@privat.broulik.de|Kai Uwe Broulik}}
|}

Documentation/tutorials/kparts

2012-11-16T18:13:43Z

Rhabacker: fixed link

#REDIRECT [[Development/Tutorials/Using_KParts]]

Documentation/tutorials/kparts

2012-11-16T18:10:52Z

Rhabacker: There is a wikipedia link to this page, which is otherwise broken

#REDIRECT [[/Development/Tutorials/Using_KParts]]

Schedules/KDE4/4.10 Feature Plan

2012-10-25T19:09:49Z

Rhabacker: /* kdesdk */

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

See also:

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

 Legend:

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

__TOC__

 

= kdelibs =

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

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

= kde-runtime =

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|kio-mtp|KIO-Slave for MTP|philschmidt@gmx.net|Philipp Schmidt}}
{{FeatureInProgress|QML Containments|Making it possible to do full-featured containments in QML|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|nepomuk-indexer|New Nepomuk Indexer|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomukbakcup|Nepomuk Backup rewritten from scratch|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomukcleaner|An application to port/clean invalid/legacy data in Nepomuk|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomuk KCM|Rewrite the Nepomuk KCM|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomuk tags|Nepomuk Tags KIO Slave|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomuk filemetadtawdiget|Nepomuk Metadata Widget|me@vhanda.in|Vishesh Handa}}
|}
 

= kde-workspace =

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

! Status
! Project
! Description
! Contact

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


{{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Medium focus stealing prevention should also prevent focus stealing when the timestamp on the active window is uncertain ({{bug |304746}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Usability issue: "Attach as tab to" menu can be empty ({{bug |306451}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Display application menu and title bar side by side for maximized windows ({{bug |102607}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Add support for appmenu-qt ({{bug |266596}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Import Scripted Effect from All Effets Tab ({{bug |296772}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|GHNS support for Scripted Effects ({{bug |296773}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|Remove legacy window decorations ({{bug |299144}}, Review 104281)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Get rid of "Display borders on maximized windows" setting ({{bug |299245}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Cube animation on border approach should not be used unless the electric borders are actually in use and the config should be disabled, align or hint the electric border configuration ({{bug |299901}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Make ShaderManager act as a real stack ({{bug |300349}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|clientPopup: "'More actions' and "Attach as tab to" lack mnemonics ({{bug |302833}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Make KWin compile with C++11 ({{bug |303313}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Copy all useful Client properties to Deleted ({{bug |303916}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Display content of resizing/moving windows: KDE-Help shows obsolete instructions ({{bug |305297}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Mouse action support for sending window to different activity ({{bug |305758}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Windows list icon does not show up in "Walk Through Desktop List" ({{bug |306187}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Game mode ({{bug |306448}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Animate Window Maximize/Restore ({{bug |308990}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Common animation settings for effects of same type ({{bug |308991}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Use Resize Area in Aurorae ({{bug |308992}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Configurable quick tile area ({{bug |308993}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Decorations not visible ({{bug |305875}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|drag-and-drop between windows by cover switch alt-tab causes apps to crash ({{bug |179077}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add a rule to select the screen ({{bug |183996}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: Need Mouse navigation in flip switch mode ({{bug |244439}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Request category for scripted KWin Effects on kde-(look<nowiki>|</nowiki>app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Request category for KWin Scripts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Request category for Window Switcher Layouts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Allow direct rendering with fglrx ({{bug |301103}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Don't use OpenGL matrix stack in OpenGL 2 backend ({{bug |303093}}, Review 105455)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Refactor Screen/Window PaintData ({{bug |303314}}, Review 105141)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Rapid flickering in locked screen -- makes it difficult to unlock ({{bug |303579}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|double click menu to close needs GUI config ({{bug |305738}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Toplevel::windowType() needs performance improvements ({{bug |306384}}, Review 106349)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|GLPlatform should recommend either OpenGL1 or OpenGL2 compositing ({{bug |306436}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Zoom effect broken in master ({{bug |307609}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|kwin fails to build when the GLES support is disabled ({{bug |307866}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|[JJ] Some effect authors are listed as "Name1 & Name2" ({{bug |307928}}, Review 106880)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add screen management actions to window context menus ({{bug |269207}}, Review 106065)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Move Workspace's compositing functionality to own class Compositor ({{bug |299277}}, Review 102420)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Option to disable close on double click in Aurorae ({{bug |301327}}, Review 106160)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Remove Tiling Support From KWin ({{bug |303090}}, Review 105546)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Allow Scripts to add menus to useractions menu ({{bug |303756}}, Review 106285)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Generic QML support for Aurorae Themes ({{bug |303810}}, Review 105768)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Split out Useractions Menu from Workspace ({{bug |305832}}, Review 106085)|mgraesslin@kde.org}}


{{FeatureInProgress|oxygen decoration|Implement ExtendedBorderRegion support, to resize windows outside of their actual borders|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureDone|oxygen style|Implement BlurBehind semi-transparent tooltips when available|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureDone|plasma-wallpapers|Color wallpaper: add listview to display thumbnails for background mode|rshah0385@kireihana.com|Reza Fatahilah Shah}}
{{FeatureInProgress|plasma workspace|Port Notifications applet to QML|mart@kde.org|Marco Martin}}
{{FeatureInProgress|plasma workspace|Port Task Manager applets to QML|hein@kde.org|Eike Hein (Sho_)}}
{{FeatureInProgress|plasma workspace|refresh Air Plasma theme|mart@kde.org|Marco Martin}}
{{FeatureInProgress|plasma workspace|Port Kickoff to qml|yellowcake-@gmx.net|Greg T}}
{{FeatureInProgress|systemsettings|Replace krandr KCM by libkscreen-based one|dvratil@redhat.com|Dan Vrátil}}
{{FeatureInProgress|plasma workspace|Port rssnow to qml|terietor@gmail.com|Giorgos Tsiapaliokas}}
{{FeatureInProgress|various|KActivities/SLC support for most our applications|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|plasma workspace|first desktop SLC applet release|mart@kde.org|Marco Martin}}
{{FeatureDone|System Tray|System tray with interface in QML|dmitry.ashkadov@gmail.com|Dmitry Ashkadov}}
{{FeatureTodo|plasma workspace|Top-rated documents for Task Manager|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|systemsettings|Keyboard layout preview|amourphious1992@gmail.com|Shivam Makkar}}
{{FeatureInProgress|window manager|Rework and optimize vertex specification|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|window manager|Dynamic shader generation|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|window manager|Partial port to xcb|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|window manager|New launch feedback effect|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|activities|Encrypted activities|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|powerdevil|Improve profile error handling (DPMS)|kde@privat.broulik.de|Kai Uwe Broulik}}
|}
 

= kde-baseapps =

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

! Status
! Project
! Description
! Contact

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

{{FeatureTodo|FolderView|Port to QML|ignat.semenov@blue-systems.com|Ignat Semenov}}

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

{{FeatureTodo|Dolphin|Implement parallel sort algorithm|emmanuelpescosta099@gmail.com|Emmanuel Pescosta}}

{{FeatureTodo|Dolphin|Add GUI option for the "Rename Inline" setting|frank78ac@googlemail.com|Frank Reininghaus}}

{{FeatureTodo|Dolphin|Add "Icon Size" submenu to the Places Panel context menu|frank78ac@googlemail.com|Frank Reininghaus}}

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

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

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

{{FeatureTodo|Kate|As-you-type search for the search plugin|kare.sars@iki.fi|Kåre Särs}}

{{FeatureTodo|Kate|Session name API for plugins + automatic ctags database naming|kare.sars@iki.fi|Kåre Särs}}

{{FeatureInProgress|Kate|Add optional document "minimap" to the Symbols view plugin|kare.sars@iki.fi|Kåre Särs}}

{{FeatureInProgress|Kate|Macro support|kdedevel@etothepiplusone.com|Simon St James}}

{{FeatureTodo|Kdialog|Add support for detailedsorry/detailederror messages|kde@privat.broulik.de|Kai Uwe Broulik}}

{{FeatureTodo|Konsole|Improve the search filter bar|francesco.cecconi@gmail.com|Francesco Cecconi}}

{{FeatureTodo|Konsole|Add the --separate cmdline option for running in new process|adaptee@gmail.com|Jekyll Wu}}

{{FeatureTodo|Konsole|Make the d&d popup menu optional|adaptee@gmail.com|Jekyll Wu}}

|}
 

= kdeedu =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|Marble|Have support for "repeatX" in the projection classes|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Mars & Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Foursquare plugin|utkuaydin34@gmail.com|Utku Aydın}}
{{FeatureTodo|Marble|Marble Touch on Android (including SOK branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|OSM vector rendering (GSOC branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Zoom to content of geo file after loading (at least on start-up)|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Marble|Geo files thumbnailer|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Marble|Geo files metadata extractor|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Rocs|Journal files for projects.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|Revisit graph export/import functionality to fully support: TGF, DOT, GML, GraphML|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Printing and image export of graphs.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Data Structure Snapshot and Recovery.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|Main Window UI Reorganization|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Visual Graph Editor Handling: copy&paste, data structure focus, property display|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Visual Graph Editor Edit Menu|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Code Editor Configuration Dialog|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Data Structure Backend wise iconsets and preconfigurations for types|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|KTouch|Ship ktouch/next|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureTodo|KTouch|Smart resizing of training screen with aligned vertical lines|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureTodo|KTouch|Prominent hint during training if the user makes repeatedly errors|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureTodo|KTouch|Show course descriptions in course selector|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureTodo|KTouch|Show a message when keyboard layout visualizion isn't available due missing data|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureDone|Analitza|New plotting framework|percy.camilo.ta@gmail.com|Percy Camilo Triveño Aucahuasi}}
{{FeatureDone|KAlgebra|Splitted the QML Components from KAlgebraMobile|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra|New plotting plasmoid graphs, in QtQuick|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|Pairs|Pairs Theme editor|marco.calignano@gmail.com|Marco Calignano}}
{{FeatureInProgress|Cantor|Python backend|filipe@kde.org|Filipe Saraiva}}
{{FeatureInProgress|Kig|Mark right angles|david.narvaez@computer.org|David E. Narváez}}
|}
 

= kdegames=

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

! Status
! Project
! Description
! Contact

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

= kdegraphics=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|libkipi|[http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/dodonvictor/10002 Porting libkipi to KDE-XML GUI]|dodonvictor@gmail.com|Victor Dodon}}
{{FeatureInProgress|okular|Tiled rendering|okular-devel@kde.org|Okular Developers}}
{{FeatureInProgress|Gwenview|Recursive importer|agateau@kde.org|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Color profile support|agateau@kde.org|Aurélien Gâteau}}

|}
 

= kdemultimedia =

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

! Status
! Project
! Description
! Contact

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

|}
 

= kdenetwork=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|KGet|Metalink/HTTP Support|dahalaishraj@gmail.com|Aish Raj Dahal}}

|}
 

= kdepim =

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

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

= kdeplasma-addons =

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

! Status
! Project
! Description
! Contact
{{FeatureInProgress|Microblog|replace with QML version|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|StackFolder|Add applet for quick browse the stack of folders|ural.mullabaev@rosalab.ru|Ural Mullabaev}}
{{FeatureInProgress|ComicStrip|Replace with QML version|rshah0385@kireihana.com|Reza Fatahilah Shah}}
{{FeatureInProgress|Calculator|Replace with QML version|luizromario@gmail.com|Luiz Romário Santana Rios}}
{{FeatureDone|QML Wallpapers|Make it possible to have animated wallpapers written in QtQuick technologies.|aleixpol@blue-systems.com|Aleix Pol Gonzalez}}
{{FeatureDone|Dictionary KRunner|Look up words in the dictionary by typing in 'define {word}' in krunner.|Jason@zx2c4.com|Jason A. Donenfeld}}
{{FeatureInProgress|Calculator|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|Eyes|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|FifteenPuzzle|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|Luna|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|Timer|replace with QML version|bettio@kde.org|Davide Bettio}}
|}
 

= kdesdk =

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

 

= kdeutils=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|Ark|Make it possible to disable internal previewer|kde@privat.broulik.de|Kai Uwe Broulik}}
|}

Schedules/KDE4/4.10 Feature Plan

2012-10-25T18:50:27Z

Rhabacker: /* kdesdk */

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

See also:

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

 Legend:

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

__TOC__

 

= kdelibs =

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

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

= kde-runtime =

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|kio-mtp|KIO-Slave for MTP|philschmidt@gmx.net|Philipp Schmidt}}
{{FeatureInProgress|QML Containments|Making it possible to do full-featured containments in QML|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|nepomuk-indexer|New Nepomuk Indexer|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomukbakcup|Nepomuk Backup rewritten from scratch|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomukcleaner|An application to port/clean invalid/legacy data in Nepomuk|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomuk KCM|Rewrite the Nepomuk KCM|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomuk tags|Nepomuk Tags KIO Slave|me@vhanda.in|Vishesh Handa}}
{{FeatureInProgress|nepomuk filemetadtawdiget|Nepomuk Metadata Widget|me@vhanda.in|Vishesh Handa}}
|}
 

= kde-workspace =

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

! Status
! Project
! Description
! Contact

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


{{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Medium focus stealing prevention should also prevent focus stealing when the timestamp on the active window is uncertain ({{bug |304746}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Usability issue: "Attach as tab to" menu can be empty ({{bug |306451}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Display application menu and title bar side by side for maximized windows ({{bug |102607}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Add support for appmenu-qt ({{bug |266596}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Import Scripted Effect from All Effets Tab ({{bug |296772}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|GHNS support for Scripted Effects ({{bug |296773}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|Remove legacy window decorations ({{bug |299144}}, Review 104281)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Get rid of "Display borders on maximized windows" setting ({{bug |299245}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Cube animation on border approach should not be used unless the electric borders are actually in use and the config should be disabled, align or hint the electric border configuration ({{bug |299901}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Make ShaderManager act as a real stack ({{bug |300349}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|clientPopup: "'More actions' and "Attach as tab to" lack mnemonics ({{bug |302833}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Make KWin compile with C++11 ({{bug |303313}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Copy all useful Client properties to Deleted ({{bug |303916}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Display content of resizing/moving windows: KDE-Help shows obsolete instructions ({{bug |305297}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Mouse action support for sending window to different activity ({{bug |305758}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Windows list icon does not show up in "Walk Through Desktop List" ({{bug |306187}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Game mode ({{bug |306448}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Animate Window Maximize/Restore ({{bug |308990}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Common animation settings for effects of same type ({{bug |308991}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Use Resize Area in Aurorae ({{bug |308992}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Configurable quick tile area ({{bug |308993}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Decorations not visible ({{bug |305875}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|drag-and-drop between windows by cover switch alt-tab causes apps to crash ({{bug |179077}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add a rule to select the screen ({{bug |183996}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: Need Mouse navigation in flip switch mode ({{bug |244439}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Request category for scripted KWin Effects on kde-(look<nowiki>|</nowiki>app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Request category for KWin Scripts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Request category for Window Switcher Layouts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Allow direct rendering with fglrx ({{bug |301103}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Don't use OpenGL matrix stack in OpenGL 2 backend ({{bug |303093}}, Review 105455)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Refactor Screen/Window PaintData ({{bug |303314}}, Review 105141)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Rapid flickering in locked screen -- makes it difficult to unlock ({{bug |303579}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|double click menu to close needs GUI config ({{bug |305738}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Toplevel::windowType() needs performance improvements ({{bug |306384}}, Review 106349)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|GLPlatform should recommend either OpenGL1 or OpenGL2 compositing ({{bug |306436}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Zoom effect broken in master ({{bug |307609}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|kwin fails to build when the GLES support is disabled ({{bug |307866}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|[JJ] Some effect authors are listed as "Name1 & Name2" ({{bug |307928}}, Review 106880)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add screen management actions to window context menus ({{bug |269207}}, Review 106065)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Move Workspace's compositing functionality to own class Compositor ({{bug |299277}}, Review 102420)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Option to disable close on double click in Aurorae ({{bug |301327}}, Review 106160)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Remove Tiling Support From KWin ({{bug |303090}}, Review 105546)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Allow Scripts to add menus to useractions menu ({{bug |303756}}, Review 106285)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Generic QML support for Aurorae Themes ({{bug |303810}}, Review 105768)|mgraesslin@kde.org}}
{{FeatureDone|kwin|Split out Useractions Menu from Workspace ({{bug |305832}}, Review 106085)|mgraesslin@kde.org}}


{{FeatureDone|plasma-wallpapers|Color wallpaper: add listview to display thumbnails for background mode|rshah0385@kireihana.com|Reza Fatahilah Shah}}
{{FeatureInProgress|plasma workspace|Port Notifications applet to QML|mart@kde.org|Marco Martin}}
{{FeatureInProgress|plasma workspace|Port Task Manager applets to QML|hein@kde.org|Eike Hein (Sho_)}}
{{FeatureInProgress|plasma workspace|refresh Air Plasma theme|mart@kde.org|Marco Martin}}
{{FeatureInProgress|plasma workspace|Port Kickoff to qml|yellowcake-@gmx.net|Greg T}}
{{FeatureInProgress|systemsettings|Replace krandr KCM by libkscreen-based one|dvratil@redhat.com|Dan Vrátil}}
{{FeatureInProgress|plasma workspace|Port rssnow to qml|terietor@gmail.com|Giorgos Tsiapaliokas}}
{{FeatureInProgress|various|KActivities/SLC support for most our applications|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|plasma workspace|first desktop SLC applet release|mart@kde.org|Marco Martin}}
{{FeatureDone|System Tray|System tray with interface in QML|dmitry.ashkadov@gmail.com|Dmitry Ashkadov}}
{{FeatureTodo|plasma workspace|Top-rated documents for Task Manager|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|systemsettings|Keyboard layout preview|amourphious1992@gmail.com|Shivam Makkar}}
{{FeatureInProgress|window manager|Rework and optimize vertex specification|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|window manager|Dynamic shader generation|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|window manager|Partial port to xcb|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|window manager|New launch feedback effect|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|activities|Encrypted activities|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|powerdevil|Improve profile error handling (DPMS)|kde@privat.broulik.de|Kai Uwe Broulik}}
|}
 

= kde-baseapps =

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

! Status
! Project
! Description
! Contact

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

{{FeatureTodo|FolderView|Port to QML|ignat.semenov@blue-systems.com|Ignat Semenov}}

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

{{FeatureTodo|Dolphin|Implement parallel sort algorithm|emmanuelpescosta099@gmail.com|Emmanuel Pescosta}}

{{FeatureTodo|Dolphin|Add GUI option for the "Rename Inline" setting|frank78ac@googlemail.com|Frank Reininghaus}}

{{FeatureTodo|Dolphin|Add "Icon Size" submenu to the Places Panel context menu|frank78ac@googlemail.com|Frank Reininghaus}}

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

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

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

{{FeatureTodo|Kate|As-you-type search for the search plugin|kare.sars@iki.fi|Kåre Särs}}

{{FeatureTodo|Kate|Session name API for plugins + automatic ctags database naming|kare.sars@iki.fi|Kåre Särs}}

{{FeatureInProgress|Kate|Add optional document "minimap" to the Symbols view plugin|kare.sars@iki.fi|Kåre Särs}}

{{FeatureInProgress|Kate|Macro support|kdedevel@etothepiplusone.com|Simon St James}}

{{FeatureTodo|Kdialog|Add support for detailedsorry/detailederror messages|kde@privat.broulik.de|Kai Uwe Broulik}}

{{FeatureTodo|Konsole|Improve the search filter bar|francesco.cecconi@gmail.com|Francesco Cecconi}}

{{FeatureTodo|Konsole|Add the --separate cmdline option for running in new process|adaptee@gmail.com|Jekyll Wu}}

{{FeatureTodo|Konsole|Make the d&d popup menu optional|adaptee@gmail.com|Jekyll Wu}}

|}
 

= kdeedu =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|Marble|Have support for "repeatX" in the projection classes|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Mars & Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Foursquare plugin|utkuaydin34@gmail.com|Utku Aydın}}
{{FeatureTodo|Marble|Marble Touch on Android (including SOK branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|OSM vector rendering (GSOC branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Zoom to content of geo file after loading (at least on start-up)|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Marble|Geo files thumbnailer|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Marble|Geo files metadata extractor|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Rocs|Journal files for projects.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|Revisit graph export/import functionality to fully support: TGF, DOT, GML, GraphML|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Printing and image export of graphs.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Data Structure Snapshot and Recovery.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|Main Window UI Reorganization|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Visual Graph Editor Handling: copy&paste, data structure focus, property display|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Visual Graph Editor Edit Menu|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Code Editor Configuration Dialog|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|Data Structure Backend wise iconsets and preconfigurations for types|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|KTouch|Ship ktouch/next|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureTodo|KTouch|Smart resizing of training screen with aligned vertical lines|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureTodo|KTouch|Prominent hint during training if the user makes repeatedly errors|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureTodo|KTouch|Show course descriptions in course selector|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureTodo|KTouch|Show a message when keyboard layout visualizion isn't available due missing data|sebastiangottfried@web.de|Sebastian Gottfried}}
{{FeatureDone|Analitza|New plotting framework|percy.camilo.ta@gmail.com|Percy Camilo Triveño Aucahuasi}}
{{FeatureDone|KAlgebra|Splitted the QML Components from KAlgebraMobile|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra|New plotting plasmoid graphs, in QtQuick|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|Pairs|Pairs Theme editor|marco.calignano@gmail.com|Marco Calignano}}
{{FeatureInProgress|Cantor|Python backend|filipe@kde.org|Filipe Saraiva}}
{{FeatureInProgress|Kig|Mark right angles|david.narvaez@computer.org|David E. Narváez}}
|}
 

= kdegames=

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

! Status
! Project
! Description
! Contact

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

= kdegraphics=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|libkipi|[http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/dodonvictor/10002 Porting libkipi to KDE-XML GUI]|dodonvictor@gmail.com|Victor Dodon}}
{{FeatureInProgress|okular|Tiled rendering|okular-devel@kde.org|Okular Developers}}
{{FeatureInProgress|Gwenview|Recursive importer|agateau@kde.org|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Color profile support|agateau@kde.org|Aurélien Gâteau}}

|}
 

= kdemultimedia =

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

! Status
! Project
! Description
! Contact

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

|}
 

= kdenetwork=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|KGet|Metalink/HTTP Support|dahalaishraj@gmail.com|Aish Raj Dahal}}

|}
 

= kdepim =

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

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

= kdeplasma-addons =

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

! Status
! Project
! Description
! Contact
{{FeatureInProgress|Microblog|replace with QML version|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|StackFolder|Add applet for quick browse the stack of folders|ural.mullabaev@rosalab.ru|Ural Mullabaev}}
{{FeatureInProgress|ComicStrip|Replace with QML version|rshah0385@kireihana.com|Reza Fatahilah Shah}}
{{FeatureInProgress|Calculator|Replace with QML version|luizromario@gmail.com|Luiz Romário Santana Rios}}
{{FeatureDone|QML Wallpapers|Make it possible to have animated wallpapers written in QtQuick technologies.|aleixpol@blue-systems.com|Aleix Pol Gonzalez}}
{{FeatureDone|Dictionary KRunner|Look up words in the dictionary by typing in 'define {word}' in krunner.|Jason@zx2c4.com|Jason A. Donenfeld}}
{{FeatureInProgress|Calculator|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|Eyes|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|FifteenPuzzle|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|Luna|replace with QML version|bettio@kde.org|Davide Bettio}}
{{FeatureInProgress|Timer|replace with QML version|bettio@kde.org|Davide Bettio}}
|}
 

= kdesdk =

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

 

= kdeutils=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|Ark|Make it possible to disable internal previewer|kde@privat.broulik.de|Kai Uwe Broulik}}
|}

Schedules/KDE4/4.9 Feature Plan

2012-07-20T20:58:25Z

Rhabacker: /* kdeedu */ updated marble

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

See also:

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

 Legend:

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

__TOC__

 

= kdelibs =

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

! Status
! Project
! Description
! Contact
{{FeatureDone|KGlobalSettings|Make KGlobalSettings reread locale settings before calling settingsChanged().|lamarque@kde.org|Lamarque V. Souza}}
{{FeatureDone|Kate Part|Reworked Color Configuration|dhaumann@kde.org|Dominik Haumann}}
{{FeatureDone|KActivities|Encryption for private activities (not available via UI).|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|KActivities|Linking files to activities in Dolphin, Konqueror, Folder View.|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|KActivities|Activities KIO.|ivan.cukic@kde.org|Ivan Čukić}}
|}
 

= kde-runtime =

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

! Status
! Project
! Description
! Contact

{{FeatureDone|Thumbnail|fix for bookmarks|sebas@kde.org|Sebastian Kügler}}

|}
 

= kde-workspace =

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

! Status
! Project
! Description
! Contact
{{FeatureDone|ksmserver|Port shutdown dialog to QML|lamarque@kde.org|Lamarque V. Souza}}
{{FeatureInProgress|ksmserver|Merge the new qml based screen locker|mart@kde.org|Marco Martin}}
{{FeatureDone|plasma|MPRIS2 dataengine|alex.merry@kdemail.net|Alex Merry}}

{{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Lanczos Filter broken after screen size changes ({{bug |296065}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|GHNS support for KWin Scripts ({{bug |296774}}, Review 104877)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|KConf Update Script for KWin 4.9 ({{bug |296775}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for scripted KWin Effects on kde-(look<nowiki>|</nowiki>app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for KWin Scripts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|GHNS support for Window Switching Layouts ({{bug |297636}}, Review 104894)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for Window Switcher Layouts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Update Documentation for Window Switcher Layouts ({{bug |297638}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|ThumbnailItem allows upscaling of Windows ({{bug |297864}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Increase ABI version for KDecorations ({{bug |299140}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Useraction menu closes when focus passes to another window ({{bug |81743}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: change focus only when moving mouse ({{bug |92290}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: kwin fulscreen / un-fullscreen system notifications ({{bug |124612}}, Review 104457)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Insufficient stacking order handling for deleted windows ({{bug |158262}}, Review 104519)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: Use arrow keys to control cover switch. ({{bug |178595}}, Review 104438)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|No reason given why some desktop effects cannot be activated ({{bug |209213}}, Review 104847)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Dragging a title bar against a bottom panel twice makes it go under the panel on the second time ({{bug |210926}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Wobbly windows wobbles strange after quick-maximization ({{bug |222102}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|"Move" command should allow off-screen window moving same as Alt + click trick ({{bug |229942}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Bug with shading always inactive windows ({{bug |242217}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Change title of menu item "Configure window behaviour..." ({{bug |249486}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Task switcher message when no windows looks ugly with stars ({{bug |260938}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Placement Policy 'under mouse' ({{bug |272162}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: Synchronize Show Desktop wording in all tabbox effects ({{bug |273478}}, Review 104436)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|closing session crash ({{bug |282933}}, Review 104690)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Window Specific Settings dialog has no help function ({{bug |286783}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add "Present Windows - Window Class" to "Screen Edges" functions ({{bug |288960}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|[JJ] Select next window with arrow key in Alt+Tab ({{bug |291916}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|KWin crashed when I was switching windows ({{bug |292614}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Kill helper should be out of process ({{bug |295940}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Synchronize user actions menu with libtaskmanager ({{bug |296056}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Different binary name for KWin Active ({{bug |296084}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Window Switcher KCM needs to be reworked ({{bug |297639}}, Review 104525)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Document global JavaScript methods in KWin Scripting API documentation ({{bug |297640}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Elevate windows in addition to highlight ({{bug |297809}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|KWin crashes when interacting with Plasma ({{bug |298669}}, Review 104714)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add ABI check to KDecorations ({{bug |299141}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Effects cannot be configured ({{bug |299163}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Adding proper window thumbnail clipping to the QML tabbox ({{bug |299198}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Improve VSync strategy ({{bug |299274}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Screen Edge bindings for KWin Scripting ({{bug |299275}}, Review 104904)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Better QML selection list for Window Switcher layout ({{bug |299278}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add layout specification to D-Bus call for invoking TabBox ({{bug |299279}}, Review 104838)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Default Bindings for Switching between Windows of current Application ({{bug |299308}}, Review 104730)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Make desktop focus chains activities aware ({{bug |299309}}, Review 104649)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Activity window rules (Review 104972) |ivan.cukic@kde.org}}
{{FeatureDone|kwin|Desktop Zoom should be saved between sessions ({{bug |189956}}, Review 104597)|kwin-bugs-null@kde.org}}

|}
 

= kde-baseapps =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|FolderView|Refactor into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}
{{FeatureDone|FolderView|Show files related to an activity|ivan.cukic@kde.org|Ivan Cukic}}
{{FeatureDone|Dolphin|Allow to show any kind of metadata like ratings, tags, comments, image-sizes, music-artist, ... beside each item of the view (see http://ppenz.blogspot.co.at/2012/06/improved-views.html for details)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Use KMessageWidget for information- and error-messages (see http://agateau.com/2011/04/21/kde-ux-2011/ for details)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Optionally remember the column-widths of the details view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Allow to disable the expandable folders of the details view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Implement inline renaming for the new view-engine|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Allow to optionally set a maximum number of lines for the icons-view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Implement support for back/forward mouse buttons|sebasti@n-doerner.de|Sebastian Dörner}}
{{FeatureTodo|Dolphin|Implement files quick preview feature (named Klook) |evgeniy.augin@osinit.ru|Evgeniy Auzhin}}
{{FeatureDone|Konsole|Move menubar and tabbar settings out of profile and into "Configure Konsole"|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Add command line options for controlling the visibility of menubar and tabbar|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow dragging tab out of current window and into its own window|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Add "Clone Tab" action for opening new tab using the same profile used by current tab |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Add "Change Directory To" action in the popup menu of drag & drop operation |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow action in the context menu for searching selected text using KDE WebShortcuts |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Provide the searching ability in konsolepart|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|konsolepart can notify the hosting application(e.g, dolphin) of the changing of current directory |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow changing tab title through escape sequence like "\e]30;Tab Title\a" |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow users to have better control of the copy & paste behavior of mouse within Konsole|adaptee@gmail.com|Jekyll Wu}}

|}
 

= kdeedu =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|Marble|Have support for "repeatX" in the projection classes|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Mars & Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Android|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Flightgear position provider plugin|ralf.habacker@freenet.de|Ralf Habacker}}
{{FeatureDone|Rocs|Project Files to combine graphs and algorithms|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Extend graph data structure to support overlay graphs|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Stepped execution of algorithms|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|General unit test cleanup and overhauling|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Data types and pointer types|rocs-devel@kde.org|Andreas Cord-Landwehr}}
{{FeatureDone|Kig|Improve Cancel Construction and Undo actions|david.narvaez@computer.org|David E. Narváez}}
{{FeatureDone|Pairs|New memory game|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra Mobile|Many improvements, including Android and better Active support|aleixpol@kde.org|Aleix Pol Gonzalez}}
|}
 

= kdegames=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|libkdegames|[http://community.kde.org/KDE_Games/API_cleanup Major cleanup and rewrite] (done, except for the new highscore classes) '''Release team:''' please link to the [[Projects/Games/Porting_to_libkdegames_v5|porting instructions]] for third-party developers|stefan.majewsky@googlemail.com|Stefan Majewsky}}
{{FeatureDone|Granatier|improve config UI for player and arena selection|m-hias@gmx.de|Mathias Kraus}}
{{FeatureDone|Kajongg|tooltips giving playings hints|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|new config option: propose what to do|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|make it possible to replay a game from a screen shot (for better debugging)|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|improve Robot AI|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Add default voices|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Players can chat with each other from within kajongg|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Define a central game server, making it easier to play over the internet (no more tweaking of firewalls for the server side)|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|KGoldrunner|Add the Gold Rush II championship game (20 levels), contributed by Gabriel Miltschitzky|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KGoldrunner|Add solution files to some KGoldrunner games|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KPatience|Saved game files now include the whole game history|coates@kde.org|Parker Coates}}
{{FeatureDone|KSudoku|Simplify the XML descriptions of puzzle shapes|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Add XML and Desktop files for seven new two-dimensional puzzle shapes|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Add XML and Desktop files for three new three-dimensional puzzle shapes|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Improve the quality and relevance of KSudoku hints|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Make Load and Save work correctly for all puzzle types, including display of small markers/notes and restart of the puzzle clock from a saved value|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Integrate the new generator/solver and the old KSudoku code more closely|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Make puzzle features easier to see and use by improving highlighting, control and settings in both 2-D and 3-D puzzles and adding keyboard input to 3-D puzzles|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KMahjongg|Make the BoardEditor running again|Coding@Christian-Krippendorf.de|Christian Krippendorf}}
{{FeatureDone|KMahjongg|Implement an option for random layouts|Coding@Christian-Krippendorf.de|Christian Krippendorf}}
|}
 

= kdegraphics=

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

! Status
! Project
! Description
! Contact

{{FeatureDone|Gwenview|Fullscreen browse|agateau@kde.org|Aurélien Gâteau}}
{{FeatureInProgress|Okular|Store annotations with documents {{bug |151614}}|okular-devel@kde.org|}}
{{FeatureInProgress|Okular|Print document with annotations {{bug |159005}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Annotations Screen support (embedded movies in PDF) {{bug |172847}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Aggressive page preloading {{bug |184196}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Hyphen-aware search {{bug |190433}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Multiple bookmarks per page {{bug |157198}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Allow the renaming of bookmark "parent" items|okular-devel@kde.org|}}
{{FeatureDone|Okular|Allow the page number selector to be added to the toolbar {{bug |279128}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Double click to select workds {{bug |187347}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Make Okular inhibit sleep and screen power management when in Presentation mode|okular-devel@kde.org|}}
{{FeatureDone|Okular|Behavior for left/right arrow keys (Review 104596)|okular-devel@kde.org|}}
{{FeatureDone|Okular|Remember the mouse mode on exit|okular-devel@kde.org|}}
{{FeatureDone|Okular|Make search from the current page the default|okular-devel@kde.org|}}
|}
 

= kdemultimedia =

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

! Status
! Project
! Description
! Contact

{{FeatureDone|JuK|last.fm scrobbling|martin.sandsmark@kde.org|Martin Sandsmark}}
{{FeatureDone|JuK|cover-fetching from last.fm|martin.sandsmark@kde.org|Martin Sandsmark}}
{{FeatureDone|JuK|MPRIS2 support|alex.merry@kmail.net|Alex Merry}}
{{FeatureDone|JuK|MPRIS2 support|hein@kde.org|Eike Hein}}
{{FeatureDone|Dragon|MPRIS2 support|hein@kde.org|Eike Hein}}
{{FeatureDone|JuK|Support embedded cover art for MP4/AAC files|mpyne@kde.org|Michael Pyne}}
|}
 

= kdenetwork=

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

! Status
! Project
! Description
! Contact
{{FeatureDone|Kopete|Add option to group all offline users into a "Offline Users" group|kopete-devel@kde.org|Kopete Developers}}
{{FeatureDone|Kopete|Show contact's status change in chat window|igor.poboiko@gmail.com|Igor Poboiko}}
{{FeatureDone|Kopete|Add context option "rename" to contacts and allow changing custom display name inline.|kopete-devel@kde.org|Kopete Developers}}
|}
 

= kdepim =

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

! Status
! Project
! Description
! Contact

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

{{FeatureDone|KTnef|Bring back KTnef from the KDE3 days. KTnef is a standalone TNEF attachment viewer|winter@kde.org|Allen Winter}}

{{FeatureDone|Akonadi Kolab Resources|Kolab resource using the Kolab libraries to kdepim-runtime|chrigi_1@fastmail.fm|Christian Mollekopf}}

{{FeatureDone|Extend Akonotes Format|Extend the akonotes format to support features required by zanshin and kolab|chrigi_1@fastmail.fm|Christian Mollekopf}}

{{FeatureDone|Import pim data|ImportWizard allows to import settings/mails/filters/calendar/addressbook from thunderbird/evolution/etc. when exists.|montel@kde.org|Laurent Montel}}

{{FeatureDone|Archive Mail Agent|Archive Mail Agent archives your mail folders on a scheduled basis.|montel@kde.org|Laurent Montel}}

{{FeatureDone|Backup Mail|Backup Mail saves/restores mail config/config (akonadi)/database nepomuk/resources etc.|montel@kde.org|Laurent Montel}}

|}
 

= kdeplasma-addons =

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

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

= kdesdk =

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

 

= kdeutils=

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

! Status
! Project
! Description
! Contact

|}

Schedules/KDE4/4.9 Feature Plan

2012-05-29T06:19:04Z

Rhabacker: /* kdesdk */

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

See also:

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

 Legend:

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

__TOC__

 

= kdelibs =

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

! Status
! Project
! Description
! Contact
{{FeatureDone|KGlobalSettings|Make KGlobalSettings reread locale settings before calling settingsChanged().|lamarque@kde.org|Lamarque V. Souza}}
{{FeatureDone|Kate Part|Reworked Color Configuration|dhaumann@kde.org|Dominik Haumann}}
{{FeatureDone|KActivities|Encryption for private activities (not available via UI).|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|KActivities|Linking files to activities in Dolphin, Konqueror, Folder View.|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|KActivities|Activities KIO.|ivan.cukic@kde.org|Ivan Čukić}}
|}
 

= kde-runtime =

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

! Status
! Project
! Description
! Contact

{{FeatureDone|Thumbnail|fix for bookmarks|sebas@kde.org|Sebastian Kügler}}

|}
 

= kde-workspace =

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

! Status
! Project
! Description
! Contact
{{FeatureDone|ksmserver|Port shutdown dialog to QML|lamarque@kde.org|Lamarque V. Souza}}
{{FeatureInProgress|ksmserver|Merge the new qml based screen locker|mart@kde.org|Marco Martin}}
{{FeatureDone|plasma|MPRIS2 dataengine|alex.merry@kdemail.net|Alex Merry}}

{{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Lanczos Filter broken after screen size changes ({{bug |296065}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|GHNS support for KWin Scripts ({{bug |296774}}, Review 104877)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|KConf Update Script for KWin 4.9 ({{bug |296775}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for scripted KWin Effects on kde-(look<nowiki>|</nowiki>app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for KWin Scripts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|GHNS support for Window Switching Layouts ({{bug |297636}}, Review 104894)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for Window Switcher Layouts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Update Documentation for Window Switcher Layouts ({{bug |297638}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|ThumbnailItem allows upscaling of Windows ({{bug |297864}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Increase ABI version for KDecorations ({{bug |299140}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Useraction menu closes when focus passes to another window ({{bug |81743}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: change focus only when moving mouse ({{bug |92290}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: kwin fulscreen / un-fullscreen system notifications ({{bug |124612}}, Review 104457)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Insufficient stacking order handling for deleted windows ({{bug |158262}}, Review 104519)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: Use arrow keys to control cover switch. ({{bug |178595}}, Review 104438)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|No reason given why some desktop effects cannot be activated ({{bug |209213}}, Review 104847)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Dragging a title bar against a bottom panel twice makes it go under the panel on the second time ({{bug |210926}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Wobbly windows wobbles strange after quick-maximization ({{bug |222102}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|"Move" command should allow off-screen window moving same as Alt + click trick ({{bug |229942}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Bug with shading always inactive windows ({{bug |242217}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Change title of menu item "Configure window behaviour..." ({{bug |249486}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Task switcher message when no windows looks ugly with stars ({{bug |260938}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Placement Policy 'under mouse' ({{bug |272162}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: Synchronize Show Desktop wording in all tabbox effects ({{bug |273478}}, Review 104436)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|closing session crash ({{bug |282933}}, Review 104690)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Window Specific Settings dialog has no help function ({{bug |286783}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add "Present Windows - Window Class" to "Screen Edges" functions ({{bug |288960}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|[JJ] Select next window with arrow key in Alt+Tab ({{bug |291916}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|KWin crashed when I was switching windows ({{bug |292614}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Kill helper should be out of process ({{bug |295940}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Synchronize user actions menu with libtaskmanager ({{bug |296056}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Different binary name for KWin Active ({{bug |296084}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Window Switcher KCM needs to be reworked ({{bug |297639}}, Review 104525)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Document global JavaScript methods in KWin Scripting API documentation ({{bug |297640}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Elevate windows in addition to highlight ({{bug |297809}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|KWin crashes when interacting with Plasma ({{bug |298669}}, Review 104714)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add ABI check to KDecorations ({{bug |299141}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Effects cannot be configured ({{bug |299163}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Adding proper window thumbnail clipping to the QML tabbox ({{bug |299198}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Improve VSync strategy ({{bug |299274}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Screen Edge bindings for KWin Scripting ({{bug |299275}}, Review 104904)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Better QML selection list for Window Switcher layout ({{bug |299278}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add layout specification to D-Bus call for invoking TabBox ({{bug |299279}}, Review 104838)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Default Bindings for Switching between Windows of current Application ({{bug |299308}}, Review 104730)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Make desktop focus chains activities aware ({{bug |299309}}, Review 104649)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Activity window rules (Review 104972) |ivan.cukic@kde.org}}
{{FeatureDone|kwin|Desktop Zoom should be saved between sessions ({{bug |189956}}, Review 104597)|kwin-bugs-null@kde.org}}

|}
 

= kde-baseapps =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|FolderView|Refactor into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}
{{FeatureDone|FolderView|Show files related to an activity|ivan.cukic@kde.org|Ivan Cukic}}
{{FeatureDone|Dolphin|Allow to show any kind of metadata like ratings, tags, comments, image-sizes, music-artist, ... beside each item of the view.|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Use KMessageWidget for information- and error-messages (see http://agateau.com/2011/04/21/kde-ux-2011/ for details)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Optionally remember the column-widths of the details view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Allow to disable the expandable folders of the details view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Implement inline renaming for the new view-engine|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Allow to optionally set a maximum number of lines for the icons-view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureTodo|Dolphin|Implement files quick preview feature (named Klook) |evgeniy.augin@osinit.ru|Evgeniy Auzhin}}
{{FeatureDone|Konsole|Move menubar and tabbar settings out of profile and into "Configure Konsole"|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Add command line options for controlling the visibility of menubar and tabbar|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow dragging tab out of current window and into its own window|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Add "Clone Tab" action for opening new tab using the same profile used by current tab |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Add "Change Directory To" action in the popup menu of drag & drop operation |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow action in the context menu for searching selected text using KDE WebShortcuts |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Provide the searching ability in konsolepart|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|konsolepart can notify the hosting application(e.g, dolphin) of the changing of current directory |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow changing tab title through escape sequence like "\e]30;Tab Title\a" |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow users to have better control of the copy & paste behavior of mouse within Konsole|adaptee@gmail.com|Jekyll Wu}}

|}
 

= kdeedu =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Mars & Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Android|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Rocs|Project Files to combine graphs and algorithms|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Extend graph data structure to support overlay graphs|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Stepped execution of algorithms|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|General unit test cleanup and overhauling|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|New Project Wizard - guided creation based on loaded plugins|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|Project journal files|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|New Add-Node/Add-Link Toolbar for data types and pointer types|rocs-devel@kde.org|Rocs Developers}}
{{FeatureDone|Kig|Improve Cancel Construction and Undo actions|david.narvaez@computer.org|David E. Narváez}}
{{FeatureDone|Pairs|New memory game|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra Mobile|Many improvements, including Android and better Active support|aleixpol@kde.org|Aleix Pol Gonzalez}}
|}
 

= kdegames=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|libkdegames|[http://community.kde.org/Games/API_cleanup Major cleanup and rewrite] (done, except for the new highscore classes) '''Release team:''' please link to the [[Projects/Games/Porting_to_libkdegames_v5|porting instructions]] for third-party developers|stefan.majewsky@googlemail.com|Stefan Majewsky}}
{{FeatureDone|Granatier|improve config UI for player and arena selection|m-hias@gmx.de|Mathias Kraus}}
{{FeatureDone|Kajongg|tooltips giving playings hints|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|new config option: propose what to do|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|make it possible to replay a game from a screen shot (for better debugging)|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|improve Robot AI|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Add default voices|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Players can chat with each other from within kajongg|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Define a central game server, making it easier to play over the internet (no more tweaking of firewalls for the server side)|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureInProgress|Kajongg|Add support for other rule variants, starting with Classical Chinese variants|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureTodo|Kajongg|Print rulesets, also more than one in parallel for comparisons|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|KGoldrunner|Add the Gold Rush II championship game (20 levels), contributed by Gabriel Miltschitzky|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KGoldrunner|Add solution files to some KGoldrunner games|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KPatience|Saved game files now include the whole game history|coates@kde.org|Parker Coates}}
{{FeatureDone|KSudoku|Simplify the XML descriptions of puzzle shapes|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Add XML and Desktop files for seven new two-dimensional puzzle shapes|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Add XML and Desktop files for three new three-dimensional puzzle shapes|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Improve the quality and relevance of KSudoku hints|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Make Load and Save work correctly for all puzzle types, including display of small markers/notes and restart of the puzzle clock from a saved value|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Integrate the new generator/solver and the old KSudoku code more closely|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Make puzzle features easier to see and use by improving highlighting, control and settings in both 2-D and 3-D puzzles and adding keyboard input to 3-D puzzles|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KMahjongg|Make the BoardEditor running again|Coding@Christian-Krippendorf.de|Christian Krippendorf}}
{{FeatureDone|KMahjongg|Implement an option for random layouts|Coding@Christian-Krippendorf.de|Christian Krippendorf}}
|}
 

= kdegraphics=

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

! Status
! Project
! Description
! Contact

{{FeatureDone|Gwenview|Fullscreen browse|agateau@kde.org|Aurélien Gâteau}}
{{FeatureInProgress|Okular|Store annotations with documents {{bug |151614}}|okular-devel@kde.org|}}
{{FeatureInProgress|Okular|Print document with annotations {{bug |159005}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Annotations Screen support (embedded movies in PDF) {{bug |172847}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Aggressive page preloading {{bug |184196}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Hyphen-aware search {{bug |190433}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Multiple bookmarks per page {{bug |157198}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Allow the renaming of bookmark "parent" items|okular-devel@kde.org|}}
{{FeatureDone|Okular|Allow the page number selector to be added to the toolbar {{bug |279128}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Double click to select workds {{bug |187347}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Make Okular inhibit sleep and screen power management when in Presentation mode|okular-devel@kde.org|}}
{{FeatureDone|Okular|Behavior for left/right arrow keys (Review 104596)|okular-devel@kde.org|}}
{{FeatureDone|Okular|Remember the mouse mode on exit|okular-devel@kde.org|}}
{{FeatureDone|Okular|Make search from the current page the default|okular-devel@kde.org|}}
|}
 

= kdemultimedia =

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

! Status
! Project
! Description
! Contact

{{FeatureDone|JuK|last.fm scrobbling|martin.sandsmark@kde.org|Martin Sandsmark}}
{{FeatureDone|JuK|cover-fetching from last.fm|martin.sandsmark@kde.org|Martin Sandsmark}}
{{FeatureDone|JuK|MPRIS2 support|alex.merry@kmail.net|Alex Merry}}
{{FeatureDone|JuK|MPRIS2 support|hein@kde.org|Eike Hein}}
{{FeatureDone|Dragon|MPRIS2 support|hein@kde.org|Eike Hein}}
|}
 

= kdenetwork=

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

! Status
! Project
! Description
! Contact
{{FeatureDone|Kopete|Add option to group all offline users into a "Offline Users" group|kopete-devel@kde.org|Kopete Developers}}
{{FeatureDone|Kopete|Show contact's status change in chat window|igor.poboiko@gmail.com|Igor Poboiko}}
{{FeatureDone|Kopete|Add context option "rename" to contacts and allow changing custom display name inline.|kopete-devel@kde.org|Kopete Developers}}
|}
 

= kdepim =

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

! Status
! Project
! Description
! Contact

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

{{FeatureDone|KTnef|Bring back KTnef from the KDE3 days. KTnef is a standalone TNEF attachment viewer|winter@kde.org|Allen Winter}}

{{FeatureDone|Akonadi Kolab Resources|Kolab resource using the Kolab libraries to kdepim-runtime|chrigi_1@fastmail.fm|Christian Mollekopf}}

{{FeatureDone|Extend Akonotes Format|Extend the akonotes format to support features required by zanshin and kolab|chrigi_1@fastmail.fm|Christian Mollekopf}}

{{FeatureDone|Import pim data|ImportWizard allows to import settings/mails/filters/calendar/addressbook from thunderbird/evolution/etc. when exists.|montel@kde.org|Laurent Montel}}

{{FeatureDone|Archive Mail Agent|Archive Mail Agent archives your mail folders on a scheduled basis.|montel@kde.org|Laurent Montel}}

{{FeatureDone|Backup Mail|Backup Mail saves/restores mail config/config (akonadi)/database nepomuk/resources etc.|montel@kde.org|Laurent Montel}}

|}
 

= kdeplasma-addons =

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

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

= kdesdk =

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

 

= kdeutils=

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

! Status
! Project
! Description
! Contact

|}

Schedules/KDE4/4.9 Feature Plan

2012-05-29T06:18:07Z

Rhabacker: /* kdesdk */

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

See also:

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

 Legend:

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

__TOC__

 

= kdelibs =

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

! Status
! Project
! Description
! Contact
{{FeatureDone|KGlobalSettings|Make KGlobalSettings reread locale settings before calling settingsChanged().|lamarque@kde.org|Lamarque V. Souza}}
{{FeatureDone|Kate Part|Reworked Color Configuration|dhaumann@kde.org|Dominik Haumann}}
{{FeatureDone|KActivities|Encryption for private activities (not available via UI).|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|KActivities|Linking files to activities in Dolphin, Konqueror, Folder View.|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|KActivities|Activities KIO.|ivan.cukic@kde.org|Ivan Čukić}}
|}
 

= kde-runtime =

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

! Status
! Project
! Description
! Contact

{{FeatureDone|Thumbnail|fix for bookmarks|sebas@kde.org|Sebastian Kügler}}

|}
 

= kde-workspace =

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

! Status
! Project
! Description
! Contact
{{FeatureDone|ksmserver|Port shutdown dialog to QML|lamarque@kde.org|Lamarque V. Souza}}
{{FeatureInProgress|ksmserver|Merge the new qml based screen locker|mart@kde.org|Marco Martin}}
{{FeatureDone|plasma|MPRIS2 dataengine|alex.merry@kdemail.net|Alex Merry}}

{{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Lanczos Filter broken after screen size changes ({{bug |296065}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|GHNS support for KWin Scripts ({{bug |296774}}, Review 104877)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|KConf Update Script for KWin 4.9 ({{bug |296775}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for scripted KWin Effects on kde-(look<nowiki>|</nowiki>app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for KWin Scripts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}
{{FeatureInProgress|kwin|GHNS support for Window Switching Layouts ({{bug |297636}}, Review 104894)|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Request category for Window Switcher Layouts on kde-(look<nowiki>|</nowiki>app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Update Documentation for Window Switcher Layouts ({{bug |297638}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|ThumbnailItem allows upscaling of Windows ({{bug |297864}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Increase ABI version for KDecorations ({{bug |299140}})|kwin-bugs-null@kde.org}}
{{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Useraction menu closes when focus passes to another window ({{bug |81743}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: change focus only when moving mouse ({{bug |92290}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: kwin fulscreen / un-fullscreen system notifications ({{bug |124612}}, Review 104457)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Insufficient stacking order handling for deleted windows ({{bug |158262}}, Review 104519)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: Use arrow keys to control cover switch. ({{bug |178595}}, Review 104438)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|No reason given why some desktop effects cannot be activated ({{bug |209213}}, Review 104847)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Dragging a title bar against a bottom panel twice makes it go under the panel on the second time ({{bug |210926}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Wobbly windows wobbles strange after quick-maximization ({{bug |222102}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|"Move" command should allow off-screen window moving same as Alt + click trick ({{bug |229942}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Bug with shading always inactive windows ({{bug |242217}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Change title of menu item "Configure window behaviour..." ({{bug |249486}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Task switcher message when no windows looks ugly with stars ({{bug |260938}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Placement Policy 'under mouse' ({{bug |272162}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|JJ: Synchronize Show Desktop wording in all tabbox effects ({{bug |273478}}, Review 104436)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|closing session crash ({{bug |282933}}, Review 104690)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Window Specific Settings dialog has no help function ({{bug |286783}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add "Present Windows - Window Class" to "Screen Edges" functions ({{bug |288960}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|[JJ] Select next window with arrow key in Alt+Tab ({{bug |291916}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|KWin crashed when I was switching windows ({{bug |292614}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Kill helper should be out of process ({{bug |295940}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Synchronize user actions menu with libtaskmanager ({{bug |296056}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Different binary name for KWin Active ({{bug |296084}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Window Switcher KCM needs to be reworked ({{bug |297639}}, Review 104525)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Document global JavaScript methods in KWin Scripting API documentation ({{bug |297640}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Elevate windows in addition to highlight ({{bug |297809}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|KWin crashes when interacting with Plasma ({{bug |298669}}, Review 104714)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add ABI check to KDecorations ({{bug |299141}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Effects cannot be configured ({{bug |299163}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Adding proper window thumbnail clipping to the QML tabbox ({{bug |299198}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Improve VSync strategy ({{bug |299274}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Screen Edge bindings for KWin Scripting ({{bug |299275}}, Review 104904)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Better QML selection list for Window Switcher layout ({{bug |299278}})|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Add layout specification to D-Bus call for invoking TabBox ({{bug |299279}}, Review 104838)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Default Bindings for Switching between Windows of current Application ({{bug |299308}}, Review 104730)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Make desktop focus chains activities aware ({{bug |299309}}, Review 104649)|kwin-bugs-null@kde.org}}
{{FeatureDone|kwin|Activity window rules (Review 104972) |ivan.cukic@kde.org}}
{{FeatureDone|kwin|Desktop Zoom should be saved between sessions ({{bug |189956}}, Review 104597)|kwin-bugs-null@kde.org}}

|}
 

= kde-baseapps =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|FolderView|Refactor into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}
{{FeatureDone|FolderView|Show files related to an activity|ivan.cukic@kde.org|Ivan Cukic}}
{{FeatureDone|Dolphin|Allow to show any kind of metadata like ratings, tags, comments, image-sizes, music-artist, ... beside each item of the view.|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Use KMessageWidget for information- and error-messages (see http://agateau.com/2011/04/21/kde-ux-2011/ for details)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Optionally remember the column-widths of the details view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Allow to disable the expandable folders of the details view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Implement inline renaming for the new view-engine|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Allow to optionally set a maximum number of lines for the icons-view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureTodo|Dolphin|Implement files quick preview feature (named Klook) |evgeniy.augin@osinit.ru|Evgeniy Auzhin}}
{{FeatureDone|Konsole|Move menubar and tabbar settings out of profile and into "Configure Konsole"|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Add command line options for controlling the visibility of menubar and tabbar|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow dragging tab out of current window and into its own window|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Add "Clone Tab" action for opening new tab using the same profile used by current tab |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Add "Change Directory To" action in the popup menu of drag & drop operation |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow action in the context menu for searching selected text using KDE WebShortcuts |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Provide the searching ability in konsolepart|adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|konsolepart can notify the hosting application(e.g, dolphin) of the changing of current directory |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow changing tab title through escape sequence like "\e]30;Tab Title\a" |adaptee@gmail.com|Jekyll Wu}}
{{FeatureDone|Konsole|Allow users to have better control of the copy & paste behavior of mouse within Konsole|adaptee@gmail.com|Jekyll Wu}}

|}
 

= kdeedu =

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

! Status
! Project
! Description
! Contact

{{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Mars & Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}
{{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Marble Touch on Android|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Rocs|Project Files to combine graphs and algorithms|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Extend graph data structure to support overlay graphs|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Stepped execution of algorithms|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|General unit test cleanup and overhauling|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureTodo|Rocs|New Project Wizard - guided creation based on loaded plugins|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|Project journal files|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureInProgress|Rocs|New Add-Node/Add-Link Toolbar for data types and pointer types|rocs-devel@kde.org|Rocs Developers}}
{{FeatureDone|Kig|Improve Cancel Construction and Undo actions|david.narvaez@computer.org|David E. Narváez}}
{{FeatureDone|Pairs|New memory game|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra Mobile|Many improvements, including Android and better Active support|aleixpol@kde.org|Aleix Pol Gonzalez}}
|}
 

= kdegames=

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

! Status
! Project
! Description
! Contact

{{FeatureInProgress|libkdegames|[http://community.kde.org/Games/API_cleanup Major cleanup and rewrite] (done, except for the new highscore classes) '''Release team:''' please link to the [[Projects/Games/Porting_to_libkdegames_v5|porting instructions]] for third-party developers|stefan.majewsky@googlemail.com|Stefan Majewsky}}
{{FeatureDone|Granatier|improve config UI for player and arena selection|m-hias@gmx.de|Mathias Kraus}}
{{FeatureDone|Kajongg|tooltips giving playings hints|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|new config option: propose what to do|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|make it possible to replay a game from a screen shot (for better debugging)|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|improve Robot AI|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Add default voices|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Players can chat with each other from within kajongg|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Define a central game server, making it easier to play over the internet (no more tweaking of firewalls for the server side)|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureInProgress|Kajongg|Add support for other rule variants, starting with Classical Chinese variants|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureTodo|Kajongg|Print rulesets, also more than one in parallel for comparisons|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|KGoldrunner|Add the Gold Rush II championship game (20 levels), contributed by Gabriel Miltschitzky|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KGoldrunner|Add solution files to some KGoldrunner games|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KPatience|Saved game files now include the whole game history|coates@kde.org|Parker Coates}}
{{FeatureDone|KSudoku|Simplify the XML descriptions of puzzle shapes|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Add XML and Desktop files for seven new two-dimensional puzzle shapes|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Add XML and Desktop files for three new three-dimensional puzzle shapes|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Improve the quality and relevance of KSudoku hints|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Make Load and Save work correctly for all puzzle types, including display of small markers/notes and restart of the puzzle clock from a saved value|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Integrate the new generator/solver and the old KSudoku code more closely|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KSudoku|Make puzzle features easier to see and use by improving highlighting, control and settings in both 2-D and 3-D puzzles and adding keyboard input to 3-D puzzles|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KMahjongg|Make the BoardEditor running again|Coding@Christian-Krippendorf.de|Christian Krippendorf}}
{{FeatureDone|KMahjongg|Implement an option for random layouts|Coding@Christian-Krippendorf.de|Christian Krippendorf}}
|}
 

= kdegraphics=

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

! Status
! Project
! Description
! Contact

{{FeatureDone|Gwenview|Fullscreen browse|agateau@kde.org|Aurélien Gâteau}}
{{FeatureInProgress|Okular|Store annotations with documents {{bug |151614}}|okular-devel@kde.org|}}
{{FeatureInProgress|Okular|Print document with annotations {{bug |159005}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Annotations Screen support (embedded movies in PDF) {{bug |172847}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Aggressive page preloading {{bug |184196}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Hyphen-aware search {{bug |190433}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Multiple bookmarks per page {{bug |157198}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Allow the renaming of bookmark "parent" items|okular-devel@kde.org|}}
{{FeatureDone|Okular|Allow the page number selector to be added to the toolbar {{bug |279128}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Double click to select workds {{bug |187347}}|okular-devel@kde.org|}}
{{FeatureDone|Okular|Make Okular inhibit sleep and screen power management when in Presentation mode|okular-devel@kde.org|}}
{{FeatureDone|Okular|Behavior for left/right arrow keys (Review 104596)|okular-devel@kde.org|}}
{{FeatureDone|Okular|Remember the mouse mode on exit|okular-devel@kde.org|}}
{{FeatureDone|Okular|Make search from the current page the default|okular-devel@kde.org|}}
|}
 

= kdemultimedia =

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

! Status
! Project
! Description
! Contact

{{FeatureDone|JuK|last.fm scrobbling|martin.sandsmark@kde.org|Martin Sandsmark}}
{{FeatureDone|JuK|cover-fetching from last.fm|martin.sandsmark@kde.org|Martin Sandsmark}}
{{FeatureDone|JuK|MPRIS2 support|alex.merry@kmail.net|Alex Merry}}
{{FeatureDone|JuK|MPRIS2 support|hein@kde.org|Eike Hein}}
{{FeatureDone|Dragon|MPRIS2 support|hein@kde.org|Eike Hein}}
|}
 

= kdenetwork=

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

! Status
! Project
! Description
! Contact
{{FeatureDone|Kopete|Add option to group all offline users into a "Offline Users" group|kopete-devel@kde.org|Kopete Developers}}
{{FeatureDone|Kopete|Show contact's status change in chat window|igor.poboiko@gmail.com|Igor Poboiko}}
{{FeatureDone|Kopete|Add context option "rename" to contacts and allow changing custom display name inline.|kopete-devel@kde.org|Kopete Developers}}
|}
 

= kdepim =

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

! Status
! Project
! Description
! Contact

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

{{FeatureDone|KTnef|Bring back KTnef from the KDE3 days. KTnef is a standalone TNEF attachment viewer|winter@kde.org|Allen Winter}}

{{FeatureDone|Akonadi Kolab Resources|Kolab resource using the Kolab libraries to kdepim-runtime|chrigi_1@fastmail.fm|Christian Mollekopf}}

{{FeatureDone|Extend Akonotes Format|Extend the akonotes format to support features required by zanshin and kolab|chrigi_1@fastmail.fm|Christian Mollekopf}}

{{FeatureDone|Import pim data|ImportWizard allows to import settings/mails/filters/calendar/addressbook from thunderbird/evolution/etc. when exists.|montel@kde.org|Laurent Montel}}

{{FeatureDone|Archive Mail Agent|Archive Mail Agent archives your mail folders on a scheduled basis.|montel@kde.org|Laurent Montel}}

{{FeatureDone|Backup Mail|Backup Mail saves/restores mail config/config (akonadi)/database nepomuk/resources etc.|montel@kde.org|Laurent Montel}}

|}
 

= kdeplasma-addons =

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

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

= kdesdk =

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

 

= kdeutils=

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

! Status
! Project
! Description
! Contact

|}

Schedules/KDE4/4.9 Feature Plan

2012-03-17T10:15:32Z

Rhabacker: /* kdesdk */ graphviz dot export

Schedules/KDE4/4.9 Feature Plan

2012-03-07T14:21:40Z

Rhabacker: added umbrello dot export

Schedules/KDE4/4.9 Feature Plan

2012-03-06T06:01:49Z

Rhabacker: added umbrello featues

Projects/KDE on Windows/In the Press

2010-10-30T00:02:16Z

Rhabacker: kde 4.4

;:2010-03-08:[http://linuxhelp.blogspot.com/2010/03/kde-for-windows-overview.html KDE 4.4 For Windows - An Overview]

;:2010-02-22:[http://www.pro-linux.de/news/1/15335/kde-sc-44-fuer-windows-freigegeben.html KDE SC 4.4 for Windows released] (in german)

;:2009-08-13:[http://www.golem.de/0908/69043.html KDE 4.3 for Windows] (in german)

;:2008-06-30:[http://www.simplehelp.net/2008/06/30/how-to-install-and-run-kde-programs-in-windows/ How to Install and run KDE programs in Windows]

;:2008-02-03:[http://apple.slashdot.org/article.pl?sid=08/01/23/1848227 KDE Goes Cross-Platform, Supports Windows and OS X], Zonk, (article referring to ArsTechnica)

;:2008-01-30:[http://mrcopilot.com/2008/01/can-kde-save-dying-windows-platform.html Can KDE Save a Dying Windows Platform], MrCopilot, [http://mrcopilot.com MrCopilot.com]

;:2008-01-23:[http://arstechnica.com/news.ars/post/20080123-kde-goes-cross-platform-with-windows-mac-os-x-support.html KDE goes cross-platform with Windows, Mac OS X support], Ryan Paul, [http://arstechnica.com/authors.ars/segphault]

;:2007-01-31:[http://lxer.com/module/newswire/view/79007/ The Open Source Hook: Porting KDE to Mac and Windows], Scott Ruecker, LXer

Projects/KDE on Windows/In the Press

2010-10-29T23:59:59Z

Rhabacker: kde 4.4 sc

;:2010-02-22:[http://www.pro-linux.de/news/1/15335/kde-sc-44-fuer-windows-freigegeben.html KDE SC 4.4 for Windows released] (in german)

;:2009-08-13:[http://www.golem.de/0908/69043.html KDE 4.3 for Windows] (in german)

;:2008-06-30:[http://www.simplehelp.net/2008/06/30/how-to-install-and-run-kde-programs-in-windows/ How to Install and run KDE programs in Windows]

;:2008-02-03:[http://apple.slashdot.org/article.pl?sid=08/01/23/1848227 KDE Goes Cross-Platform, Supports Windows and OS X], Zonk, (article referring to ArsTechnica)

;:2008-01-30:[http://mrcopilot.com/2008/01/can-kde-save-dying-windows-platform.html Can KDE Save a Dying Windows Platform], MrCopilot, [http://mrcopilot.com MrCopilot.com]

;:2008-01-23:[http://arstechnica.com/news.ars/post/20080123-kde-goes-cross-platform-with-windows-mac-os-x-support.html KDE goes cross-platform with Windows, Mac OS X support], Ryan Paul, [http://arstechnica.com/authors.ars/segphault]

;:2007-01-31:[http://lxer.com/module/newswire/view/79007/ The Open Source Hook: Porting KDE to Mac and Windows], Scott Ruecker, LXer

Projects/KDE on Windows/In the Press

2010-10-29T23:58:29Z

Rhabacker: added kde 4.3. artical

;:2009-08-13:[http://www.golem.de/0908/69043.html KDE 4.3 for Windows] (in german)

;:2008-06-30:[http://www.simplehelp.net/2008/06/30/how-to-install-and-run-kde-programs-in-windows/ How to Install and run KDE programs in Windows]

;:2008-02-03:[http://apple.slashdot.org/article.pl?sid=08/01/23/1848227 KDE Goes Cross-Platform, Supports Windows and OS X], Zonk, (article referring to ArsTechnica)

;:2008-01-30:[http://mrcopilot.com/2008/01/can-kde-save-dying-windows-platform.html Can KDE Save a Dying Windows Platform], MrCopilot, [http://mrcopilot.com MrCopilot.com]

;:2008-01-23:[http://arstechnica.com/news.ars/post/20080123-kde-goes-cross-platform-with-windows-mac-os-x-support.html KDE goes cross-platform with Windows, Mac OS X support], Ryan Paul, [http://arstechnica.com/authors.ars/segphault]

;:2007-01-31:[http://lxer.com/module/newswire/view/79007/ The Open Source Hook: Porting KDE to Mac and Windows], Scott Ruecker, LXer

File:Installer-003.png

2009-08-22T07:17:24Z

Rhabacker: uploaded a new version of "File:Installer-003.png"

Projects/KDE on Windows/Installation

2009-08-22T06:53:47Z

Rhabacker: updated sumary steps, setting path and kdedirs is not required

{{Template:I18n/Language Navigation Bar|Projects/KDE_on_Windows/Installation}}

{{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 pre-compiled 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.

'''If you experience any problems please have a look into our [http://lists.kde.org/?l=kde-windows&r=1&w=2| mailing list].'''

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 ===
* Download and save the latest version of the installer from [http://www.winkde.org/pub/kde/ports/win32/installer/kdewin-installer-gui-latest.exe here] to a directory, e.g. <tt>C:\KDE4</tt>
* Run the installer, download and install what you need (see [[#Download needed packages|Download needed packages]] below).
* Try to run a KDE application from the windows start menu (see for KDE x.x.x Release entry)

=== Download needed packages ===
When you run KDE-installer for the first time, you'll see the welcome screen. Since it's your first launch leave the checkbox below unchecked.
[[File:installer-001.png|600px|left|]]
Proceed to the next screen, where you choose the KDE4 installation directory. It can be anything you prefer, e.g. C:\KDE4.
[[File:installer-002.png|600px|left|]]
 
On the next screen, define who you are: End User or Developer. The End User installation installs only binary packages and libraries needed to run KDE application. Package Manager mode provides you also with the source code for all packages needed to build KDE from scratch.
Then you need to decide what compiler to use - MinGW or MSVC.
[[File:installer-003.png|600px|left|]]
 
Proceed to the next screen and there choose the directory where all the downloaded packages will be stored. Let it be something like C:\KDE4-tmp or C:\KDE4-packages.
[[File:installer-004.png|600px|left|]]
 
The next screen will ask you to choose your internet connection type, particularly whether or not you're using a proxy. If you don't use a proxy server, just click 'Next'. If you are unsure of whether you're using proxy or if you have web browser configured to work with it properly, choose the second or the third option, according to your favourite web-browser. If you'd like to set all the settings manually - choose the last option and go ahead.
[[File:installer-005.png|600px|left|]] 
When you click the 'Next' button the (currently, rather short) list of available servers will be loaded and you could choose the one closest to you.
[[File:installer-006.png|600px|left|]]
 
When you click 'Next', a list of available releases on the selected server will be shown. Depending on the server there may be stable and/or unstable release available. Some unstable releases may only be available from www.winkde.org because the kde mirrors provides only a limited range of unstable releases.
[[File:installer-007.png|600px|left|]]
 
After selecting a release an a click on the 'Next' button, the list of all available packages will be loaded and processed, providing you with the list of package groups you can select for further installation. The short description next to each group of packages should make your choice easier. Select the packages you need. Proceed to the next screen.
[[File:installer-008.png|600px|left|]]
 
Here you can see all the required dependencies, or software necessary to support the choices you've made. Click 'Next' to download them all.
[[File:installer-009.png|600px|left|]]
 
[[File:installer-0010.png|600px|left|]]
After all the packages are downloaded they'll be unpacked and processed by the installer.
[[File:installer-011.png|600px|left|]]
The final window will tell that your KDE installation for Windows is complete.[[File:installer-011.png|600px|left|]]
 

=== Issues with KDE Installer for Windows ===
If something goes wrong during installation, for example a file can't be replaced because it is still in use, the installer may still report successful completion. If you see any alert or failure message from the installer, when it completes, quit and re-run it. 
If that didn't help and you think it's a bug, please report to [mailto:kde-windows@kde.org]

== 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 lskat.exe from the kdegames package.

Look into your start menu: there will be a new entry KDE 4.XX.XX Release. Below that folder you can find all the apps you installed.

=== Startup, shutdown, and diagnosing problems ===
The first KDE program you run should automatically invoke <tt>kdeinit4.exe</tt>, the KDE initialization app,
which starts background KDE applications and services like dbus-daemon, klauncher and kded4.

The first time you save or open, another background application, kioslave, will start.

These background KDE applications and services remain running after you close KDE applications. If you want you can shut them down by running <tt>kdeinit4 --terminate</tt> from a command prompt.

You can run <tt>kdeinit4 --list</tt> from a command prompt to see what processes are running. <tt>kdeinit4</tt> has other useful options documented elsewhere.

== Fine-tuning ==
=== Common step: editing the kdeglobals file ===
Unless otherwise stated you make all the setting changes below by editing the <tt>kdeglobals</tt> file in the directory <tt>%APPDATA%\.kde\share\config\</tt> with any text editor (such as kwrite).
(Note that for versions older than 4.0.85 the file is in <tt>%USERPROFILE%\.kde\share\config\kdeglobals</tt>.)
%APPDATA% (and %USERPROFILE%) is different for different Windows users/versions/locales; in a command prompt, entering the command <tt>cd %APPDATA%</tt> will switch to it, effectively telling you what it is.

===Set Oxygen style for widgets===
The default KDE widget style on Windows is the native one. The Oxygen style installs with basic KDE installation (as a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:
# edit kdeglobals
#locate the General section (a line containing the text "[General]"). If there is no General section, create one.
#Within the General section ([General]), edit the line containing <tt>widgetStyle=....</tt> so that it reads <tt>widgetStyle=oxygen</tt>. If there is no such <tt>widgetStyle=...</tt> line, create it.
Newly started applications should be displayed with the Oxygen style now.

===Set Tahoma (Windows default font) for widgets===
To set it for a single user:
# edit kdeglobals
#locate the General section (a line containing the text "[General]"). If there is no General section, create one.
#Within the General section ([General]), add these two lines:
<tt>font=Tahoma 
menuFont=Tahoma</tt>

Newly started applications should use this font now.
Note: this works for any font you have installed.

===Change the mouse to Double Click===
To change the mouse to use double click:
#Add a new section with a line: 
<tt>[KDE] 
SingleClick=false</tt> 
Newly started applications (Dolphin and Konqueror) should use double click now.
===Change locale and country settings===
To change locale setting:
#Add a new section with the line: 
<tt>[Locale] 
Country=** 
Language=**</tt> 
Replace ** with your lowercase [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 alpha-2 country code], e.g. pl for Poland; of course, you need to install your language localization package.
===Change native/KDE file dialogs===
To chose native or KDE file dialog:
#Add a new section with the lines: 
<tt> [KFileDialog Settings] 
Native=false</tt> 
Either set Native to true or false.

== Status ==
Using kdewin-installer-gui-0.9.3.exe to install 4.1.3 packages:
* starting a KDE program correctly starts dbus-daemon.exe
* many games run
* choosing File > Open correctly starts klauncher.exe, kioslave.exe and kded4.exe, and runs kbuildsycoca4.exe as needed.
* Full-text search in khelpcenter does not work because Perl scripts are disabled.
* Many applications have a generic icon in Windows Explorer.
* Multimedia support should work, although video support might be missing (from the backend)

General notes:
* There are many other KDE programs that are not part of KDE 4.0.0 and are not currently packaged for MS Windows.
* By design, KDE-windows does not provide the full-blown KDE desktop, a preview on the plasma shell replacement will be available in 4.1.2 - Nevertheless this does not rely on kwin/X11 which means that desktop effects are not available
* Some KDE programs use UNIX-specific features, such as konsole's use of pseudo-terminals, and thus are difficult (read: currently impossible) to port to MS Windows.

=== Package status and contents ===
{| border="0" cellpadding="2"
|-valign="top"
!package
!status
!contains applications
|-valign="top"
|amarok
|packaged
|Amarok music player
|-valign="top"
|Digikam
|packaged
|Photo management
|-valign="top"
|kdebase-apps
|packaged
|Konqueror, Dolphin, KWrite, folderview etc.
|-valign="top"
|kdebase-workspace
|packaged
|Plasma, Wallpapers, Solid, etc.
|-valign="top"
|kdeedu
|packaged
|Marble, Parley, KStars, KHangman, etc.
|-valign="top"
|kdegames
|packaged
|Kgoldrunner, Kpat, KMahjongg, etc.
|-valign="top"
|kdegraphics
|packaged
|Okular, kolourpaint, gwenview, etc.
|-valign="top"
|kdemultimedia
|packaged
|JuK, etc.
|-valign="top"
|kdenetwork
|packaged
|Kopete, KGet, etc.
|-valign="top"
|kdepim
|not packaged
|KMail, AKregator, etc.
|-valign="top"
|kdesdk
|packaged
|Kate, Umbrello, etc.
|-valign="top"
|kdetoys
|packaged
|KTeatime, etc.
|-valign="top"
|kdeutils
|packaged
|KGpg, KWallet, Okteta, etc.
|-valign="top"
|koffice
|packaged
|KWord, Krita, Karbon, etc. (Beta 3)
|-valign="top"
|ktorrent
|packaged
|the KTorrent utility
|-valign="top"
|konversation
|packaged
|the KDE IRC client (alpha 3)
|}

[[Category: MS Windows]]

Projects/KDE on Windows/Installation

2009-08-22T06:51:41Z

Rhabacker: added installer images

{{Template:I18n/Language Navigation Bar|Projects/KDE_on_Windows/Installation}}

{{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 pre-compiled 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.

'''If you experience any problems please have a look into our [http://lists.kde.org/?l=kde-windows&r=1&w=2| mailing list].'''

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://www.winkde.org/pub/kde/ports/win32/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|Download needed packages]] below).
* 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>).
* Add your lib directory and your bin directory to your Windows %PATH%. (Start > Control Panel > System > Advanced > Environment Variables, double-click the Path System Variable and add "<tt>%KDEDIRS%\lib;%KDEDIRS%\bin</tt>" to your path separated by semicolon.)
* If you don't have Visual Studio 2005 installed, download and install the "Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)" [http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en]
* 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>kwrite.exe</tt>.

=== Download needed packages ===
When you run KDE-installer for the first time, you'll see the welcome screen. Since it's your first launch leave the checkbox below unchecked.
[[File:installer-001.png|600px|left|]]
Proceed to the next screen, where you choose the KDE4 installation directory. It can be anything you prefer, e.g. C:\KDE4.
[[File:installer-002.png|600px|left|]]
 
On the next screen, define who you are: End User or Developer. The End User installation installs only binary packages and libraries needed to run KDE application. Package Manager mode provides you also with the source code for all packages needed to build KDE from scratch.
Then you need to decide what compiler to use - MinGW or MSVC.
[[File:installer-003.png|600px|left|]]
 
Proceed to the next screen and there choose the directory where all the downloaded packages will be stored. Let it be something like C:\KDE4-tmp or C:\KDE4-packages.
[[File:installer-004.png|600px|left|]]
 
The next screen will ask you to choose your internet connection type, particularly whether or not you're using a proxy. If you don't use a proxy server, just click 'Next'. If you are unsure of whether you're using proxy or if you have web browser configured to work with it properly, choose the second or the third option, according to your favourite web-browser. If you'd like to set all the settings manually - choose the last option and go ahead.
[[File:installer-005.png|600px|left|]] 
When you click the 'Next' button the (currently, rather short) list of available servers will be loaded and you could choose the one closest to you.
[[File:installer-006.png|600px|left|]]
 
When you click 'Next', a list of available releases on the selected server will be shown. Depending on the server there may be stable and/or unstable release available. Some unstable releases may only be available from www.winkde.org because the kde mirrors provides only a limited range of unstable releases.
[[File:installer-007.png|600px|left|]]
 
After selecting a release an a click on the 'Next' button, the list of all available packages will be loaded and processed, providing you with the list of package groups you can select for further installation. The short description next to each group of packages should make your choice easier. Select the packages you need. Proceed to the next screen.
[[File:installer-008.png|600px|left|]]
 
Here you can see all the required dependencies, or software necessary to support the choices you've made. Click 'Next' to download them all.
[[File:installer-009.png|600px|left|]]
 
[[File:installer-0010.png|600px|left|]]
After all the packages are downloaded they'll be unpacked and processed by the installer.
[[File:installer-011.png|600px|left|]]
The final window will tell that your KDE installation for Windows is complete.[[File:installer-011.png|600px|left|]]
 

=== Issues with KDE Installer for Windows ===
If something goes wrong during installation, for example a file can't be replaced because it is still in use, the installer may still report successful completion. If you see any alert or failure message from the installer, when it completes, quit and re-run it. 
If that didn't help and you think it's a bug, please report to [mailto:kde-windows@kde.org]

== 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 lskat.exe from the kdegames package.

Look into your start menu: there will be a new entry KDE 4.XX.XX Release. Below that folder you can find all the apps you installed.

=== Startup, shutdown, and diagnosing problems ===
The first KDE program you run should automatically invoke <tt>kdeinit4.exe</tt>, the KDE initialization app,
which starts background KDE applications and services like dbus-daemon, klauncher and kded4.

The first time you save or open, another background application, kioslave, will start.

These background KDE applications and services remain running after you close KDE applications. If you want you can shut them down by running <tt>kdeinit4 --terminate</tt> from a command prompt.

You can run <tt>kdeinit4 --list</tt> from a command prompt to see what processes are running. <tt>kdeinit4</tt> has other useful options documented elsewhere.

== Fine-tuning ==
=== Common step: editing the kdeglobals file ===
Unless otherwise stated you make all the setting changes below by editing the <tt>kdeglobals</tt> file in the directory <tt>%APPDATA%\.kde\share\config\</tt> with any text editor (such as kwrite).
(Note that for versions older than 4.0.85 the file is in <tt>%USERPROFILE%\.kde\share\config\kdeglobals</tt>.)
%APPDATA% (and %USERPROFILE%) is different for different Windows users/versions/locales; in a command prompt, entering the command <tt>cd %APPDATA%</tt> will switch to it, effectively telling you what it is.

===Set Oxygen style for widgets===
The default KDE widget style on Windows is the native one. The Oxygen style installs with basic KDE installation (as a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:
# edit kdeglobals
#locate the General section (a line containing the text "[General]"). If there is no General section, create one.
#Within the General section ([General]), edit the line containing <tt>widgetStyle=....</tt> so that it reads <tt>widgetStyle=oxygen</tt>. If there is no such <tt>widgetStyle=...</tt> line, create it.
Newly started applications should be displayed with the Oxygen style now.

===Set Tahoma (Windows default font) for widgets===
To set it for a single user:
# edit kdeglobals
#locate the General section (a line containing the text "[General]"). If there is no General section, create one.
#Within the General section ([General]), add these two lines:
<tt>font=Tahoma 
menuFont=Tahoma</tt>

Newly started applications should use this font now.
Note: this works for any font you have installed.

===Change the mouse to Double Click===
To change the mouse to use double click:
#Add a new section with a line: 
<tt>[KDE] 
SingleClick=false</tt> 
Newly started applications (Dolphin and Konqueror) should use double click now.
===Change locale and country settings===
To change locale setting:
#Add a new section with the line: 
<tt>[Locale] 
Country=** 
Language=**</tt> 
Replace ** with your lowercase [http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 alpha-2 country code], e.g. pl for Poland; of course, you need to install your language localization package.
===Change native/KDE file dialogs===
To chose native or KDE file dialog:
#Add a new section with the lines: 
<tt> [KFileDialog Settings] 
Native=false</tt> 
Either set Native to true or false.

== Status ==
Using kdewin-installer-gui-0.9.3.exe to install 4.1.3 packages:
* starting a KDE program correctly starts dbus-daemon.exe
* many games run
* choosing File > Open correctly starts klauncher.exe, kioslave.exe and kded4.exe, and runs kbuildsycoca4.exe as needed.
* Full-text search in khelpcenter does not work because Perl scripts are disabled.
* Many applications have a generic icon in Windows Explorer.
* Multimedia support should work, although video support might be missing (from the backend)

General notes:
* There are many other KDE programs that are not part of KDE 4.0.0 and are not currently packaged for MS Windows.
* By design, KDE-windows does not provide the full-blown KDE desktop, a preview on the plasma shell replacement will be available in 4.1.2 - Nevertheless this does not rely on kwin/X11 which means that desktop effects are not available
* Some KDE programs use UNIX-specific features, such as konsole's use of pseudo-terminals, and thus are difficult (read: currently impossible) to port to MS Windows.

=== Package status and contents ===
{| border="0" cellpadding="2"
|-valign="top"
!package
!status
!contains applications
|-valign="top"
|amarok
|packaged
|Amarok music player
|-valign="top"
|Digikam
|packaged
|Photo management
|-valign="top"
|kdebase-apps
|packaged
|Konqueror, Dolphin, KWrite, folderview etc.
|-valign="top"
|kdebase-workspace
|packaged
|Plasma, Wallpapers, Solid, etc.
|-valign="top"
|kdeedu
|packaged
|Marble, Parley, KStars, KHangman, etc.
|-valign="top"
|kdegames
|packaged
|Kgoldrunner, Kpat, KMahjongg, etc.
|-valign="top"
|kdegraphics
|packaged
|Okular, kolourpaint, gwenview, etc.
|-valign="top"
|kdemultimedia
|packaged
|JuK, etc.
|-valign="top"
|kdenetwork
|packaged
|Kopete, KGet, etc.
|-valign="top"
|kdepim
|not packaged
|KMail, AKregator, etc.
|-valign="top"
|kdesdk
|packaged
|Kate, Umbrello, etc.
|-valign="top"
|kdetoys
|packaged
|KTeatime, etc.
|-valign="top"
|kdeutils
|packaged
|KGpg, KWallet, Okteta, etc.
|-valign="top"
|koffice
|packaged
|KWord, Krita, Karbon, etc. (Beta 3)
|-valign="top"
|ktorrent
|packaged
|the KTorrent utility
|-valign="top"
|konversation
|packaged
|the KDE IRC client (alpha 3)
|}

[[Category: MS Windows]]

File:Installer-012.png

2009-08-22T06:22:03Z

Rhabacker:

File:Installer-011.png

2009-08-22T06:21:36Z

Rhabacker:

File:Installer-010.png

2009-08-22T06:21:26Z

Rhabacker:

File:Installer-009.png

2009-08-22T06:21:17Z

Rhabacker:

File:Installer-008.png

2009-08-22T06:21:05Z

Rhabacker:

File:Installer-007.png

2009-08-22T06:20:50Z

Rhabacker:

File:Installer-006.png

2009-08-22T06:20:37Z

Rhabacker:

File:Installer-005.png

2009-08-22T06:20:28Z

Rhabacker:

File:Installer-004.png

2009-08-22T06:20:21Z

Rhabacker:

File:Installer-003.png

2009-08-22T06:20:13Z

Rhabacker:

File:Installer-002.png

2009-08-22T06:18:47Z

Rhabacker:

File:Installer-001.png

2009-08-22T06:16:39Z

Rhabacker:

Projects/KDE on Windows/Issues/kdewin-installer

2009-08-22T05:44:18Z

Rhabacker: wishes are implemented already

== Issues ==
Issues that should be considered for the KDEWin-Installer:
* currently no issues known

== Wishes ==
[[Category:MS Windows]]

== Long time goals ==
*Give more meaningful installation progress: show the whole data size to be downloaded, show download speed calculated over the whole duration, estimate time needed for the whole installation to complete
*Centralize redistributable Qt and KDE files around the KDEWin-Installer (putting location in PATH?)
*Allow third party KDE/Qt app to reuse the installer to check if all their dependencies are already installed, and download where necessary
*Polish the installer to look and behave like other installers on Windows, including customizable app specific branding with all packages and dependency resolution hidden from the user
*Specify human readable installation configuration file containing all the customizing options for third party app developers, allowing running KDEWin-Installer from this file locally or from the net as 1-click-install solution
*Aggressively promote KDEWin-Installer as *the* one stop KDE/Qt software distribution solution on Windows systems

Projects/KDE on Windows/In the Press

2009-07-24T22:17:44Z

Rhabacker: added install how to

;:2008-06-30:[http://www.simplehelp.net/2008/06/30/how-to-install-and-run-kde-programs-in-windows/ How to Install and run KDE programs in Windows]

;:2008-02-03:[http://apple.slashdot.org/article.pl?sid=08/01/23/1848227 KDE Goes Cross-Platform, Supports Windows and OS X], Zonk, (article referring to ArsTechnica)

;:2008-01-30:[http://mrcopilot.com/2008/01/can-kde-save-dying-windows-platform.html Can KDE Save a Dying Windows Platform], MrCopilot, [http://mrcopilot.com MrCopilot.com]

;:2008-01-23:[http://arstechnica.com/news.ars/post/20080123-kde-goes-cross-platform-with-windows-mac-os-x-support.html KDE goes cross-platform with Windows, Mac OS X support], Ryan Paul, [http://arstechnica.com/authors.ars/segphault]

;:2007-01-31:[http://lxer.com/module/newswire/view/79007/ The Open Source Hook: Porting KDE to Mac and Windows], Scott Ruecker, LXer

Projects/KDE on Windows/FAQ

2009-06-15T19:53:22Z

Rhabacker:

__TOC__

== Technical ==

==== How to replace windows explorer as shell ? ====
Download and run autorun from http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx - enter the tab 'Logon' and replace the value of HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell with the dolphin path - but - be aware that explorer provides almost everything in the system settings area and other stuff.

==== What versions of windows does KDE windows work on? ====
KDE4 is known to run on various versions of Windows XP and Vista, as well as the upcoming Windows 7.

==== Does KDE windows use additional resources or does it replace any windows resources with it's own? ====

==== Is it easy to uninstall if I don't want it on my system? ====
It is easy to uninstall. You can run the installer and select the "Remove installed packages" option. To clean out your personal settings, you will need to remove the ".kde" directory in your Application Data directory (%APPDATA%).

==== Is it stable? ====
No, it is not stable yet. While most of the applications should run fine, there are a lot of problems that come in with porting software to new platforms.
The KDE on Windows team is working hard to fix bugs and resolve issues with this port, so be patient and let them know what you think.

==== Is it possible to replace Windows' WM with KWin or would it ever be? ====

== Reasons for KDE on Windows ==

==== [http://dot.kde.org/2009/06/08/kde-windows-continues ... tell me who except über geeks needs KDE on Windows]? ====
We need KDE on Windows for three reasons:

1. Most businesses can't just switch to Linux. I've heard more than enough stories of workers being stucked with Windows as they're of course not allowed or able (because of special apps) to convert their boxes to Linux. KDE might provide them with a comfortable working environment to which they are used.

2. Most businesses won't suddenly switch. Clear step-by-step migration paths (Windows + Office + Explorer -> Windows + OpenOffice + Konqueror -> Linux + OpenOffice + Konqueror) make it easier for the IT deciders to enter this process. (Something along the lines of "If the users do not like Konqueror, they can still use Explorer.") Yes, I know that Konqueror is not a good example, as many Windows users have just learned Firefox and will most probably not look into learning yet another browser.

3. Having FOSS applications available on the Windows platform is crucial for attracting users. Not many people go into the store and buy a SuSE box, but many people get single FOSS apps like OOo or Firefox because they read about it in some magazine, or some friend recommended it to them.

==== [http://dot.kde.org/2009/06/08/kde-windows-continues KDE on windows attracts developer] ====
A few years ago (leading up to Akademy 2007 IIRC) we had a huge discussion on the planet about the merits of making KDE applications available on Windows. The core of my argument for doing that then was, and still is, that its really in the interest of KDE to do this because it attracts developers who would otherwise not contribute.

Take Amarok for instance. The core developers spend very little time on making Amarok run on windows (I think the total amount of work I have done on this amounts to one time changing the order of some things in a CMake file as someone reported that it otherwise broke the build on Windows.) So all in all, this is not something that takes much time away from developing Amarok itself. On the other hand, the original implementation of the Last.fm service was written by a developer whose original intention was to make Amarok work better on Windows. Once he had gotten as far as he could at the time, he started, still using Windows, to hack on other stuff that benefits all users of Amarok. He did not use linux at all, and only contributed because it was possible to run and work on Amarok using Windows.

So I really think it is wrong to look at this as a zero sum game as time spent making stuff run on windows is not automatically time taken away from developing the core application. Quite contrary, making the application usable on other platforms will also attract developers who would not otherwise have worked on it. Of course there is a tipping point for this as the applications have to be working well and have a significant user base on Windows before any significant amount of developers shows up, but as my example about Amarok illustrates, people are already taking notice.

And then there is the whole issue about philosophy. To me, Free Software is about just that, freedom. I think it would be against the spirit of that to artificially limit the platforms that our software runs on. that is for all the "other" guys to do, I think we are better than that! :-)

==== [http://dot.kde.org/2009/06/08/kde-windows-continues Morty wrote - Not the desktop] ====
... The power of KDE are it's library and the applications made with it, and those are also interresting for the Windows platform.

And for KDE as a whole, any developers brought in and bugs fixed by the Windows port are a net win for KDE.

====[http://dot.kde.org/2009/06/08/kde-windows-continues majorTomBelgium wrote about amarok, dolphin, ...] ====
really, having all the nice kde programs available on windows is very cool. amarok, dolphin, ktorrent, kwrite, etc. and also, the educational programs are important.

+1 for kde on windows for me! it's like an artist being on a smaller label with almost no air time converting to a bigger label and getting his records played on the radio...

Projects/KDE on Windows/FAQ

2009-06-15T19:51:16Z

Rhabacker: update entry title

__TOC__

== Technical ==

==== How to replace windows explorer as shell ? ====
Download and run autorun from http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx - enter the tab 'Logon' and replace the value of HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell with the dolphin path - but - be aware that explorer provides almost everything in the system settings area and other stuff.

==== What versions of windows does KDE windows work on? ====
KDE4 is known to run on various versions of Windows XP and Vista, as well as the upcoming Windows 7.

==== Does KDE windows use additional resources or does it replace any windows resources with it's own? ====

* Is it easy to uninstall if I don't want it on my system?
It is easy to uninstall. You can run the installer and select the "Remove installed packages" option. To clean out your personal settings, you will need to remove the ".kde" directory in your Application Data directory (%APPDATA%).

==== Is it stable? ====
No, it is not stable yet. While most of the applications should run fine, there are a lot of problems that come in with porting software to new platforms.
The KDE on Windows team is working hard to fix bugs and resolve issues with this port, so be patient and let them know what you think.

==== Is it possible to replace Windows' WM with KWin or would it ever be? ====

== Reasons for KDE on Windows ==

==== ... [http://dot.kde.org/2009/06/08/kde-windows-continues tell me who except über geeks needs KDE on Windows]? ====
We need KDE on Windows for three reasons:

1. Most businesses can't just switch to Linux. I've heard more than enough stories of workers being stucked with Windows as they're of course not allowed or able (because of special apps) to convert their boxes to Linux. KDE might provide them with a comfortable working environment to which they are used.

2. Most businesses won't suddenly switch. Clear step-by-step migration paths (Windows + Office + Explorer -> Windows + OpenOffice + Konqueror -> Linux + OpenOffice + Konqueror) make it easier for the IT deciders to enter this process. (Something along the lines of "If the users do not like Konqueror, they can still use Explorer.") Yes, I know that Konqueror is not a good example, as many Windows users have just learned Firefox and will most probably not look into learning yet another browser.

3. Having FOSS applications available on the Windows platform is crucial for attracting users. Not many people go into the store and buy a SuSE box, but many people get single FOSS apps like OOo or Firefox because they read about it in some magazine, or some friend recommended it to them.

==== [http://dot.kde.org/2009/06/08/kde-windows-continues KDE on windows attracts developer] ====
A few years ago (leading up to Akademy 2007 IIRC) we had a huge discussion on the planet about the merits of making KDE applications available on Windows. The core of my argument for doing that then was, and still is, that its really in the interest of KDE to do this because it attracts developers who would otherwise not contribute.

Take Amarok for instance. The core developers spend very little time on making Amarok run on windows (I think the total amount of work I have done on this amounts to one time changing the order of some things in a CMake file as someone reported that it otherwise broke the build on Windows.) So all in all, this is not something that takes much time away from developing Amarok itself. On the other hand, the original implementation of the Last.fm service was written by a developer whose original intention was to make Amarok work better on Windows. Once he had gotten as far as he could at the time, he started, still using Windows, to hack on other stuff that benefits all users of Amarok. He did not use linux at all, and only contributed because it was possible to run and work on Amarok using Windows.

So I really think it is wrong to look at this as a zero sum game as time spent making stuff run on windows is not automatically time taken away from developing the core application. Quite contrary, making the application usable on other platforms will also attract developers who would not otherwise have worked on it. Of course there is a tipping point for this as the applications have to be working well and have a significant user base on Windows before any significant amount of developers shows up, but as my example about Amarok illustrates, people are already taking notice.

And then there is the whole issue about philosophy. To me, Free Software is about just that, freedom. I think it would be against the spirit of that to artificially limit the platforms that our software runs on. that is for all the "other" guys to do, I think we are better than that! :-)

==== [http://dot.kde.org/2009/06/08/kde-windows-continues Morty wrote - Not the desktop] ====
... The power of KDE are it's library and the applications made with it, and those are also interresting for the Windows platform.

And for KDE as a whole, any developers brought in and bugs fixed by the Windows port are a net win for KDE.

====[http://dot.kde.org/2009/06/08/kde-windows-continues majorTomBelgium wrote about amarok, dolphin, ...] ====
really, having all the nice kde programs available on windows is very cool. amarok, dolphin, ktorrent, kwrite, etc. and also, the educational programs are important.

+1 for kde on windows for me! it's like an artist being on a smaller label with almost no air time converting to a bigger label and getting his records played on the radio...

Projects/KDE on Windows/FAQ

2009-06-15T19:49:54Z

Rhabacker: added entry

__TOC__

== Technical ==

==== How to replace windows explorer as shell ? ====
Download and run autorun from http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx - enter the tab 'Logon' and replace the value of HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell with the dolphin path - but - be aware that explorer provides almost everything in the system settings area and other stuff.

==== What versions of windows does KDE windows work on? ====
KDE4 is known to run on various versions of Windows XP and Vista, as well as the upcoming Windows 7.

==== Does KDE windows use additional resources or does it replace any windows resources with it's own? ====

* Is it easy to uninstall if I don't want it on my system?
It is easy to uninstall. You can run the installer and select the "Remove installed packages" option. To clean out your personal settings, you will need to remove the ".kde" directory in your Application Data directory (%APPDATA%).

==== Is it stable? ====
No, it is not stable yet. While most of the applications should run fine, there are a lot of problems that come in with porting software to new platforms.
The KDE on Windows team is working hard to fix bugs and resolve issues with this port, so be patient and let them know what you think.

==== Is it possible to replace Windows' WM with KWin or would it ever be? ====

== Reasons for KDE on Windows ==

==== ... [http://dot.kde.org/2009/06/08/kde-windows-continues tell me who except über geeks needs KDE on Windows]? ====
We need KDE on Windows for three reasons:

1. Most businesses can't just switch to Linux. I've heard more than enough stories of workers being stucked with Windows as they're of course not allowed or able (because of special apps) to convert their boxes to Linux. KDE might provide them with a comfortable working environment to which they are used.

2. Most businesses won't suddenly switch. Clear step-by-step migration paths (Windows + Office + Explorer -> Windows + OpenOffice + Konqueror -> Linux + OpenOffice + Konqueror) make it easier for the IT deciders to enter this process. (Something along the lines of "If the users do not like Konqueror, they can still use Explorer.") Yes, I know that Konqueror is not a good example, as many Windows users have just learned Firefox and will most probably not look into learning yet another browser.

3. Having FOSS applications available on the Windows platform is crucial for attracting users. Not many people go into the store and buy a SuSE box, but many people get single FOSS apps like OOo or Firefox because they read about it in some magazine, or some friend recommended it to them.

==== [http://dot.kde.org/2009/06/08/kde-windows-continues KDE on windows attracts developer] ====
A few years ago (leading up to Akademy 2007 IIRC) we had a huge discussion on the planet about the merits of making KDE applications available on Windows. The core of my argument for doing that then was, and still is, that its really in the interest of KDE to do this because it attracts developers who would otherwise not contribute.

Take Amarok for instance. The core developers spend very little time on making Amarok run on windows (I think the total amount of work I have done on this amounts to one time changing the order of some things in a CMake file as someone reported that it otherwise broke the build on Windows.) So all in all, this is not something that takes much time away from developing Amarok itself. On the other hand, the original implementation of the Last.fm service was written by a developer whose original intention was to make Amarok work better on Windows. Once he had gotten as far as he could at the time, he started, still using Windows, to hack on other stuff that benefits all users of Amarok. He did not use linux at all, and only contributed because it was possible to run and work on Amarok using Windows.

So I really think it is wrong to look at this as a zero sum game as time spent making stuff run on windows is not automatically time taken away from developing the core application. Quite contrary, making the application usable on other platforms will also attract developers who would not otherwise have worked on it. Of course there is a tipping point for this as the applications have to be working well and have a significant user base on Windows before any significant amount of developers shows up, but as my example about Amarok illustrates, people are already taking notice.

And then there is the whole issue about philosophy. To me, Free Software is about just that, freedom. I think it would be against the spirit of that to artificially limit the platforms that our software runs on. that is for all the "other" guys to do, I think we are better than that! :-)

==== [http://dot.kde.org/2009/06/08/kde-windows-continues Morty wrote] ====
... The power of KDE are it's library and the applications made with it, and those are also interresting for the Windows platform.

And for KDE as a whole, any developers brought in and bugs fixed by the Windows port are a net win for KDE.

====[http://dot.kde.org/2009/06/08/kde-windows-continues majorTomBelgium wrote about amarok, dolphin, ...] ====
really, having all the nice kde programs available on windows is very cool. amarok, dolphin, ktorrent, kwrite, etc. and also, the educational programs are important.

+1 for kde on windows for me! it's like an artist being on a smaller label with almost no air time converting to a bigger label and getting his records played on the radio...

Projects/KDE on Windows/FAQ

2009-06-15T19:46:31Z

Rhabacker: restructered technical faq entries

__TOC__

== Technical ==

==== How to replace windows explorer as shell ? ====
Download and run autorun from http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx - enter the tab 'Logon' and replace the value of HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell with the dolphin path - but - be aware that explorer provides almost everything in the system settings area and other stuff.

==== What versions of windows does KDE windows work on? ====
KDE4 is known to run on various versions of Windows XP and Vista, as well as the upcoming Windows 7.

==== Does KDE windows use additional resources or does it replace any windows resources with it's own? ====

* Is it easy to uninstall if I don't want it on my system?
It is easy to uninstall. You can run the installer and select the "Remove installed packages" option. To clean out your personal settings, you will need to remove the ".kde" directory in your Application Data directory (%APPDATA%).

==== Is it stable? ====
No, it is not stable yet. While most of the applications should run fine, there are a lot of problems that come in with porting software to new platforms.
The KDE on Windows team is working hard to fix bugs and resolve issues with this port, so be patient and let them know what you think.

==== Is it possible to replace Windows' WM with KWin or would it ever be? ====

== Reasons for KDE on Windows ==

==== ... [http://dot.kde.org/2009/06/08/kde-windows-continues tell me who except über geeks needs KDE on Windows]? ====
We need KDE on Windows for three reasons:

1. Most businesses can't just switch to Linux. I've heard more than enough stories of workers being stucked with Windows as they're of course not allowed or able (because of special apps) to convert their boxes to Linux. KDE might provide them with a comfortable working environment to which they are used.

2. Most businesses won't suddenly switch. Clear step-by-step migration paths (Windows + Office + Explorer -> Windows + OpenOffice + Konqueror -> Linux + OpenOffice + Konqueror) make it easier for the IT deciders to enter this process. (Something along the lines of "If the users do not like Konqueror, they can still use Explorer.") Yes, I know that Konqueror is not a good example, as many Windows users have just learned Firefox and will most probably not look into learning yet another browser.

3. Having FOSS applications available on the Windows platform is crucial for attracting users. Not many people go into the store and buy a SuSE box, but many people get single FOSS apps like OOo or Firefox because they read about it in some magazine, or some friend recommended it to them.

==== [http://dot.kde.org/2009/06/08/kde-windows-continues KDE on windows attracts developer] ====
A few years ago (leading up to Akademy 2007 IIRC) we had a huge discussion on the planet about the merits of making KDE applications available on Windows. The core of my argument for doing that then was, and still is, that its really in the interest of KDE to do this because it attracts developers who would otherwise not contribute.

Take Amarok for instance. The core developers spend very little time on making Amarok run on windows (I think the total amount of work I have done on this amounts to one time changing the order of some things in a CMake file as someone reported that it otherwise broke the build on Windows.) So all in all, this is not something that takes much time away from developing Amarok itself. On the other hand, the original implementation of the Last.fm service was written by a developer whose original intention was to make Amarok work better on Windows. Once he had gotten as far as he could at the time, he started, still using Windows, to hack on other stuff that benefits all users of Amarok. He did not use linux at all, and only contributed because it was possible to run and work on Amarok using Windows.

So I really think it is wrong to look at this as a zero sum game as time spent making stuff run on windows is not automatically time taken away from developing the core application. Quite contrary, making the application usable on other platforms will also attract developers who would not otherwise have worked on it. Of course there is a tipping point for this as the applications have to be working well and have a significant user base on Windows before any significant amount of developers shows up, but as my example about Amarok illustrates, people are already taking notice.

And then there is the whole issue about philosophy. To me, Free Software is about just that, freedom. I think it would be against the spirit of that to artificially limit the platforms that our software runs on. that is for all the "other" guys to do, I think we are better than that! :-)

==== [http://dot.kde.org/2009/06/08/kde-windows-continues Morty wrote] ====
... The power of KDE are it's library and the applications made with it, and those are also interresting for the Windows platform.

And for KDE as a whole, any developers brought in and bugs fixed by the Windows port are a net win for KDE.

Projects/KDE on Windows/FAQ

2009-06-15T19:35:32Z

Rhabacker: added two topics to reasons section

__TOC__

== Technical ==

* How to replace windows explorer as shell ?
Download and run autorun from http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx - enter the tab 'Logon' and replace the value of HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell with the dolphin path - but - be aware that explorer provides almost everything in the system settings area and other stuff.

* What versions of windows does KDE windows work on?
KDE4 is known to run on various versions of Windows XP and Vista, as well as the upcoming Windows 7.

* Does KDE windows use additional resources or does it replace any windows resources with it's own?

* Is it easy to uninstall if I don't want it on my system?
It is easy to uninstall. You can run the installer and select the "Remove installed packages" option. To clean out your personal settings, you will need to remove the ".kde" directory in your Application Data directory (%APPDATA%).

* Is it stable?
No, it is not stable yet. While most of the applications should run fine, there are a lot of problems that come in with porting software to new platforms.
The KDE on Windows team is working hard to fix bugs and resolve issues with this port, so be patient and let them know what you think.

* Is it possible to replace Windows' WM with KWin or would it ever be?

== Reasons for KDE on Windows ==

* ... [http://dot.kde.org/2009/06/08/kde-windows-continues tell me who except über geeks needs KDE on Windows]?
We need KDE on Windows for three reasons:

1. Most businesses can't just switch to Linux. I've heard more than enough stories of workers being stucked with Windows as they're of course not allowed or able (because of special apps) to convert their boxes to Linux. KDE might provide them with a comfortable working environment to which they are used.

2. Most businesses won't suddenly switch. Clear step-by-step migration paths (Windows + Office + Explorer -> Windows + OpenOffice + Konqueror -> Linux + OpenOffice + Konqueror) make it easier for the IT deciders to enter this process. (Something along the lines of "If the users do not like Konqueror, they can still use Explorer.") Yes, I know that Konqueror is not a good example, as many Windows users have just learned Firefox and will most probably not look into learning yet another browser.

3. Having FOSS applications available on the Windows platform is crucial for attracting users. Not many people go into the store and buy a SuSE box, but many people get single FOSS apps like OOo or Firefox because they read about it in some magazine, or some friend recommended it to them.

* [http://dot.kde.org/2009/06/08/kde-windows-continues KDE on windows attracts developer]
A few years ago (leading up to Akademy 2007 IIRC) we had a huge discussion on the planet about the merits of making KDE applications available on Windows. The core of my argument for doing that then was, and still is, that its really in the interest of KDE to do this because it attracts developers who would otherwise not contribute.

Take Amarok for instance. The core developers spend very little time on making Amarok run on windows (I think the total amount of work I have done on this amounts to one time changing the order of some things in a CMake file as someone reported that it otherwise broke the build on Windows.) So all in all, this is not something that takes much time away from developing Amarok itself. On the other hand, the original implementation of the Last.fm service was written by a developer whose original intention was to make Amarok work better on Windows. Once he had gotten as far as he could at the time, he started, still using Windows, to hack on other stuff that benefits all users of Amarok. He did not use linux at all, and only contributed because it was possible to run and work on Amarok using Windows.

So I really think it is wrong to look at this as a zero sum game as time spent making stuff run on windows is not automatically time taken away from developing the core application. Quite contrary, making the application usable on other platforms will also attract developers who would not otherwise have worked on it. Of course there is a tipping point for this as the applications have to be working well and have a significant user base on Windows before any significant amount of developers shows up, but as my example about Amarok illustrates, people are already taking notice.

And then there is the whole issue about philosophy. To me, Free Software is about just that, freedom. I think it would be against the spirit of that to artificially limit the platforms that our software runs on. that is for all the "other" guys to do, I think we are better than that! :-)

Getting Started/Build/Windows/DistributionBasedBuild

2009-04-05T06:38:55Z

Rhabacker: added package making

This page describes (re)building of KDE binary packages using the kdewin distribution.

Applications build in this way will not have debugging support because the packages build in release mode do not have any debug symbols. If you need debug symbols you should use the [[Getting Started/Build/KDE4/Windows/emerge|Windows ''emerge'' tool]]

It is assumed that KDE is installed using the KDEWin gui or console installer in %PROGRAMFILES%\kde and a developer tries to recompile the kdeedu binary package.
It is also assumed that the KDE installation tree is empty or contains only packages for the related compiler.

== (Re)building packages for MS Visual Studio C++ ==

* download [http://www.winkde.org/pub/kde/ports/win32/installer/kdewin-installer-gui-latest.exe KDE windows installer]

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* choose the '''all''' category and select (at least) the following packages
** kdeedu bin and source package - this will also select all depending packages
** automoc
** cmake
** perl
** psdk-msvc
** one of the vcexpress-xx-msvc package
** the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-msvc, kdebase-runtime-msvc and qt-msvc are required.

* install the selected packages using the installer.

* open a Visual Studio command prompt

* set the required environment for the MS Platform SDK e.g. if your are using the 2003 R2 Release of the Platform SDK the command line looks like that:
"%PROGRAMFILES%\Microsoft Platform SDK for Windows Server 2003 R2\setenv.cmd"

* add the bin subdirectory of the kde installation dir to the PATH environment variable:
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-msvc-build && cd kdeedu-msvc-build

* run cmake
cmake.exe -G "NMake Makefiles" ..\kdeedu-msvc-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
nmake

* install the compiled package
nmake install

== (Re)building packages for the MinGW compiler ==

* download [http://www.winkde.org/pub/kde/ports/win32/installer/kdewin-installer-gui-latest.exe KDE windows installer]

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* choose the '''all''' category and then select the following packages
** the kdeedu bin and source package - this will also select all depending packages
** automoc
** cmake
** gcc-mingw
** perl
** the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-mingw, kdebase-runtime-mingw and qt-mingw are required.

* install the selected packages using the installer. For the gcc-mingw package use \Mingw as installation root.

* add bin subdirectory of the mingw installation dir to the PATH environment variable
set PATH=\Mingw\bin;%PATH%

* add bin subdirectory of the kde installation dir to the PATH environment variable
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root e.g.
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-mingw-build && cd kdeedu-mingw-build

* run cmake
cmake.exe -G "MinGW Makefiles" ..\kdeedu-mingw-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
mingw32-make

* install the compiled package
mingw32-make install

== Make a binary package for the KDE on windows distribution ==

* run the installer in '''Package Manager Mode''' and select '''kdewin-installer(-mingw|-msvc) '''

* install the above mentioned packages with <make-tool> install

* run kdewin-packager from kde installation bin dir with the following options:
- name <the name of the package>
- version <the package version e.g. 1.2.3 or 20090312
- type <msvc> or <mingw> depending on the type of used compiler
- root <the install root where the package has been installed into>
- srcroot <the root of the source package tree>
- destdir <the directory where the package will be placed into>

Getting Started/Build/Windows/DistributionBasedBuild

2009-03-16T21:56:46Z

Rhabacker: made installer link more nice

Getting Started/Build/Windows/DistributionBasedBuild

2009-03-16T21:55:24Z

Rhabacker: updated installer link

This page describes (re)building of KDE binary packages using the kdewin distribution.

Applications build in this way will not have debugging support because the packages build in release mode do not have any debug symbols. If you need debug symbols you should use the [[Getting Started/Build/KDE4/Windows/emerge|Windows ''emerge'' tool]]

It is assumed that KDE is installed using the KDEWin gui or console installer in %PROGRAMFILES%\kde and a developer tries to recompile the kdeedu binary package.
It is also assumed that the KDE installation tree is empty or contains only packages for the related compiler.

== (Re)building packages for MS Visual Studio C++ ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/kdewin-installer-gui-latest.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* choose the '''all''' category and select (at least) the following packages
** kdeedu bin and source package - this will also select all depending packages
** automoc
** cmake
** perl
** psdk-msvc
** one of the vcexpress-xx-msvc package
** the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-msvc, kdebase-runtime-msvc and qt-msvc are required.

* install the selected packages using the installer.

* open a Visual Studio command prompt

* set the required environment for the MS Platform SDK e.g. if your are using the 2003 R2 Release of the Platform SDK the command line looks like that:
"%PROGRAMFILES%\Microsoft Platform SDK for Windows Server 2003 R2\setenv.cmd"

* add the bin subdirectory of the kde installation dir to the PATH environment variable:
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-msvc-build && cd kdeedu-msvc-build

* run cmake
cmake.exe -G "NMake Makefiles" ..\kdeedu-msvc-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
nmake

* install the compiled package
nmake install

== (Re)building packages for the MinGW compiler ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* choose the '''all''' category and then select the following packages
** the kdeedu bin and source package - this will also select all depending packages
** automoc
** cmake
** gcc-mingw
** perl
** the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-mingw, kdebase-runtime-mingw and qt-mingw are required.

* install the selected packages using the installer. For the gcc-mingw package use \Mingw as installation root.

* add bin subdirectory of the mingw installation dir to the PATH environment variable
set PATH=\Mingw\bin;%PATH%

* add bin subdirectory of the kde installation dir to the PATH environment variable
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root e.g.
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-mingw-build && cd kdeedu-mingw-build

* run cmake
cmake.exe -G "MinGW Makefiles" ..\kdeedu-mingw-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
mingw32-make

* install the compiled package
mingw32-make install

Talk:Projects/KDE on Windows/Installation

2009-01-15T23:38:32Z

Rhabacker: updated links

Use this page to record your experiences with KDE on Windows.

Before reporting problems with the installer please make sure that you are using the [http://download.cegit.de/kde-windows/installer/kdewin-installer-gui-latest.exe latest installer version] because your problem may already be fixed.

Click the + tab and enter <nowiki>~~~~</nowiki> as the subject to add your experiences. Include both your installer version and the KDE version (from the "installed" column for the kde* package names in the installer, or from the Help > About KDE dialog).

'''Please use only meaningful descriptions (the content will be edited). The software is in early beta now. The installer will receive usability improvements before the final release.'''

== 4.00.80 progress - skierpage (18 February 2008) ==
Amarok installs a phonon package, and sounds play!

Enabling sound in KHangMan doesn't work, when it tries to play .ogg file it crashes. Amarok hangs at 98% CPU trying to play .ogg file. This could be my Windows install of codecs, but .ogg files play fine in WMP, VLC, MPC, etc.

KHelpCenter: Search doesn't return anything (known issue). Top sections such as "Welcome to KDE" and "KDE Users' Manual" don't do anything ({{Bug|158030}}).

Clicking on known filetypes in Dolphin gives <tt>C:/Program Files/KDE/share/applications/kde4/''some app''.desktop' is malformatted.</tt> alert ({{Bug|156442}}). You can't run a .exe from Dolphin, it prompts you to choose an application to open it with ({{Bug|158034}}).

Help > Report Bug still broken.

== A Blog "review" with screenshots - MrCopilot (30 January 2008) ==
See http://mrcopilot.blogspot.com/2008/01/can-kde-save-dying-windows-platform.html , with screenshots and comments on many KDE applications running in MS Windows.

== Version 0.8.5 notes - 75.128.118.56 (26 January 2008)==
Since I am not what you call a Linux guru, I tried initially installing as an end-user. However, that seems to not install certain things, and once you have made that choice, there is no going back - you can't change the installer settings from End User to Developer, and I think that may be why several packages are not being installed (for example, the kruler.exe program is not installed, and is not available to be installed)
: kruler.exe is part of kdegraphics, and as "Status" says, not currently packaged

Another example: When running konquerer.exe, if I type http://www.google.com into the search bar, it complains about the following missing files: konq_aboutpage.dll, libkhtmlpart.dll, and katepart.dll. None of those files were available to install. Perhaps they are available if you say you are a developer, but I had no way to test that because the buttons that select end user or developer are grayed out.
: Works for me, did you set KDEDIR and add the lib directory to your PATH as per "Summary of Steps"?

I do have one request, after you get the problems fixed, please consider adding krusader to the list of supported packages.

== [[User:Skierpage|Skierpage]] 11:33, 18 January 2008 (CET) using 3.97 ==
Here's [[User:Skierpage]]'s experience using kdewin-installer-gui-0.8.4-4.exe to install 3.97 2007-12-31 files
on Windows XP SP2.

=== Continuing ===
* No khelpcenter, so no Help > ''Program'' Handbook
* Help > Report Bug... > Launch Bug Report Wizard still does nothing ({{Bug|156689}} filed)
* <del>Problems trying to save and open files in apps, KDE complains about their mime type.</del> Fixed by new Post-install steps on install page!
* Get Hot New Stuff still has problems trying to run gpg.exe.

::please file bugs at B.K.O. (bugs.kde.org) --[[User:SaroEngels|SaroEngels]] 01:11, 25 January 2008 (CET)

=== File Open Dialog ===
* clicking Network icon <del>crashes </del>({{Bug|156080}} filed, fixed in 4.00.80 it displays ''Local Network'')
* clicking Home icon does nothing ({{Bug|156690}} filed, still true in 4.00.80).
* clicking Root shows '''Custom''' in file path. (still true in 4.00.80).
* DebugView shows several <tt>[5940] class QStringList __thiscall Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const enum Solid::DeviceInterface::Type &) error: "org.freedesktop.DBus.Error.ServiceUnknown" </tt>

=== Specific Apps ===
==== KStars ====
* during startup or Setup Wizard outputs <tt> kstars(5344) class KStarsDateTime __cdecl KStarsDateTime::fromString(const class QString &): "Could not parse Date/Time string: " "" </tt>
* can't view Web pages from Object Details dialog > Links > View Resource. No error, but no activity. Possibly at the same time saw output "[5344] kstars(5344)/kdeui (KNotification) void __thiscall KNotification::slotReceivedIdError(const class QDBusError &): Error while contacting notify daemon "The name org.kde.knotify was not provided by any .service files"
"
:: I know this last error - but I don't know another fix than kill all apps and restart yet. --[[User:SaroEngels|SaroEngels]] 01:10, 25 January 2008 (CET)

== Issues ==

== [[User:Skierpage|Skierpage]] 07:43, 5 November 2007 (CET) on 2007-11-03 ==
Here's [[User:Skierpage]]'s experience partially installing files with
kdewin-installer-gui-0.8.1-2.exe
on Windows XP SP2.

''Some of my problems were caused by the KDE Installer silently failing to install kdebase bin.''

=== General ===
Each app's Help > Handbook fails to start

About the time I tried the handbook the program couldn't find the KDE crash handler drkonqi.exe.

Submit Bug Report fails to load anything when you click [Launch Bug Wizard];
nothing displays in Process Monitor or DebugView.

Okular and KStars crashed just after trying to access ksyscoca and then "launching kbuildsycoca4". I ran kbuildsycoca4 by hand and then both applications got further.

My display got garbled, displaying what looks like a backing store of the current window in the top left. This first happened with kolf.exe, then happened to KDE Installer. Closing every K* app seemed to cure it.

=== Specific apps ===
bovo, kblackbox, kgeography pixeltool, etc. worked fine.

==== Dolphin ====
<del>1. Even after following instructions in kbuildsycoca4 section below, still mime type id not getting picked up. In the information section it "shows type: mime" instead of correct type. Because of the same reason, I think, it shows all the elements with same icon (binary) including directories.</del>
: Fixed in 4.00.80 after running "Post-install steps"

2. If icon is clicked, open with dialog opens and if I choose kate from the list following error box appears "Service 'C:/KDE 4.0/share/applications/kde4/kate.desktop' is malformatted"
: Still happens in 4.00.80

==== KStars ====
Looks '''awesome'''. In the list of cities in setup,
accented characters appear incorrectly as multiple characters,
as if the encoding is off. [http://www.skierpage.com/kde_bugs/kstars_setup_bad_chars.png See screenshot.]

When I clicked [Download extra data], it crashes. In DebugView, last thing it tried to do was open ksycoca and then launch kbuildsycoca4.

After running kbuildsycoca4 and restarting, KStars [Download extra data] created a "Get Hot New Stuff", but that window was obscured by both KStars and its wizard. It had a [Close] button but would not accept input. I was able to [Cancel] the KStars setup window, at which point both the KStars and Get Hot New Stuff windows appeared. There was nothing in Get Hot New Stuff for "KStarsAdd On Installer" (sic -- word layout bug), so I clicked [Close].

Had some problems adding a new location (fumbled original data). Steps to reproduce:
Settings / geographic. Add a new location (Foo, norway). Realize something went wrong, edit latitude (change from say 10 10 10.00 to 11 11 11.00). Click OK. Choose OK to Override data. OK out. Open Setting/geographic again - there are now two Foos with location == original, expected was one, updated location.

==== kbuildsycoca4 ====
<strike>As this seemed to be causing problems, I ran it myself in a command window. It said "kbuildsycoca4 running..." then exited, seemingly OK.</strike>

The problem is another one:
kbuildsycoca4 builds the readonly database ksycoca in C:\Documents and Settings\USER\.kde\ .
That requires update-mime-database to have been successfully run.

So after each installation:
1. kill all processes: kioslave.exe, klauncher.exe, kded4.exe
2. enter kdeenv.bat (or a your cmd with KDEROOT set) run:
cd %KDEROOT%
%KDEROOT%\bin\update-mime-database %KDEROOT%\share\mime
%KDEROOT%\bin\kbuildsycoca4 --noincremental

update-mime-database prints lots of warnings; ignore them.
Only an error that you should rerun it as root, means that you are in the wrong directory. - Change to kderoot and rerun.

kbuildsycoca has a similar issue: if there are still some processes accessing ksycoca it will ask you whether your disk is full. You should kill all processes that are accessing this file (see process explorer from sysinternals.com ) and rerun it.

This stuff is due to be run by the installer or by emerge. I will hopefully fix this in the next few days. Until then this has to be run by hand.
--[[User:SaroEngels|SaroEngels]] 01:08, 25 January 2008 (CET)

==== KColorChooser ====
crashes when you choose "Named Colors" from the list.
(It fails to open several .mo files and .js files,
then tries to read rgb.txt from various X11 directories and obviously it's not there,
and then crashes.)

==== kruler ====
kruler's cursor in North or South orientation shows the vertical arrowhead and line but has black and white garbage on the other half of it where the selection point would be.

==== okular ====
First time it started klauncher.exe process but hung without displaying anything.
I killed the okular process and tried again; second time okular crashed; DebugView indicated it was trying to open ksyscoca, and when that failed it tried to launch ksyscocabuilder.exe:
[4644] okular(4644)/kdecore (KSycoca) bool __thiscall KSycocaPrivate::checkDatabase(class QFlags<enum KSycocaPrivate::BehaviorIfNotFound>): We have no database.... launching kbuildsycoca4
After running kbuildsycoca4 by hand okular appeared OK. When I chose File > Open I got an alert
Windows - No Disk
Exception Processing Message c00000013 Parameters ''hex hex hex''
I clicked [Continue] and got this alert again.
I think each time Windows was spinning up my empty floppy or CD-ROM drive.
Then the file dialog appeared but also an alert
Error - okular
The process for the file protocol died unexpectedly.

Meanwhile DebugView showed
[2916] not able to find 'kio_file' because KDEDIRS environment variable is not set.
[2916] Set KDEDIRS to the KDE installation root dir and restart klauncher to fix this problem.

I clicked Root in the file dialog and okular generated a ton of DebugView output in kdecore (KUrl) and then crashed.

I followed the instructions about setting up KDEDIRS, killed klauncher.exe, restarted Okular. I still got errors about No Disk but no more "file protocol death". Howeer, clicking Root in the file dialog still generates a ton of DebugView output and Okular crashes.

Even when I navigate to a folder with .png images in it, Open a document displays nothing. Even if I choose PNG image, it displays nothing. However, if I enter *.png in the Filter, it displays appropriate files.

However, choosing a png file results in okular displaying
Can not find a plugin that is able to handle the passed document
and then an error alert. Same for selecting a *.bmp.

Weirdly, entering *.jpg in the Filter immediately exits okular, with no errors.
::KBUILDSYCOCA4
::UPDATE_MIME_TYPE_ERROR --[[User:SaroEngels|SaroEngels]] 00:52, 25 January 2008 (CET)

==== ktouch ====
Exits, DebugView shows
[3452] ASSERT failure in class Phonon::PlatformPlugin *__thiscall Phonon::FactoryPrivate::platformPlugin(void): "The plugin 'C:/KDE4/lib/kde4/plugins/phonon_platform/kde.dll' uses incompatible Qt library. (Cannot mix debug and release libraries.)", file D:\kde-msvc\tmp\kdelibs-beta4-3.95.1.20071029\work\kdelibs\phonon\factory.cpp, line 283
: In 4.00.80 displays friendlier alert "Unable to use the '''Fake''' Multimedia Backend: The shared library was not found."

==== kbruch ====
The accelerator [Alt+e] for [Next Task] does not work.

==== KDE World Clock ====
<del>Is pitch dark. The tooltip shows current city and add flag works. DebugView shows:
[4524] QImage::scaled: Image is a null image
[4524] QPainter::begin: Paint device returned engine == 0, type: 3
[4524] QPainter::setCompositionMode: Painter not active
[4524] QPainter::begin: Paint device returned engine == 0, type: 2

Its context menu has Map Theme > Surface Depth / Flat World / Surface Depth / Flat World , i.e. two entries repeated. Whatever you choose is checked twice.

I can't uncheck Show Daylight, Show Cities, Show Flags in the context menu, they remain checked.</del>
: All fixed in 4.00.80 version!

==== kteatime ====
It does display a fabulous notification bubble from the system tray when the tea is ready! Howeer, DebugView indicates "error while contacting knotify server" (I had configured KTeaTime to Play a sound, Show a message in a popup and Mark taskbar entry) :
[6052] kteatime(6052)/kdeui (KNotification) unsigned int __thiscall KNotificationManager::notify(class KNotification *,const class QPixmap &,const class QStringList &,const class QList<struct QPair<class QString,class QString> > &,const class QString &): error while contacting knotify server

==== khangman ====
It put up a dialog towards the back about progress, but unlike earlier app, that completed and it then worked great. I chose to, roughly. get words in a new language, chose France from the dialog/ Get Hot New Stuff showed up and worked but displayed an alert:
Error - KHangMan
Cannot start ''gpg'' and retrieve the available keys. Make sure that ''gpg'' is installed, otherwise verification of the downloaded resources will be impossible.

I installed gpgme and reran khangman, but now Get Hot New Stuff, did not display any categories.

I changed settings to play sounds and it immediately crashed with
[6072] ASSERT failure in class Phonon::PlatformPlugin *__thiscall Phonon::FactoryPrivate::platformPlugin(void): "The plugin 'C:/KDE4/lib/kde4/plugins/phonon_platform/kde.dll' uses incompatible Qt library. (Cannot mix debug and release libraries.)", file D:\kde-msvc\tmp\kdelibs-beta4-3.95.1.20071029\work\kdelibs\phonon\factory.cpp, line 283

I got around this crash by editing khangmanrc to disable audio.
Still nothing in Get Hot New Stuff.

==== Kig ====
It worked pretty well, I was able to save a .kig file.
It kept prompting
Format not supported - Kig
Kig does not support saving to any other format than its own.
[Save Kig Format] [Cancel]
but if I choose "Save Kig Format" I get the alert again.
Only cancel worked to save the file.

However, when I tried to open that file, the Open dialog displayed its type as "plain text document", opening it led to a "Format Not Supported" alert. DebugView showed:
[5432] kig(5432)/kdecore (KUrl) __thiscall KUrl::KUrl(const class KUrl &): KUrl::KUrl(KUrl) path "" toLocalFile ""
[5432] kig(5432) bool __thiscall KigPart::openFile(void): mimetype: "text/plain"

So there are problems with mime type handling.
(It's scary that mime problems will stop a program from editing a file, how do I force it?)

::UPDATE_MIME_TYPE_ERROR --[[User:SaroEngels|SaroEngels]] 00:50, 25 January 2008 (CET)
:: Yup, fixed now with your "Post-install steps", thanks!

==== KWordQuiz ====
I was able to download French vocabulary, but when I dismissed it, I got the same alert as KHangMan once displayed
Cannot start gpg and retrieve the available keys. Make sure that gpg is installed.

kdelibs/knewstuff/knewstuff2/core/security.cpp is trying to start gpg in a new KProcess. I don't have `gpg` in my path, I'm not sure what package it's in.

::PLEASE ASSIGN TO B.K.O --[[User:SaroEngels|SaroEngels]] 00:49, 25 January 2008 (CET)

==== KGoldRunner ====
The background appears but none of the tiles, and the icons for them in Create New Game are missing. So some directory is missing, could be <tt>C:\KDE4\share\pixmaps</tt> NAME NOT FOUND, I don't know where the tiles should be.

[[Category: MS Windows]]

::PLEASE ASSIGN TO B.K.O --[[User:SaroEngels|SaroEngels]] 00:48, 25 January 2008 (CET)

==== KMail ====
kdepimlibs-msvc-4.1.0, kdepim-msvc-4.0.83-1
KMail won't start because of missing dlls:

gpgme-qt.dll not found

libgpg-error-0.dll not found

my solution: download gpgme-*bin.zip and gpgme-*lib.zip from the kde-repository (directory win32libs) and unzip into your KDE Folder. Installer does not seem to realize this dependency

sqlite3.dll not found

my workaround: sqlite3.dll is not available in the kde repository. Download the current sqlitedll-3*.zip from http://www.sqlite.org/download.html and unzip into your path (I unzipped into kde/bin).

KMail now started.

== installation ==
I tried the installer, but found it very inconvenient. It is very slow in downloading, does not support broken download, had no resume support etc... An option be given to download the required packages through torrent / download express etc. and then run the Installer from downloaded directory. An ISO image to download entire package may also be good idea. What about Localized KDE? I could not found that option either.

== bug reports ==
After several minutes trying to find an adress to submit bug reports for kde on windows I report here that I have given up! This site is the only one I found to tell anyone about the problems.

Please post a link to a forum/bugreport engine or some email address.

::Please try to help copy the bugs to http://bugs.kde.org. Try to set Platform MS Windows. Please have a look after ''your'' bugs. -- [[User:SaroEngels|SaroEngels]] 00:46, 25 January 2008 (CET)

== Download needed packages ==

== Unnecessarities in packages? ==

Some things I noticed:
* A lot of packages come with both release and debug binaries. The latter one are completely useless, at least to end users. It may be more sensible to separate debug binaries into their own packages.

rhabacker: where do you have seen this ? the qt bin package for example only contain end user applications and libraries. Debug libraries are located in the lib packages which are only installed in developer mode.

* There seem to be mingw+msvc versions even for seemingly C libraries, e.g. dbus. Such libraries are usually easily exchangeable between compilers (e.g. an MSVC compiled library with a C interface usually works w/ MinGW without problems). Perhaps this is an opportunity to remove some unnecessary packages?

chehrlic: All is fine here, we need it the way it is. We also know how to use mingw libs with msvc and vice versa but it only works under specific circumstances which are not met here.

::::FIXLATER - [[User:SaroEngels|SaroEngels]] 00:41, 25 January 2008 (CET)
::::No change here - [[User:chehrlic|chehrlic]] 07:04, 25 January 2008 (CET)

== Wishes ==
Everything's workin' perfect. But am i able to fully transform windows desktop environment into KDE ?
:[[User:Jstaniek|jstaniek]] 18:31, 30 January 2008 (CET) - short answer is NO. Not in the default setup, I guess. The transformation would break many native apps. Even if that can be fixed (really?), most users would still consider any such a full transformation as a breakage of the OS. What to do? '''As you apparently ask about replacing every part of Windows with KDE equivalents, just install Linux, BSD, etc. and and get all that immediately and natively'''.

Will kdegraphics be included in the next release?
Will the next release be built from 4.0.1 or 4.0.60 sources(from Dirk Mueller's snapshots)?

== First attempt at using ANY KDE installer for windows... - 212.32.82.218 ( 9 February 2008) ==

Guys - it's interesting that i'm in the position of needing to use KDE. I would use Linux in some form without ever going near Windows.

However, I need to provide support for many customers who need Windows and so am stuck with it.

So here we are, I want to get the features of some KDE and then I notice this site.

All goes well... used the [http://www.winkde.org/pub/kde/ports/win32/installer/kdewin-installer-gui-latest.exe latest installer].

It goes well, and the installer stops.

The next instructions are to add Path references. Did that.

Then it is time for the fun...

bin\update-mime-database C:\KDE4\share\mime is the command to run next...

I've restarted so I expect it to do something specific. Nothing... then an error message.

Also, tried different options during the install process but got no further...

"Update-mime-database - Unable to Locate Component"
"This application has failed to start because libintl3.dll was not found. Re-installing the application may fix this problem."

I have no idea where to go, i've removed and reinstalled and get the same effect. I'm clearly being thick so will continue to search for the answer myself but any pointers would be lovely.

Cheers all.

rhabacker: This looks like a dependency problem - which requires to know which mirror you are using - without this information we cannot help.

dkintheuk: OK I posted the link i used in the body of this post. http://www.winkde.org/pub/kde/ports/win32/installer/kdewin-installer-gui-latest.exe I'm not sure what you mean by a dependancy problem - what do i look for and how do i determine what you guys need to know to help? Thanks for getting back to me though i do appreciate it.

dkintheuk: ok it's alive - used the next installer and it indicated that several components were not installed even though the previous installer said they were. I have amarok running right now and tried out some interesting things but can't get one thing to work...

I can't get bin\update-mime-database C:\KDE4\share\mime to work at all - it tells me that it doesn have permissions - yet it most definitely does... tested and tested and tested - permissions are properly set.

Ah well - happy bunny here - this is really fun.

== Someone somewhere wants to uninstall... ==
<nowiki> I want to know how to uninstall it. Thanks </nowiki>
: (Please sign your edits with <nowiki>~~~~</nowiki>!) I'm guessing something like:
:* In TaskMgr.exe processes, shut down kded4, dbus-daemon, klauncher, etc.
:* Run kdewin-installer, click each installed package until it shows a garbage can, then complete the installer
:* Remove lib directory from %PATH% and the KDEDIRS environment variable (see [[{{PAGENAME}}#Summary_of_Steps]]
:* clean up your Download Path of all the downloaded packages, and delete your install directory.
: -- [[User:Skierpage|Skierpage]] 23:00, 26 February 2008 (CET)

== [[Special:Contributions/218.214.47.219|218.214.47.219]] 08:35, 3 April 2008 (CEST) KDE 4.00.61 / Amarok ==

Installer: kdewin-installer-gui-0.9.1-1.exe
Amarok: 20080211
Everything else: 4.0.61

Amarok is not playing any sound, the position adjustment bar is also disabled. Tried reinstalling to no avail.

== [[Special:Contributions/85.180.249.201|85.180.249.201]] 12:10, 28 May 2008 (CEST) ==

kdewin-installer-gui-0.9.2
KDE 4.0.80

Right click in Konqueror is broken. Shift-deleting files in the file Manager is really really slow, and the software will hang for some seconds.

Another thing: KDE should write its settings to %APPDATA% not just in the Userfolder.

== kdewin-installer-gui-0.9.2.exe ==

I have an empty "download server" textearea (or only the last url I added).

I add urls but always I have empty "package selection" textarea.
Any idea? I'm on XP pro SP2.

Thx, -- [[Special:Contributions/80.156.46.53|80.156.46.53]] 16:35, 10 June 2008 (CEST)

== instalando KOffice en Vista ==

Bajé el kdewin-installer-gui-0.9.2.exe.
Lo ejecuté, solicitó varias cosas: End User, y los paquetes, escogi Spanish, arrancó, dió la ventana de finalización, donde manifiesta que los programas están en el folder BIN, pero resulta que no existe ese folder.
¿qué pasó aquí?

== [[Special:Contributions/118.160.84.128|118.160.84.128]] 07:08, 3 July 2008 (CEST) ==

great concept! some apps don't work because of missing .dlls but the main reason that i wanted KDE is because my new notebook forces me to use Vista (hard to come back to windows after a few years of only linux), and Kmail is not being packaged! i also love Akgregator, and it suffers the same fate. please package Kmail at least! that would make it easier for me to migrate back to linux after the M70S becomes supported in linux.

thanks
Michael J. Klein

== Phonon dlls for multiple backends [[Special:Contributions/116.12.230.41|116.12.230.41]] 14:15, 4 August 2008 (CEST) ==
When I installed Amarok, no sound came out. Apparently, the phonon_backend folder was empty. You can find the dll to populate this folder by installing quarkplayer [http://code.google.com/p/phonon-vlc-mplayer/ here]

Version 4.1.00 (KDE 4.1.0), Installer: 0.9.2
-- Akhmad Fathonih

== [[User:Glen.Ansley|Glen.Ansley]] 22:59, 10 November 2008 (UTC) ==

The main reason for using this was for Amorak.

I am using KDE 4.1.3 and Amorak 1.94.

I had to edit .kde\share\config\kioslaverc and add the following lines to get traffic going through my proxy, as the normal tool (kcmshell4 proxy) wouldn't work!

[Proxy Settings]
ProxyType=1
ftpProxy=http://proxy.domainhere.com:8000
httpProxy=http://proxy.domainhere.com:8000
httpsProxy=http://proxy.domainhere.com:8000
NoProxyFor=localhost

Obviously proxy.domainhere.com:8000 is the actual name and port of "your" proxy if you wish to use one!

All in all. Things seem to be ticking along nicely.
Maybe this information would be nice to add to the "Fine-Tuning" section on
http://techbase.kde.org/Projects/KDE_on_Windows/Installation#Fine-tuning ?

== Where is KOffice 2? ==
Hoping to try out Krita, I learned that it's available as part of KOffice, and that KOffice 2 (presumably still beta) is available through the KDE installer.
Except that it isn't: not in KDE 4.1.3, not in 4.1.2, not in 4.1.1. There is a "UNSTABLE 1.9.95.10" version in KDE 4.1.0, but why would I want such an extremely obsolete package? Are there alternative installation approaches?

:1.9.95.10 isn't necessarily obsolete. Since it's beta they probably just haven't versioned it 2.0 yet, as with amarok2 that's on version 1.94. — [[Special:Contributions/83.251.203.70|83.251.203.70]] 11:02, 25 November 2008 (UTC)

Getting Started/Build/Windows/GCC And MinGW

2009-01-15T12:55:43Z

Rhabacker: updated installer location

{{improve|''This page is outdated - please don't use it anymore unless you know exactly what you do. Use [[../emerge|emerge]] instead''}}

{{KDE4}}
{{improve|''This page has been moved out of [http://kdelibs.com/wiki/index.php/Building_KDElibs_4_using_MinGW_with_Qt_4.3 kdelibs.com] wiki page.''}}

= Introduction =

This step-by-step tutorial shows how to get the current kdelibs from the upcoming KDE4 based on Qt4 compiled under Microsoft Windows.

== Basic Tools ==

=== Installing kdewin-installer ===

This is a program that lets you easily install all the requirements for building kdelibs. It also has a list of tools in its list that are helpful and needed, like the mingw compiler suite, subversion clients, debugging tools and so on.

The kdewin-installer is available in a GUI and console-only form from
[http://www.winkde.org/pub/kde/ports/win32/installer/ the kdewin-installer download page].

=== Using kdewin-installer to install the requirements ===

For the GUI version:
If you are running the Installer for the first time, you should have a look in the Settings page (click on the button 'Settings'). You can select another installation directory if you want. I suggest to choose one that has no spaces in it for now, as it seems some parts of the kde4 buildsystem have problems with that. Choose the compiler you use and accept the Settings.

You'll see a tree of all available packages on the right side. In that tree select kdesupport-mingw and win32libs in the ''all'' category under the dependecies subtree. This should select all packages that are needed to build kdelibs.

Additionally you might want to select the MinGW, cmake, TortoiseSVN, mingw-utils and zip package from the ''tools'' category if you haven't already installed those.

After clicking on 'Finish' the installer will download and install the packages. For mingw, cmake and tortoise it only downloads and starts an installer executable so expect more installation dialogs from those.

=== The Compiler ===
MinGW (Minimalist GNU for Windows) contains the GNU Compiler Collection (gcc) for MS Windows. You can either download it directly from [http://switch.dl.sourceforge.net/sourceforge/mingw/MinGW-5.1.3.exe here] or you select the package in the installer.

=== CMake ===
[http://www.cmake.org CMake] is the make tool used by KDE.
* if you did not get it with the installer, use the most recent binaries from here [http://www.cmake.org/files/v2.4/ http://www.cmake.org/files/v2.4/] (the filename should be like <tt>cmake-2.4.?-win32-x86.zip</tt>; you can also pick an .exe file instead of .zip). Make sure you use at least cmake 2.4.5
* or get CMake from [http://cmake.org/HTML/Download.html#cvs CVS] and compile it yourself.

Install cmake in a path without spaces to avoid troubles (at least under win2k).

== Compile and Install additional libraries ==
These libraries have to be installed:

=== D-Bus for Windows ===
This library shouldn't be installed with the installer, you should rather [[Getting_Started/Build/KDE4/Windows/Building DBus|compile]] it yourself.

=== Qt 4 ===
This Framework can be downloaded with the installer, or you can [[Getting_Started/Build/KDE4/Windows/Building Qt 4|build it on your own]].

=== KDESupport Libraries ===
There are several libraries which will be required for building kdelibs. [[Getting Started/Build/KDE4/Windows/Building KDESupport Libraries|You may want to compile them yourself]] or simply download them using the KDEWin-Installer. You will need:
*kdewin32
*strigi
*soprano
*qca2

== Build kdelibs ==
=== Setting up the user's environment ===

The next step is setting up a proper environment to build KDE4 applications. This includes setting the PATH variable and some additional variables needed for CMake and running KDE applications.

The path C:\kde4\win32libs is used as the installation directory for the kdewin-installer. Obviously you have to change the actual values to suit your system. The Sources from SVN reside in C:\kde4\kdelibs-src.

Create a file environment.bat and add the following lines:<pre>
@set SOURCE_PATH=C:\kde4\kdelibs-src
@set INSTALL_PATH=C:\kde4

@set DBUSDIR=%INSTALL_PATH%
@set KDEDIRS=%INSTALL_PATH%
@set KDEWIN_DIR=%INSTALL_PATH%
@set PATH=%INSTALL_PATH%\bin;%INSTALL_PATH%\lib;%PATH%
@set QT_PLUGIN_PATH=%INSTALL_PATH%\lib\kde4\plugins;%INSTALL_PATH%\plugins
@set STRIGI_HOME=%INSTALL_PATH%
@set XDG_DATA_DIRS=%INSTALL_PATH%\share
</pre>

You will have to run this file every time you start a new cmd-shell. If you don't want to run this file you can make the variable entries permanent:
Open up the Control Panel and select the System entry (or press Win+Break). Then go to the Advanced tab and select Environment Variables. In the section titled 'User variables' add the above entries.
You should have cmake and mingw32-make etc. in your path as well.

=== Building kdelibs from svn ===

Now that all requirements are installed and the environment variables are set you can checkout the kdelibs module from <pre>svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs</pre> into the dedicated source directory.

Afterwards create a new subdirectory inside the kdelibs source directory named '''build'''. Then open a command console, select Start->Run Command and type '''cmd''' into the field. Then navigate to the just created build directory.

The next step is running CMake. For an easy start just run (Using the installation directory that was set in the environment variables section):
<pre>
cmake -G "MinGW Makefiles" .. -DCMAKE_INSTALL_PREFIX=%INSTALL_PATH%\
-DCMAKE_INCLUDE_PATH=%INSTALL_PATH%\include
-DCMAKE_LIBRARY_PATH=%INSTALL_PATH%\lib
</pre>
This command should appear in just one line. Make sure that the paths contain no trailing "\".

You can set other CMake variables in the same way, also interesting might be to create a debug build. This can be achieved by adding -DCMAKE_BUILD_TYPE=Debug.

Now you can let MinGW build and install the module by issuing <pre>
mingw32-make
mingw32-make install
</pre>

This will take some time.

=== Building KDE4 applications ===
The process for building other modules that contain applications that are of interest for you is the same as the process you've just done for kdelibs. There might be additional requirements for some KDE4 modules that you have to build first, in particular kdebase might be required (which in turn requires kdepimlibs).

=== Running KDE4 applications ===
This can be done from the same command window where you've built KDE4. Just type the application name and hit enter. This should automatically start all kde4 daemons and dbus which are required to run for kde4 applications.

For example after building and installing both '''kdevplatform''' and '''kdevelop''' module the KDevelop4 IDE can be started by executing <tt>kdevelop</tt>.
If you get some errors about missing DLLs, make sure that all DLLs are set up in your PATH variable.
You can add the path either by changing the environment variables over the control panel (be sure to restart cmd.exe!) or by entering (if C:\example\path\to\dll\lib is the location of the dll):
<pre>
C:\>set PATH=C:\example\path\to\dll\lib;%PATH%
</pre>

=== Troubles ===
If you experience any troubles with the build process feel free to join #kde-windows on irc.freenode.org.

==Useful links==

List of libraries that are needed to build kde4 on windows (they should be installed by the kde-installer)

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries|3rd-party libraries required for KDElibs 4]].

[[Category:MS Windows]]

Projects/KDE on Windows/FAQ

2009-01-09T08:16:49Z

Rhabacker: updated

__TOC__

* How to replace windows explorer as shell ?
Download and run autorun from http://technet.microsoft.com/de-de/sysinternals/bb963902.aspx - enter the tab 'Logon' and replace the value of HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell with the dolphin path - but - be aware that explorer provides almost everything in the system settings area and other stuff.

Projects/KDE on Windows/FAQ

2009-01-09T08:08:26Z

Rhabacker: /* General */

==General==
* [[How to replace windows explorer as shell]] ?
download and run autorun from http://technet.microsoft.com/de-de/sysinternals/bb963902.aspx - enter the tab 'Logon' and replace the value of HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell with the dolphin path - but - be aware that explorer provides almost everything in the system settings area and other stuff.

Projects/KDE on Windows

2009-01-09T07:57:03Z

Rhabacker: update text

"''KDE 4 libraries and applications are available to you, no matter if you are a commercial developer, manager or free software hacker. You are invited to not only just use the toolkit - you can contribute your own solutions and improvements to the KDE community.''"[[Image:Konqi-win.png|frame|right|Konqi, the KDE mascot now also supporting MS Windows]]

__NOTOC__
==Overview==
*[[/Presentations|Presentations]]
*[[/How to Help|How to Help / Join]]
*[http://windows.kde.org windows.kde.org]
*[[/Maintainers|Maintainers]] of Windows version of particular module or application
*[[/FAQ|Frequently answered questions]]

==Development==
*[[Getting_Started/Build/KDE4/Windows|Build KDE 4 on Windows]] either using cmake (without automatic dependency handling) or using ''emerge''
*[[/Installation|Install KDE 4 on Windows]] using the KDE Installer for Windows
*[[Development/Tutorials/Debugging/Debugging_on_MS_Windows|Debugging on MS Windows]]
*TechBase pages related to MS Windows ports of KDE applications and libraries:
**[[/Missing features of kdelibs|Missing features of kdelibs]]
**[[Projects/PIM/MS_Windows|KDE PIM on MS Windows]]
**[[Projects/Digikam/MS_Windows|Digikam on MS Windows]]
*[[/Issues|Issues]]
**[[/Issues/emerge|Issues, thoughts and jobs for emerge]]
**[[/Issues/kdewin-installer|Issues and thoughts for KDEWin-Installer]]
**[[/Issues/MSVC|Using MSVC compiler, debugger and editor]]
*[[/Tools|Tools]] (required or useful)
*[[/Porting Guidelines|Porting Guidelines]]
*[[/Meetings|Meetings]]
*[[/TODOs|TODOs]]

==Resources==
*[mailto:kde-windows@kde.org kde-windows@kde.org] mailing list: [https://mail.kde.org/mailman/listinfo/kde-windows subscribe], [http://lists.kde.org/?l=kde-windows&r=1&w=2 archives]
*[irc://irc.freenode.net/kde-windows #kde-windows] channel on irc.freenode.net
*Source code in the KDE Subversion: [http://websvn.kde.org/trunk/kdesupport/kdewin32/ kdewin32]

==External Resources==
*Related blogs: [http://chehrlic.blogspot.com chehrlic], [http://saroengels.blogspot.com/ saroengels], [http://www.kdedevelopers.org/blog/104 jstaniek]
*[[/In the Press|KDE on Windows in the press]]
*[http://doc.trolltech.com/4.3/deployment-windows.html Deploying an Application on Qt/Windows] (trolltech.com)
*http://kdelibs.com (former KDElibs/windows site, now outdated, aimed at ISVs)

[[Category:MS Windows]]

Projects/KDE on Windows

2009-01-09T07:55:46Z

Rhabacker: added faq

"''KDE 4 libraries and applications are available to you, no matter if you are a commercial developer, manager or free software hacker. You are invited to not only just use the toolkit - you can contribute your own solutions and improvements to the KDE community.''"[[Image:Konqi-win.png|frame|right|Konqi, the KDE mascot now also supporting MS Windows]]

__NOTOC__
==Overview==
*[[/Presentations|Presentations]]
*[[/How to Help|How to Help / Join]]
*[http://windows.kde.org windows.kde.org]
*[[/Maintainers|Maintainers]] of Windows version of particular module or application
*[[/FAQ|FAQ]]

==Development==
*[[Getting_Started/Build/KDE4/Windows|Build KDE 4 on Windows]] either using cmake (without automatic dependency handling) or using ''emerge''
*[[/Installation|Install KDE 4 on Windows]] using the KDE Installer for Windows
*[[Development/Tutorials/Debugging/Debugging_on_MS_Windows|Debugging on MS Windows]]
*TechBase pages related to MS Windows ports of KDE applications and libraries:
**[[/Missing features of kdelibs|Missing features of kdelibs]]
**[[Projects/PIM/MS_Windows|KDE PIM on MS Windows]]
**[[Projects/Digikam/MS_Windows|Digikam on MS Windows]]
*[[/Issues|Issues]]
**[[/Issues/emerge|Issues, thoughts and jobs for emerge]]
**[[/Issues/kdewin-installer|Issues and thoughts for KDEWin-Installer]]
**[[/Issues/MSVC|Using MSVC compiler, debugger and editor]]
*[[/Tools|Tools]] (required or useful)
*[[/Porting Guidelines|Porting Guidelines]]
*[[/Meetings|Meetings]]
*[[/TODOs|TODOs]]

==Resources==
*[mailto:kde-windows@kde.org kde-windows@kde.org] mailing list: [https://mail.kde.org/mailman/listinfo/kde-windows subscribe], [http://lists.kde.org/?l=kde-windows&r=1&w=2 archives]
*[irc://irc.freenode.net/kde-windows #kde-windows] channel on irc.freenode.net
*Source code in the KDE Subversion: [http://websvn.kde.org/trunk/kdesupport/kdewin32/ kdewin32]

==External Resources==
*Related blogs: [http://chehrlic.blogspot.com chehrlic], [http://saroengels.blogspot.com/ saroengels], [http://www.kdedevelopers.org/blog/104 jstaniek]
*[[/In the Press|KDE on Windows in the press]]
*[http://doc.trolltech.com/4.3/deployment-windows.html Deploying an Application on Qt/Windows] (trolltech.com)
*http://kdelibs.com (former KDElibs/windows site, now outdated, aimed at ISVs)

[[Category:MS Windows]]

Projects/KDE on Windows/FAQ

2009-01-09T07:54:32Z

Rhabacker: new page

==General==
* How to replace windows explorer as shell ?
download and run autorun from http://technet.microsoft.com/de-de/sysinternals/bb963902.aspx - enter the tab 'Logon' and replace the value of HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell with the dolphin path - but - be aware that explorer provides almost everything in the system settings area and other stuff.

Projects/KDE on Windows/Issues/kdewin-installer

2009-01-02T04:15:12Z

Rhabacker: command line installer works perfectly

== Issues ==
Issues that should be considered for the KDEWin-Installer:
* currently no issues known

== Wishes ==
*Add a search bar for the packages
*Select All Packages button or Right Click Entry
[[Category:MS Windows]]

Getting Started/Build/Windows/3rd-party libraries

2009-01-01T17:26:45Z

Rhabacker: updated installer link

Here is a list of the 3rd-party libraries:
* aspell
* boost-headers
* bzip2
* expat
* giflib
* gpgme
* iconv
* jasper
* jpeg
* libintl
* libpng
* libxml2
* libxslt
* openslp
* openssl
* pcre
* redland
* tiff
* update-mime-database
* zlib

For mingw only:
* runtime-mingw
* subversion-mingw

There are sometimes mingw and msvc versions, be careful which you choose.

Download all 'bin' and 'lib' packages with [http://www.winkde.org/pub/kde/ports/win32/installer/kdewin-installer-gui-latest.exe kdewin-installer]
for the build process, set <tt>CMAKE_INCLUDE_PATH</tt> and <tt>CMAKE_LIBRARY_PATH</tt> for cmake. The Installer will put all files into the installation directory you can choose on the settings page. CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH should point to the include and lib subdirectories of your installation path respectively.
There are some [[Getting Started/Build/KDE4/Windows/additional libraries|additional libraries]] you have to build yourself to use extended features in some apps.

Getting Started/Build/Windows/DistributionBasedBuild

2008-11-27T22:59:39Z

Rhabacker: list one package in one line

This page describes (re)building of KDE binary packages using the kdewin distribution.

Applications build in this way will not have debugging support because the packages build in release mode do not have any debug symbols. If you need debug symbols you should use the [[Getting Started/Build/KDE4/Windows/emerge|Windows ''emerge'' tool]]

It is assumed that KDE is installed using the KDEWin gui or console installer in %PROGRAMFILES%\kde and a developer tries to recompile the kdeedu binary package.
It is also assumed that the KDE installation tree is empty or contains only packages for the related compiler.

== (Re)building packages for MS Visual Studio C++ ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* choose the '''all''' category and select (at least) the following packages
** kdeedu bin and source package - this will also select all depending packages
** automoc
** cmake
** perl
** psdk-msvc
** one of the vcexpress-xx-msvc package
** the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-msvc, kdebase-runtime-msvc and qt-msvc are required.

* install the selected packages using the installer.

* open a Visual Studio command prompt

* set the required environment for the MS Platform SDK e.g. if your are using the 2003 R2 Release of the Platform SDK the command line looks like that:
"%PROGRAMFILES%\Microsoft Platform SDK for Windows Server 2003 R2\setenv.cmd"

* add the bin subdirectory of the kde installation dir to the PATH environment variable:
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-msvc-build && cd kdeedu-msvc-build

* run cmake
cmake.exe -G "NMake Makefiles" ..\kdeedu-msvc-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
nmake

* install the compiled package
nmake install

== (Re)building packages for the MinGW compiler ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* choose the '''all''' category and then select the following packages
** the kdeedu bin and source package - this will also select all depending packages
** automoc
** cmake
** gcc-mingw
** perl
** the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-mingw, kdebase-runtime-mingw and qt-mingw are required.

* install the selected packages using the installer. For the gcc-mingw package use \Mingw as installation root.

* add bin subdirectory of the mingw installation dir to the PATH environment variable
set PATH=\Mingw\bin;%PATH%

* add bin subdirectory of the kde installation dir to the PATH environment variable
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root e.g.
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-mingw-build && cd kdeedu-mingw-build

* run cmake
cmake.exe -G "MinGW Makefiles" ..\kdeedu-mingw-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
mingw32-make

* install the compiled package
mingw32-make install

Getting Started/Build/Windows/DistributionBasedBuild

2008-11-27T22:58:50Z

Rhabacker: updated package list

This page describes (re)building of KDE binary packages using the kdewin distribution.

Applications build in this way will not have debugging support because the packages build in release mode do not have any debug symbols. If you need debug symbols you should use the [[Getting Started/Build/KDE4/Windows/emerge|Windows ''emerge'' tool]]

It is assumed that KDE is installed using the KDEWin gui or console installer in %PROGRAMFILES%\kde and a developer tries to recompile the kdeedu binary package.
It is also assumed that the KDE installation tree is empty or contains only packages for the related compiler.

== (Re)building packages for MS Visual Studio C++ ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* choose the '''all''' category and select (at least) the following packages
** kdeedu bin and source package - this will also select all depending packages
** automoc
** cmake
** perl
** psdk-msvc
** one of the vcexpress-xx-msvc package
** the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-msvc, kdebase-runtime-msvc and qt-msvc are required.

* install the selected packages using the installer.

* open a Visual Studio command prompt

* set the required environment for the MS Platform SDK e.g. if your are using the 2003 R2 Release of the Platform SDK the command line looks like that:
"%PROGRAMFILES%\Microsoft Platform SDK for Windows Server 2003 R2\setenv.cmd"

* add the bin subdirectory of the kde installation dir to the PATH environment variable:
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-msvc-build && cd kdeedu-msvc-build

* run cmake
cmake.exe -G "NMake Makefiles" ..\kdeedu-msvc-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
nmake

* install the compiled package
nmake install

== (Re)building packages for the MinGW compiler ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* choose the '''all''' category and then select the following packages
** the kdeedu bin and source package - this will also select all depending packages
** automoc, cmake, gcc-mingw and perl package

* then select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-mingw, kdebase-runtime-mingw and qt-mingw are required.

* install the selected packages using the installer. For the gcc-mingw package use \Mingw as installation root.

* add bin subdirectory of the mingw installation dir to the PATH environment variable
set PATH=\Mingw\bin;%PATH%

* add bin subdirectory of the kde installation dir to the PATH environment variable
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root e.g.
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-mingw-build && cd kdeedu-mingw-build

* run cmake
cmake.exe -G "MinGW Makefiles" ..\kdeedu-mingw-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
mingw32-make

* install the compiled package
mingw32-make install

Getting Started/Build/Windows/DistributionBasedBuild

2008-11-27T22:55:51Z

Rhabacker: updated package list

This page describes (re)building of KDE binary packages using the kdewin distribution.

Applications build in this way will not have debugging support because the packages build in release mode do not have any debug symbols. If you need debug symbols you should use the [[Getting Started/Build/KDE4/Windows/emerge|Windows ''emerge'' tool]]

It is assumed that KDE is installed using the KDEWin gui or console installer in %PROGRAMFILES%\kde and a developer tries to recompile the kdeedu binary package.
It is also assumed that the KDE installation tree is empty or contains only packages for the related compiler.

== (Re)building packages for MS Visual Studio C++ ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* from the '''KDE''' category select the kdeedu bin and source package - this will also select all depending packages

* from the '''devel-tools''' category select the cmake, one of vcexpress-xx-msvc and the psdk-msvc package

* from the '''KDE''' category select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-msvc, kdebase-runtime-msvc and qt-msvc are required.

* install the selected packages using the installer.

* open a Visual Studio command prompt

* set the required environment for the MS Platform SDK e.g. if your are using the 2003 R2 Release of the Platform SDK the command line looks like that:
"%PROGRAMFILES%\Microsoft Platform SDK for Windows Server 2003 R2\setenv.cmd"

* add the bin subdirectory of the kde installation dir to the PATH environment variable:
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-msvc-build && cd kdeedu-msvc-build

* run cmake
cmake.exe -G "NMake Makefiles" ..\kdeedu-msvc-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
nmake

* install the compiled package
nmake install

== (Re)building packages for the MinGW compiler ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* choose the '''all''' category and then select the following packages
** the kdeedu bin and source package - this will also select all depending packages
** automoc, cmake, gcc-mingw and perl package

* then select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-mingw, kdebase-runtime-mingw and qt-mingw are required.

* install the selected packages using the installer. For the gcc-mingw package use \Mingw as installation root.

* add bin subdirectory of the mingw installation dir to the PATH environment variable
set PATH=\Mingw\bin;%PATH%

* add bin subdirectory of the kde installation dir to the PATH environment variable
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root e.g.
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-mingw-build && cd kdeedu-mingw-build

* run cmake
cmake.exe -G "MinGW Makefiles" ..\kdeedu-mingw-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
mingw32-make

* install the compiled package
mingw32-make install

Getting Started/Build/Windows/DistributionBasedBuild

2008-11-26T13:41:17Z

Rhabacker: indent fix

This page describes (re)building of KDE binary packages using the kdewin distribution.

Applications build in this way will not have debugging support because the packages build in release mode do not have any debug symbols. If you need debug symbols you should use the [[Getting Started/Build/KDE4/Windows/emerge|Windows ''emerge'' tool]]

It is assumed that KDE is installed using the KDEWin gui or console installer in %PROGRAMFILES%\kde and a developer tries to recompile the kdeedu binary package.
It is also assumed that the KDE installation tree is empty or contains only packages for the related compiler.

== (Re)building packages for MS Visual Studio C++ ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* from the '''KDE''' category select the kdeedu bin and source package - this will also select all depending packages

* from the '''devel-tools''' category select the cmake, one of vcexpress-xx-msvc and the psdk-msvc package

* from the '''KDE''' category select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-msvc, kdebase-runtime-msvc and qt-msvc are required.

* install the selected packages using the installer.

* open a Visual Studio command prompt

* set the required environment for the MS Platform SDK e.g. if your are using the 2003 R2 Release of the Platform SDK the command line looks like that:
"%PROGRAMFILES%\Microsoft Platform SDK for Windows Server 2003 R2\setenv.cmd"

* add the bin subdirectory of the kde installation dir to the PATH environment variable:
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-msvc-build && cd kdeedu-msvc-build

* run cmake
cmake.exe -G "NMake Makefiles" ..\kdeedu-msvc-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
nmake

* install the compiled package
nmake install

== (Re)building packages for the MinGW compiler ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* from the '''KDE''' category select the kdeedu bin and source package - this will also select all depending packages

* from the '''devel-tools''' category select the cmake and gcc-mingw package

* from the '''KDE''' category select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-mingw, kdebase-runtime-mingw and qt-mingw are required.

* install the selected packages using the installer. For the gcc-mingw package use \Mingw as installation root.

* add bin subdirectory of the mingw installation dir to the PATH environment variable
set PATH=\Mingw\bin;%PATH%

* add bin subdirectory of the kde installation dir to the PATH environment variable
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root e.g.
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-mingw-build && cd kdeedu-mingw-build

* run cmake
cmake.exe -G "MinGW Makefiles" ..\kdeedu-mingw-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
mingw32-make

* install the compiled package
mingw32-make install

Getting Started/Build/Windows/DistributionBasedBuild

2008-11-26T13:39:41Z

Rhabacker: mingw instructions

This page describes (re)building of KDE binary packages using the kdewin distribution.

Applications build in this way will not have debugging support because the packages build in release mode do not have any debug symbols. If you need debug symbols you should use the [[Getting Started/Build/KDE4/Windows/emerge|Windows ''emerge'' tool]]

It is assumed that KDE is installed using the KDEWin gui or console installer in %PROGRAMFILES%\kde and a developer tries to recompile the kdeedu binary package.
It is also assumed that the KDE installation tree is empty or contains only packages for the related compiler.

== (Re)building packages for MS Visual Studio C++ ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* from the '''KDE''' category select the kdeedu bin and source package - this will also select all depending packages

* from the '''devel-tools''' category select the cmake, one of vcexpress-xx-msvc and the psdk-msvc package

* from the '''KDE''' category select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-msvc, kdebase-runtime-msvc and qt-msvc are required.

* install the selected packages using the installer.

* open a Visual Studio command prompt

* set the required environment for the MS Platform SDK e.g. if your are using the 2003 R2 Release of the Platform SDK the command line looks like that:
"%PROGRAMFILES%\Microsoft Platform SDK for Windows Server 2003 R2\setenv.cmd"

* add the bin subdirectory of the kde installation dir to the PATH environment variable:
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-msvc-build && cd kdeedu-msvc-build

* run cmake
cmake.exe -G "NMake Makefiles" ..\kdeedu-msvc-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
nmake

* install the compiled package
nmake install

== (Re)building packages for the MinGW compiler ==

* download http://www.winkde.org/pub/kde/ports/win32/installer/unstable/kdewin-installer-gui-0.9.4-rc0.exe

* run the installer in '''Package Manager Mode''' and select '''msvc compiler'''

* from the '''KDE''' category select the kdeedu bin and source package - this will also select all depending packages

* from the '''devel-tools''' category select the cmake and gcc-mingw package

* from the '''KDE''' category select the development packages required for building the requested package. In the Package Manager mode of the gui installer you can see the required package dependencies by clicking on the package name (only first level dependency yet). For the kdeedu package the development package for kdelibs-mingw, kdebase-runtime-mingw and qt-mingw are required.

* install the selected packages using the installer. For the gcc-mingw package use \Mingw as installation root.

* add bin subdirectory of the mingw installation dir to the PATH environment variable
set PATH=\Mingw\bin;%PATH%

* add bin subdirectory of the kde installation dir to the PATH environment variable
set PATH=%PROGRAMFILES%\kde\bin;%PATH%

* enter src subdirectory of the kde installation root e.g.
cd %PROGRAMFILES%\kde\src

* create a build directory and enter it
mkdir kdeedu-mingw-build && cd kdeedu-mingw-build

* run cmake
cmake.exe -G "MinGW Makefiles" ..\kdeedu-mingw-4.1.3 -DCMAKE_INCLUDE_PATH=%PROGRAMFILES%\kde\include -DCMAKE_LIBRARY_PATH=%PROGRAMFILES%\kde\lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=%PROGRAMFILES%\kde

* build
mingw32-make

* install the compiled package
mingw32-make install

Getting Started/Build/Windows/DistributionBasedBuild

2008-11-26T13:31:23Z

Rhabacker: msvc build instructions

Getting Started/Build/Windows/DistributionBasedBuild

2008-11-26T13:23:15Z

Rhabacker: intro

Policies/Kdelibs Coding Style

2008-07-10T11:15:05Z

Rhabacker: added astyle shell scripts

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

'''In short: Kdelibs coding style follows the Qt 4 coding style.'''

== Indentation ==
* No tabs
* 4 Spaces instead of one tab

== Variable declaration ==
* Each variable declaration on a new line
* Each new word in a variable name starts with a capital letter
* Avoid abbreviations
* Take useful names. No short names, except:
** Single character variable names can denote counters and temporary variables whose purpose is obvious
** Variables and functions start with a small letter

Example:
<code cppqt>
// wrong
KProgressBar *prbar;
QString prtxt, errstr;

// correct
KProgressBar *downloadProgressBar;
QString progressText;
QString errorString;
</code>

== Whitespace ==
* Use blank lines to group statements
* Use only one empty line
* Use one space after each keyword
* For pointers or references, use a single space before '*' or '&', but not after
* No space after a cast

Example:
<code cppqt>
// wrong
QString* myString;
if(true){
}

// correct
QString *myString;
if (true) {
}
</code>

== Braces ==
As a base rule, the left curly brace goes on the same line as the start of the statement.

Example:
<code cppqt>
// wrong
if (true)
{
}

// correct
if (true) {
}
</code>

Exception: Function implementations, class, struct and namespace declarations always have the opening brace on the start of a line.

Example:
<code cppqt>
void debug(int i)
{
qDebug("foo: %i", i);
}

class Debug
{
};
</code>

Use curly braces even when the body of a conditional statement contains only one line.

Example:
<code cppqt>
// wrong
if (true)
return true;

for (int i = 0; i < 10; ++i)
qDebug("%i", i);

// correct
if (true) {
return true;
}

for (int i = 0; i < 10; ++i) {
qDebug("%i", i);
}
</code>

== Switch statements ==
Case labels are on the same column as the switch

Example:
<code cppqt>
switch (myEnum) {
case Value1:
doSomething();
break;
case Value2:
doSomethingElse();
// fall through
default:
defaultHandling();
break;
}
</code>

== Line breaks ==
Try to keep lines shorter than 100 characters, inserting line breaks as necessary.

== Artistic Style (astyle) automatic code formatting ==
You can use [http://astyle.sourceforge.net/ astyle] (>=1.19) to format code or to test if you have followed this document. Run the following command:
<code>
astyle --indent=spaces=4 --brackets=linux \
--indent-labels --pad=oper --unpad=paren \
--one-line=keep-statements --convert-tabs \
--indent-preprocessor \
`find -type f -name '*.cpp'` `find -type f -name '*.h'`
</code>
A related shell script could be found for unix in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs kdesdk/scripts/astyle-kdelibs] and for windows in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs.bat kdesdk/scripts/astyle-kdelibs.bat].

== Vim script ==
You can find a vim script in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim kdesdk/scripts/kde-devel-vim.vim] that helps you to keep the coding style correct. In addition to defaulting to the kdelibs coding style it will automatically use the correct style for Solid and kdepim code. If you want to add rules for other projects feel free to add them in the SetCodingStyle function.

To use the script, include it in your {{path|~/.vimrc}} like this:
<code>
source /path/to/kde/sources/kdesdk/scripts/kde-devel-vim.vim
</code>

Document started by Urs Wolfer. Some parts of this document have been adopted from the Qt Coding Style document posted by Zack Rusin on kde-core-devel.

[[Category:Policies]] [[Category:C++]]

Projects/KDE on Windows/Installation (de)

2008-04-11T22:30:37Z

Rhabacker: updated installer link

{{Template:I18n/Language Navigation Bar|Projects/KDE_on_Windows/Installation}}

{{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?]]}}

{{note|Diese Seite ist nochn nicht vollständig ins Deutsche übersetzt. Außerdem kann die Übersetztun noch Fehler enthalten.}}

== KDE Installer für Windows ==
Dieser Installer kann dafür benutzt werden, um verschiedene Binärpakete zu downloaden und zu installieren, die dafür benötigt werden, KDE Programme unter MS Windows auszuführen. KDE ist frei und open source, also kann man alle Programme auch direkt aus dem Quellcode erstellen.
Als Erleichterung für andere haben Freiwillige jedoch diese vorcompilierten Pakete erstellt und im Internet erreichbar gemacht.

'''Disclaimer''' "KDE4 on Windows" ist noch in einem frühen Stadium der Entwicklung. Einige Programme arbeiten besser als andere und einige laufen überhaupt nicht.

'''Fals es Probleme geben sollte, sollte man einen Blick auf die [http://lists.kde.org/?l=kde-windows&r=1&w=2| Mailing Liste] werfen.'''

Der KDE Installer kann auch dazu verwendet werden, Quellcode und die notwendigen Pakete, um KDE4 auf Windows zu ''erstellen'' zu installieren (obwohl Sie das emerge-System bevorzugen könnten um KDE und seine Abhängigkeiten zu installieren, wenn Sie KDE4 auf Windows erstellen möchten); siehe auch [[Getting Started/Build/KDE4/Windows]].

=== Zusammenfassung ===
* http://www.winkde.org/pub/kde/ports/win32/installer/ aufrufen
* Die aktuellste Version Downloaden und speichern, z.B. nach <tt>C:\KDE4</tt>
* Den Installer aufrufen, alles Benötigte downloaden (sihe auch [[#benötigte Pakete herunterladen]] weiter unten).
* Das lib Verzeichnus, z.B. <tt>C:\KDE4\lib</tt> zur %PATH%-Variablen hinzufügen. (Start > Systemsteuerung > System > Erwitert > Umgebungsvariablen,
Doppelklick auf die Path-Systemvariable und das Verzeichnis, mit Semikolon getrennt, hinzufügen.)
* Die KDEDIRS Umgebungsvariable hinzufügen (Start > Systemsteuerung > System > Erwitert > Umgebungsvariablen, auf [Neu] (bei Benutzervariablen) klicken. Als Namen <tt>KDEDIRS</tt> und als Wert das Installationsverzeichnis von KDE4 eingeben (z.B. <tt>C:\KDE4</tt>).
* [TEMPORARILY] Den Instruktionen bei [[#nach der Installation]] folgen
* Versuchen, eine QT-Applikation im <tt>bin</tt> Vezwichniss, wie zum Beispiel linguist.exe auszuführen
* Fals das geht, versuchen KDE Applikationen wie <tt>kwrite.exe</tt> auszuführen.

=== benötigte Pakete herunterladen ===
Ein einzelnes KDE-Programm basiert auf vielen anderen Programmbibliotheken und Paketen; dadurch ist jede .exe relativ klein.
Der KDE-Installer hat zwar eine bedingte Kenntniss dieser Abhäängigkeiten, aber keine Vollständige.
Desshalb könnte es bei den ersten Versuchen, ein Programm auszuführen, Fehlermelungen über fehlende DLLs geben.

Fals Sie nicht vorhaben, KDE aus dem Quelltext heraus aufzubauen, klicken sie weder auf "all" noch auf "src", da sie die Quellcodes nicht benötigen. ''Unclear whether you need lib for each''.

Es gibt zwei Enwicklungssysteme für "KDE on Windows", Microsofts Visual C sowie [http://en.wikipedia.org/wiki/MinGW MinGW].
Auch wenn Sie nur Binärpackete ausführen und nicht vorhaben, KDE4 selbst aufzubauen, müssen sie wegen der bereitgestellten Laufzeitumgebungen, müssen sie ein System wählen. Sie können frei entwscheiden, welches.

Die eigentlichen KDE Programme sind in verschiedenen Gruppen organisiert: kdeedu, kdegames und kdegraphics.

folgende Pakete gehören zu den Minimalvoraussetzungen, um KDE-Applikationen auszuführen:
: dbus-msvc, kdebase-msvc, kdewin32-msvc, qt-msvc, vcredist, ??

Der "Dependencies"-Tab für ein bestimmtes Paket listet einige der zusätzlich benötigten Packete auf.
Jedoch funktioniert das Überprüfen der Abhängigkeiten zuzeit nur für Abhängigkeiten ersten Grades.
Andere Abhängigkeiten sind nicht immer leicht zu bestimmen.
Wenn Sie zu Beispiel kdegames nur mit seinen Abhängigkeiten installieren, werden Sie es nicht ausführen können, das Sie außerdem libstreamanalyze benötigen
(dafür müssen sie das stringi Packet installieren).
rhabacker: This is fixed in installer version > 0.8.4.

Unter [[Getting_Started/Build/KDE4/Windows/3rd-party_libraries]] findet sich eine vollständigere Liste der Abhängigkeiten.

=== Fehler im Installer ===
Falls Sie einen Fehler finden, melden sie ihn bitte an [mailto:kde-windows@kde.org].

==== Successful? completion ====
If something goes wrong during installation, for example a file can't be replaced because it is still in use, the installer may still report successful completion. If you see any alert or failure message from the installer, when it completes quit and re-run it.

==== Dependencies, not detailed version dependencies ====
The installer tracks dependencies on packages,
but not particular ''versions'' of packages.
So in end user install mode, the installer won't alert you to the existence of a newer version of a supporting package, and doesn't know when one of the "high-level" end-user packages requires this newer version.
: As a workaround, if you go into %KDEDIRS%\manifest and delete the .mft and .ver files for a package (e.g. qt-msvc-4.3.3-2-bin.mft, qt-msvc-4.3.3-2-bin.ver, etc.), the installer will see that you've uninstalled a package. Then, should another package require that package the installer will download the most recent one available from the mirror.

== nach der Installation ==
Zurzeit ist es noch notwendig, einige Komandozeilen-Programme auszuführen, um KDE aufzusetzen.

===update-mime-database ausführen===
Stellen Sie sicher, dass keine zu KDE gehörigen Programme laufen: starten sie den Task Manager (taskmgr.exe), gehen sie zum Reiter Prozesse und beenden sie alle Instanzen von dbus-daemon.exe, kded4.exe, kioslave.exe und klauncher.exe (und allen anderen KDE-Applikationen).

Öffnen sie eine Kommandozeile (cmd.exe) und gehen sie zu dem Verzeichnis, in das sie KDE installiert haben. Wenn KDE zum Beispiel in C:\KDE4 lieg, rufen Sie folgende Befehle aus:
C:\KDE4> '''bin\update-mime-database C:\KDE4\share\mime'''
Sie werden eine Menge Warnungen erhalten. Die meisten können Sie ignorieren;
Fals sie angewiesen werden, update-mime-database als root auszuführen, befinden Sie sich nicht im Installationsverzeichnis.

===kbuildsyscoca4 ausführen===
Nachdem Sie den vorherigen Schritt ausgeführt haben, starten Sie
C:\KDE4> '''bin\kbuildsycoca4 --noincremental'''
Fals das Programm sich beschwert, es währe nicht genug Speicherplatz vorhanden (was warscheinlich nicht der Fall ist), haben Sie immer noch einige KDE-Programme laufen. sließen Sie diese und versuchen sie es noch einmal.

Wir entschuldigen uns für die Unannehmlichkeiten — wir hoffen, dass es in den nächsten Versionen eine bessere Lösung gibt.

== Testen der Installation ==
Navigieren Sie ins <tt>bin</tt> Verzeichnis.

Versuchen sie, das Qt Programm assistant.exe auszuführen (QT-Programme haben geringere Anforderungen als KDE Applikationen).

Wenn das funktioniert, versuchen Sie, eine simple KDE-Applikation wie lskat.exe aus dem kdegames Packet auszuführen.

Die erste KDE-Applikation, die Sie starten, wird eine Konsole öffnen, um den [http://en.wikipedia.org/wiki/D-Bus D-Bus daemon] zu starten.

== Feintuning ==
===Set Oxygen style for widgets===
The default KDE widget style on Windows is the native one. You already have Oxygen style installed (which is a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:
#edit <tt>%UserPROFILE%\.kde\share\config\kdeglobals</tt> with any text editor (e.g. kwrite)
#locate line containing "[General]" text, what is a section, if there is no such line, add one
#replace or add <tt>widgetStyle=....</tt> line with <tt>widgetStyle=oxygen</tt>.
Newly started applications should be displayed with Oxygen style now.

== Status ==
Using kdewin-installer-gui-0.8.6.exe to install 4.00.60 packages:
* starting a KDE program correctly starts dbus-daemon.exe
* many games run
* choosing File > Open correctly starts klauncher.exe, kioslave.exe and kded4.exe, and runs kbuildsycoca4.exe as needed.
* Full-text search in khelpcenter does not work because Perl scripts are disabled.
* Many applications have a generic icon in Windows Explorer.
* Applications that try to play sounds might display an alert about "Multimedia Backend" problems. This requires the Windows backend for [http://phonon.kde.org/ Phonon]. The amarok package installs an experimental Windows phonon backend. Amarok plays music!!

General notes:
* There are many other KDE programs that are not part of KDE 4.0.0 and are not currently packaged for Windows, such as KOffice 2.
* By design, KDE-windows does not provide the full-blown KDE desktop, thus no KWin composite manager, KDE-specific "start" menus, Plasma desktop, etc.

=== Package status and contents ===
{| border="0" cellpadding="2"
|-valign="top"
!package
!status
!contains applications
|-valign="top"
|kdebase
|packaged
|Konqueror, Dolphin, KWrite, etc.
|-valign="top"
|kdegames
|packaged
|Kgoldrunner, Kpat, KMahjongg, etc.
|-valign="top"
|kdesdk
|packaged
|Kate, Umbrello, etc.
|-valign="top"
|kdetoys
|packaged
|KTeatime, etc.
|-valign="top"
|kdeedu
|packaged
|Marble, Parley, KStars, KHangman, etc.
|-valign="top"
|kdegraphics
|not packaged
|Okular, kolourpaint, etc.
|-valign="top"
|amarok
|packaged
|Amarok music player
|-valign="top"
|koffice
|not packaged
|KWord, Krita, Karbon, etc.
|-valign="top"
|kdepim
|not building
|KMail, AKregator, etc.
|-valign="top"
|kdenetwork
|not building
|Kopete, KGet, etc.
|-valign="top"
|kdeutils
|not packaged
|KGpg, KWallet, etc.
|}

[[Category: MS Windows]]

Projects/KDE on Windows/Installation

2008-04-11T22:28:26Z

Rhabacker: updated installer link

{{Template:I18n/Language Navigation Bar|Projects/KDE_on_Windows/Installation}}

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

'''If you experience any problems please have a look into our [http://lists.kde.org/?l=kde-windows&r=1&w=2| mailing list].'''

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://www.winkde.org/pub/kde/ports/win32/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|Download needed packages]] below).
* 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>).
* Add your lib directory, <tt>%KDEDIRS\lib</tt>, and your bin directory, <tt>%KDEDIRS\bin</tt>, to your Windows %PATH%. (Start > Control Panel > System > Advanced > Environment Variables, double-click the Path System Variable and add this to your path separated by semicolon.)
* If you don't have Visual Studio 2005 installed, download and install the "Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)" [http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en]
* [TEMPORARILY] Follow the instructions at [[#post-install steps|post-install steps]]
* 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>kwrite.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 because of the provided runtime environments.
You're free to decide which to take.

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, kdebase-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).
rhabacker: This is fixed in installer version > 0.8.4.

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries]] is a more complete list of libraries that a full installation needs.

=== Issues with KDE Installer for Windows ===
If you find an issue, please report to [mailto:kde-windows@kde.org].

==== Successful? completion ====
If something goes wrong during installation, for example a file can't be replaced because it is still in use, the installer may still report successful completion. If you see any alert or failure message from the installer, when it completes quit and re-run it.

== 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 lskat.exe from the kdegames 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].

== Fine-tuning ==
===Set Oxygen style for widgets===
The default KDE widget style on Windows is the native one. You already have Oxygen style installed (which is a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:
#edit <tt>%UserPROFILE%\.kde\share\config\kdeglobals</tt> with any text editor (e.g. kwrite) Note: `cd %UserPROFILE%` will change to the right directory, effectively telling you what %UserPROFILE% expands to, such as "C:\Documents and Settings\mark"
#locate the General section (a line containing the text "[General]"). If there is no General section, create one.
#Within the General section ([General]), edit the line containing <tt>widgetStyle=....</tt> so that it reads <tt>widgetStyle=oxygen</tt>. If there is no such <tt>widgetStyle=...</tt> line, create it.
Newly started applications should be displayed with Oxygen style now.

== Status ==
Using kdewin-installer-gui-0.8.6.exe to install 4.00.60 packages:
* starting a KDE program correctly starts dbus-daemon.exe
* many games run
* choosing File > Open correctly starts klauncher.exe, kioslave.exe and kded4.exe, and runs kbuildsycoca4.exe as needed.
* Full-text search in khelpcenter does not work because Perl scripts are disabled.
* Many applications have a generic icon in Windows Explorer.
* Applications that try to play sounds might display an alert about "Multimedia Backend" problems. This requires the Windows backend for [http://phonon.kde.org/ Phonon]. The amarok package installs an experimental Windows phonon backend. Amarok plays music!!

General notes:
* There are many other KDE programs that are not part of KDE 4.0.0 and are not currently packaged for Windows, such as KOffice 2.
* By design, KDE-windows does not provide the full-blown KDE desktop, thus no KWin composite manager, KDE-specific "start" menus, Plasma desktop, etc.

=== Package status and contents ===
{| border="0" cellpadding="2"
|-valign="top"
!package
!status
!contains applications
|-valign="top"
|kdebase
|packaged
|Konqueror, Dolphin, KWrite, etc.
|-valign="top"
|kdegames
|packaged
|Kgoldrunner, Kpat, KMahjongg, etc.
|-valign="top"
|kdesdk
|packaged
|Kate, Umbrello, etc.
|-valign="top"
|kdetoys
|packaged
|KTeatime, etc.
|-valign="top"
|kdeedu
|packaged
|Marble, Parley, KStars, KHangman, etc.
|-valign="top"
|kdegraphics
|packaged
|Okular, kolourpaint, etc.
|-valign="top"
|amarok
|packaged
|Amarok music player
|-valign="top"
|koffice
|not packaged
|KWord, Krita, Karbon, etc.
|-valign="top"
|kdepim
|not building
|KMail, AKregator, etc.
|-valign="top"
|kdenetwork
|not building
|Kopete, KGet, etc.
|-valign="top"
|kdeutils
|not packaged
|KGpg, KWallet, etc.
|}

== Deprecated: post-install steps ==
After manual installation of a package one has to run the included post-install.bat script (inside the manifest folder). This batch file includes at least the following steps.

===Run update-mime-database===
Be sure that you have no KDE-related applications running: run the Windows Task Manager (taskmgr.exe), switch to its Processes tab, and kill all occurences of dbus-daemon.exe, kded4.exe, kioslave.exe and klauncher.exe (and all other KDE apps).

Open a Windows command prompt (cmd.exe) and navigate to the directory where you installed KDE. Say you installed KDE to C:\KDE4, then run from the cmd.exe window:
C:\KDE4> '''bin\update-mime-database C:\KDE4\share\mime'''
This will give you a lot of warning message. Most of them you can easily ignore; even if you should set [[KDE_System_Administration/Environment_Variables#XDG_DATA_HOME|XDG_DATA_HOME]] or [[KDE_System_Administration/Environment_Variables#XDG_DATA_DIRS|XDG_DATA_DIRS]] it worked perfectly. If it says you should rerun update-mime-database as root then you're not within your installation directory.

===Run kbuildsyscoca4===
After finishing the previous step, run
C:\KDE4> '''bin\kbuildsycoca4 --noincremental'''
If this tells you that your disk is full (which is most probably not the case) you have still some executables from KDE running. Please close them and try again.

Excuse us for the inconvenience — we hope for a better solution in the next release.

[[Category: MS Windows]]

Projects/KDE on Windows/Installation

2008-03-25T15:10:32Z

Rhabacker: Dependencies, not detailed version dependencies-> this is fixed in 0.9.1

{{Template:I18n/Language Navigation Bar|Projects/KDE_on_Windows/Installation}}

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

'''If you experience any problems please have a look into our [http://lists.kde.org/?l=kde-windows&r=1&w=2| mailing list].'''

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|Download needed packages]] below).
* 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>).
* Add your lib directory, <tt>%KDEDIRS\lib</tt>, and your bin directory, <tt>%KDEDIRS\bin</tt>, to your Windows %PATH%. (Start > Control Panel > System > Advanced > Environment Variables, double-click the Path System Variable and add this to your path separated by semicolon.)
* If you don't have Visual Studio 2005 installed, download and install the "Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)" [http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en]
* [TEMPORARILY] Follow the instructions at [[#post-install steps|post-install steps]]
* 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>kwrite.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 because of the provided runtime environments.
You're free to decide which to take.

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, kdebase-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).
rhabacker: This is fixed in installer version > 0.8.4.

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries]] is a more complete list of libraries that a full installation needs.

=== Issues with KDE Installer for Windows ===
If you find an issue, please report to [mailto:kde-windows@kde.org].

==== Successful? completion ====
If something goes wrong during installation, for example a file can't be replaced because it is still in use, the installer may still report successful completion. If you see any alert or failure message from the installer, when it completes quit and re-run it.

== post-install steps ==
You currently need to run a number of command-line programs to set up KDE. Here are the steps.

===Run update-mime-database===
Be sure that you have no KDE-related applications running: run the Windows Task Manager (taskmgr.exe), switch to its Processes tab, and kill all occurences of dbus-daemon.exe, kded4.exe, kioslave.exe and klauncher.exe (and all other KDE apps).

Open a Windows command prompt (cmd.exe) and navigate to the directory where you installed KDE. Say you installed KDE to C:\KDE4, then run from the cmd.exe window:
C:\KDE4> '''bin\update-mime-database C:\KDE4\share\mime'''
This will give you a lot of warning message. Most of them you can easily ignore; even if you should set [[KDE_System_Administration/Environment_Variables#XDG_DATA_HOME|XDG_DATA_HOME]] or [[KDE_System_Administration/Environment_Variables#XDG_DATA_DIRS|XDG_DATA_DIRS]] it worked perfectly. If it says you should rerun update-mime-database as root then you're not within your installation directory.

===Run kbuildsyscoca4===
After finishing the previous step, run
C:\KDE4> '''bin\kbuildsycoca4 --noincremental'''
If this tells you that your disk is full (which is most probably not the case) you have still some executables from KDE running. Please close them and try again.

Excuse us for the inconvenience — we hope for a better solution in the next release.

== 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 lskat.exe from the kdegames 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].

== Fine-tuning ==
===Set Oxygen style for widgets===
The default KDE widget style on Windows is the native one. You already have Oxygen style installed (which is a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:
#edit <tt>%UserPROFILE%\.kde\share\config\kdeglobals</tt> with any text editor (e.g. kwrite) Note: `cd %UserPROFILE%` will change to the right directory, effectively telling you what %UserPROFILE% expands to, such as "C:\Documents and Settings\mark"
#locate the General section (a line containing the text "[General]"). If there is no General section, create one.
#Within the General section ([General]), edit the line containing <tt>widgetStyle=....</tt> so that it reads <tt>widgetStyle=oxygen</tt>. If there is no such <tt>widgetStyle=...</tt> line, create it.
Newly started applications should be displayed with Oxygen style now.

== Status ==
Using kdewin-installer-gui-0.8.6.exe to install 4.00.60 packages:
* starting a KDE program correctly starts dbus-daemon.exe
* many games run
* choosing File > Open correctly starts klauncher.exe, kioslave.exe and kded4.exe, and runs kbuildsycoca4.exe as needed.
* Full-text search in khelpcenter does not work because Perl scripts are disabled.
* Many applications have a generic icon in Windows Explorer.
* Applications that try to play sounds might display an alert about "Multimedia Backend" problems. This requires the Windows backend for [http://phonon.kde.org/ Phonon]. The amarok package installs an experimental Windows phonon backend. Amarok plays music!!

General notes:
* There are many other KDE programs that are not part of KDE 4.0.0 and are not currently packaged for Windows, such as KOffice 2.
* By design, KDE-windows does not provide the full-blown KDE desktop, thus no KWin composite manager, KDE-specific "start" menus, Plasma desktop, etc.

=== Package status and contents ===
{| border="0" cellpadding="2"
|-valign="top"
!package
!status
!contains applications
|-valign="top"
|kdebase
|packaged
|Konqueror, Dolphin, KWrite, etc.
|-valign="top"
|kdegames
|packaged
|Kgoldrunner, Kpat, KMahjongg, etc.
|-valign="top"
|kdesdk
|packaged
|Kate, Umbrello, etc.
|-valign="top"
|kdetoys
|packaged
|KTeatime, etc.
|-valign="top"
|kdeedu
|packaged
|Marble, Parley, KStars, KHangman, etc.
|-valign="top"
|kdegraphics
|not packaged
|Okular, kolourpaint, etc.
|-valign="top"
|amarok
|packaged
|Amarok music player
|-valign="top"
|koffice
|not packaged
|KWord, Krita, Karbon, etc.
|-valign="top"
|kdepim
|not building
|KMail, AKregator, etc.
|-valign="top"
|kdenetwork
|not building
|Kopete, KGet, etc.
|-valign="top"
|kdeutils
|not packaged
|KGpg, KWallet, etc.
|}

[[Category: MS Windows]]

Projects/KDE on Windows/Tools

2008-03-10T13:44:53Z

Rhabacker: added process monitor

Required or recommended tools for development and using KDE libraries and applications under MS Windows.

__TOC__

== Process Explorer ==
''"Ever wondered which program has a particular file or directory open? Now you can find out. Process Explorer shows you information about which handles and DLLs processes have opened or loaded."'' (freeware, for all Windows versions) [http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx more]
[[Image:ProcessExplorer.jpg|thumb|center|Process Explorer]]

== Console 2 ==
''"Console is a Windows console window (cmd.exe) enhancement, useful for using when you depend on this shell, e.g. with msvc. Console features include: multiple tabs, text editor-like text selection, different background types, alpha and color-key transparency, configurable font, different window styles."'' (GPL, for Windows 2000 or newer) [http://sourceforge.net/projects/console more]
[[Image:ConsoleWindowsTool.png|thumb|center|Console window]]

== DebugView ==
Debug messages (logs) generated by kDebug() and kWarning() are not visible on MS Windows unless application is compiled in so-called CONSOLE subsystem. To show these messages also in WINDOWS subsystem, you can use DebugView tool. The tool offers searching in logs, filtering them using wildcards and saving them to file. (freeware) [http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx more]
[[Image:DebugViewWindows.png|thumb|center|DebugView window]]

== Dependency Walker ==
A tool for checking dependency of shared libraries. This utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. (freeware) [http://www.dependencywalker.com/ more]
[[Image:DependencyWalkerWindows.png|thumb|center|Dependency Walker window]]

== Process Monitor ==
Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity.
[http://technet.microsoft.com/de-de/sysinternals/bb896645(en-us).aspx more]

Projects/Summer of Code/2008/Ideas

2008-02-26T14:54:07Z

Rhabacker: win32 named pipe implementation

This page is an open list for ideas for the 2008 edition of [http://code.google.com/soc Google Summer of Code]. This page is open for new ideas from anyone.

This list is not exhaustive. It is just a collection of some ideas. To get further ideas, please feel free to use any resources and [[#Past_Ideas|past ideas]].

Before proceeding, please read the [[Projects/Summer of Code/2008/Participation|participation instructions]] and [[#Notes_on_editing_this_page|the notes on editing this page]]. They are useful for students and developers alike.

== Past ideas ==

You may want to take a look at the ideas page for [http://wiki.kde.org/tiki-index.php?page=KDE%20Google%20SoC%202006%20ideas 2006] and [[Projects/Summer_of_Code/2007/Ideas|2007]]. Many of the ideas there are still valid today.

== Project ideas ==

These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at.

If there is no specific contact given you can ask questions on the general KDE development list kde-devel@kde.org. See [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.

When adding an idea to this section, please try to include the following data:
:* if the application is not widely known, a description of what it does and where its code lives
:* a brief explanation
:* the expected results
:* pre-requisites for working on your project
:* if applicable, links to more information or discussions
:* mailing list or IRC channel for your application/library/module
:* your name and email address for contact (if you're willing to be a mentor)

=== KDE Libs ===

==== KDE Core libraries ====

The KDE core libraries (kdecore, kdeui, kio, kparts) are the most basic libraries that all KDE applications depend upon.

==== Solid ====

Solid is the KDE hardware abstraction layer, that enables KDE programs to get consistent results when running on different platforms.

==== Phonon ====

Phonon is the KDE audio abstraction layer, that enables KDE programs to produce basic and medium-level multimedia functionality in any platform without platform-specific code.

==== KHTML ====

KHTML is the current KDE HTML engine, used by the Konqueror web-browser and other applications to display HTML in their interfaces.

==== KJS ====

KJS is the JavaScript engine used by KHTML and Kross to run JavaScript programs.

==== Sonnet ====

Sonnet is the KDE grammar, spell-checker and language-detection engine.

==== Kross ====

Kross is a modular scripting framework that provides a complete framework to embed scripting interpreters like Python, Ruby and KDE JavaScript transparently into native applications to bridge the static and dynamic worlds together.

==== Oxygen ====

Oxygen is the KDE 4's default look-and-feel. It comprises of the Oxygen icon set (including the palette and guidelines for icons), the Oxygen sound theme, the Oxygen wallpaper collection, the Oxygen window decoration and the Oxygen widget style. Note that for Summer of Code, you must produce code, so the window decoration and widget styles are your more likely candidates.

=== KDE Base applications ===

==== Konqueror ====

Konqueror is KDE's powerful web browser and file manager.

==== Dolphin ====

Dolphin is KDE 4's default file manager application.

==== Konsole ====

Konsole is KDE's terminal application.

==== Kate and KWrite ====

Kate is KDE's Advanced Text Editor, both a full-featured text editor application and a KPart engine ready for embedding into other applications (like KDevelop, Quanta and Kile). KWrite is a simple text editor based on the KatePart engine and is KDE's default text editor.

=== KDE Workspace ===

==== Plasma ====

Plasma is KDE 4's desktop and panel tool, replacing KDE 3's kicker and kdesktop. It's an advanced and power application with revolutionary ideas.

==== KWin ====

KWin is KDE's X11 Window Manager program, greatly improved when compared to its older brother in KDE 3.

==== KDM ====

KDM is KDE's Display Manager and login application.

=== KDE Runtime ===

=== KOffice ===

==== KWord ====
==== KSpread ====
==== Kexi ====
==== Krita ====

=== KDE Edu ===

=== KDE PIM (Personal Information Management) ===

==== Kontact ====

==== KOrganizer ====

==== KPilot ====

==== KMail ====

==== Akonadi ====

=== KDE Games ===

=== KDevelop & Quanta ===

=== Kopete ===

=== Amarok ===

=== Okular ===

=== Other applications ===

=== Usability ===

=== Infrastructure ===

KDE infrastructure tools, like Bugzilla, the Review Board, etc.

=== KDE dependencies and non-KDE projects ===

Depending on the relevance of the proposal, the KDE Project will accept student proposals on projects that are not part of KDE, but which are either KDE dependencies or relevant to KDE or the Free Software Desktop.

==== Qt Cryptographic Architecture ====

==== Strigi ====

==== Soprano & Nepomuk ====

==== D-Bus ====
a named pipe or shared memory transport implementation for win32

==== Other Freedesktop.org initiatives ====

== Notes on editing this page ==

Before making any modifications, please '''log in''' to Techbase. This will help us track who is contributing to the ideas.

When making modifications to existing ideas, please consider whether you're changing it more fundamentally or just superficially. If your changes are substantial, you probably have an entirely new idea. Similarly, if your idea is modified and you feel it no longer reflects your original thought, please split the idea in two, restoring yours.

Please use the [[Talk:Projects/Summer of Code/2008/Ideas|talk page]] if you want to discuss an idea.

Finally, do '''not''' delete ideas without a reason for doing so (like, for instance, being contrary to KDE ideals, being completely unrelated to KDE, being unfeasible, etc.) -- you may want to state in the [[Talk:Projects/Summer of Code/2009/Ideas|talk page]] why you removed the idea.

Do '''not''' re-add ideas that were removed without discussing first with the developers of the target application.

Projects/KDE on Windows/Installation

2008-02-01T18:30:08Z

Rhabacker: /* Status */

{{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?]]}}

Author:章世宁
== 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.

'''If you experience any problems please have a look into our [http://lists.kde.org/?l=kde-windows&r=1&w=2| mailing list].'''

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 add 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>).
* [TEMPORARILY] Follow the instructions at [[#post-install steps]]
* 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>kwrite.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 because of the provided runtime environments.
You're free to decide which to take.

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, kdebase-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).
rhabacker: This is fixed in installer version > 0.8.4.

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries]] is a more complete list of libraries that a full installation needs.

=== Issues with KDE Installer for Windows ===
Currently no issues known. If you found an issue, please report to [mailto:kde-windows@kde.org].

== post-install steps ==
You currently need to run a number of command-line programs to set up KDE. Here are the steps.

===Run update-mime-database===
Be sure that you have no KDE-related applications: run the Windows Task Manager (taskmgr.exe), switch to its Processes tab, and kill all occurences of dbus-daemon.exe, kded4.exe, kioslave.exe and klauncher.exe (and all other KDE apps).

Open a Windows command prompt (cmd.exe) and navigate to the directory where you installed KDE. Say you installed KDE to C:\KDE4, then run from the cmd.exe window:<pre>C:\KDE4> '''bin\update-mime-database C:\KDE4\share\mime'''</pre>This will give you a lot of warning message. Most of them you can easily ignore; even if you should set [[KDE_System_Administration/Environment_Variables#XDG_DATA_HOME|XDG_DATA_HOME]] or [[KDE_System_Administration/Environment_Variables#XDG_DATA_DIRS|XDG_DATA_DIRS]] it worked perfectly. If it says you should rerun update-mime-database as root then you're not within your installation directory.

===Run kbuildsyscoca4===
After finishing the previous step, run <pre>C:\KDE4> '''bin\kbuildsycoca4 --noincremental'''</pre> If this tells you that your disk is full (which is most probably not the case) you have still some executables from KDE running. Please close them and try again.

Excuse us for the inconvenience — we hope for a better solution in the next release.

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

== Fine-tuning ==
===Set Oxygen style for widgets===
The default KDE widget style on Windows is the native one. You already have Oxygen style installed (which is a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:
#edit <tt>%UserPROFILE%\.kde\share\config\kdeglobals</tt> with any text editor (e.g. kwrite)
#locate line containing "[General]" text, what is a section, if there is no such line, add one
#replace or add <tt>widgetStyle=....</tt> line with <tt>widgetStyle=oxygen</tt>.
Newly started applications should be displayed with Oxygen style now.

== Status ==
Using kdewin-installer-gui-0.8.5.exe to install 4.00.80 packages:
* starting a KDE program correctly starts dbus-daemon.exe
* many games run
* choosing File > Open correctly starts klauncher.exe, kioslave.exe and kded4.exe, and runs kbuildsycoca4.exe as needed.
* Help > ''Program'' Handbook (often mapped to the [F1] key) does not work because the KDE Help Center is not available on Windows. This is due to its use of the K3Process interface and external dependencies not ported such as perl scripts, htdig, and other libraries.
rhabacker: khelpcenter will be included in the next unstable release. The K3Process issues are fixed now. Perl scripts are disabled, which means there is no fulltext search.

General notes:
* There are many other KDE programs that are not part of KDE 4.0.0 and are not currently packaged for Windows, such as KOffice 2 and Amarok.
* By design, KDE-windows does not provide the full-blown KDE desktop, thus no KWin composite manager, KDE-specific "start" menus, Plasma desktop, etc.

=== Package status and contents ===
{| border="0" cellpadding="2"
|-valign="top"
!package
!status
!contains applications
|-valign="top"
|kdebase
|packaged
|Konqueror, Dolphin, KWrite, etc.
|-valign="top"
|kdegames
|packaged
|Kgoldrunner, Kpat, KMahjongg, etc.
|-valign="top"
|kdesdk
|packaged
|Kate, Umbrello, etc.
|-valign="top"
|kdetoys
|packaged
|KTeatime, etc.
|-valign="top"
|kdeedu
|packaged
|Marble, Parley, KStars, KHangman, etc.
|-valign="top"
|kdegraphics
|not packaged
|Okular, kolourpaint, etc.
|-valign="top"
|amarok
|not packaged
|Amarok
|-valign="top"
|koffice
|not packaged
|KWord, Krita, Karbon, etc.
|-valign="top"
|kdepim
|not building
|KMail, AKregator, etc.
|-valign="top"
|kdenetwork
|not building
|Kopete, KGet, etc.
|}

[[Category: MS Windows]]

Projects/KDE on Windows/Installation

2008-02-01T18:29:49Z

Rhabacker: /* Status */

{{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?]]}}

Author:章世宁
== 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.

'''If you experience any problems please have a look into our [http://lists.kde.org/?l=kde-windows&r=1&w=2| mailing list].'''

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 add 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>).
* [TEMPORARILY] Follow the instructions at [[#post-install steps]]
* 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>kwrite.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 because of the provided runtime environments.
You're free to decide which to take.

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, kdebase-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).
rhabacker: This is fixed in installer version > 0.8.4.

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries]] is a more complete list of libraries that a full installation needs.

=== Issues with KDE Installer for Windows ===
Currently no issues known. If you found an issue, please report to [mailto:kde-windows@kde.org].

== post-install steps ==
You currently need to run a number of command-line programs to set up KDE. Here are the steps.

===Run update-mime-database===
Be sure that you have no KDE-related applications: run the Windows Task Manager (taskmgr.exe), switch to its Processes tab, and kill all occurences of dbus-daemon.exe, kded4.exe, kioslave.exe and klauncher.exe (and all other KDE apps).

Open a Windows command prompt (cmd.exe) and navigate to the directory where you installed KDE. Say you installed KDE to C:\KDE4, then run from the cmd.exe window:<pre>C:\KDE4> '''bin\update-mime-database C:\KDE4\share\mime'''</pre>This will give you a lot of warning message. Most of them you can easily ignore; even if you should set [[KDE_System_Administration/Environment_Variables#XDG_DATA_HOME|XDG_DATA_HOME]] or [[KDE_System_Administration/Environment_Variables#XDG_DATA_DIRS|XDG_DATA_DIRS]] it worked perfectly. If it says you should rerun update-mime-database as root then you're not within your installation directory.

===Run kbuildsyscoca4===
After finishing the previous step, run <pre>C:\KDE4> '''bin\kbuildsycoca4 --noincremental'''</pre> If this tells you that your disk is full (which is most probably not the case) you have still some executables from KDE running. Please close them and try again.

Excuse us for the inconvenience — we hope for a better solution in the next release.

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

== Fine-tuning ==
===Set Oxygen style for widgets===
The default KDE widget style on Windows is the native one. You already have Oxygen style installed (which is a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:
#edit <tt>%UserPROFILE%\.kde\share\config\kdeglobals</tt> with any text editor (e.g. kwrite)
#locate line containing "[General]" text, what is a section, if there is no such line, add one
#replace or add <tt>widgetStyle=....</tt> line with <tt>widgetStyle=oxygen</tt>.
Newly started applications should be displayed with Oxygen style now.

== Status ==
Using kdewin-installer-gui-0.8.5.exe to install 4.00.80 packages:
* starting a KDE program correctly starts dbus-daemon.exe
* many games run
* choosing File > Open correctly starts klauncher.exe, kioslave.exe and kded4.exe, and runs kbuildsycoca4.exe as needed.
* Help > ''Program'' Handbook (often mapped to the [F1] key) does not work because the KDE Help Center is not available on Windows. This is due to its use of the K3Process interface and external dependencies not ported such as perl scripts, htdig, and other libraries.
rhabacker: khelpcenter will be included be in the next unstable release. The K3Process issues are fixed now. Perl scripts are disabled, which means there is no fulltext search.

General notes:
* There are many other KDE programs that are not part of KDE 4.0.0 and are not currently packaged for Windows, such as KOffice 2 and Amarok.
* By design, KDE-windows does not provide the full-blown KDE desktop, thus no KWin composite manager, KDE-specific "start" menus, Plasma desktop, etc.

=== Package status and contents ===
{| border="0" cellpadding="2"
|-valign="top"
!package
!status
!contains applications
|-valign="top"
|kdebase
|packaged
|Konqueror, Dolphin, KWrite, etc.
|-valign="top"
|kdegames
|packaged
|Kgoldrunner, Kpat, KMahjongg, etc.
|-valign="top"
|kdesdk
|packaged
|Kate, Umbrello, etc.
|-valign="top"
|kdetoys
|packaged
|KTeatime, etc.
|-valign="top"
|kdeedu
|packaged
|Marble, Parley, KStars, KHangman, etc.
|-valign="top"
|kdegraphics
|not packaged
|Okular, kolourpaint, etc.
|-valign="top"
|amarok
|not packaged
|Amarok
|-valign="top"
|koffice
|not packaged
|KWord, Krita, Karbon, etc.
|-valign="top"
|kdepim
|not building
|KMail, AKregator, etc.
|-valign="top"
|kdenetwork
|not building
|Kopete, KGet, etc.
|}

[[Category: MS Windows]]

Projects/KDE on Windows/Installation

2008-02-01T18:29:05Z

Rhabacker: khelpcenter notes

{{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?]]}}

Author:章世宁
== 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.

'''If you experience any problems please have a look into our [http://lists.kde.org/?l=kde-windows&r=1&w=2| mailing list].'''

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 add 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>).
* [TEMPORARILY] Follow the instructions at [[#post-install steps]]
* 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>kwrite.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 because of the provided runtime environments.
You're free to decide which to take.

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, kdebase-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).
rhabacker: This is fixed in installer version > 0.8.4.

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries]] is a more complete list of libraries that a full installation needs.

=== Issues with KDE Installer for Windows ===
Currently no issues known. If you found an issue, please report to [mailto:kde-windows@kde.org].

== post-install steps ==
You currently need to run a number of command-line programs to set up KDE. Here are the steps.

===Run update-mime-database===
Be sure that you have no KDE-related applications: run the Windows Task Manager (taskmgr.exe), switch to its Processes tab, and kill all occurences of dbus-daemon.exe, kded4.exe, kioslave.exe and klauncher.exe (and all other KDE apps).

Open a Windows command prompt (cmd.exe) and navigate to the directory where you installed KDE. Say you installed KDE to C:\KDE4, then run from the cmd.exe window:<pre>C:\KDE4> '''bin\update-mime-database C:\KDE4\share\mime'''</pre>This will give you a lot of warning message. Most of them you can easily ignore; even if you should set [[KDE_System_Administration/Environment_Variables#XDG_DATA_HOME|XDG_DATA_HOME]] or [[KDE_System_Administration/Environment_Variables#XDG_DATA_DIRS|XDG_DATA_DIRS]] it worked perfectly. If it says you should rerun update-mime-database as root then you're not within your installation directory.

===Run kbuildsyscoca4===
After finishing the previous step, run <pre>C:\KDE4> '''bin\kbuildsycoca4 --noincremental'''</pre> If this tells you that your disk is full (which is most probably not the case) you have still some executables from KDE running. Please close them and try again.

Excuse us for the inconvenience — we hope for a better solution in the next release.

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

== Fine-tuning ==
===Set Oxygen style for widgets===
The default KDE widget style on Windows is the native one. You already have Oxygen style installed (which is a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:
#edit <tt>%UserPROFILE%\.kde\share\config\kdeglobals</tt> with any text editor (e.g. kwrite)
#locate line containing "[General]" text, what is a section, if there is no such line, add one
#replace or add <tt>widgetStyle=....</tt> line with <tt>widgetStyle=oxygen</tt>.
Newly started applications should be displayed with Oxygen style now.

== Status ==
Using kdewin-installer-gui-0.8.5.exe to install 4.00.80 packages:
* starting a KDE program correctly starts dbus-daemon.exe
* many games run
* choosing File > Open correctly starts klauncher.exe, kioslave.exe and kded4.exe, and runs kbuildsycoca4.exe as needed.
* Help > ''Program'' Handbook (often mapped to the [F1] key) does not work because the KDE Help Center is not available on Windows. This is due to its use of the K3Process interface and external dependencies not ported such as perl scripts, htdig, and other libraries.
rhabacker: khelpcenter will available be in the next unstable release. The K3Process issues are fixed now. Perl scripts are disabled, which means there is no fulltext search.

General notes:
* There are many other KDE programs that are not part of KDE 4.0.0 and are not currently packaged for Windows, such as KOffice 2 and Amarok.
* By design, KDE-windows does not provide the full-blown KDE desktop, thus no KWin composite manager, KDE-specific "start" menus, Plasma desktop, etc.

=== Package status and contents ===
{| border="0" cellpadding="2"
|-valign="top"
!package
!status
!contains applications
|-valign="top"
|kdebase
|packaged
|Konqueror, Dolphin, KWrite, etc.
|-valign="top"
|kdegames
|packaged
|Kgoldrunner, Kpat, KMahjongg, etc.
|-valign="top"
|kdesdk
|packaged
|Kate, Umbrello, etc.
|-valign="top"
|kdetoys
|packaged
|KTeatime, etc.
|-valign="top"
|kdeedu
|packaged
|Marble, Parley, KStars, KHangman, etc.
|-valign="top"
|kdegraphics
|not packaged
|Okular, kolourpaint, etc.
|-valign="top"
|amarok
|not packaged
|Amarok
|-valign="top"
|koffice
|not packaged
|KWord, Krita, Karbon, etc.
|-valign="top"
|kdepim
|not building
|KMail, AKregator, etc.
|-valign="top"
|kdenetwork
|not building
|Kopete, KGet, etc.
|}

[[Category: MS Windows]]

Projects/KDE on Windows/Installation

2008-02-01T18:24:22Z

Rhabacker: /* Download needed packages */

{{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?]]}}

Author:章世宁
== 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.

'''If you experience any problems please have a look into our [http://lists.kde.org/?l=kde-windows&r=1&w=2| mailing list].'''

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 add 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>).
* [TEMPORARILY] Follow the instructions at [[#post-install steps]]
* 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>kwrite.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 because of the provided runtime environments.
You're free to decide which to take.

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, kdebase-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).
rhabacker: This is fixed in installer version > 0.8.4.

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries]] is a more complete list of libraries that a full installation needs.

=== Issues with KDE Installer for Windows ===
Currently no issues known. If you found an issue, please report to [mailto:kde-windows@kde.org].

== post-install steps ==
You currently need to run a number of command-line programs to set up KDE. Here are the steps.

===Run update-mime-database===
Be sure that you have no KDE-related applications: run the Windows Task Manager (taskmgr.exe), switch to its Processes tab, and kill all occurences of dbus-daemon.exe, kded4.exe, kioslave.exe and klauncher.exe (and all other KDE apps).

Open a Windows command prompt (cmd.exe) and navigate to the directory where you installed KDE. Say you installed KDE to C:\KDE4, then run from the cmd.exe window:<pre>C:\KDE4> '''bin\update-mime-database C:\KDE4\share\mime'''</pre>This will give you a lot of warning message. Most of them you can easily ignore; even if you should set [[KDE_System_Administration/Environment_Variables#XDG_DATA_HOME|XDG_DATA_HOME]] or [[KDE_System_Administration/Environment_Variables#XDG_DATA_DIRS|XDG_DATA_DIRS]] it worked perfectly. If it says you should rerun update-mime-database as root then you're not within your installation directory.

===Run kbuildsyscoca4===
After finishing the previous step, run <pre>C:\KDE4> '''bin\kbuildsycoca4 --noincremental'''</pre> If this tells you that your disk is full (which is most probably not the case) you have still some executables from KDE running. Please close them and try again.

Excuse us for the inconvenience — we hope for a better solution in the next release.

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

== Fine-tuning ==
===Set Oxygen style for widgets===
The default KDE widget style on Windows is the native one. You already have Oxygen style installed (which is a plugin library %KDEROOT%\lib\kde4\plugins\styles\oxygen.dll), so it can be used as well. To set it for a single user:
#edit <tt>%UserPROFILE%\.kde\share\config\kdeglobals</tt> with any text editor (e.g. kwrite)
#locate line containing "[General]" text, what is a section, if there is no such line, add one
#replace or add <tt>widgetStyle=....</tt> line with <tt>widgetStyle=oxygen</tt>.
Newly started applications should be displayed with Oxygen style now.

== Status ==
Using kdewin-installer-gui-0.8.5.exe to install 4.00.80 packages:
* starting a KDE program correctly starts dbus-daemon.exe
* many games run
* choosing File > Open correctly starts klauncher.exe, kioslave.exe and kded4.exe, and runs kbuildsycoca4.exe as needed.
* Help > ''Program'' Handbook (often mapped to the [F1] key) does not work because the KDE Help Center is not available on Windows. This is due to its use of the K3Process interface and external dependencies not ported such as perl scripts, htdig, and other libraries.

General notes:
* There are many other KDE programs that are not part of KDE 4.0.0 and are not currently packaged for Windows, such as KOffice 2 and Amarok.
* By design, KDE-windows does not provide the full-blown KDE desktop, thus no KWin composite manager, KDE-specific "start" menus, Plasma desktop, etc.

=== Package status and contents ===
{| border="0" cellpadding="2"
|-valign="top"
!package
!status
!contains applications
|-valign="top"
|kdebase
|packaged
|Konqueror, Dolphin, KWrite, etc.
|-valign="top"
|kdegames
|packaged
|Kgoldrunner, Kpat, KMahjongg, etc.
|-valign="top"
|kdesdk
|packaged
|Kate, Umbrello, etc.
|-valign="top"
|kdetoys
|packaged
|KTeatime, etc.
|-valign="top"
|kdeedu
|packaged
|Marble, Parley, KStars, KHangman, etc.
|-valign="top"
|kdegraphics
|not packaged
|Okular, kolourpaint, etc.
|-valign="top"
|amarok
|not packaged
|Amarok
|-valign="top"
|koffice
|not packaged
|KWord, Krita, Karbon, etc.
|-valign="top"
|kdepim
|not building
|KMail, AKregator, etc.
|-valign="top"
|kdenetwork
|not building
|Kopete, KGet, etc.
|}

[[Category: MS Windows]]

Getting Started/Build/Windows/MS Visual Studio

2008-01-04T16:29:18Z

Rhabacker: updated dbus topic

{{improve|''This page is outdated - please don't use it anymore unless you know exactly what you do. Use [[Getting_Started/Build/KDE4/Windows/emerge]] instead''}}

{{KDE4}}
{{improve|''This page has been moved out of [http://kdelibs.com/wiki/index.php/Building_KDElibs_4_using_MS_Visual_Studio kdelibs.com] wiki page.''}}
== Basic Tools ==
=== Kdewin-Installer ===
This is a program that lets you easily install all the requirements for building kdelibs. It also has a list of tools in its list that are helpful and needed, like the mingw compiler suite, subversion clients, debugging tools and so on.

The kdewin-installer is available in a GUI and console-only form from
[http://download.cegit.de/kde-windows/installer/ the kdewin-installer download page].

=== The Compiler ===
You can use either:
* (commercial) Visual Studio 2005 SP1, or
* free (as in beer) [http://msdn.microsoft.com/vstudio/express/visualC/default.aspx Visual Studio 2005 Express Edition] with the [http://www.microsoft.com/downloads/details.aspx?familyid=484269E2-3B89-47E3-8EB7-1F2BE6D7123A Platfrom SDK] and [http://www.microsoft.com/downloads/details.aspx?FamilyID=7b0b0339-613a-46e6-ab4d-080d4d4a8c4e&DisplayLang=de#filelist Service Pack 1]

Express Edition users: If you want to generate project files for Visual C++ then you must add the Platform SDK include and library directory to the default directories of the IDE:

<pre>
Open Visual C++, go to Tool->Options
in "Projects and Solutions" go to "VC++ Directories"

On the right add the paths to your Platform SDK files:
for "Library Files": YOUR_PLATFORM_SDK_PATH\lib
for "Include Files": YOUR_PLATFORM_SDK_PATH\include
</pre>

=== CMake ===
[http://www.cmake.org CMake] is the make tool used by KDE.
You can get the most recent binaries from [http://www.cmake.org/HTML/Download.html here]. Use the Win32 Installer or the zip archive. Make sure you use at least cmake 2.4.5

On Windows 2000, it's recommended to install cmake in a path without spaces to avoid troubles.

== Compile and Install additional libraries ==
These libraries have to be installed:

=== D-Bus for Windows ===
This library can be downloaded and installed with the installer (use the package name dbus-msvc) or you can [[Getting_Started/Build/KDE4/Windows/Building DBus|compile]] it by yourself.

=== Qt 4 ===
This Framework can be downloaded with the installer, or you can [[Getting_Started/Build/KDE4/Windows/Building Qt 4|build it on your own]].

=== KDESupport Libraries ===
There are several libraries which will be required for building kdelibs. [[Getting Started/Build/KDE4/Windows/Building KDESupport Libraries|You may want to compile them yourself]] or simply download them using the KDEWin-Installer. You will need:
*kdewin32 (compiled with msvc)
*strigi
*soprano
*qca2
*qimageblitz

=== Environment Settings ===
To set up a build environment, follow the steps over [[Getting Started/Build/KDE4/Windows/Environment|here]]. '''If you have Cygwin installed, please be sure to remove Cygwin's /bin out of your path.'''

== Build KDElibs ==
Check out the sources and make another build directory at the same level as kdelibs:
<pre>
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs
cd ..
mkdir kdelibs-build
cd kdelibs-build
</pre>
Now you have to add some paths to your PATH environment variable simliar to this:
<pre>
set PATH=%QTDIR%\bin;%PATH%;%INSTALL_PATH%\lib;
</pre>
Build KDE libraries with:
<pre>
cmake -DCMAKE_INSTALL_PREFIX=%INSTALL_PATH% -DCMAKE_BUILD_TYPE=Debug\
-G"NMake Makefiles" ..\kdelibs
nmake
nmake install
</pre>
or use the IDE:
<pre>
cmake -DCMAKE_INSTALL_PREFIX=%INSTALL_PATH% -DCMAKE_BUILD_TYPE=Debug\
-G "Visual Studio 8 2005" ..\kdelibs
</pre>
(use -G "Visual Studio 7 .NET 2003" for the older compiler)

In the latter case <tt>kdelibs.sln</tt> solution file will be created. Build and '''install''' the Debug and Release builds with the IDE. '''Tip:''' to do this from command line, type:

devenv /build Debug /project INSTALL kdelibs.sln
devenv /build Release /project INSTALL kdelibs.sln

The devenv command is not available in the Express Edition.

If you use makefiles and also want to build the test programs add the option <tt>-DKDE4_BUILD_TESTS=1</tt> to the <tt>cmake</tt> command. This is not necessary for the IDE projects.

== Troubles? ==
*to enable the release build add <tt>-DCMAKE_BUILD_TYPE=Release</tt> to the <tt>cmake</tt> command
*when kdewin32 is not found, try adding the cmake parameter (with YOUR path)<tt>-DGNUWIN32_DIR=c:/gnuwin32</tt>
*don't use a cygwin or mingw shell, you will get errors because these shells use UNIX path names
*you could restart the configure process by deleting CMakeCache.txt
*you could test for only one library by deleting the assignment in CMakeCache.txt
*ask for more help on [https://mail.kde.org/mailman/listinfo/kde-buildsystem kde-buildsystem@kde.org] mailing list
*whenever you update your checkout DON'T forget to rebuild '''AND''' reinstall kdewin32.lib

== Going further: kdepimlibs ==
'''kdepimlibs''' are needed by kdebase or other modules like koffice.
=== Requirements ===
kdepimlibs require:
*[http://boost.org/ boost libraries]. Download the tarball. As boost is consisted of headers only, unpack the tarball and copy <tt>boost</tt> subdirectory to <tt>%KDEDIR%\include</tt>. Then add use <tt>set BOOST_ROOT=%KDEDIR%\include</tt> (you may want to add it to your <tt>environment.bat</tt> file as well).
*[http://www.gpg4win.org/ gpgme] libraries, needed to provide GNU Privacy Guard support in KDE PIM applications
*(really optional for now) [http://www.openldap.org OpenLDAP]: LDAP (Lightweight Directory Access Protocol) libraries Needed to provide LDAP functionality in KDE
*(really optional for now) [http://asg.web.cmu.edu/sasl/sasl-library.html cyrus-sasl]: Cyrus SASL API needed to support authentication of logins

=== Build ===
Check out the sources, make another build directory and build:
<pre>
cd {KDE_SOURCE_DIR}\trunk\KDE
svn up kdepimlibs
mkdir kdepimlibs-build
cd kdelibs-build
cmake -DCMAKE_INSTALL_PREFIX=%KDEDIRS% -DCMAKE_BUILD_TYPE=Debug\
-G"NMake Makefiles" ..\kdepimlibs
nmake
nmake install
</pre>
or use Visual Studio:
<pre>
cmake -DCMAKE_INSTALL_PREFIX=%INSTALL_PATH% -DCMAKE_BUILD_TYPE=Debug\
-G "Visual Studio 8 2005" ..\kdepimlibs
</pre>
(use -G "Visual Studio 7 .NET 2003" for the older compiler)

In the latter case <tt>kdepimlibs.sln</tt> solution file will be created. Build and '''install''' the Debug and Release builds with the IDE. '''Tip:''' to do this from command line, type:

devenv /build Debug /project INSTALL kdepimlibs.sln
devenv /build Release /project INSTALL kdepimlibs.sln

The devenv command is not available in the Express Edition.

== Going further: kofficelibs ==
''(work in progress, to be moved to KOffice wiki)''

'''kofficelibs''' are needed for apps like KWord or Kexi.
=== Requirements ===
kofficelibs require:
*[http://www.littlecms.com Little cms] library. Download the newest lcms-1.??.zip from [http://www.littlecms.com/downloads.htm] and uncompress. To build it with msvc, go to <tt>Projects</tt> subdir and choose a subdir for your compiler (i.e. Vc7 or Vc2005).
*#Then you will see <tt>lcms.sln</tt> solution file - you can click it to open in the msvc IDE. But first, you need to fix some paths in the project files. You probably have <tt>%KDEDIR%\lib\jpeg.lib</tt>, not libjpeg.lib, so edit <tt>tifficc.vcproj</tt>, <tt>tiffdiff.vcproj</tt> and <tt>jpegicc.vcproj</tt> and change libjpeg.lib to jpeg.lib in <tt>AdditionalDependencies</tt> variable. Then add full path to your <tt>%KDEDIR%\include</tt> directory (where tiffio.h resides) in AdditionalIncludeDirectories variable, (note: do it by expanding KDEDIR environment variable, i.e the result should be like: <pre>AdditionalIncludeDirectories="..\..\include;f:\kde4\include"</pre> Then add <tt>AdditionalLibraryDirectories="c:\your\path\to\kde\lib"</tt> line just after every two occurences of <tt>AdditionalIncludeDirectories=</tt>. All the changes are presented in [[Getting_Started/Build/KDE4/Windows/Littlecms.patch|this pseudo-patch]] (change f:\ paths to your KDEDIR location!).
*#You probbaly want to skip building Python wrapper, so click on Build->Configuration Manager menu command and check off "Build" in "Python" line.
*#Select "Build Solution" menu command. After successful build, you should notice:<tt>Build: 9 succeeded, 0 failed, 1 skipped</tt>
*#To also build Release versions of the binaries, in the ''Configuration Manager'', change active configuration to ''Release'' and repeat steps 1-3.
*# Copy the compiled binaries. From your <tt>lcms-1.??\Lib\Ms</tt> copy <tt>*.lib</tt> files to <tt>%KDEDIR%\lib</tt>. From <tt>lcms-1.??\bin</tt> copy <tt>*.dll</tt> and <tt>*.exe</tt> files to <tt>%KDEDIR%\bin</tt>.
*#Copy lcms headers: from <tt>lcms-1.??\include</tt> copy <tt>*.h</tt> to <tt>%KDEDIR%\include</tt>.
*#Later when you will run cmake for kofficelibs, you get message like <tt>-- Found lcms version 1.16, F:/kde4/lib/lcms.lib</tt>.

==Useful links==

List of libraries that are needed to build KDE on windows (most of these are already installed by the kde-installer)

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries|3rd-party libraries required for KDElibs 4]].

[[Category:MS Windows]]

Getting Started/Build/Windows/MS Visual Studio

2008-01-04T16:25:33Z

Rhabacker: updated

{{improve|''This page is outdated - please don't use it anymore unless you know exactly what you do. Use [[Getting_Started/Build/KDE4/Windows/emerge]] instead''}}

{{KDE4}}
{{improve|''This page has been moved out of [http://kdelibs.com/wiki/index.php/Building_KDElibs_4_using_MS_Visual_Studio kdelibs.com] wiki page.''}}
== Basic Tools ==
=== Kdewin-Installer ===
This is a program that lets you easily install all the requirements for building kdelibs. It also has a list of tools in its list that are helpful and needed, like the mingw compiler suite, subversion clients, debugging tools and so on.

The kdewin-installer is available in a GUI and console-only form from
[http://download.cegit.de/kde-windows/installer/ the kdewin-installer download page].

=== The Compiler ===
You can use either:
* (commercial) Visual Studio 2005 SP1, or
* free (as in beer) [http://msdn.microsoft.com/vstudio/express/visualC/default.aspx Visual Studio 2005 Express Edition] with the [http://www.microsoft.com/downloads/details.aspx?familyid=484269E2-3B89-47E3-8EB7-1F2BE6D7123A Platfrom SDK] and [http://www.microsoft.com/downloads/details.aspx?FamilyID=7b0b0339-613a-46e6-ab4d-080d4d4a8c4e&DisplayLang=de#filelist Service Pack 1]

Express Edition users: If you want to generate project files for Visual C++ then you must add the Platform SDK include and library directory to the default directories of the IDE:

<pre>
Open Visual C++, go to Tool->Options
in "Projects and Solutions" go to "VC++ Directories"

On the right add the paths to your Platform SDK files:
for "Library Files": YOUR_PLATFORM_SDK_PATH\lib
for "Include Files": YOUR_PLATFORM_SDK_PATH\include
</pre>

=== CMake ===
[http://www.cmake.org CMake] is the make tool used by KDE.
You can get the most recent binaries from [http://www.cmake.org/HTML/Download.html here]. Use the Win32 Installer or the zip archive. Make sure you use at least cmake 2.4.5

On Windows 2000, it's recommended to install cmake in a path without spaces to avoid troubles.

== Compile and Install additional libraries ==
These libraries have to be installed:

=== D-Bus for Windows ===
This library can be installed with the installer. Choose the package named dbus-msvc.

=== Qt 4 ===
This Framework can be downloaded with the installer, or you can [[Getting_Started/Build/KDE4/Windows/Building Qt 4|build it on your own]].

=== KDESupport Libraries ===
There are several libraries which will be required for building kdelibs. [[Getting Started/Build/KDE4/Windows/Building KDESupport Libraries|You may want to compile them yourself]] or simply download them using the KDEWin-Installer. You will need:
*kdewin32 (compiled with msvc)
*strigi
*soprano
*qca2
*qimageblitz

=== Environment Settings ===
To set up a build environment, follow the steps over [[Getting Started/Build/KDE4/Windows/Environment|here]]. '''If you have Cygwin installed, please be sure to remove Cygwin's /bin out of your path.'''

== Build KDElibs ==
Check out the sources and make another build directory at the same level as kdelibs:
<pre>
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs
cd ..
mkdir kdelibs-build
cd kdelibs-build
</pre>
Now you have to add some paths to your PATH environment variable simliar to this:
<pre>
set PATH=%QTDIR%\bin;%PATH%;%INSTALL_PATH%\lib;
</pre>
Build KDE libraries with:
<pre>
cmake -DCMAKE_INSTALL_PREFIX=%INSTALL_PATH% -DCMAKE_BUILD_TYPE=Debug\
-G"NMake Makefiles" ..\kdelibs
nmake
nmake install
</pre>
or use the IDE:
<pre>
cmake -DCMAKE_INSTALL_PREFIX=%INSTALL_PATH% -DCMAKE_BUILD_TYPE=Debug\
-G "Visual Studio 8 2005" ..\kdelibs
</pre>
(use -G "Visual Studio 7 .NET 2003" for the older compiler)

In the latter case <tt>kdelibs.sln</tt> solution file will be created. Build and '''install''' the Debug and Release builds with the IDE. '''Tip:''' to do this from command line, type:

devenv /build Debug /project INSTALL kdelibs.sln
devenv /build Release /project INSTALL kdelibs.sln

The devenv command is not available in the Express Edition.

If you use makefiles and also want to build the test programs add the option <tt>-DKDE4_BUILD_TESTS=1</tt> to the <tt>cmake</tt> command. This is not necessary for the IDE projects.

== Troubles? ==
*to enable the release build add <tt>-DCMAKE_BUILD_TYPE=Release</tt> to the <tt>cmake</tt> command
*when kdewin32 is not found, try adding the cmake parameter (with YOUR path)<tt>-DGNUWIN32_DIR=c:/gnuwin32</tt>
*don't use a cygwin or mingw shell, you will get errors because these shells use UNIX path names
*you could restart the configure process by deleting CMakeCache.txt
*you could test for only one library by deleting the assignment in CMakeCache.txt
*ask for more help on [https://mail.kde.org/mailman/listinfo/kde-buildsystem kde-buildsystem@kde.org] mailing list
*whenever you update your checkout DON'T forget to rebuild '''AND''' reinstall kdewin32.lib

== Going further: kdepimlibs ==
'''kdepimlibs''' are needed by kdebase or other modules like koffice.
=== Requirements ===
kdepimlibs require:
*[http://boost.org/ boost libraries]. Download the tarball. As boost is consisted of headers only, unpack the tarball and copy <tt>boost</tt> subdirectory to <tt>%KDEDIR%\include</tt>. Then add use <tt>set BOOST_ROOT=%KDEDIR%\include</tt> (you may want to add it to your <tt>environment.bat</tt> file as well).
*[http://www.gpg4win.org/ gpgme] libraries, needed to provide GNU Privacy Guard support in KDE PIM applications
*(really optional for now) [http://www.openldap.org OpenLDAP]: LDAP (Lightweight Directory Access Protocol) libraries Needed to provide LDAP functionality in KDE
*(really optional for now) [http://asg.web.cmu.edu/sasl/sasl-library.html cyrus-sasl]: Cyrus SASL API needed to support authentication of logins

=== Build ===
Check out the sources, make another build directory and build:
<pre>
cd {KDE_SOURCE_DIR}\trunk\KDE
svn up kdepimlibs
mkdir kdepimlibs-build
cd kdelibs-build
cmake -DCMAKE_INSTALL_PREFIX=%KDEDIRS% -DCMAKE_BUILD_TYPE=Debug\
-G"NMake Makefiles" ..\kdepimlibs
nmake
nmake install
</pre>
or use Visual Studio:
<pre>
cmake -DCMAKE_INSTALL_PREFIX=%INSTALL_PATH% -DCMAKE_BUILD_TYPE=Debug\
-G "Visual Studio 8 2005" ..\kdepimlibs
</pre>
(use -G "Visual Studio 7 .NET 2003" for the older compiler)

In the latter case <tt>kdepimlibs.sln</tt> solution file will be created. Build and '''install''' the Debug and Release builds with the IDE. '''Tip:''' to do this from command line, type:

devenv /build Debug /project INSTALL kdepimlibs.sln
devenv /build Release /project INSTALL kdepimlibs.sln

The devenv command is not available in the Express Edition.

== Going further: kofficelibs ==
''(work in progress, to be moved to KOffice wiki)''

'''kofficelibs''' are needed for apps like KWord or Kexi.
=== Requirements ===
kofficelibs require:
*[http://www.littlecms.com Little cms] library. Download the newest lcms-1.??.zip from [http://www.littlecms.com/downloads.htm] and uncompress. To build it with msvc, go to <tt>Projects</tt> subdir and choose a subdir for your compiler (i.e. Vc7 or Vc2005).
*#Then you will see <tt>lcms.sln</tt> solution file - you can click it to open in the msvc IDE. But first, you need to fix some paths in the project files. You probably have <tt>%KDEDIR%\lib\jpeg.lib</tt>, not libjpeg.lib, so edit <tt>tifficc.vcproj</tt>, <tt>tiffdiff.vcproj</tt> and <tt>jpegicc.vcproj</tt> and change libjpeg.lib to jpeg.lib in <tt>AdditionalDependencies</tt> variable. Then add full path to your <tt>%KDEDIR%\include</tt> directory (where tiffio.h resides) in AdditionalIncludeDirectories variable, (note: do it by expanding KDEDIR environment variable, i.e the result should be like: <pre>AdditionalIncludeDirectories="..\..\include;f:\kde4\include"</pre> Then add <tt>AdditionalLibraryDirectories="c:\your\path\to\kde\lib"</tt> line just after every two occurences of <tt>AdditionalIncludeDirectories=</tt>. All the changes are presented in [[Getting_Started/Build/KDE4/Windows/Littlecms.patch|this pseudo-patch]] (change f:\ paths to your KDEDIR location!).
*#You probbaly want to skip building Python wrapper, so click on Build->Configuration Manager menu command and check off "Build" in "Python" line.
*#Select "Build Solution" menu command. After successful build, you should notice:<tt>Build: 9 succeeded, 0 failed, 1 skipped</tt>
*#To also build Release versions of the binaries, in the ''Configuration Manager'', change active configuration to ''Release'' and repeat steps 1-3.
*# Copy the compiled binaries. From your <tt>lcms-1.??\Lib\Ms</tt> copy <tt>*.lib</tt> files to <tt>%KDEDIR%\lib</tt>. From <tt>lcms-1.??\bin</tt> copy <tt>*.dll</tt> and <tt>*.exe</tt> files to <tt>%KDEDIR%\bin</tt>.
*#Copy lcms headers: from <tt>lcms-1.??\include</tt> copy <tt>*.h</tt> to <tt>%KDEDIR%\include</tt>.
*#Later when you will run cmake for kofficelibs, you get message like <tt>-- Found lcms version 1.16, F:/kde4/lib/lcms.lib</tt>.

==Useful links==

List of libraries that are needed to build KDE on windows (most of these are already installed by the kde-installer)

[[Getting_Started/Build/KDE4/Windows/3rd-party_libraries|3rd-party libraries required for KDElibs 4]].

[[Category:MS Windows]]

Projects/KDE on Windows/Installation

2007-12-11T07:29:17Z

Rhabacker: updated installer issues

Projects/KDE on Windows/Meetings/Berlin Meeting September 2007

2007-12-04T22:24:28Z

Rhabacker: added note

During the last weekend, the KDE on Windows developers conducted their second real life meeting in the Trolltech offices in Berlin Adlershof, incorporating new developers and improving infrastructure. [http://dot.kde.org/1190143020/ Read the dot story for details].

Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

=== TOPICS ===
*mirror related
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows -> there are snapshots available
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
*installer related
#development installation requires tools having own installers -> rhabacker: The installer is able to handle different installation roots, so one install root can be used for development and one for end-user. There is no need for additional installers.
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
#define directory format of the kde mirrors --> rhabacker: there is a directory structure available on the currently used mirrors, which is usable by the installer.
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host computer could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
# extend the installer with the following features:
#** <del>update function --> rhabacker: fixed</del>
#** <del>simplified end user interface --> rhabacker: fixed</del>
#** integrity checks (md5 package and file checks) --> rhabacker: started
#** cd/dvd/usb stick installation --> rhabacker: started

*package related
#<del>Insert compiler name into package and manifest file name (msvc, gcc) --> chehrlic: Should be fixed now</del>
* dbus related
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
*build system related
# KDELibsDependencies.cmake contains absolute file pathes. They have to be variabled to be evaluated on configure time using kdelibs installation. The same belongs to KDEPimLibsDependencies.cmake

* source code related
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
#* kioslaves are only working partially --> chehrlic: file, http and ftp are working better now, maybe we still have some unicode problems there.
# kde application state
#* kate - '@' could not be typed in --> chehrlic: fixed for msvc (don't know why it does not work with mingw)
#* konqueror - crashes --> chehrlic: fixed some of them recently
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* <del>umbrello - writing and printing does not work --> rhabacker: fixed</del>
*compiler tools chain issues
# loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.
# There are problems mixing msvc debug and release libraries resulting in runtime errors. One problem seems to be that the FILE structure differs between debug and release libraries. It has to be checked if there are workarounds for all developers.

=== FAQ ===
#Question: snapshot releases with debugging information - New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features
#* Answer rhabacker: saroengles has provided mingw snapshot releases with debug informations on http://www.saroengels.net/kde-windows/. Msvc snapshots are probably not possible because the debug msvc runtime isn't distributable.
#Question: Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information.
#* Answer chehrlic: the official releases are now build in Release mode with debug informations
#Question: Should not the distribution of the file be reduced by keeping a snapshot of all required files on our server(s) - this would make mirroring possible
#* Answer rhabacker: mirroring is possible already now because the installer is able to fetch package online from external sites. If those external packages would not be available in the future it could be easly added to the mirrors.
#Question: is there a central list of mirrors available ?
#* Answer rhabacker: Yes a list of all available mirrors is located on the main kde on windows mirror http://download.cegit.de/kde-windows/mirrors.lst. This file is used by the installer to let the user choosing a mirror.
#Question: We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported?
#* Answer chehrlic: I got a vista license from Adriaan de Groot and after a system upgrade vista will be supported. Until now we should deny any vista support

=== KDE on Windows can be called the first official KDE-own distribution ===

Projects/KDE on Windows/Meetings/Berlin Meeting September 2007

2007-12-04T22:13:00Z

Rhabacker: extracted faq entries

During the last weekend, the KDE on Windows developers conducted their second real life meeting in the Trolltech offices in Berlin Adlershof, incorporating new developers and improving infrastructure. [http://dot.kde.org/1190143020/ Read the dot story for details].

Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

=== TOPICS ===
*mirror related
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows -> there are snapshots available
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
#development installation requires tools having own installers
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...) -> rhabacker: This need some more explanations
#define directory format of the kde mirrors -> TODO

*installer related
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host computer could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
# extend the installer with the following features:
#** <del>update function -> rhabacker: fixed</del>
#** <del>simplified end user interface -> rhabacker: fixed</del>
#** integrity checks (md5 package and file checks) -> rhabacker: started
#** cd/dvd/usb stick installation -> rhabacker: started

*package related
#<del>Insert compiler name into package and manifest file name (msvc, gcc) --> chehrlic: Should be fixed now</del>
* dbus related
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
*build system related
# KDELibsDependencies.cmake contains absolute file pathes. They have to be variabled to be evaluated on configure time using kdelibs installation. The same belongs to KDEPimLibsDependencies.cmake

* source code related
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
#* kioslaves are only working partially --> chehrlic: file, http and ftp are working better now, maybe we still have some unicode problems there.
# kde application state
#* kate - '@' could not be typed in --> chehrlic: fixed for msvc (don't know why it does not work with mingw)
#* konqueror - crashes --> chehrlic: fixed some of them recently
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* <del>umbrello - writing and printing does not work -> rhabacker: fixed</del>
*compiler tools chain issues
# loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.
# There are problems mixing msvc debug and release libraries resulting in runtime errors. One problem seems to be that the FILE structure differs between debug and release libraries. It has to be checked if there are workarounds for all developers.

=== FAQ ===
#Question: snapshot releases with debugging information - New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features
#* Answer rhabacker: saroengles has provided mingw snapshot releases with debug informations on http://www.saroengels.net/kde-windows/. Msvc snapshots are probably not possible because the debug msvc runtime isn't distributable.
#Question: Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information.
#* Answer chehrlic: the official releases are now build in Release mode with debug informations
#Question: Should not the distribution of the file be reduced by keeping a snapshot of all required files on our server(s) - this would make mirroring possible
#* Answer rhabacker: mirroring is possible already now because the installer is able to fetch package online from external sites. If those external packages would not be available in the future it could be easly added to the mirrors.
#Question: is there a central list of mirrors available ?
#* Answer rhabacker: Yes a list of all available mirrors is located on the main kde on windows mirror http://download.cegit.de/kde-windows/mirrors.lst. This file is used by the installer to let the user choosing a mirror.
#Question: We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported?
#* Answer chehrlic: I got a vista license from Adriaan de Groot and after a system upgrade vista will be supported. Until now we should deny any vista support

=== KDE on Windows can be called the first official KDE-own distribution ===

Projects/KDE on Windows/Meetings/Berlin Meeting September 2007

2007-12-04T21:59:28Z

Rhabacker: marked some more todo's as deleted -> some of the todos are in real faq entries

During the last weekend, the KDE on Windows developers conducted their second real life meeting in the Trolltech offices in Berlin Adlershof, incorporating new developers and improving infrastructure. [http://dot.kde.org/1190143020/ Read the dot story for details].

Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

Topics:
*mirror related
#reducing distribution of the file by keeping a snapshot of files on our server(s)
#*this makes mirroring possible
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
#development installation requires tools having own installers
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
#define directory format of the kde mirrors -> TODO
#<del>define central mirror list format -> rhabacker: done</del> see http://download.cegit.de/kde-windows/mirrors.lst

*installer related
#We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported? --> chehrlic: I got a vista license from Adriaan de Groot and after a system upgrade vista will be supported. Until now we should deny any vista support
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host computer could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
# extend the installer with the following features:
#** <del>update function -> rhabacker: fixed</del>
#** <del>simplified end user interface -> rhabacker: fixed</del>
#** integrity checks (md5 package and file checks) -> rhabacker: started
#** cd/dvd/usb stick installation -> rhabacker: started

*package related
#<del>Insert compiler name into package and manifest file name (msvc, gcc) --> chehrlic: Should be fixed now</del>
#<del>snapshot releases with debugging information - New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features.</del> -> rhabacker: saroengles has provided mingw snapshot releases with debug informations on http://www.saroengels.net/kde-windows/. Msvc snapshots are probably nmot possible because the debug msvc runtime isn't distributable.
#<del>Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information.</del> --> chehrlic: the official releases are now build in Release mode with debug informations

* dbus related
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
*build system related
# KDELibsDependencies.cmake contains absolute file pathes. They have to be variabled to be evaluated on configure time using kdelibs installation. The same belongs to KDEPimLibsDependencies.cmake

* source code related
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
#* kioslaves are only working partially --> chehrlic: file, http and ftp are working better now, maybe we still have some unicode problems there.
# kde application state
#* kate - '@' could not be typed in --> chehrlic: fixed for msvc (don't know why it does not work with mingw)
#* konqueror - crashes --> chehrlic: fixed some of them recently
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* umbrello - writing and printing does not work -> rhabacker: fixed
*compiler tools chain issues
# loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.
# There are problems mixing msvc debug and release libraries resulting in runtime errors. One problem seems to be that the FILE structure differs between debug and release libraries. It has to be checked if there are workarounds for all developers.

=== KDE on Windows can be called the first official KDE-own distribution ===

Projects/KDE on Windows/Meetings/Berlin Meeting September 2007

2007-12-04T18:55:14Z

Rhabacker: mark completed topics as deleted

During the last weekend, the KDE on Windows developers conducted their second real life meeting in the Trolltech offices in Berlin Adlershof, incorporating new developers and improving infrastructure. [http://dot.kde.org/1190143020/ Read the dot story for details].

Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

Topics:
*mirror related
#reducing distribution of the file by keeping a snapshot of files on our server(s)
#*this makes mirroring possible
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
#development installation requires tools having own installers
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
#define directory format of the kde mirrors -> TODO
#<del>define central mirror list format -> done see http://download.cegit.de/kde-windows/mirrors.lst</del>

*installer related
#We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported? --> chehrlic: I got a vista license from Adriaan de Groot and after a system upgrade vista will be supported. Until now we should deny any vista support
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host computer could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
# extend the installer with the following features:
#** <del>update function -> rhabacker: fixed</del>
#** <del>simplified end user interface -> rhabacker: fixed</del>
#** integrity checks (md5 package and file checks) -> rhabacker: started
#** cd/dvd/usb stick installation -> rhabacker: started

*package related
#<del>Insert compiler name into package and manifest file name (msvc, gcc) --> chehrlic: Should be fixed now</del>
#snapshot releases with debugging information
#*New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features.
#*Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information. --> chehrlic: the official releases are now build in Release mode with debug informations

* dbus related
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
*build system related
# KDELibsDependencies.cmake contains absolute file pathes. They have to be variabled to be evaluated on configure time using kdelibs installation. The same belongs to KDEPimLibsDependencies.cmake

* source code related
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
#* kioslaves are only working partially --> chehrlic: file, http and ftp are working better now, maybe we still have some unicode problems there.
# kde application state
#* kate - '@' could not be typed in --> chehrlic: fixed for msvc (don't know why it does not work with mingw)
#* konqueror - crashes --> chehrlic: fixed some of them recently
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* umbrello - writing and printing does not work -> rhabacker: fixed
*compiler tools chain issues
# loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.
# There are problems mixing msvc debug and release libraries resulting in runtime errors. One problem seems to be that the FILE structure differs between debug and release libraries. It has to be checked if there are workarounds for all developers.

=== KDE on Windows can be called the first official KDE-own distribution ===

Projects/KDE on Windows/Meetings/Berlin Meeting September 2007

2007-12-04T18:51:17Z

Rhabacker: removed bold printing

During the last weekend, the KDE on Windows developers conducted their second real life meeting in the Trolltech offices in Berlin Adlershof, incorporating new developers and improving infrastructure. [http://dot.kde.org/1190143020/ Read the dot story for details].

Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

Topics:
*mirror related
#reducing distribution of the file by keeping a snapshot of files on our server(s)
#*this makes mirroring possible
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
#development installation requires tools having own installers
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
#define directory format of the kde mirrors -> TODO
#define central mirror list format -> done see http://download.cegit.de/kde-windows/mirrors.lst

*installer related
#We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported? --> chehrlic: I got a vista license from Adriaan de Groot and after a system upgrade vista will be supported. Until now we should deny any vista support
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host computer could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
# extend the installer with the following features:
#** update function -> rhabacker: fixed
#** simplified end user interface -> rhabacker: fixed
#** integrity checks (md5 package and file checks) -> rhabacker: started
#** cd/dvd/usb stick installation -> rhabacker: started

*package related
#Insert compiler name into package and manifest file name (msvc, gcc) --> chehrlic: Should be fixed now
#snapshot releases with debugging information
#*New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features.
#*Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information. --> chehrlic: the official releases are now build in Release mode with debug informations

* dbus related
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
*build system related
# KDELibsDependencies.cmake contains absolute file pathes. They have to be variabled to be evaluated on configure time using kdelibs installation. The same belongs to KDEPimLibsDependencies.cmake

* source code related
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
#* kioslaves are only working partially --> chehrlic: file, http and ftp are working better now, maybe we still have some unicode problems there.
# kde application state
#* kate - '@' could not be typed in --> chehrlic: fixed for msvc (don't know why it does not work with mingw)
#* konqueror - crashes --> chehrlic: fixed some of them recently
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* umbrello - writing and printing does not work -> rhabacker: fixed
*compiler tools chain issues
# loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.
# There are problems mixing msvc debug and release libraries resulting in runtime errors. One problem seems to be that the FILE structure differs between debug and release libraries. It has to be checked if there are workarounds for all developers.

=== KDE on Windows can be called the first official KDE-own distribution ===

Projects/KDE on Windows/Meetings/Berlin Meeting September 2007

2007-12-04T18:48:14Z

Rhabacker: rearranged using main topics

During the last weekend, the KDE on Windows developers conducted their second real life meeting in the Trolltech offices in Berlin Adlershof, incorporating new developers and improving infrastructure. [http://dot.kde.org/1190143020/ Read the dot story for details].

Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

Topics:
*mirror related
#reducing distribution of the file by keeping a snapshot of files on our server(s)
#*this makes mirroring possible
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
#development installation requires tools having own installers
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
#define directory format of the kde mirrors -> TODO
#define central mirror list format -> done see http://download.cegit.de/kde-windows/mirrors.lst

*installer related
#We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported? --> chehrlic: I got a vista license from Adriaan de Groot and after a system upgrade vista will be supported. Until now we should deny any vista support
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host computer could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
# extend the installer with the following features:
#** '''update function -> rhabacker: fixed'''
#** '''simplified end user interface -> rhabacker: fixed'''
#** '''integrity checks (md5 package and file checks) -> rhabacker: started'''
#** '''cd/dvd/usb stick installation -> rhabacker: started'''

*package related
#Insert compiler name into package and manifest file name (msvc, gcc) --> chehrlic: Should be fixed now
#snapshot releases with debugging information
#*New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features.
#*Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information. --> chehrlic: the official releases are now build in Release mode with debug informations

* dbus related
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
*build system related
# KDELibsDependencies.cmake contains absolute file pathes. They have to be variabled to be evaluated on configure time using kdelibs installation. The same belongs to KDEPimLibsDependencies.cmake

* source code related
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
#* kioslaves are only working partially --> chehrlic: file, http and ftp are working better now, maybe we still have some unicode problems there.
# kde application state
#* kate - '@' could not be typed in --> chehrlic: fixed for msvc (don't know why it does not work with mingw)
#* konqueror - crashes --> chehrlic: fixed some of them recently
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* '''umbrello - writing and printing does not work -> rhabacker: fixed'''
#* ...
*compiler tools chain issues
# loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.
# There are problems mixing msvc debug and release libraries resulting in runtime errors. One problem seems to be that the FILE structure differs between debug and release libraries. It has to be checked if there are workarounds for all developers.

=== KDE on Windows can be called the first official KDE-own distribution ===

Projects/KDE on Windows/Meetings/Berlin Meeting September 2007

2007-12-01T21:36:01Z

Rhabacker: added some completed todo's, added cmnake bug

During the last weekend, the KDE on Windows developers conducted their second real life meeting in the Trolltech offices in Berlin Adlershof, incorporating new developers and improving infrastructure. [http://dot.kde.org/1190143020/ Read the dot story for details].

==Notes==
{{improve}}

Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

Topics:
#reducing distribution of the file by keeping a snapshot of files on our server(s)
#*this makes mirroring possible
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
#development installation requires tools having own installers
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
#We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported?
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host conuter could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
#format of the kde mirrors:
#*TODO
#Insert compiler name into package and manifest file name (msvc, gcc)
#snapshot releases with debugging information
#*New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features.
#*Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information.
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
# win32 issues with the cmake build system
#* KDELibsDependencies.cmake contains absolute file pathes. They have to be variabled to be evaluated on configure time using kdelibs installation. The same belongs to KDEPimLibsDependencies.cmake
# install system topics:
#* it is planned to evaluate the microsoft windows installer for releasing kde windows application. -> noone has taken this job
#* if msi is not usable the kdewin-installer should be extended with the following features:
#** '''update function -> fixed'''
#** '''simplified end user interface ->fixed'''
#** '''integrity checks (md5 package and file checks) -> started'''
#** '''cd/dvd/usb stick installation -> started'''
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
#* kioslaves are only working partially
# kde application state
#* kate - '@' could not be typed in
#* konqueror - crashes
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* '''umbrello - writing and printing does not work -> fixed'''
#* ...
#compiler tools chain issues
#* loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.
#* There are problems mixing msvc debug and release libraries resulting in runtime errors. One problem seems to be that the FILE structure differs between debug and release libraries. It has to be checked if there are workarounds for all developers.

=== KDE on Windows can be called the first official KDE-own distribution ===

ISV/Roadmap (de)

2007-11-23T00:18:56Z

Rhabacker: /* KDE Entwicklung */

== KDE stabile Version ==
== KDE Entwicklung ==

Die aktuelle KDE Entwicklung konzentriert sich auf KDE 4, welche eine wichtige Version sein wird. Es wird verschiedene neue Funktionen und neue API's und Frameworks enthalten und aus diesem Grund die API Kompatitibilität durchbrechen.

In der gleichen Zeit laufen jedoch verschiedene Bemühungen in der Community die Portierung von Anwendungen nach KDE4 sehr einfach zu machen.

Die Roadmap für KDE 4 enthält die [[Schedules/KDE_4.0_Release_Schedule| Versionsplanung]] und die [http://developer.kde.org/development-versions/kde-4.0-features.html geplanten Erweiterungen].

== Teilprojekte ==

einige KDE Teilprojekte haben ihre eigene Roadmap:
* [http://multimedia.kde.org/roadmap.php KDE Multimedia Projekt] - unterstützt durch [http://phonon.kde.org/ Phonon], eine neue Multimedia API.
* [http://koffice.kde.org/developer/ KOffice] - eine freie, integrierte Office suite für KDE.

[[Category:ISV]]

ISV/Roadmap (de)

2007-11-23T00:17:20Z

Rhabacker: /* KDE Entwicklung */

== KDE stabile Version ==
== KDE Entwicklung ==

Die aktuelle KDE Entwicklung konzentriert sich auf KDE 4, welche eine wichtige Version sein wird. Es wird verschiedene neue Funktionen und neue API's und Frameworks enthalten und aus diesem Grund die API Kompatitibilität durchbrechen.

In der gleichen Zeit laufen jedoch verschiedene Bemühungen in der Community die Portierung von Anwendungen nach KDE4 sehr einfach zu machen.

Die Roadmap für KDE 4 ist unterteilt in die [[Schedules/KDE_4.0_Release_Schedule| Versionsplanung]] und die [http://developer.kde.org/development-versions/kde-4.0-features.html geplanten Erweiterungen].

== Teilprojekte ==

einige KDE Teilprojekte haben ihre eigene Roadmap:
* [http://multimedia.kde.org/roadmap.php KDE Multimedia Projekt] - unterstützt durch [http://phonon.kde.org/ Phonon], eine neue Multimedia API.
* [http://koffice.kde.org/developer/ KOffice] - eine freie, integrierte Office suite für KDE.

[[Category:ISV]]

ISV (de)

2007-11-23T00:16:11Z

Rhabacker: initial translation

__NOTOC__ __NOEDITSECTION__
{{Template:I18n/Language Navigation Bar|ISV}}
Willkommen im Bereich für unabhängige Softwarehersteller.

Diese Seite gibt einen Überblick über KDE's Entwicklerseiten insbesondere für unabhängige Softwarehersteller (ISVs), die entweder interessiert sind die K Desktop Umgebung für ihre tägliche Arbeit einzusetzen oder ihre Software nahtlos in KDE zu integrieren.



Es gibt verschiedene Bereiche, die für Sie interessant sein könnten:

<table width="100%" style="border-collapse:separate; border-spacing:10px;">
<tr>
<td align="center" style="border: solid 1px #1e90ff; background-color:#f8f8ff; padding:0 1em 1em 1em;">
<h3 style="text-align:center;">[[ISV/Why use KDE|Warum KDE einsetzen?]]</h3>
Lesen Sie mehr darüber, warum KDE die richtige Auswahl ist. </td>
<td align="center" style="border: solid 1px #1e90ff; background-color:#f8f8ff; padding:0 1em 1em 1em;">
<h3 style="text-align:center;">[[ISV/Support|Unterstützung erhalten]]</h3>
Erfahren Sie mehr darüber, wie Sie Unterstützung erhalten.</td>
</tr>
<tr>
<td align="center" style="border: solid 1px #1e90ff; background-color:#f8f8ff; padding:0 1em 1em 1em;">
<h3 style="text-align:center;">[[ISV/Licensing|Lizenzierung]]</h3>
Lesen Sie mehr über die von KDE verwendeten Lizenzen.</td>
<td align="center" style="border: solid 1px #1e90ff; background-color:#f8f8ff; padding:0 1em 1em 1em;">
<h3 style="text-align:center;">[[ISV/Developer Information|Werkzeuge und Bibliotheken]]</h3>
Erfahren Sie mehr über nützliche Werkzeuge und Bibliotheken.</td>
</tr>
<tr>
<td align="center" style="border: solid 1px #1e90ff; background-color:#f8f8ff; padding:0 1em 1em 1em;">
<h3 style="text-align:center;">[[ISV/KDE Community|KDE Community]]</h3>
Erfahren Sie mehr über die ''treibenden Kräfte'' hinter KDE.</td>
<td align="center" style="border: solid 1px #1e90ff; background-color:#f8f8ff; padding:0 1em 1em 1em;">
<h3 style="text-align:center;">[http://enterprise.kde.org/bizcase/ Erfolgsstories]</h3>
Lesen Sie mehr über erfolgreiche KDE Einführungen.</td>
</tr>
<tr>
<td align="center" style="border: solid 1px #1e90ff; background-color:#f8f8ff; padding:0 1em 1em 1em;" colspan="2">
<h3 style="text-align:center;">[[ISV/Roadmap|Roadmap]]</h3>
Erfahren Sie mehr über Versionen und geplante Erweiterungen.</td>
</tr>
</table>



[[Category:ISV]]

ISV/Support (de)

2007-11-23T00:03:30Z

Rhabacker: added Community Support

== Community Support ==

Es gibt Mailinglisten für fast alle KDE Bereiche. Eine Übersicht dieser Listen ist [http://www.kde.org/mailinglists/ hier] zu finden.

Speziell die [http://mail.kde.org/mailman/listinfo/kde-devel kde-devel] Mailingliste ist für jeden interessant der sich mit der Entwicklung von KDE basierten Anwendungen oder KDE selber beschäftigt.

Bitte denken Sie daran, das diese Listen weitgehend von Freiwilligen gesteuert werden - Anforderungen und abscheifende Themen werden manchmal mit Zynismus and Ablehnung beantwortet, während technische Fragen und echte Kritik in der Regel schnell und gut beantwortet werden.

== Kommerzieller Support ==

Wenn Sie garantierte Antwortzeiten und Business Level Support benötigen, gibt es verschiedene Auswahlmöglichkeiten:

[http://www.trolltech.com Trolltech] liefert [http://www.trolltech.com/support kommerziellen Support ] für Ihr [http://www.trolltech.com/products/qt Qt-Toolkit], auf das KDE basiert.

Eine Liste von Firmen die KDE unterstützen, erhalten Sie in KDE's [http://enterprise.kde.org/bizdir/ Firmenverzeichnis].

[[Category:ISV]]

ISV/Support (de)

2007-11-22T23:52:36Z

Rhabacker: added commercial support

== Kommerzieller Support ==

Wenn Sie garantierte Antwortzeiten und Business Level Support benötigen, gibt es verschiedene Auswahlmöglichkeiten:

[http://www.trolltech.com Trolltech] liefert [http://www.trolltech.com/support kommerziellen Support ] für Ihr [http://www.trolltech.com/products/qt Qt-Toolkit], auf das KDE basiert.

Eine Liste von Firmen die KDE unterstützen, erhalten Sie in KDE's [http://enterprise.kde.org/bizdir/ Firmenverzeichnis].

[[Category:ISV]]

ISV/Roadmap (de)

2007-11-22T23:42:28Z

Rhabacker: added sub-projects

== KDE stabile Version ==
== KDE Entwicklung ==

Die aktuelle KDE Entwicklung konzentriert sich auf KDE 4, welche eine wichtige Version sein wird. Es wird verschiedene neue Funktionen und neue API's und Frameworks enthalten und aus diesem Grund die API Kompatitibilität durchbrechen.

In der gleichen Zeit laufen jedoch verschiedene Bemühungen in der Community die Portierung von Anwendungen nach KDE4 sehr einfach zu machen.

Die Roadmap für KDE 4 ist unterteilt in die [[Schedules/KDE_4.0_Release_Schedule| Releaseplanung]] und die [http://developer.kde.org/development-versions/kde-4.0-features.html Erweiterungsplanung].

== Teilprojekte ==

einige KDE Teilprojekte haben ihre eigene Roadmap:
* [http://multimedia.kde.org/roadmap.php KDE Multimedia Projekt] - unterstützt durch [http://phonon.kde.org/ Phonon], eine neue Multimedia API.
* [http://koffice.kde.org/developer/ KOffice] - eine freie, integrierte Office suite für KDE.

[[Category:ISV]]

ISV/Roadmap (de)

2007-11-22T23:38:43Z

Rhabacker: initial translation

ISV/Licensing (de)

2007-11-22T23:26:13Z

Rhabacker: minor restyle

=== Licensing ===
Eine oft gestellte Frage ist: ''Kann ich KDE zur Entwicklung von kommerziellen Anwendungen verwenden?'' - '''Ja, es ist möglich kommerzielle Anwendungen für KDE zu entwicklen'''. KDE's Basisbibliotheken {{path|kdelibs}} und {{path|kdepimlibs}}, ebenso wie die KOffice Bibliotheken und andere wichtige Anwendungen sind unter der [http://www.gnu.org/copyleft/lesser.html LGPL] lizenziert. Die [http://www.gnu.org/copyleft/lesser.html LGPL] erlaubt das Linken von nicht quelloffenen Anwendungen gegen diese Bibliotheken. Allerdings ist für die Entwicklung von nicht quelloffenen Anwendungen eine [http://www.trolltech.com/products/qt/licenses Qt Developer Lizenz] erforderlich.

[[Category:ISV]]

ISV/Licensing (de)

2007-11-22T23:24:55Z

Rhabacker: added some wiki tags

=== Licensing ===
Eine oft gestellte Frage ist:

''Kann ich KDE zur Entwicklung von kommerziellen Anwendungen verwenden?'' - '''Ja, es ist möglich kommerzielle Anwendungen für KDE zu entwicklen'''.

KDE's Basisbibliotheken {{path|kdelibs}} und {{path|kdepimlibs}}, ebenso wie die KOffice Bibliotheken und andere wichtige Anwendungen sind unter der [http://www.gnu.org/copyleft/lesser.html LGPL] lizenziert. Die [http://www.gnu.org/copyleft/lesser.html LGPL] erlaubt das Linken von nicht quelloffenen Anwendungen gegen diese Bibliotheken. Allerdings ist für die Entwicklung von nicht quelloffenen Anwendungen eine [http://www.trolltech.com/products/qt/licenses Qt Developer Lizenz] erforderlich.

[[Category:ISV]]

ISV/Licensing (de)

2007-11-22T23:18:46Z

Rhabacker: deutsche Übersetzung

Eine oft gestellte Frage ist: Kann ich KDE zur Entwicklung von kommerziellen Anwendungen verwenden ? - Ja, es ist möglich kommerzielle Anwendungen für KDE zu entwickeln. KDE's Basisbibliotheken kdelibs und kdepimlibs, ebenso wie die KOffice Bibliotheken und andere wichtige Anwendungen sind unter der LGPL lizenziert. Die LGPL erlaubt das Linken von nicht quelloffenen Anwendungen gegen diese Bibliotheken. Allerdings ist für die Entwicklung von nicht quelloffenen Anwendungen eine Qt Developer Lizenz erforderlich.

Development/Tools

2007-09-22T21:32:34Z

Rhabacker: added msvc express

This section contains information about tools for KDE development.

== Debugging and Analysis ==
A list of tools which are used to analyze a program. This includes debuggers and profilers, for instance.

; Valgrind
: [[/Valgrind|Valgrind]] helps to find memory leaks and uninitialized memory blocks. Additional features are a profiler and more. Valgrind is one of the most important development tools!

; The GNU Project Debugger (GDB)
: [http://sources.redhat.com/gdb/ GDB] helps in debugging source code. As GDB evolved over time it is recommended to use version 6.x. Graphical frontends are available (see below). See also the debugging tutorial [[../Tutorials/Debugging/Debugging with GDB|Debugging with GDB]].

; KDbg
: [http://www.kdbg.org/ KDbg] is a graphical user interface to GDB, which is able to set breakpoints, step through the code etc.

== Development Tools ==
; KDevelop
: [http://www.kdevelop.org KDevelop] is an excellent IDE for developing KDE and Qt C++ applications. It includes a an integrated debugger, a powerful editor with syntax highlighting, a ''Project wizard'' to create applications from templates, the automake/autoconf gunk, and even the class documentation. Further details can also be found in the [http://kdevelop.org/mediawiki/index.php/Main_Page KDevelop wiki].

:Instructions on how to use KDevelop with KDE 4 applications is available at [[Getting_Started/Set_up_KDE_4_for_development#KDevelop|this page]]

; Qt Designer
: With Trolltechs [http://www.trolltech.com/products/qt/features/designer Qt Designer] it is easy to layout user interfaces like buttons and checkboxes. Additional features are undo/redo, checking accelerator conflicts etc. Qt Designer allows even non-programmers to help design KDE dialogs. Further details can be found in the tutorial [[Development/Tutorials/Using_Qt_Designer|Using Qt Designer]] and in the [http://doc.trolltech.com/4.2/designer-manual.html Qt documentation].

; MS Visual Studio® Express 2005 IDE (Windows only)
: Visual C++® 2005 Express Edition [http://www.microsoft.com/germany/msdn/vstudio/products/express/visualc/default.mspx] is the free version of the Microsoft Visual Studio 2000 compiler from Microsoft, which is official supported by Trolltech since QT 4.3.2 and a choice for compiling qt and kde applications on windows.

== Internationalization (i18n) Tools ==

; KBabel
: [http://kbabel.kde.org/ KBabel] is a set of tools for editing and managing gettext PO files. Its main part is a powerful and comfortable PO file editor which features full navigation capabilities, full editing functionality, possibility to search for translations in different dictionaries, spell and syntax checking, showing diffs and many more.

: Also included is a "Catalog Manager", a file manager view which helps keeping an overview of PO files. Last but not least it includes a standalone dictionary application as an additional possibility to access KBabel's powerful dictionaries. KBabel will help you to translate fast and also keep consistent translations.

; Dr. Klash
: This little utility, once activated, can present a report about conflicting shortcuts in menus. Not only this is helpful for translators but also for developers. A little hand editing of {{path|`kde-config --localprefix`/share/config/kdeglobals}} activates this feature:

<code ini>
[Development]
CheckAccelerators=F12
AutoCheckAccelerators=false
AlwaysShowCheckAccelerators=false
</code>

: Now pressing F12 will show a dialog containing which accelerators in the currently focussed interface conflict and provide suggestions for new accelerators. If no accelerators conflict or Dr. Klash has nothing to suggest, no popup dialog will not be displayed at all.

: With <tt>AutoCheckAccelerators</tt> enabled the dialog will popup automatically if a conflict exists and <tt>AlwaysShowCheckAccelerators</tt> can force the dialog to always popup even if there are no conflicts to report.

; The XX language
: This helper language serves as a debugging aid for people finding untranslated strings in applications. If you start your application with the ``xx'' locale, all translated strings will appear with x's. First you have to check out these ``translations'' from l10n/xx and install them.

: After you've built l10n/xx and installed it, run your application using the XX locale. This can be done by launching it from the command line like this:

> KDE_LANG=xx kspread

: This will start KSpread using the XX locale no matter what your current language setting is. Look for strings that do not have the x's in them. If x's are missing from a string, it could be due to missing i18n calls or even missing or incorrectly generated .pot files. Consult the i18n tutorials for further information.

: When checking for untranslated strings, be sure to check all the WhatsThis help and tooltips.

=== Examining .po files ===

You can look at the translated .po files to see if a string is present and has been translated. For example, here's a portion of {{path|l10n/de/messages/kdebase/konqueror.po}}:

#: konq_mainwindow.cc:3707 konq_tabs.cc:84
msgid "&New Tab"
msgstr "Neues &Unterfenster"

The string to be translated is given on the msgid line. The translated string is on the msgstr line. Notice that the exact same string to translate came from {{path|konq_mainwindow.cc}} and also from {{path|konq_tabs.cc}}. This saves the translators from having to translate the same identical string twice.

You can also use KBabel to examine {{path|.po}} files. KBabel is part of the kdesdk module.

{{note|More information on writing and translating documentation can be found on [http://l10n.kde.org/ the l10n project site].}}

== Helper Tools ==

; [[/Using kde-config|Get information about KDE's installation - kde-config]]
: The tool kde-config helps to find out more about a KDE installation.

; [[/Using kfmclient|Driving Konqueror From Scripts - kfmclient]]
: kfmclient is a small tool to communicate with Konqueror.

;[[/Using kconf_update|Updating User Configuration Files - kconf_update]]
: kconf_update is a tool designed to update config files.

== Quality Assurance ==

; Continuous Building - Dashboard
: [http://developer.kde.org/~dirk/dashboard/ all kde modules on Dirk's dashboard]
: [http://public.kitware.com/dashboard.php?name=kde kdelibs on kitware]

; [http://englishbreakfastnetwork.org/ English Breakfast Network] - Static Analysis
: [http://www.englishbreakfastnetwork.org/krazy/ Krazy ] - Code Analysis, [[Development/Tutorials/Code_Checking|Usage Tutorial]]
: [http://www.englishbreakfastnetwork.org/apidocs/ APIDOX] - API Documentation Statistics
: [http://www.englishbreakfastnetwork.org/sanitizer/ Sanitizer] - DocBook Checker
: [http://www.englishbreakfastnetwork.org/usability/ Usability Checks]

Development/Tutorials/Debugging/Debugging on MS Windows

2007-09-22T21:19:41Z

Rhabacker: added kioslave debugging

=General Hints=
==Debugging with DebugView==
Debug messages (logs) generated by kDebug() and kWarning() are not visible on MS Windows unless application is compiled in so-called CONSOLE subsystem. To show these messages also in WINDOWS subsystem, you can use DebugView tool, coming from SysInternals (currently acquired by Microsoft). The tool offers searching in logs, filtering and saving them to file.

→ [http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx More informations]
==Debugging kioslaves==
kioslaves on windows are started by klauncher (or kio) as separate kioslave processes. The kioslave executable then loads the related kioslave dll dynamically.

To debug kioslaves set the KDE_SLAVE_DEBUG_WAIT environment variable to the name of the kioslave to debug (for example 'file' for the kio_file slave) and restart klauncher. If the requested kioslave is requested the next time, a debugger will be started and attached to the kioslave process immediatly before the kio_slave 'kdemain' function.

On mingw platform gdb is launched and connected to the kioslave process, on msvc platforms the currently install just-in-time-debugger is used. This may be msvc vc2005 ide or the windbg debugger [http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx]. The latter could be set as jit-debugger by running windbg -I.

You may inspect kioslave sources [http://lxr.kde.org/source//KDE/kdelibs/kinit/kioslave.cpp] for more informations.

= MS Visual Studio hints =

== Using MS Visual Studio environment for just debugging ==

Let's assume you're using command line tools (typically SCons) and want to use MS Visual Studio environment for just debugging.
You don't need to create msvc project for your KDE application to be able to start debugging.

* compile and working executable version of your appliation (compiled in debug mode)
* run msvc environment
* execute ''File->Open project''
* pick your exe file in the file window
* you can set command line arguments as usual, by pick ''Project->...Properties'' command and enter all of them it in ''Command Arguments'' field
* if you have libraries placed in other directories than your application's .exe file, and you want to step into these libraries' source code while debugging, pick ''Project->...Properties'' command and enter paths to these directories in ''Symbol Path'' field
* hit F5 to run the application start the application or F10 to start step by step
* all debugging functions like setting breakpoints will be available, so you can open source code in the integrated editor and press F9 where needed
* you can even edit your source code but to compile it, do it with your external, command line tools. You cannot compile the application in the msvc environment because you have not defined a project file
* before compiling your application, stop debugging session to unlock binaries; no need to close msvc window
* after compilation you can start debugging again
* on exit you will be asked to save .sln file (so-called ''solution file'') with your debugging session -- do it and you will be able just to click the .sln file to start your debugging again
* it's recommended to save the .sln file in the .exe file directory
* next time you will run msvc environment, you can see name of your application's .sln file in ''File->Recent Projects'' submenu - you can click it to load your debugging session

== Attaching to running application ==

If you have your application is already running, you can attach to it and then start debugging.

* run msvc environment
* execute ''Debug->processes''
* select your from the processes list and click "Attach..."
* msvc environment will load your .sln file if it exists in the same directory as the .exe file, so your breakpoints set in previous session will be active again
* your program will stop on any breakpoint you have set

== One-step attaching to running application ==
You can create a macro that automates the task. See [http://blogs.msdn.com/jimgries/archive/2005/11/30/498264.aspx].

== Memory Values ==
If you are using the debug heap, memory is initialized and cleared with special values. Most interesting values are:
* 0xCDCDCDCD - Allocated in heap, but not initialized
* 0xDDDDDDDD - Released heap memory.
* 0xFDFDFDFD - "NoMansLand" fences automatically placed at boundary of heap memory. Should never be overwritten. If you do overwrite one, you're probably walking off the end of an array.
* 0xCCCCCCCC - Allocated on stack, but not initialized
See also: [http://www.samblackburn.com/wfc/technotes/WTN006.htm]

= MinGW hints =

* Dr. Mingw - Just in Time Debugger [http://jrfonseca.planetaclix.pt/projects/gnu-win32/software/drmingw/]
* Debugging Qt programs on Windows [http://lists.trolltech.com/qt-interest/2005-08/thread01124-0.html]

[[Category:MS Windows]]

Talk:Installing third party softwares in terminal/Build/KDE4/Windows

2007-09-18T10:09:40Z

Rhabacker: msvc debug/relase mixing problem

{{improve}}

==KDE-Windows Meeting: Notes==
Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

Topics:
#reducing distribution of the file by keeping a snapshot of files on our server(s)
#*this makes mirroring possible
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
#development installation requires tools having own installers
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
#We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported?
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host conuter could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
#format of the kde mirrors:
#*TODO
#Insert compiler name into package and manifest file name (msvc, gcc)
#snapshot releases with debugging information
#*New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features.
#*Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information.
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
# win32 issues with the cmake build system (TODO: list the issues)
# install system topics:
#* it is planned to evaluate the microsoft windows installer for releasing kde windows application.
#* if msi is not usable the kdewin-installer should be extended with the following features:
#**update function
#**simplified end user interface
#**integrity checks (md5 package and file checks)
#**cd/dvd/usb stick installation
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
#* kioslaves are only working partially
# kde application state
#* kate - '@' could not be typed in
#* konqueror - crashes
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* umbrello - writing and printing does not work
#* ...
#compiler tools chain issues
#* loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.
#* There are problems mixing msvc debug and release libraries resulting in runtime errors. One problem seems to be that the FILE structure differs between debug and release libraries. It has to be checked if there are workarounds for all developers.

=== KDE on Windows can be called the first official KDE-own distribution ===

Talk:Installing third party softwares in terminal/Build/KDE4/Windows

2007-09-18T09:42:16Z

Rhabacker: added gdb notes

{{improve}}

==KDE-Windows Meeting: Notes==
Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

Topics:
#reducing distribution of the file by keeping a snapshot of files on our server(s)
#*this makes mirroring possible
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
#development installation requires tools having own installers
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
#We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported?
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host conuter could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
#format of the kde mirrors:
#*TODO
#Insert compiler name into package and manifest file name (msvc, gcc)
#snapshot releases with debugging information
#*New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features.
#*Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information.
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
# win32 issues with the cmake build system (TODO: list the issues)
# install system topics:
#* it is planned to evaluate the microsoft windows installer for releasing kde windows application.
#* if msi is not usable the kdewin-installer should be extended with the following features:
#**update function
#**simplified end user interface
#**integrity checks (md5 package and file checks)
#**cd/dvd/usb stick installation
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
#* kioslaves are only working partially
# kde application state
#* kate - '@' could not be typed in
#* konqueror - crashes
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* umbrello - writing and printing does not work
#* ...
#compiler tools chain issues
#* loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.

=== KDE on Windows can be called the first official KDE-own distribution ===

Talk:Installing third party softwares in terminal/Build/KDE4/Windows

2007-09-17T06:07:55Z

Rhabacker: kdelibs/kde application state

{{improve}}

==KDE-Windows Meeting: Notes==
Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

Topics:
#reducing distribution of the file by keeping a snapshot of files on our server(s)
#*this makes mirroring possible
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
#development installation requires tools having own installers
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
#We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported?
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host conuter could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
#format of the kde mirrors:
#*TODO
#Insert compiler name into package and manifest file name (msvc, gcc)
#snapshot releases with debugging information
#*New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features.
#*Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information.
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
# win32 issues with the cmake build system (TODO: list the issues)
# install system topics:
#* it is planned to evaluate the microsoft windows installer for releasing kde windows application.
#* if msi is not usable the kdewin-installer should be extended with the following features:
#**update function
#**simplified end user interface
#**integrity checks (md5 package and file checks)
#**cd/dvd/usb stick installation
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
#* kioslaves are only working partially
# kde application state
#* kate - '@' could not be typed in
#* konqueror - crashes
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* umbrello - writing and printing does not work
#* ...

=== KDE on Windows can be called the first official KDE-own distribution ===

Talk:Projects/NamingTheWiki

2007-01-24T09:21:52Z

Rhabacker: /* Name Suggestions */

= Name Suggestions =

: '''TechZone''': I like this name for several reasons: They give a clue on the pages purpose, are not biased towards either devs or system integrators, and leave room to brand them (Question to Promo team: is that a good idea). Please note that we will redirect developer.kde.org to this domain, so people who are looking for this domain straight will still end up in the right place. The word ''Base'' in '''Tech''Base''''' was criticized as being meaningless plus there is already a domain called devbase.com, and I want to stay out of tm issues. --[[User:Danimo|Danimo]] 01:42, 19 January 2007 (CET)

::I agree with these ideas. Regarding not biasing articles, that imho is a particularly important idea. While the major apps/suites (KOffice, Kontact, Kolab, Kopete, etc) are taken care of, there is an incredibly vast set of vertical markets untouched by KDE. These markets are not often discussed, yet make up a rather significant developer market. Examples would be software to manage a dental office, consulting firm, accounting firm, millwork companies, etc. Those working on this won't necessarily fall into a neat and clean category, so I'd consider this advantageous. --[[User:CuCullin|CuCullin]] 16:21, 19 January 2007 (CET)

:: I don't think the word base is meaningless it all. At least for English speakers it carries both the idea of a canonical location ("home base") and solidity (base and foundation can be used interchangeably in many cases) --[[User:Aseigo|Aseigo]] 00:15, 20 January 2007 (CET)

:: In my opinion, TechZone sounds like it's trying to be 'cool'. The word 'zone' sounds like it describing something much less well defined than, say, 'base' and so makes it sound very vague. --[[User:Milliams|milliams]] 00:42, 20 January 2007 (CET)

: '''TechBase''': I like this name because we already call the site that elsewhere, so there's some continuity. It also is representative of the fact that this site (as i understand it) is meant to be the base of technical information for and about KDE on the interwebs. There is a company called TechBase International"KDE Technical Reference" which does things completely unrelated to KDE so maybe there's some tm issues, but I doubt it. Perhaps we might want to have a thing where the full name of the site is ''KDE Technical Base'' and we just call it ''TechBase'' for short --[[User:Mattr|Mattr]] 02:22, 19 January 2007 (CET)

:: I like the Word 'base'. For exactly the two reasons aseigo mentioned (under TechZone). Maybe officially naming the site "Technology Base" and just having the URL as techbase.kde.org? However, I'm sure that everyone would just refer to it as 'TechBase' anyway --[[User:Milliams|milliams]] 00:42, 20 January 2007 (CET)

: '''TechCenter''': Similar to TechZone and TechBase. Maybe also similar to the [http://www.qtcentre.org/ qt-centre].

: '''TechZone and TechBase ''': I feel that "tech[base|zone]"is a poor choice of name - it's a made up word and as such will age rapidly. It's a lowest common denominator, meaningless choice. The KDE project is bigger than that and would be better served by clean, functional terms such as "KDE Technical Reference", "KDE Technical Resource". If it has to be one word, "Learn" or "Platform". --[[User:Bille|Bille]] 23:18, 17 January 2007 (CET)

:: You ''feel'' it is a lowest common denominator, meaningless choice. I ''feel'' otherwise. Let's try and stay away from communicating things as if they are universal truths when they are actually subjective reflections. "Learn" might be an interesting name; "Platform" would make it confusing for me to talk about the KDE platform vs the website called Platform; "Technical Reference" would be very hard to market. One of the sides of this that I have to deal with that probably most others don't is representing it to the public during interviews, in press materials, when giving presentations at conferences, etc... So for me the marketability of the term is also important, as are the clarity and accuracy issues you raise in your comment here. --[[User:Aseigo|Aseigo]] 00:15, 20 January 2007 (CET)

::: Aaron, I knew what ''feel'' means before you italicised it. I'm not enough of a solipsist to confuse my feelings with universal truths. Just sharing my subjective opinion here. Why do you feel "KDE Technical Reference/Resource" is hard to market? IMO it says exactly what the site does, has the KDE brand and can be communicated in any language. After all, what you'd be marketing is KDE, with the message that KDE has comprehensive technical resources - you'd not be marketing eg our "KDE Technical Reference" site vs. some competing "Larry's KDE Experts Forum" --[[User:Bille|Bille]] 10:23, 20 January 2007 (CET)

:::: I feel "KDE Technical Reference/Resource" is hard to market because it has about as much zing to it as a colon exam. It's not easy to say (6 syllables, even) and unless you prepend "KDE" to it it's not recognizable since it's a generic term. "Technical reference" could apply to any number of things within KDE, so this would be THE Technical Reference website. Contrast with "TechBase", "TechZone", "WallZomper", etc.. easy to say, compact, not an ambiguous noun so further qualifiers ('the', 'KDE', 'website') aren't necessary once it is introduced into the vernacular. These short names also lend to being the domain name of the site, unless technicalreference.kde.org seems like a good idea to you? Describing the site to people as the KDE technical reference is probably a clear way of doing it, but a name and a description are not the same thing --[[User:Aseigo|Aseigo]] 22:56, 20 January 2007 (CET)

:: The thing I don't like about this is that it ''is'' just a noun like "web page". This site has a purpose, and I think the name should promote that purpose - otherwise, there would be no limitation on any KDE content going on here. Users might add application manuals, or e.V. info could go on here, whatever. That would only create confusion imho. --[[User:CuCullin|CuCullin]] 16:21, 19 January 2007 (CET)

:: Isn't the ''KDE wiki'' wiki.kde.org? That's already taken. Besides, we still need a name on the right of the KDE logo. "KDE Technical Reference" or similar titles are better than "KDE wiki". --[[User:Dhaumann|Dhaumann]] 16:56, 19 January 2007 (CET)

::: I thought the old wiki.kde.org, now '''redundant''' (look at its TOC), is pretty much a history now when the new ''developernew'' wiki appeared, and as Mediawiki not only contains predictable hyperlinks and good interwiki and templates support, but its engine is far superior to the old one and constantly improved. At least I consider moving all of my content out of it elsewhere. There's no day when I did not have problems with its tikiwiki's configuration, html layout and speed. Application manuals? The old wiki.kde.org does not contain this kind of stuff, so history shows it's not a problem. Every larger KDE apps can host its own wiki, as we know in case of KOffice, Kexi, KDevelop, KDEWebDev family, etc. So ''Wiki'' is still my favourite term. Regarding "KDE Technical Reference", it sounds a bit serious. There's similar very popular (100x more according to google) term: '''"Knowledge Base"'''. Personally I have no problem with having wiki.kde.org (because it's as short as possible) and "Knowledge Base" title. --[[User:Jstaniek|jstaniek]] 18:54, 19 January 2007 (CET)

:::: Part of that, imho, is that wiki.kde.org (and TikiWiki) isn't as friendly as MediaWiki. Perhaps it should be wiki.kde.org, and simply have a nice listing somewhere on this site discussing what does and does not belong on here, just to direct content that may be more appropriate elsewhere. Personally, I like a more descriptive name because I think it separates this wiki from others. --[[User:CuCullin|CuCullin]] 19:49, 19 January 2007 (CET)

:::: '''Knowledge base''' is an interesting name posibility IMHO. It's a bit on the dry side but it is accurate. My concern is that it might cast the net too wide and we'd end up with scope creep, e.g. becoming a place for user information. I don't think we should try and cater to absolutely everyone with this site, and a more focussed name might help with that. --[[User:Aseigo|Aseigo]] 00:15, 20 January 2007 (CET)

:: "wiki" is not something I could market (see my comment to Bille's response on this matter for more on this point). "Wiki" does not speak directly to the target audiences due to being a generic noun/verb, nor does it say what is on the site since a wiki can contain anything. It's also already taken anyways =) --[[User:Aseigo|Aseigo]] 00:15, 20 January 2007 (CET)

:: "Wiki" only describes what it is, not what it does or what it's for. In a way wiki is synonymous with "site". And we'd never think of calling this "KDE Site" yet that conveys just as much information to the reader. --[[User:Milliams|milliams]] 00:42, 20 January 2007 (CET)

: Do you also mean platform.kde.org or reference.kde.org then? We are searching for both a readable name and a subdomain name. --[[User:Dhaumann|Dhaumann]] 16:56, 19 January 2007 (CET)

'''Conquer KDE''': The name should reflect the whole KDE project as (the way I see it) it tries to group everything KDE will be doing in the future to one wiki.

As I read on the mailing list, we are trying to promote KDE to the OSV and to the system admins as well so the Slogan would be a nice way to name the wiki.--[[User:Imagine|Imagine]] 19:11, 19 January 2007 (CET)

: While I'm pretty sure this isn't what you were trying to say, I'd like to make it clear that we're not actually trying to group ''everything'' KDE will be doing, just everything that is a) technical information and b) relevant to those who create things with KDE technology. '''Conquer KDE''' is a neat slogan, but i'm not sure if it translates to usage as a noun: "Go to conquer KDE." or "Conquer KDE is the technical information website." Maybe it would just take time to get used to using it in that fashion; perhaps it would be good to have a name that doesn't take time to get used to =) --[[User:Aseigo|Aseigo]] 00:15, 20 January 2007 (CET)

::I understand what you mean and I'm sorry I got it wrong. I am following the discussion you guys had for a few days in the mailing-list but it's very confusing! --[[User:Imagine|Imagine]] 05:54, 20 January 2007 (CET)

'''Korner''': Well I was thinking about this after what Aseigo told me. I think, like Aseigo, that the name is very important when it comes to marketing. TechZone, TechData, TechBase are very good names but they fall into the normality which is a good thing and a bad thing. There is so much technical information about KDE that I think it would get confusing for everyone about what the Tech[name] would be. So that's why I tried to think out of the box and came out with the Korner.

I think this could be a nice name to market it because we get the 'K' that is referring to KDE and the word 'Corner' that specifies a gathering of information. Plus, "Go to the Korner" could be easy to get use to it.--[[User:Imagine|Imagine]] 05:55, 20 January 2007 (CET)

: "Korner" will attract confused blues guitar fans. And I'd hang on to the dictionary that specifies "Corner" as a gathering of information - it might be worth something on the rare books market. Plus, "Go to the Corner" is used to punish naughty children. --[[User:Bille|Bille]] 10:23, 20 January 2007 (CET)

'''Empower KDE''': could be used as empower.kde.org for a subdomain. Is it ok to tell people to "go to Empower KDE"? I think it gives regular users the idea that it's not for them (they just ''use'' KDE), and it gives the developers/isvs/etc. the pleasant feeling of contributing. I thought of 'power users' at first, but it didn't sound appropriate. --[[User:Exit3219|Exit3219]] 19:56, 20 January 2007 (CET)

'''KDE Workshop''' or '''KDE Workbench''' or '''KDE Garage''' or '''KDE Lab''' - fresh ideas that came by night: --[[User:Jstaniek|jstaniek]] 01:52, 24 January 2007 (CET)

: lab is so-so; garage, workbench and workshop all work for me, though. garage is kind of "cool" sounding =) --[[User:Aseigo|Aseigo]] 06:16, 24 January 2007 (CET)

'''KDE Wisdom''': (wisdom.kde.org) Isn't that what this wiki strives to become? A source of wisdom and knowledge. The long name could be ''The KDE Wisdom Wiki''. Slogan: ''Wisdom is Power.'' ;) [[User:Exit3219|Exit3219]] 09:47, 24 January 2007 (CET)

'''KDE TechNet''': (technet.kde.org) I like the name "technology network" in short "technet" because it covers a wide (unlimited) range of technical informations on this or other sites. Additional for me it sounds better than techbase or techzone. --[[User:rhabacker|rhabacker]] 10:19, 24 January 2007 (CET)

: '''KDE Wiki''': ''Wiki'' is now a noun just like a ''web page''. Many of us are used to talking ''KDevelop wiki'', ''SUSE wiki'', and even below, Daniel used ''Kolab Wiki'' for Kolab. After all ''it's easy to remember'' and compatible with KISS principles... --[[User:Jstaniek|jstaniek]] 16:10, 19 January 2007 (CET)

= Thoughts on the Scope of This Wiki =

= Thoughts on the Target Audiences =

:Perhaps someone could clarify what is meant by "system administrators". At the extreme this term could apply to everyone from those with root on their local desktop install to people managing a network of thousands of PCs. I suspect the first of these includes the vast majority of KDE users. I assume this is not what is intended as this is a separate site to wiki.kde.org. -- TheoSpears

::We're talking about people that administer a multitude of PCs, probably they are doing this professionally most of the time. We want to provide resources for them (howtos, scripts, pittfalls and workarounds). The wiki also gives us the unique chance that they can contribute their knowledge back (works fine e.g. on the [http://wiki.kolab.org Kolab Wiki]. --[[User:Danimo|Danimo]] 02:12, 19 January 2007 (CET)

:::Also, do we need to put this up on this site? The question being, does Sys Admin information belong? Or should it remain at http://www.kde.org/areas/sysadmin/ ? --[[User:CuCullin|CuCullin]] 18:22, 19 January 2007 (CET)

:::: Good question. That fact that pretty well nobody knows about /areas/sysadmin is telling. I'm constantly educating people about the existence of that area on our website because people don't find it on their own. The reason seems to be that it is too buried in a general purpose side (www.kde.org) to be easily findable and because it isn't promoted well. We can elevate it's visibility by putting it on the front page of the wiki and we can use marketing and promotional support applied to the wiki to increase awareness of this body of information. In other words, we can tell people all at once about this "hub of technical information" which should let us reach more people with a simpler concept (simpler because you don't have to think, "ok, sysadmin technical documents would be over here... programmer technical documents would be over on this site..."). also note that we already will have sysadmin type information here to educate programmers on topics such as Kiosk. may as well keep it all together, no? bonus points that unlike www.kde.org, the wiki is community editable and updatable. /areas/sysadmin languishes so badly because you need special privileges to make changes to it. -[[User:Aseigo|Aseigo]] 00:15, 20 January 2007 (CET)

:::This is also a place where sys admins can find out more about the whole KDE community. This Wiki should be more like the very first place for anyone who wants to know what is KDE. Screenshot, announcement, the best apps(amarok, k3b, koffice, konqueror, etc.), so that the user will WANT to try this out.--[[User:Imagine|Imagine]] 19:16, 19 January 2007 (CET)

:::: I'm concerned that this scope creep would make it very hard to organize things well. We have other sites that are for user oriented information; keeping our sites focussed will make it easier to promote as well as more rewarding for visitors as they will have places "just for them". I agree we can use our web sites to market KDE better, but that is a separate topic that is IMO out of scope for this website. That said, this site should be first place people who want technical documents should think of going. --[[User:Aseigo|Aseigo]] 00:15, 20 January 2007 (CET)

:With such an international audience, presumably we need to think about how the name carries around the world. I know that this can sink any discussion with concerns from every country, but I wonder how well (for example) 'zone' and 'base' are understood in this context, particularly since both have more than one meaning in English. [[User:Tomchance|Tomchance]] 08:24, 19 January 2007 (CET)

:: Good point. How can we test this? Float names by people on irc or blogs or? --[[User:Aseigo|Aseigo]] 00:15, 20 January 2007 (CET)

Getting Started/Build

2007-01-05T14:35:48Z

Rhabacker: added KDE on Windows

Here you will find instructions for compiling and installing KDE from source and suggestions for when compilation doesn't go so smoothly.

== Building The Source ==

; [[/Stable Version|KDE 3.5 (Stable version)]]: Instructions for installing the latest stable KDE 3.5 release.

; [[/Unstable Version|KDE 4 (Unstable version, trunk)]]: Instructions for installing the latest and greatest KDE development source code.

; [[/Older KDE Versions|Old Versions]]: Instructions for building older KDE versions.

; [[/Coexisting Versions|Coexisting Versions]]: Directions to build multiple KDE versions on the same machine simultaneously.

; [[/FAQ|FAQ]]: Help with errors and other questions you might have.

== Further Links ==
* Build [http://solaris.kde.org/ KDE on Solaris]
* Build [http://www.kdelibs.com/ KDE on Windows]
[[Category:Build KDE]]