Le 04/12/2017 à 18:53, Tomasz Wlostowski a écrit : > On 04/12/17 18:48, Chris Pavlina wrote: >> Hey, just a comment because I see people are wrestling with >> COMPONENT_TREE performance as I did when writing it. TEST ON MACOS. The >> performance of the widget there has a really different profile from on >> other systems. I had to do things in really unobvious ways to make it >> perform reasonably there. >> > > I've noticed spending more and more time fixing wxWidgets bugs instead > of Kicad bugs. Maybe we should have a serious look at Qt or Electron > (Webkit/JS-based UI) as a possible future alternative for wx... > > Tom (fighting with wxWidgets thread safety under Windows...)
Hi Tom, I did not use QT when starting Kicad mainly because it was not free on Windows (only on Linux). But, please, keep in mind the main reason you are not fighting with QT is the fact we are not using QT. I remember coworkers who spent a lot of time to convert their work from QT3 to QT4 ... And QT4 is not the latest version. This is an issue we never have with wxWidgets. When someone say me: you are using this tool, but this other tool has not these issues, well: - Of course this other tool has not these issues. - but this other tool has other issues. So, before spending my time on QT, I want a *proof* we will have really less issues. I do not want just change the list of issues. And until now, I never see this proof. -- Jean-Pierre CHARRAS _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
