Re: It is time for me to take a decision.
Re: It is time for me to take a decision.
- Subject: Re: It is time for me to take a decision.
- From: "Simon Stapleton" <email@hidden>
- Date: Wed, 08 Aug 2001 09:31:28 +0100
>
Subject: It is time for me to take a decision.
>
From: Bertrand Mansion <email@hidden>
>
To: <email@hidden>
>
<snip>
>
I have seen that TrollTech made a beta version of Qt available
>
yesterday on their site. I had a look at it, it seems slower than
>
Cocoa and it is not really Aqua but it seems to be quite easy to
>
port the code to Windows (or Linux). How does Cocoa compare to Qt
>
in terms of productivity (development time), features and
>
portability ?
>
>
Thanks for your replies.
>
>
Bertrand Mansion
Having done some Qt development myself, I'd say that Cocoa is way more
productive. Really. By about 50%, and that's as a bit of a newbie to
both the framework itself and to Objective-C.
Features-wise, there's nothing I found in Qt that I'd give up Cocoa for.
The Internationalisation bits of Cocoa, though - Wow! And the tools -
ObjectAlloc and ` set NSZombieEnabled YES` are absolutely awesome.
Portability is a bit of an issue, though. Doesn't bother me too much, as
I'm developing for MacOSX only (and possibly GNUStep in the future). If
you need Windows support, you might as well forget Cocoa. Although it
_might_ be possible to write your model code in Objective-C using the
GNUStep Foundationkit code, and code up view and controllers using C or
C++ under Windows (but that's a guess, and the result is hardly likely to
be pretty).
Another toolkit you might want to look at is Gtk, which has the benefits
of not being C++ and being nice and easy to code for (Although I don't
think there's a native MacOS/MacOSX port of it) and having bindings for
almost every conceivable language.
But none of 'em touch Cocoa.
Simon
--
If the answer isn't obvious, the question is a distraction. Go find an
easier question.
This message was sent by Easymail -
http://www.easynet.co.uk/