You are on page 1of 3

UI frameworks

platform price longevity performance graphics looks development bad sides my experience

WPF ( NET FRAMEWORK)


NET Framework windows ( Vista and WIN 7) free since 2006 can be slower than others cause of heavyweight elements though drawing faster natively uses Direct3d (best for windows) best choise for windows (animation , style etc), need to write wrapper between c++ and CLI (C#/Vb,net) have (half , mvvm pattern-yes)

RESULTS platform price longevity graphics and look performance development time experience best choise for product

QT equal QT WPF Mfc 1)Winforms 2)WPF

QT
Cross platform free (non commercial version) since 1992 fast uses opengl good (animation , styles ,etc) need to learn qt not got

MFC
Windows free
1992-1993

faster ( after WIN32 API) uses gdi , direct can be used ( hard task) for own controls normal windows (winapi looks and features) need 2 learn MFC,MFC headache , bad designed UI not got

cross platform can be decline cause of destkop market mostly occupied by windows Qt got commercial version too WPF(xaml) can be killed by new windows toy (html5/jscript) .Wpf killed win forms , win forms killed Mfc , MFc killed raw win32 AP can be declined cause of product sensitivity to look MFC , more time will go to MFC itself than its (UI's) looks , for me it be better use win32 api than mfc

WIN FORMS (NET FRAME)

Net framework free 2002 good use gdi , direct can be used (hard task) normal windows (winapi looks and features) need to write wrapper between c++ and CLI (C#/Vb,net) have

d win forms , win forms killed Mfc , MFc killed raw win32 API

e better use win32 api than mfc

You might also like