{"id":20970,"date":"2015-03-26T16:09:16","date_gmt":"2015-03-26T15:09:16","guid":{"rendered":"https:\/\/www.inovex.de\/\/?p=231"},"modified":"2015-03-26T16:09:16","modified_gmt":"2015-03-26T15:09:16","slug":"android-graphics-pipeline-from-button-to-framebuffer-part-1","status":"publish","type":"post","link":"https:\/\/www.inovex.de\/de\/blog\/android-graphics-pipeline-from-button-to-framebuffer-part-1\/","title":{"rendered":"Android Graphics Pipeline: From Button to Framebuffer (Part 1)"},"content":{"rendered":"

In this mini-series of blog articles we want to shed some light on the internals of the Android Graphics Pipeline. Google itself already released some insights and documentation on the subject such as the beautiful Google I\/O 2012 talk For Butter or Worse<\/a><\/em>\u00a0by Chet Haase and Romain Guy (go watch it if you haven\u2019t!) or the article Graphics architecture<\/a><\/em>. While they certainly help to get the big picture involved in getting a simple view displayed on the screen, they are not that helpful when trying to understand the source code behind it. This series will give you a gentle jump start into the interesting world of the Android Graphics Pipeline.<\/p>\n

Beware, a lot of source code and sequence diagrams will be involved in this mini-series! Its worth a read though, especially if you have even the slightest interest in the Android Graphics Pipeline, as you are going to learn a lot (or at least get to look at some pretty pictures). So get yourself a coffee and read on!<\/p>\n

\n

<\/p>\n<\/div>