Hi, All: I don't know whether this is the right place to post my question, maybe my question is more related with android framework design. I think android is designed with "composited desktop" in heart, here I mean each window doesnot render itself directly on screen, rather they are rendered to separate "back buffers" without any clipping applied (such as obscured by other windows), then the surfaceflinger compose these backstores into the framebuffer to be displayed with z-order or clip rectangle applied. It is the lacking of this feature for core X window in desktop world that leading to xComposite extension which at last leading to compiz to be born. My question is, for compiz, not only simply to composite each window backstores to framebuffer but rather it provides a plugin mechanism that user application can customize the behavior before/in/after the composing process, so such as water effect, magnifier tools/effect can be implemented easily. But for surfaceflinger, is the compose behavior fixed? Do surfaceflinger or windowmanager service or anyone others provide the similar "plugin" interface for application to use for customizing the compose behavior, or the only way left is hacking surfaceflinger? Thanks.
Regards Westermann Fu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
