ANDROID图形系统详解.docVIP

ANDROID图形系统详解 本文试图讲述Android图形系统的底层实现。Android图形系统底层实现非常复杂，文档较少，没有使用比较流行的图形组建如Xwindow, Cairo等。Android中的图形系统采用Client/Server架构。Server(即SurfaceFlinger)主要由c++代码编写而成。Client端代码分为两部分，一部分是由Java提供的供应用使用的api,另一部分则是由c++写成的底层实现。下图概要介绍了android图形系统的架构以及使用到的主要组件。Android图形系统中一个重要的概念和线索是surface。View及其子类（如TextView,Button）要画在surface上。每个surface创建一个Canvas对象（但属性时常改变），用来管理view在surface上的绘图操作，如画点画线。每个canvas对象对应一个bitmap，存储画在surface上的内容。每个Surface通常对应两个buffer，一个front buffer, 一个back buffer。其中，back buffer就是canvas绘图时对应的bitmap (研究android_view_Surface.cpp::lockCanvas)。因此，绘画总是在backbuffer上，需要更新时，则将back buffer和front buffer互换。The window is tied to a Surface and the ViewRoot asks the Surfacefor aCanvas that is then used by the Views to draw onto. After View drawits data to canvas, ViewRootwill call surface.unlockCanvasAndPost(canvas) to schedulesurfaceFlinger::composeSurfaces() which do the actually displayto牋display panel. SurfaceFlinger handles to transfers drawn data in canvas to surfacefront buffer or backbufferExcept for SurfaceViews, different views within the same ViewRootshare the same surface.Layer的概念：每个surface又对应一个layer, SurfaceFlinger负责将各个layer的frontbuffer合成（composite）绘制到屏幕上。A Layer is something that can be composited by SurfaceFlinger (shouldhave been called LayerFlinger). There are several types of Layers ifyou look in the code,??in particular the regular ones (Layer.cpp) ,they are backed by a Surface, and the LayerBuffer (very badly chosenname) which dont have a backing store, but receive one from theirclient. .Note that the GGLSurface type, should have been called GGLBufferMultiple layers are just composited to the final buffer in牋their Z order.有几个对象与Surface概念紧密相关：1. Java Surface（frameworks/base/core/java/android/view/Surface.java）。该对象被应用间接调用（通过SurfaceView,ViewRoot等）， 应用需要创建surface,（并同时创建canvas）,将图形绘制到这个对象上并最终投递到屏幕上。2. C++ Surface (frameworks/base/libs/ui/Surface.cpp。 这个对象被JavaSurface通过Jni 调用，实现Java Surface 的功能3. ISurface (以及其派生类Bn