在使用 React Native(如下简称 RN ) 开发移动App时,会碰到不少弹窗的场景,虽然 RN自带了一个 Modal 组件能够实现这一效果,可是因为Android和iOS平台的差别性,使得使用同一个组件开发出来的效果会略有差别。好比,Modal组件在iOS平台,弹框是全屏的,可是在Android平台却不是,会有状态栏,以下效果。
之因此这样,是由于Android 端的Modal 控件使用的Dialog,内容没法从状态栏处开始布局。而iOS是基于 Window 的,因此是覆盖在视图上面的。若是要让双端的样式同样,那么须要对Android进行特殊处理。react
因为RN的Modal 组件在Android中是使用Dialog实现的,因此若是要实现一个全屏的弹框,那么就须要自定义一个全屏展现的Dialog。android
首先,咱们新建一个继承自Dialog的自定义组件FullModal,代码以下:ios
package com.cgv.cn.movie.modal; import android.app.Dialog; import android.content.Context; import android.view.View; import androidx.annotation.NonNull; import androidx.annotation.StyleRes; public class FullModal extends Dialog { private boolean isDarkMode; private View rootView; public void setDarkMode(boolean isDarkMode) { this.isDarkMode = isDarkMode; } public FullModal(@NonNull Context context, @StyleRes int themeResId) { super(context, themeResId); } @Override public void setContentView(@NonNull View view) { super.setContentView(view); this.rootView = view; } @Override public void show() { super.show(); StatusBarUtil.setTransparent(getWindow()); if (isDarkMode) { StatusBarUtil.setDarkMode(getWindow()); } else { StatusBarUtil.setLightMode(getWindow()); } AndroidWorkaround.assistView(rootView, getWindow()); } }
在上面的代码中,StatusBarUtil.setTransparent(getWindow())
方法的主要做用就是将状态栏背景透明,而且让布局内容能够从 Android 状态栏开始。而后咱们看一下setTransparent()方法的实现。app
@TargetApi(Build.VERSION_CODES.KITKAT) private static void transparentStatusBar(Window window) { if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) { View decorView = window.getDecorView(); int option = View.SYSTEM_UI_FLAG_LAYOUT_FULLSCREEN | View.SYSTEM_UI_FLAG_LAYOUT_STABLE; decorView.setSystemUiVisibility(option); window.setStatusBarColor(Color.TRANSPARENT); } else { window.addFlags(WindowManager.LayoutParams.FLAG_TRANSLUCENT_STATUS); } }
须要说明的是,transparentStatusBar()方法只在 Android 4.4 以上才会有效果,Android 4.4以前要实现沉浸式状态栏须要使用其余的方式(好比反射)。不过如今都已是9012年了, Android 4.4版本的应该不多了吧。ide
自定义的原生组件开发完成以后,接下来就是按照RN和原生交互的规则进行RN的封装。首先,新建一个FullModalManager类,该类的主要做用就是RN的Android和Js的通讯桥梁,代码以下。布局
public class FullModalManager extends ViewGroupManager<FullModalView> { @Override public String getName() { return "RCTFullScreenModalHostView"; } public enum Events { ON_SHOW("onFullScreenShow"), ON_REQUEST_CLOSE("onFullScreenRequstClose"); private final String mName; Events(final String name) { mName = name; } @Override public String toString() { return mName; } } @Override @Nullable public Map getExportedCustomDirectEventTypeConstants() { MapBuilder.Builder builder = MapBuilder.builder(); for (Events event : Events.values()) { builder.put(event.toString(), MapBuilder.of("registrationName", event.toString())); } return builder.build(); } @Override protected FullModalView createViewInstance(ThemedReactContext reactContext) { final FullModalView view = new FullModalView(reactContext); final RCTEventEmitter mEventEmitter = reactContext.getJSModule(RCTEventEmitter.class); view.setOnRequestCloseListener(new FullModalView.OnRequestCloseListener() { @Override public void onRequestClose(DialogInterface dialog) { mEventEmitter.receiveEvent(view.getId(), Events.ON_REQUEST_CLOSE.toString(), null); } }); view.setOnShowListener(new DialogInterface.OnShowListener() { @Override public void onShow(DialogInterface dialog) { mEventEmitter.receiveEvent(view.getId(), Events.ON_SHOW.toString(), null); } }); return view; } @Override public LayoutShadowNode createShadowNodeInstance() { return new FullScreenModalHostShadowNode(); } @Override public Class<? extends LayoutShadowNode> getShadowNodeClass() { return FullScreenModalHostShadowNode.class; } @Override public void onDropViewInstance(FullModalView view) { super.onDropViewInstance(view); view.onDropInstance(); } @ReactProp(name = "autoKeyboard") public void setAutoKeyboard(FullModalView view, boolean autoKeyboard) { view.setAutoKeyboard(autoKeyboard); } @ReactProp(name = "isDarkMode") public void setDarkMode(FullModalView view, boolean isDarkMode) { view.setDarkMode(isDarkMode); } @ReactProp(name = "animationType") public void setAnimationType(FullModalView view, String animationType) { view.setAnimationType(animationType); } @ReactProp(name = "transparent") public void setTransparent(FullModalView view, boolean transparent) { view.setTransparent(transparent); } @ReactProp(name = "hardwareAccelerated") public void setHardwareAccelerated(FullModalView view, boolean hardwareAccelerated) { view.setHardwareAccelerated(hardwareAccelerated); } @Override protected void onAfterUpdateTransaction(FullModalView view) { super.onAfterUpdateTransaction(view); view.showOrUpdate(); } }
FullModalManager类最重要的createViewInstance()方法。而且,在事件通讯中,RN的Modal 已经存在了onShow()和 onRequestClose()回调,可是这里不能再使用这两个命名,因此这里改为了 onFullScreenShow 和 onFullScreenRequstClose,可是在Js端仍是从新命名成 onShow 和 onRequestClose ,因此在使用过程当中仍是没有任何变化。flex
在RN的Js部分,咱们只须要处理 Android 的实现便可,而对于iOS部分则不须要处理。为了方便在RN代码中进行引用,咱们能够参考RN自定义组件的方式新建FullModal.android.js和FullModal.ios.js两个文件,其中FullModal.android.js的源码以下。ui
const FullScreenModal = requireNativeComponent('RCTFullScreenModalHostView', null); export default class FullModalViewAndroid extends Component { _shouldSetResponder = () => { return true; } static propTypes = { isDarkMode: PropTypes.bool, // false 表示白底黑字,true 表示黑底白字 autoKeyboard: PropTypes.bool, // 未知缘由的坑,modal中的edittext自动弹起键盘要设置这个参数为true }; render() { if (this.props.visible === false) { return null; } const containerStyles = { backgroundColor: this.props.transparent ? 'transparent' : 'white', }; return ( <FullScreenModal style={{position: 'absolute'}} {...this.props} onStartShouldSetResponder={this._shouldSetResponder} onFullScreenShow={() => this.props.onShow && this.props.onShow()} onFullScreenRequstClose={() => this.props.onRequestClose && this.props.onRequestClose()}> <View style={[{position: 'absolute', left: 0, top: 0}, containerStyles]}> {this.props.children} </View> </FullScreenModal> ); } }
接下来,咱们就能够在业务代码中进行使用了,以下所示。this
const ModalView = tools.isIos ? Modal : FullModal return ( <ModalView transparent={false} visible={targetShow} onRequestClose={() => { }}> <View style={{ flex: 1 }}> ...//省略其余代码 </View> </ModalView> )
附,相关源码spa