Hello Andre,
On woensdag, november 14, 2001, at 10:33 , Andre Weinand wrote:
(It would sure be more natural to port SWT to Carbon...
Yes, the Carbon event model is a good fit to SWT because its similar
to the Windows API.
Because Carbon is a C api as is the lowest level Windows widget API?
but then, of course, you don't get Aqua...)
No, you get Aqua with Carbon on MacOS X, but you loose some of the
niceties of Cocoa (like really nice looking antialiased text).
Microsoft and many other companies are porting their apps to Carbon
only, not to Cocoa!
And its not easy to spot the difference to Cocoa apps!
I mainly developed in Java so far. Didn't do any C/C++ programming on
any other platform I used. This also means that I'm not familiar with
the path that Apple takes concerning their libraries. Correct me if I'm
wrong, but isn't Carbon a temporary (even long term) migration path for
Classic to OS X conversion? My idea of the whole situation is that
Apple is pushing developers to go the Cocoa way and only to use Carbon
for a first port of an app to OS X and then start mixing Carbon with
Cocoa, finally resulting in a pure Cocoa app. If this is the case, I
would not like to do a binding to Carbon.
