Talk:Directory Structure: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
:: If that's the case, then we should create another directory of Qt resorce compiler files -- may be '''QtResources''' as a sibiling (or may be a child) of every '''Resources''' directory. The '''Resources''' directory can then contain all the xml/ui files. Since we will be having xmls for filters/filter grouping etc etc it's best to keep them separate from the rest of C++ code. | :: If that's the case, then we should create another directory of Qt resorce compiler files -- may be '''QtResources''' as a sibiling (or may be a child) of every '''Resources''' directory. The '''Resources''' directory can then contain all the xml/ui files. Since we will be having xmls for filters/filter grouping etc etc it's best to keep them separate from the rest of C++ code. | ||
::--[[User:Utkarsh|Utkarsh]] 16:53, 17 Mar 2006 (EST) | ::--[[User:Utkarsh|Utkarsh]] 16:53, 17 Mar 2006 (EST) | ||
::: I disagree. I have always seen the .ui files co-located with the source code. This is because a ui file almost always has some attached source code. For example, a <tt>pqMyWidget.ui</tt> file should have <tt>pqMyWidget</tt> and <tt>pqMyWidget.cxx</tt> source files coupled with it. | |||
::: ui files are really source files. Unless you are going to process them at run time, they should be treated as source files. | |||
:::--[[User:Kmorel|Kmorel]] 09:54, 20 Mar 2006 (EST) | |||
Latest revision as of 09:54, 20 March 2006
I think the directory structure looks good. I noticed that the chart is underneath the widgets directory. Does this mean it doesn't depend on any paraview code? I think this would be a good idea to keep it separate. Doing so would allow the chart to be reused in other Qt applications. It would be easy to put the default context menu and PGraph interface in a separate library.
--Mark Richardson 12:25, 17 Mar 2006 (EST)
- You are correct, any classes in the GUI/Widgets subtree don't depend on ParaView/ServerManager/VTK at all. There are pure Qt dependent classes.
- --Utkarsh 16:53, 17 Mar 2006 (EST)
I don't think we want all *.ui files in the Resources directory. I'd generally only consider files processed by Qt's resource compiler belonging there. Most *.ui files aren't resource files.
--Clinton 16:40, 17 Mar 2006 (EST)
- If that's the case, then we should create another directory of Qt resorce compiler files -- may be QtResources as a sibiling (or may be a child) of every Resources directory. The Resources directory can then contain all the xml/ui files. Since we will be having xmls for filters/filter grouping etc etc it's best to keep them separate from the rest of C++ code.
- --Utkarsh 16:53, 17 Mar 2006 (EST)
- I disagree. I have always seen the .ui files co-located with the source code. This is because a ui file almost always has some attached source code. For example, a pqMyWidget.ui file should have pqMyWidget and pqMyWidget.cxx source files coupled with it.
- ui files are really source files. Unless you are going to process them at run time, they should be treated as source files.
- --Kmorel 09:54, 20 Mar 2006 (EST)
