diff options
Diffstat (limited to 'examples/cross_calculator')
| -rw-r--r-- | examples/cross_calculator/android/readme.txt | 6 | ||||
| -rw-r--r-- | examples/cross_calculator/ios/readme.txt | 4 | ||||
| -rw-r--r-- | examples/cross_calculator/lazarus/readme.txt | 16 | ||||
| -rw-r--r-- | examples/cross_calculator/nim_backend/backend.nim | 10 | ||||
| -rw-r--r-- | examples/cross_calculator/readme.txt | 26 |
5 files changed, 26 insertions, 36 deletions
diff --git a/examples/cross_calculator/android/readme.txt b/examples/cross_calculator/android/readme.txt index 51fa9c6fd..96bd403ca 100644 --- a/examples/cross_calculator/android/readme.txt +++ b/examples/cross_calculator/android/readme.txt @@ -20,11 +20,5 @@ installed on your system, you can simply run "ant debug" to build everything. Once the apk is built you can install it on your device or emulator with the command "adb install bin/CrossCalculator-debug.apk". -You can use this example as a starting point for your project or look at the -history of the github project at https://github.com/gradha/nimrod-on-android. -That repository documents the individual integration steps you would take for -any Android project (note it uses Eclipse rather than ant to build and -therefore the build process requires more manual fiddling). - This example runs against the Android level 3 API, meaning devices from Android 1.5 and above should be able to run the generated binary. diff --git a/examples/cross_calculator/ios/readme.txt b/examples/cross_calculator/ios/readme.txt index 83538aad7..3ea03a367 100644 --- a/examples/cross_calculator/ios/readme.txt +++ b/examples/cross_calculator/ios/readme.txt @@ -8,10 +8,6 @@ When the calculate button is used the view controller calls the Nim code to delegate the logic of the operation and puts the result in a label for display. All interface error checks are implemented in the view controller. -You can use this as a starting point for your project or look at the history of -the github project at https://github.com/gradha/nimrod-on-ios. That repository -documents the individual integration steps you would take for any iOS project. - This version of the iOS project is known to work with Xcode 4.2 and Xcode 4.4.1. The final binary can be deployed on iOS 3.x to 5.x supporting all iOS platforms and versions available at the moment. diff --git a/examples/cross_calculator/lazarus/readme.txt b/examples/cross_calculator/lazarus/readme.txt index 2d5048445..c704d53fd 100644 --- a/examples/cross_calculator/lazarus/readme.txt +++ b/examples/cross_calculator/lazarus/readme.txt @@ -1,8 +1,8 @@ -This example demonstrates how to use Nim with Lazarus. The GUI is generated -with Lazarus, while the "backend" is written in Nim. To compile the example, -use this command: - - nim c --app:gui --no_main --no_linking backend.nim - -Open the ``nimlaz.lpi`` file in Lazarus and run the program. - +This example demonstrates how to use Nim with Lazarus. The GUI is generated +with Lazarus, while the "backend" is written in Nim. To compile the example, +use this command: + + nim c --app:gui --no_main --no_linking backend.nim + +Open the ``nimlaz.lpi`` file in Lazarus and run the program. + diff --git a/examples/cross_calculator/nim_backend/backend.nim b/examples/cross_calculator/nim_backend/backend.nim index ffa4311f9..c8684581c 100644 --- a/examples/cross_calculator/nim_backend/backend.nim +++ b/examples/cross_calculator/nim_backend/backend.nim @@ -1,5 +1,5 @@ -# Backend for the different user interfaces. - -proc myAdd*(x, y: int): int {.cdecl, exportc.} = - result = x + y - +# Backend for the different user interfaces. + +proc myAdd*(x, y: int): int {.cdecl, exportc.} = + result = x + y + diff --git a/examples/cross_calculator/readme.txt b/examples/cross_calculator/readme.txt index 12ad558d4..5011792b9 100644 --- a/examples/cross_calculator/readme.txt +++ b/examples/cross_calculator/readme.txt @@ -1,13 +1,13 @@ -The cross platform calculator illustrates how to use Nim to create a backend -called by different native user interfaces. - -Since the purpose of the example is to show how the cross platform code -interacts with Nimrod the actual backend code is just a simple addition proc. -By keeping your program logic in Nim you can easily reuse it in different -platforms. - -To avoid duplication of code, the backend code lies in a separate directory and -each platform compiles it with a different custom build process, usually -generating C code in a temporary build directory. - -For a more elaborate and useful example see the cross_todo example. +The cross platform calculator illustrates how to use Nim to create a backend +called by different native user interfaces. + +Since the purpose of the example is to show how the cross platform code +interacts with Nimrod the actual backend code is just a simple addition proc. +By keeping your program logic in Nim you can easily reuse it in different +platforms. + +To avoid duplication of code, the backend code lies in a separate directory and +each platform compiles it with a different custom build process, usually +generating C code in a temporary build directory. + +For a more elaborate and useful example see the cross_todo example. |