summary refs log tree commit diff stats
path: root/examples/cross_todo
diff options
context:
space:
mode:
authorAdam Strzelecki <ono@java.pl>2015-09-04 23:11:11 +0200
committerAdam Strzelecki <ono@java.pl>2015-09-04 23:12:03 +0200
commitc99a9e5a6cdb6be1f716e5bea0a4e6429f0a53d7 (patch)
treefdc5428d70809ac89fd4ee56d844a98c8926203d /examples/cross_todo
parent567b7d5a6a7fe426355b496b22b7ec573929b2d3 (diff)
downloadNim-c99a9e5a6cdb6be1f716e5bea0a4e6429f0a53d7.tar.gz
examples: Trim .txt files trailing whitespace
via OSX: find . -name '*.txt' -exec sed -i '' -E 's/[[:space:]]+$//' {} +
Diffstat (limited to 'examples/cross_todo')
-rw-r--r--examples/cross_todo/nim_backend/readme.txt28
-rw-r--r--examples/cross_todo/readme.txt10
2 files changed, 19 insertions, 19 deletions
diff --git a/examples/cross_todo/nim_backend/readme.txt b/examples/cross_todo/nim_backend/readme.txt
index 16cb592fc..4b31408e3 100644
--- a/examples/cross_todo/nim_backend/readme.txt
+++ b/examples/cross_todo/nim_backend/readme.txt
@@ -1,14 +1,14 @@
-This directory contains the nim backend code for the todo cross platform

-example.

-

-Unlike the cross platform calculator example, this backend features more code,

-using an sqlite database for storage. Also a basic test module is provided, not

-to be included with the final program but to test the exported functionality.

-The test is not embedded directly in the backend.nim file to avoid being able

-to access internal data types and procs not exported and replicate the

-environment of client code.

-

-In a bigger project with several people you could run `nim doc backend.nim`

-(or use the doc2 command for a whole project) and provide the generated html

-documentation to another programer for her to implement an interface without

-having to look at the source code.

+This directory contains the nim backend code for the todo cross platform
+example.
+
+Unlike the cross platform calculator example, this backend features more code,
+using an sqlite database for storage. Also a basic test module is provided, not
+to be included with the final program but to test the exported functionality.
+The test is not embedded directly in the backend.nim file to avoid being able
+to access internal data types and procs not exported and replicate the
+environment of client code.
+
+In a bigger project with several people you could run `nim doc backend.nim`
+(or use the doc2 command for a whole project) and provide the generated html
+documentation to another programer for her to implement an interface without
+having to look at the source code.
diff --git a/examples/cross_todo/readme.txt b/examples/cross_todo/readme.txt
index dfc21d861..5be01e197 100644
--- a/examples/cross_todo/readme.txt
+++ b/examples/cross_todo/readme.txt
@@ -1,5 +1,5 @@
-The cross platform todo illustrates how to use Nim to create a backend

-called by different native user interfaces.

-

-This example builds on the knowledge learned from the cross_calculator example.

-Check it out first to learn how to set up Nim on different platforms.

+The cross platform todo illustrates how to use Nim to create a backend
+called by different native user interfaces.
+
+This example builds on the knowledge learned from the cross_calculator example.
+Check it out first to learn how to set up Nim on different platforms.