On 08/10/2011, at 6:07 AM, Harri Porten wrote: > On Fri, 7 Oct 2011, craig.sc...@csiro.au wrote: > >> Desktop apps won't be going away any time soon, and there are some >> rather big commercial companies who would likely make some noise if Qt >> on desktop was being neglected. > > Were and how will they make that noise? Remember that Nokia has freed > themselves of the commercial Qt sales and support business. That freedom > is now being used for experiments with new approaches. There are service > providers for classic QWidget-based programming but when it comes to new > developments the market still has to be established.
Hi Harri, I understand why you might also have some interest in this area (we are one of your customers!). Since I have no affiliation with Autodesk, I don't want to speculate on any specifics here. My point is more that Autodesk obviously made a business decision to rewrite Maya to be based on Qt, specifically its QWidgets. They surveyed their community of plugin developers more than once to gauge interest before they did this and since they went ahead with it, one can assume they deemed it worth the effort. Should they encounter problems with Qt's QWidgets where those problems have a strong negative impact on their product, they will simply have to find a way to address them. Being a big company (hence more $$$ and manpower), they should have more options open to them than a smaller business might. Whether they would find working through Digia to be the most effective or whether they engage with the wider Qt development community more actively, my main point is that their n eed to keep their customers happy will drive them to find a solution. And they should have the means to do so. Currently, they rely on the LGPL version of Qt and they make available all their customisations on their website. Their community of plugin developers also rely on the LGPL version as a consequence. One would hope that the rest of the Qt community would benefit from any steps Autodesk found they had to take. I'm just using Autodesk as one example here, purely because I'm more familiar with them (we are part of the community of plugin developers for Maya). I don't want to distract from the main discussions on this list. I was more hoping to simply point out that there are plenty of companies that rely on Qt's current QWidget functionality. For those who can't or don't want to change from QWidget in the medium term, there will be a collective need to see the QWidget-based capabilities maintained at least at some modest level. Those with the deeper pockets are probably more likely to have more options. -- Dr Craig Scott Computational Software Engineering Team Leader, CSIRO (CMIS) Melbourne, Australia _______________________________________________ Qt5-feedback mailing list Qt5-feedback@qt.nokia.com http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
