You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Qt is an incredibly powerful, portable and easy to code for environment that has a bright future (unlike GTK+). By making a Qt 5 GUI we will make sure that:
a) XQF will be able to run on any platform supported by qt5 - this includes Windows, Mac and numerous mobile platforms.
b) We won't depend on GTK+ devs breaking API at their whim.
Porting heavily depends on splitting UI and core logic (#68).
The text was updated successfully, but these errors were encountered:
I am not really excited about this. Not only gtk is not dead or dying, but porting to qt mostly means an entirely different project. What would this fix exactly?
Aside from Qt being way more portable, widespread (is it me or people actually call GTK libgnome nowadays?) and having a stable API (unlike GTK3), I'd like to do it for some of my own coding practice.
And I'm pretty sure that once UI and core logic are separated we can build a GUI with any toolkit possible.
Qt is an incredibly powerful, portable and easy to code for environment that has a bright future (unlike GTK+). By making a Qt 5 GUI we will make sure that:
a) XQF will be able to run on any platform supported by qt5 - this includes Windows, Mac and numerous mobile platforms.
b) We won't depend on GTK+ devs breaking API at their whim.
Porting heavily depends on splitting UI and core logic (#68).
The text was updated successfully, but these errors were encountered: