Hi,
On 31/03/11 11:57, Andrew Flegg wrote:
There's been some confusion, and I hope to get this clarified before
everyone's scratching their head:
* What is the relationship between MeeGo UX Components and
Qt Components[1]?
I talked (briefly) with Rusty on IRC about this last night, and was told
that the MeeGo UX components' "long term" future so to speak lies with
Qt Components. Relevant part of discussion snipped below:
03/30@23:57:43 <rustylynch> if the re-layout was faster (so the user
didn't notice it), then this wouldn't be an issue
03/30@23:58:00 <w00t_> that's true
03/30@23:58:10 <w00t_> ideally, we need to tell the app we're about to
show it
03/30@23:58:11 <rustylynch> i know the new meego-ux-components has a
much better implementation for this, but i haven't
verified if it's good enough to hide the
relayout
03/30@23:58:21 <w00t_> ooh
03/30@23:58:23 <w00t_> is this in git?
03/30@23:58:25 <rustylynch> yea, we need an about-to-show signal
03/30@23:58:26 <w00t_> I can probably poke it
03/30@23:58:39 <rustylynch> yes, there is a meego-ux-components project
03/30@23:59:02 <rustylynch> this is what we actually want to use, and
are in process of migrating stuff out of
meegolabs-ux-compnoents
03/30@23:59:36 <rustylynch> meegolabs-ux-components (imported as
MeeGo.Labs.Components) is what we started with, before
qt-components was far enough along to build off
Day changed to 31 Mar 2011
03/31@00:00:12 <rustylynch> i'm being told by the maintainers that they
are ready to start doing a massive porting of the
apps
03/31@00:00:28 <w00t_> okay, and what's meego-ux-components then? an
implementation of the Qt Components APIs?
03/31@00:00:46 <rustylynch> it builds on top of it
03/31@00:00:53 <w00t_> cool
Best regards,
--
Robin Burchell
http://rburchell.com
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
