Differences

This shows you the differences between two versions of the page.

--- qt:project_structure [2010/12/08 21:58] – [The file view] mithat
+++ qt:project_structure [2011/04/01 11:01] (current) – [Source files] mithat
@@ Line 20: / Line 20: @@
 === Explicitly generated ===
   * **''main.cpp''**
-    * The project's main C++ file containing the main function.
+    * The project's main C++ file containing the ''main'' function.
     * The name of this file is a convention, not a requirement.
   * **''{yourclass}.h''** and **''{yourclass}.cpp''**
     * C++ class header and implementation files for a class that you derived from QObject (if needed).
-    * May contain ''Q_OBJECT'', a Qt macro used to implement signals and slots.
+    * Probably contains ''Q_OBJECT'', a Qt macro used to implement signals and slots.
     * There may be more than one of these.
   * **''{yourdialog}.ui''**
@@ Line 54: / Line 54: @@
 ===== The workflow view =====
-The typical Qt project workflow consists of the following major phases: creating a project, adding files to a project, building and testing a project. These are discussed below. ((These phases hold true whether you are using a IDE or a simple command line based environment. However, an IDE will typically manage many of these tasks for you.))
+The typical Qt project workflow consists of the following major phases: creating a project, adding files to a project, building and testing a project. These are discussed below.((These phases hold true whether you are using a IDE or a simple command line based environment. However, an IDE will typically manage many of these tasks for you.))
 ==== Creating a project ====
@@ Line 71: / Line 71: @@
 Notes:
-  * Repeat the above as needed. Whenever you add new files, be sure to reflect those changes into the *.pro file and regenerate the Makefile before building.
+  * Repeat the above as needed.
+  * Whenever you add new files, be sure to reflect those changes into the *.pro file and rerun ''qmake'' before running building and testing.
   * Assuming {directory-name}.pro is correctly configured, the Makefile generated by ''[[qmake]]'' will automagically be configured to call [[moc]] and [[uic]] as needed.