We're looking for developers to interview about their migration experience
-
Have you migrated or are you migrating from Qt Widgets to Qt Quick? Please book a short interview with us and help us improve Qt. https://outlook.office.com/book/ProductSpecialists@qt.io/?ismsaljsauthenabled
-
A Axel Spoerl pinned this topic
-
Hi,
You might also want to reach KDE folks since they have done quite a lot of work around that as well.
-
Hi,
You might also want to reach KDE folks since they have done quite a lot of work around that as well.
@SGaist Absolutely :) We're just starting small here since summer break is upon us any day now.
-
When I first saw this post a few days back, it was non-obvious to me that the request for interview from was from Qt Company.
You might want to make that more clear.
I thought it was coming from a team that specializes in Qt consulting, and I thought to myself "hmmm... I don't know if other teams are going to want to share their learnings with a competing consulting team..." 😅
Maybe even start a new thread? In case others had the same initial impression that I did?
-
Have you migrated or are you migrating from Qt Widgets to Qt Quick? Please book a short interview with us and help us improve Qt. https://outlook.office.com/book/ProductSpecialists@qt.io/?ismsaljsauthenabled
@Benedikte.holm said in We're looking for developers to interview about their migration experience:
Have you migrated or are you migrating from Qt Widgets to Qt Quick? Please book a short interview with us and help us improve Qt. https://outlook.office.com/book/ProductSpecialists@qt.io/?ismsaljsauthenabled
@KH-219Design it's all in the link ! :-D
But I agree, something more explicit in the post would likely trigger less confusion :-)
-
When I first saw this post a few days back, it was non-obvious to me that the request for interview from was from Qt Company.
You might want to make that more clear.
I thought it was coming from a team that specializes in Qt consulting, and I thought to myself "hmmm... I don't know if other teams are going to want to share their learnings with a competing consulting team..." 😅
Maybe even start a new thread? In case others had the same initial impression that I did?
@KH-219Design: similar here, some explanation who is "we" or at least a qt.io link may help.
Anyway: Why the interest in porting "within" Qt, not "to" Qt? And if "within", why not target the smaller and faster solution?
-
@KH-219Design: similar here, some explanation who is "we" or at least a qt.io link may help.
Anyway: Why the interest in porting "within" Qt, not "to" Qt? And if "within", why not target the smaller and faster solution?
@A-Former-User said in We're looking for developers to interview about their migration experience:
@KH-219Design: similar here, some explanation who is "we" or at least a qt.io link may help.
Anyway: Why the interest in porting "within" Qt, not "to" Qt? And if "within", why not target the smaller and faster solution?
Because the question was: from widgets to Qt Quick whatever the size of the application.
