KDE TechBase - User contributions [en]

Development/Architecture/KDE4 (zh TW)

2013-01-03T18:57:15Z

Wrohdewald: do not mention GGZ anymore

{{Template:I18n/Language Navigation Bar_(zh_TW)|Development/Architecture/KDE4}}
== 開發框架 ==

# 桌面
#* [[Development/Architecture/KDE4/Plasma (zh TW)|Plasma - 桌面]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - 拼寫及文法檢查技術]]
#* [[Development/Architecture/KDE4/KParts|KParts - KDE 的元件架構]]
# 硬體
#* [[Development/Architecture/KDE4/Solid|Solid - 硬體及網路探知]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - 多媒體框架]]
# 通訊
#* [[Development/Architecture/KDE4/Decibel|Decibel - 即時通訊框架]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - 集中式的 PIM 儲存解決方案]]
# 使用者界面
#* [[Development/Architecture/KDE4/Providing_Online_Help|線上幫助]]
# 服務
#* [[Development/Architecture/KDE4/Starting_Other_Programs_(zh_TW)|啟動其它程式]]
#* [[Development/Architecture/KDE4/Strigi|Strigi - 桌面搜尋引擎]]
#* [[Projects/KNS2|KNewStuff2 - 協作資料共享]]（可能會移到專案）

== 其它 KDE 模塊中的框架 ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Development/Architecture/KDE4 (it)

2013-01-03T18:56:46Z

Wrohdewald: do not mention GGZ anymore

== Development Framework ==

# Desktop
#* [[Development/Architecture/KDE4/Plasma(it)|Plasma - Il Desktop]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Tecnologia di controllo ortografia e grammatica]]
#* [[Development/Architecture/KDE4/KParts_(it)|KParts - I componenti dell'architettura di KDE]]
# Hardware
#* [[Development/Architecture/KDE4/Solid_(it)|Solid - Controllo totale su Hardware e Rete]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Development/Architecture/KDE4/Decibel|Decibel - Framework per comunicazioni real time]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Development/Architecture/KDE4/Providing_Online_Help|Fornire Aiuto Online]]
# Services
#* [[Development/Architecture/KDE4/Starting_Other_Programs|Avvio di altri programmi]]
#* [[Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (potrebbero passare da qui alcuni progetti)

== Frameworks negli altri moduli KDE ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Development/Architecture/KDE4 (pt BR)

2013-01-03T18:56:26Z

Wrohdewald: do not mention GGZ anymore

== Framework de desenvolvimento ==

# Área de trabalho
#* [[Development/Architecture/KDE4/Plasma|Plasma - A área de trabalho]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Tecnologia de verificação de ortografia e gramática]]
#* [[Development/Architecture/KDE4/KParts|KParts - Arquitetura dos componentes KDE]]
# Hardware
#* [[Development/Architecture/KDE4/Solid|Solid - Hardware e network awareness]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - Framework multimídia]]
# Comunicação
#* [[Development/Architecture/KDE4/Decibel|Decibel - Framework para comunicação em tempo real]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Development/Architecture/KDE4/Providing_Online_Help|Fornecendo Ajuda Online]]
# Services
#* [[Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Projects/KNS2|KNewStuff2 - Compartilhamento de dados colaborativo]] (might move here from projects)

== Frameworks em outros módulos KDE ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Development/Architecture/KDE4 (ru)

2013-01-03T18:56:03Z

Wrohdewald: do not mention GGZ anymore

== Среда разработчика ==

# Рабочий стол
#* [[Development/Architecture/KDE4/Plasma (ru)|Plasma - рабочий стол]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - технология словарно-грамматической проверки текстов]]
#* [[Development/Architecture/KDE4/KParts|KParts - компонент архитектуры KDE]]
# Оборудование
#* [[Development/Architecture/KDE4/Solid|Solid - база знаний об оборудовании и сетевых устройствах]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - задача-ориентированное решение для Multimedia-приложений]]
# Комуникации
#* [[Development/Architecture/KDE4/Decibel|Decibel - универсальное решение для коммуникаций в реальном режиме времени (VoIP-телефония и системы мгновенного обмена сообщениями)]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - решение для централизованного хранения пользовательских данных в системах мгновенного обмена сообщениями]]
# Пользовательский интерфейс
#* [[Development/Architecture/KDE4/Providing_Online_Help|Обеспечение помощи в режиме онлайн]]
# Сервисы
#* [[Development/Architecture/KDE4/Strigi|Strigi - решение для быстрого поиска и индексации данных]]
#* [[Projects/KNS2|KNewStuff2 - Совместное использование данных]]

== Влияние на другие модули KDE ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Development/Architecture/KDE4/KGGZ (es)

2013-01-03T18:55:34Z

Wrohdewald: remove KGGZ description, it is not used anymore

''[http://www.ggzgamingzone.org/ GGZ Gaming Zone]'' is not used by KDE anymore.

[[Category:KDE4]]

Development/Architecture/KDE4 (es)

2013-01-03T18:54:40Z

Wrohdewald: do not mention GGZ anymore

== Infraestructura de desarrollo ==

# Escritorio
#* [[Development/Architecture/KDE4/Plasma_(es)|Plasma - El escritorio]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Tecnologia de corrección de gramática y vocabulario]]
#* [[Development/Architecture/KDE4/KParts_(es)|KParts - Arquitectura de componentes de KDE]]
# Hardware
#* [[Development/Architecture/KDE4/Solid_(es)|Solid - Capa de abstracción hardware y de red]]
#* [[Development/Architecture/KDE4/Phonon_(es)|Phonon - Infraestructura multimedia]]
# Comunicación
#* [[Development/Architecture/KDE4/Decibel_(es)|Decibel - Infraestructura para comunicaciones en tiempo real]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Solución de almacenamiento centralizado PIM]]
# Interfaz de usuario
#* [[Development/Architecture/KDE4/Providing_Online_Help_(es)|Suministro de ayuda en línea]]
# Servicios
#* [[Development/Architecture/KDE4/Starting_Other_Programs|Ejecutar otros programas]]
#* [[Development/Architecture/KDE4/Strigi|Strigi - Motor de busqueda para el escritorio]]
#* [[Projects/KNS2_(es)|KNewStuff2 - Compartición de datos colaborativo]] (podría moverse aqui desde proyectos)

== Infraestructuras en otros modulos de KDE ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Development/Architecture/KDE4 (pl)

2013-01-03T18:54:22Z

Wrohdewald: do not mention GGZ anymore

== Development Framework ==

# Pulpit
#* [[Development/Architecture/KDE4/Plasma|Plasma - Pulpit]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Technologia sprawdzania pisowni i gramatyki]]
#* [[Development/Architecture/KDE4/KParts|KParts - Architektura komponentów KDE]]
# Sprzęt
#* [[Development/Architecture/KDE4/Solid|Solid - Sprawy sprzętu i sieci]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - Framework odpodwiadający za multimedia]]
# Komunikacja
#* [[Development/Architecture/KDE4/Decibel|Decibel - Framework odpowiadający za komunikację w czasie rzeczywistym]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Centralne zarządzanie bazą PIM (Zarządzanie informacjami osobistymi) ]]

* [[Development/Architecture/KDE4/Strigi|Strigi - silnik wyszukujący]]
* [[Projects/KNS2|KNewStuff2 - Wspólne (collaborative) udostępnianie danych]] (może zostać przeniesione tutaj z projektów)
...

== Frameworki i inne moduły KDE ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Development/Architecture/KDE4/KGGZ (fi)

2013-01-03T18:54:02Z

Wrohdewald: remove KGGZ description, it is not used anymore

''GGZ Gaming Zone'' is not used by KDE anymore.

[[Category:KDE4]]

Development/Architecture/KDE4 (fi)

2013-01-03T18:53:23Z

Wrohdewald: do not mention GGZ anymore

== Kehityskehys ==

# Työpöytä
#* [[Development/Architecture/KDE4/Plasma_(fi)|Plasma - Työpöytä]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Oikeinkirjoitus- ja kielioppitarkistustekniikka]]
#* [[Development/Architecture/KDE4/KParts_(fi)|KParts - KDE:n komponenttiarkkitehtuuri]]
# Laitteisto
#* [[Development/Architecture/KDE4/Solid|Solid - Laitteisto ja verkkotietoisuus]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - Multimedia-kehys]]
# Viestintä
#* [[Development/Architecture/KDE4/Decibel|Decibel - Kehys tosiaikaviestintään]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Keskitetty PIM-tallennusratkaisu]]
# Käyttöliittymä
#* [[Development/Architecture/KDE4/Providing_Online_Help|Online-opastuksen tarjoaminen]]
# Palvelut
#* [[Development/Architecture/KDE4/Starting_Other_Programs|Muiden ohjelmien käynnistäminen]]
#* [[Development/Architecture/KDE4/Strigi|Strigi - Työpöydän hakukone]]
#* [[Projects/KNS2|KNewStuff2 - jakaminen]] (saattaa siirtyä tänne projekteista)

== Kehykset muissa KDE-moduuleissa ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Development/Architecture/KDE4 (se)

2013-01-03T18:52:55Z

Wrohdewald: do not mention GGZ anymore

== Utvecklingsramverk ==

# Skrivbordet
#* [[Development/Architecture/KDE4/Plasma|Plasma - Skrivbordet]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Stavnings- och grammatik teknologi]]
#* [[Development/Architecture/KDE4/KParts|KParts - KDE's komponent arkitektur]]
# Hårdvara
#* [[Development/Architecture/KDE4/Solid|Solid - Hårdvara och nätverks "awareness"]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - Multimedia ramverk]]
# Kommunikation
#* [[Development/Architecture/KDE4/Decibel|Decibel - Ramverk för realtidskommunikation]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Centraliserad PIM lagringslösning]]

* [[Development/Architecture/KDE4/Strigi|Strigi - Skrivbords sökmotor]]
* [[Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)
...

== Ramverk i andra KDE moduler ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Development/Architecture/KDE4 (gl)

2013-01-03T18:52:33Z

Wrohdewald: do not mention GGZ anymore

== Infraestrutura de desenvolvemento ==

# Escritorio
#* [[Development/Architecture/KDE4/Plasma|Plasma - O escritorio]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Tecnoloxía de corrección de gramática e vocabulario]]
#* [[Development/Architecture/KDE4/KParts|KParts - Arquitectura de componentes de KDE]]
# Hardware
#* [[Development/Architecture/KDE4/Solid|Solid - Capa de abstracción de hardware e rede]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - Infraestrutura multimedia]]
# Comunicación
#* [[Development/Architecture/KDE4/Decibel|Decibel - Infraestrutura para comunicacións en tempo real]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Almacenamento de datos personais]]

* [[Development/Architecture/KDE4/Strigi|Strigi - Motor de busca no escritorio]]
* [[Projects/KNS2|KNewStuff2 - Compartizón de datos colaborativo]] (pode que sexa movido dende proxectos aquí)
...

== Infraestruturas noutros módulos de KDE ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Projects/Related (zh CN)

2013-01-03T18:52:00Z

Wrohdewald: do not mention GGZ anymore

This page tries to document inter-project relationships that KDE has with other (independently-run) projects. The page is far from being complete.

''Note: In the dependencies list, it doesn't specify an exact list of libraries and their versions. Such a page is still needed in addition!''

== 开发工具 ==

详见 [[Development/Tools|全部列表]].

[[Projects/Related/Subversion|'''Subversion''']] is used as the version control system throughout KDE. [[Development/Tutorials/CMake|'''CMake''']] is also used,
and KDE played a heavy role in its development. Finally, KDE also served as a sufficiently complex target for [[Development/Tools/Valgrind|'''Valgrind''']].

'''MediaWiki''' is used for user-editable websites, although KDE's own [[Projects/kde.org/Capacity_HOWTO|'''Capacity''']] is also being used.

== 运行时 ==

Several libraries from [[/freedesktop.org|'''freedesktop.org''']] are used in KDE to run the basic desktop and window manager.

The '''GNU''' project develops software, some of which is used in KDE applications, and some for development. In the beginning of KDE there was some [http://www.kde.org/announcements/rmsresponse.php confusion] around this.
However, this has long been settled, KDE developers had a [http://phil.freehackers.org/writings/tea-with-stallman.html tee] with RMS in 2003 and KDE can be used as a totally free desktop for the GNU system.

Last but not least, KDE uses the fine Qt library from '''Trolltech'''.

Development/Architecture/KDE4 (de)

2013-01-03T18:51:07Z

Wrohdewald: do not mention GGZ anymore

== Development Framework ==

# Desktop
#* [[Development/Architecture/KDE4/Plasma (de)|Plasma - Der Desktop]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Technik zum Rechtschreib- und Grammatikcheck]]
#* [[Development/Architecture/KDE4/KParts (de)|KParts - Die KDE Komponentenarchitektur]]
# Hardware
#* [[Development/Architecture/KDE4/Solid|Solid - Schnittstelle zur Hardware und Netzwerken]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Development/Architecture/KDE4/Decibel|Decibel - Framework für Echtzeitkommunikation]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Zentralisierte PIM Speicherlösung]]
# User Interface
#* [[Development/Architecture/KDE4/Providing_Online_Help (de)|Online Hilfe verfügbar machen]]
# Services
#* [[Development/Architecture/KDE4/Strigi|Strigi - Desktop Suchmaschine]]
#* [[Projects/KNS2|KNewStuff2 - Gemeinsame Daten benutzen]] (könnte hierher von den Projekten verschoben werden)

== Frameworks in anderen KDE Modulen ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Projects/Related

2013-01-03T18:50:08Z

Wrohdewald: do not mention GGZ anymore

This page tries to document inter-project relationships that KDE has with other (independently-run) projects. The page is far from being complete.

''Note: In the dependencies list, it doesn't specify an exact list of libraries and their versions. Such a page is still needed in addition!''

== Development Tools ==

See [[Development/Tools|here]] for a full list of tools.

[[/Subversion|'''Subversion''']] is used as the version control system throughout KDE. [[Development/Tutorials/CMake|'''CMake''']] is also used,
and KDE played a heavy role in its development. Finally, KDE also served as a sufficiently complex target for [[Development/Tools/Valgrind|'''Valgrind''']].

'''MediaWiki''' is used for user-editable websites, although KDE's own [[Projects/kde.org/Capacity_HOWTO|'''Capacity''']] is also being used.

== Runtime Experience ==

Several libraries from [[/freedesktop.org|'''freedesktop.org''']] are used in KDE to run the basic desktop and window manager.

The '''GNU''' project develops software, some of which is used in KDE applications, and some for development. In the beginning of KDE there was some [http://www.kde.org/announcements/rmsresponse.php confusion] around this.
However, this has long been settled, KDE developers had a [http://phil.freehackers.org/writings/tea-with-stallman.html tee] with RMS in 2003 and KDE can be used as a totally free desktop for the GNU system.

Last but not least, KDE uses the fine Qt library from '''Trolltech'''.

Development/Architecture/KDE4/KGGZ

2013-01-03T18:48:44Z

Wrohdewald: remove KGGZ description, it is not used anymore

The ''[http://www.ggzgamingzone.org/ GGZ Gaming Zone]'' offers a complete free infrastructure for online games.

It is not used by KDE anymore.
[[Category:KDE4]]

Development/Architecture/KDE4

2013-01-03T18:47:21Z

Wrohdewald: remove link to KGGZ which is not used anymore

== Development Framework ==

# Desktop
#* [[Development/Architecture/KDE4/Plasma|Plasma - The desktop]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Spell- and grammar-checking technology]]
#* [[Development/Architecture/KDE4/KParts|KParts - KDE's component architecture]]
# Hardware
#* [[Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Schedules/KDE4/4.9 Feature Plan

2012-06-04T18:30:16Z

Wrohdewald: /* kdegames */

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}}
{{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}}
{{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
{{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}}
{{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-03-28T05:37:52Z

Wrohdewald: kajongg features

Schedules/KDE4/4.9 Feature Plan

2012-03-23T14:16:58Z

Wrohdewald: update kajongg status

Projects/MoveToGit/UsingSvn2Git

2012-03-16T07:07:31Z

Wrohdewald: renamed kde_svn to svn because svn is hardcoded in kde-ruleset/bin/startSync

{{Template:I18n/Language Navigation Bar|Projects/MoveToGit/UsingSvn2Git}}

This page documents how to go about getting a KDE module ready for the Great Git Migration of 2010.

=== Servers to use for all developers ===

KDE Sysadmin provides 3 servers which are fully setup for writing rules. You can find more information about that on: http://community.kde.org/Sysadmin/DeveloperAccessForRuleWriting.

All registered KDE developers have access to these machines. The rest of this document assumes a setup on your local computer, you are free to set it up on your local computer, but there is no need to. You can use the servers provided by KDE Sysadmin.

=== Getting the tools ===

The necessary tools are hosted at [http://www.gitorious.org/svn2git http://www.gitorious.org/svn2git] and [https://projects.kde.org/projects/playground/sdk/kde-ruleset https://projects.kde.org/projects/playground/sdk/kde-ruleset]. To get started do:

<syntaxhighlight lang="bash">
git clone git://gitorious.org/svn2git/svn2git.git
git clone git://anongit.kde.org/kde-ruleset
</syntaxhighlight>

And then install the libsvn-dev package.

This will get you the source code to build svn2git and the KDE ruleset files as they currently exist. Build the svn2git tool before moving on to the next step.

==== Building svn2git ====
Make sure you have Qt4 installed, then simply issue
<nowiki>qmake && make</nowiki> to build the executable called "svn-all-fast-export"

=== How rulesets work ===
The format for the svn2git rules is pretty simple. First and foremost you
have to declare some repositories:

<pre>
create repository kdelibs
end repository
</pre>

This tells svn2git that it should create a git repository called "kdelibs" that we can later on use to put commits into it.

The rest of the file are rules matching specific paths in Subversion, each rule
specifies what to do with the commits that appeared at the given path. The
possible actions are ignoring them or adding them to a particular branch in a particular repository. '''Note:''' Ignoring is done by simply leaving out the information about the repository and the branch.

As examples are more explanatory, the following rule would put all commits from 123453 to 456789 from the path /trunk/KDE/kdelibs into the master branch of
the kdelibs repository:
<pre>
match /trunk/KDE/kdelibs/
min revision 123453
max revision 456789
repository kdelibs
branch master
end match
</pre>

The min and max revision are useful in cases where the same path in SVN contains
code for different branches. An example would be KDevelop3, where KDevelop 3.3 was shipped with KDE 3.5 until 3.5.7, 3.5.8 contained KDevelop 3.4 and 3.5.9 contained KDevelop 3.5 and all of those kdevelop versions are now under /branches/KDE/3.5/kdevelop.

The two revision parameters are however not mandatory, if they're left out, then all commits that went to the given matching path in SVN are taken over into the specified branch.

To generate tags with git you use a special format for the branch parameter: refs/tags/<tagname>. So to put all commits from /tags/KDE/4.4.0/kdelibs into the v4.4.0 tag in the kdelibs git repository the rule would be like this:

<pre>
match /tags/KDE/4.4.0/kdelibs/
repository kdelibs
branch refs/tags/v4.4.0
end match
</pre>

For more examples see the svn2git/samples/ directory and the rules in the kde-ruleset repository.

The recurse action is a hack to tell svn2git to recurse into a directory it has just copied or that existed because it is of interest. Example: if we are importing kdelibs, it exists in {{path|trunk/KDE/kdelibs}}. At branching, someone did: <syntaxhighlight lang="bash">svn cp $SVNROOT/trunk/KDE $SVNROOT/branches/KDE/4.4</syntaxhighlight>

SVN recorded in that commit that branches/KDE/4.4 was the only path changed.
That means the rule <pre>branches/KDE/[^/]+/kdelibs/</pre> will not match.

We need to tell the tool that something interesting happened inside and it
should recurse. Then it will apply again all rules to the files that exist at
that point, at which point the rules will match.

==== Important Details ====

* All rules matching directories need to end with a '/', else the tool will crash at some point. This is a known bug. The only exception are the rules using the recurse-action.

* All rules matching files need to use the prefix rule.

* Matching rules can use Regular Expressions (according to the QRegExp syntax) in the match line and can use backreferences in the repository, prefix and branch parameters using \n (n=1,2,3,...) to reduce the amount of rules.

* The rules form an ordered list that the tool goes through while matching the changed paths for each commit. So if two rules match the same path and neither of the two has more matching criteria, then the rule that is written further up in the file wins. This is useful to exclude certain commits from the extraction process, if you look at the existing kde ruleset you'll notice that at the top some revisions are ignored.

* Each rule file needs to handle all commits, ie. each file should end with a rule which matches everything and does nothing.

=== Setting up your system ===

You will need ~65GB of disk space to get started, as the process requires a copy of the KDE svn database. There is a script that will download this for you (and which can be used to update it periodically using rsync) in kde-ruleset/bin/startSync.

more stuff goes here ...

=== Step-by-Step on writing rules for a module ===

==== Analyzing Subversion history to write rules ====
First of all you should check whether there are already rules for this module in the kde-ruleset repository. If there are rules already please go down to "Running svn2git"

If there are no rules yet, lets start with the master (aka trunk) branch. The easiest way to find out history with svn is executing:
<pre>svn log -v --stop-on-copy file:///path/to/svn/trunk/KDE/module</pre>

Please note that '/path/to/svn/' is the path to the 65GB you downloaded, and the 'trunk/KDE/module' is the module you want to write rules for, but those two put together is *not* a path that physically exists on your disk. svn log is smart enough to do what you want.

This will give you a history of the given module in trunk, it'll stop on the first commit that copied the code from somewhere else. The verbose output will allow you to see where this copy came from.

Now we have a starting point to write a rule, we want all commits from this path in our module repository in the master branch:
<pre>
match /trunk/KDE/module/
repository module
branch master
end match
</pre>
If the log stops at a commit that copied the module from somewhere, we need to
follow this to also get the history imported from the "old" place the module resided. The same svn command can be used with slightly different path argument:

<pre>svn log -v --stop-on-copy file:///path/to/svn/some/other/path@revision</pre>
The @revision is important as the original path usually doesn't exist anymore. With this we can write the next rule to the rules file and repeat until we've finally reached the point where the code was initially imported into svn (or probably cvs in the old days)

Now we can take care of the branches, this is a bit more involved as there may be multiple branches scattered over the /branches directory in svn. You can use the same commands as before to find out the history of a branch if you know the path. This time however you can stop following the source of copy-operations once you've found a source that you've already matched in a rule. That way your branch will be connected to the branch it originated from (which is often trunk aka master) in git.

A useful help with finding branches is svn ls in combination with the path@revision syntax, that way you can view the content of a particular svn directory as it was in an older revision. With this you can even find branches that are not visible (have been deleted) in the current revision.

The rule for putting commits into a git branch in the final repository is only slightly different (the example is for a core module):
<pre>
match /branches/KDE/4.4/module
repository module
branch 4.4
end match
</pre>

And last are the tags, this works the same as branches and trunk, except for using branch refs/tags/v<tag-version> for the branch parameter.

==== Running svn2git ====
This is the easiest, but most time-consuming part. As example lets say that in our current working directory we have the kde rules repository in kde-ruleset subdir, the svn2git tool in the svn2git subdir and the KDE repository in the svn subdir:
<pre>
svn2git/svn-all-fast-export --identity-map kde-ruleset/account-map --rules kde-ruleset/module svn
</pre>

This will take a few hours usually, but it'll spit out the progress. The tool also writes a logfile to module.log, so in case something goes wrong you can find more details in there.

Once its done you should have a new "module" git repository in your current working directory.

==== Checking for proper history in the new git repository ====
To check the history of the created git repository simply change into the directory and use your favourite git command like ''git log'' to check if all is well.

A '''very easy way to check whether the history was imported properly''' is to use the gitk tool from git. It shows you a graphical representation of the history in the git repository which makes it easy to identify where something is wrong.

The tool should be run with the --all switch so it shows all branches.

You can now scroll through the history to check whether things have been imported correctly.

First and foremost there should be the master branch starting at the top with the most recent commit to trunk/ and ending in the oldest commit that imported the code into KDE's svn or cvs repository.

From the master branch there should be several branches going away for each branch you imported. And eventually also branches that start from another non-master branch.

Things that you should look out for are branches that start "nowhere", that is the first commit in the branch has no parent in another branch or master. This means that svn2git didn't see a commit that created this branch from another using a svn cp command. That can mean that you may have forgotton to add a match rule for some path or that the same path was used for different branches in different revisions. The same applies to tags which have a commit without any parent.

This can usually be fixed by using svn log and svn ls to follow the history of the branch. Eventually you might need to apply the min/max revision paramters.

You'll notice that some tags are looking like this:

<pre>
|
* * <v1.2.3>
| |
* *
| /
*
</pre>

Thats normal for our tags even if a bit ugly. The reason is that often compile-fixes are done in trunk/ after the tag has been created and then the commit has been merged over to the tag.

Another thing however are tags that are named vx.y.z_124321. These are tags that have been deleted and re-created later. You can usually see that in the svn log history, these tags can either be manually deleted after the repository creation using git tag or you can add rules that ignore certain revisions of the tag-path before the one putting the commits into the git repository:

<pre>
match /tags/KDE/3.3.2/kdelibs
min revision 424234
max revision 424236
end match
match /tags/KDE/3.3.2/kdelibs
repository kdelibs
branch refs/tags/3.3.2
end match
</pre>

If you choose to delete them manually please make sure to document this with a textfile or inside the rule file so if someone else does the conversion later again he'll know what manual steps you did.

Also try grepping the output from svn2git for the string '"copy from"' (with the double quotation marks). This will give you a list of revisions/paths that svn2git could not detect the origin of. That is someone did a svn cp/mv and the old path is not in the generated git repository.

Before publishing the newly created git repository make sure to repack it. This can greatly reduce it's size (i.e. Phonon's git repository could be shrunken from 18 MB to 5.2 MB)

==== Pushing the Repository to git.kde.org ====
Request a new project as described in the [http://community.kde.org/Sysadmin/GitFAQ#Requesting_project_migrations_from_KDE_SVN_or_Gitorious.org Git KDE Manual]. Then push the repository into that new git project.

==== How to update the account-map file ====

Currently, account-map file is being generated with 'generateAccountMap'[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/generateAccountMap] script which parses kde-common/accounts[http://websvn.kde.org/trunk/kde-common/accounts?view=log] and kde-common/disabled-accounts[http://websvn.kde.org/trunk/kde-common/disabled-accounts?view=log] from SVN.

Once you have your git repository you should check if there are accounts not listed in account-map file (you can use checkMissingAccounts[http://gitorious.org/svn2git/kde-ruleset/blobs/master/bin/checkMissingAccounts]), if that is the case, check if the missing accounts are listed in kde-common/accounts or kde-common/disabled-accounts, if it's not there file a sysadmin bug report[https://bugs.kde.org/enter_sysadmin_request.cgi] to get your missing account included in disabled-accounts. Once you get your missing accounts included in disabled accounts, you could generate the account-map file running 'bin/generateAccountMap', then run svn-all-fast-export again. Do not edit account-map file directly!

=== Troubleshooting ===

==== Recurse action doesn't work with cvs2svn tag commits ====

You may have to deal with a commit done by cvs2svn to create a tag, for example:
<pre>
r386536 | (no author) | 2005-02-05 22:16:00 +0100 (Sat, 05 Feb 2005) | 2 lines
Changed paths:
A /branches/beta_0_7_branch (from /trunk:386535)
D /branches/beta_0_7_branch/art-devel
D /branches/beta_0_7_branch/arts
D /branches/beta_0_7_branch/bugs
D /branches/beta_0_7_branch/devel-home
D /branches/beta_0_7_branch/developer.kde.org
D /branches/beta_0_7_branch/enterprise.kde.org
D /branches/beta_0_7_branch/events.kde.org
D /branches/beta_0_7_branch/foundation
D /branches/beta_0_7_branch/kckde
D /branches/beta_0_7_branch/kde-common
D /branches/beta_0_7_branch/kde-i18n
D /branches/beta_0_7_branch/kde-qt-addon
D /branches/beta_0_7_branch/kde-women.kde.org
D /branches/beta_0_7_branch/kdeaccessibility
D /branches/beta_0_7_branch/kdeaddons
D /branches/beta_0_7_branch/kdeadmin
D /branches/beta_0_7_branch/kdeartwork
D /branches/beta_0_7_branch/kdebase
D /branches/beta_0_7_branch/kdebindings
D /branches/beta_0_7_branch/kdeedu
D /branches/beta_0_7_branch/kdeextragear-1
D /branches/beta_0_7_branch/kdeextragear-2
M /branches/beta_0_7_branch/kdeextragear-3
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.am.in
D /branches/beta_0_7_branch/kdeextragear-3/Makefile.cvs
D /branches/beta_0_7_branch/kdeextragear-3/README
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.bot
D /branches/beta_0_7_branch/kdeextragear-3/configure.in.in
D /branches/beta_0_7_branch/kdeextragear-3/digikam
D /branches/beta_0_7_branch/kdeextragear-3/digikamimageplugins
D /branches/beta_0_7_branch/kdeextragear-3/doc
D /branches/beta_0_7_branch/kdeextragear-3/filelight
D /branches/beta_0_7_branch/kdeextragear-3/kcfgcreator
D /branches/beta_0_7_branch/kdeextragear-3/kconfigeditor
D /branches/beta_0_7_branch/kdeextragear-3/kdebluetooth
D /branches/beta_0_7_branch/kdeextragear-3/kdetv
D /branches/beta_0_7_branch/kdeextragear-3/keurocalc
D /branches/beta_0_7_branch/kdeextragear-3/kiosktool
D /branches/beta_0_7_branch/kdeextragear-3/klicker
D /branches/beta_0_7_branch/kdeextragear-3/kplayer
D /branches/beta_0_7_branch/kdeextragear-3/pwmanager
D /branches/beta_0_7_branch/kdeextragear-libs-1
D /branches/beta_0_7_branch/kdegames
D /branches/beta_0_7_branch/kdegraphics
D /branches/beta_0_7_branch/kdeinstaller
D /branches/beta_0_7_branch/kdejava
D /branches/beta_0_7_branch/kdekiosk
D /branches/beta_0_7_branch/kdelibs
D /branches/beta_0_7_branch/kdemultimedia
D /branches/beta_0_7_branch/kdenetwork
D /branches/beta_0_7_branch/kdenonbeta
D /branches/beta_0_7_branch/kdenox
D /branches/beta_0_7_branch/kdepim
D /branches/beta_0_7_branch/kdeplayground-artwork
D /branches/beta_0_7_branch/kdeplayground-base
D /branches/beta_0_7_branch/kdeplayground-edu
D /branches/beta_0_7_branch/kdeplayground-games
D /branches/beta_0_7_branch/kdeplayground-ioslaves
D /branches/beta_0_7_branch/kdeplayground-multimedia
D /branches/beta_0_7_branch/kdeplayground-network
D /branches/beta_0_7_branch/kdeplayground-pim
D /branches/beta_0_7_branch/kdeplayground-utils
D /branches/beta_0_7_branch/kdereview
D /branches/beta_0_7_branch/kdesdk
D /branches/beta_0_7_branch/kdesecurity
D /branches/beta_0_7_branch/kdesupport
D /branches/beta_0_7_branch/kdetoys
D /branches/beta_0_7_branch/kdeutils
D /branches/beta_0_7_branch/kdevelop
D /branches/beta_0_7_branch/kdewebdev
D /branches/beta_0_7_branch/kdoc
D /branches/beta_0_7_branch/kfte
D /branches/beta_0_7_branch/khtmltests
D /branches/beta_0_7_branch/klyx
D /branches/beta_0_7_branch/kmusic
D /branches/beta_0_7_branch/koffice
D /branches/beta_0_7_branch/kofficetests
D /branches/beta_0_7_branch/konstruct
D /branches/beta_0_7_branch/qt-copy
D /branches/beta_0_7_branch/quanta
D /branches/beta_0_7_branch/sysconfig
D /branches/beta_0_7_branch/valgrind
D /branches/beta_0_7_branch/www

This commit was manufactured by cvs2svn to create branch
'beta_0_7_branch'.
</pre>
If you do this
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/
min revision 386536
max revision 386536
action recurse
end match
</pre>
svn-all-fast-export will fail, you'll get an error sayining that '/foo/bar/path' was not found where '/foo/bar/path' is one of the deleted paths in the cvs2svn commit. This is because some paths were deleted in the same commit where you want to do an 'action recurse'. Therefore, to avoid matching the deleted paths you should do an action recurse on each intermediate directory from '/branches/beta_0_7_branch/' to '/branches/beta_0_7_branch/kdeextragear-3/krecipes/' and you should use a final '$' to make sure that the deleted paths will not be considered, thusly:
<pre>
match /branches/beta_0_7_branch/kdeextragear-3/krecipes/
repository krecipes
branch 0.7
end match

match /branches/beta_0_7_branch/kdeextragear-3/$
min revision 386536
max revision 386536
action recurse
end match

match /branches/beta_0_7_branch/$
min revision 386536
max revision 386536
action recurse
end match
</pre>

=== Getting Help ===
If you run into strange things or can't find a rule for something you can reach the KDE Git migration team on IRC: irc.freenode.org, #kde-git or on the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest mailinglist]

Schedules/KDE4/4.9 Feature Plan

2012-02-28T23:33:16Z

Wrohdewald: /* kdegames/Kajongg */

Getting Started/Build/Windows/emerge

2011-03-29T08:50:43Z

Wrohdewald: clarify what trunk is in relation to git

''emerge'' is a tool to build the KDE sources and its third-party requirements on MS Windows. It is the '''easy''' way to build KDE on MS Windows.

== Introduction ==
Emerge is a tool that can build the different parts of KDE and its dependencies under Windows. We created this tool to automate and simplify the build process under Windows. We try to build all packages that we offer in the KDE installer with emerge. That has some advantages for us:
* it is easy for people to join us:
Before emerge it was quite some work to set a system up for development. There were some quirks, which were documented in some mailing lists, but you had to remember them or you ran into an already solved problem again, etc.
Now to get a development machine you need a Windows computer, need to install Python and Subversion and do the emerge checkout. Then execute emerge to build what you want to build. This is easy for developers coming from Windows to KDE, and also for KDE developers coming to Windows.
* it is easy for us to do (nightly/continuous/release/reproducable/...) builds:
With emerge you can build the whole software stack (low-level libs, Qt, kdelibs, things above that) with only one command. You can start that build, and some hours later you can check if it worked, or if something broke. So we can spot problems easier and earlier. We can also start with a "naked" Windows computer without any other installed software and bootstrap kde on it. That ensures, that no hidden dependencies on some pieces of software sneak in, because then the builds on a "naked" computer would break and show the problem.
* it is easier to collaborate:
We can test the same emerge build description for a package on different Windows versions/computers before we do binary releases. People can also add build descriptions for new packages to the Subversion repository.

This emerge tool was inspired by the Gentoo emerge tool.

== Set up the environment ==
=== Root directory ===
Create a directory if possible in your harddrive's root e.g. C:\kderoot or D:\kderoot (You will need this PATH later). This directory will contain the whole kde installation later. We will refer to it as %KDEROOT%.

=== Python interpreter ===
<tt>emerge.bat</tt> invokes an <tt>emerge.py</tt> script written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] programming language, so you first need to [http://www.python.org/download/ install the Python 2.7 Interpreter]. The ''python'' installation directory will be added to the PATH later by <tt>%KDEROOT%\etc\kdesettings.bat</tt> script.

=== Subversion client ===
The latest source code for Windows ''emerge'' and the rest of KDE is stored in a repository created and managed using the [http://subversion.tigris.org/ Subversion] version control tool, abbreviated svn. You need a Subversion client for the first checkout of emerge. There are at least two applications:
*a command line client, available at [http://subversion.apache.org/packages.html subversion.apache.org], aimed at developers or power users accustomed with the command line,
*a GUI program like [http://tortoisesvn.tigris.org/ TortoiseSVN], optional, useful for displaying differences between various versions of files in the repository in a graphical way.

Emerge uses its own Subversion client for checking out all KDE source code. However it is not quite up to date: From August 2009. You can find it in %KDEROOT%\dev-utils\svn\bin. It will be used by emerge even if you have another svn executable installed.

Note 1: If you experience problems with the checkout of Qt (svn doesn't work correctly) please remove any other svn binaries out of the path that you do have. '''The different versions of the Apache portable runtime (APR) are incompatible!'''

Note 2: Most source files in the KDE Subversion repository have Unix line endings, and svn will not convert them to Windows line endings. This is fine for emerge, but the standard Windows editor might not show those files correctly. You can use another editor like vim (http://www.vim.org).

=== Getting the ''emerge'' tool ===
The source code of the ''emerge'' tool and the recipes for creating KDE packages are located at <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt>, which is an URL based on the Subversion-specific ''svn'' protocol.

You need to check out the source code from the ''emerge'' Subversion directory into a new directory below your root directory (the root directory is normally called %KDEROOT% here) or get it inside a self extracting archive (not tested yet).

==== Check out using the 'svn' command ====

*Option 1: With the ''svn'' command line tool, you can accomplish this with the following commands:<pre>cd %KDEROOT%</pre>
**if you will only use anonymous (read-only) access to the KDE svn repository:<pre>svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
**or, if you plan to use write access (commit) to the KDE svn repository
***via https:<pre>svn co --username yourusername https://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
***via a [[Getting_Started/Build/KDE4/Windows/subversion|puTTY tunnel]] using your existing account & OpenSSH private key: <pre>svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>

This would result with:

Error validating server certificate for '<nowiki>https://svn.kde.org:443</nowiki>':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: svn.kde.org
- Valid: from Wed, 11 May 2005 09:08:21 GMT until Sat, 09 May 2015 09:08:21 GMT
- Issuer: SVN, KDE e.V., Nuernberg, Bavaria, DE
- Fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
(R)eject, accept (t)emporarily or accept (p)ermanently?

enter ''p'' here to permanently accept the certificate:

Authentication realm: <<nowiki>https://svn.kde.org:443</nowiki>> KDE SVN account
Password for 'yourusername': ***************
A emerge\kdeenv.bat
A emerge\portage
A emerge\portage\kdesupport
[....]

The password and cache for the certificates is saved in <tt>%APPDATA%\Subversion\auth</tt> directory.

==== Check out using the TortoiseSVN ====

*Option 2: If you use TortoiseSVN:
*#right-click on your %KDEROOT% folder and select ''SVN Checkout...'' command from the context menu,
*#paste <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt> URL into the ''URL of repository'' text box (replace with <tt><nowiki>https://svn.kde.org/home/kde/trunk/kdesupport/emerge</nowiki></tt> for read-write access)
*#add <tt>\emerge</tt> to the folder name in the ''Checkout directory'' box and click OK to continue
*#if you picked the read-write access, you will be asked for accepting the SSL certificate of the SVN server (click "Premanent") and then for username and password. For convenience select "Save authentication" checkbox too (the password and cache for the certificates will be saved in <tt>%APPDATA%\Subversion\auth</tt> directory).

After the checkout you should have the directory <tt>%KDEROOT%\emerge</tt>. If you don't, you move your ''emerge'' directory to that location.

==== Installing from the self-extracting archive ====
*Option 3: Get the self-extracting archive from [http://www.winkde.org/pub/kde/ports/win32/emerge/emerge-latest.exe here], unpack it into your KDEROOT directory so that you have a folder %KDEROOT%\emerge.
* This self-extracting archive brings a subversion repository containing the emerge scripts and a python installation with it, so you do not need either of them before starting with emerge.

=== Configure the ''emerge'' tool ===
# Create the directory <tt>%KDEROOT%\etc</tt>.
# Copy the file <tt>%KDEROOT%\emerge\kdesettings-example.bat</tt> as <tt>%KDEROOT%\etc\kdesettings.bat</tt> and change its contents according to your needs. The options are described in the ''rem'' lines in the file itself.

The kdesettings.bat script will be called by the main kdeenv.bat script.

Note 1: '''Be sure that you neither have the msys/bin nor the cygwin/bin in your path. If so you have to definitely remove it from the path.'''

Note 2 '''from a user: The applications gimp, inkscape and graphviz are also a problem. To make sure that there's nothing wrong I stripped my path to contain only what I needed to build.'''

Note 3 '''from another user: be careful when renaming the file to "kdesettings.bat" it is easy to end up with "kdesettings.bat.bat" instead of what you want since Windows(by default) will not show the the file extension part of a file.'''

=== [Optional, Advanced] emergehosts.conf ===
Add a file emergehosts.conf in the <tt>%KDEROOT%\etc</tt> directory. The format of this file is a typical config file with only two entries per section:
The first entry is the ''host'' as mentioned in the portage file for the package. The second entry is called ''replace'' and is the replace string for the host string.

As an example, here is how to checkout all gitorious based repos of the kde-developers group using a push url instead of the anonymous access:
<code>
[qt gitorious]
host: git://gitorious.org/+kde-developers/
replace: git@gitorious.org:+kde-developers/
</code>

As a second example here is how to checkout with a ssh user from a subversion repository:
<code>
[svn.example.com]
host: svn://svn.example.com/
replace: svn+ssh://user@svn.example.com/
</code>

The name of the section doesn't matter and can be used for descriptions.

== Using emerge ==

To use emerge you need to start a console window and point that to <tt>%KDEROOT%\emerge</tt>. For example:

C:
cd \%KDEROOT%\emerge

Then you have to execute

kdeenv.bat

This tells emerge about your environment settings (e.g. paths). It will load your configuration from <tt>%KDEROOT%\etc\kdesettings.bat</tt>. It should not give any error messages, otherwise emerge will not work as expected. The output should look similar to this one (of course with your paths):

C:\kderoot\emerge>kdeenv.bat
kdesettings.bat executed
KDEROOT : C:\kderoot
KDECOMPILER : mingw
KDESVNDIR : C:\kderoot\svn
PYTHONPATH : C:\python27
DOWNLOADDIR : C:\kderoot\download

C:\kderoot\emerge>

Next, if you have configured your kdesettings.bat to use svn+ssh for your subversion checkout, then you need to run:

<code>plink <your-svn-username>@svn.kde.org
plink <your-kde-username>@git.kde.org</code>

This will prompt you to accept the fingerprint of the server, otherwise svn will hang forever when trying to download from the server.

Now you should be able to use emerge. Type

emerge --help

to get some help on usage.

''Note: There is a short path option in kdesettings which you will
need if you want to build Qt in a directory that has a pathlenght of
more then around 5 characters. This problem is due to limitations of the command line length and the Qt build system.''

== Setting up a compiler ==
Currently emerge supports both the MinGW and MS Visual C++ (msvc) compilers. We did not add dependencies for the compilers, so you have to make sure to install a compiler by yourself. There are three ways to set up a compiler for emerge.
We assumed you have set KDECOMPILER variable properly in the <tt>%KDEROOT%\etc\kdesettings.bat</tt>.

In the following sections you can find information on how to install or reuse an existing compiler.

=== Install the MinGW compiler with emerge ===
Let emerge install the MinGW compiler, as soon as emerge needs MinGW it will automatically fetch the correct version for you.

=== Install MS Visual C++ ===
Read [[../MS_Visual_Studio#The_Compiler|here]].

=== Point to an existing MS Visual C++ installation ===
You need to point emerge to an existing msvc installation. This is run automatically for you from kdeenv.bat if configured properly in kdesettings.bat. Check your kdesettings.bat file to know where to set it.

== Installing the base system ==
Once you have emerge and a compiler installed and working, try:
* <tt>emerge --help</tt> for a list of available commands
* <tt>emerge --print-installable</tt> to get a list of available packages
* <tt>emerge --print-installed</tt> to get a list of currently installed packages
Further options are described below.

You are now ready to start building KDE, it is recommended to do so progressively, relying on emerge to automatically resolve the required dependencies at each set step:

* Enter <tt>emerge qt</tt>. This will fetch and install Windows versions of numerous UNIX-like utilities and libraries, then checkout, compile and install Qt. This will take several hours.
* Enter <tt>emerge kdelibs</tt>. This will checkout, compile and install the required kdesupport modules and then kdelibs.
* Enter <tt>emerge kdebase-apps</tt>. This will checkout, compile and install kdebase-runtime, and kdebase-apps

You will now have successfully installed a base KDE system and can now install other KDE modules as required.

Note that this will install the development version of KDE (trunk in svn repositories, master in git repositories), if you wish to install a particular stable branch then you must prefix the KDE package names with the required version, i.e. <tt>emerge kde-4.5/kdelibs</tt>. You can force emerge to always default to a given branch by setting the <tt>EMERGE_DEFAULTCATEGORY</tt> variable in your kdesettings.bat file. You should not mix kde packages from different branches.

It is strongly recommended you do not choose to manually install any of the utilities and libraries yourself, as you may install the wrong version and cause installation failures. Instead allow emerge to resolve the dependencies for you.

Every time you want to update or install a package, you should first update your emerge checkout (simply run emerge --update emerge) to ensure you are using the latest package recipies.

== What emerge does ==
'''emerge ''packageName'' ''' performs the separate actions <tt>--fetch</tt>, <tt>--unpack</tt>, <tt>--compile</tt>, <tt>--install</tt>, <tt>--manifest</tt>, and <tt>--qmerge</tt>.

The <tt>--fetch</tt> action will retrieve either a binary or the source code for the package:
* If a binary package, this will be downloaded into the <tt>DOWNLOADDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\download</tt>.
* If a non-KDE source package, the source repository will be checked-out into <tt>%DOWNLOADDIR%\svn-src</tt>, e.g. Qt source may be found in <tt>C:\kderoot\download\svn-src\qt</tt>.
* If a KDE source package from the <tt>svn.kde.org</tt> repository, then the source will be checked-out into the <tt>KDESVNDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\svn</tt>.

== ''emerge'' command line options and settings ==
There are some options that can be used when building with ''emerge''.

{| border="0" cellpadding="2"
!Command line switch
!Command line argument
!
!Description
|-valign="top"
|<tt>-v</tt>
|<tt>EMERGE_VERBOSE</tt>
|width="5%"|
|This option sets the verbosity level. Currently the highest verbosity level is 3 (<tt>-v -v -v</tt>). A verbosity level of 0 should give no output and equals to <tt>-q</tt>. You can set <tt>EMERGE_VERBOSE=3</tt> instead in the environment of the commandline or within your <tt>kdesettings.bat</tt> file.
|-valign="top"
|<tt>--offline</tt>
|
|
|This option suppresses the update step of the local tree - which needs some time. Be aware though that you have to have existing sources already if you want to use this option.
|-valign="top"
|<tt>-t</tt>
|<tt>EMERGE_BUILDTESTS</tt>
|
|This option enables or disables KDE4 buildtests for KDE modules. Other packages will not change. Use <tt>EMERGE_BUILDTESTS=True</tt> or <tt>=False</tt>.
|-valign="top"
|<tt>--print-targets</tt>
|
|
|This option will display all "targets" a certain package has. Normally targets are fixed releases or different branches. They are defined in the portage file.
|-valign="top"
|<tt>--target=TARGET</tt>
|
|
|This sets a specific target for this package. If not added, the default target is used, which can be checked by looking at the output of '''--print-targets'''.
|-valign="top"
|<tt>-i</tt>
|
|
|This option ignores that a package is already installed. It builds it completely new, but keeps the dependencies.
|-valign="top"
|<tt>--update</tt>
|
|
|This option ignores that a package is already installed but doesn't cleanup an already existing build directory. Thus you will only rebuild files that have changed since the last build.
|}

== Hints ==
=== Updating packages ===
*Once you have ''packagename'' built, type <code>emerge --update packagename</code> to update <tt>packagename</tt> from the Subversion and compile it without removing the build dir or <code>emerge --update-all</code> to update all packages that can be rebuild (they are rebuild with --update).

=== General setup ===
For Fine Tuning see here:
[[Projects/KDE_on_Windows/Installation#Fine-tuning|Fine-tuning]]

== Notes ==

''emerge'' can mostly cooperate with the [[Projects/KDE_on_Windows/Installation#KDE_Installer_for_Windows|kdewin-installer]] but we're currently still working on some packages which are packaged in a wrong way.
It is not recommended to use another layout then '''installer''' for '''directory_layout''' in the '''kdesettings.bat''' anymore (see that file for more detailed information).

''emerge'' creates lots of files in '''\kderoot\tmp''' during build.
After a package is successfully installed
(check '''\kderoot\etc\portage\installed''' or the directory '''\kderoot\manifest\'''), you can delete its temporary directory.

Windows ''emerge'' is derived from the Gentoo portage system, but we are currently not enforcing compatibility. If you have questions about that please contact us at the channel #kde-windows on irc.freenode.net.

last reviewed by [[User:SaroEngels|SaroEngels]] 22:25, 4 November 2010 (UTC)

==Vista issues==
*[[User:Jstaniek|jstaniek]] 12:02, 15 January 2008 (CET): UAC has infamous heuristics that make programs like patch.exe treat as installers and try to run them with admin rights (!). This heuristics can be tricked by renaming patch.exe to something like pch.exe ([http://nevali.net/2007/01/update-workaround-for-the-cygwin-uac-problem/ example]) but we did not want to add item to our infrastructure. Instead it is possibleto turn off the heuristics (see the screenshot [http://theinvisiblethings.blogspot.com/2007/02/running-vista-every-day.html here in the security blog calling the heuristics 'severe hole in the design of UAC']). If you happen to disable the UAC, as many annoyed users and devs do (msvc demands admin rights anyway!), patch.exe should already work for you as in older Windows. Alternatively you may want to disable UAC [http://www.howtogeek.com/howto/windows-vista/disable-user-account-controluac-for-administrators-only/ for admins only], but this makes no sense if you are the only user of your machine and use only the admin account.
* [http://ben.versionzero.org/wiki/Fixing_the_way_Vista_Auto-detects_Installers This wiki page] lists instructions on how to use program manifest to disable privilege elevation for a single binary and makes patch play nice with UAC. This [https://bugs.kde.org/show_bug.cgi?id=186712 should] eventually be integrated to emerge scripts.

[[Category:MS Windows]]

Getting Started/Build/Windows/emerge

2011-03-29T08:49:08Z

Wrohdewald: remove hint about emerge fetch qt hanging, should not happen anymore

''emerge'' is a tool to build the KDE sources and its third-party requirements on MS Windows. It is the '''easy''' way to build KDE on MS Windows.

== Introduction ==
Emerge is a tool that can build the different parts of KDE and its dependencies under Windows. We created this tool to automate and simplify the build process under Windows. We try to build all packages that we offer in the KDE installer with emerge. That has some advantages for us:
* it is easy for people to join us:
Before emerge it was quite some work to set a system up for development. There were some quirks, which were documented in some mailing lists, but you had to remember them or you ran into an already solved problem again, etc.
Now to get a development machine you need a Windows computer, need to install Python and Subversion and do the emerge checkout. Then execute emerge to build what you want to build. This is easy for developers coming from Windows to KDE, and also for KDE developers coming to Windows.
* it is easy for us to do (nightly/continuous/release/reproducable/...) builds:
With emerge you can build the whole software stack (low-level libs, Qt, kdelibs, things above that) with only one command. You can start that build, and some hours later you can check if it worked, or if something broke. So we can spot problems easier and earlier. We can also start with a "naked" Windows computer without any other installed software and bootstrap kde on it. That ensures, that no hidden dependencies on some pieces of software sneak in, because then the builds on a "naked" computer would break and show the problem.
* it is easier to collaborate:
We can test the same emerge build description for a package on different Windows versions/computers before we do binary releases. People can also add build descriptions for new packages to the Subversion repository.

This emerge tool was inspired by the Gentoo emerge tool.

== Set up the environment ==
=== Root directory ===
Create a directory if possible in your harddrive's root e.g. C:\kderoot or D:\kderoot (You will need this PATH later). This directory will contain the whole kde installation later. We will refer to it as %KDEROOT%.

=== Python interpreter ===
<tt>emerge.bat</tt> invokes an <tt>emerge.py</tt> script written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] programming language, so you first need to [http://www.python.org/download/ install the Python 2.7 Interpreter]. The ''python'' installation directory will be added to the PATH later by <tt>%KDEROOT%\etc\kdesettings.bat</tt> script.

=== Subversion client ===
The latest source code for Windows ''emerge'' and the rest of KDE is stored in a repository created and managed using the [http://subversion.tigris.org/ Subversion] version control tool, abbreviated svn. You need a Subversion client for the first checkout of emerge. There are at least two applications:
*a command line client, available at [http://subversion.apache.org/packages.html subversion.apache.org], aimed at developers or power users accustomed with the command line,
*a GUI program like [http://tortoisesvn.tigris.org/ TortoiseSVN], optional, useful for displaying differences between various versions of files in the repository in a graphical way.

Emerge uses its own Subversion client for checking out all KDE source code. However it is not quite up to date: From August 2009. You can find it in %KDEROOT%\dev-utils\svn\bin. It will be used by emerge even if you have another svn executable installed.

Note 1: If you experience problems with the checkout of Qt (svn doesn't work correctly) please remove any other svn binaries out of the path that you do have. '''The different versions of the Apache portable runtime (APR) are incompatible!'''

Note 2: Most source files in the KDE Subversion repository have Unix line endings, and svn will not convert them to Windows line endings. This is fine for emerge, but the standard Windows editor might not show those files correctly. You can use another editor like vim (http://www.vim.org).

=== Getting the ''emerge'' tool ===
The source code of the ''emerge'' tool and the recipes for creating KDE packages are located at <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt>, which is an URL based on the Subversion-specific ''svn'' protocol.

You need to check out the source code from the ''emerge'' Subversion directory into a new directory below your root directory (the root directory is normally called %KDEROOT% here) or get it inside a self extracting archive (not tested yet).

==== Check out using the 'svn' command ====

*Option 1: With the ''svn'' command line tool, you can accomplish this with the following commands:<pre>cd %KDEROOT%</pre>
**if you will only use anonymous (read-only) access to the KDE svn repository:<pre>svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
**or, if you plan to use write access (commit) to the KDE svn repository
***via https:<pre>svn co --username yourusername https://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
***via a [[Getting_Started/Build/KDE4/Windows/subversion|puTTY tunnel]] using your existing account & OpenSSH private key: <pre>svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>

This would result with:

Error validating server certificate for '<nowiki>https://svn.kde.org:443</nowiki>':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: svn.kde.org
- Valid: from Wed, 11 May 2005 09:08:21 GMT until Sat, 09 May 2015 09:08:21 GMT
- Issuer: SVN, KDE e.V., Nuernberg, Bavaria, DE
- Fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
(R)eject, accept (t)emporarily or accept (p)ermanently?

enter ''p'' here to permanently accept the certificate:

Authentication realm: <<nowiki>https://svn.kde.org:443</nowiki>> KDE SVN account
Password for 'yourusername': ***************
A emerge\kdeenv.bat
A emerge\portage
A emerge\portage\kdesupport
[....]

The password and cache for the certificates is saved in <tt>%APPDATA%\Subversion\auth</tt> directory.

==== Check out using the TortoiseSVN ====

*Option 2: If you use TortoiseSVN:
*#right-click on your %KDEROOT% folder and select ''SVN Checkout...'' command from the context menu,
*#paste <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt> URL into the ''URL of repository'' text box (replace with <tt><nowiki>https://svn.kde.org/home/kde/trunk/kdesupport/emerge</nowiki></tt> for read-write access)
*#add <tt>\emerge</tt> to the folder name in the ''Checkout directory'' box and click OK to continue
*#if you picked the read-write access, you will be asked for accepting the SSL certificate of the SVN server (click "Premanent") and then for username and password. For convenience select "Save authentication" checkbox too (the password and cache for the certificates will be saved in <tt>%APPDATA%\Subversion\auth</tt> directory).

After the checkout you should have the directory <tt>%KDEROOT%\emerge</tt>. If you don't, you move your ''emerge'' directory to that location.

==== Installing from the self-extracting archive ====
*Option 3: Get the self-extracting archive from [http://www.winkde.org/pub/kde/ports/win32/emerge/emerge-latest.exe here], unpack it into your KDEROOT directory so that you have a folder %KDEROOT%\emerge.
* This self-extracting archive brings a subversion repository containing the emerge scripts and a python installation with it, so you do not need either of them before starting with emerge.

=== Configure the ''emerge'' tool ===
# Create the directory <tt>%KDEROOT%\etc</tt>.
# Copy the file <tt>%KDEROOT%\emerge\kdesettings-example.bat</tt> as <tt>%KDEROOT%\etc\kdesettings.bat</tt> and change its contents according to your needs. The options are described in the ''rem'' lines in the file itself.

The kdesettings.bat script will be called by the main kdeenv.bat script.

Note 1: '''Be sure that you neither have the msys/bin nor the cygwin/bin in your path. If so you have to definitely remove it from the path.'''

Note 2 '''from a user: The applications gimp, inkscape and graphviz are also a problem. To make sure that there's nothing wrong I stripped my path to contain only what I needed to build.'''

Note 3 '''from another user: be careful when renaming the file to "kdesettings.bat" it is easy to end up with "kdesettings.bat.bat" instead of what you want since Windows(by default) will not show the the file extension part of a file.'''

=== [Optional, Advanced] emergehosts.conf ===
Add a file emergehosts.conf in the <tt>%KDEROOT%\etc</tt> directory. The format of this file is a typical config file with only two entries per section:
The first entry is the ''host'' as mentioned in the portage file for the package. The second entry is called ''replace'' and is the replace string for the host string.

As an example, here is how to checkout all gitorious based repos of the kde-developers group using a push url instead of the anonymous access:
<code>
[qt gitorious]
host: git://gitorious.org/+kde-developers/
replace: git@gitorious.org:+kde-developers/
</code>

As a second example here is how to checkout with a ssh user from a subversion repository:
<code>
[svn.example.com]
host: svn://svn.example.com/
replace: svn+ssh://user@svn.example.com/
</code>

The name of the section doesn't matter and can be used for descriptions.

== Using emerge ==

To use emerge you need to start a console window and point that to <tt>%KDEROOT%\emerge</tt>. For example:

C:
cd \%KDEROOT%\emerge

Then you have to execute

kdeenv.bat

This tells emerge about your environment settings (e.g. paths). It will load your configuration from <tt>%KDEROOT%\etc\kdesettings.bat</tt>. It should not give any error messages, otherwise emerge will not work as expected. The output should look similar to this one (of course with your paths):

C:\kderoot\emerge>kdeenv.bat
kdesettings.bat executed
KDEROOT : C:\kderoot
KDECOMPILER : mingw
KDESVNDIR : C:\kderoot\svn
PYTHONPATH : C:\python27
DOWNLOADDIR : C:\kderoot\download

C:\kderoot\emerge>

Next, if you have configured your kdesettings.bat to use svn+ssh for your subversion checkout, then you need to run:

<code>plink <your-svn-username>@svn.kde.org
plink <your-kde-username>@git.kde.org</code>

This will prompt you to accept the fingerprint of the server, otherwise svn will hang forever when trying to download from the server.

Now you should be able to use emerge. Type

emerge --help

to get some help on usage.

''Note: There is a short path option in kdesettings which you will
need if you want to build Qt in a directory that has a pathlenght of
more then around 5 characters. This problem is due to limitations of the command line length and the Qt build system.''

== Setting up a compiler ==
Currently emerge supports both the MinGW and MS Visual C++ (msvc) compilers. We did not add dependencies for the compilers, so you have to make sure to install a compiler by yourself. There are three ways to set up a compiler for emerge.
We assumed you have set KDECOMPILER variable properly in the <tt>%KDEROOT%\etc\kdesettings.bat</tt>.

In the following sections you can find information on how to install or reuse an existing compiler.

=== Install the MinGW compiler with emerge ===
Let emerge install the MinGW compiler, as soon as emerge needs MinGW it will automatically fetch the correct version for you.

=== Install MS Visual C++ ===
Read [[../MS_Visual_Studio#The_Compiler|here]].

=== Point to an existing MS Visual C++ installation ===
You need to point emerge to an existing msvc installation. This is run automatically for you from kdeenv.bat if configured properly in kdesettings.bat. Check your kdesettings.bat file to know where to set it.

== Installing the base system ==
Once you have emerge and a compiler installed and working, try:
* <tt>emerge --help</tt> for a list of available commands
* <tt>emerge --print-installable</tt> to get a list of available packages
* <tt>emerge --print-installed</tt> to get a list of currently installed packages
Further options are described below.

You are now ready to start building KDE, it is recommended to do so progressively, relying on emerge to automatically resolve the required dependencies at each set step:

* Enter <tt>emerge qt</tt>. This will fetch and install Windows versions of numerous UNIX-like utilities and libraries, then checkout, compile and install Qt. This will take several hours.
* Enter <tt>emerge kdelibs</tt>. This will checkout, compile and install the required kdesupport modules and then kdelibs.
* Enter <tt>emerge kdebase-apps</tt>. This will checkout, compile and install kdebase-runtime, and kdebase-apps

You will now have successfully installed a base KDE system and can now install other KDE modules as required.

Note that this will install the trunk version of KDE, if you wish to install a particular stable branch then you must prefix the KDE package names with the required version, i.e. <tt>emerge kde-4.5/kdelibs</tt>. You can force emerge to always default to a given branch by setting the <tt>EMERGE_DEFAULTCATEGORY</tt> variable in your kdesettings.bat file. You should not mix kde packages from different branches.

It is strongly recommended you do not choose to manually install any of the utilities and libraries yourself, as you may install the wrong version and cause installation failures. Instead allow emerge to resolve the dependencies for you.

Every time you want to update or install a package, you should first update your emerge checkout (simply run emerge --update emerge) to ensure you are using the latest package recipies.

== What emerge does ==
'''emerge ''packageName'' ''' performs the separate actions <tt>--fetch</tt>, <tt>--unpack</tt>, <tt>--compile</tt>, <tt>--install</tt>, <tt>--manifest</tt>, and <tt>--qmerge</tt>.

The <tt>--fetch</tt> action will retrieve either a binary or the source code for the package:
* If a binary package, this will be downloaded into the <tt>DOWNLOADDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\download</tt>.
* If a non-KDE source package, the source repository will be checked-out into <tt>%DOWNLOADDIR%\svn-src</tt>, e.g. Qt source may be found in <tt>C:\kderoot\download\svn-src\qt</tt>.
* If a KDE source package from the <tt>svn.kde.org</tt> repository, then the source will be checked-out into the <tt>KDESVNDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\svn</tt>.

== ''emerge'' command line options and settings ==
There are some options that can be used when building with ''emerge''.

{| border="0" cellpadding="2"
!Command line switch
!Command line argument
!
!Description
|-valign="top"
|<tt>-v</tt>
|<tt>EMERGE_VERBOSE</tt>
|width="5%"|
|This option sets the verbosity level. Currently the highest verbosity level is 3 (<tt>-v -v -v</tt>). A verbosity level of 0 should give no output and equals to <tt>-q</tt>. You can set <tt>EMERGE_VERBOSE=3</tt> instead in the environment of the commandline or within your <tt>kdesettings.bat</tt> file.
|-valign="top"
|<tt>--offline</tt>
|
|
|This option suppresses the update step of the local tree - which needs some time. Be aware though that you have to have existing sources already if you want to use this option.
|-valign="top"
|<tt>-t</tt>
|<tt>EMERGE_BUILDTESTS</tt>
|
|This option enables or disables KDE4 buildtests for KDE modules. Other packages will not change. Use <tt>EMERGE_BUILDTESTS=True</tt> or <tt>=False</tt>.
|-valign="top"
|<tt>--print-targets</tt>
|
|
|This option will display all "targets" a certain package has. Normally targets are fixed releases or different branches. They are defined in the portage file.
|-valign="top"
|<tt>--target=TARGET</tt>
|
|
|This sets a specific target for this package. If not added, the default target is used, which can be checked by looking at the output of '''--print-targets'''.
|-valign="top"
|<tt>-i</tt>
|
|
|This option ignores that a package is already installed. It builds it completely new, but keeps the dependencies.
|-valign="top"
|<tt>--update</tt>
|
|
|This option ignores that a package is already installed but doesn't cleanup an already existing build directory. Thus you will only rebuild files that have changed since the last build.
|}

== Hints ==
=== Updating packages ===
*Once you have ''packagename'' built, type <code>emerge --update packagename</code> to update <tt>packagename</tt> from the Subversion and compile it without removing the build dir or <code>emerge --update-all</code> to update all packages that can be rebuild (they are rebuild with --update).

=== General setup ===
For Fine Tuning see here:
[[Projects/KDE_on_Windows/Installation#Fine-tuning|Fine-tuning]]

== Notes ==

''emerge'' can mostly cooperate with the [[Projects/KDE_on_Windows/Installation#KDE_Installer_for_Windows|kdewin-installer]] but we're currently still working on some packages which are packaged in a wrong way.
It is not recommended to use another layout then '''installer''' for '''directory_layout''' in the '''kdesettings.bat''' anymore (see that file for more detailed information).

''emerge'' creates lots of files in '''\kderoot\tmp''' during build.
After a package is successfully installed
(check '''\kderoot\etc\portage\installed''' or the directory '''\kderoot\manifest\'''), you can delete its temporary directory.

Windows ''emerge'' is derived from the Gentoo portage system, but we are currently not enforcing compatibility. If you have questions about that please contact us at the channel #kde-windows on irc.freenode.net.

last reviewed by [[User:SaroEngels|SaroEngels]] 22:25, 4 November 2010 (UTC)

==Vista issues==
*[[User:Jstaniek|jstaniek]] 12:02, 15 January 2008 (CET): UAC has infamous heuristics that make programs like patch.exe treat as installers and try to run them with admin rights (!). This heuristics can be tricked by renaming patch.exe to something like pch.exe ([http://nevali.net/2007/01/update-workaround-for-the-cygwin-uac-problem/ example]) but we did not want to add item to our infrastructure. Instead it is possibleto turn off the heuristics (see the screenshot [http://theinvisiblethings.blogspot.com/2007/02/running-vista-every-day.html here in the security blog calling the heuristics 'severe hole in the design of UAC']). If you happen to disable the UAC, as many annoyed users and devs do (msvc demands admin rights anyway!), patch.exe should already work for you as in older Windows. Alternatively you may want to disable UAC [http://www.howtogeek.com/howto/windows-vista/disable-user-account-controluac-for-administrators-only/ for admins only], but this makes no sense if you are the only user of your machine and use only the admin account.
* [http://ben.versionzero.org/wiki/Fixing_the_way_Vista_Auto-detects_Installers This wiki page] lists instructions on how to use program manifest to disable privilege elevation for a single binary and makes patch play nice with UAC. This [https://bugs.kde.org/show_bug.cgi?id=186712 should] eventually be integrated to emerge scripts.

[[Category:MS Windows]]

Development/Tutorials/Text-To-Speech

2011-03-25T02:02:42Z

Wrohdewald: fix link to the speech API

== What is Text to Speech? ==

Jovie (previously called ktts in KDE <= 4.4) -- is a subsystem within the KDE desktop for conversion of text to audible speech. Jovie is currently under development and aims to become the standard subsystem for all KDE applications to provide speech output.

== How does it work? ==

Applications send text they wish spoken to Jovie via D-Bus. For example, in a terminal window, you can type the following commands to start Jovie and speak "Hello World".

<pre># Start Jovie (if not already running)
jovie
# Send "Hello World" to KTTSD for speaking in English.
qdbus org.kde.KSpeech /KSpeech say "Hello World" 0</pre>

=== Using speech in your application ===

The above example shows how to play with speech via command-line, but to use it inside your application you'll likely want to use the dbus interface programmatically. It's defined in kdelibs/interfaces/kspeech/org.kde.KSpeech.xml and can be used in your application by putting the following in your CMakeLists.txt:

<pre>qt4_add_dbus_interfaces(my_SRCS ${KDE4_DBUS_INTERFACES_DIR}/org.kde.KSpeech.xml)</pre>

Then in the source file you want to use speech in, #include <kspeech.h> to get some of the enumerations needed (i.e. KSpeech::soPlainText). Finally, define an object of type org::kde::KSpeech* and use it like so:

<pre>org::kde::KSpeech* kspeech = new org::kde::Kspeech("org.kde.kttsd", "/KSpeech", QDbusConnection::sessionBus());
kspeech->setApplicationName("myappname");
kspeech->say("text to speak", KSpeech::soPlainText);</pre>

=== The KSpeech API ===
For a complete description of these and other commands, see the [http://api.kde.org/4.x-api/kdelibs-apidocs/interfaces/kspeech/html/index.html KDE Text-to-Speech API.]

Jovie takes care of sending the text to speech-dispatcher. Jovie is not a speech synthesis engine itself. You must install one of the compatible speech engines. Speech-dispatcher is designed with a plugin architecture that makes it easy to write new plugins for other speech engines.

== Why? Who needs it? ==

Jovie provides a common interface for all KDE applications to use for speaking. Programmers need not concern themselves with the details of the particular speech synthesis engine(s) used.

=== User Features ===

* Speak any text from the clipboard.
* Speak any plain text file.
* Speak all or any portion of a text file from Kate, including instances where Kate is embedded in another application.
* Speak all or any portion of an HTML page from Konqueror.
* Use as the speech backend for KMouth
* Speak KDE notifications (KNotify).
* Speech is spoken via speech-dispatcher, so any speech-dispatcher backend can be used (espeak, festival, etc.)
* User-configurable filters for substituting misspoken words, choosing speech synthesizers, and transforming XHMTL/XML documents.

=== Programmer Features ===

* Priority system for screen reader outputs, warnings and messages, while still playing regular texts.
* Permit generation of speech from the command line (or via shell scripts) using the KDE DCOP utilities.
* Provide a lightweight and easily usable interface for applications to generate speech output.
* Applications need not be concerned about contention over the speech device.
* FUTURE: Provide support for speech markup languages, such as VoiceXML, Sable, Java Speech Markup Language (JSML), and Speech Markup Meta-language (SMML).
* FUTURE: Provide limited support for embedded speech markers.
* Asynchronous to prevent system blocking.

It is hoped that more programmers will begin adding speech capabilities to their KDE programs using Jovie.

=== Different parts ===
Jovie actually consists of a few programs:

==== Jovie ====
The KDE Text-to-Speech system, a system tray application that provides TTS support to KDE applications. Applications initiate TTS by making D-Bus calls to Jovie.

==== kcmkttsd ====
A KControl module for configuring the Text to Speech System. kcmkttsd runs in the KDE Control Center or start it with the command "kcmshell4 kcmkttsd" or by choosing "configure" from Jovie system tray icon's menu.

==== ktexteditor_kttsd ====
A plugin for the KDE Advanced Text Editor that permits you to speak an entire text file or any portion of a file.

==== libkhtmlkttsdplugin ====
A plugin for Konqueror that permits you to speak all or any portion of an HTML web page.

== Requirements ==

* KDE 4.4 or later.
* speech-dispatcher version 0.6.7 or later.
* A speech synthesizer such as espeak, festival, or flite.

Getting Started/Build/Windows/emerge

2011-01-14T11:46:04Z

Wrohdewald: what to do when emerge qt hangs

''emerge'' is a tool to build the KDE sources and its third-party requirements on MS Windows. It is the '''easy''' way to build KDE on MS Windows.

== Introduction ==
Emerge is a tool that can build the different parts of KDE and its dependencies under Windows. We created this tool to automate and simplify the build process under Windows. We try to build all packages that we offer in the KDE installer with emerge. That has some advantages for us:
* it is easy for people to join us:
Before emerge it was quite some work to set a system up for development. There were some quirks, which were documented in some mailing lists, but you had to remember them or you ran into an already solved problem again, etc.
Now to get a development machine you need a Windows computer, need to install Python and Subversion and do the emerge checkout. Then execute emerge to build what you want to build. This is easy for developers coming from Windows to KDE, and also for KDE developers coming to Windows.
* it is easy for us to do (nightly/continuous/release/reproducable/...) builds:
With emerge you can build the whole software stack (low-level libs, Qt, kdelibs, things above that) with only one command. You can start that build, and some hours later you can check if it worked, or if something broke. So we can spot problems easier and earlier. We can also start with a "naked" Windows computer without any other installed software and bootstrap kde on it. That ensures, that no hidden dependencies on some pieces of software sneak in, because then the builds on a "naked" computer would break and show the problem.
* it is easier to collaborate:
We can test the same emerge build description for a package on different Windows versions/computers before we do binary releases. People can also add build descriptions for new packages to the Subversion repository.

This emerge tool was inspired by the Gentoo emerge tool.

== Set up the environment ==
=== Root directory ===
Create a directory if possible in your harddrive's root e.g. C:\kderoot or D:\kderoot (You will need this PATH later). This directory will contain the whole kde installation later. We will refer to it as %KDEROOT%.

=== Python interpreter ===
<tt>emerge.bat</tt> invokes an <tt>emerge.py</tt> script written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] programming language, so you first need to [http://www.python.org/download/ install the Python 2.7 Interpreter]. The ''python'' installation directory will be added to the PATH later by <tt>%KDEROOT%\etc\kdesettings.bat</tt> script.

=== Subversion client ===
The latest source code for Windows ''emerge'' and the rest of KDE is stored in a repository created and managed using the [http://subversion.tigris.org/ Subversion] version control tool, abbreviated svn. You need a Subversion client for the first checkout of emerge. There are at least two applications:
*a command line client, available at [http://subversion.apache.org/packages.html subversion.apache.org], aimed at developers or power users accustomed with the command line,
*a GUI program like [http://tortoisesvn.tigris.org/ TortoiseSVN], optional, useful for displaying differences between various versions of files in the repository in a graphical way.

Emerge uses its own Subversion client for checking out all KDE source code. However it is not quite up to date: From August 2009. You can find it in %KDEROOT%\dev-utils\svn\bin. It will be used by emerge even if you have another svn executable installed.

Note 1: If you experience problems with the checkout of Qt (svn doesn't work correctly) please remove any other svn binaries out of the path that you do have. '''The different versions of the Apache portable runtime (APR) are incompatible!'''

Note 2: Most source files in the KDE Subversion repository have Unix line endings, and svn will not convert them to Windows line endings. This is fine for emerge, but the standard Windows editor might not show those files correctly. You can use another editor like vim (http://www.vim.org).

=== Getting the ''emerge'' tool ===
The source code of the ''emerge'' tool and the recipes for creating KDE packages are located at <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt>, which is an URL based on the Subversion-specific ''svn'' protocol.

You need to check out the source code from the ''emerge'' Subversion directory into a new directory below your root directory (the root directory is normally called %KDEROOT% here) or get it inside a self extracting archive (not tested yet).

==== Check out using the 'svn' command ====

*Option 1: With the ''svn'' command line tool, you can accomplish this with the following commands:<pre>cd %KDEROOT%</pre>
**if you will only use anonymous (read-only) access to the KDE svn repository:<pre>svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
**or, if you plan to use write access (commit) to the KDE svn repository
***via https:<pre>svn co --username yourusername https://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
***via a [[Getting_Started/Build/KDE4/Windows/subversion|puTTY tunnel]] using your existing account & OpenSSH private key: <pre>svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>

This would result with:

Error validating server certificate for '<nowiki>https://svn.kde.org:443</nowiki>':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: svn.kde.org
- Valid: from Wed, 11 May 2005 09:08:21 GMT until Sat, 09 May 2015 09:08:21 GMT
- Issuer: SVN, KDE e.V., Nuernberg, Bavaria, DE
- Fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
(R)eject, accept (t)emporarily or accept (p)ermanently?

enter ''p'' here to permanently accept the certificate:

Authentication realm: <<nowiki>https://svn.kde.org:443</nowiki>> KDE SVN account
Password for 'yourusername': ***************
A emerge\kdeenv.bat
A emerge\portage
A emerge\portage\kdesupport
[....]

The password and cache for the certificates is saved in <tt>%APPDATA%\Subversion\auth</tt> directory.

==== Check out using the TortoiseSVN ====

*Option 2: If you use TortoiseSVN:
*#right-click on your %KDEROOT% folder and select ''SVN Checkout...'' command from the context menu,
*#paste <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt> URL into the ''URL of repository'' text box (replace with <tt><nowiki>https://svn.kde.org/home/kde/trunk/kdesupport/emerge</nowiki></tt> for read-write access)
*#add <tt>\emerge</tt> to the folder name in the ''Checkout directory'' box and click OK to continue
*#if you picked the read-write access, you will be asked for accepting the SSL certificate of the SVN server (click "Premanent") and then for username and password. For convenience select "Save authentication" checkbox too (the password and cache for the certificates will be saved in <tt>%APPDATA%\Subversion\auth</tt> directory).

After the checkout you should have the directory <tt>%KDEROOT%\emerge</tt>. If you don't, you move your ''emerge'' directory to that location.

==== Installing from the self-extracting archive ====
*Option 3: Get the self-extracting archive from [http://www.winkde.org/pub/kde/ports/win32/emerge/emerge-latest.exe here], unpack it into your KDEROOT directory so that you have a folder %KDEROOT%\emerge.
* This self-extracting archive brings a subversion repository containing the emerge scripts and a python installation with it, so you do not need either of them before starting with emerge.

=== Configure the ''emerge'' tool ===
# Create the directory <tt>%KDEROOT%\etc</tt>.
# Copy the file <tt>%KDEROOT%\emerge\kdesettings-example.bat</tt> as <tt>%KDEROOT%\etc\kdesettings.bat</tt> and change its contents according to your needs. The options are described in the ''rem'' lines in the file itself.

The kdesettings.bat script will be called by the main kdeenv.bat script.

Note 1: '''Be sure that you neither have the msys/bin nor the cygwin/bin in your path. If so you have to definitely remove it from the path.'''

Note 2 '''from a user: The applications gimp, inkscape and graphviz are also a problem. To make sure that there's nothing wrong I stripped my path to contain only what I needed to build.'''

Note 3 '''from another user: be careful when renaming the file to "kdesettings.bat" it is easy to end up with "kdesettings.bat.bat" instead of what you want since Windows(by default) will not show the the file extension part of a file.'''

=== [Optional, Advanced] emergehosts.conf ===
Add a file emergehosts.conf in the <tt>%KDEROOT%\etc</tt> directory. The format of this file is a typical config file with only two entries per section:
The first entry is the ''host'' as mentioned in the portage file for the package. The second entry is called ''replace'' and is the replace string for the host string.

As an example, here is how to checkout all gitorious based repos of the kde-developers group using a push url instead of the anonymous access:
<code>
[qt gitorious]
host: git://gitorious.org/+kde-developers/
replace: git@gitorious.org:+kde-developers/
</code>

As a second example here is how to checkout with a ssh user from a subversion repository:
<code>
[svn.example.com]
host: svn://svn.example.com/
replace: svn+ssh://user@svn.example.com/
</code>

The name of the section doesn't matter and can be used for descriptions.

== Using emerge ==

To use emerge you need to start a console window and point that to <tt>%KDEROOT%\emerge</tt>. For example:

C:
cd \%KDEROOT%\emerge

Then you have to execute

kdeenv.bat

This tells emerge about your environment settings (e.g. paths). It will load your configuration from <tt>%KDEROOT%\etc\kdesettings.bat</tt>. It should not give any error messages, otherwise emerge will not work as expected. The output should look similar to this one (of course with your paths):

C:\kderoot\emerge>kdeenv.bat
kdesettings.bat executed
KDEROOT : C:\kderoot
KDECOMPILER : mingw
KDESVNDIR : C:\kderoot\svn
PYTHONPATH : C:\python27
DOWNLOADDIR : C:\kderoot\download

C:\kderoot\emerge>

Next, if you have configured your kdesettings.bat to use svn+ssh for your subversion checkout, then you need to run:

<code>plink <your-svn-username>@svn.kde.org
plink <your-kde-username>@git.kde.org</code>

This will prompt you to accept the fingerprint of the server, otherwise svn will hang forever when trying to download from the server.

Now you should be able to use emerge. Type

emerge --help

to get some help on usage.

''Note: There is a short path option in kdesettings which you will
need if you want to build Qt in a directory that has a pathlenght of
more then around 5 characters. This problem is due to limitations of the command line length and the Qt build system.''

== Setting up a compiler ==
Currently emerge supports both the MinGW and MS Visual C++ (msvc) compilers. We did not add dependencies for the compilers, so you have to make sure to install a compiler by yourself. There are three ways to set up a compiler for emerge.
We assumed you have set KDECOMPILER variable properly in the <tt>%KDEROOT%\etc\kdesettings.bat</tt>.

In the following sections you can find information on how to install or reuse an existing compiler.

=== Install the MinGW compiler with emerge ===
Let emerge install the MinGW compiler, as soon as emerge needs MinGW it will automatically fetch the correct version for you.

=== Install MS Visual C++ ===
Read [[../MS_Visual_Studio#The_Compiler|here]].

=== Point to an existing MS Visual C++ installation ===
You need to point emerge to an existing msvc installation. This is run automatically for you from kdeenv.bat if configured properly in kdesettings.bat. Check your kdesettings.bat file to know where to set it.

== Installing the base system ==
Once you have emerge and a compiler installed and working, try:
* <tt>emerge --help</tt> for a list of available commands
* <tt>emerge --print-installable</tt> to get a list of available packages
* <tt>emerge --print-installed</tt> to get a list of currently installed packages
Further options are described below.

You are now ready to start building KDE, it is recommended to do so progressively, relying on emerge to automatically resolve the required dependencies at each set step:

* Enter <tt>emerge qt</tt>. This will fetch and install Windows versions of numerous UNIX-like utilities and libraries, then checkout, compile and install Qt. This will take several hours.
* Enter <tt>emerge kdelibs</tt>. This will checkout, compile and install the required kdesupport modules and then kdelibs.
* Enter <tt>emerge kdebase-apps</tt>. This will checkout, compile and install kdebase-runtime, and kdebase-apps

Note: '''There is a known problem with fetching qt sources. If emerge hangs, you should disable EMERGE_LOG_DIR in kdesettings.bat, execute <tt>emerge --fetch qt</tt> and re-enable EMERGE_LOG_DIR.'''

You will now have successfully installed a base KDE system and can now install other KDE modules as required.

Note that this will install the trunk version of KDE, if you wish to install a particular stable branch then you must prefix the KDE package names with the required version, i.e. <tt>emerge kde-4.5/kdelibs</tt>. You can force emerge to always default to a given branch by setting the <tt>EMERGE_DEFAULTCATEGORY</tt> variable in your kdesettings.bat file. You should not mix kde packages from different branches.

It is strongly recommended you do not choose to manually install any of the utilities and libraries yourself, as you may install the wrong version and cause installation failures. Instead allow emerge to resolve the dependencies for you.

Every time you want to update or install a package, you should first update your emerge checkout (simply run emerge --update emerge) to ensure you are using the latest package recipies.

== What emerge does ==
'''emerge ''packageName'' ''' performs the separate actions <tt>--fetch</tt>, <tt>--unpack</tt>, <tt>--compile</tt>, <tt>--install</tt>, <tt>--manifest</tt>, and <tt>--qmerge</tt>.

The <tt>--fetch</tt> action will retrieve either a binary or the source code for the package:
* If a binary package, this will be downloaded into the <tt>DOWNLOADDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\download</tt>.
* If a non-KDE source package, the source repository will be checked-out into <tt>%DOWNLOADDIR%\svn-src</tt>, e.g. Qt source may be found in <tt>C:\kderoot\download\svn-src\qt</tt>.
* If a KDE source package from the <tt>svn.kde.org</tt> repository, then the source will be checked-out into the <tt>KDESVNDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\svn</tt>.

== ''emerge'' command line options and settings ==
There are some options that can be used when building with ''emerge''.

{| border="0" cellpadding="2"
!Command line switch
!Command line argument
!
!Description
|-valign="top"
|<tt>-v</tt>
|<tt>EMERGE_VERBOSE</tt>
|width="5%"|
|This option sets the verbosity level. Currently the highest verbosity level is 3 (<tt>-v -v -v</tt>). A verbosity level of 0 should give no output and equals to <tt>-q</tt>. You can set <tt>EMERGE_VERBOSE=3</tt> instead in the environment of the commandline or within your <tt>kdesettings.bat</tt> file.
|-valign="top"
|<tt>--offline</tt>
|
|
|This option suppresses the update step of the local tree - which needs some time. Be aware though that you have to have existing sources already if you want to use this option.
|-valign="top"
|<tt>-t</tt>
|<tt>EMERGE_BUILDTESTS</tt>
|
|This option enables or disables KDE4 buildtests for KDE modules. Other packages will not change. Use <tt>EMERGE_BUILDTESTS=True</tt> or <tt>=False</tt>.
|-valign="top"
|<tt>--print-targets</tt>
|
|
|This option will display all "targets" a certain package has. Normally targets are fixed releases or different branches. They are defined in the portage file.
|-valign="top"
|<tt>--target=TARGET</tt>
|
|
|This sets a specific target for this package. If not added, the default target is used, which can be checked by looking at the output of '''--print-targets'''.
|-valign="top"
|<tt>-i</tt>
|
|
|This option ignores that a package is already installed. It builds it completely new, but keeps the dependencies.
|-valign="top"
|<tt>--update</tt>
|
|
|This option ignores that a package is already installed but doesn't cleanup an already existing build directory. Thus you will only rebuild files that have changed since the last build.
|}

== Hints ==
=== Updating packages ===
*Once you have ''packagename'' built, type <code>emerge --update packagename</code> to update <tt>packagename</tt> from the Subversion and compile it without removing the build dir or <code>emerge --update-all</code> to update all packages that can be rebuild (they are rebuild with --update).

=== General setup ===
For Fine Tuning see here:
[[Projects/KDE_on_Windows/Installation#Fine-tuning|Fine-tuning]]

== Notes ==

''emerge'' can mostly cooperate with the [[Projects/KDE_on_Windows/Installation#KDE_Installer_for_Windows|kdewin-installer]] but we're currently still working on some packages which are packaged in a wrong way.
It is not recommended to use another layout then '''installer''' for '''directory_layout''' in the '''kdesettings.bat''' anymore (see that file for more detailed information).

''emerge'' creates lots of files in '''\kderoot\tmp''' during build.
After a package is successfully installed
(check '''\kderoot\etc\portage\installed''' or the directory '''\kderoot\manifest\'''), you can delete its temporary directory.

Windows ''emerge'' is derived from the Gentoo portage system, but we are currently not enforcing compatibility. If you have questions about that please contact us at the channel #kde-windows on irc.freenode.net.

last reviewed by [[User:SaroEngels|SaroEngels]] 22:25, 4 November 2010 (UTC)

==Vista issues==
*[[User:Jstaniek|jstaniek]] 12:02, 15 January 2008 (CET): UAC has infamous heuristics that make programs like patch.exe treat as installers and try to run them with admin rights (!). This heuristics can be tricked by renaming patch.exe to something like pch.exe ([http://nevali.net/2007/01/update-workaround-for-the-cygwin-uac-problem/ example]) but we did not want to add item to our infrastructure. Instead it is possibleto turn off the heuristics (see the screenshot [http://theinvisiblethings.blogspot.com/2007/02/running-vista-every-day.html here in the security blog calling the heuristics 'severe hole in the design of UAC']). If you happen to disable the UAC, as many annoyed users and devs do (msvc demands admin rights anyway!), patch.exe should already work for you as in older Windows. Alternatively you may want to disable UAC [http://www.howtogeek.com/howto/windows-vista/disable-user-account-controluac-for-administrators-only/ for admins only], but this makes no sense if you are the only user of your machine and use only the admin account.
* [http://ben.versionzero.org/wiki/Fixing_the_way_Vista_Auto-detects_Installers This wiki page] lists instructions on how to use program manifest to disable privilege elevation for a single binary and makes patch play nice with UAC. This [https://bugs.kde.org/show_bug.cgi?id=186712 should] eventually be integrated to emerge scripts.

[[Category:MS Windows]]

Getting Started/Build/Windows/emerge

2011-01-08T10:34:26Z

Wrohdewald: typo

''emerge'' is a tool to build the KDE sources and its third-party requirements on MS Windows. It is the '''easy''' way to build KDE on MS Windows.

== Introduction ==
Emerge is a tool that can build the different parts of KDE and its dependencies under Windows. We created this tool to automate and simplify the build process under Windows. We try to build all packages that we offer in the KDE installer with emerge. That has some advantages for us:
* it is easy for people to join us:
Before emerge it was quite some work to set a system up for development. There were some quirks, which were documented in some mailing lists, but you had to remember them or you ran into an already solved problem again, etc.
Now to get a development machine you need a Windows computer, need to install Python and Subversion and do the emerge checkout. Then execute emerge to build what you want to build. This is easy for developers coming from Windows to KDE, and also for KDE developers coming to Windows.
* it is easy for us to do (nightly/continuous/release/reproducable/...) builds:
With emerge you can build the whole software stack (low-level libs, Qt, kdelibs, things above that) with only one command. You can start that build, and some hours later you can check if it worked, or if something broke. So we can spot problems easier and earlier. We can also start with a "naked" Windows computer without any other installed software and bootstrap kde on it. That ensures, that no hidden dependencies on some pieces of software sneak in, because then the builds on a "naked" computer would break and show the problem.
* it is easier to collaborate:
We can test the same emerge build description for a package on different Windows versions/computers before we do binary releases. People can also add build descriptions for new packages to the Subversion repository.

This emerge tool was inspired by the Gentoo emerge tool.

== Set up the environment ==
=== Root directory ===
Create a directory if possible in your harddrive's root e.g. C:\kderoot or D:\kderoot (You will need this PATH later). This directory will contain the whole kde installation later. We will refer to it as %KDEROOT%.

=== Python interpreter ===
<tt>emerge.bat</tt> invokes an <tt>emerge.py</tt> script written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] programming language, so you first need to [http://www.python.org/download/ install the Python 2.7 Interpreter]. The ''python'' installation directory will be added to the PATH later by <tt>%KDEROOT%\etc\kdesettings.bat</tt> script.

=== Subversion client ===
The latest source code for Windows ''emerge'' and the rest of KDE is stored in a repository created and managed using the [http://subversion.tigris.org/ Subversion] version control tool, abbreviated svn. You need a Subversion client for the first checkout of emerge. There are at least two applications:
*a command line client, available at [http://subversion.apache.org/packages.html subversion.apache.org], aimed at developers or power users accustomed with the command line,
*a GUI program like [http://tortoisesvn.tigris.org/ TortoiseSVN], optional, useful for displaying differences between various versions of files in the repository in a graphical way.

Emerge uses its own Subversion client for checking out all KDE source code. However it is not quite up to date: From August 2009. You can find it in %KDEROOT%\dev-utils\svn\bin. It will be used by emerge even if you have another svn executable installed.

Note 1: If you experience problems with the checkout of Qt (svn doesn't work correctly) please remove any other svn binaries out of the path that you do have. '''The different versions of the Apache portable runtime (APR) are incompatible!'''

Note 2: Most source files in the KDE Subversion repository have Unix line endings, and svn will not convert them to Windows line endings. This is fine for emerge, but the standard Windows editor might not show those files correctly. You can use another editor like vim (http://www.vim.org).

=== Getting the ''emerge'' tool ===
The source code of the ''emerge'' tool and the recipes for creating KDE packages are located at <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt>, which is an URL based on the Subversion-specific ''svn'' protocol.

You need to check out the source code from the ''emerge'' Subversion directory into a new directory below your root directory (the root directory is normally called %KDEROOT% here) or get it inside a self extracting archive (not tested yet).

==== Check out using the 'svn' command ====

*Option 1: With the ''svn'' command line tool, you can accomplish this with the following commands:<pre>cd %KDEROOT%</pre>
**if you will only use anonymous (read-only) access to the KDE svn repository:<pre>svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
**or, if you plan to use write access (commit) to the KDE svn repository
***via https:<pre>svn co --username yourusername https://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
***via a [[Getting_Started/Build/KDE4/Windows/subversion|puTTY tunnel]] using your existing account & OpenSSH private key: <pre>svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>

This would result with:

Error validating server certificate for '<nowiki>https://svn.kde.org:443</nowiki>':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: svn.kde.org
- Valid: from Wed, 11 May 2005 09:08:21 GMT until Sat, 09 May 2015 09:08:21 GMT
- Issuer: SVN, KDE e.V., Nuernberg, Bavaria, DE
- Fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
(R)eject, accept (t)emporarily or accept (p)ermanently?

enter ''p'' here to permanently accept the certificate:

Authentication realm: <<nowiki>https://svn.kde.org:443</nowiki>> KDE SVN account
Password for 'yourusername': ***************
A emerge\kdeenv.bat
A emerge\portage
A emerge\portage\kdesupport
[....]

The password and cache for the certificates is saved in <tt>%APPDATA%\Subversion\auth</tt> directory.

==== Check out using the TortoiseSVN ====

*Option 2: If you use TortoiseSVN:
*#right-click on your %KDEROOT% folder and select ''SVN Checkout...'' command from the context menu,
*#paste <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt> URL into the ''URL of repository'' text box (replace with <tt><nowiki>https://svn.kde.org/home/kde/trunk/kdesupport/emerge</nowiki></tt> for read-write access)
*#add <tt>\emerge</tt> to the folder name in the ''Checkout directory'' box and click OK to continue
*#if you picked the read-write access, you will be asked for accepting the SSL certificate of the SVN server (click "Premanent") and then for username and password. For convenience select "Save authentication" checkbox too (the password and cache for the certificates will be saved in <tt>%APPDATA%\Subversion\auth</tt> directory).

After the checkout you should have the directory <tt>%KDEROOT%\emerge</tt>. If you don't, you move your ''emerge'' directory to that location.

==== Installing from the self-extracting archive ====
*Option 3: Get the self-extracting archive from [http://www.winkde.org/pub/kde/ports/win32/emerge/emerge-latest.exe here], unpack it into your KDEROOT directory so that you have a folder %KDEROOT%\emerge.
* This self-extracting archive brings a subversion repository containing the emerge scripts and a python installation with it, so you do not need either of them before starting with emerge.

=== Configure the ''emerge'' tool ===
# Create the directory <tt>%KDEROOT%\etc</tt>.
# Copy the file <tt>%KDEROOT%\emerge\kdesettings-example.bat</tt> as <tt>%KDEROOT%\etc\kdesettings.bat</tt> and change its contents according to your needs. The options are described in the ''rem'' lines in the file itself.

The kdesettings.bat script will be called by the main kdeenv.bat script.

Note 1: '''Be sure that you neither have the msys/bin nor the cygwin/bin in your path. If so you have to definitely remove it from the path.'''

Note 2 '''from a user: The applications gimp, inkscape and graphviz are also a problem. To make sure that there's nothing wrong I stripped my path to contain only what I needed to build.'''

Note 3 '''from another user: be careful when renaming the file to "kdesettings.bat" it is easy to end up with "kdesettings.bat.bat" instead of what you want since Windows(by default) will not show the the file extension part of a file.'''

=== [Optional, Advanced] emergehosts.conf ===
Add a file emergehosts.conf in the <tt>%KDEROOT%\etc</tt> directory. The format of this file is a typical config file with only two entries per section:
The first entry is the ''host'' as mentioned in the portage file for the package. The second entry is called ''replace'' and is the replace string for the host string.

As an example, here is how to checkout all gitorious based repos of the kde-developers group using a push url instead of the anonymous access:
<code>
[qt gitorious]
host: git://gitorious.org/+kde-developers/
replace: git@gitorious.org:+kde-developers/
</code>

As a second example here is how to checkout with a ssh user from a subversion repository:
<code>
[svn.example.com]
host: svn://svn.example.com/
replace: svn+ssh://user@svn.example.com/
</code>

The name of the section doesn't matter and can be used for descriptions.

== Using emerge ==

To use emerge you need to start a console window and point that to <tt>%KDEROOT%\emerge</tt>. For example:

C:
cd \%KDEROOT%\emerge

Then you have to execute

kdeenv.bat

This tells emerge about your environment settings (e.g. paths). It will load your configuration from <tt>%KDEROOT%\etc\kdesettings.bat</tt>. It should not give any error messages, otherwise emerge will not work as expected. The output should look similar to this one (of course with your paths):

C:\kderoot\emerge>kdeenv.bat
kdesettings.bat executed
KDEROOT : C:\kderoot
KDECOMPILER : mingw
KDESVNDIR : C:\kderoot\svn
PYTHONPATH : C:\python27
DOWNLOADDIR : C:\kderoot\download

C:\kderoot\emerge>

Next, if you have configured your kdesettings.bat to use svn+ssh for your subversion checkout, then you need to run:

<code>plink <your-svn-username>@svn.kde.org
plink <your-kde-username>@git.kde.org</code>

This will prompt you to accept the fingerprint of the server, otherwise svn will hang forever when trying to download from the server.

Now you should be able to use emerge. Type

emerge --help

to get some help on usage.

''Note: There is a short path option in kdesettings which you will
need if you want to build Qt in a directory that has a pathlenght of
more then around 5 characters. This problem is due to limitations of the command line length and the Qt build system.''

== Setting up a compiler ==
Currently emerge supports both the MinGW and MS Visual C++ (msvc) compilers. We did not add dependencies for the compilers, so you have to make sure to install a compiler by yourself. There are three ways to set up a compiler for emerge.
We assumed you have set KDECOMPILER variable properly in the <tt>%KDEROOT%\etc\kdesettings.bat</tt>.

In the following sections you can find information on how to install or reuse an existing compiler.

=== Install the MinGW compiler with emerge ===
Let emerge install the MinGW compiler, as soon as emerge needs MinGW it will automatically fetch the correct version for you.

=== Install MS Visual C++ ===
Read [[../MS_Visual_Studio#The_Compiler|here]].

=== Point to an existing MS Visual C++ installation ===
You need to point emerge to an existing msvc installation. This is run automatically for you from kdeenv.bat if configured properly in kdesettings.bat. Check your kdesettings.bat file to know where to set it.

== Installing the base system ==
Once you have emerge and a compiler installed and working, try:
* <tt>emerge --help</tt> for a list of available commands
* <tt>emerge --print-installable</tt> to get a list of available packages
* <tt>emerge --print-installed</tt> to get a list of currently installed packages
Further options are described below.

You are now ready to start building KDE, it is recommended to do so progressively, relying on emerge to automatically resolve the required dependencies at each set step:

* Enter <tt>emerge qt</tt>. This will fetch and install Windows versions of numerous UNIX-like utilities and libraries, then checkout, compile and install Qt. This will take several hours.
* Enter <tt>emerge kdelibs</tt>. This will checkout, compile and install the required kdesupport modules and then kdelibs.
* Enter <tt>emerge kdebase-apps</tt>. This will checkout, compile and install kdebase-runtime, and kdebase-apps

You will now have successfully installed a base KDE system and can now install other KDE modules as required.

Note that this will install the trunk version of KDE, if you wish to install a particular stable branch then you must prefix the KDE package names with the required version, i.e. <tt>emerge kde-4.5/kdelibs</tt>. You can force emerge to always default to a given branch by setting the <tt>EMERGE_DEFAULTCATEGORY</tt> variable in your kdesettings.bat file. You should not mix kde packages from different branches.

It is strongly recommended you do not choose to manually install any of the utilities and libraries yourself, as you may install the wrong version and cause installation failures. Instead allow emerge to resolve the dependencies for you.

Every time you want to update or install a package, you should first update your emerge checkout (simply run emerge --update emerge) to ensure you are using the latest package recipies.

== What emerge does ==
'''emerge ''packageName'' ''' performs the separate actions <tt>--fetch</tt>, <tt>--unpack</tt>, <tt>--compile</tt>, <tt>--install</tt>, <tt>--manifest</tt>, and <tt>--qmerge</tt>.

The <tt>--fetch</tt> action will retrieve either a binary or the source code for the package:
* If a binary package, this will be downloaded into the <tt>DOWNLOADDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\download</tt>.
* If a non-KDE source package, the source repository will be checked-out into <tt>%DOWNLOADDIR%\svn-src</tt>, e.g. Qt source may be found in <tt>C:\kderoot\download\svn-src\qt</tt>.
* If a KDE source package from the <tt>svn.kde.org</tt> repository, then the source will be checked-out into the <tt>KDESVNDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\svn</tt>.

== ''emerge'' command line options and settings ==
There are some options that can be used when building with ''emerge''.

{| border="0" cellpadding="2"
!Command line switch
!Command line argument
!
!Description
|-valign="top"
|<tt>-v</tt>
|<tt>EMERGE_VERBOSE</tt>
|width="5%"|
|This option sets the verbosity level. Currently the highest verbosity level is 3 (<tt>-v -v -v</tt>). A verbosity level of 0 should give no output and equals to <tt>-q</tt>. You can set <tt>EMERGE_VERBOSE=3</tt> instead in the environment of the commandline or within your <tt>kdesettings.bat</tt> file.
|-valign="top"
|<tt>--offline</tt>
|
|
|This option suppresses the update step of the local tree - which needs some time. Be aware though that you have to have existing sources already if you want to use this option.
|-valign="top"
|<tt>-t</tt>
|<tt>EMERGE_BUILDTESTS</tt>
|
|This option enables or disables KDE4 buildtests for KDE modules. Other packages will not change. Use <tt>EMERGE_BUILDTESTS=True</tt> or <tt>=False</tt>.
|-valign="top"
|<tt>--print-targets</tt>
|
|
|This option will display all "targets" a certain package has. Normally targets are fixed releases or different branches. They are defined in the portage file.
|-valign="top"
|<tt>--target=TARGET</tt>
|
|
|This sets a specific target for this package. If not added, the default target is used, which can be checked by looking at the output of '''--print-targets'''.
|-valign="top"
|<tt>-i</tt>
|
|
|This option ignores that a package is already installed. It builds it completely new, but keeps the dependencies.
|-valign="top"
|<tt>--update</tt>
|
|
|This option ignores that a package is already installed but doesn't cleanup an already existing build directory. Thus you will only rebuild files that have changed since the last build.
|}

== Hints ==
=== Updating packages ===
*Once you have ''packagename'' built, type <code>emerge --update packagename</code> to update <tt>packagename</tt> from the Subversion and compile it without removing the build dir or <code>emerge --update-all</code> to update all packages that can be rebuild (they are rebuild with --update).

=== General setup ===
For Fine Tuning see here:
[[Projects/KDE_on_Windows/Installation#Fine-tuning|Fine-tuning]]

== Notes ==

''emerge'' can mostly cooperate with the [[Projects/KDE_on_Windows/Installation#KDE_Installer_for_Windows|kdewin-installer]] but we're currently still working on some packages which are packaged in a wrong way.
It is not recommended to use another layout then '''installer''' for '''directory_layout''' in the '''kdesettings.bat''' anymore (see that file for more detailed information).

''emerge'' creates lots of files in '''\kderoot\tmp''' during build.
After a package is successfully installed
(check '''\kderoot\etc\portage\installed''' or the directory '''\kderoot\manifest\'''), you can delete its temporary directory.

Windows ''emerge'' is derived from the Gentoo portage system, but we are currently not enforcing compatibility. If you have questions about that please contact us at the channel #kde-windows on irc.freenode.net.

last reviewed by [[User:SaroEngels|SaroEngels]] 22:25, 4 November 2010 (UTC)

==Vista issues==
*[[User:Jstaniek|jstaniek]] 12:02, 15 January 2008 (CET): UAC has infamous heuristics that make programs like patch.exe treat as installers and try to run them with admin rights (!). This heuristics can be tricked by renaming patch.exe to something like pch.exe ([http://nevali.net/2007/01/update-workaround-for-the-cygwin-uac-problem/ example]) but we did not want to add item to our infrastructure. Instead it is possibleto turn off the heuristics (see the screenshot [http://theinvisiblethings.blogspot.com/2007/02/running-vista-every-day.html here in the security blog calling the heuristics 'severe hole in the design of UAC']). If you happen to disable the UAC, as many annoyed users and devs do (msvc demands admin rights anyway!), patch.exe should already work for you as in older Windows. Alternatively you may want to disable UAC [http://www.howtogeek.com/howto/windows-vista/disable-user-account-controluac-for-administrators-only/ for admins only], but this makes no sense if you are the only user of your machine and use only the admin account.
* [http://ben.versionzero.org/wiki/Fixing_the_way_Vista_Auto-detects_Installers This wiki page] lists instructions on how to use program manifest to disable privilege elevation for a single binary and makes patch play nice with UAC. This [https://bugs.kde.org/show_bug.cgi?id=186712 should] eventually be integrated to emerge scripts.

[[Category:MS Windows]]

Getting Started/Build/Windows/subversion

2011-01-08T06:27:56Z

Wrohdewald: how to make Pageant automatically reload keys at startup

This article details how a developer can set up the Subversion command line client <tt>svn</tt> and <tt>PuTTY</tt> on MS Windows to enable write access to the KDE Subversion Repository, using your existing SSH credentials from *nix.

==Install PuTTY==
*Install PuTTY
[http://en.wikipedia.org/wiki/PuTTY PuTTY] is a free implementation of SSH for Win32. [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Download] and install PuTTY. Using the Windows install file is the easiest method. As of this writing the current version is [ftp://ftp.chiark.greenend.org.uk/users/sgtatham/putty-latest/x86/putty-0.60-installer.exe putty-0.60-installer.exe].

*Put PuTTY in $PATH
In order for MS Windows to be able to find PuTTY and its related executable files, you need to add their location to your PATH variable. By default, PuTTY will install to C:\Program Files\PuTTY. To edit your PATH (for Windows >= Win2k), Start -> Control Panel -> System -> Advanced -> Environment Variables -> System Variables -> Path -> Edit. Add "C:\Program Files\PuTTY;" to the end of the PATH variable value.

==Enable Existing Key==
*Transfer existing ~\.ssh\id_dsa to Windows
Copy the private ssh key that is associated with your KDE Subversion account to the MS Windows machine. In many cases this will be /home/kde-devel/.ssh/id_dsa. I put mine in C:\Documents and Settings\mark\My Documents.

*Load into PuTTY Key Generator
In order to use your OpenSSH private key, you must first convert it to a PuTTY Private Key (*.ppk). To do this, Start -> All Programs -> PuTTY -> PuTTYgen -> Load. Browse to wherever you saved your private key (id_dsa) and load it.

*Save Private Key
Once the key is loaded, click on 'Save Private Key' to save a copy of the key in a version that PuTTY can use. I saved mine as id_dsa.ppk.

==Enable Pageant==
Pageant is PuTTY's version of sshagent, holding your keys for you so you don't always have to enter your passphrase.

*Start Pageant
Start Pageant Start -> All Programs -> PuTTY -> Pageant. An icon will appear in your system tray. Right-click in the icon, then select view keys. If your key isn't listed, click on 'Add Key' and add the id_dsa.ppk key you created earlier.

*Add Pageant to Startup group
I suggest adding Pageant to the MS Windows Startup group so that it launches every time you start Windows.

Pageant does not automatically reload keys when it is started. See the Pageant Help, there is a chapter "Making Pageant automatically load keys on startup".

==Configure Subversion PuTTY Tunnel==
We need to create a new type of tunnel: subversion over PuTTY (svn+ssh://).
We call the tunnel ssh for consistency with the Linux world. We could
just as well call it putty and then use svn+putty everywhere. The default configuration for emerge (kdesettings-example.bat) uses ssh.

*We create this tunnel in the Subversion configuration file. Open <tt>%appdata%\Subversion\config</tt>

*In [Tunnels] section, we create our new tunnel by adding a line (use \\ for backslash):
<tt>ssh = plink -ssh -C -i c:\\path\\to\\id_dsa.ppk -agent <svnaccountname>@svn.kde.org</tt>

<tt>plink</tt> is the command line version of PuTTY. <tt>-ssh</tt> tells PuTTY to use SSH protocol. <tt>-C</tt> turns on compression. <tt>-i</tt> is the path to your private key. <tt>-agent</tt> tells PuTTY to try to use Pageant.

As an alternative to editing the Subversion configuration file, you can define the environment variable SVN_SSH just like you would define the ssh tunnel (untested).

Now open PuTTY (Start -> All Programs -> PuTTY -> PuTTY) and open a connection to <tt>svn.kde.org</tt> it will ask you if you accept the server id. Select yes,
a terminal window with an error message may appear, this is normal. If prompted, enter your username. It may then throw errors, but don't worry. The authentication process between your computer and svn.kde.org is now complete, and you may close the PuTTY session.

==Repository Access==
*The repository can now be accessed by using the svn+ssh:// tunnel, e.g. <tt>
C:\KDE4> svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</tt>

==Setup Git==
Install Git by either running [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge 'emerge git' ] or by downloading the zip yourself from the [http://code.google.com/p/msysgit/ msysgit page].

After installation you will need to setup the following environment variables (as shown above):
*Create a new variable HOME with value %USERPROFILE%. This will be expanded to the path of your account automatically.
*Create a new variable GIT_SSH with value: plink.exe

Git is now completely setup to follow the steps in the [http://techbase.kde.org/Getting_Started/Sources/KDE_git-tutorial KDE Git tutorial]

Getting Started/Build/Windows/subversion

2011-01-07T16:21:37Z

Wrohdewald: SVN_SSH as an alternative to editing the svn config file

This article details how a developer can set up the Subversion command line client <tt>svn</tt> and <tt>PuTTY</tt> on MS Windows to enable write access to the KDE Subversion Repository, using your existing SSH credentials from *nix.

==Install PuTTY==
*Install PuTTY
[http://en.wikipedia.org/wiki/PuTTY PuTTY] is a free implementation of SSH for Win32. [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Download] and install PuTTY. Using the Windows install file is the easiest method. As of this writing the current version is [ftp://ftp.chiark.greenend.org.uk/users/sgtatham/putty-latest/x86/putty-0.60-installer.exe putty-0.60-installer.exe].

*Put PuTTY in $PATH
In order for MS Windows to be able to find PuTTY and its related executable files, you need to add their location to your PATH variable. By default, PuTTY will install to C:\Program Files\PuTTY. To edit your PATH (for Windows >= Win2k), Start -> Control Panel -> System -> Advanced -> Environment Variables -> System Variables -> Path -> Edit. Add "C:\Program Files\PuTTY;" to the end of the PATH variable value.

==Enable Existing Key==
*Transfer existing ~\.ssh\id_dsa to Windows
Copy the private ssh key that is associated with your KDE Subversion account to the MS Windows machine. In many cases this will be /home/kde-devel/.ssh/id_dsa. I put mine in C:\Documents and Settings\mark\My Documents.

*Load into PuTTY Key Generator
In order to use your OpenSSH private key, you must first convert it to a PuTTY Private Key (*.ppk). To do this, Start -> All Programs -> PuTTY -> PuTTYgen -> Load. Browse to wherever you saved your private key (id_dsa) and load it.

*Save Private Key
Once the key is loaded, click on 'Save Private Key' to save a copy of the key in a version that PuTTY can use. I saved mine as id_dsa.ppk.

==Enable Pageant==
Pageant is PuTTY's version of sshagent, holding your keys for you so you don't always have to enter your passphrase.

*Start Pageant
Start Pageant Start -> All Programs -> PuTTY -> Pageant. An icon will appear in your system tray. Right-click in the icon, then select view keys. If your key isn't listed, click on 'Add Key' and add the id_dsa.ppk key you created earlier.

*Add Pageant to Startup group
I suggest adding Pageant to the MS Windows Startup group so that it launches every time you start Windows.

==Configure Subversion PuTTY Tunnel==
We need to create a new type of tunnel: subversion over PuTTY (svn+ssh://).
We call the tunnel ssh for consistency with the Linux world. We could
just as well call it putty and then use svn+putty everywhere. The default configuration for emerge (kdesettings-example.bat) uses ssh.

*We create this tunnel in the Subversion configuration file. Open <tt>%appdata%\Subversion\config</tt>

*In [Tunnels] section, we create our new tunnel by adding a line (use \\ for backslash):
<tt>ssh = plink -ssh -C -i c:\\path\\to\\id_dsa.ppk -agent <svnaccountname>@svn.kde.org</tt>

<tt>plink</tt> is the command line version of PuTTY. <tt>-ssh</tt> tells PuTTY to use SSH protocol. <tt>-C</tt> turns on compression. <tt>-i</tt> is the path to your private key. <tt>-agent</tt> tells PuTTY to try to use Pageant.

As an alternative to editing the Subversion configuration file, you can define the environment variable SVN_SSH just like you would define the ssh tunnel (untested).

Now open PuTTY (Start -> All Programs -> PuTTY -> PuTTY) and open a connection to <tt>svn.kde.org</tt> it will ask you if you accept the server id. Select yes,
a terminal window with an error message may appear, this is normal. If prompted, enter your username. It may then throw errors, but don't worry. The authentication process between your computer and svn.kde.org is now complete, and you may close the PuTTY session.

==Repository Access==
*The repository can now be accessed by using the svn+ssh:// tunnel, e.g. <tt>
C:\KDE4> svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</tt>

==Setup Git==
Install Git by either running [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge 'emerge git' ] or by downloading the zip yourself from the [http://code.google.com/p/msysgit/ msysgit page].

After installation you will need to setup the following environment variables (as shown above):
*Create a new variable HOME with value %USERPROFILE%. This will be expanded to the path of your account automatically.
*Create a new variable GIT_SSH with value: plink.exe

Git is now completely setup to follow the steps in the [http://techbase.kde.org/Getting_Started/Sources/KDE_git-tutorial KDE Git tutorial]

Getting Started/Build/Windows/emerge

2011-01-07T14:54:45Z

Wrohdewald:

''emerge'' is a tool to build the KDE sources and its third-party requirements on MS Windows. It is the '''easy''' way to build KDE on MS Windows.

== Introduction ==
Emerge is a tool that can build the different parts of KDE and its dependencies under Windows. We created this tool to automate and simplify the build process under Windows. We try to build all packages that we offer in the KDE installer with emerge. That has some advantages for us:
* it is easy for people to join us:
Before emerge it was quite some work to set a system up for development. There were some quirks, which were documented in some mailing lists, but you had to remember them or you ran into an already solved problem again, etc.
Now to get a development machine you need a Windows computer, need to install Python and Subversion and do the emerge checkout. Then execute emerge to build what you want to build. This is easy for developers coming from Windows to KDE, and also for KDE developers coming to Windows.
* it is easy for us to do (nightly/continuous/release/reproducable/...) builds:
With emerge you can build the whole software stack (low-level libs, Qt, kdelibs, things above that) with only one command. You can start that build, and some hours later you can check if it worked, or if something broke. So we can spot problems easier and earlier. We can also start with a "naked" Windows computer without any other installed software and bootstrap kde on it. That ensures, that no hidden dependencies on some pieces of software sneak in, because then the builds on a "naked" computer would break and show the problem.
* it is easier to collaborate:
We can test the same emerge build description for a package on different Windows versions/computers before we do binary releases. People can also add build descriptions for new packages to the Subversion repository.

This emerge tool was inspired by the Gentoo emerge tool.

== Set up the environment ==
=== Root directory ===
Create a directory if possible in your harddrive's root e.g. C:\kderoot or D:\kderoot (You will need this PATH later). This directory will contain the whole kde installation later. We will refer to it as %KDEROOT%.

=== Python interpreter ===
<tt>emerge.bat</tt> invokes an <tt>emerge.py</tt> script written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] programming language, so you first need to [http://www.python.org/download/ install the Python 2.7 Interpreter]. The ''python'' installation directory will be added to the PATH later by <tt>%KDEROOT%\etc\kdesettings.bat</tt> script.

=== Subversion client ===
The latest source code for Windows ''emerge'' and the rest of KDE is stored in a repository created and managed using the [http://subversion.tigris.org/ Subversion] version control tool, abbreviated svn. You need a Subversion client for the first checkout of emerge. There are at least two applications:
*a command line client, available at [http://subversion.apache.org/packages.html subversion.apache.org], aimed at developers or power users accustomed with the command line,
*a GUI program like [http://tortoisesvn.tigris.org/ TortoiseSVN], optional, useful for displaying differences between various versions of files in the repository in a graphical way.

Emerge uses its own Subversion client for checking out all KDE source code. However it is not quite up to date: From August 2009. You can find it in %KDEROOT%\dev-utils\svn\bin. It will be used by emerge even if you have another svn executable installed.

Note 1: If you experience problems with the checkout of Qt (svn doesn't work correctly) please remove any other svn binaries out of the path that you do have. '''The different versions of the Apache portable runtime (APR) are incompatible!'''

Note 2: Most source files in the KDE Subversion repository have Unix line endings, and svn will not convert them to Windows line endings. This is fine for emerge, but the standard Windows editor might not show those files correctly. You can use another editor like vim (http://www.vim.org).

=== Getting the ''emerge'' tool ===
The source code of the ''emerge'' tool and the recipes for creating KDE packages are located at <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt>, which is an URL based on the Subversion-specific ''svn'' protocol.

You need to check out the source code from the ''emerge'' Subversion directory into a new directory below your root directory (the root directory is normally called %KDEROOT% here) or get it inside a self extracting archive (not tested yet).

==== Check out using the 'svn' command ====

*Option 1: With the ''svn'' command line tool, you can accomplish this with the following commands:<pre>cd %KDEROOT%</pre>
**if you will only use anonymous (read-only) access to the KDE svn repository:<pre>svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
**or, if you plan to use write access (commit) to the KDE svn repository
***via https:<pre>svn co --username yourusername https://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
***via a [[Getting_Started/Build/KDE4/Windows/subversion|puTTY tunnel]] using your existing account & OpenSSH private key: <pre>svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>

This would result with:

Error validating server certificate for '<nowiki>https://svn.kde.org:443</nowiki>':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: svn.kde.org
- Valid: from Wed, 11 May 2005 09:08:21 GMT until Sat, 09 May 2015 09:08:21 GMT
- Issuer: SVN, KDE e.V., Nuernberg, Bavaria, DE
- Fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
(R)eject, accept (t)emporarily or accept (p)ermanently?

enter ''p'' here to permanently accept the certificate:

Authentication realm: <<nowiki>https://svn.kde.org:443</nowiki>> KDE SVN account
Password for 'yourusername': ***************
A emerge\kdeenv.bat
A emerge\portage
A emerge\portage\kdesupport
[....]

The password and cache for the certificates is saved in <tt>%APPDATA%\Subversion\auth</tt> directory.

==== Check out using the TortoiseSVN ====

*Option 2: If you use TortoiseSVN:
*#right-click on your %KDEROOT% folder and select ''SVN Checkout...'' command from the context menu,
*#paste <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt> URL into the ''URL of repository'' text box (replace with <tt><nowiki>https://svn.kde.org/home/kde/trunk/kdesupport/emerge</nowiki></tt> for read-write access)
*#add <tt>\emerge</tt> to the folder name in the ''Checkout directory'' box and click OK to continue
*#if you picked the read-write access, you will be asked for accepting the SSL certificate of the SVN server (click "Premanent") and then for username and password. For convenience select "Save authentication" checkbox too (the password and cache for the certificates will be saved in <tt>%APPDATA%\Subversion\auth</tt> directory).

After the checkout you should have the directory <tt>%KDEROOT%\emerge</tt>. If you don't, you move your ''emerge'' directory to that location.

==== Installing from the self-extracting archive ====
*Option 3: Get the self-extracting archive from [http://www.winkde.org/pub/kde/ports/win32/emerge/emerge-latest.exe here], unpack it into your KDEROOT directory so that you have a folder %KDEROOT%\emerge.
* This self-extracting archive brings a subversion repository containing the emerge scripts and a python installation with it, so you do not need either of them before starting with emerge.

=== Configure the ''emerge'' tool ===
# Create the directory <tt>%KDEROOT%\etc</tt>.
# Copy the file <tt>%KDEROOT%\emerge\kdesettings-example.bat</tt> as <tt>%KDEROOT%\etc\kdesettings.bat</tt> and change its contents according to your needs. The options are described in the ''rem'' lines in the file itself.

The kdesettings.bat script will be called by the main kdeenv.bat script.

Note 1: '''Be sure that you neither have the msys/bin nor the cygwin/bin in your path. If so you have to definitely remove it from the path.'''

Note 2 '''from a user: The applications gimp, inkscape and graphviz are also a problem. To make sure that there's nothing wrong I stripped my path to contain only what I needed to build.'''

Note 3 '''from another user: be careful when renaming the file to "kdesettings.bat" it is easy to end up with "kdesettings.bat.bat" instead of what you want since Windows(by default) will not show the the file extension part of a file.'''

=== [Optional, Advanced] emergehosts.conf ===
Add a file emergehosts.conf in the <tt>%KDEROOT%\etc</tt> directory. The format of this file is a typical config file with only two entries per section:
The first entry is the ''host'' as mentioned in the portage file for the package. The second entry is called ''replace'' and is the replace string for the host string.

As an example, here is how to checkout all gitorious based repos of the kde-developers group using a push url instead of the anonymous access:
<code>
[qt gitorious]
host: git://gitorious.org/+kde-developers/
replace: git@gitorious.org:+kde-developers/
</code>

As a second example here is how to checkout with a ssh user from a subversion repository:
<code>
[svn.example.com]
host: svn://svn.example.com/
replace: svn+ssh://user@svn.example.com/
</code>

The name of the section doesn't matter and can be used for descriptions.

== Using emerge ==

To use emerge you need to start a console window and point that to <tt>%KDEROOT%\emerge</tt>. For example:

C:
cd \%KDEROOT%\emerge

Then you have to execute

kdeenv.bat

This tells emerge about your environment settings (e.g. paths). It will load your configuration from <tt>%KDEROOT%\etc\kdesettings.bat</tt>. It should not give any error messages, otherwise emerge will not work as expected. The output should look similar to this one (of course with your paths):

C:\kderoot\emerge>kdeenv.bat
kdesettings.bat executed
KDEROOT : C:\kderoot
KDECOMPILER : mingw
KDESVNDIR : C:\kderoot\svn
PYTHONPATH : C:\python27
DOWNLOADDIR : C:\kderoot\download

C:\kderoot\emerge>

Next, if you have configured your kdesettings.bat to use svn+ssh for your subversion checkout, then you need to run:

<code>plink <your-svn-username>@svn.kde.org
plink <your-kde-username>@git.kde.org</code>

This will prompt you to accept the fingerprint of the server, otherwise svn will hang forever when trying to download from the server.

Now you should be able to use emerge. Type

emerge --help

to get some help on usage.

''Note: There is a short path option in kdesettings which you will
need if you want to build Qt in a directory that has a pathlenght of
more then around 5 characters. This problem is due to limitations of the command line length and the Qt build system.''

== Setting up a compiler ==
Currently emerge supports both the MinGW and MS Visual C++ (msvc) compilers. We did not add dependencies for the compilers, so you have to make sure to install a compiler by yourself. There are three ways to set up a compiler for emerge.
We assumed you have set KDECOMPILER variable properly in the <tt>%KDEROOT%\etc\kdesettings.bat</tt>.

In the following sections you can find information on how to install or reuse an existing compiler.

=== Install the MinGW compiler with emerge ===
Let emerge install the MinGW compiler, as soon as emerge needs MinGW it will automatically fetch the correct version for you.

=== Install MS Visual C++ ===
Read [[../MS_Visual_Studio#The_Compiler|here]].

=== Point to an existing MS Visual C++ installation ===
You need to point emerge to an existing msvc installation. This is run automatically for you from kdeenv.bat if configured properly in kdesettings.bat. Check your kdesettings.bat file to know where to set it.

== Installing the base system ==
Once you have emerge and a compiler installed and working, try:
* <tt>emerge --help</tt> for a list of available commands
* <tt>emerge --print-installable</tt> to get a list of available packages
* <tt>emerge --print-installed</tt> to get a list of currently installed packages
Further options are described below.

You are now ready to start building KDE, it is recommended to do so progressively, relying on emerge to automatically resolve the required dependencies at each set step:

* Enter <tt>emerge qt</tt>. This will fetch and install Windows versions of numerous UNIX-like utilities and libraries, then checkout, compile and install Qt. This will take several hours.
* Enter <tt>emerge kdelibs</tt>. This will checkout, compile and install the required kdesupport modules and then kdelibs.
* Enter <tt>emerge kdebase-apps</tt>. This will checkout, compile and install kdebase-runtime, and kdebase-apps

You will now have successfully installed a base KDE system and can now install other KDE modules as required.

Note that this will install the trunk version of KDE, if you wish to install a particular stable branch then you must prefix the KDE package names with the required version, i.e. <tt>emerge kde-4.5/kdelibs</tt>. You can force emerge to always default to a given branch by setting the <tt>EMERGE_DEFAULTCATEGORY</tt> variable in your kdesettings.bat file. You should not mix kde packages from different branches.

It is strongly recommened you do not choose to manually install any of the utilities and libraries yourself, as you may install the wrong version and cause installation failures. Instead allow emerge to resolve the dependencies for you.

Every time you want to update or install a package, you should first update your emerge checkout (simply run emerge --update emerge) to ensure you are using the latest package recipies.

== What emerge does ==
'''emerge ''packageName'' ''' performs the separate actions <tt>--fetch</tt>, <tt>--unpack</tt>, <tt>--compile</tt>, <tt>--install</tt>, <tt>--manifest</tt>, and <tt>--qmerge</tt>.

The <tt>--fetch</tt> action will retrieve either a binary or the source code for the package:
* If a binary package, this will be downloaded into the <tt>DOWNLOADDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\download</tt>.
* If a non-KDE source package, the source repository will be checked-out into <tt>%DOWNLOADDIR%\svn-src</tt>, e.g. Qt source may be found in <tt>C:\kderoot\download\svn-src\qt</tt>.
* If a KDE source package from the <tt>svn.kde.org</tt> repository, then the source will be checked-out into the <tt>KDESVNDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\svn</tt>.

== ''emerge'' command line options and settings ==
There are some options that can be used when building with ''emerge''.

{| border="0" cellpadding="2"
!Command line switch
!Command line argument
!
!Description
|-valign="top"
|<tt>-v</tt>
|<tt>EMERGE_VERBOSE</tt>
|width="5%"|
|This option sets the verbosity level. Currently the highest verbosity level is 3 (<tt>-v -v -v</tt>). A verbosity level of 0 should give no output and equals to <tt>-q</tt>. You can set <tt>EMERGE_VERBOSE=3</tt> instead in the environment of the commandline or within your <tt>kdesettings.bat</tt> file.
|-valign="top"
|<tt>--offline</tt>
|
|
|This option suppresses the update step of the local tree - which needs some time. Be aware though that you have to have existing sources already if you want to use this option.
|-valign="top"
|<tt>-t</tt>
|<tt>EMERGE_BUILDTESTS</tt>
|
|This option enables or disables KDE4 buildtests for KDE modules. Other packages will not change. Use <tt>EMERGE_BUILDTESTS=True</tt> or <tt>=False</tt>.
|-valign="top"
|<tt>--print-targets</tt>
|
|
|This option will display all "targets" a certain package has. Normally targets are fixed releases or different branches. They are defined in the portage file.
|-valign="top"
|<tt>--target=TARGET</tt>
|
|
|This sets a specific target for this package. If not added, the default target is used, which can be checked by looking at the output of '''--print-targets'''.
|-valign="top"
|<tt>-i</tt>
|
|
|This option ignores that a package is already installed. It builds it completely new, but keeps the dependencies.
|-valign="top"
|<tt>--update</tt>
|
|
|This option ignores that a package is already installed but doesn't cleanup an already existing build directory. Thus you will only rebuild files that have changed since the last build.
|}

== Hints ==
=== Updating packages ===
*Once you have ''packagename'' built, type <code>emerge --update packagename</code> to update <tt>packagename</tt> from the Subversion and compile it without removing the build dir or <code>emerge --update-all</code> to update all packages that can be rebuild (they are rebuild with --update).

=== General setup ===
For Fine Tuning see here:
[[Projects/KDE_on_Windows/Installation#Fine-tuning|Fine-tuning]]

== Notes ==

''emerge'' can mostly cooperate with the [[Projects/KDE_on_Windows/Installation#KDE_Installer_for_Windows|kdewin-installer]] but we're currently still working on some packages which are packaged in a wrong way.
It is not recommended to use another layout then '''installer''' for '''directory_layout''' in the '''kdesettings.bat''' anymore (see that file for more detailed information).

''emerge'' creates lots of files in '''\kderoot\tmp''' during build.
After a package is successfully installed
(check '''\kderoot\etc\portage\installed''' or the directory '''\kderoot\manifest\'''), you can delete its temporary directory.

Windows ''emerge'' is derived from the Gentoo portage system, but we are currently not enforcing compatibility. If you have questions about that please contact us at the channel #kde-windows on irc.freenode.net.

last reviewed by [[User:SaroEngels|SaroEngels]] 22:25, 4 November 2010 (UTC)

==Vista issues==
*[[User:Jstaniek|jstaniek]] 12:02, 15 January 2008 (CET): UAC has infamous heuristics that make programs like patch.exe treat as installers and try to run them with admin rights (!). This heuristics can be tricked by renaming patch.exe to something like pch.exe ([http://nevali.net/2007/01/update-workaround-for-the-cygwin-uac-problem/ example]) but we did not want to add item to our infrastructure. Instead it is possibleto turn off the heuristics (see the screenshot [http://theinvisiblethings.blogspot.com/2007/02/running-vista-every-day.html here in the security blog calling the heuristics 'severe hole in the design of UAC']). If you happen to disable the UAC, as many annoyed users and devs do (msvc demands admin rights anyway!), patch.exe should already work for you as in older Windows. Alternatively you may want to disable UAC [http://www.howtogeek.com/howto/windows-vista/disable-user-account-controluac-for-administrators-only/ for admins only], but this makes no sense if you are the only user of your machine and use only the admin account.
* [http://ben.versionzero.org/wiki/Fixing_the_way_Vista_Auto-detects_Installers This wiki page] lists instructions on how to use program manifest to disable privilege elevation for a single binary and makes patch play nice with UAC. This [https://bugs.kde.org/show_bug.cgi?id=186712 should] eventually be integrated to emerge scripts.

[[Category:MS Windows]]

Getting Started/Build/Windows/emerge

2011-01-07T14:44:15Z

Wrohdewald: fix a few things about the subversion client

''emerge'' is a tool to build the KDE sources and its third-party requirements on MS Windows. It is the '''easy''' way to build KDE on MS Windows.

== Introduction ==
Emerge is a tool that can build the different parts of KDE and its dependencies under Windows. We created this tool to automate and simplify the build process under Windows. We try to build all packages that we offer in the KDE installer with emerge. That has some advantages for us:
* it is easy for people to join us:
Before emerge it was quite some work to set a system up for development. There were some quirks, which were documented in some mailing lists, but you had to remember them or you ran into an already solved problem again, etc.
Now to get a development machine you need a Windows computer, need to install Python and Subversion and do the emerge checkout. Then execute emerge to build what you want to build. This is easy for developers coming from Windows to KDE, and also for KDE developers coming to Windows.
* it is easy for us to do (nightly/continuous/release/reproducable/...) builds:
With emerge you can build the whole software stack (low-level libs, Qt, kdelibs, things above that) with only one command. You can start that build, and some hours later you can check if it worked, or if something broke. So we can spot problems easier and earlier. We can also start with a "naked" Windows computer without any other installed software and bootstrap kde on it. That ensures, that no hidden dependencies on some pieces of software sneak in, because then the builds on a "naked" computer would break and show the problem.
* it is easier to collaborate:
We can test the same emerge build description for a package on different Windows versions/computers before we do binary releases. People can also add build descriptions for new packages to the Subversion repository.

This emerge tool was inspired by the Gentoo emerge tool.

== Set up the environment ==
=== Root directory ===
Create a directory if possible in your harddrive's root e.g. C:\kderoot or D:\kderoot (You will need this PATH later). This directory will contain the whole kde installation later. We will refer to it as %KDEROOT%.

=== Python interpreter ===
<tt>emerge.bat</tt> invokes an <tt>emerge.py</tt> script written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] programming language, so you first need to [http://www.python.org/download/ install the Python 2.7 Interpreter]. The ''python'' installation directory will be added to the PATH later by <tt>%KDEROOT%\etc\kdesettings.bat</tt> script.

=== Subversion client ===
The latest source code for Windows ''emerge'' and the rest of KDE is stored in a repository created and managed using the [http://subversion.tigris.org/ Subversion] version control tool, abbreviated svn. You need a Subversion client for the first checkout of emerge. There are at least two applications:
*a command line client, available at [http://subversion.apache.org/packages.html subversion.apache.org], aimed at developers or power users accustomed with the command line,
*a GUI program like [http://tortoisesvn.tigris.org/ TortoiseSVN], optional, useful for displaying differences between various versions of files in the repository in a graphical way.

Emerge uses its own Subversion client for checking out all KDE source code. However it is not quite up to date: From August 2009. You can find it in %KDEROOT%\dev-utils\svn\bin. It will be used by emerge even if you have another svn executable installed.

Note 1: If you experience problems with the checkout of Qt (svn doesn't work correctly) please remove any other svn binaries out of the path that you do have. '''The different versions of the Apache portable runtime (APR) are incompatible!'''

Note 2: Most source files in the KDE Subversion repository have Unix line endings, and svn will not convert them to Windows line endings. This is fine for emerge, but the standard Windows editor might not show those files correctly. You can use another editor like vim (http://www.vim.org).

=== Getting the ''emerge'' tool ===
The source code of the ''emerge'' tool and the recipes for creating KDE packages are located at <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt>, which is an URL based on svn-specific ''svn'' protocol.

You need to check out the source code from the ''emerge'' Subversion directory into a new directory below your root directory (the root directory is normally called %KDEROOT% here) or get it inside a self extracting archive (not tested yet).

==== Check out using the 'svn' command ====

*Option 1: With the ''svn'' command line tool, you can accomplish this with the following commands:<pre>cd %KDEROOT%</pre>
**if you will only use anonymous (read-only) access to the KDE svn repository:<pre>svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
**or, if you plan to use write access (commit) to the KDE svn repository
***via https:<pre>svn co --username yourusername https://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
***via a [[Getting_Started/Build/KDE4/Windows/subversion|puTTY tunnel]] using your existing account & OpenSSH private key: <pre>svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>

This would result with:

Error validating server certificate for '<nowiki>https://svn.kde.org:443</nowiki>':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: svn.kde.org
- Valid: from Wed, 11 May 2005 09:08:21 GMT until Sat, 09 May 2015 09:08:21 GMT
- Issuer: SVN, KDE e.V., Nuernberg, Bavaria, DE
- Fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
(R)eject, accept (t)emporarily or accept (p)ermanently?

enter ''p'' here to permanently accept the certificate:

Authentication realm: <<nowiki>https://svn.kde.org:443</nowiki>> KDE SVN account
Password for 'yourusername': ***************
A emerge\kdeenv.bat
A emerge\portage
A emerge\portage\kdesupport
[....]

The password and cache for the certificates is saved in <tt>%APPDATA%\Subversion\auth</tt> directory.

==== Check out using the TortoiseSVN ====

*Option 2: If you use TortoiseSVN:
*#right-click on your %KDEROOT% folder and select ''SVN Checkout...'' command from the context menu,
*#paste <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt> URL into the ''URL of repository'' text box (replace with <tt><nowiki>https://svn.kde.org/home/kde/trunk/kdesupport/emerge</nowiki></tt> for read-write access)
*#add <tt>\emerge</tt> to the folder name in the ''Checkout directory'' box and click OK to continue
*#if you picked the read-write access, you will be asked for accepting the SSL certificate of the SVN server (click "Premanent") and then for username and password. For convenience select "Save authentication" checkbox too (the password and cache for the certificates will be saved in <tt>%APPDATA%\Subversion\auth</tt> directory).

After the checkout you should have the directory <tt>%KDEROOT%\emerge</tt>. If you don't, you move your ''emerge'' directory to that location.

==== Installing from the self-extracting archive ====
*Option 3: Get the self-extracting archive from [http://www.winkde.org/pub/kde/ports/win32/emerge/emerge-latest.exe here], unpack it into your KDEROOT directory so that you have a folder %KDEROOT%\emerge.
* This self-extracting archive brings a subversion repository containing the emerge scripts and a python installation with it, so you do not need either of them before starting with emerge.

=== Configure the ''emerge'' tool ===
# Create the directory <tt>%KDEROOT%\etc</tt>.
# Copy the file <tt>%KDEROOT%\emerge\kdesettings-example.bat</tt> as <tt>%KDEROOT%\etc\kdesettings.bat</tt> and change its contents according to your needs. The options are described in the ''rem'' lines in the file itself.

The kdesettings.bat script will be called by the main kdeenv.bat script.

Note 1: '''Be sure that you neither have the msys/bin nor the cygwin/bin in your path. If so you have to definitely remove it from the path.'''

Note 2 '''from a user: The applications gimp, inkscape and graphviz are also a problem. To make sure that there's nothing wrong I stripped my path to contain only what I needed to build.'''

Note 3 '''from another user: be careful when renaming the file to "kdesettings.bat" it is easy to end up with "kdesettings.bat.bat" instead of what you want since Windows(by default) will not show the the file extension part of a file.'''

=== [Optional, Advanced] emergehosts.conf ===
Add a file emergehosts.conf in the <tt>%KDEROOT%\etc</tt> directory. The format of this file is a typical config file with only two entries per section:
The first entry is the ''host'' as mentioned in the portage file for the package. The second entry is called ''replace'' and is the replace string for the host string.

As an example, here is how to checkout all gitorious based repos of the kde-developers group using a push url instead of the anonymous access:
<code>
[qt gitorious]
host: git://gitorious.org/+kde-developers/
replace: git@gitorious.org:+kde-developers/
</code>

As a second example here is how to checkout with a ssh user from a subversion repository:
<code>
[svn.example.com]
host: svn://svn.example.com/
replace: svn+ssh://user@svn.example.com/
</code>

The name of the section doesn't matter and can be used for descriptions.

== Using emerge ==

To use emerge you need to start a console window and point that to <tt>%KDEROOT%\emerge</tt>. For example:

C:
cd \%KDEROOT%\emerge

Then you have to execute

kdeenv.bat

This tells emerge about your environment settings (e.g. paths). It will load your configuration from <tt>%KDEROOT%\etc\kdesettings.bat</tt>. It should not give any error messages, otherwise emerge will not work as expected. The output should look similar to this one (of course with your paths):

C:\kderoot\emerge>kdeenv.bat
kdesettings.bat executed
KDEROOT : C:\kderoot
KDECOMPILER : mingw
KDESVNDIR : C:\kderoot\svn
PYTHONPATH : C:\python27
DOWNLOADDIR : C:\kderoot\download

C:\kderoot\emerge>

Next, if you have configured your kdesettings.bat to use svn+ssh for your subversion checkout, then you need to run:

<code>plink <your-svn-username>@svn.kde.org
plink <your-kde-username>@git.kde.org</code>

This will prompt you to accept the fingerprint of the server, otherwise svn will hang forever when trying to download from the server.

Now you should be able to use emerge. Type

emerge --help

to get some help on usage.

''Note: There is a short path option in kdesettings which you will
need if you want to build Qt in a directory that has a pathlenght of
more then around 5 characters. This problem is due to limitations of the command line length and the Qt build system.''

== Setting up a compiler ==
Currently emerge supports both the MinGW and MS Visual C++ (msvc) compilers. We did not add dependencies for the compilers, so you have to make sure to install a compiler by yourself. There are three ways to set up a compiler for emerge.
We assumed you have set KDECOMPILER variable properly in the <tt>%KDEROOT%\etc\kdesettings.bat</tt>.

In the following sections you can find information on how to install or reuse an existing compiler.

=== Install the MinGW compiler with emerge ===
Let emerge install the MinGW compiler, as soon as emerge needs MinGW it will automatically fetch the correct version for you.

=== Install MS Visual C++ ===
Read [[../MS_Visual_Studio#The_Compiler|here]].

=== Point to an existing MS Visual C++ installation ===
You need to point emerge to an existing msvc installation. This is run automatically for you from kdeenv.bat if configured properly in kdesettings.bat. Check your kdesettings.bat file to know where to set it.

== Installing the base system ==
Once you have emerge and a compiler installed and working, try:
* <tt>emerge --help</tt> for a list of available commands
* <tt>emerge --print-installable</tt> to get a list of available packages
* <tt>emerge --print-installed</tt> to get a list of currently installed packages
Further options are described below.

You are now ready to start building KDE, it is recommended to do so progressively, relying on emerge to automatically resolve the required dependencies at each set step:

* Enter <tt>emerge qt</tt>. This will fetch and install Windows versions of numerous UNIX-like utilities and libraries, then checkout, compile and install Qt. This will take several hours.
* Enter <tt>emerge kdelibs</tt>. This will checkout, compile and install the required kdesupport modules and then kdelibs.
* Enter <tt>emerge kdebase-apps</tt>. This will checkout, compile and install kdebase-runtime, and kdebase-apps

You will now have successfully installed a base KDE system and can now install other KDE modules as required.

Note that this will install the trunk version of KDE, if you wish to install a particular stable branch then you must prefix the KDE package names with the required version, i.e. <tt>emerge kde-4.5/kdelibs</tt>. You can force emerge to always default to a given branch by setting the <tt>EMERGE_DEFAULTCATEGORY</tt> variable in your kdesettings.bat file. You should not mix kde packages from different branches.

It is strongly recommened you do not choose to manually install any of the utilities and libraries yourself, as you may install the wrong version and cause installation failures. Instead allow emerge to resolve the dependencies for you.

Every time you want to update or install a package, you should first update your emerge checkout (simply run emerge --update emerge) to ensure you are using the latest package recipies.

== What emerge does ==
'''emerge ''packageName'' ''' performs the separate actions <tt>--fetch</tt>, <tt>--unpack</tt>, <tt>--compile</tt>, <tt>--install</tt>, <tt>--manifest</tt>, and <tt>--qmerge</tt>.

The <tt>--fetch</tt> action will retrieve either a binary or the source code for the package:
* If a binary package, this will be downloaded into the <tt>DOWNLOADDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\download</tt>.
* If a non-KDE source package, the source repository will be checked-out into <tt>%DOWNLOADDIR%\svn-src</tt>, e.g. Qt source may be found in <tt>C:\kderoot\download\svn-src\qt</tt>.
* If a KDE source package from the <tt>svn.kde.org</tt> repository, then the source will be checked-out into the <tt>KDESVNDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\svn</tt>.

== ''emerge'' command line options and settings ==
There are some options that can be used when building with ''emerge''.

{| border="0" cellpadding="2"
!Command line switch
!Command line argument
!
!Description
|-valign="top"
|<tt>-v</tt>
|<tt>EMERGE_VERBOSE</tt>
|width="5%"|
|This option sets the verbosity level. Currently the highest verbosity level is 3 (<tt>-v -v -v</tt>). A verbosity level of 0 should give no output and equals to <tt>-q</tt>. You can set <tt>EMERGE_VERBOSE=3</tt> instead in the environment of the commandline or within your <tt>kdesettings.bat</tt> file.
|-valign="top"
|<tt>--offline</tt>
|
|
|This option suppresses the update step of the local tree - which needs some time. Be aware though that you have to have existing sources already if you want to use this option.
|-valign="top"
|<tt>-t</tt>
|<tt>EMERGE_BUILDTESTS</tt>
|
|This option enables or disables KDE4 buildtests for KDE modules. Other packages will not change. Use <tt>EMERGE_BUILDTESTS=True</tt> or <tt>=False</tt>.
|-valign="top"
|<tt>--print-targets</tt>
|
|
|This option will display all "targets" a certain package has. Normally targets are fixed releases or different branches. They are defined in the portage file.
|-valign="top"
|<tt>--target=TARGET</tt>
|
|
|This sets a specific target for this package. If not added, the default target is used, which can be checked by looking at the output of '''--print-targets'''.
|-valign="top"
|<tt>-i</tt>
|
|
|This option ignores that a package is already installed. It builds it completely new, but keeps the dependencies.
|-valign="top"
|<tt>--update</tt>
|
|
|This option ignores that a package is already installed but doesn't cleanup an already existing build directory. Thus you will only rebuild files that have changed since the last build.
|}

== Hints ==
=== Updating packages ===
*Once you have ''packagename'' built, type <code>emerge --update packagename</code> to update <tt>packagename</tt> from the Subversion and compile it without removing the build dir or <code>emerge --update-all</code> to update all packages that can be rebuild (they are rebuild with --update).

=== General setup ===
For Fine Tuning see here:
[[Projects/KDE_on_Windows/Installation#Fine-tuning|Fine-tuning]]

== Notes ==

''emerge'' can mostly cooperate with the [[Projects/KDE_on_Windows/Installation#KDE_Installer_for_Windows|kdewin-installer]] but we're currently still working on some packages which are packaged in a wrong way.
It is not recommended to use another layout then '''installer''' for '''directory_layout''' in the '''kdesettings.bat''' anymore (see that file for more detailed information).

''emerge'' creates lots of files in '''\kderoot\tmp''' during build.
After a package is successfully installed
(check '''\kderoot\etc\portage\installed''' or the directory '''\kderoot\manifest\'''), you can delete its temporary directory.

Windows ''emerge'' is derived from the Gentoo portage system, but we are currently not enforcing compatibility. If you have questions about that please contact us at the channel #kde-windows on irc.freenode.net.

last reviewed by [[User:SaroEngels|SaroEngels]] 22:25, 4 November 2010 (UTC)

==Vista issues==
*[[User:Jstaniek|jstaniek]] 12:02, 15 January 2008 (CET): UAC has infamous heuristics that make programs like patch.exe treat as installers and try to run them with admin rights (!). This heuristics can be tricked by renaming patch.exe to something like pch.exe ([http://nevali.net/2007/01/update-workaround-for-the-cygwin-uac-problem/ example]) but we did not want to add item to our infrastructure. Instead it is possibleto turn off the heuristics (see the screenshot [http://theinvisiblethings.blogspot.com/2007/02/running-vista-every-day.html here in the security blog calling the heuristics 'severe hole in the design of UAC']). If you happen to disable the UAC, as many annoyed users and devs do (msvc demands admin rights anyway!), patch.exe should already work for you as in older Windows. Alternatively you may want to disable UAC [http://www.howtogeek.com/howto/windows-vista/disable-user-account-controluac-for-administrators-only/ for admins only], but this makes no sense if you are the only user of your machine and use only the admin account.
* [http://ben.versionzero.org/wiki/Fixing_the_way_Vista_Auto-detects_Installers This wiki page] lists instructions on how to use program manifest to disable privilege elevation for a single binary and makes patch play nice with UAC. This [https://bugs.kde.org/show_bug.cgi?id=186712 should] eventually be integrated to emerge scripts.

[[Category:MS Windows]]

Getting Started/Build/Windows/subversion

2011-01-07T14:14:04Z

Wrohdewald: tunnel for svn: call it ssh, not putty. And fix spelling for PuTTY

This article details how a developer can set up the Subversion command line client <tt>svn</tt> and <tt>PuTTY</tt> on MS Windows to enable write access to the KDE Subversion Repository, using your existing SSH credentials from *nix.

==Install PuTTY==
*Install PuTTY
[http://en.wikipedia.org/wiki/PuTTY PuTTY] is a free implementation of SSH for Win32. [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Download] and install PuTTY. Using the Windows install file is the easiest method. As of this writing the current version is [ftp://ftp.chiark.greenend.org.uk/users/sgtatham/putty-latest/x86/putty-0.60-installer.exe putty-0.60-installer.exe].

*Put PuTTY in $PATH
In order for MS Windows to be able to find PuTTY and its related executable files, you need to add their location to your PATH variable. By default, PuTTY will install to C:\Program Files\PuTTY. To edit your PATH (for Windows >= Win2k), Start -> Control Panel -> System -> Advanced -> Environment Variables -> System Variables -> Path -> Edit. Add "C:\Program Files\PuTTY;" to the end of the PATH variable value.

==Enable Existing Key==
*Transfer existing ~\.ssh\id_dsa to Windows
Copy the private ssh key that is associated with your KDE Subversion account to the MS Windows machine. In many cases this will be /home/kde-devel/.ssh/id_dsa. I put mine in C:\Documents and Settings\mark\My Documents.

*Load into PuTTY Key Generator
In order to use your OpenSSH private key, you must first convert it to a PuTTY Private Key (*.ppk). To do this, Start -> All Programs -> PuTTY -> PuTTYgen -> Load. Browse to wherever you saved your private key (id_dsa) and load it.

*Save Private Key
Once the key is loaded, click on 'Save Private Key' to save a copy of the key in a version that PuTTY can use. I saved mine as id_dsa.ppk.

==Enable Pageant==
Pageant is PuTTY's version of sshagent, holding your keys for you so you don't always have to enter your passphrase.

*Start Pageant
Start Pageant Start -> All Programs -> PuTTY -> Pageant. An icon will appear in your system tray. Right-click in the icon, then select view keys. If your key isn't listed, click on 'Add Key' and add the id_dsa.ppk key you created earlier.

*Add Pageant to Startup group
I suggest adding Pageant to the MS Windows Startup group so that it launches every time you start Windows.

==Configure Subversion PuTTY Tunnel==
We need to create a new type of tunnel: subversion over PuTTY (svn+ssh://).
We call the tunnel ssh for consistency with the Linux world. We could
just as well call it putty and then use svn+putty everywhere. The default configuration for emerge (kdesettings-example.bat) uses ssh.

*We create this tunnel in the Subversion configuration file. Open <tt>%appdata%\Subversion\config</tt>

*In [Tunnels] section, we create our new tunnel by adding a line (use \\ for backslash):
<tt>ssh = plink -ssh -C -i c:\\path\\to\\id_dsa.ppk -agent <svnaccountname>@svn.kde.org</tt>

<tt>plink</tt> is the command line version of PuTTY. <tt>-ssh</tt> tells PuTTY to use SSH protocol. <tt>-C</tt> turns on compression. <tt>-i</tt> is the path to your private key. <tt>-agent</tt> tells PuTTY to try to use Pageant.

Now open PuTTY (Start -> All Programs -> PuTTY -> PuTTY) and open a connection to <tt>svn.kde.org</tt> it will ask you if you accept the server id. Select yes,
a terminal window with an error message may appear, this is normal. If prompted, enter your username. It may then throw errors, but don't worry. The authentication process between your computer and svn.kde.org is now complete, and you may close the PuTTY session.

==Repository Access==
*The repository can now be accessed by using the svn+ssh:// tunnel, e.g. <tt>
C:\KDE4> svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</tt>

==Setup Git==
Install Git by either running [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge 'emerge git' ] or by downloading the zip yourself from the [http://code.google.com/p/msysgit/ msysgit page].

After installation you will need to setup the following environment variables (as shown above):
*Create a new variable HOME with value %USERPROFILE%. This will be expanded to the path of your account automatically.
*Create a new variable GIT_SSH with value: plink.exe

Git is now completely setup to follow the steps in the [http://techbase.kde.org/Getting_Started/Sources/KDE_git-tutorial KDE Git tutorial]

Getting Started/Build/Windows/emerge

2011-01-07T14:00:42Z

Wrohdewald: change svn+putty to svn+ssh

''emerge'' is a tool to build the KDE sources and its third-party requirements on MS Windows. It is the '''easy''' way to build KDE on MS Windows.

== Introduction ==
Emerge is a tool that can build the different parts of KDE and its dependencies under Windows. We created this tool to automate and simplify the build process under Windows. We try to build all packages that we offer in the KDE installer with emerge. That has some advantages for us:
* it is easy for people to join us:
Before emerge it was quite some work to set a system up for development. There were some quirks, which were documented in some mailing lists, but you had to remember them or you ran into an already solved problem again, etc.
Now to get a development machine you need a Windows computer, need to install Python and Subversion and do the emerge checkout. Then execute emerge to build what you want to build. This is easy for developers coming from Windows to KDE, and also for KDE developers coming to Windows.
* it is easy for us to do (nightly/continuous/release/reproducable/...) builds:
With emerge you can build the whole software stack (low-level libs, Qt, kdelibs, things above that) with only one command. You can start that build, and some hours later you can check if it worked, or if something broke. So we can spot problems easier and earlier. We can also start with a "naked" Windows computer without any other installed software and bootstrap kde on it. That ensures, that no hidden dependencies on some pieces of software sneak in, because then the builds on a "naked" computer would break and show the problem.
* it is easier to collaborate:
We can test the same emerge build description for a package on different Windows versions/computers before we do binary releases. People can also add build descriptions for new packages to the Subversion repository.

This emerge tool was inspired by the Gentoo emerge tool.

== Set up the environment ==
=== Root directory ===
Create a directory if possible in your harddrive's root e.g. C:\kderoot or D:\kderoot (You will need this PATH later). This directory will contain the whole kde installation later. We will refer to it as %KDEROOT%.

=== Python interpreter ===
<tt>emerge.bat</tt> invokes an <tt>emerge.py</tt> script written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] programming language, so you first need to [http://www.python.org/download/ install the Python 2.7 Interpreter]. The ''python'' installation directory will be added to the PATH later by <tt>%KDEROOT%\etc\kdesettings.bat</tt> script.

=== Subversion client ===
The latest source code for Windows ''emerge'' and the rest of KDE is stored in a repository created and managed using the [http://subversion.tigris.org/ Subversion] version control tool. You need a Subversion client for the first checkout. There are at least two applications:
*a command line client, available at [http://subversion.apache.org/packages.html subversion.apache.org] '''(required by emerge to get the source code from KDE Subversion repository)''', aimed at developers or power users accustomed with the command line,
*GUI program like [http://tortoisesvn.tigris.org/ TortoiseSVN], optional, useful for displaying differences between various versions of files in the repository in a graphical way.

Note 1: If you experience problems with the checkout of Qt (Subversion doesn't work correctly) please remove any other Subversion binaries out of the path that you do have. '''The different versions of the Apache portable runtime (APR) are incompatible!'''

Note 2: Make sure to use a copy of Subversion that was built on Windows so that checked-out files do not use UNIX line endings. If you check out with UNIX line endings, the ''patch'' program will fail when attempting to apply a patch whose line endings don't match the system's.

=== Getting the ''emerge'' tool ===
The source code of the ''emerge'' tool and the recipes for creating KDE packages are located at <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt>, which is an URL based on Subversion-specific ''svn'' protocol.

You need to check out the source code from the ''emerge'' Subversion directory into a new directory below your root directory (the root directory is normally called %KDEROOT% here) or get it inside a self extracting archive (not tested yet).

==== Check out using the 'svn' command ====

*Option 1: With the ''svn'' command line tool, you can accomplish this with the following commands:<pre>cd %KDEROOT%</pre>
**if you will only use anonymous (read-only) access to the KDE svn repository:<pre>svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
**or, if you plan to use write access (commit) to the KDE svn repository
***via https:<pre>svn co --username yourusername https://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
***via a [[Getting_Started/Build/KDE4/Windows/subversion|puTTY tunnel]] using your existing account & OpenSSH private key: <pre>svn co svn+ssh://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>

This would result with:

Error validating server certificate for '<nowiki>https://svn.kde.org:443</nowiki>':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: svn.kde.org
- Valid: from Wed, 11 May 2005 09:08:21 GMT until Sat, 09 May 2015 09:08:21 GMT
- Issuer: SVN, KDE e.V., Nuernberg, Bavaria, DE
- Fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
(R)eject, accept (t)emporarily or accept (p)ermanently?

enter ''p'' here to permanently accept the certificate:

Authentication realm: <<nowiki>https://svn.kde.org:443</nowiki>> KDE SVN account
Password for 'yourusername': ***************
A emerge\kdeenv.bat
A emerge\portage
A emerge\portage\kdesupport
[....]

The password and cache for the certificates is saved in <tt>%APPDATA%\Subversion\auth</tt> directory.

==== Check out using the TortoiseSVN ====

*Option 2: If you use TortoiseSVN:
*#right-click on your %KDEROOT% folder and select ''SVN Checkout...'' command from the context menu,
*#paste <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt> URL into the ''URL of repository'' text box (replace with <tt><nowiki>https://svn.kde.org/home/kde/trunk/kdesupport/emerge</nowiki></tt> for read-write access)
*#add <tt>\emerge</tt> to the folder name in the ''Checkout directory'' box and click OK to continue
*#if you picked the read-write access, you will be asked for accepting the SSL certificate of the SVN server (click "Premanent") and then for username and password. For convenience select "Save authentication" checkbox too (the password and cache for the certificates will be saved in <tt>%APPDATA%\Subversion\auth</tt> directory).

After the checkout you should have the directory <tt>%KDEROOT%\emerge</tt>. If you don't, you move your ''emerge'' directory to that location.

==== Installing from the self-extracting archive ====
*Option 3: Get the self-extracting archive from [http://www.winkde.org/pub/kde/ports/win32/emerge/emerge-latest.exe here], unpack it into your KDEROOT directory so that you have a folder %KDEROOT%\emerge.
* This self-extracting archive brings a subversion repository containing the emerge scripts and a python installation with it, so you do not need either of them before starting with emerge.

=== Configure the ''emerge'' tool ===
# Create the directory <tt>%KDEROOT%\etc</tt>.
# Copy the file <tt>%KDEROOT%\emerge\kdesettings-example.bat</tt> as <tt>%KDEROOT%\etc\kdesettings.bat</tt> and change its contents according to your needs. The options are described in the ''rem'' lines in the file itself.

The kdesettings.bat script will be called by the main kdeenv.bat script.

Note 1: '''Be sure that you neither have the msys/bin nor the cygwin/bin in your path. If so you have to definitely remove it from the path.'''

Note 2 '''from a user: The applications gimp, inkscape and graphviz are also a problem. To make sure that there's nothing wrong I stripped my path to contain only what I needed to build.'''

Note 3 '''from another user: be careful when renaming the file to "kdesettings.bat" it is easy to end up with "kdesettings.bat.bat" instead of what you want since Windows(by default) will not show the the file extension part of a file.'''

=== [Optional, Advanced] emergehosts.conf ===
Add a file emergehosts.conf in the <tt>%KDEROOT%\etc</tt> directory. The format of this file is a typical config file with only two entries per section:
The first entry is the ''host'' as mentioned in the portage file for the package. The second entry is called ''replace'' and is the replace string for the host string.

As an example, here is how to checkout all gitorious based repos of the kde-developers group using a push url instead of the anonymous access:
<code>
[qt gitorious]
host: git://gitorious.org/+kde-developers/
replace: git@gitorious.org:+kde-developers/
</code>

As a second example here is how to checkout with a ssh user from a subversion repository:
<code>
[svn.example.com]
host: svn://svn.example.com/
replace: svn+ssh://user@svn.example.com/
</code>

The name of the section doesn't matter and can be used for descriptions.

== Using emerge ==

To use emerge you need to start a console window and point that to <tt>%KDEROOT%\emerge</tt>. For example:

C:
cd \%KDEROOT%\emerge

Then you have to execute

kdeenv.bat

This tells emerge about your environment settings (e.g. paths). It will load your configuration from <tt>%KDEROOT%\etc\kdesettings.bat</tt>. It should not give any error messages, otherwise emerge will not work as expected. The output should look similar to this one (of course with your paths):

C:\kderoot\emerge>kdeenv.bat
kdesettings.bat executed
KDEROOT : C:\kderoot
KDECOMPILER : mingw
KDESVNDIR : C:\kderoot\svn
PYTHONPATH : C:\python27
DOWNLOADDIR : C:\kderoot\download

C:\kderoot\emerge>

Next, if you have configured your kdesettings.bat to use svn+ssh for your subversion checkout, then you need to run:

<code>plink <your-svn-username>@svn.kde.org
plink <your-kde-username>@git.kde.org</code>

This will prompt you to accept the fingerprint of the server, otherwise svn will hang forever when trying to download from the server.

Now you should be able to use emerge. Type

emerge --help

to get some help on usage.

''Note: There is a short path option in kdesettings which you will
need if you want to build Qt in a directory that has a pathlenght of
more then around 5 characters. This problem is due to limitations of the command line length and the Qt build system.''

== Setting up a compiler ==
Currently emerge supports both the MinGW and MS Visual C++ (msvc) compilers. We did not add dependencies for the compilers, so you have to make sure to install a compiler by yourself. There are three ways to set up a compiler for emerge.
We assumed you have set KDECOMPILER variable properly in the <tt>%KDEROOT%\etc\kdesettings.bat</tt>.

In the following sections you can find information on how to install or reuse an existing compiler.

=== Install the MinGW compiler with emerge ===
Let emerge install the MinGW compiler, as soon as emerge needs MinGW it will automatically fetch the correct version for you.

=== Install MS Visual C++ ===
Read [[../MS_Visual_Studio#The_Compiler|here]].

=== Point to an existing MS Visual C++ installation ===
You need to point emerge to an existing msvc installation. This is run automatically for you from kdeenv.bat if configured properly in kdesettings.bat. Check your kdesettings.bat file to know where to set it.

== Installing the base system ==
Once you have emerge and a compiler installed and working, try:
* <tt>emerge --help</tt> for a list of available commands
* <tt>emerge --print-installable</tt> to get a list of available packages
* <tt>emerge --print-installed</tt> to get a list of currently installed packages
Further options are described below.

You are now ready to start building KDE, it is recommended to do so progressively, relying on emerge to automatically resolve the required dependencies at each set step:

* Enter <tt>emerge qt</tt>. This will fetch and install Windows versions of numerous UNIX-like utilities and libraries, then checkout, compile and install Qt. This will take several hours.
* Enter <tt>emerge kdelibs</tt>. This will checkout, compile and install the required kdesupport modules and then kdelibs.
* Enter <tt>emerge kdebase-apps</tt>. This will checkout, compile and install kdebase-runtime, and kdebase-apps

You will now have successfully installed a base KDE system and can now install other KDE modules as required.

Note that this will install the trunk version of KDE, if you wish to install a particular stable branch then you must prefix the KDE package names with the required version, i.e. <tt>emerge kde-4.5/kdelibs</tt>. You can force emerge to always default to a given branch by setting the <tt>EMERGE_DEFAULTCATEGORY</tt> variable in your kdesettings.bat file. You should not mix kde packages from different branches.

It is strongly recommened you do not choose to manually install any of the utilities and libraries yourself, as you may install the wrong version and cause installation failures. Instead allow emerge to resolve the dependencies for you.

Every time you want to update or install a package, you should first update your emerge checkout (simply run emerge --update emerge) to ensure you are using the latest package recipies.

== What emerge does ==
'''emerge ''packageName'' ''' performs the separate actions <tt>--fetch</tt>, <tt>--unpack</tt>, <tt>--compile</tt>, <tt>--install</tt>, <tt>--manifest</tt>, and <tt>--qmerge</tt>.

The <tt>--fetch</tt> action will retrieve either a binary or the source code for the package:
* If a binary package, this will be downloaded into the <tt>DOWNLOADDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\download</tt>.
* If a non-KDE source package, the source repository will be checked-out into <tt>%DOWNLOADDIR%\svn-src</tt>, e.g. Qt source may be found in <tt>C:\kderoot\download\svn-src\qt</tt>.
* If a KDE source package from the <tt>svn.kde.org</tt> repository, then the source will be checked-out into the <tt>KDESVNDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\svn</tt>.

== ''emerge'' command line options and settings ==
There are some options that can be used when building with ''emerge''.

{| border="0" cellpadding="2"
!Command line switch
!Command line argument
!
!Description
|-valign="top"
|<tt>-v</tt>
|<tt>EMERGE_VERBOSE</tt>
|width="5%"|
|This option sets the verbosity level. Currently the highest verbosity level is 3 (<tt>-v -v -v</tt>). A verbosity level of 0 should give no output and equals to <tt>-q</tt>. You can set <tt>EMERGE_VERBOSE=3</tt> instead in the environment of the commandline or within your <tt>kdesettings.bat</tt> file.
|-valign="top"
|<tt>--offline</tt>
|
|
|This option suppresses the update step of the local tree - which needs some time. Be aware though that you have to have existing sources already if you want to use this option.
|-valign="top"
|<tt>-t</tt>
|<tt>EMERGE_BUILDTESTS</tt>
|
|This option enables or disables KDE4 buildtests for KDE modules. Other packages will not change. Use <tt>EMERGE_BUILDTESTS=True</tt> or <tt>=False</tt>.
|-valign="top"
|<tt>--print-targets</tt>
|
|
|This option will display all "targets" a certain package has. Normally targets are fixed releases or different branches. They are defined in the portage file.
|-valign="top"
|<tt>--target=TARGET</tt>
|
|
|This sets a specific target for this package. If not added, the default target is used, which can be checked by looking at the output of '''--print-targets'''.
|-valign="top"
|<tt>-i</tt>
|
|
|This option ignores that a package is already installed. It builds it completely new, but keeps the dependencies.
|-valign="top"
|<tt>--update</tt>
|
|
|This option ignores that a package is already installed but doesn't cleanup an already existing build directory. Thus you will only rebuild files that have changed since the last build.
|}

== Hints ==
=== Updating packages ===
*Once you have ''packagename'' built, type <code>emerge --update packagename</code> to update <tt>packagename</tt> from the Subversion and compile it without removing the build dir or <code>emerge --update-all</code> to update all packages that can be rebuild (they are rebuild with --update).

=== General setup ===
For Fine Tuning see here:
[[Projects/KDE_on_Windows/Installation#Fine-tuning|Fine-tuning]]

== Notes ==

''emerge'' can mostly cooperate with the [[Projects/KDE_on_Windows/Installation#KDE_Installer_for_Windows|kdewin-installer]] but we're currently still working on some packages which are packaged in a wrong way.
It is not recommended to use another layout then '''installer''' for '''directory_layout''' in the '''kdesettings.bat''' anymore (see that file for more detailed information).

''emerge'' creates lots of files in '''\kderoot\tmp''' during build.
After a package is successfully installed
(check '''\kderoot\etc\portage\installed''' or the directory '''\kderoot\manifest\'''), you can delete its temporary directory.

Windows ''emerge'' is derived from the Gentoo portage system, but we are currently not enforcing compatibility. If you have questions about that please contact us at the channel #kde-windows on irc.freenode.net.

last reviewed by [[User:SaroEngels|SaroEngels]] 22:25, 4 November 2010 (UTC)

==Vista issues==
*[[User:Jstaniek|jstaniek]] 12:02, 15 January 2008 (CET): UAC has infamous heuristics that make programs like patch.exe treat as installers and try to run them with admin rights (!). This heuristics can be tricked by renaming patch.exe to something like pch.exe ([http://nevali.net/2007/01/update-workaround-for-the-cygwin-uac-problem/ example]) but we did not want to add item to our infrastructure. Instead it is possibleto turn off the heuristics (see the screenshot [http://theinvisiblethings.blogspot.com/2007/02/running-vista-every-day.html here in the security blog calling the heuristics 'severe hole in the design of UAC']). If you happen to disable the UAC, as many annoyed users and devs do (msvc demands admin rights anyway!), patch.exe should already work for you as in older Windows. Alternatively you may want to disable UAC [http://www.howtogeek.com/howto/windows-vista/disable-user-account-controluac-for-administrators-only/ for admins only], but this makes no sense if you are the only user of your machine and use only the admin account.
* [http://ben.versionzero.org/wiki/Fixing_the_way_Vista_Auto-detects_Installers This wiki page] lists instructions on how to use program manifest to disable privilege elevation for a single binary and makes patch play nice with UAC. This [https://bugs.kde.org/show_bug.cgi?id=186712 should] eventually be integrated to emerge scripts.

[[Category:MS Windows]]

Getting Started/Build/Windows/emerge

2011-01-07T12:09:34Z

Wrohdewald: plink also for the kde git server

''emerge'' is a tool to build the KDE sources and its third-party requirements on MS Windows. It is the '''easy''' way to build KDE on MS Windows.

== Introduction ==
Emerge is a tool that can build the different parts of KDE and its dependencies under Windows. We created this tool to automate and simplify the build process under Windows. We try to build all packages that we offer in the KDE installer with emerge. That has some advantages for us:
* it is easy for people to join us:
Before emerge it was quite some work to set a system up for development. There were some quirks, which were documented in some mailing lists, but you had to remember them or you ran into an already solved problem again, etc.
Now to get a development machine you need a Windows computer, need to install Python and Subversion and do the emerge checkout. Then execute emerge to build what you want to build. This is easy for developers coming from Windows to KDE, and also for KDE developers coming to Windows.
* it is easy for us to do (nightly/continuous/release/reproducable/...) builds:
With emerge you can build the whole software stack (low-level libs, Qt, kdelibs, things above that) with only one command. You can start that build, and some hours later you can check if it worked, or if something broke. So we can spot problems easier and earlier. We can also start with a "naked" Windows computer without any other installed software and bootstrap kde on it. That ensures, that no hidden dependencies on some pieces of software sneak in, because then the builds on a "naked" computer would break and show the problem.
* it is easier to collaborate:
We can test the same emerge build description for a package on different Windows versions/computers before we do binary releases. People can also add build descriptions for new packages to the Subversion repository.

This emerge tool was inspired by the Gentoo emerge tool.

== Set up the environment ==
=== Root directory ===
Create a directory if possible in your harddrive's root e.g. C:\kderoot or D:\kderoot (You will need this PATH later). This directory will contain the whole kde installation later. We will refer to it as %KDEROOT%.

=== Python interpreter ===
<tt>emerge.bat</tt> invokes an <tt>emerge.py</tt> script written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] programming language, so you first need to [http://www.python.org/download/ install the Python 2.7 Interpreter]. The ''python'' installation directory will be added to the PATH later by <tt>%KDEROOT%\etc\kdesettings.bat</tt> script.

=== Subversion client ===
The latest source code for Windows ''emerge'' and the rest of KDE is stored in a repository created and managed using the [http://subversion.tigris.org/ Subversion] version control tool. You need a Subversion client for the first checkout. There are at least two applications:
*a command line client, available at [http://subversion.apache.org/packages.html subversion.apache.org] '''(required by emerge to get the source code from KDE Subversion repository)''', aimed at developers or power users accustomed with the command line,
*GUI program like [http://tortoisesvn.tigris.org/ TortoiseSVN], optional, useful for displaying differences between various versions of files in the repository in a graphical way.

Note 1: If you experience problems with the checkout of Qt (Subversion doesn't work correctly) please remove any other Subversion binaries out of the path that you do have. '''The different versions of the Apache portable runtime (APR) are incompatible!'''

Note 2: Make sure to use a copy of Subversion that was built on Windows so that checked-out files do not use UNIX line endings. If you check out with UNIX line endings, the ''patch'' program will fail when attempting to apply a patch whose line endings don't match the system's.

=== Getting the ''emerge'' tool ===
The source code of the ''emerge'' tool and the recipes for creating KDE packages are located at <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt>, which is an URL based on Subversion-specific ''svn'' protocol.

You need to check out the source code from the ''emerge'' Subversion directory into a new directory below your root directory (the root directory is normally called %KDEROOT% here) or get it inside a self extracting archive (not tested yet).

==== Check out using the 'svn' command ====

*Option 1: With the ''svn'' command line tool, you can accomplish this with the following commands:<pre>cd %KDEROOT%</pre>
**if you will only use anonymous (read-only) access to the KDE svn repository:<pre>svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
**or, if you plan to use write access (commit) to the KDE svn repository
***via https:<pre>svn co --username yourusername https://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>
***via a [[Getting_Started/Build/KDE4/Windows/subversion|puTTY tunnel]] using your existing account & OpenSSH private key: <pre>svn co svn+putty://svn.kde.org/home/kde/trunk/kdesupport/emerge</pre>

This would result with:

Error validating server certificate for '<nowiki>https://svn.kde.org:443</nowiki>':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: svn.kde.org
- Valid: from Wed, 11 May 2005 09:08:21 GMT until Sat, 09 May 2015 09:08:21 GMT
- Issuer: SVN, KDE e.V., Nuernberg, Bavaria, DE
- Fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
(R)eject, accept (t)emporarily or accept (p)ermanently?

enter ''p'' here to permanently accept the certificate:

Authentication realm: <<nowiki>https://svn.kde.org:443</nowiki>> KDE SVN account
Password for 'yourusername': ***************
A emerge\kdeenv.bat
A emerge\portage
A emerge\portage\kdesupport
[....]

The password and cache for the certificates is saved in <tt>%APPDATA%\Subversion\auth</tt> directory.

==== Check out using the TortoiseSVN ====

*Option 2: If you use TortoiseSVN:
*#right-click on your %KDEROOT% folder and select ''SVN Checkout...'' command from the context menu,
*#paste <tt>svn://anonsvn.kde.org/home/kde/trunk/kdesupport/emerge</tt> URL into the ''URL of repository'' text box (replace with <tt><nowiki>https://svn.kde.org/home/kde/trunk/kdesupport/emerge</nowiki></tt> for read-write access)
*#add <tt>\emerge</tt> to the folder name in the ''Checkout directory'' box and click OK to continue
*#if you picked the read-write access, you will be asked for accepting the SSL certificate of the SVN server (click "Premanent") and then for username and password. For convenience select "Save authentication" checkbox too (the password and cache for the certificates will be saved in <tt>%APPDATA%\Subversion\auth</tt> directory).

After the checkout you should have the directory <tt>%KDEROOT%\emerge</tt>. If you don't, you move your ''emerge'' directory to that location.

==== Installing from the self-extracting archive ====
*Option 3: Get the self-extracting archive from [http://www.winkde.org/pub/kde/ports/win32/emerge/emerge-latest.exe here], unpack it into your KDEROOT directory so that you have a folder %KDEROOT%\emerge.
* This self-extracting archive brings a subversion repository containing the emerge scripts and a python installation with it, so you do not need either of them before starting with emerge.

=== Configure the ''emerge'' tool ===
# Create the directory <tt>%KDEROOT%\etc</tt>.
# Copy the file <tt>%KDEROOT%\emerge\kdesettings-example.bat</tt> as <tt>%KDEROOT%\etc\kdesettings.bat</tt> and change its contents according to your needs. The options are described in the ''rem'' lines in the file itself.

The kdesettings.bat script will be called by the main kdeenv.bat script.

Note 1: '''Be sure that you neither have the msys/bin nor the cygwin/bin in your path. If so you have to definitely remove it from the path.'''

Note 2 '''from a user: The applications gimp, inkscape and graphviz are also a problem. To make sure that there's nothing wrong I stripped my path to contain only what I needed to build.'''

Note 3 '''from another user: be careful when renaming the file to "kdesettings.bat" it is easy to end up with "kdesettings.bat.bat" instead of what you want since Windows(by default) will not show the the file extension part of a file.'''

=== [Optional, Advanced] emergehosts.conf ===
Add a file emergehosts.conf in the <tt>%KDEROOT%\etc</tt> directory. The format of this file is a typical config file with only two entries per section:
The first entry is the ''host'' as mentioned in the portage file for the package. The second entry is called ''replace'' and is the replace string for the host string.

As an example, here is how to checkout all gitorious based repos of the kde-developers group using a push url instead of the anonymous access:
<code>
[qt gitorious]
host: git://gitorious.org/+kde-developers/
replace: git@gitorious.org:+kde-developers/
</code>

As a second example here is how to checkout with a ssh user from a subversion repository:
<code>
[svn.example.com]
host: svn://svn.example.com/
replace: svn+ssh://user@svn.example.com/
</code>

The name of the section doesn't matter and can be used for descriptions.

== Using emerge ==

To use emerge you need to start a console window and point that to <tt>%KDEROOT%\emerge</tt>. For example:

C:
cd \%KDEROOT%\emerge

Then you have to execute

kdeenv.bat

This tells emerge about your environment settings (e.g. paths). It will load your configuration from <tt>%KDEROOT%\etc\kdesettings.bat</tt>. It should not give any error messages, otherwise emerge will not work as expected. The output should look similar to this one (of course with your paths):

C:\kderoot\emerge>kdeenv.bat
kdesettings.bat executed
KDEROOT : C:\kderoot
KDECOMPILER : mingw
KDESVNDIR : C:\kderoot\svn
PYTHONPATH : C:\python27
DOWNLOADDIR : C:\kderoot\download

C:\kderoot\emerge>

Next, if you have configured your kdesettings.bat to use svn+ssh for your subversion checkout, then you need to run:

<code>plink <your-svn-username>@svn.kde.org
plink <your-kde-username>@git.kde.org</code>

This will prompt you to accept the fingerprint of the server, otherwise svn will hang forever when trying to download from the server.

Now you should be able to use emerge. Type

emerge --help

to get some help on usage.

''Note: There is a short path option in kdesettings which you will
need if you want to build Qt in a directory that has a pathlenght of
more then around 5 characters. This problem is due to limitations of the command line length and the Qt build system.''

== Setting up a compiler ==
Currently emerge supports both the MinGW and MS Visual C++ (msvc) compilers. We did not add dependencies for the compilers, so you have to make sure to install a compiler by yourself. There are three ways to set up a compiler for emerge.
We assumed you have set KDECOMPILER variable properly in the <tt>%KDEROOT%\etc\kdesettings.bat</tt>.

In the following sections you can find information on how to install or reuse an existing compiler.

=== Install the MinGW compiler with emerge ===
Let emerge install the MinGW compiler, as soon as emerge needs MinGW it will automatically fetch the correct version for you.

=== Install MS Visual C++ ===
Read [[../MS_Visual_Studio#The_Compiler|here]].

=== Point to an existing MS Visual C++ installation ===
You need to point emerge to an existing msvc installation. This is run automatically for you from kdeenv.bat if configured properly in kdesettings.bat. Check your kdesettings.bat file to know where to set it.

== Installing the base system ==
Once you have emerge and a compiler installed and working, try:
* <tt>emerge --help</tt> for a list of available commands
* <tt>emerge --print-installable</tt> to get a list of available packages
* <tt>emerge --print-installed</tt> to get a list of currently installed packages
Further options are described below.

You are now ready to start building KDE, it is recommended to do so progressively, relying on emerge to automatically resolve the required dependencies at each set step:

* Enter <tt>emerge qt</tt>. This will fetch and install Windows versions of numerous UNIX-like utilities and libraries, then checkout, compile and install Qt. This will take several hours.
* Enter <tt>emerge kdelibs</tt>. This will checkout, compile and install the required kdesupport modules and then kdelibs.
* Enter <tt>emerge kdebase-apps</tt>. This will checkout, compile and install kdebase-runtime, and kdebase-apps

You will now have successfully installed a base KDE system and can now install other KDE modules as required.

Note that this will install the trunk version of KDE, if you wish to install a particular stable branch then you must prefix the KDE package names with the required version, i.e. <tt>emerge kde-4.5/kdelibs</tt>. You can force emerge to always default to a given branch by setting the <tt>EMERGE_DEFAULTCATEGORY</tt> variable in your kdesettings.bat file. You should not mix kde packages from different branches.

It is strongly recommened you do not choose to manually install any of the utilities and libraries yourself, as you may install the wrong version and cause installation failures. Instead allow emerge to resolve the dependencies for you.

Every time you want to update or install a package, you should first update your emerge checkout (simply run emerge --update emerge) to ensure you are using the latest package recipies.

== What emerge does ==
'''emerge ''packageName'' ''' performs the separate actions <tt>--fetch</tt>, <tt>--unpack</tt>, <tt>--compile</tt>, <tt>--install</tt>, <tt>--manifest</tt>, and <tt>--qmerge</tt>.

The <tt>--fetch</tt> action will retrieve either a binary or the source code for the package:
* If a binary package, this will be downloaded into the <tt>DOWNLOADDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\download</tt>.
* If a non-KDE source package, the source repository will be checked-out into <tt>%DOWNLOADDIR%\svn-src</tt>, e.g. Qt source may be found in <tt>C:\kderoot\download\svn-src\qt</tt>.
* If a KDE source package from the <tt>svn.kde.org</tt> repository, then the source will be checked-out into the <tt>KDESVNDIR</tt> defined in your <tt>kdesettings.bat</tt>, which is usually <tt>%KDEROOT%\svn</tt>.

== ''emerge'' command line options and settings ==
There are some options that can be used when building with ''emerge''.

{| border="0" cellpadding="2"
!Command line switch
!Command line argument
!
!Description
|-valign="top"
|<tt>-v</tt>
|<tt>EMERGE_VERBOSE</tt>
|width="5%"|
|This option sets the verbosity level. Currently the highest verbosity level is 3 (<tt>-v -v -v</tt>). A verbosity level of 0 should give no output and equals to <tt>-q</tt>. You can set <tt>EMERGE_VERBOSE=3</tt> instead in the environment of the commandline or within your <tt>kdesettings.bat</tt> file.
|-valign="top"
|<tt>--offline</tt>
|
|
|This option suppresses the update step of the local tree - which needs some time. Be aware though that you have to have existing sources already if you want to use this option.
|-valign="top"
|<tt>-t</tt>
|<tt>EMERGE_BUILDTESTS</tt>
|
|This option enables or disables KDE4 buildtests for KDE modules. Other packages will not change. Use <tt>EMERGE_BUILDTESTS=True</tt> or <tt>=False</tt>.
|-valign="top"
|<tt>--print-targets</tt>
|
|
|This option will display all "targets" a certain package has. Normally targets are fixed releases or different branches. They are defined in the portage file.
|-valign="top"
|<tt>--target=TARGET</tt>
|
|
|This sets a specific target for this package. If not added, the default target is used, which can be checked by looking at the output of '''--print-targets'''.
|-valign="top"
|<tt>-i</tt>
|
|
|This option ignores that a package is already installed. It builds it completely new, but keeps the dependencies.
|-valign="top"
|<tt>--update</tt>
|
|
|This option ignores that a package is already installed but doesn't cleanup an already existing build directory. Thus you will only rebuild files that have changed since the last build.
|}

== Hints ==
=== Updating packages ===
*Once you have ''packagename'' built, type <code>emerge --update packagename</code> to update <tt>packagename</tt> from the Subversion and compile it without removing the build dir or <code>emerge --update-all</code> to update all packages that can be rebuild (they are rebuild with --update).

=== General setup ===
For Fine Tuning see here:
[[Projects/KDE_on_Windows/Installation#Fine-tuning|Fine-tuning]]

== Notes ==

''emerge'' can mostly cooperate with the [[Projects/KDE_on_Windows/Installation#KDE_Installer_for_Windows|kdewin-installer]] but we're currently still working on some packages which are packaged in a wrong way.
It is not recommended to use another layout then '''installer''' for '''directory_layout''' in the '''kdesettings.bat''' anymore (see that file for more detailed information).

''emerge'' creates lots of files in '''\kderoot\tmp''' during build.
After a package is successfully installed
(check '''\kderoot\etc\portage\installed''' or the directory '''\kderoot\manifest\'''), you can delete its temporary directory.

Windows ''emerge'' is derived from the Gentoo portage system, but we are currently not enforcing compatibility. If you have questions about that please contact us at the channel #kde-windows on irc.freenode.net.

last reviewed by [[User:SaroEngels|SaroEngels]] 22:25, 4 November 2010 (UTC)

==Vista issues==
*[[User:Jstaniek|jstaniek]] 12:02, 15 January 2008 (CET): UAC has infamous heuristics that make programs like patch.exe treat as installers and try to run them with admin rights (!). This heuristics can be tricked by renaming patch.exe to something like pch.exe ([http://nevali.net/2007/01/update-workaround-for-the-cygwin-uac-problem/ example]) but we did not want to add item to our infrastructure. Instead it is possibleto turn off the heuristics (see the screenshot [http://theinvisiblethings.blogspot.com/2007/02/running-vista-every-day.html here in the security blog calling the heuristics 'severe hole in the design of UAC']). If you happen to disable the UAC, as many annoyed users and devs do (msvc demands admin rights anyway!), patch.exe should already work for you as in older Windows. Alternatively you may want to disable UAC [http://www.howtogeek.com/howto/windows-vista/disable-user-account-controluac-for-administrators-only/ for admins only], but this makes no sense if you are the only user of your machine and use only the admin account.
* [http://ben.versionzero.org/wiki/Fixing_the_way_Vista_Auto-detects_Installers This wiki page] lists instructions on how to use program manifest to disable privilege elevation for a single binary and makes patch play nice with UAC. This [https://bugs.kde.org/show_bug.cgi?id=186712 should] eventually be integrated to emerge scripts.

[[Category:MS Windows]]

Development/Tutorials/Localization/Building KDE's l10n Module

2010-11-30T09:04:50Z

Wrohdewald: revpath: debian/ubuntu has no package imake

{{TutorialBrowser|

series=Localization|

name=Building KDE's l10n Module|

pre=[[Getting_Started/Sources/Using_Subversion_with_KDE|Using Subversion with KDE]] [[Getting_Started/Build/KDE4|Building KDE From Subversion]] [[../i18n|Writing Applications With Localization in Mind]]|

}}

== Abstract ==

For those working on applications in KDE's main repository, building and installing language support from KDE's localization (l10n) module is a good idea. Doing so will allow you to test applications in other languages so as to spot problems related to localization that may exist in KDE. Learn how to do just that in this tutorial.

== Step 1: l10n ==

You must download, build and install each language in the l10n module separately. You can check out and build just the German, and XX languages using the following procedure:

svn co -N svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4 l10n
cd l10n
svn up scripts
svn up templates
svn up x-test
svn up de
./scripts/autogen.sh de
./scripts/autogen.sh x-test

Once this is done, switch to your build directory, start cmake in the <tt>l10n/x-test</tt>, <tt>l10n/de</tt>, etc directories that you wish to build the language support for one at a time. You may then make and install from the build directory.

{{note|You need revpath (may be found in package imake or xutils-dev) to run autogen.sh}}
{{tip|Do not combine make and make install in a single step. It won't install anything.}}

== Step 2: Test An Application ==

To run your application using, for instance, the German catalogs open a terminal (e.g. konsole) and type:

KDE_LANG=de myapp

where "myapp" is the name of the application you wish to test. Replace the "de" with the language code you wish to test, e.g. "x-test".

The German language is a good choice for testing the layout of your application, as German translated strings tend to be quite long. French is also a good choice. The x-test language is useful for identifying strings in your application that are not translated.

Schedules/KDE4/4.6 Feature Plan

2010-11-09T08:49:58Z

Wrohdewald:

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

See also:

*[[Schedules/KDE4/4.6 Release Schedule]]
*[[Schedules/KDE4/4.6 Release Goals]]
*[[Schedules/KDE4/4.5 Feature Plan]] (previous major release)

 Legend:

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

__TOC__

 

= kdebase-apps =

{| 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|Konsole|Move to KTabWidget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Dolphin|Faceted browsing via Nepomuk|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Dolphin|Searching support for non-indexed files|peter.penz19@gmail.com|Peter Penz}}
{{FeatureInProgress|Dolphin|Git-plugin (implemented by Sebastian Dörner and Johannes Steffen)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin| Resizeable columns in the column-view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin| Allow leading zeros when renaming multiple files (implemented by Matthias Fuchs)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureInProgress|nspluginviewer|Full npruntime support|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|Dolphin|Smooth scrolling|fredrik@kde.org|Fredrikh Höglund}}
|}

 

= kdebase-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|Plasma|Plasma KPart|ry@n.rix.si|Ryan Rix}}
{{FeatureInProgress|Plasma|Declarative AppletScript to write QML plasmoids|mart@kde.org|Marco Martin}}
{{FeatureInProgress|Plasma|Optimize the Newspaper containment for the use with touchscreens and the Plasma KPart|mart@kde.org|Marco Martin}}
{{FeatureDone|KWin|Focus tracking for the zoom plugin (uses kaccessible)|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KWin|Extend mouse tracking modes for the zoom plugin|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Nepomuk Backup & Sync| Provide Backup and Sync capabilities to Nepomuk|handa.vish@gmail.com|Vishesh Handa}}
{{FeatureTodo|Web Metadata extractor| Provide a framework to get additional data about resources|handa.vish@gmail.com|Vishesh Handa}}
{{FeatureDone|Activities manager service|Merge the kded and nepomuk modules for activities into one service|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|Activities manager service|Register desktop events instead directly linking the activities to resources|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|KNotify|Add support for relative present actions in contexts|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|KNotify|Add Plugin Loading Support|j.maceachern@gmail.com|Jeffery MacEachern}}
{{FeatureInProgress|Locale KCM|Complete re-write to improve usability, support for new localization features|john@layt.net|John Layt}}
{{FeatureInProgress|Phonon KCM|Add video input device configuration support|kiagiadakis.george@gmail.com|George Kiagiadakis}}
{{FeatureInProgress|ksecretserviced|Make it replace KWallet|lemma@confuego.org|Michael Leupold}}
|}

 

= kdebase-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
|-
! style="text-align: center;" colspan="4" | Plasma
{{FeatureInProgress|libtaskmanager / tasks-applet| support for Windows 7 like launchers |akreuzkamp@web.de|Anton Kreuzkamp}}
{{FeatureInProgress|notifications| rework notification applet appearance |mart@kde.org|Marco Martin}}
{{FeatureInProgress|notifications| make various dataengines use Plasma::Storage |mart@kde.org|Marco Martin}}
{{FeatureDone|plasma-desktop| UI for editing activity name and icon|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|plasma-desktop| add some default activities|fux@kde.org|Mario Fux}}
{{FeatureDone|plasma| finish support for activity templates |chani@kde.org|Chani}}
{{FeatureInProgress|plasma-devicenotifier| Improve notification support |wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureTodo|plasma-devicenotifier| Signal to the user which apps are blocking a device|wilderkde@gmail.com |Jacopo De Simoi}}
{{FeatureDone|quicklaunch| populate new applets with user's default browser, file manager, ... instead of hardcoded ones |ingomar@wesp.name|Ingomar Wesp}}
{{FeatureDone|quicklaunch| allow editing of existing launchers (including ones that do not point to a .desktop file) |ingomar@wesp.name|Ingomar Wesp}}
{{FeatureInProgress|quicklaunch| better layout for desktop and media center form factors |ingomar@wesp.name|Ingomar Wesp}}
{{FeatureInProgress|libplasma|Improvements to Calendar/Clock widgets. Improved config ui. Allow multiple holidays on same day. Allow multiple Holiday Regions. Weekends. etc.|john@layt.net|John Layt}}
{{FeatureInProgress|libplasma|Make Calendar DataEngine a Service.|john@layt.net|John Layt}}
{{FeatureTodo|plasma-desktop| integrate activity-sessions|chani@kde.org|Ivan/Chani}}
{{FeatureInProgress|plasma-desktop|activity dataengine|chani@kde.org|Chani}}
|-
! style="text-align: center;" colspan="4" | KWin
{{FeatureInProgress|windowgeometry effect| compositor powered move/resize windowgeometry display |thomas.luebking@web.de|Thomas Lübking}}
{{FeatureInProgress|dashboard effect| new effect for Plasma dashboard |ademmer@opensuse.org|Andreas Demmer}}
{{FeatureDone|kwin/ksmserver| activity sessions |chanika@gmail.com|Chani}}
{{FeatureTodo|libtaskmanager/kwin?| combine the three window-contextmenu codebases into one |chani@kde.org|Chani}}
{{FeatureTodo|libtaskmanager/kwin] | Expose Window Tabs to taskmanager |kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|kwin|ARB Shader support|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|Aurorae|Tooltips on window tabs|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Present Windows|Close window GUI control|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Startup Feedback|Effect to replace the Startup Feedback notification|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Screenshot Effect|KSanpshot can use KWin for screenshots|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KCM Compositing|Allow compositing even if GL is buggy/X crashes|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin Killer|Use notification instead of dialog|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|Compositing|Improved platform detection|fredrik@kde.org|Fredrik Höglund}}

|-
! style="text-align: center;" colspan="4" | KDE Power Management system
{{FeatureDone|core| PowerDevil v2 core |drf@kde.org|Dario Freddi}}
{{FeatureDone|actions| Basic actions for feature parity with PowerDevil v1 |drf@kde.org|Dario Freddi}}
{{FeatureInProgress|actions| More actions for advanced users |drf@kde.org|Dario Freddi}}
{{FeatureInProgress|policy-handler| Create a new policy handler for handling inhibition properly, and have kdelibs' Solid API use it |drf@kde.org|Dario Freddi}}
|-
! style="text-align: center;" colspan="4" | System Settings
{{FeatureInProgress|keyboard| Support for sticky layout switching |arysin@gmail.com|Andriy Rysin}}
{{FeatureInProgress|keyboard| Support for > 4 layouts|arysin@gmail.com|Andriy Rysin}}
{{FeatureInProgress|driconf|New module for configuring DRI drivers|fredrik@kde.org|Fredrik Höglund}}
|-
! style="text-align: center;" colspan="4" | Blue Devil
{{FeatureInProgress|Review| Get into kdebase|alex@eyeos.org|Alex Fiestas}}
{{FeatureInProgress|kio_obexftp| Better error handling|alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|usability|Review all the components improving hig/elegance|alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|share folders|Be able to share folders via obexftp|alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|Devices KCM|Add further information about devices, like address...|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|Devices KCM|Allow to connect to devices services|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|libbluedevil|Review DBus handling|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|libbluedevil|Add support for services|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|Monolithic|Fix listing problems under certain conditions|ereslibre@kde.org|Rafael Fernández López}}
|}

 

= 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|libnepomuk|Convenience operator overloads for query construction|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|libnepomuk|New query flags and improved handling of full text matching scores including sorting|trueg@kde.org|Sebastian Trueg}}
{{FeatureTodo|kdeui|Generic find bar widget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureDone|kdeui|Allow getting and setting the size of the pixmap cache in KImageCache|2kmm@gmx.de|Manuel Mommertz}}
{{FeatureDone|katepart|scripted actions|dhaumann@kde.org|Dominik Haumann}}
{{FeatureDone|katepart|QAccessibleInterface's for document+cursor|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|libplasma|PluginLoader class|ry@n.rix.si|Ryan Rix}}
{{FeatureDone|libplasma|Allow SVGs to use systemcolors before rendering|2kmm@gmx.de|Manuel Mommertz}}
{{FeatureInProgress|libplasma|DeclarativeWidget to load QML scenes in Plasma|mart@kde.org|Marco Martin}}
{{FeatureInProgress|libplasma|finish up the gsoc project about Plasma::Storage service|mart@kde.org|Marco Martin}}
{{FeatureDone|libplasma|let Plasma::SVG find the best matching size hinted element if there is no exact match|ingomar@wesp.name|Ingomar Wesp (mentored by Manuel Mommertz)}}
{{FeatureInProgress|libnepomuk/KIO|Search excerpts|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuk|Standardqueries for convenience|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuk|GUI elements for resource/file searching including faceted browsing|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuksync|Sync library to be used in BackupSync, Strigi, Akonadi, WebExtractor and Removable Media|handa.vish@gmail.com|Vishesh Handa}}
{{FeatureInProgress|kdecore|Add more possible synchronization primitives to KSharedDataCache to expand OS support. POSIX Semaphores Contributed by Alberto Villa of the FreeBSD project. Windows support may still occur as well.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdecore|Add fallback to QCache<QString,QByteArray> in KSharedDataCache.|mpyne@kde.org|Michael Pyne}}
{{FeatureDone|kdecore|Add cache-wide timestamp to KSharedDataCache.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdecore|Add ability to make KSharedDataCache strictly read-only for laptop support.|mpyne@kde.org|Michael Pyne}}
{{FeatureInProgress|kdeui|Social About Dialog|teo@kde.org|Teo Mrnjavac}}
{{FeatureInProgress|kdeui|Allow to hide icons in menus|christoph@maxiom.de|Christoph Feck}}
{{FeatureTodo|KCalendarSystem||john@layt.net|John Layt}}
{{FeatureTodo|KCalendarSystem|Add astronomical calculation support classes and astronomical based calendars.|john@layt.net|John Layt}}
{{FeatureDone|KCalendarSystem|Add api for first/last day of year/month.|john@layt.net|John Layt}}
{{FeatureInProgress|KDate|New convenience class to make date localization easy.|john@layt.net|John Layt}}
{{FeatureDone|KLocale|Add configuration for AM/PM symbols.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Add default colour to optionally display negative numbers.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Add more date formats.|john@layt.net|John Layt}}
{{FeatureInProgress|KLocale|Full POSIX compliant format support for date, time, numbers and money, including but not limited to: traditional/US week numbers, AM/PM symbols, number grouping|john@layt.net|John Layt}}
{{FeatureInProgress|KLocale|Implement separate backends for each supported platform/desktop to use platform localization in place of KDE locale.|john@layt.net|John Layt}}
{{FeatureInProgress|KLocale|Implement support for Country Code sub-regions and other country code standard conversions.|john@layt.net|John Layt}}
{{FeatureInProgress|KHTML|HTML5 postMessage.|maksim@kde.org|Maksim Orlovich}}
{{FeatureTodo|kcookiejar|New domain specific cookie policy based on patch provided in bug#54300|adawit@kde.org|Dawit A.}}
{{FeatureInProgress|kcookiejar|Implement storing cookies in KWallet|fid@gpul.org|José Millán Soto}}
{{FeatureInProgress|ksecretservice|Make KWallet::Wallet use the secrets-service API|lemma@confuego.org|Michael Leupold}}
{{FeatureInProgress|anywhere|Allow to build without deprecated symbols|ervin@kde.org|Kevin Ottens (with lots of support from David Faure)}}
{{FeatureInProgress|KIO|Use `net usershare` in KSambaShare|rclbelem@gmail.com|Rodrigo Belem}}
|}

 

= 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
{{FeatureDone|Marble|Loading of routes in .kml format (Maemo)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Route printing (map and directions, configurabe)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Route state saving and restoring|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Convert MarbleRunners to plugins|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|worldwide and offline routing|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Extend MarbleRunner interface to handle reverse geocoding and routing requests; Display of alternative routes|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Routing API|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|"Go To" dialog for Maemo|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Tile download along the route for offline usage|akssps011@gmail.com|Siddharth Srivastava}}
{{FeatureDone|Marble|Turn-by-turn navigation mode|akssps011@gmail.com|Siddharth Srivastava}}
{{FeatureTodo|Marble|QtDeclarative plugin (possibly rather in 4.7)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Implement sun locator blendings as derived classes of Marble::Blending|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|Marble|Separate thread for tile loading and texture blending (not texture mapping at the moment) for more smooth browsing|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|Marble|Tile loading "read ahead" when idle, prerequisite: threaded tile loading|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|Marble|Multi threaded texture mapping|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureDone|Marble|Improve GeoData API|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Convert Gps tracking to GeoDataDocument|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Provide a treeModel for GeoDataDocuments|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Draw the geometries of multiple GeoDataDocuments|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Marble|Load Pnt vector data files as GeoData|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Marble|Manipulate Gps track data|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Cantor|Backend for GNU Octave|miha.cancula@gmail.com|Miha Čančula}}
{{FeatureInProgress|Cantor|Merge R improvement branch|alexanderrieder@gmail.com|Alexander Rieder}}
{{FeatureInProgress|Cantor|Variable management panel|alexanderrieder@gmail.com|Alexander Rieder}}
{{FeatureTodo|Cantor|Formulas inside Text Entries|alexanderrieder@gmail.com| Alexander Rieder}}
{{FeatureDone|Kalzium|Port Kalzium to use QGV based periodic table widget|mhanwell@kde.org|Marcus D. Hanwell}}
{{FeatureDone|KAlgebra|Implicit functions plot|percy.camilo.ta@gmail.com|Percy Aucahuasi}}
{{FeatureDone|KAlgebra|Improved execution speed on the calculator|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra|Better integration between the Console and the Plotting facilities|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra|Lighter version aimed to mobile users|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureInProgress|KStars|OpenGL rendering support for KStars|akarshsimha@gmail.com|Harry de Valence, Akarsh Simha}}
{{FeatureInProgress|KStars|Better designed object database|akarshsimha@gmail.com|Victor Carbune, Akarsh Simha}}
{{FeatureInProgress|KStars|Star Hop Generator|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureDone|Kig|LaTeX/TikZ exporter|miha.cancula@gmail.com|Miha Čančula}}
|}

 

= 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
{{FeatureTodo|JuK|Remove Qt/KDE3 support lib requirements|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Allow setting covers directly from URLs supported by KIO - drag/drop already allows this however|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Add MPRIS support to JuK so that the NowPlaying applet doesn't need to special-case JuK.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Update JuK's MusicBrainz support to a modern version of MusicBrainz.|mpyne@kde.org|Michael Pyne}}
{{FeatureInProgress|kmix|Improved volume OSD|fredrik@kde.org|Fredrik Höglund}}
|}

 

= 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|Import KGameRenderer framework and [[Projects/Games/Porting|port games]] to this unified rendering infrastructure.|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|Kigo|Fix KNewStuff provider issues|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureDone|Palapeli|Import Goldberg slicer as the new default slicer plugin.|loehnert.kde@gmx.de|Johannes Loehnert}}
{{FeatureDone|Palapeli|Update libpala API. Improve usability of "Create new puzzle" dialog.|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Kajongg|Docbook: Describe the basic game, until now I supposed the player already knows how to play Mah Jong.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Tiles can be discarded with drag&drop.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make robot player AI more intelligent.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make tiles in the hand larger and the wall tiles smaller for better playability on small screens.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make games suspendable/resumable.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Animate moving tiles.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Demo mode.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Introduce an option to only offer possible actions.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureTodo|Kajongg|Add more rulesets like other Classical Chinese variants and the international tournament rules.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|KGoldrunner|Save and restore the current control-mode, keyboard-control option and game-speed settings.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KGoldrunner|Add a keyboard-mode option to start moving when a direction-key is pressed and stop when it is released. Support multiple keys being pressed.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|Klickety|An adaptation of the "clickomania" game.Rewrite the kde3 version.|shuizhuyuanluo@126.com|Ni Hui}}
{{FeatureDone|Klickety|Merge KSame into Klickety.|shuizhuyuanluo@126.com|Ni Hui}}
{{FeatureInProgress|Kolf|Port to KGameRenderer, cleanup all QGraphicsView- and physics-related code (and physics engine), incorporate ideas from Kolf-NG.|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|Granatier|Port to KGameRenderer.|k.hias@gmx.de|Mathias Kraus}}
{{FeatureInProgress|Granatier|Use TagaroAudio for sound.|k.hias@gmx.de|Mathias Kraus}}
{{FeatureDone|Knights|New game: Chess board for KDE4|miha.cancula@gmail.com|Miha Čančula}}
|}

 

= 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
{{FeatureTodo|gwenview|Simplify photo sharing|agateau@kde.org|Aurélien Gâteau}}
|}

 

= 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|Lokalize|Integrate snowball stemmer for glossary|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Continue implementing XLIFF spec|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Segmentation [editing] functionality|shafff@NOSPAMukr.net |Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Remote translation memories|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate with nepomuk (fast stats retrieval, tag cloud - incl sharing!)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|loading compressed files and then saving them back in the original compression format (bug 65518)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Nepomukshell|New Nepomukshell development tool allowing to browse and debug Nepomuk data|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Dolphin|Git plugin|sebastian@sebastian-doerner.de|Sebastian Doerner}}
{{FeatureDone|Kate|GDB plugin|kare.sars@iki.fi|Kåre Särs}}
|}

 

= 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
{{FeatureTodo|Ark|Add a "Preview with..." context menu item|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Add an options dialog (maybe)|haraldhv@stud.ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Add feedback for the latest operation in the status bar|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Get rid of the Observer code in Kerfuffle|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make error reporting work as expected in Kerfuffle|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make Kerfuffle really thread-safe (and use threads in less places)|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make the internal previewer optional|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Simplify Kerfuffle's API (jobs, interfaces etc) and try to make it stable|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Support for custom options from the compression interface (eg. a slider for selecting compression level for rar files)|haraldhv@stud.ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Try multiple plugins for each archive type before failing|kubito@gmail.com|Raphael Kubo da Costa}}
{{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|printer-applet|Restore feature parity with KDEPrint3 where possible.||Jonathon Riddell, John Layt}}
{{FeatureTodo|Okteta|Add view profiles|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|KGpg|Better workflow to edit encrypted files|kde@opensource.sf-tec.de|Rolf Eike Beer}}
|}

 

= 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|Kontact|Plasma-based Summary Page|ry@n.rix.si|Ryan Rix}}
{{FeatureInProgress|KHolidays|Add support for holiday types and day-off types.|john@layt.net|John Layt}}
{{FeatureInProgress|KHolidays|Holiday Region selection widget.|john@layt.net|John Layt}}
{{FeatureDone|KHolidays|Holiday duration api.|john@layt.net|John Layt}}
{{FeatureDone|KHolidays|Default Holiday Region api.|john@layt.net|John Layt}}
{{FeatureInProgress|KAlarm|Port to Akonadi|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Option to not notify execution errors for pre-alarm actions|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|KAlarm|Allow reminders after the main alarm|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|KAlarm|Provide wake-from-suspend option for alarms|djarvie@kde.org|David Jarvie}}
|}
 

= kdeaccessibility =

{| 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|KAccessible|Added a dbus-service and a QAccessibleBridgePlugin for focus tracking (used in KMagnifier and the KWin zoom plugin).|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KMagnifier|Follow Focus Mode for Focus Tracking (uses kaccessible).|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KAccessible|Added Screenreader (uses speech-dispatcher)|mail@dipe.org|Sebastian Sauer}}
|}

 
= kdeartwork =

{| 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|KDE Asciiquarium|Added a new ASCII sprite (a submarine). Contributed by Ryan Meldrum.|mpyne@kde.org.|Michael Pyne}}
|}

 
= 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|Shelf|Automatic sizing of the popup|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Setting a custom popup icon|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|Shelf|Cascading popup menus for folders|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Keyboard navigation|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Search completion|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|libLancelot-datamodels|Akonadi integration|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|libLancelot-datamodels|Folder contents sorting|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|Lancelot|Theme improvements, animations|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|Events Runner|Event search|alexey.noskov@gmail.com|Alexey Noskov}}
{{FeatureTodo|Comic plasmoid|Per comic max cache limit|mat69@gmx.net|Matthias Fuchs}}
{{FeatureTodo|Comic plasmoid|Change behaviour when comic can't be found|mat69@gmx.net|Matthias Fuchs}}
|}

 

= 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|krfb|Refactor Core to make it more maintainable/extensible|grundleborg@googlemail.com.|George Goldberg}}
{{FeatureInProgress|krfb|Telepathy Tubes support|grundleborg@googlemail.com.|George Goldberg}}
{{FeatureInProgress|krfb|UI Improvements to support new features/deal with some existing bug reports|grundleborg@googlemail.com.|George Goldberg}}
{{FeatureTodo|kget|Log for transfers|l.appelhans@gmx.de|Lukas Appelhans}}
|}

Schedules/KDE4/4.6 Feature Plan

2010-11-02T09:40:56Z

Wrohdewald: update Kajongg status

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

See also:

*[[Schedules/KDE4/4.6 Release Schedule]]
*[[Schedules/KDE4/4.6 Release Goals]]
*[[Schedules/KDE4/4.5 Feature Plan]] (previous major release)

 Legend:

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

__TOC__

 

= kdebase-apps =

{| 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|Konsole|Move to KTabWidget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Dolphin|Faceted browsing via Nepomuk|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Dolphin|Searching support for non-indexed files|peter.penz19@gmail.com|Peter Penz}}
{{FeatureInProgress|Dolphin|Git-plugin (implemented by Sebastian Dörner and Johannes Steffen)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin| Resizeable columns in the column-view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin| Allow leading zeros when renaming multiple files (implemented by Matthias Fuchs)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureInProgress|nspluginviewer|Full npruntime support|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|Dolphin|Smooth scrolling|fredrik@kde.org|Fredrikh Höglund}}
|}

 

= kdebase-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|Plasma|Plasma KPart|ry@n.rix.si|Ryan Rix}}
{{FeatureInProgress|Plasma|Declarative AppletScript to write QML plasmoids|mart@kde.org|Marco Martin}}
{{FeatureInProgress|Plasma|Optimize the Newspaper containment for the use with touchscreens and the Plasma KPart|mart@kde.org|Marco Martin}}
{{FeatureDone|KWin|Focus tracking for the zoom plugin (uses kaccessible)|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KWin|Extend mouse tracking modes for the zoom plugin|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Nepomuk Backup & Sync| Provide Backup and Sync capabilities to Nepomuk|handa.vish@gmail.com|Vishesh Handa}}
{{FeatureTodo|Web Metadata extractor| Provide a framework to get additional data about resources|handa.vish@gmail.com|Vishesh Handa}}
{{FeatureDone|Activities manager service|Merge the kded and nepomuk modules for activities into one service|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|Activities manager service|Register desktop events instead directly linking the activities to resources|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|KNotify|Add support for relative present actions in contexts|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|KNotify|Add Plugin Loading Support|j.maceachern@gmail.com|Jeffery MacEachern}}
{{FeatureInProgress|Locale KCM|Complete re-write to improve usability, support for new localization features|john@layt.net|John Layt}}
{{FeatureInProgress|Phonon KCM|Add video input device configuration support|kiagiadakis.george@gmail.com|George Kiagiadakis}}
{{FeatureInProgress|ksecretserviced|Make it replace KWallet|lemma@confuego.org|Michael Leupold}}
|}

 

= kdebase-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
|-
! style="text-align: center;" colspan="4" | Plasma
{{FeatureInProgress|libtaskmanager / tasks-applet| support for Windows 7 like launchers |akreuzkamp@web.de|Anton Kreuzkamp}}
{{FeatureInProgress|notifications| rework notification applet appearance |mart@kde.org|Marco Martin}}
{{FeatureInProgress|notifications| make various dataengines use Plasma::Storage |mart@kde.org|Marco Martin}}
{{FeatureDone|plasma-desktop| UI for editing activity name and icon|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|plasma-desktop| add some default activities|fux@kde.org|Mario Fux}}
{{FeatureDone|plasma| finish support for activity templates |chani@kde.org|Chani}}
{{FeatureInProgress|plasma-devicenotifier| Improve notification support |wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureTodo|plasma-devicenotifier| Signal to the user which apps are blocking a device|wilderkde@gmail.com |Jacopo De Simoi}}
{{FeatureDone|quicklaunch| populate new applets with user's default browser, file manager, ... instead of hardcoded ones |ingomar@wesp.name|Ingomar Wesp}}
{{FeatureDone|quicklaunch| allow editing of existing launchers (including ones that do not point to a .desktop file) |ingomar@wesp.name|Ingomar Wesp}}
{{FeatureInProgress|quicklaunch| better layout for desktop and media center form factors |ingomar@wesp.name|Ingomar Wesp}}
{{FeatureInProgress|libplasma|Improvements to Calendar/Clock widgets. Improved config ui. Allow multiple holidays on same day. Allow multiple Holiday Regions. Weekends. etc.|john@layt.net|John Layt}}
{{FeatureInProgress|libplasma|Make Calendar DataEngine a Service.|john@layt.net|John Layt}}
{{FeatureTodo|plasma-desktop| integrate activity-sessions|chani@kde.org|Ivan/Chani}}
{{FeatureInProgress|plasma-desktop|activity dataengine|chani@kde.org|Chani}}
|-
! style="text-align: center;" colspan="4" | KWin
{{FeatureInProgress|windowgeometry effect| compositor powered move/resize windowgeometry display |thomas.luebking@web.de|Thomas Lübking}}
{{FeatureInProgress|dashboard effect| new effect for Plasma dashboard |ademmer@opensuse.org|Andreas Demmer}}
{{FeatureDone|kwin/ksmserver| activity sessions |chanika@gmail.com|Chani}}
{{FeatureTodo|libtaskmanager/kwin?| combine the three window-contextmenu codebases into one |chani@kde.org|Chani}}
{{FeatureTodo|libtaskmanager/kwin] | Expose Window Tabs to taskmanager |kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|kwin|ARB Shader support|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|Aurorae|Tooltips on window tabs|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Present Windows|Close window GUI control|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Startup Feedback|Effect to replace the Startup Feedback notification|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Screenshot Effect|KSanpshot can use KWin for screenshots|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KCM Compositing|Allow compositing even if GL is buggy/X crashes|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin Killer|Use notification instead of dialog|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|Compositing|Improved platform detection|fredrik@kde.org|Fredrik Höglund}}

|-
! style="text-align: center;" colspan="4" | KDE Power Management system
{{FeatureDone|core| PowerDevil v2 core |drf@kde.org|Dario Freddi}}
{{FeatureDone|actions| Basic actions for feature parity with PowerDevil v1 |drf@kde.org|Dario Freddi}}
{{FeatureInProgress|actions| More actions for advanced users |drf@kde.org|Dario Freddi}}
{{FeatureInProgress|policy-handler| Create a new policy handler for handling inhibition properly, and have kdelibs' Solid API use it |drf@kde.org|Dario Freddi}}
|-
! style="text-align: center;" colspan="4" | System Settings
{{FeatureInProgress|keyboard| Support for sticky layout switching |arysin@gmail.com|Andriy Rysin}}
{{FeatureInProgress|keyboard| Support for > 4 layouts|arysin@gmail.com|Andriy Rysin}}
{{FeatureInProgress|driconf|New module for configuring DRI drivers|fredrik@kde.org|Fredrik Höglund}}
|-
! style="text-align: center;" colspan="4" | Blue Devil
{{FeatureInProgress|Review| Get into kdebase|alex@eyeos.org|Alex Fiestas}}
{{FeatureInProgress|kio_obexftp| Better error handling|alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|usability|Review all the components improving hig/elegance|alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|share folders|Be able to share folders via obexftp|alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|Devices KCM|Add further information about devices, like address...|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|Devices KCM|Allow to connect to devices services|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|libbluedevil|Review DBus handling|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|libbluedevil|Add support for services|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|Monolithic|Fix listing problems under certain conditions|ereslibre@kde.org|Rafael Fernández López}}
|}

 

= 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|libnepomuk|Convenience operator overloads for query construction|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|libnepomuk|New query flags and improved handling of full text matching scores including sorting|trueg@kde.org|Sebastian Trueg}}
{{FeatureTodo|kdeui|Generic find bar widget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureDone|kdeui|Allow getting and setting the size of the pixmap cache in KImageCache|2kmm@gmx.de|Manuel Mommertz}}
{{FeatureDone|katepart|scripted actions|dhaumann@kde.org|Dominik Haumann}}
{{FeatureDone|katepart|QAccessibleInterface's for document+cursor|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|libplasma|PluginLoader class|ry@n.rix.si|Ryan Rix}}
{{FeatureDone|libplasma|Allow SVGs to use systemcolors before rendering|2kmm@gmx.de|Manuel Mommertz}}
{{FeatureInProgress|libplasma|DeclarativeWidget to load QML scenes in Plasma|mart@kde.org|Marco Martin}}
{{FeatureInProgress|libplasma|finish up the gsoc project about Plasma::Storage service|mart@kde.org|Marco Martin}}
{{FeatureDone|libplasma|let Plasma::SVG find the best matching size hinted element if there is no exact match|ingomar@wesp.name|Ingomar Wesp (mentored by Manuel Mommertz)}}
{{FeatureInProgress|libnepomuk/KIO|Search excerpts|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuk|Standardqueries for convenience|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuk|GUI elements for resource/file searching including faceted browsing|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuksync|Sync library to be used in BackupSync, Strigi, Akonadi, WebExtractor and Removable Media|handa.vish@gmail.com|Vishesh Handa}}
{{FeatureInProgress|kdecore|Add more possible synchronization primitives to KSharedDataCache to expand OS support. POSIX Semaphores Contributed by Alberto Villa of the FreeBSD project. Windows support may still occur as well.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdecore|Add fallback to QCache<QString,QByteArray> in KSharedDataCache.|mpyne@kde.org|Michael Pyne}}
{{FeatureDone|kdecore|Add cache-wide timestamp to KSharedDataCache.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdecore|Add ability to make KSharedDataCache strictly read-only for laptop support.|mpyne@kde.org|Michael Pyne}}
{{FeatureInProgress|kdeui|Social About Dialog|teo@kde.org|Teo Mrnjavac}}
{{FeatureInProgress|kdeui|Allow to hide icons in menus|christoph@maxiom.de|Christoph Feck}}
{{FeatureTodo|KCalendarSystem||john@layt.net|John Layt}}
{{FeatureTodo|KCalendarSystem|Add astronomical calculation support classes and astronomical based calendars.|john@layt.net|John Layt}}
{{FeatureDone|KCalendarSystem|Add api for first/last day of year/month.|john@layt.net|John Layt}}
{{FeatureInProgress|KDate|New convenience class to make date localization easy.|john@layt.net|John Layt}}
{{FeatureDone|KLocale|Add configuration for AM/PM symbols.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Add default colour to optionally display negative numbers.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Add more date formats.|john@layt.net|John Layt}}
{{FeatureInProgress|KLocale|Full POSIX compliant format support for date, time, numbers and money, including but not limited to: traditional/US week numbers, AM/PM symbols, number grouping|john@layt.net|John Layt}}
{{FeatureInProgress|KLocale|Implement separate backends for each supported platform/desktop to use platform localization in place of KDE locale.|john@layt.net|John Layt}}
{{FeatureInProgress|KLocale|Implement support for Country Code sub-regions and other country code standard conversions.|john@layt.net|John Layt}}
{{FeatureInProgress|KHTML|HTML5 postMessage.|maksim@kde.org|Maksim Orlovich}}
{{FeatureTodo|kcookiejar|New domain specific cookie policy based on patch provided in bug#54300|adawit@kde.org|Dawit A.}}
{{FeatureInProgress|kcookiejar|Implement storing cookies in KWallet|fid@gpul.org|José Millán Soto}}
{{FeatureInProgress|ksecretservice|Make KWallet::Wallet use the secrets-service API|lemma@confuego.org|Michael Leupold}}
{{FeatureInProgress|anywhere|Allow to build without deprecated symbols|ervin@kde.org|Kevin Ottens (with lots of support from David Faure)}}
{{FeatureInProgress|KIO|Use `net usershare` in KSambaShare|rclbelem@gmail.com|Rodrigo Belem}}
|}

 

= 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|Import of routes in .gpx and .kml format|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Route printing (map and directions, configurabe)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Route state saving and restoring|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Convert MarbleRunners to plugins|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|worldwide and offline routing|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Extend MarbleRunner interface to handle reverse geocoding and routing requests; Display of alternative routes|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Routing API|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|"Go To" dialog for Maemo|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureTodo|Marble|QtDeclarative plugin (possibly rather in 4.7)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Implement sun locator blendings as derived classes of Marble::Blending|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|Marble|Separate thread for tile loading and texture blending (not texture mapping at the moment) for more smooth browsing|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|Marble|Tile loading "read ahead" when idle, prerequisite: threaded tile loading|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureDone|Marble|Tile download along the route for offline usage|akssps011@gmail.com|Siddharth Srivastava}}
{{FeatureInProgress|Marble|Turn-by-turn navigation mode|akssps011@gmail.com|Siddharth Srivastava}}
{{FeatureTodo|Marble|Multi threaded texture mapping|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureDone|Marble|Improve GeoData API|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Convert Gps tracking to GeoDataDocument|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Provide a treeModel for GeoDataDocuments|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Draw the geometries of multiple GeoDataDocuments|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Marble|Load Pnt vector data files as GeoData|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Marble|Manipulate Gps track data|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Cantor|Backend for GNU Octave|miha.cancula@gmail.com|Miha Čančula}}
{{FeatureInProgress|Cantor|Merge R improvement branch|alexanderrieder@gmail.com|Alexander Rieder}}
{{FeatureInProgress|Cantor|Variable management panel|alexanderrieder@gmail.com|Alexander Rieder}}
{{FeatureTodo|Cantor|Formulas inside Text Entries|alexanderrieder@gmail.com| Alexander Rieder}}
{{FeatureDone|Kalzium|Port Kalzium to use QGV based periodic table widget|mhanwell@kde.org|Marcus D. Hanwell}}
{{FeatureDone|KAlgebra|Implicit functions plot|percy.camilo.ta@gmail.com|Percy Aucahuasi}}
{{FeatureDone|KAlgebra|Improved execution speed on the calculator|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra|Better integration between the Console and the Plotting facilities|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra|Lighter version aimed to mobile users|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureInProgress|KStars|OpenGL rendering support for KStars|akarshsimha@gmail.com|Harry de Valence, Akarsh Simha}}
{{FeatureInProgress|KStars|Better designed object database|akarshsimha@gmail.com|Victor Carbune, Akarsh Simha}}
{{FeatureInProgress|KStars|Star Hop Generator|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureDone|Kig|LaTeX/TikZ exporter|miha.cancula@gmail.com|Miha Čančula}}
|}

 

= 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
{{FeatureTodo|JuK|Remove Qt/KDE3 support lib requirements|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Allow setting covers directly from URLs supported by KIO - drag/drop already allows this however|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Add MPRIS support to JuK so that the NowPlaying applet doesn't need to special-case JuK.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Update JuK's MusicBrainz support to a modern version of MusicBrainz.|mpyne@kde.org|Michael Pyne}}
{{FeatureInProgress|kmix|Improved volume OSD|fredrik@kde.org|Fredrik Höglund}}
|}

 

= 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|Import KGameRenderer framework and [[Projects/Games/Porting|port games]] to this unified rendering infrastructure.|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|Kigo|Fix KNewStuff provider issues|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureDone|Palapeli|Import Goldberg slicer as the new default slicer plugin.|loehnert.kde@gmx.de|Johannes Loehnert}}
{{FeatureDone|Palapeli|Update libpala API. Improve usability of "Create new puzzle" dialog.|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Kajongg|Docbook: Describe the basic game, until now I supposed the player already knows how to play Mah Jong.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Tiles can be discarded with drag&drop.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make robot player AI more intelligent.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make tiles in the hand larger and the wall tiles smaller for better playability on small screens.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make games suspendable/resumable.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Animate moving tiles.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureInProgress|Kajongg|Demo mode.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Introduce an option to only offer possible actions.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureTodo|Kajongg|Add more rulesets like other Classical Chinese variants and the international tournament rules.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|KGoldrunner|Save and restore the current control-mode, keyboard-control option and game-speed settings.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KGoldrunner|Add a keyboard-mode option to start moving when a direction-key is pressed and stop when it is released. Support multiple keys being pressed.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|Klickety|An adaptation of the "clickomania" game.Rewrite the kde3 version.|shuizhuyuanluo@126.com|Ni Hui}}
{{FeatureInProgress|Klickety|IMerge KSame into Klickety.|shuizhuyuanluo@126.com|Ni Hui}}
{{FeatureInProgress|Kolf|Port to KGameRenderer, cleanup all QGraphicsView- and physics-related code (and physics engine), incorporate ideas from Kolf-NG.|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|Granatier|Port to KGameRenderer.|k.hias@gmx.de|Mathias Kraus}}
{{FeatureInProgress|Granatier|Use TagaroAudio for sound.|k.hias@gmx.de|Mathias Kraus}}
{{FeatureDone|Knights|New game: Chess board for KDE4|miha.cancula@gmail.com|Miha Čančula}}
|}

 

= 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
{{FeatureTodo|gwenview|Simplify photo sharing|agateau@kde.org|Aurélien Gâteau}}
|}

 

= 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|Lokalize|Integrate snowball stemmer for glossary|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Continue implementing XLIFF spec|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Segmentation [editing] functionality|shafff@NOSPAMukr.net |Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Remote translation memories|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate with nepomuk (fast stats retrieval, tag cloud - incl sharing!)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|loading compressed files and then saving them back in the original compression format (bug 65518)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Nepomukshell|New Nepomukshell development tool allowing to browse and debug Nepomuk data|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Dolphin|Git plugin|sebastian@sebastian-doerner.de|Sebastian Doerner}}
{{FeatureDone|Kate|GDB plugin|kare.sars@iki.fi|Kåre Särs}}
|}

 

= 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
{{FeatureTodo|Ark|Add a "Preview with..." context menu item|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Add an options dialog (maybe)|haraldhv@stud.ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Add feedback for the latest operation in the status bar|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Get rid of the Observer code in Kerfuffle|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make error reporting work as expected in Kerfuffle|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make Kerfuffle really thread-safe (and use threads in less places)|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make the internal previewer optional|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Simplify Kerfuffle's API (jobs, interfaces etc) and try to make it stable|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Support for custom options from the compression interface (eg. a slider for selecting compression level for rar files)|haraldhv@stud.ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Try multiple plugins for each archive type before failing|kubito@gmail.com|Raphael Kubo da Costa}}
{{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|printer-applet|Restore feature parity with KDEPrint3 where possible.||Jonathon Riddell, John Layt}}
{{FeatureTodo|Okteta|Add view profiles|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|KGpg|Better workflow to edit encrypted files|kde@opensource.sf-tec.de|Rolf Eike Beer}}
|}

 

= 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|Kontact|Plasma-based Summary Page|ry@n.rix.si|Ryan Rix}}
{{FeatureInProgress|KHolidays|Add support for holiday types and day-off types.|john@layt.net|John Layt}}
{{FeatureInProgress|KHolidays|Holiday Region selection widget.|john@layt.net|John Layt}}
{{FeatureDone|KHolidays|Holiday duration api.|john@layt.net|John Layt}}
{{FeatureDone|KHolidays|Default Holiday Region api.|john@layt.net|John Layt}}
{{FeatureInProgress|KAlarm|Port to Akonadi|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Option to not notify execution errors for pre-alarm actions|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|KAlarm|Allow reminders after the main alarm|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|KAlarm|Provide wake-from-suspend option for alarms|djarvie@kde.org|David Jarvie}}
|}
 

= kdeaccessibility =

{| 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|KAccessible|Added a dbus-service and a QAccessibleBridgePlugin for focus tracking (used in KMagnifier and the KWin zoom plugin).|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KMagnifier|Follow Focus Mode for Focus Tracking (uses kaccessible).|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KAccessible|Added Screenreader (uses speech-dispatcher)|mail@dipe.org|Sebastian Sauer}}
|}

 
= kdeartwork =

{| 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|KDE Asciiquarium|Added a new ASCII sprite (a submarine). Contributed by Ryan Meldrum.|mpyne@kde.org.|Michael Pyne}}
|}

 
= 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|Shelf|Automatic sizing of the popup|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Setting a custom popup icon|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|Shelf|Cascading popup menus for folders|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Keyboard navigation|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Search completion|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|libLancelot-datamodels|Akonadi integration|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|libLancelot-datamodels|Folder contents sorting|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|Lancelot|Theme improvements, animations|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|Events Runner|Event search|alexey.noskov@gmail.com|Alexey Noskov}}
{{FeatureTodo|Comic plasmoid|Per comic max cache limit|mat69@gmx.net|Matthias Fuchs}}
{{FeatureTodo|Comic plasmoid|Change behaviour when comic can't be found|mat69@gmx.net|Matthias Fuchs}}
|}

 

= 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|krfb|Refactor Core to make it more maintainable/extensible|grundleborg@googlemail.com.|George Goldberg}}
{{FeatureInProgress|krfb|Telepathy Tubes support|grundleborg@googlemail.com.|George Goldberg}}
{{FeatureInProgress|krfb|UI Improvements to support new features/deal with some existing bug reports|grundleborg@googlemail.com.|George Goldberg}}
{{FeatureTodo|kget|Log for transfers|l.appelhans@gmx.de|Lukas Appelhans}}
|}

Schedules/KDE4/4.6 Feature Plan

2010-10-24T20:37:02Z

Wrohdewald: update Todos for Kajongg

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

See also:

*[[Schedules/KDE4/4.6 Release Schedule]]
*[[Schedules/KDE4/4.6 Release Goals]]
*[[Schedules/KDE4/4.5 Feature Plan]] (previous major release)

 Legend:

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

__TOC__

 

= kdebase-apps =

{| 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|Konsole|Move to KTabWidget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Dolphin|Faceted browsing via Nepomuk|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Dolphin|Searching support for non-indexed files|peter.penz19@gmail.com|Peter Penz}}
{{FeatureInProgress|Dolphin|Git-plugin (implemented by Sebastian Dörner and Johannes Steffen)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin| Resizeable columns in the column-view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin| Allow leading zeros when renaming multiple files (implemented by Matthias Fuchs)|peter.penz19@gmail.com|Peter Penz}}
|}

 

= kdebase-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|Plasma|Plasma KPart|ry@n.rix.si|Ryan Rix}}
{{FeatureInProgress|Plasma|Declarative AppletScript to write QML plasmoids|mart@kde.org|Marco Martin}}
{{FeatureInProgress|Plasma|Optimize the Newspaper containment for the use with touchscreens and the Plasma KPart|mart@kde.org|Marco Martin}}
{{FeatureDone|KWin|Focus tracking for the zoom plugin (uses kaccessible)|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KWin|Extend mouse tracking modes for the zoom plugin|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Nepomuk Backup & Sync| Provide Backup and Sync capabilities to Nepomuk|handa.vish@gmail.com|Vishesh Handa}}
{{FeatureInProgress|Activities manager service|Merge the kded and nepomuk modules for activities into one service|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|Activities manager service|Register desktop events instead directly linking the activities to resources|ivan.cukic@kde.org|Ivan Čukić}}
|}

|}

 

= kdebase-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
|-
! style="text-align: center;" colspan="4" | Plasma
{{FeatureInProgress|libtaskmanager / tasks-applet| support for Windows 7 like launchers |akreuzkamp@web.de|Anton Kreuzkamp}}
{{FeatureInProgress|notifications| rework notification applet appearance |mart@kde.org|Marco Martin}}
{{FeatureInProgress|notifications| make various dataengines use Plasma::Storage |mart@kde.org|Marco Martin}}
{{FeatureDone|plasma-desktop| UI for editing activity name and icon|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|plasma-desktop| add some default activities|fux@kde.org|Mario Fux}}
{{FeatureTodo|plasma| finish support for activity templates | |??}}
|-
! style="text-align: center;" colspan="4" | KWin
{{FeatureInProgress|windowgeometry effect| compositor powered move/resize windowgeometry display |thomas.luebking@web.de|Thomas Lübking}}
{{FeatureInProgress|dashboard effect| new effect for Plasma dashboard |ademmer@opensuse.org|Andreas Demmer}}
{{FeatureInProgress|kwin/ksmserver| activity sessions |chanika@gmail.com|Chani}}
{{FeatureTodo|libtaskmanager/kwin?| combine the three window-contextmenu codebases into one | |??}}
|}

 

= 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|libnepomuk|Convenience operator overloads for query construction|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|libnepomuk|New query flags and improved handling of full text matching scores including sorting|trueg@kde.org|Sebastian Trueg}}
{{FeatureTodo|kdeui|Generic find bar widget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureDone|kdeui|Allow getting and setting the size of the pixmap cache in KImageCache|2kmm@gmx.de|Manuel Mommertz}}
{{FeatureDone|katepart|scripted actions|dhaumann@kde.org|Dominik Haumann}}
{{FeatureDone|katepart|QAccessibleInterface's for document+cursor|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|libplasma|PluginLoader class|ry@n.rix.si|Ryan Rix}}
{{FeatureDone|libplasma|Allow SVGs to use systemcolors before rendering|2kmm@gmx.de|Manuel Mommertz}}
{{FeatureInProgress|libplasma|DeclarativeWidget to load QML scenes in Plasma|mart@kde.org|Marco Martin}}
{{FeatureInProgress|libplasma|finish up the gsoc project about Plasma::Storage service|mart@kde.org|Marco Martin}}
{{FeatureInProgress|libnepomuk/KIO|Search excerpts|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuk|Standardqueries for convenience|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuk|GUI elements for resource/file searching including faceted browsing|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuksync|Sync library to be used in BackupSync, Strigi, Akonadi, WebExtractor and Removable Media|handa.vish@gmail.com|Vishesh Handa}}
{{FeatureInProgress|kdecore|Add more possible synchronization primitives to KSharedDataCache to expand OS support. POSIX Semaphores Contributed by Alberto Villa of the FreeBSD project. Windows support may still occur as well.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdecore|Add fallback to QCache<QString,QByteArray> in KSharedDataCache.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdecore|Add cache-wide timestamp to KSharedDataCache.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdecore|Add ability to make KSharedDataCache strictly read-only for laptop support.|mpyne@kde.org|Michael Pyne}}
{{FeatureInProgress|kdeui|Social About Dialog|teo@kde.org|Teo Mrnjavac}}
|}

 

= 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|GPX import of routes|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Route printing (map and directions, configurabe)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Route state saving and restoring|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Convert MarbleRunners to plugins|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|worldwide and offline routing|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Extend MarbleRunner interface to handle reverse geocoding and routing requests; Display of alternative routes|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Routing API|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Implement sun locator blendings as derived classes of Marble::Blending|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|Marble|Separate thread for tile loading and texture blending (not texture mapping at the moment) for more smooth browsing|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|Marble|Tile loading "read ahead" when idle, prerequisite: threaded tile loading|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureDone|Marble|Tile download along the route for offline usage|akssps011@gmail.com|Siddharth Srivastavah}}
{{FeatureInProgress|Marble|Turn-by-turn navigation mode|akssps011@gmail.com|Siddharth Srivastavah}}
{{FeatureTodo|Marble|Multi threaded texture mapping|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureDone|Marble|Improve GeoData API|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Convert Gps tracking to GeoDataDocument|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Provide a treeModel for GeoDataDocuments|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Draw the geometries of multiple GeoDataDocuments|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Marble|Load Pnt vector data files as GeoData|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Marble|Manipulate Gps track data|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Cantor|Backend for GNU Octave|miha.cancula@gmail.com|Miha Čančula}}
{{FeatureTodo|Cantor|Merge R improvement branch|alexanderrieder@gmail.com|Alexander Rieder}}
{{FeatureTodo|Cantor|Variable management panel|alexanderrieder@gmail.com|Alexander Rieder}}
{{FeatureDone|Kalzium|Port Kalzium to use QGV based periodic table widget|mhanwell@kde.org|Marcus D. Hanwell}}
{{FeatureDone|KAlgebra|Implicit functions plot|percy.camilo.ta@gmail.com|Percy Aucahuasi}}
{{FeatureDone|KAlgebra|Improved execution speed on the calculator|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra|Better integration between the Console and the Plotting facilities|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureInProgress|KStars|OpenGL rendering support for KStars|akarshsimha@gmail.com|Harry de Valence, Akarsh Simha}}
{{FeatureInProgress|KStars|Better designed object database|akarshsimha@gmail.com|Victor Carbune, Akarsh Simha}}
{{FeatureInProgress|KStars|Star Hop Generator|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureDone|Kig|LaTeX/TikZ exporter|miha.cancula@gmail.com|Miha Čančula}}
|}

 

= 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
{{FeatureTodo|JuK|Remove Qt/KDE3 support lib requirements|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Allow setting covers directly from URLs supported by KIO - drag/drop already allows this however|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Add MPRIS support to JuK so that the NowPlaying applet doesn't need to special-case JuK.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Update JuK's MusicBrainz support to a modern version of MusicBrainz.|mpyne@kde.org|Michael Pyne}}

|}

 

= 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|Import KGameRenderer framework and [[Projects/Games/Porting|port games]] to this unified rendering infrastructure.|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|Kigo|Fix KNewStuff provider issues|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureDone|Palapeli|Import Goldberg slicer as the new default slicer plugin.|loehnert.kde@gmx.de|Johannes Loehnert}}
{{FeatureDone|Palapeli|Update libpala API. Improve usability of "Create new puzzle" dialog.|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Kajongg|Docbook: Describe the basic game, until now I supposed the player already knows how to play Mah Jong.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Tiles can be discarded with drag&drop.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make robot player AI more intelligent.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make tiles in the hand larger and the wall tiles smaller for better playability on small screens.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make games suspendable/resumable.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureInProgress|Kajongg|Animate moving tiles.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureInProgress|Kajongg|Demo mode.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureTodo|Kajongg|Introduce an option to only offer possible actions.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureTodo|Kajongg|Add more rulesets like other Classical Chinese variants and the international tournament rules.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|KGoldrunner|Save and restore the current control-mode, keyboard-control option and game-speed settings.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KGoldrunner|Add a keyboard-mode option to start moving when a direction-key is pressed and stop when it is released. Support multiple keys being pressed.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|Klickety|An adaptation of the "clickomania" game.Rewrite the kde3 version.|shuizhuyuanluo@126.com|Ni Hui}}
{{FeatureInProgress|Klickety|IMerge KSame into Klickety.|shuizhuyuanluo@126.com|Ni Hui}}
{{FeatureInProgress|Kolf|Port to KGameRenderer, cleanup all QGraphicsView- and physics-related code (and physics engine), incorporate ideas from Kolf-NG.|majewsky@gmx.net|Stefan Majewsky}}
|}

 

= 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|Lokalize|Integrate snowball stemmer for glossary|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Continue implementing XLIFF spec|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Segmentation [editing] functionality|shafff@NOSPAMukr.net |Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Remote translation memories|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate with nepomuk (fast stats retrieval, tag cloud - incl sharing!)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|loading compressed files and then saving them back in the original compression format (bug 65518)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Nepomukshell|New Nepomukshell development tool allowing to browse and debug Nepomuk data|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Dolphin|Git plugin|sebastian@sebastian-doerner.de|Sebastian Doerner}}
|}

 

= 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
{{FeatureTodo|Ark|Add a "Preview with..." context menu item|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Add an options dialog (maybe)|haraldhv@stud.ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Add feedback for the latest operation in the status bar|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Get rid of the Observer code in Kerfuffle|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make error reporting work as expected in Kerfuffle|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make Kerfuffle really thread-safe (and use threads in less places)|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make the internal previewer optional|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Simplify Kerfuffle's API (jobs, interfaces etc) and try to make it stable|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Support for custom options from the compression interface (eg. a slider for selecting compression level for rar files)|haraldhv@stud.ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Try multiple plugins for each archive type before failing|kubito@gmail.com|Raphael Kubo da Costa}}
{{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|printer-applet|Restore feature parity with KDEPrint3 where possible.||Jonathon Riddell, John Layt}}
{{FeatureTodo|Okteta|Add view profiles|kossebau@kde.org|Friedrich W. H. Kossebau}}
|}

 

= 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|Kontact|Plasma-based Summary Page|ry@n.rix.si|Ryan Rix}}
|}

 

= kdeaccessibility =

{| 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|KAccessible|Added a dbus-service and a QAccessibleBridgePlugin for focus tracking (used in KMagnifier and the KWin zoom plugin).|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KMagnifier|Follow Focus Mode for Focus Tracking (uses kaccessible).|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KAccessible|Added Screenreader (uses speech-dispatcher)|mail@dipe.org|Sebastian Sauer}}
|}

 
= kdeartwork =

{| 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|KDE Asciiquarium|Added a new ASCII sprite (a submarine). Contributed by Ryan Meldrum.|mpyne@kde.org.|Michael Pyne}}
|}

 
= 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|Shelf|Automatic sizing of the popup|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Setting a custom popup icon|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|Shelf|Cascading popup menus for folders|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Keyboard navigation|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Search completion|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|libLancelot-datamodels|Akonadi integration|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|libLancelot-datamodels|Folder contents sorting|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|Lancelot|Theme improvements, animations|ivan.cukic@kde.org|Ivan Čukić}}
|}

 
= 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|krfb|Refactor Core to make it more maintainable/extensible|grundleborg@googlemail.com.|George Goldberg}}
{{FeatureInProgress|krfb|Telepathy Tubes support|grundleborg@googlemail.com.|George Goldberg}}
{{FeatureInProgress|krfb|UI Improvements to support new features/deal with some existing bug reports|grundleborg@googlemail.com.|George Goldberg}}
|}

Schedules/KDE4/4.6 Feature Plan

2010-10-03T12:48:35Z

Wrohdewald: update Todos for Kajongg

Development/CMake/Python

2010-09-27T12:34:07Z

Wrohdewald: Adapt to comments by Jonathan Riddell

= How to integrate a Python project into the KDE4 cmake system =

This is work in progress - right now there seem to be very different views about how runtime dependencies for projects should be handled. This is much more of a problem for Python projects because almost all of their dependencies are runtime only.

Here are some links to discussions:

http://lists.kde.org/?l=kde-buildsystem&m=128267903722403&w=4
http://lists.kde.org/?l=kde-core-devel&m=126890156111852&w
http://lists.kde.org/?l=kde-buildsystem&m=128550824619920&w=4

== Build time dependencies ==

There is not much that needs to be compiled for a Python project:

* The byte-compiled *.pyc files if you choose to do that when building the package. A better way would be to do that at install time - that ensures the correct Python version is used. This is what Debian-based distros do. If you compile them at buid time, they should be generated for all project modules. However the main .py file (or files) like kajongg.py which are executed first should not be bytecompiled. The Python interpreter would not use that anyway, it always recompiles the main .py file when loading it. For shorter startups, make it as small as possible. See the example below. Since cmake bytecompiles all python source files at build time, this main file (like kajongg.py) should not be added to the list of source files. Instead simply install those main .py files directly in the right place.

* Maybe some *.ui files to be processed by pyuic4. If you only have few small *.ui files you may prefer to simply distribute the *.ui files and have them processed at runtime (I did not measure how much time that actually takes). This of course simplifies cmake configuration.<code>
from PyQt4 import uic
uic.loadUi('mywidget.ui')
</code>

So you need a Python interpreter installed for the generation of byte-compiled *.pyc files. Make sure it is a version that can also execute your program. If the version installed at the client side is too different, your precompiled bytecode is incompatible and cannot be used, so the client system will recompile your sources. And if it cannot write them because of missing access rights, it will do that at every program start (there are ways how to tell python where to write its local *.pyc files but that is out of scope for here).

And optionally you need pyuic4 installed. This macro calls pyuic4 and installs the resulting *ui.py files:<code>PYKDE4_ADD_UI_FILES(src/*.ui)</code>However I believe I had some problems with that macro, that may have been one reason why I now do that at runtime for Kajongg. This would need to be checked.

== Runtime dependencies ==
In C/C++ most runtime dependencies are also build time dependencies - the KDE4 cmake macros do not even let you differentiate them (yet). However Python source code can be bytecompiled without the imported modules being installed - so the set of build time dependencies is very small and about the same for all Python projects.

Most distribution packagers do '''NOT''' want cmake to error out on missing runtime dependencies, they do not even want warnings about them because they just might not want to install them. They want to have their build system as simple (and as fast) as possible with a minimal set of dependencies. However this is not true for all packagers, some do want warnings. Developers probably want warnings too but it should be a small burden for them to install what the program claims as missing.

Until an easy way is found to satisfy both use cases, it is probably best to only implement the least common denominator: Do not error out or produce warnings.

Of course packagers still need to know the runtime dependencies. For now there is no nice way of specifying this with existing cmake macros. Currently the best solution for you is to write runtime dependency information into a file README.packagers in the home of your project.

== Executables ==
In theory, the main.py (like kajongg.py in the example below) could directly be installed in whatever */bin directory but it is nicer to only put a symbolic link there like /usr/bin/kajongg -> /usr/share/kde4/apps/kajongg/kajongg.py.
Of course cmake comes with a macro for this:
<code>
PYKDE4_ADD_EXECUTABLE(kajongg.py kajongg)
</code>

== Example projects ==
*[http://websvn.kde.org/trunk/KDE/kdegames/kajongg/ Kajongg], a board game. This project is not yet conforming to the above text - I will convert it as soon as nobody objects to this.

Development/CMake/Python

2010-09-26T21:13:41Z

Wrohdewald: cmake and Python projects - initial version

= How to integrate a Python project into the KDE4 cmake system =

This is work in progress - right now there seem to be very different views about how runtime dependencies for projects should be handled. This is much more of a problem for Python projects because almost all of their dependencies are runtime only.

Here are some links to discussions:

http://lists.kde.org/?l=kde-buildsystem&m=128267903722403&w=4
http://lists.kde.org/?l=kde-core-devel&m=126890156111852&w
http://lists.kde.org/?l=kde-buildsystem&m=128550824619920&w=4

== Build time dependencies ==

There is not much that needs to be compiled for a Python project:

* Mainly the byte-compiled *.pyc files. They should be generated for all project modules. However the main .py file (or files) like kajongg.py which are executed first should not be bytecompiled. The Python interpreter would not use that anyway, it always recompiles the main .py file when loading it. For shorter startups, make it as small as possible. See the example below. Since cmake bytecompiles all python source files at build time, this main file (like kajongg.py) should not be added to the list of source files. Instead simply install those main .py files directly in the right place.

* And maybe some *.ui files to be processed by pyuic4. If you only have few small *.ui files you may prefer to simply distribute the *.ui files and have them processed at runtime (I did not measure how much time that actually takes). This of course simplifies cmake configuration.<code>
from PyQt4 import uic
uic.loadUi('mywidget.ui')
</code>

So you need a Python interpreter installed for the generation of byte-compiled *.pyc files. Make sure it is a version that can also execute your program. If the version installed at the client side is too different, your precompiled bytecode is incompatible and cannot be used, so the client system will recompile your sources. And if it cannot write them because of missing access rights, it will do that at every program start (there are ways how to tell python where to write its local *.pyc files but that is out of scope for here).

And optionally you need pyuic4 installed. This macro calls pyuic4 and installs the resulting *ui.py files:<code>PYKDE4_ADD_UI_FILES(src/*.ui)</code>However I believe I had some problems with that macro, that may have been one reason why I now do that at runtime for Kajongg. This would need to be checked.

== Runtime dependencies ==
In C/C++ most runtime dependencies are also build time dependencies - the KDE4 cmake macros do not even let you differentiate them (yet). However Python source code can be bytecompiled without the imported modules being installed - so the set of build time dependencies is very small and about the same for all Python projects.

Since cmake is mostly used by distribution packagers, you should respect their preferences. Developers do not need cmake for Python development at all.

Distribution packagers do '''NOT''' want cmake to error out on missing runtime dependencies, they do not even want warnings about them because they just might not want to install them. Packagers want to have their build system as simple (and as fast) as possible with a minimal set of dependencies. Of course they still need to know the runtime dependencies. For now there is no nice way of specifying this with existing cmake macros. Currently the best solution for you is to write runtime dependency information into a file README.packagers in the home of your project.

== Executables ==
In theory, the main.py (like kajongg.py in the example below) could directly be installed in whatever */bin directory but it is nicer to only put a symbolic link there like /usr/bin/kajongg -> /usr/share/kde4/apps/kajongg/kajongg.py.
Of course cmake comes with a macro for this:
<code>
PYKDE4_ADD_EXECUTABLE(kajongg.py kajongg)
</code>

== Example projects ==
*[http://websvn.kde.org/trunk/KDE/kdegames/kajongg/ Kajongg], a board game. This project is not yet conforming to the above text - I will convert it as soon as nobody objects to this.

Development/CMake

2010-09-26T20:00:29Z

Wrohdewald: add a new page for cmake with Python projects

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

This is the central directory of all [http://www.cmake.org CMake]-related pages on TechBase.

== KDE4 Specific CMake Documentation==

;[[Development/Tutorials/CMake|CMake tutorial]]
:''An introduction to using CMake for KDE4''

;[[Development/CMake_FAQ|KDE's CMake FAQ]]
:''Some Frequently Asked Questions''

;[http://api.kde.org/cmake/modules.html KDE CMake modules API]
:''Documentation for all CMake modules in kdelibs (generated from kdelibs svn)''

;[[Development/CMake/DashboardBuilds|Nightly dashboard builds for KDE]]
: ''Describes the quality dashboard for KDE and how to set up Nightly builds for it''

;[[Development/CMake/Addons for KDE|KDE4 CMake Buildtypes, macros and variables]]
:''Documentation for the buildtypes (debugfull, release, ...), macros and variables for building KDE4 software, provided by FindKDE4Internal.cmake (manually written)''

;[[Development/Tools/Automoc4|Automoc4]]
:''Automoc4 documentation.''

;[[Development/CMake/Python|CMake for Python projects]]
:''How to integrate a Python project into the KDE4 cmake system.''

==Policies==

;[[Policies/CMake_Commit_Policy|Commit Policy for kdelibs/cmake/modules/]]
:''The files in kdelibs/cmake/modules/ are part of the public interface of KDE, some special policies apply to committing there.''

;[[Policies/CMake_and_Source_Compatibility|Source compatiblity with CMake]]
:''This page discusses what has to be taken care of in order to stay source compatible on the CMake level.''

;[[Policies/CMake_Coding_Style|Coding style for CMake files]]
:''Some guidelines how to write CMake scripts in KDE.''

==Changelog for KDE's CMake buildsystem==

;[[Development/CMake_KDE_4_5 |Changes in the buildsystem with KDE 4.5]]
:''What has changed in KDE 4.5 compared to KDE 4.4''

;[[Development/CMake_KDE_4_4 |Changes in the buildsystem with KDE 4.4]]
:''What has changed in KDE 4.4 compared to KDE 4.3''

;[[Development/CMake_KDE_4_3 |Changes in the buildsystem with KDE 4.3]]
:''What has changed in KDE 4.3 compared to KDE 4.2''

;[[Development/CMake_KDE_4_2 |Changes in the buildsystem with KDE 4.2]]
:''What has changed in KDE 4.2 compared to KDE 4.0/4.1''

==More Places to learn about CMake==

Here are some good places to learn about CMake in general:
* [http://www.cmake.org/HTML/Documentation.html CMake Manual]
* [http://www.cmake.org/Wiki/CMake CMake Wiki]
* [http://www.cmake.org/Wiki/CMake_HowToDoPlatformChecks CMake System Checks ]
* [http://www.cmake.org/Wiki/CMake_HowToFindInstalledSoftware Finding Optional Packages ]
* [http://www.cmake.org/Wiki/HowToBuildKDE4Software KDE 4 Tutorial at the CMake Wiki ]
* [http://www.cmake.org/Wiki/CMake_FAQ CMake FAQ]
* [http://www.elpauer.org/stuff/learning_cmake.pdf Slides for the "Learning CMake" seminar]
* [http://mail.kde.org/pipermail/kde-buildsystem/ The kde-buildsystem Mailing List Archive]

Also, consider joining the [http://www.cmake.org/mailman/listinfo/cmake CMake mailing list].

Development/Languages/Python

2010-09-26T16:38:45Z

Wrohdewald: mention Kajongg in applications using PyKDE

{{Template:I18n/Language Navigation Bar|Development/Languages/Python}}

Python is a powerful object oriented, dynamic language. You can find out more about the language itself on the Python website at http://www.python.org/.

Two important pieces of software are needed to develop KDE applications using Python, [http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt] and PyKDE. PyQt provides Python support for the Qt library which KDE is built on. PyQt can be obtained at http://www.riverbankcomputing.co.uk/software/pyqt/ . Riverbank Computing has a lot of good documentation about how to use PyQt to create pure Qt applications. If you are new to KDE / Python development, then learning how to use PyQt is the best first step.

PyKDE builds on top of PyQt and adds Python support for KDE's libraries and technologies.

PyKDE is distributed as part of the kdebindings module. Stable releases can be downloaded from the normal [http://kde.org/download/ KDE download page], although it is usually easier to install pre-built packages from your operating system distribution. You can also obtain PyKDE from KDE's subversion repository:

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebindings/python/pykde4

The code in subversion can be browsed online via http://websvn.kde.org/trunk/KDE/kdebindings/python/pykde4/.

==Documentation and Tutorials==
* [http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt home page and documentation]
* [[/Using PyKDE 4|Using PyKDE 4]]
* [http://api.kde.org/pykde-4.3-api/toc.html PyKDE 4.3 Documentation]
* [http://api.kde.org/pykde-4.3-api/modules.html PyKDE 4.3 API class reference]
* [http://api.kde.org/pykde-4.2-api/ PyKDE 4.2 API class reference]
* [[/PyKDE_WebKit_Tutorial|PyKDE WebKit Tutorial]], a simple web browser application in PyKDE
* [[Development/Tutorials/Python introduction to signals and slots|introduction to signals and slots]]
* [[Development/Tutorials/Python-hello world|Hello world]]. An example that you can also use as a starting point for your development.
* [http://www.rkblog.rk.edu.pl/w/p/introduction-pyqt4/ Introduction article about PyQt4]
* [http://lateral.netmanagers.com.ar/stories/BBS47.html PyQt by Example]
* [[/PyKDE_DBus_Tutorial|Python DBus Tutorial]]. See how to call dbus methods from PyKDE.
* [[/PyKDE_Knotify_Tutorial|Python KNotify Tutorial]]. How to use Notification and Jobs in your Applications
* [[Development/Tutorials/Phonon/Introduction/Python|Phonon Example]]
* [[Development/Tutorials/Plasma#Plasma_Programming_with_Python|Plasma tutorials]]

===KDE 3 and PyKDE 3===
Documentation and tutorials for the older PyQt and PyKDE 3.
* [http://vizzzion.org/?id=pyqt Python-Qt tutorial] '' In this tutorial, the basic steps of creating a Qt-based application with PyQt are explained. ''

==Further reading and information==
*[http://www.riverbankcomputing.com/mailman/listinfo/pyqt PyQt and PyKDE mailing list]
*[http://www.riverbankcomputing.co.uk/software/pykde/intro PyKDE Homepage]
*[http://www.diotavelli.net/PyQtWiki The PyQt and PyKDE community Wiki]
*The book [http://www.qtrac.eu/pyqtbook.html Rapid GUI Programming with Python and Qt] is available and covers Qt 4 programming with Python.
*The IRC channel ''#kubuntu-devel'' on freenode often has PyKDE programmers in it.
*The IRC channel ''#pyqt'' on freenode is used by some PyQt application developers.

==Applications using PyKDE==
*[http://utils.kde.org/projects/printer-applet/ printer-applet]
*[http://websvn.kde.org/trunk/KDE/kdeadmin/system-config-printer-kde/ system-config-printer-kde]
*[http://websvn.kde.org/trunk/extragear/utils/guidance-power-manager/ Guidance Power Manager], a battery applet
*[https://code.launchpad.net/ubiquity/trunk Ubiquity], installer for Kubuntu
*[https://code.launchpad.net/~ubuntu-core-dev/gdebi/ubuntu GDebi], .deb package installer
*[https://code.launchpad.net/~jr/install-package/trunk install-package], graphical apt-get
*[http://draketo.de/light/english/pyrad pyRad], wheel type command interface
*[http://websvn.kde.org/trunk/KDE/kdebindings/python/pykde4/examples/ some examples are in the PyKDE source]
*[http://websvn.kde.org/trunk/KDE/kdegames/kajongg/ Kajongg], a board game

[[Category:Python]]

Schedules/KDE4/4.6 Feature Plan

2010-08-27T04:49:38Z

Wrohdewald: Kajongg for 4.6

Schedules/KDE4/4.5 Feature Plan

2010-05-27T10:37:21Z

Wrohdewald:

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

See also:

*[[Schedules/KDE4/4.5 Release Schedule]]
*[[Schedules/KDE4/4.5 Release Goals]]
*[[Schedules/KDE4/4.4 Feature Plan]]

 Legend:

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

__TOC__

 

= kdeadmin =

{| 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|system-config-printer-kde|Restore feature parity with KDEPrint3 where possible.||Jonathan Riddell, John Layt}}

|}

 

= kdeartwork =

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

 

= kdebase-apps =

{| 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|Konqueror|Improvements in session-management|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureTodo|Konqueror|Improvements in tab-bar widget|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|Konqueror|New Konqueror bookmarks using Akonadi and Nepomuk, awesome bar|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|nspluginviewer|npruntime scripting support|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|Konqueror|Add speeddial/thumbnails-like start page|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|Konsole|Finish implementing tab context menu|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureDone|Konsole|Allow setting tab profile from file on command-line|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureInProgress|Konsole|Adds support for SHELL_SESSION_ID|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureDone|Konsole|Modernize menu layout|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Konsole|Move to KTabWidget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|print-manager|New Print manager KCM and applet replacement, using C++|dantti85-pk@yahoo.com.br|Daniel Nicoletti}}
{{FeatureDone|Dolphin|Drag and drop on tabs|toddrme2178@gmail.com|Todd}}
{{FeatureDone|Dolphin|Make menus like "View Mode", "Additional Information" and "Sort By" available as toolbar buttons|toddrme2178@gmail.com|Todd}}
{{FeatureTodo|Dolphin|Smooth scrolling|fredrik@kde.org|Fredrik Höglund}}
{{FeatureTodo|Dolphin|Faceted browsing|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|Dolphin|Make use of additional columns (Symbolic Link Destination, Path or URL) in KFileItemDelegate|frank78@googlemail.com|Frank Reininghaus}}
|}
 

= kdebase-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|KWallet|Single Sign On using PAM|lemma@confuego.org|Michael Leupold}}
{{FeatureTodo|network kioslave|Backend for LISa|kossebau@kde.org|Friedrich Kossebau}}
{{FeatureTodo|network kioslave|Backend for SMB|kossebau@kde.org|Friedrich Kossebau}}
{{FeatureTodo|network kioslave|Integrate with remote and zeroconf kioslaves|kossebau@kde.org|Friedrich Kossebau}}
{{FeatureTodo|Locale KCM|Add support for new KLocale and KCalendarSystem features (see kdelibs section) including Digit Groups, AM/PM, etc. Improvements to usability of existing money display options.|john@layt.net|John Layt}}
{{FeatureInProgress|network kioslave|Backend for UPnP|kossebau@kde.org|Friedrich Kossebau}}
{{FeatureTodo|network kioslave| Backend to discover bluetooth devices and they services |edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|bluetooth kioslave|Backend to browse bluetooth devices|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureDone|Nepomuk|Monitor file system changes via inotify|trueg@kde.org|Sebastian Trueg}}
{{FeatureTodo|KNotify|Route solid errors via knotify to the device notifier|wilderkde@gmail.com|Jacopo De Simoi}}
|}

 

= kdebase-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
|-
! style="text-align: center;" colspan="4" | Non-Plasma, Non-KWin
{{FeatureDone|KInfoCenter|Complete rewrite of KInfoCenter|hubnerd@ntlworld.com|David Hubner}}
{{FeatureDone|KInfoCenter|Add Export functionality into KInfoCenter|hubnerd@ntlworld.com|David Hubner}}
{{FeatureDone|DeviceInfo KCM|New DeviceInfo KCM for KInfoCenter|hubnerd@ntlworld.com|David Hubner}}
{{FeatureDone|Summary KCM|New Summary KCM for KInfoCenter|hubnerd@ntlworld.com|David Hubner}}
{{FeatureTodo|Icons KCM|More configurable icon sizes|christoph@maxiom.de|Christoph Feck}}
{{FeatureTodo|Fonts KCM|More configurable fonts|christoph@maxiom.de|Christoph Feck}}
{{FeatureTodo|BlueDevil Wizard |Write a new Wizard to pair Bluetooth devices |alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|Bluetooth KCM|New KCM to manage all bluetooth configurations and devices|ereslibre@kde.org|Rafael Fernandez}}
{{FeatureTodo|Screenedges|Screenedges handling outside of kwin/plasma|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|Oxygen style|Move window using left-mouse button on windows' empty areas|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureDone|Oxygen configuration|Oxygen style and decoration standalone expert configuration tool|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureDone|Free Space Notifier Daemon|Small daemon that warns you when your home has almost no space left|knuckles@gmail.com|Ivo Anjo}}
{{FeatureInProgress|Activities Daemons|Daemons to handle info about activities (kded daemon and a nepomuk service)|ivan.cukic@kde.org|Ivan Cukic}}
{{FeatureInProgress|Systemsettings|driconf KCM|fredrik@kde.org|Fredrik Höglund}}
{{FeatureDone|PowerDevil|Display brightness OSD|debfx-kde@fobos.de|Felix Geyer}}
{{FeatureDone|Keyboard|Merge keyboard hardware and layouts configuration UI|arysin@gmail.com|Andriy Rysin}}
{{FeatureDone|Keyboard|Allow adding layouts by language|arysin@gmail.com|Andriy Rysin}}
{{FeatureDone|Keyboard|Add keyboard layout indicator plasma applet|arysin@gmail.com|Andriy Rysin}}
{{FeatureDone|Keyboard|Allow configuring keyboard model without configuring layouts|arysin@gmail.com|Andriy Rysin}}
{{FeatureDone|Keyboard|Allow by-window switching and KDE shortcut without configuring layouts|arysin@gmail.com|Andriy Rysin}}
{{FeatureDone|Keyboard|Rewrite keyboard layouts app into kded daemon|arysin@gmail.com|Andriy Rysin}}
|-
! style="text-align: center;" colspan="4" | Plasma
{{FeatureInProgress|systemtray/taskmanager|port the systray and tasks applet to windows|windows@kde.org|kde windows}}
{{FeatureInProgress|systemtray|monochrome statusnotifier based systray icons support|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|systemtray|sort icons by category|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|systemtray|put hidden icons in a popup menu|notmart@gmail.com|Marco Martin}}
{{FeatureDone|tasks dataengine|export all informations needed to build an applet comparable to the current one|matthieu_gallien@yahoo.fr|Matthieu Gallien}}
{{FeatureDone|notifications|split systemtray and notifications applet|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|notifications|new look and behaviour for notifications|notmart@gmail.com|Marco Martin}}
{{FeatureDone|notifications|support for remote applets for notifications|notmart@gmail.com|Marco Martin}}
{{FeatureDone|netbook/SAL|use QStandardModels|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|netbook/SAL|support for drag and drop of items|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|netbook/SAL|package manager invocation from the toolbox|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|netbook/Workspace KCM|New default options for KWin: tabbox as present windows, that will be set as regular grid|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|libplasma/extenders|put extendergroups in scrollwidgets|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|libplasma/extenders|possibility to detach exteneritems as standalone windows|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|libplasma/theme|more transparent dialogs when the blur effect is enabled|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|libplasma/desktop|Activity Manager UI|chani@kde.org|Chani}}
{{FeatureTodo|accounts applet|a plasma widget that is a central place to add accounts to social sites like identica and opendesktop, optimized for the netbook shell|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|libplasma|Improvements to Calendar/Clock widgets. Improved config ui. Allow multiple holidays on same day. Allow multiple Holiday Regions. Weekends. etc.|john@layt.net|John Layt}}
{{FeatureTodo|folderview|"Open folder" icon to open folder into pop-up at request instead of automatically.|bigras.bruno@gmail.com|Bruno Bigras}}
{{FeatureTodo|folderview|Extend the configuration UI for nepomuksearch|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Extend Calendar DataEngine with Akonadi calendar incidents|Allows to query calendar events/todos from Akonadi in Plasma|gladhornKDEorg|Frederik Gladhorn}}
{{FeatureDone|calculator|Added optional libqalculate support in the calculator runner|agostinelli@gmail.com|Matteo Agostinelli}}
{{FeatureInProgress|KRunner|Add some advanced sorting to KRunner using Nepomuk|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureTodo|KRunner|Improve keyboard navigation & command history interaction|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|device-notifier|Route all solid error notifications via knotify to the device notifier|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|device-notifier|Detailed (HAL) error notifications in the device notifier|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|Plasma::Theme|Themed CSS support|sebas@kde.org|Sebastian Kügler}}
{{FeatureTodo|battery|Weighted charge information for multiple batteries|sebas@kde.org|Sebastian Kügler}}
{{FeatureTodo|Plasma|Welcome plasmoid|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|crystal|New desktop search widget|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|networkmanagement|Network management Plasmoid|sebas@kde.org|Sebastian Kügler}}
{{FeatureDone|quicklaunch|Improvements from Ingomar Wesp|l.appelhans@gmx.de|Lukas Appelhans}}

|-
! style="text-align: center;" colspan="4" | KWin
{{FeatureDone|Tiling|Merge window tiling branch|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|KWin|New flag to exclude windows from switchers|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KCM Decoration|New decoration kcm with previews and GHNS|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Aurorae|Port Aurorae to GraphicsView and KDecoration|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Aurorae|Better themeing support|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Aurorae|Window tabbing support|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Aurorae|Decorations on window sides|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Aurorae|Autohiding decoration for maximized windows|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|kwin|hide windows from other activities|chani@kde.org|Chani}}
{{FeatureTodo|Effects|Move features from present windows to libkwineffects to make them available in desktop grid|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Effects|Add close window button to each window in present windows/desktop grid|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Window Tabbing/libtaskmanager|Announce window groups to be used for grouping in tasks applet|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|KWin/plasma|New window type for Plasma dashboard|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Effects|New blur effect|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Effects|High quality scaling shader for the taskbar thumbnails|fredrik@kde.org|Fredrik Höglund}}
{{FeatureTodo|KWin|Hint for defining the window snap rect|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Effects|Glide effect for opening and closing windows|iori.yagami.26979@gmail.com|Iori Yagami}}
|}

 

= 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|KStars|Display Comet Magnitudes whenever possible|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Information links in-place for each technical term|akarshsimha@gmail.com|Akarsh Simha}} {{FeatureTodo|KStars|Tool to suggest star-hopping techniques???|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Extend conjunction tool to have one object unspecified, but have a genre of objects specified instead|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Simulate Lunar Eclipses|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Simulate Satellites and Iridium Flares|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Social and Geographical Integration for KStars|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Marble widget for Geolocation tool|mboquien@free.fr|Médéric Boquien}}
{{FeatureTodo|KStars|Better printed star charts|kstars@30doradus.org|Jason Harris}}
{{FeatureTodo|KStars|Better rendering of comets/asteroids|kstars@30doradus.org|Jason Harris}}
{{FeatureTodo|KStars|Texture mapping of the skymap???|kstars@30doradus.org|Jason Harris}}
{{FeatureTodo|Kalzium|Port Kalzium to use QGV based periodic table widget|mhanwell@kde.org|Marcus D. Hanwell}}
{{FeatureTodo|Marble|Add proper support for GPX waypoints, tracks and routes display|anders@alweb.dk|Anders Lund}}
{{FeatureTodo|Marble|Export map to MxN pixel bitmap|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Map Contents translation|tackat@kde.org|Torsten Rahn}}
{{FeatureDone|Marble|Support OpenStreetMap Nominatim as search backend (MarbleRunner)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Generalized Animations with GeoDataLookAt support|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Online-Routing|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|GPS improvements|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Maemo Support|earthwings@gentoo.org|Bastian Holst, Dennis Nienhüser}}
{{FeatureInProgress|Marble|GeoGraphicsScene for Online Service Plugins|bastianholst@gmx.de|Bastian Holst}}
{{FeatureInProgress|Marble|Follow XDG Base Directory Specification|bastianholst@gmx.de|Bastian Holst}}
{{FeatureDone|Marble|Download region|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Implement sun locator blendings as derived classes of Marble::Blending|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Configurable texture layer blending|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Import geonames city data|sonu.itbhu@gmail.com|Harshit Jain}}
{{FeatureInProgress|Marble|Bookmark support|anik.varshney@gmail.com|Kumar Anik Varshney}}
{{FeatureInProgress|Marble|Various Marble speed improvements|rahn@kde.org|Torsten Rahn, Ariya Hidayat}}
{{FeatureInProgress|Marble|Plugin to display APRS data|hardaker@users.sourceforge.net|Wes Hardaker}}
{{FeatureDone|KAlgebra|Type checker for expressions to statically detect errors|aleixpol@kde.org|Aleix Pol}}
{{FeatureDone|KAlgebra|Support for drawing implicit curves|percy.camilo.ta@gmail.com|Percy Camilo Triveño Aucahuasi}}
{{FeatureInProgress|Parley|Parley practice mode rewritten|gladhornKDEorg|Daniel Laidig, Frederik Gladhorn}}
{{FeatureTodo|Parley|LaTeX support|laidig_kde.org|Daniel Laidig}}
{{FeatureTodo|Parley|Better support for entering synonyms|laidig_kde.org|Benjamin Schleinzer, Daniel Laidig}}
{{FeatureTodo|Cantor|import and polish Qalculate! backend|mail@milianw.de|Milian Wolff}}
{{FeatureDone|KTurtle|Implement GHNS download support|nielsslot@gmail.com|Niels Slot}}
{{FeatureTodo|KTurtle|Implement GHNS upload support|nielsslot@gmail.com|Niels Slot}}
{{FeatureDone|Rocs|Node beautification in SVG|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Threads for not blocking the UI|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Redesigned the UI for better usability|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Plugin System|wiglot@gmail.com|Wagner Reck}}
{{FeatureDone|Rocs|Small plugins as examples|wiglot@gmail.com|Wagner Reck}}
{{FeatureDone|Rocs|Multiple Script support|tcanabrava@kde.org|Tomaz Canabrava}}
|}
 

= 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
{{FeatureTodo|Granatier|Arena Editor|k.hias@gmx.de|Mathias Kraus}}
{{FeatureInProgress|Kajongg|New traditional Mahjongg for four players|wolfgang@rohdewald.de|Wolfang Rohdewald}}
{{FeatureTodo|Kajongg|Default voices for computer players|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|KBounce|Difficulty levels|ascherfy@gmail.com|Andreas Scherf}}
{{FeatureDone|KBounce|Random images as background|ascherfy@gmail.com|Andreas Scherf}}
{{FeatureTodo|KBreakOut|Level Sets|fela.kde@gmail.com|Fela Winkelmolen}} {{FeatureTodo|KBreakOut|Sound|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureDone|KGoldrunner|Add the Demolition game (20 levels)|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|Kigo|Load SGF games from command line and register to mimetype 'application/x-go-sgf'|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Kigo|Fix KNewStuff provider issues|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Kiriki|Hint|luizromario@gmail.com|Luiz Romário Santana Rios}}
{{FeatureTodo|Kolf|Replace with Kolf 2 (help on coding and artwork desired)|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Konquest|Merge the patch by Sean D'Epagnier to implement many features like map editing|pinaraf@pinaraf.info|Pierre Ducroquet}}
{{FeatureDone|KPat|Add keyboard controls to allow playing without a mouse.|parker.coates@kdemail.net|Parker Coates}}
{{FeatureInProgress|KPat|Create a new LibKCardGame from KPat's card scene logic. Make it generic and friendly enough for use in other card games.|parker.coates@kdemail.net|Parker Coates}}
{{FeatureTodo|KsirK|rewrite AI code or at least correct most problems related in bug #170777. Volunteers wanted!|kleag@free.fr|Gaël de Chalendar}}
{{FeatureTodo|KsirK|Boost playing over Jabber|kleag@free.fr|Gaël de Chalendar}}
{{FeatureTodo|KSquares|Re-write computer player, make it act faster and more intelligent|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureTodo|KSquares|Add more types of boards: hexagonal, triangular|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureTodo|KSudoku|Import new engine|joselb@gmx.net|Johannes Bergmeier}}
{{FeatureTodo|KSudoku|Port game to new engine|joselb@gmx.net|Johannes Bergmeier}}
{{FeatureTodo|KSudoku|Adapt view to show information provided by engine|joselb@gmx.net|Johannes Bergmeier}}
{{FeatureTodo|KSudoku|Add new actions to GUI|joselb@gmx.net|Johannes Bergmeier}}
{{FeatureInProgress|KTuberling|A new "fast switch" between playgrounds|alex@eyeos.org|Alex Fiestas}}
{{FeatureDone|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}233784 Optimize size of puzzle files in default collection] (temporarily fixed for this release cycle with an awful hack)|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}211859 Recieve new puzzles over KNewStuff]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}211861 Introduce handicap as a means to configure difficulty]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}211866 Implement puzzle piles to organize pieces]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}212814 Quick piece grouping]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}213774 Add magnifying glass]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Palapeli|Rewrite puzzle table mouse interaction stack|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Palapeli|Cleanup config dialog code|majewsky@gmx.net|Stefan Majewsky}}
|}

 

= kdegraphics =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|libkdcraw|Make color management options more flexible|marcel.wiesweg@gmx.de|Marcel Wiesweg}}
{{FeatureDone|libksane|Improve auto-selection|kare.sars@iki.fi|Kåre Särs}}
{{FeatureDone|libksane|Highlight scanned area|kare.sars@iki.fi|Kåre Särs}}
{{FeatureTodo|libksane|Add public API for available devices|kare.sars@iki.fi|Kåre Särs}}
{{FeatureTodo|gwenview|Show Nepomuk info in image meta info|agateau@kde.org|Aurelien Gateau}}
{{FeatureTodo|gwenview|Persistent changes|agateau@kde.org|Aurelien Gateau}}
{{FeatureTodo|okular|Thumb creators via Okular Core|harsh@harshj.com|Harsh J}}

|}

 

= 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
{{FeatureTodo|katepart|Add visual block mode and make the basic commands support it|ehambergαgmail.com|Erlend Hamberg}}
{{FeatureTodo|katepart|context dependent indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|scripting configuration, esp. for indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|list of available scripts and indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|GHNS for scripts/indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|easier writing of indenters, esp. by automatically reloading them when changed|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|extend list of available default styles for highlighting, remove hardcoded colors from existing XML files|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|improve AutoBrace plugin|mail@milianw.de|Milian Wolff}}
{{FeatureInProgress|katepart/ktexteditor|defaultvalues, regular expressions, mirroring master, scripting of templates|jowenn(you_know)kde(here_too)org|Joseph Wenninger}}
{{FeatureInProgress|ktexteditor plugin|InsaneHTML_LE (zencoding like selector input (light edition)|jowenn(you_know)kde(here_too)org|Joseph Wenninger}}
{{FeatureTodo|katepart|replace smart cursor/ranges API|cullmann@kde.org|Christoph Cullmann}}
{{FeatureTodo|kdeui|API to integrate KStatusNotifierItem and KNotification: both as class api and DBus specification API|davide.bettio@kdemail.net|Davide Bettio}}
{{FeatureDone|KCalendarSystem|Add support for Date Difference calculations.|john@layt.net|John Layt}}
{{FeatureDone|KCalendarSystem|Add support for era based calendar systems.|john@layt.net|John Layt}}
{{FeatureDone|KCalendarSystem|Add new calendar systems: Japanese Era, Thai, Taiwanese.|john@layt.net|John Layt}}
{{FeatureInProgress|KCalendarSystem|Add support for Unicode format strings for Qt and cross-platform compatability.|john@layt.net|John Layt}}
{{FeatureTodo|KCalendarSystem|Add new astronomical calculation support classes to be used in kdelibs to build new astronomically based calendar systems, and in kdepim to build new version of libkholiday.|john@layt.net|John Layt}}
{{FeatureTodo|KCalendarSystem|Add new calendar systems: Bahai'i, Chinese, Buddhist, etc.|john@layt.net|John Layt}}
{{FeatureTodo|KCalendarSystem|Add support for traditional/USA week numbering.|john@layt.net|John Layt}}
{{FeatureTodo|kdecore|Group policy (Windows) backend for KAuth|drf@kde.org|Dario Freddi}}
{{FeatureTodo|KDEPrint|Add framework for standard actions for 'Send to...' for e-mail, fax, etc by printing to PDF/PS.|john@layt.net|John Layt}}
{{FeatureTodo|kdeui|Implement caps-lock warning for password entry widgets|lemma@confuego.org|Michael Leupold}}
{{FeatureTodo|KLocale|Implement support for number grouping other than thousands using LC_NUMERIC and LC_MONETARY formats, e.g. India 00 00 000 and China 0000 0000.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Add configuration for AM/PM symbols.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Full POSIX compliant format support for date, time, numbers and money.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement more 'named' date/time formats, e.g. ISO, UnixTimestamp, RFC3339, etc.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Add Full date format in addition to existing short and long.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Add default colour to optionally display negative numbers.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement separate backends for each supported platform/desktop to use platform localisation in place of KDE locale.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement support for additional Country Code standards: ISO Alpha 3, ISO Numeric 3, FIPS-10.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement support for Country Code sub-regions, i.e. States/Provinces/etc. Needed for new KHolidays.|john@layt.net|John Layt}}
{{FeatureTodo|kdeui|Improvements to KDatePicker/KDateTable for feature parity with Plasma Calendar widget, i.e. holiday support, select calendar system, etc.|john@layt.net|John Layt}}
{{FeatureTodo|kdeui|DBus interface in StatusNotifierItem to connect it with freedesktop notifications instances|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|khtml|Improvements in kwallet integration|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|khtml|Basic audio/video tag support|germain@ebooksfrance.org|Michael Howell and Germain Garand}}
{{FeatureInProgress|khtml|DOM3 XPath/XPath1 support|maksim@kde.org|Maks Orlovich}}
{{FeatureDone|khtml|Selectors API1|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|khtml and kparts|More general KPart scripting interfaces|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|khtml|Implement more of DOM3's CSSOM View module|germain@ebooksfrance.org|Germain Garand}}
{{FeatureInProgress|khtml|Implement missing parts of DOM3's Background and Borders module|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|khtml|add new form widgets defined in HTML5 draft|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|KNewStuff|Improved Download Dialog, multiple previews, better integration of details, changelog is displayed|gladhornKDEorg|Frederik Gladhorn}}
{{FeatureInProgress|KNewStuff|Icon view mode|gladhornKDEorg|Reza Shah, Frederik Gladhorn}}
{{FeatureDone|KNewStuff|Upload dialog rewritten: It now supports updating of old uploads, previews, most data that can be entered on the website and allows direct login to the account|gladhornKDEorg|Frederik Gladhorn}}
{{FeatureTodo|KNewStuff|Support more than one payload|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|kdeui|Social About Dialog|teo@kde.org|Téo Mrnjavac}}
{{FeatureTodo|kdeui|Generic find bar widget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureTodo|kio|SSL client certificate support|ahartmetz@gmail.com|Andreas Hartmetz}}
{{FeatureTodo|kio|SSL root certificate list GUI + backend|ahartmetz@gmail.com|Andreas Hartmetz}}
{{FeatureDone|kio|Add "apply to all" checkbox in renamedialog and allow for automatic renaming|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kio|Port renamedialog to KFileMetaDataWidget|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kio|Don't select extension in renamedialog|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kio|Better listing of applications in file "open with" context menu|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kio|Context menu entry to open all files in their default applications|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kio|Add support for additional columns (e.g., smybolic link destination) in KFileItemDelegate|frank78ac@googlemail.com|Frank Reininghaus}}
{{FeatureDone|kfile|Scroll wheel support for breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kfile|Show all sub-folders in breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kfile|Middle-click on subfolder in the breadcrumb bar to open in a new tab|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kfile|Easier access to protocols in breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureTodo|kfile|Show sub-sub-folders (and so on) in breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kdecore|Generic shared-memory cache|mpyne@kde.org|Michael Pyne}}
{{FeatureInProgress|kdeui|Redesigned icon cache|mpyne@kde.org|Michael Pyne}}
{{FeatureDone|kdeui|Support alpha channel in KColor classes|christoph@maxiom.de|Christoph Feck}}
{{FeatureDone|nepomuk|Redesigned Nepomuk::TagWidget which can now actually be used by applications|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|kio|Remember downloads via Nepomuk|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|solid|Broadcast mount/unmount messages across processes|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureTodo|solid|Add parent matching to predicate parsing|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureDone|kdeui|Add the KRecursiveFilterProxyModel to kdeui/itemviews|steveire@gmail.com|Stephen Kelly}}
|}
 

= 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|Video Thumbnailer|Add ffmpegthumbnailer for faster video thumbnailing|ascherfy@gmail.com|Andreas Scherf}}
{{FeatureTodo|JuK|Remove Qt/KDE3 support lib requirements -- will move to KDE 4.5 feature plan|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Allow setting covers directly from URLs supported by KIO - drag/drop already allows this however -- will move to KDE 4.5 feature plan|mpyne.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
{{FeatureTodo|Kopete|UPnp Support|mattr@kde.org|Matt Rogers}}
{{FeatureTodo|Kopete|Jabber Jingle video support|detlev.casanova@gmail.com|Detlev Casanova}}
{{FeatureTodo|Kopete|Jabber Jingle ICE support|detlev.casanova@gmail.com|Detlev Casanova}}
{{FeatureTodo|Kopete|Add support for urls to Bonjour plugin|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Kopete|Rich text support for ICQ|kedgedev@gmail.com|Roman Jarosz}}
{{FeatureDone|Kopete|Extended video controls|fschaefer.oss(at)googlemail.com|Frank Schaefer}}
{{FeatureTodo|Kopete|Akonadi History Plugin|roideuniverse@gmail.com|Kaushik Saurabh}}
{{FeatureTodo|Krdc|Connection status and reconnect screen|murraytony@gmail.com|Tony Murray}}
{{FeatureDone|Krdc|Much improved new connection screen: more info, sortable, interactive, and better use of space|murraytony@gmail.com|Tony Murray}}
{{FeatureInProgress|KGet|Use plasma notifications to show the progress|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|KGet|Refaktor Torrent-Plugin to base on the newly created libktorrent from extragear|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|KGet|Better error handling|l.appelhans@gmx.de|Lukas Appelhans}}
|}

 

= 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|KAlarm|Port to Akonadi|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|KMail|Port to Akonadi|kde-pim@kde.org|Thomas McGuire}}
{{FeatureInProgress|KOrganizer|Port to Akonadi|kde-pim@kde.org|Frank Osterfeld, Sebastian Sauer}}
{{FeatureInProgress|KJots|Port to Akonadi|kde-pim@kde.org|Stephen Kelly}}
{{FeatureInProgress|KHolidays|Add support for alternative calendar systems, advanced holiday calculations, and improved API.|john@layt.net|John Layt}}
|}

 

= 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
{{FeatureTodo|knowledgebase|port knowledgebase plasmoid to new engine|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureTodo|knowledgebase|Add categories|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureDone|Bookmarks widget|New|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Mandelbrot Wallpaper|Performance improvements|jacob.benoit.1@gmail.com|Benoit Jacob}}
{{FeatureDone|Mandelbrot Wallpaper|Rendering improvements (through dithering, extra iterations, and better/simpler formulas)|jacob.benoit.1@gmail.com|Benoit Jacob}}
{{FeatureDone|Mandelbrot Wallpaper|Allow to import/export parameters and to export to PNG images|jacob.benoit.1@gmail.com|Benoit Jacob}}
{{FeatureDone|Comic Applet|Add option to show "text", "icons" or both "text and icons" for tabs|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Comic Applet|Prefetch next and previous comic strip (thx to Miha Cancula)|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Character Runner|New|akreuzkamp@web.de|Anton Kreuzkamp}}
{{FeatureDone|KDE Observatory|Performance improvements, new data engine|sandroandrade@kde.org|Sandro Andrade}}
{{FeatureDone|Plasmaboard|Completly rework the current onscreen keyboard and add key layouts for tablets and mids. Better performance, better useability, less memory usage. See: http://btux1984.wordpress.com/ |bjoern@ruberg-wegener.de|Björn Ruberg}}
|}

 

= 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|Lokalize|Integrate snowball stemmer for glossary|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Continue implementing XLIFF spec|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Segmentation [editing] functionality|shafff@NOSPAMukr.net |Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Remote translation memories|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate with nepomuk (fast stats retrieval, tag cloud - incl sharing!)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Kate|Replace old snippet plugin through TNG plugin and enhance the usability of the new plugin|jowenn(you_know)kde(here_too)org|Joseph Wenninger}}
{{FeatureDone|Kate|Port the old XML completion plugin (xmltools)|tomastrnka@gmx.com|Tomáš Trnka}}
{{FeatureInProgress|Umbrello|Add a code importing wizzard|andi.fischer@NOSPAMhispeed.ch|Andi Fischer}}
|}

 

= 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
{{FeatureTodo|Ark|Add an options dialog (maybe)|haraldhv@stud.ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Simplify Kerfuffle's API (jobs, interfaces etc) and try to make it stable|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Support for custom options from the compression interface (eg. a slider for selecting compression level for rar files)|haraldhv@stud.ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Add feedback for the latest operation in the status bar|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Try multiple plugins for each archive type before failing|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make the internal previewer optional|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Add a "Preview with..." context menu item|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make Kerfuffle really thread-safe (and use threads in less places)|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Get rid of the Observer code in Kerfuffle|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make error reporting work as expected in Kerfuffle|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Okteta|add Kate-like search tool|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|copy again puts also a value or char variant of the data to clipboard|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 Okular like embedded notifications|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 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|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|Merge row and column widgets into one|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|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add view profiles, incl. editor/manager|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|printer-applet|Restore feature parity with KDEPrint3 where possible.||Jonathon Riddell, John Layt}}
{{FeatureInProgress|Okteta|Allow writing structure definitions in JavaScript|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureInProgress|Okteta|Add possibility to set count of bytes per line/group|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|kdelirc/kremotecontrol|Transition from KDELirc to KRemoteControl|michael_zanetti@gmx.net|Michael Zanetti}}
{{FeatureDone|KGpg|Add "caff" mode for keysigning|kde@opensource.sf-tec.de|Rolf Eike Beer}}
{{FeatureDone|Okteta|Add KNewStuff support to the structures tool|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureDone|Okteta|Allow pinning structure beginning to a specific offset|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureDone|Okteta|new export formats: S-Record, Intel Hex, Base32, Ascii85, Uuencoding, Xxencoding|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|add QIODevice for AbstractByteArrayModel and make mimetype detection use this instead of only filename |kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|Refactor mouse input to controllers for the bytearray widget|kossebau@kde.org|Friedrich W. H. Kossebau}}
|}

 

= kdetoys =

{| 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|kteatime|Port to KStatusNotifierItem|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|kteatime|Port to KConfigXT|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|kteatime|Support categories|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|kteatime|Improved indicator icon painting|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|kteatime|Fork multiple instances for multiple timers|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|kteatime|Tea runner|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|kteatime|Improved command line|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Do some refactoring in amor|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Improve theme support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Implement KNewStuff support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Revamp configure dialog|kde@hilefoks.org|Stefan Böhmann}} {{FeatureTodo|amor|Sound support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Add KStatusNotifierItem support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|ktux|Do some refactoring in ktux|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|ktux|Revamp configure dialog|kde@hilefoks.org|Stefan Böhmann}} {{FeatureTodo|ktux|Sound support|kde@hilefoks.org|Stefan Böhmann}}
|}

 

= Other =

{| 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.5 Feature Plan

2010-04-14T15:04:35Z

Wrohdewald:

Development/Tutorials/Using KActions

2010-03-14T17:20:58Z

Wrohdewald: & in action text

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

{{TutorialBrowser|

series=Beginner Tutorial|

name=How To Use KActions and XMLGUI|

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

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

reading=None
}}

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

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

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

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

== The Code ==

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

#include "mainwindow.h"

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

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

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

#include <KXmlGuiWindow>
#include <KTextEdit>

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

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

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

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

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

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

setupActions();
}

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

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

setupGUI(Default, "tutorial3ui.rc");
}
</code>

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

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

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

The text of the action should contain a <tt>&</tt> because that makes it easier to translate in non latin1 languages. In Japanese, the translation might be <tt>ソース(&S)</tt> and without the <tt>&</tt> in the english text the translators cannot know if they have to add a <tt>&</tt> or not.

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

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

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

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

===KStandardAction===

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

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

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

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

==Defining your own help menu==
The help menu is god-given, that is why all KDE help menus look the same. If you want to create your own help menu, go [http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/widgets/khelpmenu.h?revision=1002779&view=markup here] and search for the explanation around showAboutApplication().

==XMLGUI==

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

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

''See also'' [http://developer.kde.org/documentation/library/kdeqt/kde3arch/xmlgui.html developer.kde.org] which still provides valid information for KDE4.

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

Since the description of the UI is defined with XML, the layout must follow strict rules. This tutorial will not go into great depth on this topic, but for more information, see the [[Development/Architecture/KDE4/XMLGUI_Technology|detailed XMLGUI page]] (here is an older tutorial: [http://developer.kde.org/documentation/tutorials/xmlui/preface.html]).

===tutorial3ui.rc===
<code xml>
<?xml version="1.0" encoding="UTF-8"?>
<gui name="tutorial3"
version="1"
xmlns="http://www.kde.org/standards/kxmlgui/1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.kde.org/standards/kxmlgui/1.0
http://www.kde.org/standards/kxmlgui/1.0/kxmlgui.xsd" >

<MenuBar>
<Menu name="file" >
<Action name="clear" />
</Menu>
</MenuBar>

<ToolBar name="mainToolBar" >
<text>Main Toolbar</text>
<Action name="clear" />
</ToolBar>

</gui>
</code>

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

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

Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update. Be sure it is an integer, if you use a decimal value, it will not work, but will not notify that it didn't. '''Note:''' The version attribute must be an integer number, i.e. it may not contain dots or other non-digits like an application version number.

Some notes on the interaction between code and the .rc file: Menus appear automatically and should have a <tt><nowiki><text/></nowiki></tt> child tag unless they refer to standard menus. Actions need to be created manually and inserted into the actionCollection() using the name in the .rc file. Actions can be hidden or disabled, whereas menus can't.

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

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

set(tutorial3_SRCS
main.cpp
mainwindow.cpp
)

kde4_add_executable(tutorial3 ${tutorial3_SRCS})

target_link_libraries(tutorial3 ${KDE4_KDEUI_LIBS})

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

This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.

===Make, Install And Run===
If you don't have write access to where your KDE4 installation directory, you can install it to a folder in your home directory.

To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:
mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial3
which will create a KDE-like directory structure in your user's home directory directory and will install the executable to {{path|$HOME/bin/tutorial3}}.

==Moving On==
Now you can move on to [[Development/Tutorials/Saving_and_loading|saving and loading]].

[[Category:C++]]