Re: [Development] Nominating Antti Määttä as Qt3D approver

[Pasi Keränen]

+1 from me as well.

Regards,
Pasi

On 14/11/16 17:19, "Development on behalf of Sean Harmer" 
 wrote:

On Monday 14 November 2016 15:15:16 Paul Lemire wrote:
> Hi
> 
> I would like to propose the nomination of Antti Määttä for approver 
status.
> Antti has been contributing many patches to Qt3D adding new features and
> providing bug fixes. In addition, having another approver would be a great
> help to reduce the amount of time patches are spent awaiting a review.

+1 from me.

Cheers,

Sean

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


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

Re: [Development] Examples and Demos in qtdoc

[Pasi Keränen]

Hi,

I agree 100% with the need to have a place to store beautiful demos and 
examples. And I agree with Sean’s large file support need as Qt 3D Studio 
examples and demos will also depend on having access to large textures and hdr 
textures to make things look nice. Even 2D examples can require “large” 
resources when you are striving to create beautiful results.

I’m not 100% sure about qtdoc as the repo though. But I can live with it if 
that is what is seen as best option by others.

Cheers,
Pasi

--
Pasi Keränen
Senior Manager

The Qt Company
Elektroniikkatie 13
90590, Oulu, Finland


On 14/06/2017, 15.15, "Development on behalf of Sean Harmer" wrote:

Hi,

On Wednesday 14 June 2017 13:18:35 Frederik Gladhorn wrote:
> Hi all,
> 
> We recently had a discussion in the Qt Company about how we can improve 
the
> first use experience of Qt and one important aspect are the examples and
> demos.
> 
> We have a lot of examples that are limited by the Qt module they live in,
> for example not making use of ready made buttons in Qt Quick. To allow
> examples to use any Qt module while keeping the build system clean (no
> cyclic dependencies between modules), I'd like to propose using the qtdoc
> module to gather fresh and beautiful examples.
> 
> We currently have a few bigger examples already that would fit this 
category
> and plan to invest more into good looking nice and welcoming examples to
> give new Qt users a positive first impression.
> 
> Of course we could create a new repo, but considering that we have an
> existing repo which did contain the demo launcher previously and which is
> ready to be used, I'd propse going with it, while the name is not perfect.
> It's already part of the infrastructure and qt5.git, so this seems like an
> easy way to go forward.

I agree that we need something like this. Ideally we also need support for 
git-lfs or some other mechanism for handling large files. Particularly for 
Qt 
3D, getting "nice looking" results often requires HDR textures for 
environment 
maps and often other texture inputs too.

Cheers,

Sean
-- 
Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK
KDAB (UK) Ltd, a KDAB Group company
Tel. +44 (0)1625 809908; Sweden (HQ) +46-563-540090
Mobile: +44 (0)7545 140604
KDAB - Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


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

[Development] Nominating Tomi Korpipää for approver

[Pasi Keränen]

Hi,

I’d like to nominate Tomi Korpipää from my team here at The Qt Company for 
approver status. Tomi has been key contributor in Qt Charts, Qt 
DataVizualisation, Qt3D Editor and in the recently unveiled Qt 3D Studio. I 
think this nomination is long overdue as Tomi has been one of the carrying 
forces in those components. Those with access, you can see his contributions 
here: https://codereview.qt-project.org/#/q/owner:"Tomi 
Korpipää"+status:merged,n,z

Regards,
Pasi Keränen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Nominating Maintainers of qt3dstudio/qt3dstudio

[Pasi Keränen]

Hi all,

Those of you who have been following our blog posts or who went to QtCon this 
year know about the new 3D UI design tool and runtime combination we received 
as contribution from NVIDIA earlier this year. The tool is now known as Qt 3D 
Studio and the repositories were opened before Qt WS 2017. For more info check 
out: 
http://blog.qt.io/blog/2017/10/11/qt-3d-studio-source-code-pre-release-snapshots-available/

I’d like to name myself (Pasi Keränen) as the maintainer of Qt 3D Studio. I’ve 
been involved in the project since the early negotiations with NVIDIA and 
handling the receiving of the contribution from them. All the way to leading 
the Qt integration work that is still ongoing towards 1.0 release later this 
month.

As Qt 3D Studio is a large piece of work I’d like to also suggest the following 
persons as maintainers of sub-areas of Qt 3D Studio:
Soili Väinämö – Maintainer of UX, ensuring the user experience of the tool and 
runtime develop going onwards. Soili has been doing excellent work in both 
converting the look’n’feel of the application to leading UX studies on how to 
improve the usability of the product from end user point of view.
Tomi Korpipää – Maintainer of Editor Application code. Tomi has done great work 
in handling the bug flow and converting the look’n’feel to more Qt like 
together with Soili.
Antti Määttä – Maintainer of Runtime 1.0 and runtime integration. Antti has 
long history of working with 3D engine code and has done excellent work in for 
example prototyping OpenGL ES 2 support in the runtime component of Qt 3D 
Studio.
Laszlo Agocs – Maintainer of Qt 3D based Runtime 2.0. Laszlo has been working 
on the prototype runtime for some time now and is already looking in to 
productizing it.
Miikka Heikkinen – Maintainer of installer and viewer application. Miikka has 
been instrumental in getting the installer creation implemented and also has 
been adding new experimental features to the viewer like image sequence 
generation.

Regards,
Pasi Keränen
Team lead of TQtC 3D Team, Oulu
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Christoph Schleifenbaum for Approver

[Pasi Keränen]

+1 from me as well. Christoph has done good work on Qt 3D Studio.


Regards,

Pasi


From: Development  on 
behalf of Mike Krus 
Sent: Saturday, November 4, 2017 12:04:14 AM
To: Sergio Martins
Cc: development@qt-project.org
Subject: Re: [Development] Nominating Christoph Schleifenbaum for Approver

+1 from me (with the disclaimer that we both work for KDAB).

> On 2 Nov 2017, at 12:46, Sergio Martins  wrote:
>
> Hi,
>
>
> I'd like to nominate Christoph Schleifenbaum for Approver.
>
> He's been with KDAB for 12 years and has done dozens of fixes for cocoa, 
> widgets and item views.
>
> He' also one of the developers who worked on the Qt3DStudio port to Qt very 
> recently.
>
>
> https://codereview.qt-project.org/#/q/owner:%22Christoph+Schleifenbaum%22,n,z
>
>
>
>
> Regards,
> --
> Sérgio Martins | sergio.mart...@kdab.com | Senior Software Engineer
> Klarälvdalens Datakonsult AB, a KDAB Group company
> Tel: Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
> KDAB - The Qt, C++ and OpenGL Experts
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

--
Mike Krus | mike.k...@kdab.com | Senior Software Engineer
KDAB (UK) Ltd., a KDAB Group company
Tel: UK Office +44 1625 809908   Mobile +44 7833 491941
KDAB - The Qt Experts, C++, OpenGL Experts

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

Re: [Development] Nominating Maintainers of qt3dstudio/qt3dstudio

[Pasi Keränen]

Hi,

As the required 15 work days have (ages ago) passed the nominations below for 
Qt 3D Studio are final.
Congratulations to all appointed maintainers!
Thank you Lars for updating the https://wiki.qt.io/Maintainers page and gerrit 
maintainers group.

Regards,
Pasi


From: Development  on 
behalf of Pasi Keränen 
Date: Thursday, 2 November 2017 at 13.49
To: "development@qt-project.org" 
Subject: [Development] Nominating Maintainers of qt3dstudio/qt3dstudio

Hi all,

Those of you who have been following our blog posts or who went to QtCon this 
year know about the new 3D UI design tool and runtime combination we received 
as contribution from NVIDIA earlier this year. The tool is now known as Qt 3D 
Studio and the repositories were opened before Qt WS 2017. For more info check 
out: 
http://blog.qt.io/blog/2017/10/11/qt-3d-studio-source-code-pre-release-snapshots-available/

I’d like to name myself (Pasi Keränen) as the maintainer of Qt 3D Studio. I’ve 
been involved in the project since the early negotiations with NVIDIA and 
handling the receiving of the contribution from them. All the way to leading 
the Qt integration work that is still ongoing towards 1.0 release later this 
month.

As Qt 3D Studio is a large piece of work I’d like to also suggest the following 
persons as maintainers of sub-areas of Qt 3D Studio:
Soili Väinämö – Maintainer of UX, ensuring the user experience of the tool and 
runtime develop going onwards. Soili has been doing excellent work in both 
converting the look’n’feel of the application to leading UX studies on how to 
improve the usability of the product from end user point of view.
Tomi Korpipää – Maintainer of Editor Application code. Tomi has done great work 
in handling the bug flow and converting the look’n’feel to more Qt like 
together with Soili.
Antti Määttä – Maintainer of Runtime 1.0 and runtime integration. Antti has 
long history of working with 3D engine code and has done excellent work in for 
example prototyping OpenGL ES 2 support in the runtime component of Qt 3D 
Studio.
Laszlo Agocs – Maintainer of Qt 3D based Runtime 2.0. Laszlo has been working 
on the prototype runtime for some time now and is already looking in to 
productizing it.
Miikka Heikkinen – Maintainer of installer and viewer application. Miikka has 
been instrumental in getting the installer creation implemented and also has 
been adding new experimental features to the viewer like image sequence 
generation.

Regards,
Pasi Keränen
Team lead of TQtC 3D Team, Oulu
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Pasi Keränen]

Hi there,

+1 for having a generic telemetry plugin in Qt.

This is great initiative and very much the way today's app and application 
industry works. UX studies performed by UX experts have been minimized and 
targeted for specific (usually new/experimental) features or upcoming new 
software (like we did with Qt 3D Studio back in last spring). And the mass 
information on "how do our users use the SW? do they find the stuff we've put 
in there? how often they hit a wall in doing sequence X? how many crashes do 
they experience when doing Y?" is collected via automated telemetry. It is 
great as it brings data from the actual user in their actual work and you can 
then use that to concentrate on functionality that really matters to your 
users. Making stuff they repeat hundred times a week easier and faster, making 
them more productive.

I see definite need for this in Qt 3D Studio so please don’t make this just 
with Qt Creator in mind. Also, in my humble opinion, in order to be relevant in 
today's UI development, Qt should also offer this kind of a plug-in to our 
customers. A ready-to-go plug-in that automatically ensures the data is 
collected in a way that fulfills data privacy acts and respects the privacy of 
the user would be great. Especially for startups and smaller companies, but 
also for bigger companies wanting to switch to the modern way of doing UI 
development. It is not as easy to do as one might think at glance.

I would ask anyone who has not done work with usability and user experience 
people in the past to give this way of working a chance. I've worked 7 years in 
application development while we grew usability knowledge in the team over that 
time. The first time I got to observe a real world user working with our 
software in actual real world situation was eye opening. We had gotten so many 
important things wrong in our idealistic thinking and forgotten to handle 
certain cases that occur on the field. Also you become blind to your own 
creations faults as you just know how the software works. It's just a fact of 
life.

Regards,
Pasi Keränen

--
Senior Manager, 3D
The Qt Company





On 22/02/2018, 22.36, "Development on behalf of André Pönitz" 
 wrote:

On Thu, Feb 22, 2018 at 01:58:55PM +, Tino Pyssysalo wrote:
> Hi,
> 
> The idea is to develop a generic library/plugin, which anyone could use for
> analytics.

I see no reason why this can't be done as part of e.g. the commercial Qt
offering, with customers being free to deploy that if they feel it helps
their own offering (for whatever reasons that I luckily do not need to
comprehend), nor do I see a reason why this should be used by the Qt
Project's Qt Creator, especially when the people potentially acting on the
results expressed severe dislike and doubts on the usefulness of such
analytics for their work.

For an Open Source solution there is e.g. KUserFeedback. I haven't used
that myself, but judging from the description it appears to do what you
claim to want to do, and judging from a quick look at the code and the
name of the author I am ready to bet its implementation is sane.

So I really have a hard time to see a gap here that needs to be filled.

> The backend can be any storage and The Qt Company does not provide
> that.
> 
> We plan to use the same backend, which we already use in online installers to
> collect statistics about installations. At least in case of Qt Creator, the
> plan is to make some analysis results available for the community. Obviously,
> we do not do that for our commercial tooling.
> 
> Analytics is opt-in and disabled by default in Qt Creator. We plan to ask user
> in the installer, if the user wish to participate in Qt UX improvement. If the
> answers is no, the analytics plugin is never installed.  When the creator is
> started for the first time, it will show a dialog, consisting a list of
> collected data items and an option to enable/disable the plugin. There will be
> a new output pane, which shows collected data, conversions methods, if any
> used, and transmitted data to the user.  -- Tino

At some point you need to qualify what you mean when you use the word "we".
Your current use of "we" clearly does not include myself, nor, if you allow
me to extrapolate from the grapevine, the majority of the Qt Creator team.

So, 
  - who is "we"?
  - why is "us" (the Qt Creator team) not part of "we"
when the topic is related to Qt Creator?
  - what data do you intent to collect exactly?
  - what mechanism do you plan to use to translate
the collected data into what actions?


Andre'

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

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

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Pasi Keränen]

Hi,

Repos can be relocated to new homes if really needed, but I think it’s fair to 
say more generic location is definitely preferred from Qt 3D Studio point of 
view.

To make this even easier I’d even start with a playground repo if nothing else 
can be found. Qt has always been (despite our vocal and sometimes a bit harsh 
dialogue) inclusive, so it should be fine to go and experiment with all things 
UI related. Just to see if something is worth the effort or not.

Regards,
Pasi

From: Development  on 
behalf of Maurice Kalinowski 
Date: Friday, 23 February 2018 at 9.33
To: Tino Pyssysalo , Simon Hausmann 
, Tuukka Turunen , 
"qt-crea...@qt-project.org" , 
"development@qt-project.org" 
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator

“The idea is to develop a generic library/plugin, which anyone could use for 
analytics”

If that is the case, then qt-creator/telemetry is the wrong repository to ask 
for. If you are aiming at something generic, then it should be qt/

Maurice

Von: Qt-creator 
[mailto:qt-creator-bounces+maurice.kalinowski=qt...@qt-project.org] Im Auftrag 
von Tino Pyssysalo
Gesendet: Thursday, February 22, 2018 2:59 PM
An: Simon Hausmann ; Tuukka Turunen 
; qt-crea...@qt-project.org; development@qt-project.org
Betreff: Re: [Qt-creator] [Development] Requesting repository for telemetry 
plugin in Qt Creator

Hi,

The idea is to develop a generic library/plugin, which anyone could use for 
analytics. The backend can be any storage and The Qt Company does not provide 
that.

We plan to use the same backend, which we already use in online installers to 
collect statistics about installations. At least in case of Qt Creator, the 
plan is to make some analysis results available for the community. Obviously, 
we do not do that for our commercial tooling.

Analytics is opt-in and disabled by default in Qt Creator. We plan to ask user 
in the installer, if the user wish to participate in Qt UX improvement. If the 
answers is no, the analytics plugin is never installed.  When the creator is 
started for the first time, it will show a dialog, consisting a list of 
collected data items and an option to enable/disable the plugin. There will be 
a new output pane, which shows collected data, conversions methods, if any 
used, and transmitted data to the user.
--
Tino


On 22/02/2018, 15.26, "Simon Hausmann" 
mailto:simon.hausm...@qt.io>> wrote:


Hi,



Can you provide a bit more information about how this plugin / frontend fits 
into the Qt project? Where is the collected data sent to and how is it 
accessible to the community?



(-1 from me, as I think this needs to be clarified)



Simon


From: Development 
mailto:development-bounces+simon.hausmann=qt...@qt-project.org>>
 on behalf of Tuukka Turunen mailto:tuukka.turu...@qt.io>>
Sent: Thursday, February 22, 2018 2:14:14 PM
To: Tino Pyssysalo; 
qt-crea...@qt-project.org; 
development@qt-project.org
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator




Hi,



+1 for creating the repo, but what about qt/qtanalytics as a name? This item 
could be useful also for other applications.



Yours,



 Tuukka



From: Qt-creator 
mailto:qt-creator-bounces+tuukka.turunen=qt...@qt-project.org>>
 on behalf of Tino Pyssysalo mailto:tino.pyssys...@qt.io>>
Date: Thursday, 22 February 2018 at 13.04
To: "qt-crea...@qt-project.org" 
mailto:qt-crea...@qt-project.org>>
Subject: [Qt-creator] Requesting repository for telemetry plugin in Qt Creator



Description:



Telemetry plugin (frontend) to collect usage data from Qt Creator to help 
improving Qt, Qt features, and Qt tools.

Non-personal data items, such as duration the user spent in design mode, will 
be collected in a way, which is completely transparent to the user.



Responsible: Tino Pyssysalo



Repository: qt-creator/plugin-telemetry





---

Tino Pyssysalo

Senior Manager



The Qt Company

Hämeenkatu 14 C 25

33100 Tampere, Finland

tino.pyssys...@qt.io

+358 40 8615475

http://qt.io



The future is Written with Qt

---




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

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Pasi Keränen]

Hi Tobias,

I planned to stay out of this, but
-1 since I am totally confused about the scope of this project at this point.
So are we talking about a generic telemetry framework for Qt applications or 
about watching Qt Creator users specifically?
Tino started by making the claim that this is a generic library and then kept 
listing Qt Creator specific integrations. You focus entirely onto the generic 
part, leaving out creator completely.
What exactly are we talking about here?

My understanding at this point is that this is meant to be a telemetry 
framework for Qt applications and first integration point that has been in 
discussions is Qt Creator. I intentionally left Qt Creator out as I don’t feel 
comfortable talking what they need/don’t need. So instead I concentrated on 
what I see Qt 3D Studio needs as I feel much more comfortable to talk about 
that based on our experiences, our engagements with customers and the usability 
and UI work we’ve done so far in Qt 3D Studio project.

I’m always in favor of iterative development as you very very rarely understand 
the scope and needs at the beginning. So I understand the need to have a 
“reference integration to try out” even if we talk about aiming towards generic 
telemetry plugin. And it seems quite obvious from these discussions that we 
don’t yet know ourselves a lot about how to collect data, what type of data is 
to be collected and how to process it. We seem to be a bit divided in to 
individuals thinking this is inherently bad and morally dubious. And 
individuals (like myself) who see this as great idea to be able to get more 
data on how people use our tools. Not just from big customers and people who 
come to our events. But also from people out there in universities, small 
companies, startups, the people we rarely meet in person.

Once we have understanding on what exactly are we after, then it would be good 
to move towards a generic Qt framework prototype. Maybe integrate against a 
known and trusted third party framework, add features to the API iteratively 
based on learnings and iterations. Then move on to publish this as tech preview 
and while we investigate integrating against another 3rd party framework so 
that we end up with a truly generic, Qt-like wrapper for specific functionality.

A Qt creator spyware plug-in (which does more than what we discuss here I 
hope:-) would be a matter of a couple of weeks to do, putting a generic 
framework into place with all the bits and pieces for that to be actually 
useful in a wide list of possible contexts is a very different beast.

I object to using “Spyware” term in this context. Spyware is SW that does 
things behind your back. Siphons contact information, user account info etc. 
without telling you. We’re NOT talking about such use cases here! I don’t think 
anyone in The Qt Company wants to do such things. From what I hear the 
intention is to track certain things in an open, transparent manner, respecting 
the communitys clear wish to keep things in the open and for the benefit of our 
end users.


This is great initiative and very much the way today's app and application 
industry works. UX studies performed by UX experts have been minimized and 
targeted for specific (usually new/experimental) features or upcoming new 
software (like we did with Qt 3D Studio back in last spring). And the mass 
information on "how do our users use the SW? do they find the stuff we've put 
in there? how often they hit a wall in doing sequence X? how many crashes do 
they experience when doing Y?" is collected via automated telemetry. It is 
great as it brings data from the actual user in their actual work and you can 
then use that to concentrate on functionality that really matters to your 
users. Making stuff they repeat hundred times a week easier and faster, making 
them more productive.

I see value in this approach when you can do lots of small releases fast. So 
you can do evaluate the effect of small changes by doing one change to evaluate 
per release and measure how that effects usage.
We can not do more than two releases per year in Qt. Is this approach even 
applicable to us?

Qt 3D Studio plans to do 4 releases per year, so for us this is definitely 
applicable. Qt Creator does also more than 2 releases a year so perhaps this 
could be useful for them as well, but as I said. I’m not comfortable talking on 
their behalf on this.

I want to also point out that answering any of the questions you used as an 
example require *way* more information than I am even remotely comfortable to 
collect.


This is where we definitely differ as individuals. I use software from Apple, 
Adobe etc. and I’m 100% fine giving them information on my usage statistics as 
it means the SW might get better over time for me. If e.g. Blender would some 
day ask me “are you ok for us to track your usage of the SW” I’d be 100% ok to 
do that as I see that it definitely could improve a lot from observing users. I 

[Development] Qt 3D Studio 2.0 BETA 2 released

[Pasi Keränen]

Hi,

We have released Qt 3D Studio 2.0 BETA2 today. It is available as both 
commercial and open sourceversions from online and offline installers.

For instructions on how to get started and install everything correctly, see 
Laszlo’s excellent blog on the subject for BETA1 here:
http://blog.qt.io/blog/2018/05/18/get-started-qt-3d-studio-2-0-beta-1/

Regards,
Pasi Keränen
Senior Manager, 3D Team
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt 3D Studio RC2 is available

[Pasi Keränen]

Hi,

We have released Qt 3D Studio 2.0 RC2 today. It is available as both commercial 
and open source versions from online and offline installers.

Qt 3D Studio 2.0 has a whole new 3D engine built on top of Qt 3D, a new 
timeline built from ground up with Qt based on the new timeline code in 
upcoming Qt Design Studio. Also there are a lot of improvements to the designer 
user experience, interactions in the 3D edit view and visualisation of lights 
and cameras being most notable ones. And of course we have numerous bug fixes.

For instructions on how to get started and install everything correctly, see 
Laszlo’s excellent blog on the subject here:
http://blog.qt.io/blog/2018/05/18/get-started-qt-3d-studio-2-0-beta-1/

Regards,
Pasi Keränen
Senior Manager, 3D Team

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

[Development] Deprecation of Qt Canvas3D in 5.12

[Pasi Keränen]

We’ve maintained the Canvas3D (a WebGL like API for Qt Quick JavaScript) module 
with very minimal effort, but when we look at our future it seems clear we need 
to start supporting multiple low level APIs in Qt’s graphics stack and make our 
graphics stack less OpenGL centric. This was discussed in the Qt Contributor’s 
Summit 2018 and has been “in the air” for some time now among developers of Qt 
3D, Qt 3D Studio and Qt Quick. Qt will of course still support OpenGL, but it’s 
not going to be the only API we need to support.

To this end Canvas3D with it’s WebGL API that maps nearly 1:1 to OpenGL is no 
longer a simple API to maintain going in to the future. It would require a 
major rewrite and a lot more involved design work to map it to new APIs (e.g. 
Vulcan, DX 12 or Metal).  Also there hasn’t been a big uptake in the customers 
or in the community to use this QML API or the ported three.js javascript 3D 
engine versions. All in all I think Qt’s graphics stack development effort 
would be better spent in improving Qt 3D, Qt 3D Studio and Qt Quick, adding 
enablers in these modules for supporting new graphics APIs etc.

So as creator and maintainer of Canvas3D I’d like to propose the deprecation of 
the module in Qt 5.12 and removal of the module and it’s APIs in a future Qt 
version. Instead of Qt Canvas3D I’d strongly recommend any existing developers 
on top of Canvas3D to move on top of Qt 3D or Qt 3D Studio APIs as those are 
being developed actively, offer much improved performance (especially on 
resource limited devices) and enable more modern GPU acceleration than is 
possible with Canvas3D.

Regards,
Pasi


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

Re: [Development] Deprecation of Qt Canvas3D in 5.12

[Pasi Keränen]

As there has been no objections I’ve created task: 
https://bugreports.qt.io/browse/QTBUG-70510 Mark Canvas3D APIs as deprecated
I’m setting fix version target to 5.12 RC, but I’m not 100% if that is 
achievable/allowed for RC change.

Regards,
Pasi

From: Tuukka Turunen 
Date: Monday, 3 September 2018 at 11.59
To: Lars Knoll , Pasi Keränen 
Cc: Qt development mailing list 
Subject: Re: [Development] Deprecation of Qt Canvas3D in 5.12


+1 from me as well.

It is good to mark it deprecated to give the right message for our users.

Yours,

Tuukka

From: Development  on 
behalf of Lars Knoll 
Date: Monday, 3 September 2018 at 10.14
To: Pasi Keränen 
Cc: Qt development mailing list 
Subject: Re: [Development] Deprecation of Qt Canvas3D in 5.12

+1 from my side.

Cheers,
Lars



On 31 Aug 2018, at 12:23, Pasi Keränen 
mailto:pasi.kera...@qt.io>> wrote:

We’ve maintained the Canvas3D (a WebGL like API for Qt Quick JavaScript) module 
with very minimal effort, but when we look at our future it seems clear we need 
to start supporting multiple low level APIs in Qt’s graphics stack and make our 
graphics stack less OpenGL centric. This was discussed in the Qt Contributor’s 
Summit 2018 and has been “in the air” for some time now among developers of Qt 
3D, Qt 3D Studio and Qt Quick. Qt will of course still support OpenGL, but it’s 
not going to be the only API we need to support.

To this end Canvas3D with it’s WebGL API that maps nearly 1:1 to OpenGL is no 
longer a simple API to maintain going in to the future. It would require a 
major rewrite and a lot more involved design work to map it to new APIs (e.g. 
Vulcan, DX 12 or Metal).  Also there hasn’t been a big uptake in the customers 
or in the community to use this QML API or the ported three.js javascript 3D 
engine versions. All in all I think Qt’s graphics stack development effort 
would be better spent in improving Qt 3D, Qt 3D Studio and Qt Quick, adding 
enablers in these modules for supporting new graphics APIs etc.

So as creator and maintainer of Canvas3D I’d like to propose the deprecation of 
the module in Qt 5.12 and removal of the module and it’s APIs in a future Qt 
version. Instead of Qt Canvas3D I’d strongly recommend any existing developers 
on top of Canvas3D to move on top of Qt 3D or Qt 3D Studio APIs as those are 
being developed actively, offer much improved performance (especially on 
resource limited devices) and enable more modern GPU acceleration than is 
possible with Canvas3D.

Regards,
Pasi


___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

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

Re: [Development] Maintainers for Qt Charts and Data Visualization

[Pasi Keränen]

Absolute, definite +1 for this! It’s long overdue :)

Cheers,
Pasi




On 09/05/16 14:22, "Development on behalf of Lars Knoll" 
 wrote:

>Hi,
>
>Since we now open sourced Charts and Data Visualisation for Qt 5.7, the 
>modules also need a Maintainer. I'd like to propose the two people that have 
>been maintaining these modules while they were developed inside TQtC to 
>continue in this role: Miikka Heikkinen for Charts, and Tomi Korpipää for Data 
>Visualisation.
>
>Cheers,
>Lars
>
>
>___
>Development mailing list
>Development@qt-project.org
>http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development