小手动一动，点赞转发加关注。微信搜索【大前端杂货铺】公众号关注大前端老司机带您遨游大前端知识的海洋。关注 Github https://github.com/big-frontend 还有大前端代码实践哦。
名词解释
- 渲染器renderer: 使用React 提供的npm包react-reconciler 可以自定义渲染器renderer，React Native渲染器的npm包为react-native-renderer,github仓库为packages/react-native-renderer。React的渲染器renderer有React DOM、React Native、Ink，用于适配各个平台，浏览器、移动端、终端等
- 渲染流水线pipeline：pipeline 的原义是将计算机指令处理过程拆分为多个步骤，并通过多个硬件处理单元并行执行来加快指令执行速度。其具体执行过程类似工厂中的流水线，并因此得名。React Native 渲染器(Fabric Renderer)在多个线程之间分配渲染流水线（render pipeline）任务。
- 渲染流水线可大致分为三个阶段phase：
- 渲染（Render）
- 提交（Commit）
- 挂载（Mount）
- 线程模型：渲染流水线的各个阶段可能发生在不同的线程，大多数渲染流水线发生在javascript线程与后台线程，当UI线程上有高优先级事件，渲染器能够在 UI 线程上同步执行所有渲染流水线。
- UIThread
- JSThread
- BGThread
React Native渲染场景我们分为初次渲染与状态更新。
react元素树 ---> shadow树 ---> android view树
在2022年react native的团队规划中，做了一次大的技术改造，将shadow树在cpp中实现，react采用fabric，整个渲染流水线发生了较大的变动。目前代码还没有完成，等完成再来分析。除了官方的优化，shopify在渲染这块也做了大胆的尝试，抛弃了平台渲染直接用skia进行dom树渲染，项目这里react-native-skia
自定义native ui component
先来点代码示例看看如何定义并且使用native ui component
native ui componetn 声明
// view
internal class MyImageView @JvmOverloads constructor(
context: Context, attrs: AttributeSet? = null, defStyleAttr: Int = -1
) : androidx.appcompat.widget.AppCompatImageView(
context, attrs, defStyleAttr
) {
init {
Log.d("cjf","MyImageView init")
}
fun setSource(sources: ReadableArray?) {
Log.d("cjf","source:"+sources)
}
fun setBorderRadius(borderRadius: Float) {
Log.d("cjf","setBorderRadius:"+borderRadius)
}
fun setScaleType(toScaleType: ScalingUtils.ScaleType?) {}
fun onReceiveNativeEvent() {
val event = Arguments.createMap()
event.putString("message", "MyMessage")
val reactContext = context as ReactContext
reactContext.getJSModule(RCTEventEmitter::class.java).receiveEvent(id, "topChange", event)
}
}
//view manager
public class MyImageViewManager extends SimpleViewManager<MyImageView> {
ReactApplicationContext mCallerContext;
public MyImageViewManager(ReactApplicationContext reactContext) {
mCallerContext = reactContext;
}
@Override
public String getName() {
return "MyImageView";
}
@Override
public MyImageView createViewInstance(ThemedReactContext context) {
return new MyImageView(context);
}
@ReactProp(name = "src")
public void setSrc(MyImageView view, @Nullable ReadableArray sources) {
view.setSource(sources);
}
@ReactProp(name = "borderRadius", defaultFloat = 0f)
public void setBorderRadius(MyImageView view, float borderRadius) {
view.setBorderRadius(borderRadius);
}
@ReactProp(name = ViewProps.RESIZE_MODE)
public void setResizeMode(MyImageView view, @Nullable String resizeMode) {
view.setScaleType(ImageResizeMode.toScaleType(resizeMode));
}
@Override
public Map getExportedCustomBubblingEventTypeConstants() {
//java层的topChange 与 js层的onChange进行映射
return MapBuilder.builder().put(
"topChange",
MapBuilder.of(
"phasedRegistrationNames",
MapBuilder.of("bubbled", "onChange")
)
).build();
}
}
//包
public class MyAppPackage implements ReactPackage {
@Override
public List<NativeModule> createNativeModules(ReactApplicationContext reactContext) {
List<NativeModule> modules = new ArrayList<>();
modules.add(new CalendarModule(reactContext));
return modules;
}
@Override
public List<ViewManager> createViewManagers(ReactApplicationContext reactContext) {
return Arrays.asList(new MyImageViewManager(reactContext));
}
}
myview.js文件
import { NativeModules, Button, requireNativeComponent } from "react-native";
import React from "react";
class MyCustomView extends React.Component {
constructor(props) {
super(props);
this._onChange = this._onChange.bind(this);
}
_onChange(event) {
if (!this.props.onChangeMessage) {
return;
}
this.props.onChangeMessage(event.nativeEvent.message);
}
render() {
const MyImageView = requireNativeComponent("MyImageView");
return <MyImageView {...this.props} onChange={this._onChange} />;
}
}
module.exports = MyCustomView;
app.js文件
import MyCustomView from './myviews';
export default function App() {
return (
<View style={styles.container}>
<Text>Open up App.js to start working on your app!</Text>
<StatusBar style="auto" />
<MyCustomView></MyCustomView>
</View>
);
}
在myview.js文件中通过requireNativeComponent函数加载HostComponent(native ui component).
requireNativeComponent.js
const requireNativeComponent = <T>(uiViewClassName: string): HostComponent<T> =>
((createReactNativeComponentClass(uiViewClassName, () =>
getNativeComponentAttributes(uiViewClassName),
): any): HostComponent<T>);
调用requireNativeComponent函数时会将组件名为key，获取组件属性的闭包存储在viewConfigCallbacks结构中。
react应用页面初次渲染
渲染阶段
渲染阶段会创建shadow树，shadow树用于布局(layout)ui，关于布局的计算会在提交阶段，那么来看看如何创建shadow树的。之前在react应用启动流程篇章里面，最后我们讲到调用ReactNativeRenderer-prod.js中render函数进行组件的渲染时，会先创建ReactRootView对应的根节点FiberRootNode，接下就updateContainer开始渲染各个组件。
//element：PerformanceLoggerContext.Provider 树 ，container：FiberRootNode
function updateContainer(element, container, parentComponent, callback) {
var current = container.current,
eventTime = requestEventTime(),
lane = requestUpdateLane(current);
a: if (parentComponent) {
...
} else parentComponent = emptyContextObject;
//FiberRootNode的context为null
null === container.context
? (container.context = parentComponent)
: (container.pendingContext = parentComponent);
container = createUpdate(eventTime, lane);
container.payload = { element: element };
callback = void 0 === callback ? null : callback;
null !== callback && (container.callback = callback);
enqueueUpdate(current, container);
element = scheduleUpdateOnFiber(current, lane, eventTime);
null !== element && entangleTransitions(element, current, lane);
return lane;
}
workInProgress的tag为5或者6时调用ReactNativePrivateInterface.UIManager.createView创建组件
UIManager.js
{:.fileName}
//UIManagerJSInterface 接口声明
export interface UIManagerJSInterface extends Spec {
+getViewManagerConfig: (viewManagerName: string) => Object;
+hasViewManagerConfig: (viewManagerName: string) => boolean;
+createView: (
reactTag: ?number,
viewName: string,
rootTag: RootTag,
props: Object,
) => void;
+updateView: (reactTag: number, viewName: string, props: Object) => void;
+manageChildren: (
containerTag: ?number,
moveFromIndices: Array<number>,
moveToIndices: Array<number>,
addChildReactTags: Array<number>,
addAtIndices: Array<number>,
removeAtIndices: Array<number>,
) => void;
}
//BridgelessUIManager文件或者PaperUIManager文件为UIManagerJSInterface 接口实现
const UIManager: UIManagerJSInterface =
global.RN$Bridgeless === true
? require('./BridgelessUIManager')//log打印
: require('./PaperUIManager');//真正的实现
module.exports = UIManager;
NativeUIManager.js
export interface Spec extends TurboModule {
+createView: (
reactTag: ?number,
viewName: string,
rootTag: RootTag,
props: Object,
) => void;
}
// 通过global.__turboModuleProxy获取名为UIManager的模块
export default (TurboModuleRegistry.getEnforcing<Spec>('UIManager'): Spec);
js侧与java侧的接口调用主要采用turbo，所以js侧UIManager对应的java侧UIManagerModule，如果不理解turbo，可以查看这一篇文章React Native—Java和JavaScript互操作
@ReactModule(name = UIManagerModule.NAME)
public class UIManagerModule extends ReactContextBaseJavaModule
implements OnBatchCompleteListener, LifecycleEventListener, UIManager {
...
@ReactMethod
public void createView(int tag, String className, int rootViewTag, ReadableMap props) {
if (DEBUG) {
String message =
"(UIManager.createView) tag: " + tag + ", class: " + className + ", props: " + props;
FLog.d(ReactConstants.TAG, message);
PrinterHolder.getPrinter().logMessage(ReactDebugOverlayTags.UI_MANAGER, message);
}
mUIImplementation.createView(tag, className, rootViewTag, props);
}
...
}
根据设计模式为了保持java侧与js侧的接口一致性UIManagerModule只负责接口声明，实现全部交给UIImplementation。
public class UIImplementation {
protected Object uiImplementationThreadLock = new Object();
//事件分发
protected final EventDispatcher mEventDispatcher;
protected final ReactApplicationContext mReactContext;
//shadow node的注册中心，shadow树
protected final ShadowNodeRegistry mShadowNodeRegistry = new ShadowNodeRegistry();
//ViewManager注册中心，管理ui组件
private final ViewManagerRegistry mViewManagers;
//存放来自于js侧操作dom的指令
private final UIViewOperationQueue mOperationsQueue;
private final NativeViewHierarchyOptimizer mNativeViewHierarchyOptimizer;
private final int[] mMeasureBuffer = new int[4];
private long mLastCalculateLayoutTime = 0;
protected @Nullable LayoutUpdateListener mLayoutUpdateListener;
...
public void createView(int tag, String className, int rootViewTag, ReadableMap props) {
if (!mViewOperationsEnabled) {
return;
}
synchronized (uiImplementationThreadLock) {
ReactShadowNode cssNode = createShadowNode(className);
ReactShadowNode rootNode = mShadowNodeRegistry.getNode(rootViewTag);
Assertions.assertNotNull(rootNode, "Root node with tag " + rootViewTag + " doesn't exist");
cssNode.setReactTag(tag); // Thread safety needed here
cssNode.setViewClassName(className);
cssNode.setRootTag(rootNode.getReactTag());
cssNode.setThemedContext(rootNode.getThemedContext());
mShadowNodeRegistry.addNode(cssNode);
ReactStylesDiffMap styles = null;
if (props != null) {
styles = new ReactStylesDiffMap(props);
cssNode.updateProperties(styles);
}
handleCreateView(cssNode, rootViewTag, styles);
}
}
protected void handleCreateView(
ReactShadowNode cssNode, int rootViewTag, @Nullable ReactStylesDiffMap styles) {
if (!cssNode.isVirtual()) {
mNativeViewHierarchyOptimizer.handleCreateView(cssNode, cssNode.getThemedContext(), styles);
}
}
}
从UIImplementation的成员变量就能大概猜测其职能，维系一棵js侧树的shadow树来决定prop有没有发生变化，变化了就会发送操作指令create、update对真实的dom树进行更新。在createView阶段，会创建ShadowNode(LayoutShadowNode)对js侧的react dom树进行shadow。
整棵shadow树的基石是yoga，关于yoga后续有空可以来讲解一下。NativeViewHierarchyOptimizer会将操作指令发送到UIViewOperationQueue。等到了下一帧绘制时，读取并且处理队列中的指令，比如ViewManager#createView方法。
提交阶段
当渲染阶段的renderApplicatioin执行完成，cpp层的callFunctionReturnFlushedQueue_#call得到结果之后，经过一系列的调用链最后会调用UIManagerModule#onBatchComplete在mqt_native后台线程计算shadow树的布局。
UIImplementation.java
{:.fileName}
public class UIImplementation {
/** Invoked at the end of the transaction to commit any updates to the node hierarchy. */
public void dispatchViewUpdates(int batchId) {
...
try {
updateViewHierarchy();
mNativeViewHierarchyOptimizer.onBatchComplete();
mOperationsQueue.dispatchViewUpdates(batchId, commitStartTime, mLastCalculateLayoutTime);
} finally {
...
}
}
protected void updateViewHierarchy() {
...
try {
for (int i = 0; i < mShadowNodeRegistry.getRootNodeCount(); i++) {
int tag = mShadowNodeRegistry.getRootTag(i);
ReactShadowNode cssRoot = mShadowNodeRegistry.getNode(tag);
if (cssRoot.getWidthMeasureSpec() != null && cssRoot.getHeightMeasureSpec() != null) {
...
try {
notifyOnBeforeLayoutRecursive(cssRoot);
} finally {
Systrace.endSection(Systrace.TRACE_TAG_REACT_JAVA_BRIDGE);
}
calculateRootLayout(cssRoot);
SystraceMessage.beginSection(
Systrace.TRACE_TAG_REACT_JAVA_BRIDGE, "UIImplementation.applyUpdatesRecursive")
.arg("rootTag", cssRoot.getReactTag())
.flush();
try {
applyUpdatesRecursive(cssRoot, 0f, 0f);
} finally {
Systrace.endSection(Systrace.TRACE_TAG_REACT_JAVA_BRIDGE);
}
if (mLayoutUpdateListener != null) {
mOperationsQueue.enqueueLayoutUpdateFinished(cssRoot, mLayoutUpdateListener);
}
}
}
} finally {
...
}
}
}
- updateViewHierarchy：calculateRootLayout计算shadow树的布局，包括width、height,applyUpdatesRecursive会把每个需要更新的shadow节点信息push到指令queue里面，等到下一帧到来处理
- dispatchViewUpdates: view command operations、non batched operations、batched operations会在下一帧绘制时在UI线程被处理
挂载阶段
挂载阶段为vsync信号发送到来之后，会调用DispatchUIFrameCallback。
UIViewOperationQueue.java
{:.fileName}
private final class CreateViewOperation extends ViewOperation {
...
@Override
public void execute() {
Systrace.endAsyncFlow(Systrace.TRACE_TAG_REACT_VIEW, "createView", mTag);
mNativeViewHierarchyManager.createView(mThemedContext, mTag, mClassName, mInitialProps);
}
...
}
private final class UpdateLayoutOperation extends ViewOperation {
...
@Override
public void execute() {
Systrace.endAsyncFlow(Systrace.TRACE_TAG_REACT_VIEW, "updateLayout", mTag);
mNativeViewHierarchyManager.updateLayout(mParentTag, mTag, mX, mY, mWidth, mHeight);
}
...
}
最先执行的ui原子操作指令为create，去构造某个View, 而update layout 指令是接下来负责将shadow树的layout结果更新到view树的每个节点
react应用页面状态更新
public class UIImplementation {
...
/** Invoked by React to create a new node with a given tag has its properties changed. */
public void updateView(int tag, String className, ReadableMap props) {
if (!mViewOperationsEnabled) {
return;
}
ViewManager viewManager = mViewManagers.get(className);
if (viewManager == null) {
throw new IllegalViewOperationException("Got unknown view type: " + className);
}
ReactShadowNode cssNode = mShadowNodeRegistry.getNode(tag);
if (cssNode == null) {
throw new IllegalViewOperationException("Trying to update non-existent view with tag " + tag);
}
if (props != null) {
ReactStylesDiffMap styles = new ReactStylesDiffMap(props);
cssNode.updateProperties(styles);
handleUpdateView(cssNode, className, styles);
}
}
protected void handleUpdateView(
ReactShadowNode cssNode, String className, ReactStylesDiffMap styles) {
if (!cssNode.isVirtual()) {
mNativeViewHierarchyOptimizer.handleUpdateView(cssNode, className, styles);
}
}
...
}
更新流程的调用链UIImplementation#updateView ---> UIImplementation#handleUpdateView ---> NativeViewHierarchyOptimizer#handleUpdateView ---> UIViewOperationQueue#enqueueUpdateProperties ---> android系统绘制下一帧时 ---> UpdatePropertiesOperation#execute。
在NativeViewHierarchyOptimizer#handleUpdateView的逻辑中通过shadow树判断要不要将更新的指令放到UIViewOperationQueue中。等到android系统开始绘制下一帧时，会从UIViewOperationQueue获取指令并且处理
private final class UpdatePropertiesOperation extends ViewOperation {
private final ReactStylesDiffMap mProps;
private UpdatePropertiesOperation(int tag, ReactStylesDiffMap props) {
super(tag);
mProps = props;
}
@Override
public void execute() {
mNativeViewHierarchyManager.updateProperties(mTag, mProps);
}
}
调用链NativeViewHierarchyManager#updateProperties ---> ViewManager#updateProperties ---> ViewManagerPropertyUpdater#updateProps ---> FallbackViewManagerSetter#setProperty ---> ViewManagersPropertyCache.PropSetter#updateViewProp
实例化FallbackViewManagerSetter对象的时候，会扫描ViewManager带有ReactProp注解的方法，并保存到ViewManagersPropertyCache的map中，当在setProperty刷新每个属性时，就会调用其对应的方法进行正在ui更新。
之前我们讲过NativeViewHierarchyOptimizer#handleUpdateView会通过shadow树判断要不要更新属性，这块我们深挖一下。在UIImplementation#updateView过程中，会执行两个重要事情，一个updateProperties shadow树的节点，另外一个NativeViewHierarchyOptimizer#handleUpdateView。
参考资料
The how and why on React’s usage of linked list in Fiber to walk the component’s tree
小手动一动，点赞转发加关注。微信搜索【大前端杂货铺】公众号关注大前端老司机带您遨游大前端知识的海洋。关注 Github https://github.com/big-frontend 还有大前端代码实践哦。
1万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
