We went down the Qml road for 3D CAD application and it's doable, you only need to make a good 3D render to texture view elements until the 3D can catch up. With Canvas and render to a texture I don't see any real limitation. Maybe the boilers plate is increase compare to QWidgets but still doable.
The speed at which you design and create GUI element with animation is great with Qml. My main complain is more around all the small function you have to create (matrix4x4, quaternion exposition have so few method for example, you need to rotate a vector3d with a quaternion and the like, there is a lot of missing pieces, that will probably make it one day). You can take a look at our web site: http://bodycad.com/en/a-new-way-to-prep/software We did quiet a few super component with Qml like puck menu, dynmic side drawer that expend with mouse hover where you can store any Qml Items and auto resize itself and can be anchors on any side of the screen, 2D/3D length/angles measurements with Canvas. A lot of the UI element are draggable and/or drag n drop between 2D/3D elements (required us to make some event convertion). If we ever need to port one of our application to mobile, we will be able to do it. If they ever make Qml for the web bridge that would be awsome for us. I don't say all desktop application should be done into Qml, but just that it's doable into Qml no matter the application you have. Jerome [image: bodycad] <https://www.bodycad.com/> Jerome Godbout Software Developer 2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7 T: +1 418 527-1388 E: jer...@bodycad.com www.bodycad.com The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Le contenu de ce message et les pièces jointes sont destinés uniquement pour le(s) destinataire(s) et peuvent contenir des informations confidentielles et / ou privilégiées qui peuvent être protégées légalement contre toute divulgation. Si vous n'êtes pas le destinataire de ce message ou son agent, ou si ce message vous a été adressé par erreur, s’il vous plaît avertir immédiatement l'expéditeur par courriel de réponse, puis supprimer ce message et les pièces jointes. Si vous n'êtes pas le destinataire prévu, vous êtes par la présente informé que toute utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces jointes est strictement interdit. On Wed, May 17, 2017 at 10:04 AM, william.croc...@analog.com < william.croc...@analog.com> wrote: > > >> It's not tomorrow that you will design an airplane on an Android >> tablet, control the CERN particle accelerator from a Windows phone or >> monitor the country electricity distribution network grid from an >> Apple iPod. >> >> > Well said! Hear! Hear! > Bill > > (Oh, damn. Where was that closest Starbucks again.) > > > Chris >> >> [1] blog.qt.io/blog/2017/01/19/should-you-be-using-qgraphicsview/ >> >> >>> Cheers, >>> Oliver >>> >>> _______________________________________________ >>> Interest mailing list >>> Interest@qt-project.org >>> http://lists.qt-project.org/mailman/listinfo/interest >>> >>> _______________________________________________ >> Interest mailing list >> Interest@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/interest >> >> _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
