Added most of initial code

Author: Preben Ludviksen

.gitignore

@@ -0,0 +1 @@
+.idea/

LICENSE

@@ -0,0 +1,191 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2016 Tripfinger AS
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

README.md

@@ -1,59 +1,80 @@
 # 9-projects-layout
 
-This is a boilerplate for redistributable React Native components and modules with native code
-(iOS & Android). It has unit tests for native code, and integration tests for running on emulators
-or devices.
+This is a boilerplate for distributable React Native components with native code
+(iOS & Android). It has unit tests for native code, and integration tests for automated testing
+on emulators or devices. The boilerplate example has a HelloWorld component, and a HelloWorld
+module backed by native code.
 
-When installed via npm, it also supports automatic linking of native code.
+When published and installed via npm, the resulting package supports automatic linking of the native 
+code. The contained package react-native-helloworld is published, and can be installed/linked like 
+this:
+
+    npm install react-native-helloworld
+    react-native link react-native-helloworld
 
 ## Explanation
 
-What is a 9 projects layout? It is, as a matter of fact, a project layout consisting of 9 
-individual sub-projects. But bear with me for a minute, it's not nearly as horrible as it sounds.
+For a full explanation of the layout, see 
+[this article](https://www.benwixen.com/articles/distributing-react-native-components-with-native-code).
 
-When you create a new React Native project, three different projects are created for you: the 
-JS-code, a Java-project (for Android) and an Objective C-project (for iOS). This layout has 
-three sets of those projects. The first set contains the component code:
+There are 3 sets of 3 projects (JS, Obj-C & Java). The first set is for the component code:
 
     /
     /android
     /ios
 
-Strictly speaking, this is the only set you need, but if you want your code base to stay stable and
- correct, you will want to add some tests. 
-Since RN components are normally bundled with all source code, we want to keep the  
-projects as simple as possible. To achieve this, we create a separate set of three projects for 
-testing:
+The second set is for unit- and integration tests:
 
     /tests
     /tests/android
     /tests/ios
 
-Since these projects link the component code directly, you can do all development from
-within these projects in XCode, Android Studio, Webstorm, etc. 
-
-The third set of projects are for a sample RN app, demonstrating the component / module in use.
-This is of course optional, but a nice feature to have if you want to expand your audience.
+The third set is just a sample project to demonstrate usage of the components. The Android and iOS
+parts are just the standard React Native boilerplate:
 
     /example
     /example/android
     /example/ios
 
 ## Development
 
-Like mentioned above, you can develop the component code through within the context of the 
-test-projects. This makes sense because they normally are developed in parallel, and because React 
-and React Native are peer dependencies of the main project 
-(meaning they need the context of an app to resolve in your Javascript IDE).
+For development of the component code, first run `npm install` in the `tests`-folder. Since the 
+native code is linked directly in the test-projects, they serve as a context you can develop it in
+(the root projects only link React/Native as peer dependencies). 
+
+### iOS
+
+If you open `/tests/ios/HelloWorldTests.xcodeproj` in XCode, you can edit the native code and 
+unit tests side-by-side. You'll find the native code under `Libraries/HelloWorld.xcodeproj`. 
+Unit- and integration tests can be run together in the standard test-runner with ⌘+U.
+
+### Android
+
+Open `/tests/android` in Android Studio, and you'll find both the native code and the unit tests
+in the project view. The unit tests can be run by right-clicking the package containing the tests,
+and choosing *Run Tests in tests*.
+
+There is not yet an automatic test runner for integration tests, but you can run them by firing up
+ `/tests` as a normal React Native app on an Android emulator or device, and selecting the tests 
+ manually from a list.
+
+### JS-code
+
+To develop the JS-components and the integration tests, just open `/tests` in your editor of choice 
+(f.ex. Atom or WebStorm). The JS-code can be edited from within the `/tests/symlinks`-folder.
+Integration tests are located under `/tests/integration-test`.
+
+There is a script `/tests/make-copies.sh` that copies the JS-code from the root project into a 
+folder `/tests/copies`. This is because the React Native packager doesn't follow symlinks. When 
+running the integration tests through XCode, this script is run automatically.
 
-## Unit testss
+### Example code
 
-The unit tests for iOS run through the standard XCTest framework. On Android they run using JUnit.
-The Javascript tests use jest.
+If you want to include an example to demonstrate usage of your component, the `/example` folder is 
+the place for that. Ideally, you only touch the JS-code, and leave the React Native 
+boilerplate as it is.
 
-## Integration tests
+## Publishing
 
-The integration tests run on iOS through a custom React test runner (that is compatible with XCode).
-A test-runner for Android is not yet in place, but the tests can be run from the test app, by
-running it on an emulator / device.
-# 9-project-layout
+Once you have finished your components, you can run a normal `npm publish` from the root folder. The
+`/tests` and `/example` folders are automatically excluded from the package.

android/.gitignore

@@ -0,0 +1,9 @@
+*.iml
+.gradle
+/local.properties
+/.idea/workspace.xml
+/.idea/libraries
+.DS_Store
+/build
+/captures
+.externalNativeBuild

android/build.gradle

@@ -0,0 +1,61 @@
+// Top-level build file where you can add configuration options common to all sub-projects/modules.
+
+apply plugin: 'com.android.library'
+
+buildscript {
+  repositories {
+    mavenLocal()
+    jcenter()
+    maven {
+      // For developing the library outside the context of the example app, expect `react-native`
+      // to be installed at `./node_modules`.
+      url "$projectDir/../node_modules/react-native/android"
+    }
+    maven {
+      // For developing the example app.
+      url "$projectDir/../../react-native/android"
+    }
+  }
+  dependencies {
+    classpath 'com.android.tools.build:gradle:2.2.0'
+
+    // NOTE: Do not place your application dependencies here; they belong
+    // in the individual module build.gradle files
+  }
+}
+
+allprojects {
+  repositories {
+    mavenLocal()
+    jcenter()
+    maven {
+      // For developing the library outside the context of the example app, expect `react-native`
+      // to be installed at `./node_modules`.
+      url "$projectDir/../node_modules/react-native/android"
+    }
+    maven {
+      // For developing the example app.
+      url "$projectDir/../../react-native/android"
+    }
+  }
+}
+
+android {
+  compileSdkVersion 23
+  buildToolsVersion "23.0.3"
+  defaultConfig {
+    minSdkVersion 16
+    targetSdkVersion 23
+    versionCode 1
+//    versionName "1.0"
+//    testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
+  }
+
+  lintOptions {
+    disable 'InvalidPackage'
+  }
+}
+
+dependencies {
+  compile 'com.facebook.react:react-native:+'
+}

android/gradle.properties

@@ -0,0 +1,17 @@
+# Project-wide Gradle settings.
+
+# IDE (e.g. Android Studio) users:
+# Gradle settings configured through the IDE *will override*
+# any settings specified in this file.
+
+# For more details on how to configure your build environment visit
+# http://www.gradle.org/docs/current/userguide/build_environment.html
+
+# Specifies the JVM arguments used for the daemon process.
+# The setting is particularly useful for tweaking memory settings.
+org.gradle.jvmargs=-Xmx1536m
+
+# When configured, Gradle will run in incubating parallel mode.
+# This option should only be used with decoupled projects. More details, visit
+# http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:decoupled_projects
+# org.gradle.parallel=true