[Development] QtQuick QtCS Sessions

Hausmann Simon Simon.Hausmann at digia.com
Wed Jun 25 17:24:01 CEST 2014


The done is referring to the fact that a binding to qsTr("...") does not result in the creation of a Javascript binding but is treated directly by the engine as translation. just like the jira report indicates, support for dynamic re-evaluation of such bindings is not implemented yet (and was never claimed as done).

Simon

  Opprinnelig melding
Fra: Thomas Senyk
Sendt: 17:13 onsdag 25. juni 2014
Til: development at qt-project.org
Emne: Re: [Development] QtQuick QtCS Sessions


On Friday, 13 June, 2014 23:07:08 Alan Alpert wrote:
> Here are the results and brief summaries of the 3 QtQuick related
> sessions, where we came up with some suggested new properties and
> types for QtQuick.
>
> Touch and Gestures:
> http://qt-project.org/groups/qt-contributors-summit-2014/wiki/QtCS14TouchAnd
> Gestures
>
> No real solution other than handling Mouse, Touch, and Gestures
> (system gestures, no gesture manager). Also looking into new grab
> transfer mechanisms in QtQuick, such as a MouseArea.priority property
> for automatic transfer.
>
> QtQuick:
> http://qt-project.org/groups/qt-contributors-summit-2014/wiki/QtCS14QtQuick
>
> Proposed new module, QtQmlGui (working title), which exposes non-core
> stuff to QML but can be shared between QtQuick and other modules (like
> Qt3D). Proposed new types, PolarPositioner, MouseRegion,
> TextContainer.
>
> Declarative QML:
> http://qt-project.org/groups/qt-contributors-summit-2014/wiki/QtCs14MoreDecl
> arative
>
> Proposed new property, deferredLoading, on Item, to solve the less
> dynamic uses of Loader. Proposed new element, StateChange, to allow
> more declarative state changing. Big solutions of pull bindings and a
> pragma strictly-declarative are a lot of work, unlikely to occur soon.

How is "Translation" "DONE"?

Just to make sure we talk about the same thing:

https://bugreports.qt-project.org/browse/QTBUG-15602

Affects version should be "all" I guess .. this is (was?) the same case for all
Qt versions and also QQuickView (quick2)

That's not solved .. is it?

>
> --
> Alan Alpert
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development



More information about the Development mailing list