Use wxWidgets for the GUI about efte HOT 7 OPEN

The toolkit alone doesn't cause slowness or ugliness; it is how the toolkit is being used.

from efte.

Using wxWidgets would certainly help creating GUI versions for platforms that don't have one yet. However, I would keep wxWidgets as an optional dependency; making it a requirement for compiling efte would be pretty annoying in some scenarios.

from efte.

I'm currently using CodeBlocks on Linux. It is based on wxWidgets. Compared with Qt Creator it is horribly slow and ugly :(
I would prefer to eFTE went in the direction such as the SublimeText.

from efte.

from efte.

Not exactly. wxWidget works on X11, Gtk or Qt. On X11 is very ugly. On Gtk is very buggy and slowly. On Qt I don't know. I did not use it.

I have been using wxWidgets at work for more than 10 years, so I know a thing or two about it. And it is not "very buggy and slowly" on Gtk. Sure it is possible to make buggy and slow programs with it, but again, it is about how it is being used.

from efte.

I side with lanurmi on this. I've been using wxWidgets off and on for more than 15 years on multiple platforms and been very happy with it's native look and feel and it's great performance (including some animation). I also use a number of application based on wxWidgets and have not experienced any slowness, ugliness or bugs.
wxWidgets uses the native GUI (admittedly there are choices to make on *nix so it introduces a little complication that Mac, Win, etc doesn't have, but what commonly used *nix doesn't have GTK these days?). From the wxWigets site, "...and unlike other cross-platform toolkits, wxWidgets gives applications a truly native look and feel because it uses the platform's native API rather than emulating the GUI."
Besides, Qt, I feel, is much harder to code for. I abandoned KDE because I didn't like Qt. I will not install an application based on Qt. But that's just MHO and not meant start a flame war.

from efte.

from efte.