I would also suggest avoiding wx. I've been using it and have just found it to be convoluted and counter-intuitive, and while it is cross-platform I've found some annoying discrepancies which appeared when porting from windows.lb wrote:I can only recommend to use GTK (with the excellent PyGTK bindings) directly instead. wx is badly designed, badly documented, buggy and a lot of bloat. The Python bindings are a mess, too.
I've used a lot of UI toolkits, and wx is about the worst I've seen yet.
I disagree strongly with this observation. I am the original author of wxLua (wxlua.sourceforge.net) - which runs fine on the Pi BTW, and I had very few problems with wx. There were are very few incompatibilities between the platforms. Wx and wxPython is used by many shipping applications.Aquaticpenguin wrote: I would also suggest avoiding wx. I've been using it and have just found it to be convoluted and counter-intuitive, and while it is cross-platform I've found some annoying discrepancies which appeared when porting from windows.
Hicbegg50 wrote:If I want to run RocRail model train control software, I have no choice. WxWidgets is what it uses for cross-platform graphics. RocRail runs on PC, MAC and various flavours of Linux (Raspberry Pi varieties now included). I don't doubt there are better graphics toolkits, but I don't fancy writing my own DCC software from scratch, when RocRail works so well.
Have you been able to get GTK to build on the RPi?lb wrote:I can only recommend to use GTK (with the excellent PyGTK bindings) ...
Code: Select all
/home/gbriggs/raspberrypi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/../lib/gcc/arm-linux-gnueabihf/4.7.2/../../../../arm-linux-gnueabihf/bin/ld: cannot find -lgtk-3 ... // followed by one for each of the included libraries, then the whole 11 errors are repeated again (once for each library)
Users browsing this forum: No registered users and 5 guests