[Qt-creator] Suggestion

[Felipe Ferreri Tonello]

On Mon, Jan 26, 2009 at 11:44 AM, Yves Bailly <yves.bailly at sescoi.fr> wrote:

>
> Hello all,
>
> Here's a feedback after having completed a small project using
> QtCreator (assuming a project is ever finished, of course).
> General feeling: very, very (very, very) positive.
>
> But... because there's always a "but"...
> This project contains 7 forms, 28 headers, 29 source files. On a
> day-to-day usage, the proposed flat view of files is not really
> adequate when you have many files, even though it is sometimes
> handy. Some grouping would be quite nice to have.
>
> Let me suggest some possible groupings.
>
> 1- The classic grouping, by file type:
> my_project
>    \- my_project.pro
>    |- Headers
>    |   \- first_dialog.h
>    |   |- second_dialog.h
>    |   |- some_class.h
>    |- Sources
>    |   \- first_dialog.cpp
>    |   |- second_dialog.cpp
>    |   |- some_class.cpp
>    |   |- main.cpp
>    |- Forms
>    |   \- first_dialog.ui
>    |   |- second_dialog.ui
>    |- Resources
>        \- first_resource.qrc
>        |- second_resource.qrc
>
> 2- As shown here, I mostly name my files using the class name then
>   adding .h or .cpp according if it's a header or a source file. If
>   two files are detected, such as "my_file.h" and "my_file.cpp", they
>   could be grouped. Maybe even group with them the form file. Thus
>   the previous tree would be shown like this:
> my_project
>    \- my_project.pro
>    |- first_dialog
>    |    \- header (first_dialog.h)
>    |    |- source (first_dialog.cpp)
>    |    |- form (first_dialog.ui)
>    |- second_dialog
>    |    \- header (second_dialog.h)
>    |    |- source (second_dialog.cpp)
>    |    |- form (second_dialog.ui)
>    |- some_class
>    |    \- header (some_class.h)
>    |    |- source (some_class.cpp)
>    |- Other sources
>    |    \- main.cpp
>    |- Resources
>        \- first_resource.qrc
>        |- second_resource.qrc
>
> Well, you get the idea: to be able to see only some of your files,
> to reduce the visual searching in the list to find a given file.
> But maybe this can be done by creating a plugin, maybe I should have
> a look at *how* to create a plugin for QtCreator... ;-)
>

I agree with the hole Idea, and the third group option. Actually I was
looking for someting like that.
But I don't think this should be a task for a plugin, thus should be a Qt
Creator task.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20090127/f8450570/attachment.html