Re: [Interest] [Development] "Examples and demos" component in Jira (QTBUG project)

2020-09-11 Thread Kai Köhne
> -Ursprüngliche Nachricht-
> Von: Development  Im Auftrag von
> Santtu Ahonen
> Betreff: Re: [Development] "Examples and demos" component in Jira (QTBUG
> project)
> 
> Retiring the component would be a massive loss of data and alignment
> between projects. This before retirement proposal we should have a plan on
> how to manage this area properly. Granted, this is a messy area without clear
> ownership thus we can argue on what team / who should be the owner of the
> component.
>
> In fact the component combines two different use cases (Examples and
> Demos) and it is not helping that different Qt projects have differently named
> components for the same overall use case.

Well, then I'm wondering what the loss of alignment is 

> In Product Management we use quite a lot of these Demo components to
> track demos we need to create for specific customer verticals or events,
> marketing needs etc. Our master board is here:
> https://bugreports.qt.io/secure/RapidBoard.jspa?rapidView=83

The filter query for this very board is: 

component in (Demo, Demos, "Demo Design (internal)", "Demo Implementation 
(internal)", DemosAndPresentations, "Examples and Demos", Examples) OR labels 
in (example, examples, Examples)

So the fix for QTBUG is easy: Tag the JIRA issues you're interested in in QTBUG 
with 'example' label. Or even better, extend the query and use a more 
descriptive label like 'pm_demo'. Because I actually doubt that the various 
bugs we have currently reported against the 'Examples and Demos' component are 
really regularly reviewed by PM.

> If we touch this area I'd be welcoming on splitting the Examples and Demos in
> to two separate use cases but this is not an issue for just QTBUG project, 
> this
> goes across the board and over several projects. 

If we ever get properly maintained demos into QTBUG back (with clear 
responsibility) then I'm certainly not against it.

Regards

Kai
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] QML/C++ interaction in Qt6

2020-09-11 Thread Jérôme Godbout
Will Qt 6 still use the Meta information to access Qml properties or it rely 
more on compiled C++ now? I guess it still the same as before.
Is the properties declaration of Qt for MCU (Qml lite or soemthign like that) 
be available (syntax wise, template)? That would leverage soo much redundent 
code to expose properties with get/set and changed event. That will be a slim 
fast for code that expose to Qml (to Meta data actually, Qml use the meta data) 
and maybe event make that layer disapear one day.

-Original Message-
From: Interest  On Behalf Of Ulf Hermann
Sent: September 11, 2020 6:20 AM
To: interest@qt-project.org
Subject: Re: [Interest] QML/C++ interaction in Qt6

> - Allow QML to access public properties of classes, even if these 
> public properties do not use `Q_PROPERTY`
> - Allow QML access to classes that are neither `QObject`, nor 
> `QGadget`

This is not planned right now. Note that we rely on moc to generate the class 
descriptions that QML uses. Therefore, we need constructs like Q_OBJECT, 
Q_GADGET and Q_PROPERTY to make things visible.

best regards,
Ulf

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] No implementation found for boolean org.qtproject.qt5.android.QtNative.startQtAndroidPlugin

2020-09-11 Thread Jérôme Godbout
There was a discussion about this a while back into Slack QtMob into the 
Android channel:



my android.pri now include the right manifest based on the build version:



   MANIFEST_ANDROID_AMOTUS = AndroidManifest.xml



LIBS_ANDROID_AMOTUS = libs.xml



versionAtLeast(QT_VERSION, 5.13.0) {

AMOTUS_ANDROID_MANIFEST_FOLDER = "android-src/"

AMOTUS_ANDROID_LIBS_FOLDER = "android-src/res/values/"

}



!versionAtLeast(QT_VERSION, 5.13.0) {

AMOTUS_ANDROID_MANIFEST_FOLDER = "android-src/old"

AMOTUS_ANDROID_LIBS_FOLDER = "android-src/res/values/old"

}



QMAKE_EXTRA_TARGETS += $$androidSourceMaker("Amotus_Android_Manifest", 
"/", $$AMOTUS_ROOT, $$AMOTUS_ANDROID_MANIFEST_FOLDER, MANIFEST_ANDROID_AMOTUS)

QMAKE_EXTRA_TARGETS += $$androidSourceMaker("Amotus_Android_Libs", 
"res/values", $$AMOTUS_ROOT, $$AMOTUS_ANDROID_LIBS_FOLDER, LIBS_ANDROID_AMOTUS)



DISTFILES += \

$$AMOTUS_ANDROID_MANIFEST_FOLDER/AndroidManifest.xml \

$$AMOTUS_ANDROID_LIBS_FOLDER/libs.xml \





The androidSourceMaker is based on Luke Vear work: 
https://github.com/lukevear/qmakeAndroidSourcesHelper

This allow to cherry pick part of code and happend it to the android source 
folder, this allow multiple subrepos contributing to the android source folder 
(we can only have one, which is limiting we you keep a lots of sub repos into 
your projects).



Here is my source for it (I did sent it to Luke Vear already, but our needs 
diverge, I should open source fork it, but it is right now into a private 
repos):



# CopyAndroidSources.pri

# MIT License

#

# Copyright (c) 2018 Luke Vear

#

# Permission is hereby granted, free of charge, to any person obtaining a copy

# of this software and associated documentation files (the "Software"), to deal

# in the Software without restriction, including without limitation the rights

# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell

# copies of the Software, and to permit persons to whom the Software is

# furnished to do so, subject to the following conditions:

#

# The above copyright notice and this permission notice shall be included in all

# copies or substantial portions of the Software.

#

# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE

# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,

# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

# SOFTWARE.

#

#

# Taken from https://github.com/lukevear/qmakeAndroidSourcesHelper

# commit e0e47e0d0f1b70bedcc9e31e9f8b217e027d3a54

#

# Modification is as follow

# 2018-06-01 JG remove the .gitignore section, not needed

# 2018-06-01 JG return with more export

# 2018-06-01 JG Add FORCE depends for created target



defineReplace(copyAndroidSources) {

commandAlias = $$1

targetDirectory = $$2

sourceFiles = $$3



# Ensure we were provided a valid alias for this command

isEmpty(commandAlias) {

error("copyAndroidSources requires a valid command alias as its first 
argument.")

}



# Ensure we were provided a valid target directory

isEmpty(targetDirectory) {

error("copyAndroidSources requires a valid target directory path as its 
second argument.")

}



# Ensure we were provide a valid set of source files

isEmpty(sourceFiles) {

error("copyAndroidSources requires a valid set of files as its third 
argument.")

}



# Make sure the command is run, TODO godboutj 2018-06-01, this should be 
depends on used files instead

$${commandAlias}.depends += FORCE



# Create the target directory

# Work around problem with Windows that cannot make or on command and syntaxt 
is not the same with Windows and other *nix system

contains(QMAKE_HOST.os, Windows) {

$${commandAlias}.commands += $$escape_expand(\n\t)$(CHK_DIR_EXISTS) 
$$shell_path($$ANDROID_PACKAGE_SOURCE_DIR/$$targetDirectory) $(MKDIR) 
$$shell_path($$ANDROID_PACKAGE_SOURCE_DIR/$$targetDirectory)

} else {

$${commandAlias}.commands += $$escape_expand(\n\t)$(CHK_DIR_EXISTS) 
$$shell_path($$ANDROID_PACKAGE_SOURCE_DIR/$$targetDirectory) || $(MKDIR) 
$$shell_path($$ANDROID_PACKAGE_SOURCE_DIR/$$targetDirectory)

}

# Process each file that we were provided

for(fileName, sourceFiles) {

# Copy the file from the source directory to the target directory

$${commandAlias}.commands += $$escape_expand(\n\t)$(COPY_FILE) 
$$shell_path($$fileName) 
$$shell_path($$ANDROID_PACKAGE_SOURCE_DIR/$$targetDirectory/$$basename(fileName))

}



# We need to make our new command globally available so that qmake can 

Re: [Interest] No implementation found for boolean org.qtproject.qt5.android.QtNative.startQtAndroidPlugin

2020-09-11 Thread Alexander Dyagilev

Thanks. This + https://wiki.qt.io/AndroidServices helped.

On 9/11/2020 2:19 PM, Markus Haberlander wrote:

Have a look at  https://wiki.qt.io/Qt_for_Android_known_issues :

In order to work with Qt 5.14.0 and later releases, the
AndroidManifest.xml generated for older versions has to be updated.
This can be done either by replacing the manifest automatically using
Qt Creator, or by manually editing the manifest. An example of the
modifications needed can be found in
https://codereview.qt-project.org/c/qt/qtandroidextras/+/278987



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] No implementation found for boolean org.qtproject.qt5.android.QtNative.startQtAndroidPlugin

2020-09-11 Thread Markus Haberlander
Have a look at  https://wiki.qt.io/Qt_for_Android_known_issues :

In order to work with Qt 5.14.0 and later releases, the
AndroidManifest.xml generated for older versions has to be updated.
This can be done either by replacing the manifest automatically using
Qt Creator, or by manually editing the manifest. An example of the
modifications needed can be found in
https://codereview.qt-project.org/c/qt/qtandroidextras/+/278987

Hope this helps,
Markus


Am Fr., 11. Sept. 2020 um 12:29 Uhr schrieb ekke :
>
> yes - it's no 'update'
> I have checked-in all files created from template into my git
> then create templates and check the diffs so you can manually adjust
>
>
> Am 11.09.20 um 11:53 schrieb Alexander Dyagilev:
> > There is no such a feature. It just completely overwrites manifest so
> > I loose everything and my project gets broken even more. It's not an
> > update
> >
> > On 9/11/2020 9:59 AM, ekke wrote:
> >> Have you tried to update your templates ?
> >> Project - Android - Build - Create Templates
> >> ekke
> >>
> >> Am 11.09.20 um 05:42 schrieb Alexander Dyagilev:
> >>> Hello,
> >>>
> >>> I'm trying to build and run my project under Qt 5.15.1. The app
> >>> crashes on start with the following output:
> >>>
> >>> E loadmanager.fd: No implementation found for boolean
> >>> org.qtproject.qt5.android.QtNative.startQtAndroidPlugin(java.lang.String,
> >>> java.lang.String) (tried
> >>> Java_org_qtproject_qt5_android_QtNative_startQtAndroidPlugin and
> >>> Java_org_qtproject_qt5_android_QtNative_startQtAndroidPlugin__Ljava_lang_String_2Ljava_lang_String_2)
> >>>
> >>> E AndroidRuntime: FATAL EXCEPTION: qtMainLoopThread
> >>>
> >>> Qt 5.12.9 works fine. I suspect there some changes in
> >>> androidmanifest.xml are required. Failed to google which ones...
> >>>
> >>> Any help?
> >>>
> >>> ___
> >>> Interest mailing list
> >>> Interest@qt-project.org
> >>> https://lists.qt-project.org/listinfo/interest
> >>
> >> ___
> >> Interest mailing list
> >> Interest@qt-project.org
> >> https://lists.qt-project.org/listinfo/interest
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] No implementation found for boolean org.qtproject.qt5.android.QtNative.startQtAndroidPlugin

2020-09-11 Thread ekke

yes - it's no 'update'
I have checked-in all files created from template into my git
then create templates and check the diffs so you can manually adjust


Am 11.09.20 um 11:53 schrieb Alexander Dyagilev:
There is no such a feature. It just completely overwrites manifest so 
I loose everything and my project gets broken even more. It's not an 
update


On 9/11/2020 9:59 AM, ekke wrote:

Have you tried to update your templates ?
Project - Android - Build - Create Templates
ekke

Am 11.09.20 um 05:42 schrieb Alexander Dyagilev:

Hello,

I'm trying to build and run my project under Qt 5.15.1. The app 
crashes on start with the following output:


E loadmanager.fd: No implementation found for boolean 
org.qtproject.qt5.android.QtNative.startQtAndroidPlugin(java.lang.String, 
java.lang.String) (tried 
Java_org_qtproject_qt5_android_QtNative_startQtAndroidPlugin and 
Java_org_qtproject_qt5_android_QtNative_startQtAndroidPlugin__Ljava_lang_String_2Ljava_lang_String_2) 


E AndroidRuntime: FATAL EXCEPTION: qtMainLoopThread

Qt 5.12.9 works fine. I suspect there some changes in 
androidmanifest.xml are required. Failed to google which ones...


Any help?

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] QML/C++ interaction in Qt6

2020-09-11 Thread Ulf Hermann
- Allow QML to access public properties of classes, even if these public 
properties do not use `Q_PROPERTY`

- Allow QML access to classes that are neither `QObject`, nor `QGadget`


This is not planned right now. Note that we rely on moc to generate the 
class descriptions that QML uses. Therefore, we need constructs like 
Q_OBJECT, Q_GADGET and Q_PROPERTY to make things visible.


best regards,
Ulf

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] No implementation found for boolean org.qtproject.qt5.android.QtNative.startQtAndroidPlugin

2020-09-11 Thread Stanislas RENAN

Hi,

You have to diff templates bundled with the two Qt versions and 
integrate manually the differences in the xml of your project.


May not fix your case, though.

Stanislas

Le 11/09/2020 à 11:53, Alexander Dyagilev a écrit :
There is no such a feature. It just completely overwrites manifest so 
I loose everything and my project gets broken even more. It's not an 
update


On 9/11/2020 9:59 AM, ekke wrote:

Have you tried to update your templates ?
Project - Android - Build - Create Templates
ekke

Am 11.09.20 um 05:42 schrieb Alexander Dyagilev:

Hello,

I'm trying to build and run my project under Qt 5.15.1. The app 
crashes on start with the following output:


E loadmanager.fd: No implementation found for boolean 
org.qtproject.qt5.android.QtNative.startQtAndroidPlugin(java.lang.String, 
java.lang.String) (tried 
Java_org_qtproject_qt5_android_QtNative_startQtAndroidPlugin and 
Java_org_qtproject_qt5_android_QtNative_startQtAndroidPlugin__Ljava_lang_String_2Ljava_lang_String_2) 


E AndroidRuntime: FATAL EXCEPTION: qtMainLoopThread

Qt 5.12.9 works fine. I suspect there some changes in 
androidmanifest.xml are required. Failed to google which ones...


Any help?

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


[Interest] QML/C++ interaction in Qt6

2020-09-11 Thread Magnus Groß

Hi,

since Qt6 is going to include the strict QML subset, where everything can be 
compiled down to native C++, I was wondering if there are efforts going with 
that to improve interactions between the two languages along with it.


Two things I am thinking of specifically:

- Allow QML to access public properties of classes, even if these public   
properties do not use `Q_PROPERTY`

- Allow QML access to classes that are neither `QObject`, nor `QGadget`

Surely the fact that strict QML can be transpiled to C++ is going to help with 
implementing this. I think this would improve interactions between the two 
languages immensely.


Are there any plans to allow something like this?

Best regards,
Magnus
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] No implementation found for boolean org.qtproject.qt5.android.QtNative.startQtAndroidPlugin

2020-09-11 Thread Alexander Dyagilev
There is no such a feature. It just completely overwrites manifest so I 
loose everything and my project gets broken even more. It's not an 
update


On 9/11/2020 9:59 AM, ekke wrote:

Have you tried to update your templates ?
Project - Android - Build - Create Templates
ekke

Am 11.09.20 um 05:42 schrieb Alexander Dyagilev:

Hello,

I'm trying to build and run my project under Qt 5.15.1. The app 
crashes on start with the following output:


E loadmanager.fd: No implementation found for boolean 
org.qtproject.qt5.android.QtNative.startQtAndroidPlugin(java.lang.String, 
java.lang.String) (tried 
Java_org_qtproject_qt5_android_QtNative_startQtAndroidPlugin and 
Java_org_qtproject_qt5_android_QtNative_startQtAndroidPlugin__Ljava_lang_String_2Ljava_lang_String_2) 


E AndroidRuntime: FATAL EXCEPTION: qtMainLoopThread

Qt 5.12.9 works fine. I suspect there some changes in 
androidmanifest.xml are required. Failed to google which ones...


Any help?

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] No implementation found for boolean org.qtproject.qt5.android.QtNative.startQtAndroidPlugin

2020-09-11 Thread ekke

Have you tried to update your templates ?
Project - Android - Build - Create Templates
ekke

Am 11.09.20 um 05:42 schrieb Alexander Dyagilev:

Hello,

I'm trying to build and run my project under Qt 5.15.1. The app 
crashes on start with the following output:


E loadmanager.fd: No implementation found for boolean 
org.qtproject.qt5.android.QtNative.startQtAndroidPlugin(java.lang.String, 
java.lang.String) (tried 
Java_org_qtproject_qt5_android_QtNative_startQtAndroidPlugin and 
Java_org_qtproject_qt5_android_QtNative_startQtAndroidPlugin__Ljava_lang_String_2Ljava_lang_String_2)

E AndroidRuntime: FATAL EXCEPTION: qtMainLoopThread

Qt 5.12.9 works fine. I suspect there some changes in 
androidmanifest.xml are required. Failed to google which ones...


Any help?

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest