[Qt-interest] QT and KDE code

[Pau Garcia i Quiles]

Hello,



On Tue, Mar 23, 2010 at 6:50 AM, M. Bashir Al-Noimi <mbnoimi at gmx.com> wrote:
> Hi,
>
> This point I wanted to know about since I migrated to kubuntu.
>
> Why KDE isn't completely cross platform just like Qt? although it inherited
> from many Qt classes (KDE applications in Windows are absolute disaster
> where Qt works smoothly in many platforms) !!!

KDE needs various services, such as DBus, which do not work that 100%
reliably (yet) on Windows. KDE on Windows (and Mac, and Haiku, etc)
works pretty well, though. What are the reasons you call it an
"absolute disaster"?

> Why portability of GTK -generally- is better than KDE specially by comparing
> to KDE3?

You are comparing apples to oranges here.

Gtk = equivalent to Qt
Gnome = equivalent to KDE

You can't compare Gtk to KDE.

That being said, I'd like Qt developers to consider KDElibs,
KDEPIMlibs and KOfficelibs as additional Qt modules, just like QtCore,
QtGui, etc. Those KDE modules are licensed LGPL, therefore they can be
used on closed-source applications.


> Sorry for obtrusion but I was looking for answers years ago but I couldn't
> get them.
>
> On 22/03/2010 10:20 م, Stephen Kelly wrote:
>
> Anatoly Burakov wrote:
>
>
>
> Hi all
>
> I was reading some mailing lists and articles about coding for KDE vs
> coding for QT. In that swarm of information the main idea i got was that
> KDE classes are basically QT classes with added functionality and names
> starting with K instead of Q. Does that mean that basically if i replace
> all Q's in class names in header files with K (when the corresponding
> class is available) the code will compile without any further
> modifications (provided i have included all the needed KDE headers of
> course)?
>
>
> That's not quite the point.
>
> The KDE development platform is written with Qt and consists of a lot of
> libraries and classes extending existing Qt functionality and adding new
> APIs not provided by Qt. These include APIs for writing games, educational
> software, personal information management (the bit that I do), as well as
> platform integration such as common dialogs, uniform configuration
> management, standard application data directory structures and more.
>
> The API docs for the KDE development platform are
>
> * http://api.kde.org/4.4-api/kdelibs-apidocs/
> * http://api.kde.org/4.4-api/kdepimlibs-apidocs/
>
> and there are tutorials here:
>
> http://techbase.kde.org/Development/Tutorials/
>
> Many KDE classes do inherit Qt classes and add functionality but that's the
> case with all software that uses Qt. Just using KTextEdit instead of
> QTextEdit won't make your application better unless you know why your using
> it. In the case of KTextEdit, the widget will automatically respect the
> system settings for mouse hiding for example, so it doesn't need to be
> configured per application.
>
> http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKTextEdit.html
>
> Best regards,
>
> Steve.
>
>
>
> Best regards,
> Anatoly
>
>
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
>
>
>
> --
> Best Regards
> Muhammad Bashir Al-Noimi
> My Blog: http://mbnoimi.net
>
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
>
>



-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)