In the past few days, I have been looking at the source code for chrome and WebKit, read the wiki and watch Google videos. What I want to do is take what WebKit renders and put in the GL texture. But I need to have different DOM nodes in different textures. I have a few questions, and I'm not sure if I should use Chromium or implement my own simple browser. Chromium obviously has a lot of nice features, but it is very large and extensive. I also find that the algorithms for splitting rendering layers are unpredictable (I want to have pretty good control).
Where to find in the source of WebKit or Chromium, where it displays raster data? It would be convenient if I could access the RX raster data to compost. But, as I said, the rendering layers will probably mix me up so that I don’t want them to be.
Is WebKit GPU accelerator, in this case I should be able to directly access the data. I know that Chromium + Blink is there, but I cannot find out if WebKit is on its own.
How much does it all have to do with a simple browser?
PS I can’t use Awesomium because I need to map different DOM nodes / sub-segments to different textures. The Chromium Embedded Framework does not have support for DOM manipulation, and I believe that it simply displays the entire page and gives you raster data.
source share