2011/4/6 Arjan van de Ven <[email protected]>: > On 4/5/2011 7:47 PM, Tracy Graydon wrote: >> >> Hi, >> >> Meegotouchcp-bluetooth is failing in T:T. I did a little digging and it >> appears that the meegotouch-controlpanel changes may be related, sort of >> indirectly. Namely the /usr/lib -> /usr/share thing. (BMC#15144) > > is any vertical actually using the MT control panel? > I know the recently released UX is not... > > we should remove the packages if nobody has been using these...
We're still using the MT control panel on N900 images (and rest of handset-* images), though the new QML one looks/is delicious, it doesn't integrate properly into systems with sysuid just yet (seperate status bar impl). We're still investigating the use of UX on N900*. It should also be assumed there might be non-public users of MeeGo 1.2 track + Handset UX. Since 'tablet' UX was dropped in quite late in the process and developed in secret, it is fair that it should not break any other verticals that has been more or less stabilized for 1.2. Let's get 1.2 out the door, plus the stated 'pre-alpha' tablet UX and then do the big switch in 1.3. Again, as stated on IRC, since even Imad called UX 'tablet user experience', please provide 5 lines that states the intended direction of UX and where it should be used. I've heard IVI, Handset, Tablet on IRC and you've suggested Netbook in some emails, but a coherent and straightforward official message on where UX is used would be good. Until then, don't remove any Handset UX related packages or break Handset UX experience. Thank you, /Carsten Munk * http://wiki.meego.com/ARM/N900/TabletUX > > _______________________________________________ > MeeGo-packaging mailing list > [email protected] > http://lists.meego.com/listinfo/meego-packaging > _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
