> To me trying to wrap the API is just a way to do things more complicated, for > the sake of making it more complicated.
The programs I was thinking would benefit from something like this in particular are the ones that have been built on top of C and GTK, and would maybe like to switch now that GTK seems to be hell-bent on forcing GNOME's design on all of its apps and users. Many of these programs are built on top of years of C code, so I don't think it would be easy for the developers of those programs to switch from C to C++ even if they wanted to. > It can often be a work of difficult diplomacy to get a project to add > support between c/c++ . Having already done the work can open more > avenues and get more people interested. I've been able to make some external bindings for common widgets using inline functions. It's uploaded here on github <https://github.com/sammonius/qtc>. I hadn't known how large Qt was when I started that project, so I was going to try starting from scratch by making a script that generates bindings from Qt's header files, but I wanted to see if having it built-into Qt was an option first.
_______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
