History

Spencer Ahrens 2a1ab36257 Breaking API change - abandon `ItemComponent` in favor of `renderItem` Summary: After a fair bit of use, we have concluded that the `ItemComponent` mechanism is not worth the hassle. Flow has trouble type checking it thoroughly, requiring an 'item' prop is annoying, and it is very common to need to capture `this` anyway, e.g. for an `onPress` handler. A common pattern was something like: _renderItem = ({item}) => <MyItem foo={item.foo} onPress={() => this._onPress(item)} />}; ... ItemComponent={this._renderItem} which wouldn't flow check the props and doesn't benefit from reusing components. If we find some specific patterns that would benefit from the `ItemComponent` pattern, we can create a new component that provides that API and wraps `FlatList` under the hood. I'm going to do `SectionList` in a stacked diff. Reviewed By: bvaughn Differential Revision: D4625338 fbshipit-source-id: a4901f1c9d77e0115b0b8032b8c210f624e97ea3		2017-02-28 02:17:23 -08:00
..
UIExplorer	Usage `intrinsicContentSize` property of `RCTRootView` intead of deprecated `intrinsicSize`	2017-02-27 14:04:58 -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	rename UIExplorerUnitTests/TestBundle to UIExplorerUnitTests/UIExplorerUnitTestsBundle	2017-02-27 14:04:56 -08:00
UIExplorerCxx.xcodeproj	rename UIExplorerUnitTests/TestBundle to UIExplorerUnitTests/UIExplorerUnitTestsBundle	2017-02-27 14:04:56 -08:00
UIExplorerIntegrationTests	Add missing reference image for tvOS ImageSnapshotTest	2017-02-17 05:20:15 -08:00
UIExplorerUnitTests	rename UIExplorerUnitTests/TestBundle to UIExplorerUnitTests/UIExplorerUnitTestsBundle	2017-02-27 14:04:56 -08:00
android/app	Apply auto-formatter for BUCK files in fbandroid.	2017-02-27 14:04:56 -08:00
js	Breaking API change - abandon `ItemComponent` in favor of `renderItem`	2017-02-28 02:17:23 -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).