Re: [Development] Qt Quick Controls for Embedded
Hi Frederik, On 04/09/2015 04:04 PM, Frederik Gladhorn wrote: We want to give you the code, here it is :) https://codereview.qt-project.org/#/admin/projects/qt-labs/qtquickcontrols2 [...] Feedback welcome! If I understand correctly, these controls are intended to be a cross-platform set of controls with their own style, with the goal of being good looking and still have a good performance; the goal is not to wrap (or make them look alike) any of the platform native controls, unlike for example qtqmlandroid. Is my understanding correct? If so, it seems to me that the naming is somehow confusing: on one hand we have qtquickcontrols1, which provides a uniform API to render native-looking controls; on the other hand, the qtquickcontrols2 module seems to have a very different goal. Maybe this qtquickcontrols2 module should be renamed to something like qtquickembedded, to avoid giving the false impression that is meant to supersede the existing module? And will qtqmlandroid eventually be merged into qtquickcontrols1, once it's ready? Ciao, Alberto -- http://blog.mardy.it - geek in un lingua international! ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Quick Controls for Embedded
Hi Alberto, On 20 Apr 2015, at 15:43, Alberto Mardegan ma...@users.sourceforge.net wrote: Hi Frederik, On 04/09/2015 04:04 PM, Frederik Gladhorn wrote: We want to give you the code, here it is :) https://codereview.qt-project.org/#/admin/projects/qt-labs/qtquickcontrols2 [...] Feedback welcome! If I understand correctly, these controls are intended to be a cross-platform set of controls with their own style, with the goal of being good looking and still have a good performance; the goal is not to wrap (or make them look alike) any of the platform native controls, unlike for example qtqmlandroid. Is my understanding correct? Consider the “native” styling an open question. It has major implications on the architecture and performance. If so, it seems to me that the naming is somehow confusing: on one hand we have qtquickcontrols1, which provides a uniform API to render native-looking controls; on the other hand, the qtquickcontrols2 module seems to have a very different goal. It’s just that the good old recipe does no longer give that shiny results. No matter how fancy ways we invent to extract native assets, the native feel is always off. Attila had very good insights on this subject in the QML bindings for native Android controls” thread. Maybe this qtquickcontrols2 module should be renamed to something like qtquickembedded, to avoid giving the false impression that is meant to supersede the existing module? Nothing is set in stone at this point. Trust me, we have spent an enormous amount of time discussing the name and going back and forth… :) And will qtqmlandroid eventually be merged into qtquickcontrols1, once it's ready? The QML for Android playground project is unlikely to be merged with Qt Quick Controls. It’s not using or even compatible with Qt Quick. -- J-P Nurmi ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Quick Controls for Embedded
We want to give you the code, here it is :) https://codereview.qt-project.org/#/admin/projects/qt-labs/qtquickcontrols2 It is in the qt-labs namespace which means no guarantees, no commitment, we'll rename and break everything. Besides this little warning, I think there is a great repository to play with :) Build it against the dev branch of Qt (that'll be 5.6 as minimum requirement for now). Feedback welcome! Cheers, Frederik On Wednesday, April 08, 2015 03:18:27 PM Frederik Gladhorn wrote: Hi all, as announced by JP's blog post, we've been working on a new set of Qt Quick Controls that have slightly different goals than the existing ones: http://blog.qt.io/blog/2015/03/31/qt-quick-controls-for-embedded/ The main target is performance, especially on low end hardware. The code will live in the qtquickcontrols module, next to the existing controls. For now there is only one style supported, with some theming capabilities. This is an important point to get top notch performance. Now is the time to give everyone the chance to play with the new controls which are at a tech preview level. Since the architecture is different, we want to keep a clean separation in the qtquickcontrols git module and will move the code around to accommodate both modules within the repository. The plan is to create two top level directories in the repository: a controls1 directory containing everything currently in the repository (src/tests/examples), and a controls2 directory to contain the new controls. Note that both sets of controls will be co-installable and work together. That is to say, the following will work just fine: import QtQuick.Controls 1.x as Controls1 import QtQuick.Controls 2.x After a long discussion, we think that going with a major version is easiest, as we didn't find a great name that makes it clear what the new control set provides; Embedded Controls or Touch Controls don't quite seem right. Greetings, Frederik ___ 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 Quick Controls for Embedded
On Thursday, April 09, 2015 01:19:24 PM Aleix Pol wrote: On Thu, Apr 9, 2015 at 10:27 AM, Tomasz Siekierda sierd...@gmail.com wrote: On 8 April 2015 at 17:35, Oswald Buddenhagen oswald.buddenha...@theqtcompany.com wrote: On Wed, Apr 08, 2015 at 04:39:52PM +0200, Frederik Gladhorn wrote: On Wednesday, April 08, 2015 04:30:23 PM Oswald Buddenhagen wrote: so ideally we find the perfect new name for both module and repository. Sadly we didn't manage to come up with a great name in a few hours of brain storming. i think quick controls 2 will work just fine. it's not like people are not used to asynchronous versioning in the qt quick world. but anyway, here are some more ideas: - the classic: qt quick controls NG - the diet: qt quick controls light - the thesaurus: qt quick widgets - the cynic: qt quicker controls I like QtQuick.LightControls. In general, since both sets are drastically different (in way they look like, in the way they perform, in styling capabilities, etc.) I do not think giving them similar names (Controls 1 and Controls 2) is a good idea - it may strongly confuse the users. Not everybody follows the mailing list and blog, so if you name them similarly you can expect a flood of questions like I'm trying to use the new Controls, but X does not work, and Y looks different, while Z can't read my style definition etc. I'd say it's a matter of whether the current QtQuick Controls will become deprecated (or considered Done). If that's the case, then the new component is the clear N+1 version. The new controls will not support the native look at least for the near future, so we will not deprecate the Qt Quick Controls yet. Also another question is whether they can be mixed. If they can be mixed then you'll want different names. They can be mixed, that's already working, by using import as with just the version as differentiator. That might be less obvious though. Cheers, Frederik Aleix ___ 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 Quick Controls for Embedded
On 8 April 2015 at 17:35, Oswald Buddenhagen oswald.buddenha...@theqtcompany.com wrote: On Wed, Apr 08, 2015 at 04:39:52PM +0200, Frederik Gladhorn wrote: On Wednesday, April 08, 2015 04:30:23 PM Oswald Buddenhagen wrote: so ideally we find the perfect new name for both module and repository. Sadly we didn't manage to come up with a great name in a few hours of brain storming. i think quick controls 2 will work just fine. it's not like people are not used to asynchronous versioning in the qt quick world. but anyway, here are some more ideas: - the classic: qt quick controls NG - the diet: qt quick controls light - the thesaurus: qt quick widgets - the cynic: qt quicker controls I like QtQuick.LightControls. In general, since both sets are drastically different (in way they look like, in the way they perform, in styling capabilities, etc.) I do not think giving them similar names (Controls 1 and Controls 2) is a good idea - it may strongly confuse the users. Not everybody follows the mailing list and blog, so if you name them similarly you can expect a flood of questions like I'm trying to use the new Controls, but X does not work, and Y looks different, while Z can't read my style definition etc. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Quick Controls for Embedded
On Thu, Apr 9, 2015 at 10:27 AM, Tomasz Siekierda sierd...@gmail.com wrote: On 8 April 2015 at 17:35, Oswald Buddenhagen oswald.buddenha...@theqtcompany.com wrote: On Wed, Apr 08, 2015 at 04:39:52PM +0200, Frederik Gladhorn wrote: On Wednesday, April 08, 2015 04:30:23 PM Oswald Buddenhagen wrote: so ideally we find the perfect new name for both module and repository. Sadly we didn't manage to come up with a great name in a few hours of brain storming. i think quick controls 2 will work just fine. it's not like people are not used to asynchronous versioning in the qt quick world. but anyway, here are some more ideas: - the classic: qt quick controls NG - the diet: qt quick controls light - the thesaurus: qt quick widgets - the cynic: qt quicker controls I like QtQuick.LightControls. In general, since both sets are drastically different (in way they look like, in the way they perform, in styling capabilities, etc.) I do not think giving them similar names (Controls 1 and Controls 2) is a good idea - it may strongly confuse the users. Not everybody follows the mailing list and blog, so if you name them similarly you can expect a flood of questions like I'm trying to use the new Controls, but X does not work, and Y looks different, while Z can't read my style definition etc. I'd say it's a matter of whether the current QtQuick Controls will become deprecated (or considered Done). If that's the case, then the new component is the clear N+1 version. Also another question is whether they can be mixed. If they can be mixed then you'll want different names. Aleix ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Quick Controls for Embedded
On Wed, Apr 08, 2015 at 04:39:52PM +0200, Frederik Gladhorn wrote: On Wednesday, April 08, 2015 04:30:23 PM Oswald Buddenhagen wrote: what's the point of keeping them in the same repo when you split it at the top anyway? you just break the uniformity of the repo layout, which is both ugly and traditionally a nightmare build system wise (cf. webkit). The idea was to make code-sharing easy is this actually planned? is it expect to happen to a significant degree? if the answer is yes, then the top-level split is not the right way to go anyway. and to lessen the burden on everyone to check out yet another repository etc. this doesn't sound all that convincing. As for the build system, I see it similar to how the qt5.git meta module behaves - just two subdirs for the qtquickcontrols repo and that's it. i'm already having nightmares. It seems that re-using the name will also cause trouble with documentation and tooling, documentation and any kind of use works on the module level, not at the repo level. so ideally we find the perfect new name for both module and repository. Sadly we didn't manage to come up with a great name in a few hours of brain storming. i think quick controls 2 will work just fine. it's not like people are not used to asynchronous versioning in the qt quick world. but anyway, here are some more ideas: - the classic: qt quick controls NG - the diet: qt quick controls light - the thesaurus: qt quick widgets - the cynic: qt quicker controls ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt Quick Controls for Embedded
Hi all, as announced by JP's blog post, we've been working on a new set of Qt Quick Controls that have slightly different goals than the existing ones: http://blog.qt.io/blog/2015/03/31/qt-quick-controls-for-embedded/ The main target is performance, especially on low end hardware. The code will live in the qtquickcontrols module, next to the existing controls. For now there is only one style supported, with some theming capabilities. This is an important point to get top notch performance. Now is the time to give everyone the chance to play with the new controls which are at a tech preview level. Since the architecture is different, we want to keep a clean separation in the qtquickcontrols git module and will move the code around to accommodate both modules within the repository. The plan is to create two top level directories in the repository: a controls1 directory containing everything currently in the repository (src/tests/examples), and a controls2 directory to contain the new controls. Note that both sets of controls will be co-installable and work together. That is to say, the following will work just fine: import QtQuick.Controls 1.x as Controls1 import QtQuick.Controls 2.x After a long discussion, we think that going with a major version is easiest, as we didn't find a great name that makes it clear what the new control set provides; Embedded Controls or Touch Controls don't quite seem right. Greetings, Frederik ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Quick Controls for Embedded
On Wednesday, April 08, 2015 04:30:23 PM Oswald Buddenhagen wrote: On Wed, Apr 08, 2015 at 03:18:27PM +0200, Frederik Gladhorn wrote: we want to keep a clean separation in the qtquickcontrols git module and will move the code around to accommodate both modules within the repository. The plan is to create two top level directories in the repository: a controls1 directory containing everything currently in the repository (src/tests/examples), and a controls2 directory to contain the new controls. what's the point of keeping them in the same repo when you split it at the top anyway? you just break the uniformity of the repo layout, which is both ugly and traditionally a nightmare build system wise (cf. webkit). The idea was to make code-sharing easy and to lessen the burden on everyone to check out yet another repository etc. As for the build system, I see it similar to how the qt5.git meta module behaves - just two subdirs for the qtquickcontrols repo and that's it. We haven't actually done the merge yet, just tested that it would be feasible, so this is not set in stone. It seems that re-using the name will also cause trouble with documentation and tooling, so ideally we find the perfect new name for both module and repository. Sadly we didn't manage to come up with a great name in a few hours of brain storming. Maybe we just need someone from the outside to come along with a great idea :) Cheers, Frederik ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Quick Controls for Embedded
On Wed, Apr 08, 2015 at 03:18:27PM +0200, Frederik Gladhorn wrote: we want to keep a clean separation in the qtquickcontrols git module and will move the code around to accommodate both modules within the repository. The plan is to create two top level directories in the repository: a controls1 directory containing everything currently in the repository (src/tests/examples), and a controls2 directory to contain the new controls. what's the point of keeping them in the same repo when you split it at the top anyway? you just break the uniformity of the repo layout, which is both ugly and traditionally a nightmare build system wise (cf. webkit). ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
