<div class="gmail_quote">On Sun, Oct 31, 2010 at 1:50 AM, Cornelius Schumacher <span dir="ltr"><<a href="mailto:schumacher@kde.org">schumacher@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
</div>KDE would still create great applications based on Qt, just as we do now, but<br>
without the additional layering of the KDE libraries on top of Qt.<br></blockquote><div><br> <snip></div><div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
KDE is much more than the libraries, actually if KDE would be about libraries<br>
already now nobody would be interested anymore. KDE is community, and a<br>
community creating great software for end-users. We have tons of applications<br>
people love to use, and a community who loves to create them. How many<br>
libraries they use, and how the stack is layered doesn't really matter, does<br>
it? For technical details, yes, but there actually maintaining our platform as<br>
integral part of Qt seems advantageous to having a separate layer, which is<br>
hard to sell, sometimes hard to use, and very hard to maintain.<br>
<br>
The KDE community would still do the same as now, the differentiating factor<br>
would still be creating great software for end-users. If Qt would have<br>
provided everything we needed we wouldn't have created kdelibs. Assuming the<br>
obstacles we have seen and still see in actively being part of Qt can be<br>
removed, we wouldn't have a strong need for our own special platform, would<br>
we?<br></blockquote><div><br></div></div>So basically, what would convince 3rd party developers<br>(Qt developers, Windows developers, iOS/Android developers)<br>to write KDE apps? Better yet, what would now constitute being<br>
a "KDE app"? Platform integration and consistency? Only on<br>desktops/netbooks perhaps. On mobile, we'd have to follow<br>*their* (Maemo, MeeGo, WM) platform. Why not just call the app<br>a Qt app then? Again, this is from an interested 3rd party<br>
developer POV. Established KDE SC apps would most<br>probably keep the same brand.<br><br>True that KDE is much more than the libraries. But aren't those<br>libraries also an important part of what makes KDE? I mean, if<br>
developers decided to make KDE apps, isn't it sometimes<br>because KDE libraries rock?<br><br><br>-- <br>Regards,<br><br>Juan Carlos Torres<br>Jucato<br><br>