<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello there<br>
<br>
First a few words about myself: My name is Simon Wächter and I work
as a software developer for an IT company in Switzerland. I use
KDevelop for my daily work and my own projects. I want to contribute
to the KDevelop project because I think that KDevelop is an awesome
IDE and helps me to reach a better workflow.<br>
<br>
So now about the real content of this email: Because I use KDevelop
for my daily work and as a starting point for developing KDE
applications, I came in touch with the KDE project templates,
provided by the KDevelop and KAppTemplate project. Sadly, I
encountered a few "problems" with these templates. I can split these
problems into two categories:<br>
<br>
1.) Smaller problems<br>
<ul>
<li>Some KAppTemplate templates contain misleading variable names,
trailing whitespaces, commented lines etc. I asked Anne-Marie
Mahfouf from the KAppTemplate project to fix/improve these
problems and she gave me her ok</li>
<li>The KDevelop Qt project templates are also improvable, so I
talked with Sven Brauch (scummos) about the situation. The idea
is that I improve these templates the following week<br>
</li>
</ul>
2.) Bigger KAppTemplate problem<br>
<ul>
<li>KAppTemplate contains several interesting templates. The
problem is, that the package is just a suggestion for KDevelop
(At least in Debian). This means, many KDevelop users don't know
about this package. This is especially bad for new developer
that want to develop a Qt/KDE application. I also had this
problem and was quite happy that there were some examples
(Beside the techbase tutorials)<br>
</li>
</ul>
<p>So my questions is: Is there a way (or a need) to set the
KAppTemplate package as a requirement for KDevelop ? This would
result in the following advantages/disadvantages:<br>
</p>
<p>Advantages<br>
</p>
<ul>
<li>Move the KDevelop Qt plugins to the KAppTemplate project. This
would simplify the KDevelop packages. KAppTemplate would serve
as a real provider for all project templates</li>
<li>KAppTemplate could contain a sample KDevelop/KDevPlatform
plugin</li>
<li>More people know about the different project templates in
KDevelop. KAppTemplate provides an application, but I don't know
anybody that uses this application<br>
</li>
</ul>
<p>Disadvantages<br>
</p>
<ul>
<li>Higher dependency of the KDevelop package. It also needs some
arrangement with the distro packager<br>
</li>
</ul>
<p><br>
As a conclusion, this would really increase the effect of the
project templates - but needs some work. I am willing to improve
the the KDevelop/KAppTemplate project templates and move them to
the KAppTemplate project.<br>
<br>
</p>
<p>Please let me know about your personal thoughts about this
situation. Maybe it's just a bad idea, maybe something
interesting. Also, if there are some other (smaller) things to do,
as a starting point, please write an email or send a message via
IRC to swaechter.<br>
<br>
</p>
Bets regards,<br>
Simon Wächter<br>
</body>
</html>