Originally Posted by egoshin

For a moment I build it on N900, following your instruction in other thread.

EDIT: It again failed in opengl check -

"The EGL functionality test failed!
EGL is required for OpenGL ES to manage contexts & surfaces.
You might need to modify the include and library search paths by editing
QMAKE_INCDIR_EGL, QMAKE_LIBDIR_EGL and QMAKE_LIBS_EGL in
/root/qt4-x11-4.6.2~git20100401/mkspecs/linux-g++-maemo5."

Both packages - opengles-sgx-img-common-dev and libgles2-sgx-img-dev are installed as so as non "-dev" versions.

Originally Posted by attila77

They cannot have *identical* widget sets as the functionality is different on various platforms, but you will certainly get a lot less #ifdefs than you would by making separate MTF, Orbit and QWidget UIs.

Originally Posted by cristids

I don't want my application to look different in symbian than meego or maemo. I mean we are talking about mobile devices having almost same screen size/resolution. There are four mobile os-es supported right now, why should one think an application needs to look different in any of them?
Well I now that the look and feel of a button is not same on meego vs symbian but that doesn't mean I need a button class for each.

Originally Posted by attila77

Because the UI paradigm *is* different on these OSes, either due to historical reasons or because of HW form factors (they definitely do NOT have nearly the same size/resolution and screen/kbd). This is not about just a QPushbutton, that we could get over easily, but rather how much part of the OS the app feels. I agree that the #ifdeffing should be done away with or at least minimized, but you cannot so easily forego platform specifics (Components is no silver bullet but at least it makes the mess more manageable). As said, QPushbutton is easy, but what do you do with Symbian softkeys, Maemo's stacked windows, funky pickers, application menus, file management, etc. I know, I know 'not my problem', but am just saying that after doing a project or two you *will* realize that you don't *really* want your apps to look literally the same on all platforms, the best Qt can do is to help you minimize the pain.

Originally Posted by daperl

Yes, the build failed. I'll take a closer look at the errors tomorrow, but from a quick glance I think it was gl related.

Originally Posted by cristids

Please explain to me how N900 is different in HW form factor than N8 or newer symbian devices bearing Qt. They all have touch screens that are about same size. I assume N9 or whatever name will have will be somwhere between 3 and 4.5 inches.

None of the elements you mention must be os specific. I mean I would've have them all put under Qt umbrella. If I want soft keys implemented that is fine, I put the code in Qt, making a note that it is only symbian supported. Meego finds out that it needs soft keys, here they are,we enable them in qt. But each with its own set of controls it is simply bad design and bad interaction between architects. I understand that they choose the shortest path but eventually this will strike back as Qt doesn't deliver on its promise. Instead they should've plan better and when a UI component is needed implement it in all platforms, make it look the same and everybody would've been happy.

Originally Posted by daperl

Yes, the build failed. I'll take a closer look at the errors tomorrow, but from a quick glance I think it was gl related.

Originally Posted by w00t

well, you make one mistake in leaving 'hardware acceleration' under MTF, as QML can also be hardware accelerated (as can QWidget), and likewise, MeeGo Touch can use software rendering, so there's no functional difference between the three there