--===============1789003912==
Content-Type: multipart/alternative; 
	boundary="----=_Part_20980_2439516.1156610872532"

------=_Part_20980_2439516.1156610872532
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,
I'm kinda new to KDE/QT development so I have some questions (simple and
rookie questions, probably):

In looking to coded for K... apps (like Krecipes), I notice they use a
'hybrid' approach, using some K... classes and some QT classes. As far as I
can see, KDE and QT classes overlap sometimes. The notorious example:
QApplication vs. KApplication. As far as I discern from the documentation,
they do the same thing.

I thought of using QT classes all along (using QApplication instead of
KApplication), just because I want to learn QT and be able to apply it in
different apps in the future, not necessarily tied to KDE, using QT as a
replacement of the STL, kinda.  But then I started wondering in code and I
see a bunch of KDE classes that are really cool (KDebug, for example).

So, the questions:
a) Is it even possible to write a KDE application without using KDE classes?
Is it advisable? (probably not, right?) Is it a good idea at all?
b) If you want to use a hybrid approach, how do you decide if you're using a
KDE or QT class in a specific instance? For example, how do you decide
between QApplication and KApplication or KPushButton and QPushButton? Are
they 100% compatible, in general? Does it matter if I use the K or Q class?

Thanks.
Jerry.

-- 
/(bb|[^b]{2})/ <- The question

------=_Part_20980_2439516.1156610872532
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,<br>I'm kinda new to KDE/QT development so I have some questions (simple and rookie questions, probably):<br>
<br>
In looking to coded for K... apps (like Krecipes), I notice they use a 'hybrid' approach, using some K... classes and some
QT classes. As far as I can see, KDE and QT classes overlap sometimes.
The notorious example: QApplication vs. KApplication. As far as I
discern from the documentation, they do the same thing. <br>
<br>
I thought of using QT classes all along (using QApplication instead of
KApplication), just because I want to learn QT and be able to apply it
in different apps in the future, not necessarily tied to KDE, using QT
as a replacement of the STL, kinda.&nbsp; But then I started wondering in code and I see a bunch of KDE classes that are really cool
(KDebug, for example). <br>
<br>
So, the questions: <br>
a) Is it even possible to write a KDE application without using KDE classes? Is it advisable? (probably not, right?) Is it a good idea at all?<br>
b) If you want to use a hybrid approach, how do you decide if you're
using a KDE or QT class in a specific instance? For example, how do you
decide between QApplication and KApplication or KPushButton and
QPushButton? Are they 100% compatible, in general? Does it matter if I
use the K or Q class?<br>
<br>
Thanks.<br>
Jerry.<br clear="all"><br>-- <br>/(bb|[^b]{2})/ &lt;- The question

------=_Part_20980_2439516.1156610872532--

--===============1789003912==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============1789003912==--