I'm not directly involved in this discussion line but would like to offer my opinion on a point.
I have tried the commercial version and it was great because it offered all functionality of the full version of MSVS for GUI forms development. But Express Edition does not provide the ability to design GUI forms like the full MSVC version does. So Qt addins, even if MSVC allowed it, doesn't buy a lot. I was frustrated by this until I found out that the Qt addin is a mute point. All I had to do was add the Qt Developer as an executable to the Express Edition. Then when I double click the .ui files it automatically launches Develop for me. The .ui files are stored in my Express Edition project folder, so it appears (almost) seamless insofar as development is concerned. However this did not turn out to be big deal. The only other process that is required is to manually create a C++ class for each .ui file. After doing one then it is a no-brainer. Hence for all practical purposes Qt integrates very well with Express Edition, but the only difference is that it requires a couple of extra manual sets, none of which are hugely intrusive: * Add the Developer executable to Express Edition so that double clicking the .ui file launches Developer - this provides the ability to do forms development * Add the custom build rules that create the moc and ui files for building your application * And finally be sure to create a class that derives from QObject for each .ui file. There more details of course, but instructions that cover these in detail are available in the Qt community site. Doing it the first time is manual and of course nobody likes that, but once done it is easy to work with. I did this so long ago that frankly I can't remember the details, so I suggest a search of the Qt community site for instructions on using Express Edition HOWEVER, it would be very nice if Nokia would add these details to the installation and configuration content in Assistant! I find the Express Edition approach to be of high value because our small business gets a full development environment, using Qt, for free. Some manual steps are involved for setup and some in development, which can be a minor pain but it sure beats paying. These are just some thoughts from someone who in the past was frustrated about the Qt integration with MS C++. Regards, George George Shannon President, Raphael Analytics, Inc. 16 Spur Fenton, MO 63026 (314) 550-5589 (cell) [email protected] The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andrey Ivanov Sent: Saturday, March 07, 2009 9:56 AM To: Thiago Macieira Cc: [email protected] Subject: Re: [Qt4-preview-feedback] qt-vs-addin-1.0.0-beta.exe doesn't work I am very appreciative for QtCreator. But if QtSoftware didn't make support for Visual Studio Express Edition, it would be massive mistake (except if QtSoftware is Microsoft's partner and wants to increase sales of commercial Visual Studio). Is it so difficult to make addin for VS Express? В сообщении от 7 марта 2009 18:34 Thiago Macieira написал(a): > Андрей Иванов So wrote: > >So, VS addin can't detect Visual C++ Express Edition SP1. > > I don't think you can have addins for the Express Edition. > > Please upgrade to the full version or use Qt Creator. -- _______________________________________________ Qt4-preview-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
_______________________________________________ Qt4-preview-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
