Fossil SCM
[Grammar] adding_code.wiki changes.
Commit
1a97a4e96c9e11aa5ca0cbc549d1a78685e12e95d1e396f24f9ffc6e5d2f795f
Parent
d4a21cd45f4a2e2…
1 file changed
+3
-3
+3
-3
| --- www/adding_code.wiki | ||
| +++ www/adding_code.wiki | ||
| @@ -37,11 +37,11 @@ | ||
| 37 | 37 | The [./makefile.wiki|Makefile] for Fossil takes care of running these |
| 38 | 38 | preprocessors with all the right arguments and in the right order. So it is |
| 39 | 39 | not necessary to understand the details of how these preprocessors work. |
| 40 | 40 | (Though, the sources for all three preprocessors are included in the source |
| 41 | 41 | tree and are well commented, if you want to dig deeper.) It is only necessary |
| 42 | -to know that these preprocessors exist and hence will effect the way you | |
| 42 | +to know that these preprocessors exist and hence will affect the way you | |
| 43 | 43 | write code. |
| 44 | 44 | |
| 45 | 45 | <h2>3.0 Adding New Source Code Files</h2> |
| 46 | 46 | |
| 47 | 47 | New source code files are added in the "src/" subdirectory of the Fossil |
| @@ -98,11 +98,11 @@ | ||
| 98 | 98 | files. See [../tools/makeheaders.html | makeheaders.html] for additional |
| 99 | 99 | information. |
| 100 | 100 | |
| 101 | 101 | After creating a template file such as shown above, and after updating |
| 102 | 102 | the makefiles, you should be able to recompile Fossil and have it include |
| 103 | -your new source file, even before you source file contains any code. | |
| 103 | +your new source file, even before your source file contains any code. | |
| 104 | 104 | It is recommended that you try this. |
| 105 | 105 | |
| 106 | 106 | Be sure to [/help/add|fossil add] your new source file to the self-hosting |
| 107 | 107 | Fossil repository and then [/help/commit|commit] your changes! |
| 108 | 108 | |
| @@ -212,11 +212,11 @@ | ||
| 212 | 212 | non-HTML content. In the unlikely event that you need to generate |
| 213 | 213 | non-HTML content, look at existing webpage implementations |
| 214 | 214 | (ex: "logo" or "style.css") to see how that is done. |
| 215 | 215 | |
| 216 | 216 | There are lots of other things that a real web-page implementation will |
| 217 | -need to do, such verifying user credentials, parsing query parameters, | |
| 217 | +need to do, such as verifying user credentials, parsing query parameters, | |
| 218 | 218 | and interacting with the repository. But now that you have the general |
| 219 | 219 | idea of how webpages are implemented, you can look at the many other |
| 220 | 220 | webpage implementations already built into Fossil to see how all that |
| 221 | 221 | works. |
| 222 | 222 | |
| 223 | 223 |
| --- www/adding_code.wiki | |
| +++ www/adding_code.wiki | |
| @@ -37,11 +37,11 @@ | |
| 37 | The [./makefile.wiki|Makefile] for Fossil takes care of running these |
| 38 | preprocessors with all the right arguments and in the right order. So it is |
| 39 | not necessary to understand the details of how these preprocessors work. |
| 40 | (Though, the sources for all three preprocessors are included in the source |
| 41 | tree and are well commented, if you want to dig deeper.) It is only necessary |
| 42 | to know that these preprocessors exist and hence will effect the way you |
| 43 | write code. |
| 44 | |
| 45 | <h2>3.0 Adding New Source Code Files</h2> |
| 46 | |
| 47 | New source code files are added in the "src/" subdirectory of the Fossil |
| @@ -98,11 +98,11 @@ | |
| 98 | files. See [../tools/makeheaders.html | makeheaders.html] for additional |
| 99 | information. |
| 100 | |
| 101 | After creating a template file such as shown above, and after updating |
| 102 | the makefiles, you should be able to recompile Fossil and have it include |
| 103 | your new source file, even before you source file contains any code. |
| 104 | It is recommended that you try this. |
| 105 | |
| 106 | Be sure to [/help/add|fossil add] your new source file to the self-hosting |
| 107 | Fossil repository and then [/help/commit|commit] your changes! |
| 108 | |
| @@ -212,11 +212,11 @@ | |
| 212 | non-HTML content. In the unlikely event that you need to generate |
| 213 | non-HTML content, look at existing webpage implementations |
| 214 | (ex: "logo" or "style.css") to see how that is done. |
| 215 | |
| 216 | There are lots of other things that a real web-page implementation will |
| 217 | need to do, such verifying user credentials, parsing query parameters, |
| 218 | and interacting with the repository. But now that you have the general |
| 219 | idea of how webpages are implemented, you can look at the many other |
| 220 | webpage implementations already built into Fossil to see how all that |
| 221 | works. |
| 222 | |
| 223 |
| --- www/adding_code.wiki | |
| +++ www/adding_code.wiki | |
| @@ -37,11 +37,11 @@ | |
| 37 | The [./makefile.wiki|Makefile] for Fossil takes care of running these |
| 38 | preprocessors with all the right arguments and in the right order. So it is |
| 39 | not necessary to understand the details of how these preprocessors work. |
| 40 | (Though, the sources for all three preprocessors are included in the source |
| 41 | tree and are well commented, if you want to dig deeper.) It is only necessary |
| 42 | to know that these preprocessors exist and hence will affect the way you |
| 43 | write code. |
| 44 | |
| 45 | <h2>3.0 Adding New Source Code Files</h2> |
| 46 | |
| 47 | New source code files are added in the "src/" subdirectory of the Fossil |
| @@ -98,11 +98,11 @@ | |
| 98 | files. See [../tools/makeheaders.html | makeheaders.html] for additional |
| 99 | information. |
| 100 | |
| 101 | After creating a template file such as shown above, and after updating |
| 102 | the makefiles, you should be able to recompile Fossil and have it include |
| 103 | your new source file, even before your source file contains any code. |
| 104 | It is recommended that you try this. |
| 105 | |
| 106 | Be sure to [/help/add|fossil add] your new source file to the self-hosting |
| 107 | Fossil repository and then [/help/commit|commit] your changes! |
| 108 | |
| @@ -212,11 +212,11 @@ | |
| 212 | non-HTML content. In the unlikely event that you need to generate |
| 213 | non-HTML content, look at existing webpage implementations |
| 214 | (ex: "logo" or "style.css") to see how that is done. |
| 215 | |
| 216 | There are lots of other things that a real web-page implementation will |
| 217 | need to do, such as verifying user credentials, parsing query parameters, |
| 218 | and interacting with the repository. But now that you have the general |
| 219 | idea of how webpages are implemented, you can look at the many other |
| 220 | webpage implementations already built into Fossil to see how all that |
| 221 | works. |
| 222 | |
| 223 |