diff --git a/docs/Accessibility.md b/docs/Accessibility.md index e0209d0f7..dd75f8f85 100644 --- a/docs/Accessibility.md +++ b/docs/Accessibility.md @@ -4,7 +4,7 @@ title: Accessibility layout: docs category: Guides permalink: docs/accessibility.html -next: native-modules-ios +next: direct-manipulation --- ## iOS diff --git a/docs/DirectManipulation.md b/docs/DirectManipulation.md index b321dacc5..8939c59e5 100644 --- a/docs/DirectManipulation.md +++ b/docs/DirectManipulation.md @@ -4,7 +4,7 @@ title: Direct Manipulation layout: docs category: Guides permalink: docs/direct-manipulation.html -next: linking-libraries-ios +next: debugging --- It is sometimes necessary to make changes directly to a component diff --git a/docs/EmbeddedApp.md b/docs/EmbeddedApp.md index f48a148a9..cc4f91a21 100644 --- a/docs/EmbeddedApp.md +++ b/docs/EmbeddedApp.md @@ -1,10 +1,10 @@ --- id: embedded-app-ios -title: Integrating with Existing Apps (iOS) +title: Integrating with Existing Apps layout: docs -category: Guides +category: Guides (iOS) permalink: docs/embedded-app-ios.html -next: javascript-environment +next: native-modules-android --- Since React makes no assumptions about the rest of your technology stack – it’s commonly noted as simply the `V` in `MVC` – it’s easily embeddable within an existing non-React Native app. In fact, it integrates with other best practice community tools like [CocoaPods](http://cocoapods.org/). diff --git a/docs/KnownIssues.md b/docs/KnownIssues.md index c98182560..b614485b4 100644 --- a/docs/KnownIssues.md +++ b/docs/KnownIssues.md @@ -4,7 +4,7 @@ title: Known Issues layout: docs category: Guides permalink: docs/known-issues.html -next: activityindicatorios +next: native-modules-ios --- ### Missing Modules and Native Views diff --git a/docs/LinkingLibraries.md b/docs/LinkingLibraries.md index cb9ec5511..f3580ad9a 100644 --- a/docs/LinkingLibraries.md +++ b/docs/LinkingLibraries.md @@ -1,10 +1,10 @@ --- id: linking-libraries-ios -title: Linking Libraries (iOS) +title: Linking Libraries layout: docs -category: Guides +category: Guides (iOS) permalink: docs/linking-libraries-ios.html -next: debugging +next: running-on-device-ios --- Not every app uses all the native capabilities, and including the code to support diff --git a/docs/NativeComponentsAndroid.md b/docs/NativeComponentsAndroid.md index 488b44274..b7d41551c 100644 --- a/docs/NativeComponentsAndroid.md +++ b/docs/NativeComponentsAndroid.md @@ -1,10 +1,10 @@ --- id: native-components-android -title: Native UI Components (Android) +title: Native UI Components layout: docs -category: Guides +category: Guides (Android) permalink: docs/native-components-android.html -next: direct-manipulation +next: running-on-device-android --- There are tons of native UI widgets out there ready to be used in the latest apps - some of them are part of the platform, others are available as third-party libraries, and still more might be in use in your very own portfolio. React Native has several of the most critical platform components already wrapped, like `ScrollView` and `TextInput`, but not all of them, and certainly not ones you might have written yourself for a previous app. Fortunately, it's quite easy to wrap up these existing components for seamless integration with your React Native application. diff --git a/docs/NativeComponentsIOS.md b/docs/NativeComponentsIOS.md index 0b369a974..e506bc6c4 100644 --- a/docs/NativeComponentsIOS.md +++ b/docs/NativeComponentsIOS.md @@ -1,10 +1,10 @@ --- id: native-components-ios -title: Native UI Components (iOS) +title: Native UI Components layout: docs -category: Guides +category: Guides (iOS) permalink: docs/native-components-ios.html -next: native-components-android +next: linking-libraries-ios --- There are tons of native UI widgets out there ready to be used in the latest apps - some of them are part of the platform, others are available as third-party libraries, and still more might be in use in your very own portfolio. React Native has several of the most critical platform components already wrapped, like `ScrollView` and `TextInput`, but not all of them, and certainly not ones you might have written yourself for a previous app. Fortunately, it's quite easy to wrap up these existing components for seamless integration with your React Native application. diff --git a/docs/NativeModulesAndroid.md b/docs/NativeModulesAndroid.md index 66f2e8e01..0a5575f74 100644 --- a/docs/NativeModulesAndroid.md +++ b/docs/NativeModulesAndroid.md @@ -1,10 +1,10 @@ --- id: native-modules-android -title: Native Modules (Android) +title: Native Modules layout: docs -category: Guides +category: Guides (Android) permalink: docs/native-modules-android.html -next: native-components-ios +next: native-components-android --- Sometimes an app needs access to a platform API that React Native doesn't have a corresponding module for yet. Maybe you want to reuse some existing Java code without having to reimplement it in JavaScript, or write some high performance, multi-threaded code such as for image processing, a database, or any number of advanced extensions. diff --git a/docs/NativeModulesIOS.md b/docs/NativeModulesIOS.md index 2bf71902b..aa2c21aec 100644 --- a/docs/NativeModulesIOS.md +++ b/docs/NativeModulesIOS.md @@ -1,10 +1,10 @@ --- id: native-modules-ios -title: Native Modules (iOS) +title: Native Modules layout: docs -category: Guides +category: Guides (iOS) permalink: docs/native-modules-ios.html -next: native-modules-android +next: native-components-ios --- Sometimes an app needs access to platform API, and React Native doesn't have a corresponding module yet. Maybe you want to reuse some existing Objective-C, Swift or C++ code without having to reimplement it in JavaScript, or write some high performance, multi-threaded code such as for image processing, a database, or any number of advanced extensions. @@ -264,7 +264,7 @@ You can then define methods and export your enum constants like this: @"statusBarAnimationFade" : @(UIStatusBarAnimationFade), @"statusBarAnimationSlide" : @(UIStatusBarAnimationSlide) } }; - + RCT_EXPORT_METHOD(updateStatusBarAnimation:(UIStatusBarAnimation)animation completion:(RCTResponseSenderBlock)callback) ``` diff --git a/docs/RunningOnDeviceAndroid.md b/docs/RunningOnDeviceAndroid.md index 74176a13d..24f710137 100644 --- a/docs/RunningOnDeviceAndroid.md +++ b/docs/RunningOnDeviceAndroid.md @@ -1,10 +1,10 @@ --- id: running-on-device-android -title: Running On Device (Android) +title: Running On Device layout: docs -category: Guides +category: Guides (Android) permalink: docs/running-on-device-android.html -next: embedded-app-ios +next: activityindicatorios --- ## USB Debugging diff --git a/docs/RunningOnDeviceIOS.md b/docs/RunningOnDeviceIOS.md index 7e2746114..9309586ad 100644 --- a/docs/RunningOnDeviceIOS.md +++ b/docs/RunningOnDeviceIOS.md @@ -1,10 +1,10 @@ --- id: running-on-device-ios -title: Running On Device (iOS) +title: Running On Device layout: docs -category: Guides +category: Guides (iOS) permalink: docs/running-on-device-ios.html -next: running-on-device-android +next: embedded-app-ios --- Note that running on device requires [Apple Developer account](https://developer.apple.com/register) and provisioning your iPhone. This guide covers only React Native specific topic. diff --git a/docs/Testing.md b/docs/Testing.md index 4ce54a151..9a188d14c 100644 --- a/docs/Testing.md +++ b/docs/Testing.md @@ -4,7 +4,7 @@ title: Testing layout: docs category: Guides permalink: docs/testing.html -next: running-on-device-ios +next: javascript-environment --- ## Running Tests and Contributing