| Trolltech Home | Qt4-preview-feedback Home | Recent Threads | All Threads | Author | Date | |
| All threads index page 1 | |
Hi, Here's a couple of suggestions for improvements with the latest Qt Eclipse Integration, gathered from working with it on bigger scale projects : - Better integration with the project's Include Paths and Symbols during .pro file import : the integration plugin automatically adds the include paths for Qt in the project's include paths and symbols, which is a good thing already, but it doesn't extract those contained in the .pro files. So if you have extra include paths for your project, and symbols defined e.g. for DLL export macros, the indexer will not recognize them and it will be confused. These can still be added manually, but it can become tedious for big projects, and it feels like a duplication of work and information considering the information is already in the .pro files. However I realise that this would take the integration plugin to a new level, with the ability to extract information from .pro files and add it to the eclipse project. I guess it can be possible though, since you can already manipulate the project settings to insert general Qt settings, and it could be limited to Include paths and symbols in a first time. Having this feature would make the indexer even more accurate and improve further the user experience. - Finer settings for the Qt Makefile generator : currently the .pro files are reparsed for every build, which can end up in a big amount of mostly unnecessary time spent when all you did is changed a .cpp file. For now I just disable the builder unless I explicitely need it, but I saw that for the CDT makefile builder you can open a property page (by clicking "Edit" after selecting the builder) which allows you to fine tune when the builder should be run. Something similar would be nice for the Qt Makefile generator, e.g. with an option to only run it for a specific target like "all", or even better if it could somehow receive notifications from the .pro file handler whenever a project has changed. (by .pro file handler I mean the component that watches changes in the filesystem and pops up a dialog whenever files are added or removed from the project) Other than that I must say that the current integration already kicks some serious *ss :-) Best regards -- [ signature omitted ]
Attachment:
pgpNdoAgknyH6.pgp
Description: PGP signature
Hi Romain, thank you for good suggestions! On Oct 9, 2007, at 8:41 PM, Romain Pokrzywka wrote: > Hi, > > Here's a couple of suggestions for improvements with the latest Qt > Eclipse Integration, gathered from working with it on bigger scale > projects : > > - Better integration with the project's Include Paths and Symbols > during .pro file import : the integration plugin automatically adds > the include paths for Qt in the project's include paths and > symbols, which is a good thing already, but it doesn't extract > those contained in the .pro files. > So if you have extra include paths for your project, and symbols > defined e.g. for DLL export macros, the indexer will not recognize > them and it will be confused. > These can still be added manually, but it can become tedious for > big projects, and it feels like a duplication of work and > information considering the information is already in the .pro files. > However I realise that this would take the integration plugin to a > new level, with the ability to extract information from .pro files > and add it to the eclipse project. I guess it can be possible > though, since you can already manipulate the project settings to > insert general Qt settings, and it could be limited to Include > paths and symbols in a first time. > Having this feature would make the indexer even more accurate and > improve further the user experience. Yes, we can probably do some stuff going in this direction. We already have all information about the .pro-files available, so it would "just" need synchronization with the CDT settings. > - Finer settings for the Qt Makefile generator : currently the .pro > files are reparsed for every build, which can end up in a big > amount of mostly unnecessary time spent when all you did is changed > a .cpp file. > For now I just disable the builder unless I explicitely need it, > but I saw that for the CDT makefile builder you can open a property > page (by clicking "Edit" after selecting the builder) which allows > you to fine tune when the builder should be run. > Something similar would be nice for the Qt Makefile generator, e.g. > with an option to only run it for a specific target like "all", or > even better if it could somehow receive notifications from the .pro > file handler whenever a project has changed. (by .pro file handler > I mean the component that watches changes in the filesystem and > pops up a dialog whenever files are added or removed from the project) Right, calling qmake recursively on a larger project can take some time. We'll think about how "automatic" that can be. > Other than that I must say that the current integration already > kicks some serious *ss :-) Thanks a lot :) Eike To unsubscribe - send "unsubscribe" in the subject to qt4-preview-feedback-request@xxxxxxxxxxxxx