Anyone switched from MFC to QT?

[Dan203]

I work as a developer for a company that currently sells a Windows only video editing application. We've recently been discussing the possibility of porting our program over to Mac. However our current program is written in C++/MFC, so porting it to Objective-C is no easy task.

I did a little research and I ran across a cross-platform API called QT which appears to be very similar to MFC, but allows cross platform deployment. This seems very appealing to us, but having never actually used QT I'm not 100% sure if it will meet all of our needs or not.

Has anyone here made the switch from MFC to QT? Any major pitfalls or experiences you'd care to share?

Also is anyone aware of the multimedia capabilities of QT? Right now we use most of our own code to open, demux and decode media files, but we do use some DirectX/DirectShow to do the final presentation. I read a little about the Phonon API included with QT, but it's not clear how customizable it is or if we'd be able to fit it into our processing chain. Does anyone here have any experience using QT/Phonon for a multimedia app? Any pitfalls or experiences you'd care to share on that front?

Thanks,
Dan

[OReubens]

1) Make sure you get the right licence of Qt. If you end up with the GPL one, you could be forced by court to make all of your sourcecode public (it's happened before).

2) Qt uses a different conceptual approach to the UI than MFC Document/View approach. Anything tightly bound to the UI will need rewrites.

3) I used Qt for a couple projects that needed crossplatform support, but I knew this from the start, I have no experience with actually converting an existing 'old' MFC project over to Qt.

4) the major pitfall is trying to solve issues "the MFC way" because you're used to doing it that way.

5) No idea about phonon.