Introduction (中文)
The react-native-awesome-navigation is a native navigation based on iOS UIViewController and Android Activity/Fragment. The purpose we are doing this is that the popular react-navigation's performance cannot satify our react-navie based application, especially on Android. Thanks to Khan Academy's Our Transition to React Native give us inspiration, we decide to develop this project, and it has been already use in our commercial application, and it will be keep optimizing and updating.
Before you decided to use this, feel free to play the example first, just read this instruct to play example
yarn add react-native-awesome-navigation
or
npm install react-native-awesome-navigation
Ensure your build files match the following requirements:
- (React Native 0.59 and lower) Define the
react-native-awesome-navigation
project inandroid/settings.gradle
:
...
include ':react-native-awesome-navigation'
project(':react-native-awesome-navigation').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-awesome-navigation/android')
- (React Native 0.59 and lower) Add the
react-native-awesome-navigation
as an dependency of your app inandroid/app/build.gradle
:
...
dependencies {
...
implementation project(':react-native-awesome-navigation')
}
Using React Native Link (React Native 0.59 and lower)
Run react-native link react-native-awesome-navigation
after which you should be able to use this library on iOS.
Put following code in index
file or you can also copy following code to individual file and import it in index
also works, as you wish.
import { Register, setStyle } from 'react-native-awesome-navigation';
import {Image} from 'react-native'
import Home from './src/Home'
import TabBar from './src/TabBar'
import Setting from './src/Setting'
// setting global style
setStyle({
hideBackTitle: true,
hideNavigationBarShadow: true,
navigationBarColor: '#FFFFFF',
navigationBarItemColor: 'FF84A9',
tabBarColor: '#FFFFFF',
tabBarItemColor: '#FF84A9',
backIcon: Image.resolveAssetSource(require('./src/image/Profile.png')),
})
Register.beforeRegister()
// register component,and set root page
Register.registerComponent('Home', Home);
Register.registerComponent('Setting', Setting);
Register.registerComponent('TabBar', TabBar)
Register.setRoot({
root: {
bottomTabs: {
children: [
{
component: {
name: 'Home',
options: {title: '主页', icon: Image.resolveAssetSource(require('./src/image/Home.png'))},
},
},
{
component: {
name: 'Setting',
options: {title: '设置', icon: Image.resolveAssetSource(require('./src/image/Setting.png'))},
},
},
],
options: {tabBarModuleName: 'TabBar'},
},
},
})
Support native page and RN page mash up Currently offer two native style setting Setting title bar title and whether hide title bar or not
Home.navigationItem = {
title: 'MainPage',
hideNavigationBar: false,
}
Currently support push
, pop
, popToRoot
, present
, dismiss
, switchTab
push
pass parameter
props.navigator.push('NativeViewController', { title: 'Native' })
push
receive parameter
const resp = await props.navigator.push('Detail')
Set value before pop
props.navigator.setResult({qwe: 123})
props.navigator.pop()
pop
multi pages (currently only support all push
pages not for present
pages)
props.navigator.popPages(2) // pop 2 pages
The present
is similar with push, the 2nd is a nullable parameter, the 3rd parameter is for config screen and nullable.
props.navigator.present('Present', undefined, {isFullScreen: true})
Like push
, support asynchronous
const resp = await props.navigator.present('Present', undefined, {isFullScreen: true})
interface PresentOption {
isFullScreen?: boolean // Only for iOS, `present` a full screen or not
isTransparency?: boolean // is transparency background or not
animated?: boolean // play animation or not
isTabBarPresented?: boolean // label custom TabBar Prensent or not
}
dismiss
present
props.navigator.dismiss()
switchTab
is for switch tab to position.
props.navigator.switchTab(0)
Every page will be enrolled their own navigator, navigator have a unique screenID and module name ,through navigator to manipulate page.
Currently include styles follows,continue updating.
interface GlobalStyle {
backIcon?: {uri: string} // set back icon
hideNavigationBarShadow?: boolean // if hide tool bar shadow
hideBackTitle?: boolean // if hide title next to back icon
navigationBarColor?: string // tool bar background color
navigationBarItemColor?: string // tool bar item color
tabBarColor?: string // tabbar background color
tabBarItemColor?: string // tabbar picked color
tabBarDotColor?: string // tabbar dot color
}
Example
setStyle({
hideBackTitle: true,
hideNavigationBarShadow: true,
navigationBarColor: '#FFFFFF',
navigationBarItemColor: 'FF84A9',
tabBarColor: '#FFFFFF',
tabBarItemColor: '#FF84A9',
backIcon: Image.resolveAssetSource(CloseIcon),
})
Toolbar can be set Badge as well.
setTabBadge([
{
index: 0,
hidden: false,
dot: true,
},
{
index: 1,
text: '1199',
hidden: false,
},
])
export interface TabBadge {
index: number
hidden: boolean
text?: string
dot?: boolean
}
Color is only support hexadecimal string, not support color string like 'red'.
Each page has their own hooks to check if the page is focused.
useVisibleEffect(
props.screenID,
useCallback(() => {
console.log(`${props.screenID} is visible`)
return () => {
console.log(`${props.screenID} is gone`)
}
}, [])
)
Adding route when register
Register.registerComponent('Home', Home, '/home')
Register.registerComponent('Setting', Setting)
Activiting at first page
useEffect(() => {
router.activate('hulaqinzi://')
return () => {
router.inactivate()
}
}, [])
Router.open('hulaqinzi://home?key=value')
Link address will be parsed as /home,paramter {key: value},and push to Home page and pass parameter.
This is for pass parameter when a page pop back.
useResult(props.screenID, (data) => {
console.log(data);
})
Type can be return ok or cancel.
Ok means back with value,cancel normal back.
Data is back value.
Resopse click tabbar repeatly,this is only for each tab bar first page. (iOS only)
useReClick(props.screenID, () => {
console.log('reclick');
})
See the contributing guide to learn how to contribute to the repository and the development workflow.