Re: Cross-Platform Windows plus Mac

["Followup-To:" header set to comp.sys.mac.programmer.help.]
On Tue, 23 Oct 2007 21:40:56 -0500, Michael Ash <mike@[EMAIL PROTECTED]
> wrote:
> In comp.sys.mac.programmer.help Steven Fisher <steve@[EMAIL PROTECTED]
> wrote:
>> In article <1193091951.878011@[EMAIL PROTECTED]
>,
>> Michael Ash <mike@[EMAIL PROTECTED]
> wrote:

[snip]

>> It also doesn't sup****t spell checking in edit fields yet, but I've
seen 
>> some evidence that may be coming soon.
>> 
>> At this point, I think I would use Qt4 to target a single platform. 
>> Project management alone is worth it: you maintain a simple text file 
>> (think Makefile, although it's much simpler) with a text editor instead

>> of an XML file that's manipulated with Xcode.
>
> A minor nitpick: Xcode project files aren't XML, they're old-style 
> OpenStep property lists. Doesn't make it any easier to edit with a text 
> editor though.
>
> How tightly are the Qt build tools tied to Qt? Seems like you ought to
be 
> able to use them to build native apps too, if you like them that much.

The 3 main build tools are qmake, uic and moc. qmake is a Makefile
generator that understands uic and moc requirements. It is not strictly
necessary, as other build systems sup****t Qt (notably cmake and bjam).
uic is the user interface compiler. It takes XML .ui files built with
Designer (Qt's equivalent of Interface Builder) and generates C++ code.
moc is the meta object compiler. Basically this parses your C++ class
defintions looking for a few special macros, and generates C++ code for
type information and message passing.
 
>> For me, it's that even now as is poor integration with C++. If I want
to 
>> cross platform business logic, it's going to be in C++. We're almost in

>> 2008, and exceptions can't be passed easily from C++ to the Objective C

>> UI code. That's a very big deal to me.
>
> You use Objective-C++ for the code that has to call into C++, and you
wrap 
> the C++ calls with exception handlers, just like you would do if the GUI

> code were C++. Seems no harder than it would be in something like Qt. Am
I 
> wrong?

No, I would imagine the Qt bindings are possible. PyQt has existed for a
while, Python bindings to Qt (I've never used it though).

A bientot
Paul