[Qt-creator] Project Tree

[GreyGeek]

 From the qmake manual and tutorial:

include(SUBDIRS)r

Where SUBDIRS is populated the same way CONFIG and other qmake variables 
are.  See the QMake tutorial for an example.

GG

Porfirio wrote:
> Yes, if Qt Creator gives an option to follow the folder structure would 
> be good enought ;)
>
>
> Em 24-03-2009 13:55, eike.ziller at nokia.com escreveu:
>   
>> Hi,
>>
>> what is the reason for "virtual" folders? Why is important to you to have virtual folders in contrast to just putting the aboutdialog.* files in a real subdirectory "about"?
>>
>> SOURCES += main.cpp \
>>     mainwindow.cpp\
>>     about/aboutdialog.cpp
>>
>> etc?
>> I know that QtCreator doesn't map the filesystem folders in folders in the tree atm, but what if it would?
>>
>> All in all, the project tree is not a very efficient way of navigating anyway - though sometimes helpful if you just can't remember at all how some file was named. So that's why it is there at all ;-). But as long as you have a rough idea about a file name, method name, or class name, using "Locator" (or "Follow Symbol") is usually better suited IMO.
>>
>> Best regards, Eike
>>
>> ________________________________________
>> From: qt-creator-bounces at trolltech.com [qt-creator-bounces at trolltech.com] On Behalf Of ext Porfirio [porfirio.ribeiro at sapo.pt]
>> Sent: Tuesday, March 24, 2009 12:03
>> To: qt-creator at trolltech.com
>> Subject: Re: [Qt-creator] Project Tree
>>
>> Well QtCreator creates a file calledyourproject.pro.user to save project settings, so i guess it could be stored there
>> Or maybe use comments on pro file like
>>
>> SOURCES += main.cpp \
>>
>>                          mainwindow.cpp \
>>
>>                          aboutdialog.cpp             #/about
>>
>>
>> HEADERS += mainwindow.h \
>>
>>                          aboutdialog.h                 #/about
>>
>>
>> FORMS     += mainwindow.ui \
>>
>>                          aboutdialog.ui                #/about
>>
>> Would be ignored by qmake and the ide could understand it
>>
>>
>> Em 24-03-2009 10:07, Sam Clegg escreveu:
>>
>> On Fri, 2009-03-20 at 09:58 +0100, Albert Graells Rovira wrote:
>>
>>
>> Another vote for this proposal :)
>>
>>
>>
>> And anther vote for this.
>>
>> Really we'd like to see a fully flexible hierarchy in the file view
>> where groups can be configured independently of the filesystem layout if
>> necessary (which is possible in, dare I say it, msvc).  I know its
>> tricky since qmake doesn't natively support logical groupings of files
>> but presumably this grouping information doesn't have to live in the
>> qmake file.
>>
>>
>>
>>
>>
>> 2009/3/20 Kuiper, Luuk<kuiper at hitt.nl><mailto:kuiper at hitt.nl>
>>
>>          We deal we great projects as well. And they subdivide in in
>>          subdirectories, but it has to lead to one library.
>>          So we do not use sub-project for that.
>>          And, yes, I also like very much to see a tree structure in the
>>          file
>>          overview that is organized as the file tree on the disk.
>>
>>          Luuk
>>
>>
>>
>>
>>          -----Original Message-----
>>          From: qt-creator-bounces at trolltech.com<mailto:qt-creator-bounces at trolltech.com>
>>          [mailto:qt-creator-bounces at trolltech.com] On Behalf Of Adam
>>          Higerd
>>          Sent: 19 March 2009 23:19
>>          To: qt-creator at trolltech.com<mailto:qt-creator at trolltech.com>
>>          Subject: Re: [Qt-creator] Project Tree
>>
>>          Porfirio wrote:
>>          >  Hi!
>>          >
>>          >  I really like QtCreator, its a great software but sometimes
>>          its hard
>>          >  to organize a big project because all files becomes messed
>>          even if
>>          >  they are in diferent folders.
>>          >
>>          >  In Eclipse it shows the folder strocture as it is in system,
>>          thats a
>>          >  good solution, in Netbeans you can have virtual folders and
>>          add your
>>          >  files there, even if they are all in same folder or
>>          whatever.
>>          >
>>          >  Something like this is realy required!
>>
>>          Creator does this based on project organization; if you have a
>>          subdirs
>>          project, it shows each subproject as a separate folder in the
>>          tree.
>>
>>          Meanwhile, if you have a project that's large enough to be
>>          spanning into
>>          subdirectories, you're looking at a case where you might want
>>          subprojects ANYWAY for the sake of build performance.
>>
>>          /s/ Adam
>>          _______________________________________________
>>     
>