Random Notes on the wxQT port.
Hello everybody
I recently decided to check out the wxQT port of wxWidgets. I was hoping for a bridge into the great unknown of Android. While wxQT has been around for several years, the documentation is still very, very scarce.
I did get wxQT built for android but using it is another issue altogether. There is proof that wxQT runs on Android, here are some references:
https://groups.google.com/forum/#!to...ev/LUyC7Gn6aCE
wxQt Android Notes by Mariano Reingart also includes screenshots
As far as I could find, OpenCPN is currently the only Android app avalible that uses wxWidgets. Building instructions are HERE.
So I put Android on the back burner for now and decided to look at the plain wxQT for Linux. I was able to build it with no problems. I used QT 5.8 and wxWidgets 3.1.1 for my experiment. I was then able to build several wx samples and several of my own apps as well.
What wxQT is actually Like:
The wxQT port is amazingly complete as far as dialogs and widgets are concerned, however it is still pretty rough when it comes to actually using them.
Several things I Noticed in the little bit of time I spent: NOTE, these are without tweaking anything in the samples or wxWidgets 3.1.1 and these issues might be fixed already.
A lot of things do work. Check out the wxQT port status.
I'm also keeping my eye on the wxQT port for HaikuOS. I seen somwhere they're even porting Audacity. Running wx on Haiku will likely be somthing I'll do before too long.
EDIT: WxQT does in fact build and run under Haiku, just install the qt5 development package via Haiku-Depot and grab the master wxWidgets from github and ./configure and make it. make install will not work since the root filesystem is read-only. You'll have to add the lib dir to LIBRARY_PATH before running a wx app.
So why mess with wxQT instead of switching to QT? Some of my reasons:
So I'm hoping wxQT takes off.
I recently decided to check out the wxQT port of wxWidgets. I was hoping for a bridge into the great unknown of Android. While wxQT has been around for several years, the documentation is still very, very scarce.
I did get wxQT built for android but using it is another issue altogether. There is proof that wxQT runs on Android, here are some references:
https://groups.google.com/forum/#!to...ev/LUyC7Gn6aCE
wxQt Android Notes by Mariano Reingart also includes screenshots
As far as I could find, OpenCPN is currently the only Android app avalible that uses wxWidgets. Building instructions are HERE.
So I put Android on the back burner for now and decided to look at the plain wxQT for Linux. I was able to build it with no problems. I used QT 5.8 and wxWidgets 3.1.1 for my experiment. I was then able to build several wx samples and several of my own apps as well.
What wxQT is actually Like:
The wxQT port is amazingly complete as far as dialogs and widgets are concerned, however it is still pretty rough when it comes to actually using them.
Several things I Noticed in the little bit of time I spent: NOTE, these are without tweaking anything in the samples or wxWidgets 3.1.1 and these issues might be fixed already.
- TextCtrl doesn't Clear(), therefore if you use Clear() and then Append("Some Text") things do get messy. Edit: there is a work-a-round to fix this.
- TextCtrl don't work to input text, without some tweaking aleast.
- ListCtrl doesnt send unselect event.
- For some reason No static text, this is a big limit.
Edit: static text does work great, but Wrap(-1); does not currently.
A lot of things do work. Check out the wxQT port status.
I'm also keeping my eye on the wxQT port for HaikuOS. I seen somwhere they're even porting Audacity. Running wx on Haiku will likely be somthing I'll do before too long.
EDIT: WxQT does in fact build and run under Haiku, just install the qt5 development package via Haiku-Depot and grab the master wxWidgets from github and ./configure and make it. make install will not work since the root filesystem is read-only. You'll have to add the lib dir to LIBRARY_PATH before running a wx app.
So why mess with wxQT instead of switching to QT? Some of my reasons:
- I like the ability to select the gui toolkit for my app without reprogramming it.
- QT is HUGE and bloated, and no matter what they say, it is just not Native like wx.
- For a Small app that only needs to run on a minimal system, I can build wx with just plain x11, no need for gtk.
So I'm hoping wxQT takes off.
Total Comments 0
