MeeGo UX Components: what about integrating them into MeeGo SDK?

[a***@public.gmane.org]

Hi,

I know that MeeGo UX Components are not finished yet, but I think it
could be a nice idea to include them in the MeeGo SDK, for many
reasons:

1) The developer won't notice the line error in QML source code, since
they would become a recognized package.

2) Having these components already installed both on SDK and MeeGo
tablet image would mean more testers for these components.

3) It would be nice to be able to use them even on Simulator and QEMU
image by default.

Please let me know what you think about this.

Regards,

[Ville M. Vainio]

Post by a***@public.gmane.org
I know that MeeGo UX Components are not finished yet, but I think it
could be a nice idea to include them in the MeeGo SDK, for many

...

I would go one step further and integrate them to the desktop &
simulator target in Qt SDK proper (as an "experimental" component),
for the simple reason that they don't really collide with anything
else.

[oleh Vasyura]

Unfortunately I am afraid that it will not be happened.
Qt SDK is managed by Nokia and Nokia is not interested in supporting MeeGo
anymore.
And perhaps will not be integrate MeeGo UX Components into Qt SDK.

Post by Ville M. Vainio

Post by a***@public.gmane.org
I know that MeeGo UX Components are not finished yet, but I think it
could be a nice idea to include them in the MeeGo SDK, for many

...
I would go one step further and integrate them to the desktop &
simulator target in Qt SDK proper (as an "experimental" component),
for the simple reason that they don't really collide with anything
else.
_______________________________________________
MeeGo-sdk mailing list
http://lists.meego.com/listinfo/meego-sdk
http://wiki.meego.com/Mailing_list_guidelines
http://meego.com/developers

[Gabriel M. Beddingfield]

Post by oleh Vasyura
Unfortunately I am afraid that it will not be happened.
Qt SDK is managed by Nokia and Nokia is not interested in
supporting MeeGo anymore.
And perhaps will not be integrate MeeGo UX Components
into Qt SDK.

Please don't spread FUD like this. This is false.

Qt merges new features based on merit, not Nokia. Qt and
MeeGo devs are still working together.

-gabriel

[Spencer, Bob]

-----Original Message-----

Post by oleh Vasyura
Unfortunately I am afraid that it will not be happened.
Qt SDK is managed by Nokia and Nokia is not interested in supporting
MeeGo anymore.

Nokia's Qt leadership has continued to strongly engage with the MeeGo team to work on a common goal of creating the best development experience now and in the future.

Post by oleh Vasyura
And perhaps will not be integrate MeeGo UX Components into Qt SDK.

Please don't spread FUD like this. This is false.
Qt merges new features based on merit, not Nokia. Qt and MeeGo devs are still
working together.

True.
The Qt team has created something called "Qt Components" which are a different implementation of QML components. MeeGo was interested in these before meego-ux-components were created but they are not open source. In the future if/when this code is opened we'll look at how to merge the projects for a single set of QML components. Having pre-defined, standard components for QML is very important for adoption and ease of use. For MeeGo today that is meego-ux-components.

Bob

-gabriel
_______________________________________________
MeeGo-sdk mailing list
http://lists.meego.com/listinfo/meego-sdk
http://wiki.meego.com/Mailing_list_guidelines
http://meego.com/developers

[Spencer, Bob]

-----Original Message-----
Hi,
I know that MeeGo UX Components are not finished yet, but I think it could be a
nice idea to include them in the MeeGo SDK,

Agree. We have started documenting their use and hope they are widely used by MeeGo developers. They will be supported in the future. We are now working with the maintainers to understand when and how they could be made more part of the SDK.

1) The developer won't notice the line error in QML source code, since they
would become a recognized package.
2) Having these components already installed both on SDK and MeeGo tablet
image would mean more testers for these components.
3) It would be nice to be able to use them even on Simulator and QEMU image
by default.

For the simulator we need to make sure there are no external (non Qt/QML) dependencies. The first version depended on dbus and contained some more low-level logic which I think has since been broken out into a separate package.

Please let me know what you think about this.

It is on the list of many things to do. Probably in an SDK update in a couple of months.

Bob
MeeGo SDK architect

Regards,
--
Andrea Grandi - Nokia Qt Ambassador
website: http://www.andreagrandi.it
_______________________________________________
MeeGo-sdk mailing list
http://lists.meego.com/listinfo/meego-sdk
http://wiki.meego.com/Mailing_list_guidelines
http://meego.com/developers