View Single Post
Venemo's Avatar
Posts: 1,296 | Thanked: 1,773 times | Joined on Aug 2009 @ Budapest, Hungary
#168
Originally Posted by attila77 View Post
#ifdefs don’t cut it. That was one of the reason Qt was born in the first place.
Qt offers platform-specific APIs for every platform.
This means that if I'd like my app to have the right look and feel for the platform, I'll need to use them.
If you want you app to run on other platforms as well, you should #ifdef them.

(Not to mention the platform-specific UI stuff that Qt has no abstraction for - in this case, direct reference to libraries of that platform are needed.)

Whatever you do on Maemo 5 will look crappy (or out-of-place at best) on Harmattan
Why would it?
I guess QMainWindow and QPushButton and so on will look as defined in Harmattan's theme.
Of course, a little Harmattan-specific APIs here and there (with #ifdefs of course, to keep the app compiling on Maemo 5) and all is well.

And I haven't spoken about Symbian yet - if a Qt app needs to run on different versions of Symbian and on different versions of Maemo (and perhaps desktop?), and wants to maintain the best look and feel on each platform, #ifdefs are inevitable.

You already have three (or four, if the reference UX counts) different ways of doing an UI without the necessary background knowledge or insight to make a stategic decision which one to use.
What are those different ways?
I'm asking out of curiousity, as I'm quite new to Qt.

And a general comment - ’smartness’ of developers have nothing to do with it. That’s like saying Qt doesn’t need documentation
My point didn't have anything to do with Qt or its documentation.
My point was for a non-developer who assumed that developers would get confused.

A clear structure (naming included) helps *everyone* interested in the platform.
As I say the n-th time here: agreed!

Last edited by Venemo; 2010-06-12 at 10:09.