I guess it depends on what software you do, if you target open reusable library, go with minimal number so as many version as possible can be used along with it.
If you do proprietary software and you alone control the source, go with the latest version as it will likely be more future proof and you will test less version in the end. I think the version that match Qt version would have been nice, but again QtQuick.Controls 1.x and 2.x show another story, you still can use the old way and the new way at the same time. But there again a new name would have works too. The version are particularly useful if dealing with Loader/Instanciator and external inputs that may have a version too. You can create a component with the right version and instantiate it to generate the proper view/processing. [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 Thu, Apr 13, 2017 at 4:12 AM, Viktor Engelmann <viktor.engelm...@qt.io> wrote: > The _version_ only affects which properties/methods are visible, so you > should always go for the minimal version that has all the interfaces you > use. > > say there is a qml class foo. in version 1.0 it has method bar, in 1.1 it > also has method ham and in 1.2 method eggs. > > if you import 1.2 although you only use bar and ham, it won't run on > systems that only have version 1.1 although it could. On systems that have > 1.2, you still have all the bugfixes that went into bar and ham between 1.1 > and 1.2 - again, the version only affects which parts of the interface are > visible. > > Viktor > p.s. I don't think that other languages "get away without having a > version". In other languages, you only push the trouble onto someone else. > So you have for example a windows 9x, a win NT, a win vista,... version of > your program and the customer must know which windows version he has (plus > you need to bundle all the non-OS libraries you use, polluting the > customers hard drive). And that approach only works for OSes that have a > very limited set of releases, which isn't the case for linux. > On linux, it's the packagers' job to know which version of which library > has which interface. That's why you have versioned dependencies in .deb > packages for example (and that makes things a lot more difficult without > any benefit). > > > > On 13.04.2017 08:48, Elvis Stansvik wrote: > > Den 13 apr. 2017 2:52 fm skrev "Jason H" <jh...@gmx.com>: > > > > > > > > > Sent: Wednesday, April 12, 2017 at 12:05 PM > > > From: "VStevenP via Interest" <interest@qt-project.org> > > > To: interest@qt-project.org > > > Subject: [Interest] QtQuick import question > > > > > > When importing a QtQuick version, is it best to import the most recent > version, or the minimum version that supports the features (properties, > etc.) of the components being used? > > > > I've asked this before as well, I don't remember getting an answer. I go > with whatever the documentation for the Qt version I'm using says, because > there is no substantive table of what is in what version. > > > > I'd love to use min version, but sometimes you just don't know. Also, > there is no clear reason (that I can tell) to have a version. I think it > would be nightmareish if Qt backeded every version of QML import that is > actually listed in my app, so I assume the version is min version. Every > other language gets away without having a version, I wonder why Qt requires > it in the source? > > +10, I would love if in our Quick application, we could just say "this is > the minimum Qt version we support" and avoid having to specify cryptic > versions on each QML import. > > The lack of docs on when/in which Qt version a particular QML version of a > certain module was added doesn't help. > > Elvis > > > > > > > > > > > _______________________________________________ > > Interest mailing list > > Interest@qt-project.org > > http://lists.qt-project.org/mailman/listinfo/interest > > > _______________________________________________ > Interest mailing > listInterest@qt-project.orghttp://lists.qt-project.org/mailman/listinfo/interest > > > -- > > Viktor Engelmann > Software Engineer > > The Qt Company GmbH > Rudower Chaussee 13 > D-12489 Berlin > viktor.engelm...@qt.io+49 151 26784521 <+49%201512%206784521> > http://qt.io > Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho > Sitz der Gesellschaft: Berlin > Registergericht: Amtsgericht Charlottenburg, HRB 144331 B > > > _______________________________________________ > 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
