Consider migrating from Gtk to Qt

Hi dipen,

We are not going to be moving to the Qt framework anytime soon.
Gtk+ is a well-developed application framework, and we make extensive use of Gtk+ objects in our dialogs and widgets already. We also are unable to consider using Qt because doing so requires using compiler extensions, as where Gtk+ is written entirely in C, and gtkmm is written entirely in C++, no compiler extensions required.

Your claim "[In Qt,] we can solve bugs quickly, and we can develop faster" (previously "We Can Solve Fast Bug.and We Can Develop Fast") is entirely dependent on how much experience you have had with either framework — I personally have little experience with the Qt framework, and in the process of migrating I would not really have any idea what I was doing, probably introducing far more bugs than I fixed.

Also, as mentioned in one of our FAQs, we are rather opposed to the idea of migrating to Qt. I myself much prefer Gtk+ because it is more flexible in regard to many things such as theming, and on Linux, the Qt framework has many extra dependencies that we would have to change to satisfy. We would also have to deal with a framework that doesn't know much about the current way we use SVG paths and can't render SVGs well without extra dependencies.

With Windows builds, we would have to recompile all of our developer libraries (lp:inkscape-devlibs and lp:inkscape-devlibs64) and that is an extremely time-consuming process, perhaps taking several weeks to do in our free time. KDE may or may not provide pre-compiled libraries, but collecting the right ones and finding the extra ones we need could similarly take several weeks.