KDE Core/Platform 11/Developer Story: Difference between revisions
< KDE Core | Platform 11
Created page with '* Compiling KDE, getting dependencies is difficult * Setting up latest stuff is painfull (e.g. Plasma Active) * Getting trunk development is hard * Providing dependencies is a di...' |
No edit summary |
||
| Line 1: | Line 1: | ||
== Issues == | |||
* Compiling KDE, getting dependencies is difficult | * Compiling KDE, getting dependencies is difficult | ||
* Setting up latest stuff is painfull (e.g. Plasma Active) | * Setting up latest stuff is painfull (e.g. Plasma Active) | ||
| Line 10: | Line 12: | ||
* Developing kioslaves or other stuff which needs to be installed is tricky, requires local environment paths setup or root to install modules | * Developing kioslaves or other stuff which needs to be installed is tricky, requires local environment paths setup or root to install modules | ||
* Two different target groups: People working on KDE itself, libraries, core applications, which need development versions of libraries. Second group: application developer who work with stable release versions of libraries, 3rd party developers | * Two different target groups: People working on KDE itself, libraries, core applications, which need development versions of libraries. Second group: application developer who work with stable release versions of libraries, 3rd party developers | ||
* Documentation is hard to find | |||
== Target groups == | |||
* Newcomers | |||
** New applications, kioslaves, plasmoids | |||
** Modifiy existing applications and other componentns | |||
* Develop KDE platform | |||
* Develop KDE frameworks | |||
* Qt-only developers | |||
== Tools == | |||
* Plasmate for Plasmoid development | |||
* KDevelop for C++ development | |||
* kde-examples git repo, integrate it with KDevelop, add metadata | |||
* New user dashboard in KDevelop, guiding user. Templates have to be maintained, examples, can't be adapted. | |||
* AbstractItemMode test from Qt examples | |||
* Tools for testing kioslaves, kded modules, Akonadi agents | |||
== Examples == | |||
=== Apple developer documentation === | |||
* Front page: What do you want to develop? (Could be our Techbase start page) | |||
* Framework is not that easy, but documentation is very targeted and makes it easy (Qt documentation is still better) | |||
Revision as of 15:47, 3 June 2011
Issues
- Compiling KDE, getting dependencies is difficult
- Setting up latest stuff is painfull (e.g. Plasma Active)
- Getting trunk development is hard
- Providing dependencies is a distribution's problem
- kdesourcebuild is more and more required
- Redmine should provide the dependencies
- Guides for all distributions how to build KDE are outdated
- Standard KDE way to access packages, using distribution-specific backends
- Two problems: Getting packages, setting up development environment
- Developing kioslaves or other stuff which needs to be installed is tricky, requires local environment paths setup or root to install modules
- Two different target groups: People working on KDE itself, libraries, core applications, which need development versions of libraries. Second group: application developer who work with stable release versions of libraries, 3rd party developers
- Documentation is hard to find
Target groups
- Newcomers
- New applications, kioslaves, plasmoids
- Modifiy existing applications and other componentns
- Develop KDE platform
- Develop KDE frameworks
- Qt-only developers
Tools
- Plasmate for Plasmoid development
- KDevelop for C++ development
- kde-examples git repo, integrate it with KDevelop, add metadata
- New user dashboard in KDevelop, guiding user. Templates have to be maintained, examples, can't be adapted.
- AbstractItemMode test from Qt examples
- Tools for testing kioslaves, kded modules, Akonadi agents
Examples
Apple developer documentation
- Front page: What do you want to develop? (Could be our Techbase start page)
- Framework is not that easy, but documentation is very targeted and makes it easy (Qt documentation is still better)