THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 06/08/2012 at 11:43, xxxxxxxx wrote:
Originally posted by xxxxxxxx
It's more than cross platform issues Steve.There's also all of these different versions of the mac OS flying around now. And each one has it's own limits of which version of Xcode it supports that Maxon has to deal with.It seems like a total nightmare to me.I think the reason AutoDesk decided to use QT is because they weren't already years deep in mac support like Maxon is. So they had the luxury of starting fresh with a true cross platform option. Maxon would have to change their whole way of thinking to do the same. Which probably seems like a huge mountain to climb.But when you look at how much trouble it is to deal with the macs changing their OS constantly. While also trying to support both platforms. Sometimes climbing the mountain ends up being the best long term decision.Then there's the issue of long time mac&PC; plugin developers who might balk at changing to a new way of writing code to deal with. Even though it would make everyone's life simpler in the long run. I would be surprised if the developers don't at least talk about this subject in their meetings.I suppose they couldn't comment about it. Even if they do talk about it.-ScottA
- Using our own cross-platform code allowed us release 64 bit more than one year earlier then we could have with QT
- It avoided the performance problems of QT (see Maya forums, if you're interested in user comments about the change of their GUI kit)
- If it is necessary to adapt GUI code due to OS changes, we know where to do it. If you use 3rd party code, it's a lot more work (with code you don't know that good) or you've to rely on other people fixing it (first Trolltech, then Nokia and in the future whoever will buy it, after Nokia is killing QT development - if anyone does...)
- Adapting QT would require not only a rewrite in Cinema's core, but also in 3rd party plugins
From my pov: Apart from having an app to design a GUI, there isn't much to gain when using QT. It solves problems we don't have, and it creates problems we haven't either.
Regarding Eclipse: There are two problems with just one IDE creating the stuff for all platforms.
1. You don't have the SDK libs and frameworks. E.g. if you're on Windows and even if the compiler would be capable to generate the correct binary format for executable and dynamic libs for OS X, without the linked frameworks (and their OS specific include files) you can't create them.
2. You can't use the best available compilers (ICC does work with VS only on Windows; the Clang/LLVM tool chain isn't available in Eclipse on the Mac) & debuggers; I don't expect most people to be able to create their custom build of eclipse with a custom build of LLVM to solve that.
Best regards,
Wilfried