Building simple GUIs: Is wxPython still the recommended method?

I’ve been away from GNU Radio for a bit and wanted to ask… is wxPython
(and
the included wrappers) still the recommended means of building simple
GUIs? Or
has it been supplanted by, e.g., “something Qt” or similar?

Thanks,
—Joel

On Wed, Apr 20, 2011 at 12:38 PM, Joel K.
[email protected]wrote:

I’ve been away from GNU Radio for a bit and wanted to ask… is wxPython
(and
the included wrappers) still the recommended means of building simple GUIs?
Or
has it been supplanted by, e.g., “something Qt” or similar?

Thanks,
—Joel

This isn’t a really clear-cut issue right now. I prefer the gr-qtgui
(which
uses Qt and QWT as well as their Python versions), but qtgui is still
missing a few features that would really make it production-ready. I’m
working in these things now, though. I find the Qt implementations to
have a
better look and feel than the Wx stuff, and the concept of signals and
slots
gives it a lot of power, which I am working on building more into the
UI.

However, like I said, qtgui is still lacking in some areas and the wxgui
interface is a bit more seasoned. It, too, is missing some features, I
think.

My recommendation is to look at qtgui and see if it does what you want.
It’s
easy to make qtgui apps now in GRC if you are working off the latest
from
Git.

Tom

On 21/04/2011 10:15 AM, Tom R. wrote:

---Joel

This isn’t a really clear-cut issue right now. I prefer the gr-qtgui
(which uses Qt and QWT as well as their Python versions), but qtgui is
still missing a few features that would really make it
production-ready. I’m working in these things now, though. I find the
Qt implementations to have a better look and feel than the Wx stuff,
and the concept of signals and slots gives it a lot of power, which I
am working on building more into the UI.

My main hope for Qt-GUI is that it will exercise fewer edge cases (or
not use at all) in OpenGL. I have an app that still, occasionally,
dumpeth the core on some platforms due to bugs deep in the bowels
of the OpenGL “ecosystem”.

But I agree that gr-qtgui as it currently exists is missing some
features that would make it production-ready, including splitting out
the individual components of the current qtgui “megasink”, and
strip-chart type features (basically, everything that wxgui currently
has).

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs