Hello Jan,
JS> FireFox and Thunderbird are pretty damn good. There are differences
JS> ofcourse to make it more mac-like. Shortcuts using symbols, based on
JS> command instead of control or alt. Changed menu structure (preferences
JS> and quit under the application menu, instead of file and edit). The
JS> usage of sheets instead of modal dialogs. Things could be better, but
JS> none would require a massive rewrite, or needs the use of another
JS> toolkit. So, yes, you need different versions for mac/linux/win to make
JS> a decent gui app, but the differences aren't that major that you need to
JS> rewrite your entire application.
Yes they are pretty good. But this is exactly what i said. For example
you can find in the "mozilla/widget/src/mac" folder 85 files with 961
KB source code which is most of the mac GUI abstraction layer. I know that some
other programs (Komodo for example) uses the Mozilla framework, but it is
still developed around the needs of the Browser application. If they need
new features they will change the toolkit and they will do it at the
same time for each toolkit. This is different from the idea
of porting from one system to another with the help of a general
purpose toolkit and without #ifdef clauses.
JS> Allot of Java apps also integrate nicely. (for example Jedit). You need
JS> changes, you need to follow the mac hig to give a nice experience, but
JS> you don't need to rewrite it in either cocoa/carbon. It is easier to get
JS> things right if you use cocoa instead of something else, but it is not
JS> absolutely necessary for a nicely integrated mac application.
Sure you can do quite well. But thats not the point i'm talking about.
I talking about apps here that will have a chance to get accept at
http://store.apple.com/1-800-MY-APP...b71EuWEVpK/0.0.9.1.0.6.13.0.4.1.3.0.7.0.1.1.0
This is not easy because recommended software must confirm to the interface
guideslines (at least a few years ago they where very strict at this
point) - and of course you must pay a lot of money.