The thing is... from what I saw in how QPA is done, we might need to have some code upstreamed in Qt5 as well, since we would have to either modify an existing platform (like xcb) to add our themeing there (since no themeing is coded) or write a completely separate platform basing on xcb which we use. Sadly it's not possible to tell Qt5 to 'load all things from the xcb platform just use this plugin here for QPlatformTheme' - it seems to be either all or nothing. Probably there is a way of accessing the xcb theme classes and objects outside of the Qt5 build tree, but I didn't see it right away as all those are theoretically internal.
So, I'm worried that anyway even using the 'right' way to get things implemented, we would need to add things to the Qt5 source. Just in case of the 'right' way, this change could get upstreamed sooner or later... That's actually why in the meantime I decided to backport the Qt4 solution. Since it's a completely new area to discover, plan and implement. I have some things started, but it's still just the first bricks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1126205 Title: [FFe] Bring Unity appmenu / HUD integration to Qt5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1126205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
