KDevelop 4/Vision
From KDevelop
Contents |
[edit] KDevelop 4 Vision and Goals
This is an attempt by mattr to define in words what the goals and vision for KDevelop 4 are in his mind. The reason for this is to provide information to current and perspective developers about what the KDevelop team as a whole is working towards.
[edit] Vision
[edit] Integration
KDevelop is an IDE, which means Integrated Development Environment. The key word there is integration. When we integrate something into KDevelop, it needs to truly be integrated. That means things need to feel less like KDevelop is just a shell around Kate and we decided to tack on these extra things and more like we put some thought and design into how we wanted to integrate something into KDevelop.
[edit] Development
KDevelop is first and foremost, a development tool. And even though it is a developer's tool, we need to make it easy for both novice developers and coding masters to use. We also need to make it easy and fun to hack on for those of us that hack on it.
[edit] Environment
KDevelop is an integrated environment. This means that our goal should be to provide features in KDevelop that keep a user away from the konsole. Does this mean that the konsole part should go away? Not at all. But keep in mind that on two of our three target platforms (in this case, Windows and Mac) that the terminal is not a common device used by developers. Therefore, we should do whatever we can to provide a feature set that give developers what they need so that they don't have to use the terminal.
[edit] Goals
Set of core languages:
- C/C++
- C#
- Ruby
- Java
Version control support:
- Subversion
- Perforce
Build systems:
- GNU Autotools
- CMake
- QMake
Make it easy for other developers to provide plugins through the use of API documentation and user documentation