KDE TechBase - Changes related to "ISV (tr)" [en]

ISV/Roadmap

2013-05-13T13:43:23Z

‎KDE development: add forgotten are word

ISV/Why use KDE

2013-05-13T13:40:37Z

‎Sub-Projects: some link and name changes

ISV/Developer Information

2013-05-13T12:02:16Z

replace Compilation FAQ which was available for pre KDE4 with Build instructions, drop dcop, fix kioslaves link, and some portland link fixes

ISV/Support

2013-05-13T11:12:15Z

‎Commercial Support: add digia, i can't find a replacement for Business Directory

ISV/Roadmap

2013-05-13T10:30:24Z

‎KDE development: fix link of epics page

@@ Line 9: / Line 9: @@
 KDE Frameworks 5 is well underway. It will allow to move to a more modern graphics rendering engine, make development platform more portable, and make it easier to reuse solutions KDE has built.
-The Roadmap of KDE Software Compilation 4 is divided into the [[Schedules/KDE4/4.11_Release_Schedule|Release Schedule]] and the [[Schedules/KDE4/4.11_Feature_Plan|Feature Plan]]. And KDE Frameworks 5 on going efforts tracked as [http://community.kde.org/Frameworks/Epics Epics].
+The Roadmap of KDE Software Compilation 4 is divided into the [[Schedules/KDE4/4.11_Release_Schedule|Release Schedule]] and the [[Schedules/KDE4/4.11_Feature_Plan|Feature Plan]]. And KDE Frameworks 5 on going efforts are tracked as [http://community.kde.org/Frameworks/Epics Epics].
 == Sub-projects ==

@@ Line 5: / Line 5: @@
 == KDE e.V. ==
-The non-profit organization [http://ev.kde.org KDE e.V.] helps in creating and distributing KDE by securing cash, hardware, and other donations, then using donations to aid KDE development and promotion. All its members are part of the KDE community which means the KDE e.V. plays an important role in the KDE project. Members of the KDE e.V. form several '''working groups''' like the [http://www.spreadkde.org/handbook/mwg/charter Marketing Working Group (MWG)] and the [http://ev.kde.org/workinggroups/hci.php Human-Computer Interaction (HCI) Working Group] to help realize KDE's vision.
+The non-profit organization [http://ev.kde.org KDE e.V.] helps in creating and distributing KDE by securing cash, hardware, and other donations, then using donations to aid KDE development and promotion. All its members are part of the KDE community which means the KDE e.V. plays an important role in the KDE project. Members of the KDE e.V. form several '''working groups''' like the [http://spread.kde.org/handbook/mwg/charter Marketing Working Group (MWG)] and the [http://ev.kde.org/workinggroups/hci.php Human-Computer Interaction (HCI) Working Group] to help realize KDE's vision.
 == Adoption of KDE ==
@@ Line 11: / Line 11: @@
 == Development ==
-The KDE development process takes place in steady release cycles. '''[http://developer.kde.org/development-versions/release.html Release schedules]''' and '''feature plans''' help the KDE project coordinating a KDE release by introducing several ''phases'' like ''feature freeze'' and ''message freeze''. This phases make sure that developers concentrate on polishing the release and the translation teams have time enough to translate all the KDE software into many different languages. Further information about KDE development tools can be found on the [[Development|development pages]].
+The KDE development process takes place in steady release cycles. '''[[Schedules|Release schedules and feature plans]]''' help the KDE project coordinating a KDE release by introducing several ''phases'' like ''feature freeze'' and ''message freeze''. This phases make sure that developers concentrate on polishing the release and the translation teams have time enough to translate all the KDE software into many different languages. Further information about KDE development tools can be found on the [[Development|development pages]].
 === Documentation ===
@@ Line 17: / Line 17: @@
 === Technologies ===
-KDE provides a wide range of '''powerful technologies''' such as [http://khtml.info KHTML and KJS] which are adopted by other companies like Apple (Safari browsers) and Nokia. Additionally there are several '''development frameworks''' like KParts (KDE's component technology), KIO (network/protocol architecture) or KXmlGui (build GUIs based on XML definitions).
+KDE provides a wide range of '''powerful technologies''' such as [http://www.webkit.org/ WebKit and KJS] which are adopted by other companies like Apple (Safari browsers) and Nokia. Additionally there are several '''development frameworks''' like KParts (KDE's component technology), KIO (network/protocol architecture) or KXmlGui (build GUIs based on XML definitions).
 KDE uses '''well-known standards''' like [http://en.wikipedia.org/wiki/Udev UDev]) and [http://dbus.freedesktop.org D-Bus] (interprocess communication).
 === Compatibility & Integration ===
-The last major KDE release was KDE 4.0. All KDE 4.x versions are '''binary compatible''', i.e. software written for KDE 4.0 will be compatible with KDE 4.5 years later. As KDE is based on standards it is, for instance, easy to integrate applications with plain [http://todo-link-to-howto .desktop files].
+The last major KDE release was KDE 4.0. All KDE 4.x versions are '''binary compatible''', i.e. software written for KDE 4.0 will be compatible with KDE 4.11 years later. As KDE is based on standards it is, for instance, easy to integrate applications with plain [[Development/Tutorials/Desktop_File|.desktop files]].
 ==== Freedesktop.org & Portland ====
 As an ISV, your target is probably not only KDE but all Linux/UNIX desktops. This is made possible due to '''strong collaboration between KDE and other projects''' like [http://freedesktop.org freedesktop.org] which defines standards and software that helps integrating applications in all standard conform desktop environments.
-One of those projects is the [http://developer.kde.org/portland/ Portland project], which intends to develop a common set of Linux Desktop Programming Interfaces and Tools to allow applications to '''easily integrate''' with the free desktop configuration an end user has chosen to work with.
+One of those projects is the [http://en.wikipedia.org/wiki/Portland_Project Portland project], which intends to develop a common set of Linux Desktop Programming Interfaces and Tools to allow applications to '''easily integrate''' with the free desktop configuration an end user has chosen to work with.
 === Sub-Projects ===
@@ Line 33: / Line 33: @@
 ; KDE Pim
-: The goal of [http://pim.kde.org KDE Pim] (Personal information management) is to provide an application suite to manage personal information. This includes applications like an email client, a calender etc. The main result is '''KDE Kontact''', our personal information manager.
+: The goal of [http://community.kde.org/KDE_PIM KDE Pim] (Personal information management) is to provide an application suite to manage personal information. This includes applications like an email client, a calender etc. The main result is '''KDE Kontact''', our personal information manager.
 ; Calligra
-: [http://calligra.org KOffice] is an '''integrated office suite''' using KDE-technology and features a full set of applications which work together seamlessly to provide the best user experience possible. The office suite contains applications like Words, Tables, Stage, Krita, Kexi and many more.
+: [http://calligra.org Calligra] is an '''integrated office suite''' using KDE-technology and features a full set of applications which work together seamlessly to provide the best user experience possible. The office suite contains applications like Words, Tables, Stage, Krita, Kexi and many more.
 ; KDevelop
-: [http://kdevelop.kde.org KDevelop] is an '''Integrated Development Environment''' (IDE) for KDE. It supports language like C/C++ and Java and helps with rapid application development.
+: [http://kdevelop.org/ KDevelop] is an '''Integrated Development Environment''' (IDE) for KDE. It supports language like C/C++ and Java and helps with rapid application development.
 == Roadmap ==

@@ Line 1: / Line 1: @@
 == Tools ==
-*You can use the [http://subversion.tigris.org Subversion] version control system to access the KDE source repository.
+*You can use [http://git-scm.com/ Git] and [http://subversion.tigris.org Subversion] version control systems to access the KDE source repository.
-*There is a list of tools available, that can be used for developing KDE applications. These include low-level debuggers, as well as the KDevelop *Integrated Development Environment (IDE), and various design programs.
+*There is a list of [http://www.kde.org/applications/development/ tools available], that can be used for developing KDE applications. These include low-level debuggers, as well as the KDevelop *Integrated Development Environment (IDE), and various design programs.
-*You may also want to read the Compilation FAQ.
+*You may also want to read the [[Getting_Started/Build/KDE4|Build instructions]].
 *Several volumes of [[Development|development documentation]] will help you getting started with your development.
 == Libraries and Interfaces ==
-=== DCOP and D-Bus ===
+=== D-Bus ===
-* '''DCOP''' is the message bus built into KDE 3, that is used for inter-process communication (IPC) between different KDE applications. DCOP can be used in order to remotely control KDE applications from your own application or to provide scriptable interfaces for your own application.
+[http://www.freedesktop.org/wiki/Software/dbus D-Bus] is the message bus used in KDE 4, that is used for inter-process communication (IPC) between different KDE applications. D-Bus can be used in order to remotely control KDE applications from your own application or to provide scriptable interfaces for your own application. It has replaced [[Development/Architecture/DCOP|DCOP]] in the KDE 4 release.
-−
-*[http://developer.kde.org/documentation/tutorials/dot/dcopiface/dcop-interface.html Creating a DCOP Interface] <br />''This tutorial shows you how to create a DCOP interface to a KDE application.''
-*[http://www-106.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP]<br />''IBM DeveloperWorks tutorial, shows how to use kdcop and dcop with several examples such as instantly messaging a contact in kopete when he comes online, and also how to create a simple DCOP-aware application.''
-D-Bus will be the message bus used in KDE 4.
 *[[Development/Tutorials#D-Bus|D-Bus Tutorials]]<br/>''This tutorials show what D-Bus is and how to use it.<br/>See also: [http://dbus.freedesktop.org/doc/dbus-tutorial.html D-Bus tutorial] at freedesktop.org.''
 === KIO-Slaves ===
 KDE is network transparent. This means that each application can access files via many network protocols just as if they were stored locally. There exist access modules (KIO-Slaves) for Samba (Windows Shares), HTTP, FTP and many other protocols.
-*[http://developer.kde.org/documentation/design/kde/ioslaves/index.html Using IOSlaves]<br />''IOSlaves are the subprocesses KDE uses to fetch remote files without blocking the user interface. This document discusses how they work and how to use them. (Somewhat dated, but might still be useful).''
+*[[Development/Tutorials#kioslaves|Using KIO Slaves]]<br />''KIO Slaves are the subprocesses KDE uses to fetch remote files without blocking the user interface. This document discusses how they work and how to use them.''
 === Portland: xdg-utils and DAPI ===
+KDE actively supports [http://en.wikipedia.org/wiki/Portland_Project The Portland Project] aiming at making cross-desktop application development easier. For more information on this fairly young project, please refer to [http://portland.freedesktop.org/xdg-utils-1.0/ The Portland Project's] website hosted on [http://www.freedesktop.org Freedesktop.org].
-KDE actively supports [http://developer.kde.org/portland/ The Portland Project] aiming at making cross-desktop application development easier. For more information on this fairly young project, please refer to [http://portland.freedesktop.org The Portland Project's] website hosted on [http://www.freedesktop.org Freedesktop.org].

@@ Line 12: / Line 12: @@
 If you need guaranteed response times and business level support, there are several options to chose from:
-Nokia provides [http://qt.nokia.com/support commercial support] for their [http://qt.nokia.com/ Qt-Toolkit], on which KDE is based.
+Digia provides [http://qt.digia.com/Support/ commercial support] for their [http://qt.digia.com/ Qt-Toolkit], on which KDE is based.
 A list of companies supporting KDE can be found in KDEs [http://enterprise.kde.org/bizdir/ Business Directory].
 [[Category:ISV]]

@@ Line 1: / Line 1: @@
 This page intends to help '''Independent Software Vendors''' (ISVs) understanding the background of the KDE Roadmap.
 == KDE development ==
-The current KDE development concentrates on KDE 4, which will be a major release. It will include several new features as well as new APIs and frameworks and therefore will break the API compatibility. However, at the same time there are several efforts in the community making porting apps to KDE 4 quite easy.
+The current KDE development concentrates on both KDE Software Compilation 4, which is current major release and KDE Frameworks 5, which will be a set of high-level components for applications to use.
-The Roadmap of KDE 4 is divided into the [[Schedules/KDE4/4.5_Release_Schedule|Release Schedule]] and the [[Schedules/KDE4/4.5_Feature_Plan|Feature Plan]].
+The Roadmap of KDE Software Compilation 4 is divided into the [[Schedules/KDE4/4.11_Release_Schedule|Release Schedule]] and the [[Schedules/KDE4/4.11_Feature_Plan|Feature Plan]]. And KDE Frameworks 5 on going efforts tracked as [http://community.kde.org/Frameworks/Epics Epics].
 == Sub-projects ==
 Some KDE sub-projects have their own roadmaps:
 * [http://calligra.org Calligra] - a free, integrated office suite for KDE
 [[Category:ISV]]