@@ -1,7 +1,7 @@
 = flow =
 == activate ==
-Right click project and select property[[BR]]
+Right click project and select properties[[BR]]
 [[Embed(projectproperty.jpg)]]
 
 Select C Coverage category and turn on the Activate nature checkbox[[BR]]
 [[Embed(activate.jpg)]]
@@ -10,9 +10,12 @@
 [[Embed(option.jpg)]]
 == linker option settings ==
 Select C/C++ Build Setting and add "-fprofile-arcs -ftest-coverage -std=c99 " linker option
 [[Embed(linkoption.jpg)]]
+
+Rebuild your project.
+
 == run ==
-Run the binaly and executed lines and never executed lines are high lighted
-* if it can not high lighted ,you should select refresh project
+Run the binary and executed lines and never executed lines are highlighted as can be seen in below screenshot.
+* Note: if the high lighted code does not show, you should select refresh project
 [[Embed(screenshot.jpg)]]
 

@@ -14,24 +14,24 @@
 In a Project with a lot of files, coverage calculation can takes a lot of time.
 Eclipse cannot be used until gcov builder is finished.
 (http://sourceforge.jp/projects/ginkgo/lists/archive/dev/2008-December/000004.html)
 == Solutions
-* Add a stop operation that can stop Builder and Error parser.
-* Add a mode that enable to start Builder and Error parser only by manually.
-* Builder and Error parser should be background task not to effect GUI.
-* To save gcov execution time, parsing *.gcno and *.gcda files directory.
-* Make a enable Builder and Error parser per folder or source file
+ * Add a stop operation that can stop Builder and Error parser.
+ * Add a mode that enable to start Builder and Error parser only by manually.
+ * Builder and Error parser should be background task not to effect GUI.
+ * To save gcov execution time, parsing *.gcno and *.gcda files directory.
+ * Make a enable Builder and Error parser per folder or source file
 (http://sourceforge.jp/forum/forum.php?thread_id=22157&forum_id=13644)
 == Problems
 The Builder file search is too slow, an other method should be used.
 (http://sourceforge.jp/projects/ginkgo/lists/archive/dev/2008-December/000004.html)
 == Solutions
-* Find source file's path from *.gcno or *.gcda file
+ * Find source file's path from *.gcno or *.gcda file
 = User Interface
 
 == Solutions
 Like for subversion plug-in it should be good to have coverage information display directly on Project Explorer view (not in an other view).
 
 = Others
-* support branch coverage
-* coverage history 
+ * support branch coverage
+ * coverage history 
 

@@ -18,14 +18,19 @@
 * Add a stop operation that can stop Builder and Error parser.
 * Add a mode that enable to start Builder and Error parser only by manually.
 * Builder and Error parser should be background task not to effect GUI.
 * To save gcov execution time, parsing *.gcno and *.gcda files directory.
-
+* Make a enable Builder and Error parser per folder or source file
+(http://sourceforge.jp/forum/forum.php?thread_id=22157&forum_id=13644)
 == Problems
 The Builder file search is too slow, an other method should be used.
 (http://sourceforge.jp/projects/ginkgo/lists/archive/dev/2008-December/000004.html)
 == Solutions
 * Find source file's path from *.gcno or *.gcda file
+= User Interface
+
+== Solutions
+Like for subversion plug-in it should be good to have coverage information display directly on Project Explorer view (not in an other view).
 
 = Others
 * support branch coverage
 * coverage history 

@@ -1,30 +1,32 @@
 = Design
 
-Coverage builder and the coverage result extraction should be separate using Builder for gcov execution and Error parser to retrieve result of coverage
-
-
+== Problems
+Possibility to use an external tools (for me it's an external make target) that will execute gcov.
+(http://sourceforge.jp/projects/ginkgo/lists/archive/dev/2008-December/000004.html)
+== Solutions
+Coverage builder and the coverage result extraction should be separated using Builder for gcov execution and Error parser to retrieve result of coverage.
+Error parser can start retrieve result of coverage by external tools' gcov execution, like external make target or lcov(http://ltp.sourceforge.net/coverage/lcov.php).
+Gcov execution of Builder should be switch between enable and disable.
+Error parser can retrieve result of coverage alone,when Builder is set to disable.
 = Performance
 
 == Problems
+In a Project with a lot of files, coverage calculation can takes a lot of time.
+Eclipse cannot be used until gcov builder is finished.
+(http://sourceforge.jp/projects/ginkgo/lists/archive/dev/2008-December/000004.html)
+== Solutions
+* Add a stop operation that can stop Builder and Error parser.
+* Add a mode that enable to start Builder and Error parser only by manually.
+* Builder and Error parser should be background task not to effect GUI.
+* To save gcov execution time, parsing *.gcno and *.gcda files directory.
 
-In a Project with a lot of files, coverage calculation can takes a lot of time
-
+== Problems
+The Builder file search is too slow, an other method should be used.
+(http://sourceforge.jp/projects/ginkgo/lists/archive/dev/2008-December/000004.html)
 == Solutions
+* Find source file's path from *.gcno or *.gcda file
 
-
-I think the reason why it takes a lot of time is gcov execution time.
-So, it may be effective that not parsing *.gcov files but parsing *.gcno and
-*.gcda files directory.
-
-- Add a stop target in the project; because eclipse cannot be used until
-> gcov builder is finished.
->
-You are right,that should be background task.
-
-- The Builder file search is too slow, an other method should be used.
-
-It may be solved if *.gcno or *.gcda file include their source file's path.
-
+= Others
 * support branch coverage
 * coverage history 
 

@@ -1,6 +1,7 @@
 = Design
 
+Coverage builder and the coverage result extraction should be separate using Builder for gcov execution and Error parser to retrieve result of coverage
 
 
 = Performance
 

@@ -1,9 +1,16 @@
+= Design
+
+
+
+= Performance
+
 == Problems
 
 In a Project with a lot of files, coverage calculation can takes a lot of time
 
 == Solutions
+
 
 I think the reason why it takes a lot of time is gcov execution time.
 So, it may be effective that not parsing *.gcov files but parsing *.gcno and
 *.gcda files directory.

@@ -1,7 +1,10 @@
-In a Project with a lot of files, coverage calculation can takes a lot of
-> time
->
+== Problems
+
+In a Project with a lot of files, coverage calculation can takes a lot of time
+
+== Solutions
+
 I think the reason why it takes a lot of time is gcov execution time.
 So, it may be effective that not parsing *.gcov files but parsing *.gcno and
 *.gcda files directory.
 

@@ -1 +1,19 @@
+In a Project with a lot of files, coverage calculation can takes a lot of
+> time
+>
+I think the reason why it takes a lot of time is gcov execution time.
+So, it may be effective that not parsing *.gcov files but parsing *.gcno and
+*.gcda files directory.
+
+- Add a stop target in the project; because eclipse cannot be used until
+> gcov builder is finished.
+>
+You are right,that should be background task.
+
+- The Builder file search is too slow, an other method should be used.
+
+It may be solved if *.gcno or *.gcda file include their source file's path.
+
+* support branch coverage
+* coverage history 
 

@@ -41,8 +41,9 @@
 reference
 http://www.cygwin.com/ml/cygwin/2007-11/msg00180.html
 
 == Feature Plan ==
+ * [wiki:FeaturePlan Feature Plan]
  * support for branch coverage
  * coverage history
 == Pages For Developers ==
  * [wiki:ForDeveloper subversion access]

@@ -5,12 +5,12 @@
 
 Select C Coverage category and turn on the Activate nature checkbox[[BR]]
 [[Embed(activate.jpg)]]
 == compiler option settings ==
-Select C/C++ Build Setting and add "-fprofile-arcs -ftest-coverage" compiler option
+Select C/C++ Build Setting and add "-fprofile-arcs -ftest-coverage -std=c99 " compiler option
 [[Embed(option.jpg)]]
 == linker option settings ==
-Select C/C++ Build Setting and add "-fprofile-arcs -ftest-coverage" linker option
+Select C/C++ Build Setting and add "-fprofile-arcs -ftest-coverage -std=c99 " linker option
 [[Embed(linkoption.jpg)]]
 == run ==
 Run the binaly and executed lines and never executed lines are high lighted
 * if it can not high lighted ,you should select refresh project