On 11 March 2013 10:17, C. Boemann <c...@boemann.dk> wrote: > On Sunday 10 March 2013 Mar, Yuë Liu wrote: >> What's your opinion on this? At leaset we need all the application >> maintainers' support. > > I don't think this is the right way to go. If we want it to look good on osx, > we should work on the qstyle, which will benefit other projects as well. It > may > never look completely native but I'm sure it can be made to look much better.
As I said, QStyle should be available, yes. But alone it's not enough. Existence of extra types for buttons shows this - it's up to app developer to actually set the flags for buttons to make the look & feel more compliant with the Mac Guidelines http://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/AppleHIGuidelines/Intro/Intro.html QStyle itself or even KStyle and friends have no APIs for these buttons because, well, QStyle abstracts somehow common denominator of HIG implementation. Recently there was a thread on qt-devel list, filled with good points: http://lists.qt-project.org/pipermail/development/2013-March/010294.html A question that most interest me here is: how to enable developers to find-tune the code for specific HIGs without blurring the code for other targets. -- regards / pozdrawiam, Jaroslaw Staniek Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org Qt Certified Specialist | http://qt-project.org http://www.linkedin.com/in/jstaniek _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
