History

Maxime Lapointe d56530d7d5 Reworking keyboardShouldPersistTaps to have a middle ground Summary: Right now, the ScrollView's keyboard hiding behavior is either all or nothing: Hide the keyboard on any tap, or do nothing ever. This PR introduces a third mode to keyboardShouldPersistTaps which is much closer to what I consider should be the default. In the new behavior, the tap responding is done in the bubbling phase (instead of the capture phase like =true). As a result, a child can handle the tap. If no child does, then the ScrollView will receive the tap and will hide the keyboard. As a result, changing TextInput focus works as a user expects, with a single tap and without keyboard hiding. But taping on Text or on the empty part of the ScrollView hides the keyboard and removes the focus. You can view the behavior in a monkey patched ScrollView demo on rnplay: https://rnplay.org/apps/E90UYw https://rnplay.org/apps/UGzhKA In order to have a uniform props set, i added 3 values to the keyboardShouldPersistTaps: 'never' and 'always' are the same as false and true. 'handled' is the new behavior. I don't Closes https://github.com/facebook/react-native/pull/10628 Differential Revision: D4294945 Pulled By: ericvicenti fbshipit-source-id: 1a753014156cac1a23fabfa8e1faa9a768868ef2		2016-12-07 21:43:35 -08:00
..
UIExplorer	Move all header imports to "<React/..>"	2016-11-23 07:58:39 -08:00
UIExplorer-tvOS	Apple TV support 2: Xcode projects and CI (scripts/objc-test.sh)	2016-10-05 07:28:44 -07:00
UIExplorer.xcodeproj	Redo exported headers and include paths for opensource	2016-12-07 15:28:29 -08:00
UIExplorerIntegrationTests	unselectedItemTintColor property available since iOS10	2016-11-29 12:28:55 -08:00
UIExplorerUnitTests	Rename C api	2016-12-03 04:44:10 -08:00
android/app	Handle "Never Ask Again" in permissions and add requestMultiplePermissions	2016-11-24 22:43:28 -08:00
js	Reworking keyboardShouldPersistTaps to have a middle ground	2016-12-07 21:43:35 -08:00
README.md	Consolidate Running on Device (Android\|iOS) Guides into one	2016-11-06 21:13:32 -08:00

README.md

UIExplorer

The UIExplorer is a sample app that showcases React Native views and modules.

Running this app

Before running the app, make sure you ran:

git clone https://github.com/facebook/react-native.git
cd react-native
npm install

Running on iOS

Mac OS and Xcode are required.

Open Examples/UIExplorer/UIExplorer.xcodeproj in Xcode
Hit the Run button

See Running on device if you want to use a physical device.

Running on Android

You'll need to have all the prerequisites (SDK, NDK) for Building React Native installed.

Start an Android emulator (Genymotion is recommended).

cd react-native
./gradlew :Examples:UIExplorer:android:app:installDebug
./packager/packager.sh

Note: Building for the first time can take a while.

Open the UIExplorer app in your emulator.

See Running on Device in case you want to use a physical device.

Running with Buck

Follow the same setup as running with gradle.

Install Buck from here.

Run the following commands from the react-native folder:

./gradlew :ReactAndroid:packageReactNdkLibsForBuck
buck fetch uiexplorer
buck install -r uiexplorer
./packager/packager.sh

Note: The native libs are still built using gradle. Full build with buck is coming soon(tm).

Built from source

Building the app on both iOS and Android means building the React Native framework from source. This way you're running the latest native and JS code the way you see it in your clone of the github repo.

This is different from apps created using react-native init which have a dependency on a specific version of React Native JS and native code, declared in a package.json file (and build.gradle for Android apps).