On Friday, August 12, 2011 16:22:08 Mark wrote: > An example. Right now I've written a small application in QML and C++for > managing todo items. In QML i display everything, apply fancyeffects and > such. In C++ i manage the data model and fill it from anexternal source. The > questions i have here is what is "the right"approach these days for making > an application that in time could betargeted for KDE SC inclusion? Note: the
you can use QWidget or QML and that decision will not likely affect any decisions for inclusion into a larger KDE release and definitely not affect whether it can be hosted in KDE's infrastructure (git, etc.) what matters is whether or not you are using KDE libraries, Qt, etc... for some applications, QML will make a lot of sense. for others, QWidget will remain the way to go as QML still isn't quite "there" yet for all possible forms of user interface. eventually, perhaps; if it continues to mature, grow and get developer support, i'd say even "probably". but even then, applications that use QWidget will not be "wrong" or be forced to port to QML. an application that is featureful and usable, elegant and useful ... that's all one can ask for as a user. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks
signature.asc
Description: This is a digitally signed message part.
