[Development] Repository request: qtpositioning

2021-10-07 Thread Ivan Solovev
Hi,

I'd like to request a new repository on codereview.qt-project.org.

Name: qt/qtpositioning
Description: Qt Positioning module
Responsible persons: Alex Blasche (alexander.blas...@qt.io) and Ivan Solovev 
(ivan.solo...@qt.io)

This is needed to ensure that QtLocation module development can be uncoupled 
from QtPositioning module packaging.
Currently enabling the building of the QtLocation module in the qtlocation.git 
repo cannot be done without automatically packaging QtLocation for the next Qt 
release.

Best regards,

Ivan Solovev
Senior Software Engineer

The Qt Company
Erich-Thilo-Str. 10 12489
Berlin, Germany

www.qt.io

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Formal voting procedure for Qt Project

2021-10-07 Thread Edward Welbourne
Lars Knoll (6 October 2021 15:33) wrote:
> * voting will be open for 7 days to give everybody enough time to react
> * The voting database will be deleted 2 weeks after voting ended

Suggested revision for the second:

* The voting database will be deleted 2 weeks after voting ended, unless
  the outcome is contested, in which case it shall be retained for as
  long as is needed to resolve disputes that can be answered by that
  database.

Note that if the outcome is contested for reasons not related to the
contents of the database (who voted, how many for which outcome) this
lets the two week schedule stand.

Eddy.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Qt 6.2 QQmlMetaType incompatibility

2021-10-07 Thread Ulf Hermann

Hi,


What part of the docs do you mean here?

https://doc.qt.io/qt-6/qqmlengine.html#QML_ANONYMOUS

"Declares the enclosing type to be available, but anonymous in QML.
The type cannot be created or used as property type, but when passed
from C++, it is recognized."

Thought that "property type" is supposed to be the type of a property
being exposed to QML ?


It means that you cannot declare a property of such type in QML, but you 
can still use a property of such type if it's declared in C++. I'll 
clarify the docs.


best regards,
Ulf
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Qt 6.2 QQmlMetaType incompatibility

2021-10-07 Thread Uwe Rathmann

Servus Ulf,


What part of the docs do you mean here?

https://doc.qt.io/qt-6/qqmlengine.html#QML_ANONYMOUS

"Declares the enclosing type to be available, but anonymous in QML.
The type cannot be created or used as property type, but when passed
from C++, it is recognized."

Thought that "property type" is supposed to be the type of a property
being exposed to QML ?

I can file a bug report if you agree, that the docs are wrong - or at least
misleading ?

You can very well have anonymous value types as C++-declared  > properties of other types. It may be that we're still missing some > 
bits and pieces for the creation from JS values to work. So far the > 
approach is only used by the QtQuick value types. Some of those are > 
indeed anonymous, but all of them happen to use the foreign/extended > 
hack. It should also work without that hack, though. Feel free to > open 
a bug report or submit a patch.
As QML_ANONYMOUS is only a macro for "Q_CLASSINFO("QML.Element", 
"anonymous")"
I was trying to identify, where "QML.Element" gets processed and didn't 
find something

beside code of the qmltyperegistrar tool.

I also read your additional reply as qmltyperegistrar being mandatory 
for my use case.


As my QSkinny project is currently used in pure C++ projects only I have 
to confess,
that I did not pay enough attention to the QML aspects and static type 
registration
( https://www.qt.io/blog/qml-type-registration-in-qt-5.15 ) should of 
course be the way to go.


Will do my homework.

Thanks,
Uwe




___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development