Considering Qt for WinCE

[SilentVOX]

Hi all,

I am considering to learn and use Qt to develop a navigation software for WinCE 6. However i'm worried if I will be able to do the following things in Qt

1. I need to connect to WinCe comm port

2. I need to make use of custom fonts

3. Does Qt have it's own 2d rendering engine or it wraps gdi? I want antialiasing.

Can anyone tell me how to do that in Qt.

Thanks

[DenisKormalev]

1. There are some libraries for com-ports at qt-apps.org
2. Antialising is available in Graphics Framework (you can read more in Assistant)

[SilentVOX]

Or, considering it's C++, can I simply call WinAPI functions and interact with them ?

[DenisKormalev]

Of course you can use platform-specific libraries and APIs. But I think it will be better first to discover is there needed functionality in Qt or not. Just in case if you will want port it to another platforms in one moment and for better look of you sources too.

[snowpong]

1. I need to connect to WinCe comm port

There is no direct support in Qt for doing this. But no big problem, you'd just have to write some C / C++ code calling whatever Microsoft provides for communicating with the ports.

2. I need to make use of custom fonts

I'd just try and install the font on the device, then run the example spesified here http://doc.qt.nokia.com/4.6/qfontdatabase.html#details to get the list of all the fonts it finds to see if Qt picks it up.

Or you could try and just load it directly: http://doc.qt.nokia.com/4.6/qfontdatabase.html#addApplicationFont - I'm not sure if it works for WinCE though :)

3. Does Qt have it’s own 2d rendering engine or it wraps gdi? I want antialiasing.

Yes, Qt has it's own rendering engine. It doesn't use GDI for anything but blit - so yeah, you get antialiasing.

Good luck :)

[kalle]

You also need to be prepared that you will hit WinCE's resource limits very quickly if you are just using a stock Qt for Windows CE. You need to slim down Qt considerably by removing the parts you don't want/need in your application. Doing without QtWebkit goes a long way, for starters.