Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate on QML #2

Open
Diadlo opened this issue Jan 30, 2017 · 4 comments
Open

Migrate on QML #2

Diadlo opened this issue Jan 30, 2017 · 4 comments

Comments

@Diadlo
Copy link
Member

Diadlo commented Jan 30, 2017

I'm not sure, that it's good idea. But we can start rewriting part of widgets into QML
http://doc.qt.io/qt-4.8/qml-integration.html

@Diadlo
Copy link
Member Author

Diadlo commented Feb 2, 2017

@sudden6 Do you agree with this and #1?

@antis81
Copy link

antis81 commented Feb 2, 2017

I would strongly advise to step away from that idea of mixing widget and qml code. However, if you want to try it, you might want to have a look into my fork (HEAD commit of branch qml) for reference on how to do that: antis81/qTox@017bdbc

The commit basically removes any QWidget related code - but you can easily just add the qml/qtquick module and start off with that…

@Diadlo
Copy link
Member Author

Diadlo commented Feb 2, 2017

@antis81 Thanks a lot

I would strongly advise to step away from that idea of mixing widget and qml code

Why? There is my arguments for mixing:

  1. I think QML -- is the future of Qt
  2. QML help to build better architecture (MVVM?)
  3. We can't drop support of current futures => we can't start from scratch
  4. We can't maintain (test, fix, rebase) one huge PR

@sudden6
Copy link
Member

sudden6 commented Feb 4, 2017

I agree with @Diadlo, we don't have the manpower to do a hard switch all at once, so we have to do it gradually, even if it takes longer. But it means our users will get continuous support during the whole process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants