SurfaceView基本使用

SurfaceView原理

Here are some definitions:

A Surface is an object holding pixels that are being composited to the screen. Every window you see on the screen (a dialog, your full-screen activity, the status bar) has its own surface that it draws in to, and Surface Flinger renders these to the final display in their correct Z-order. A surface typically has more than one buffer (usually two) to do double-buffered rendering: the application can be drawing its next UI state while the surface flinger is compositing the screen using the last buffer, without needing to wait for the application to finish drawing.

A window is basically like you think of a window on the desktop. It has a single Surface in which the contents of the window is rendered. An application interacts with the Window Manager to create windows; the Window Manager creates a Surface for each window and gives it to the application for drawing. The application can draw whatever it wants in the Surface; to the Window Manager it is just an opaque rectangle.

A View is an interactive UI element inside of a window. A window has a single view hierarchy attached to it, which provides all of the behavior of the window. Whenever the window needs to be redrawn (such as because a view has invalidated itself), this is done into the window's Surface. The Surface is locked, which returns a Canvas that can be used to draw into it. A draw traversal is done down the hierarchy, handing the Canvas down for each view to draw its part of the UI. Once done, the Surface is unlocked and posted so that the just drawn buffer is swapped to the foreground to then be composited to the screen by Surface Flinger.

A SurfaceView is a special implementation of View that also creates its own dedicated Surface for the application to directly draw into (outside of the normal view hierarchy, which otherwise must share the single Surface for the window). The way this works is simpler than you may expect -- all SurfaceView does is ask the window manager to create a new window, telling it to Z-order that window either immediately behind or in front of the SurfaceView's window, and positioning it to match where the SurfaceView appears in the containing window. If the surface is being placed behind the main window (in Z order), SurfaceView also fills its part of the main window with transparency so that the surface can be seen.

A Bitmap is just an interface to some pixel data. The pixels may be allocated by Bitmap itself when you are directly creating one, or it may be pointing to pixels it doesn't own such as what internally happens to hook a Canvas up to a Surface for drawing. (A Bitmap is created and pointed to the current drawing buffer of the Surface.)

Also please keep in mind that, as this implies, a SurfaceView is a pretty heavy-weight object. If you have multiple SurfaceViews in a particular UI, stop and think about whether this is really needed. If you have more than two, you almost certainly have too many.

看下官方API对SurfaceView的介绍

SurfaceView的API介绍

Provides a dedicated drawing surface embedded inside of a view hierarchy. You can control the format of this surface and, if you like, its size; the SurfaceView takes care of placing the surface at the correct location on the screen

The surface is Z ordered so that it is behind the window holding its SurfaceView; the SurfaceView punches a hole in its window to allow its surface to be displayed. The view hierarchy will take care of correctly compositing with the Surface any siblings of the SurfaceView that would normally appear on top of it. This can be used to place overlays such as buttons on top of the Surface, though note however that it can have an impact on performance since a full alpha-blended composite will be performed each time the Surface changes.

Access to the underlying surface is provided via the SurfaceHolder interface, which can be retrieved by calling getHolder().

The Surface will be created for you while the SurfaceView's window is visible; you should implement surfaceCreated(SurfaceHolder) and surfaceDestroyed(SurfaceHolder) to discover when the Surface is created and destroyed as the window is shown and hidden.

One of the purposes of this class is to provide a surface in which a secondary thread can render in to the screen. If you are going to use it this way, you need to be aware of some threading semantics:

•All SurfaceView and SurfaceHolder.Callback methods will be called from the thread running the SurfaceView's window (typically the main thread of the application). They thus need to correctly synchronize with any state that is also touched by the drawing thread. 
•You must ensure that the drawing thread only touches the underlying Surface while it is valid -- between SurfaceHolder.Callback.surfaceCreated() and SurfaceHolder.Callback.surfaceDestroyed(). 
对应的中文翻译
SurfaceView是视图(View)的继承类，这个视图里内嵌了一个专门用于绘制的Surface。你可以控制这个Surface的格式和尺寸。Surfaceview控制这个Surface的绘制位置。
        surface是纵深排序(Z-ordered)的，这表明它总在自己所在窗口的后面。surfaceview提供了一个可见区域，只有在这个可见区域内 的surface部分内容才可见，可见区域外的部分不可见。surface的排版显示受到视图层级关系的影响，它的兄弟视图结点会在顶端显示。这意味者 surface的内容会被它的兄弟视图遮挡，这一特性可以用来放置遮盖物(overlays)(例如，文本和按钮等控件)。注意，如果surface上面 有透明控件，那么它的每次变化都会引起框架重新计算它和顶层控件的透明效果，这会影响性能。
        你可以通过SurfaceHolder接口访问这个surface，getHolder()方法可以得到这个接口。
        surfaceview变得可见时，surface被创建；surfaceview隐藏前，surface被销毁。这样能节省资源。如果你要查看 surface被创建和销毁的时机，可以重载surfaceCreated(SurfaceHolder)和 surfaceDestroyed(SurfaceHolder)。
        surfaceview的核心在于提供了两个线程：UI线程和渲染线程。这里应注意：
        1> 所有SurfaceView和SurfaceHolder.Callback的方法都应该在UI线程里调用，一般来说就是应用程序主线程。渲染线程所要访问的各种变量应该作同步处理。
        2> 由于surface可能被销毁，它只在SurfaceHolder.Callback.surfaceCreated()和 SurfaceHolder.Callback.surfaceDestroyed()之间有效，所以要确保渲染线程访问的是合法有效的surface。

 

接下来呢，说说自己对它的理解
1、定义

可以直接从内存或者DMA等硬件接口取得图像数据,是个非常重要的绘图容器。

它的特性是：可以在主线程之外的线程中向屏幕绘图上。这样可以避免画图任务繁重的时候造成主线程阻塞，从而提高了程序的反应速度。在游戏开发中多用到SurfaceView，游戏中的背景、人物、动画等等尽量在画布canvas中画出。

2、实现

首先继承SurfaceView并实现SurfaceHolder.Callback接口
使用接口的原因：因为使用SurfaceView 有一个原则，所有的绘图工作必须得在Surface 被创建之后才能开始(Surface—表面，这个概念在 图形编程中常常被提到。基本上我们可以把它当作显存的一个映射，写入到Surface 的内容
                      可以被直接复制到显存从而显示出来，这使得显示速度会非常快)，而在Surface 被销毁之前必须结束。所以Callback 中的surfaceCreated 和surfaceDestroyed 就成了绘图处理代码的边界。

需要重写的方法

　（1）public void surfaceChanged(SurfaceHolder holder,int format,int width,int height){}

　    //在surface的大小发生改变时激发

　（2）public void surfaceCreated(SurfaceHolder holder){}

　    //在创建时激发，一般在这里调用画图的线程。

　（3）public void surfaceDestroyed(SurfaceHolder holder) {}

　    //销毁时激发，一般在这里将画图的线程停止、释放。

整个过程：继承SurfaceView并实现SurfaceHolder.Callback接口 ----> SurfaceView.getHolder()获得SurfaceHolder对象 ---->SurfaceHolder.addCallback(callback)添加回调函数---->SurfaceHolder.lockCanvas()获得Canvas对象并锁定画布----> Canvas绘画 ---->SurfaceHolder.unlockCanvasAndPost(Canvas canvas)结束锁定画图，并提交改变，将图形显示。

3、SurfaceHolder
这里用到了一个类SurfaceHolder,可以把它当成surface的控制器，用来操纵surface。处理它的Canvas上画的效果和动画，控制表面，大小，像素等。
几个需要注意的方法：
(1)、abstract void addCallback(SurfaceHolder.Callback callback);
// 给SurfaceView当前的持有者一个回调对象。
(2)、abstract Canvas lockCanvas();
// 锁定画布，一般在锁定后就可以通过其返回的画布对象Canvas，在其上面画图等操作了。
(3)、abstract Canvas lockCanvas(Rect dirty);
// 锁定画布的某个区域进行画图等..因为画完图后，会调用下面的unlockCanvasAndPost来改变显示内容。
// 相对部分内存要求比较高的游戏来说，可以不用重画dirty外的其它区域的像素，可以提高速度。
(4)、abstract void unlockCanvasAndPost(Canvas canvas);
// 结束锁定画图，并提交改变。
4、实例

这里的例子实现了一个矩形和一个计时器

View Code

  1  package  xl.test;
  2 
  3  import  android.app.Activity;
  4  import  android.content.Context;
  5  import  android.graphics.Canvas;
  6  import  android.graphics.Color;
  7  import  android.graphics.Paint;
  8  import  android.graphics.Rect;
  9  import  android.os.Bundle;
 10  import  android.view.SurfaceHolder;
 11  import  android.view.SurfaceView;
 12 
 13  public   class  ViewTest  extends  Activity {
 14       /**  Called when the activity is first created.  */
 15      @Override
 16       public   void  onCreate(Bundle savedInstanceState) {
 17           super .onCreate(savedInstanceState);
 18          setContentView( new  MyView( this ));
 19      }
 20       // 视图内部类
 21       class  MyView  extends  SurfaceView  implements  SurfaceHolder.Callback
 22      {
 23           private  SurfaceHolder holder;
 24           private  MyThread myThread; 
 25           public  MyView(Context context) {
 26               super (context);
 27               //  TODO Auto-generated constructor stub
 28              holder  =   this .getHolder();
 29              holder.addCallback( this );
 30              myThread  =   new  MyThread(holder); // 创建一个绘图线程
 31          }
 32 
 33          @Override
 34           public   void  surfaceChanged(SurfaceHolder holder,  int  format,  int  width,
 35                   int  height) {
 36               //  TODO Auto-generated method stub
 37              
 38          }
 39 
 40          @Override
 41           public   void  surfaceCreated(SurfaceHolder holder) {
 42               //  TODO Auto-generated method stub
 43              myThread.isRun  =   true ;
 44              myThread.start();
 45          }
 46 
 47          @Override
 48           public   void  surfaceDestroyed(SurfaceHolder holder) {
 49               //  TODO Auto-generated method stub
 50              myThread.isRun  =   false ;
 51          }
 52          
 53      }
 54       // 线程内部类
 55       class  MyThread  extends  Thread
 56      {
 57           private  SurfaceHolder holder;
 58           public   boolean  isRun ;
 59           public   MyThread(SurfaceHolder holder)
 60          {
 61               this .holder  = holder; 
 62              isRun  =   true ;
 63          }
 64          @Override
 65           public   void  run()
 66          {
 67               int  count  =   0 ;
 68               while (isRun)
 69              {
 70                  Canvas c  =   null ;
 71                   try
 72                  {
 73                       synchronized  (holder)
 74                      {
 75                          c  =  holder.lockCanvas(); // 锁定画布，一般在锁定后就可以通过其返回的画布对象Canvas，在其上面画图等操作了。
 76                          c.drawColor(Color.BLACK); // 设置画布背景颜色
 77                          Paint p  =   new  Paint();  // 创建画笔
 78                          p.setColor(Color.WHITE);
 79                          Rect r  =   new  Rect( 100 ,  50 ,  300 ,  250 );
 80                          c.drawRect(r, p);
 81                          c.drawText( " 这是第 " + (count ++ ) + " 秒 " ,  100 ,  310 , p);
 82                          Thread.sleep( 1000 ); // 睡眠时间为1秒
 83                      }
 84                  }
 85                   catch  (Exception e) {
 86                       //  TODO: handle exception
 87                      e.printStackTrace();
 88                  }
 89                   finally
 90                  {
 91                       if (c !=   null )
 92                      {
 93                          holder.unlockCanvasAndPost(c); // 结束锁定画图，并提交改变。
 94 
 95                      }
 96                  }
 97              }
 98          }
 99      }
100  }