Issues with Content API

Information gathered by us and friends (Qt)

• First impression: The Content API layer is not a layer at all. it's the same as the rest of the code base: a huge set of classes with a ridiculous amount of interfaces
• All interfaces are extremely well unit tested
• You'll easily go through many different layers as you try to use it
  • Network code demands a deep hierarchy of classes/calls to be built. Building this structure is not trivial, even if the pieces are there already.
• What is really missing is
  • Convenience (it's crazy how many things you have to implement to fire up basic functionality)
  • A much improved rendering interface
• On the upside, due to the lack of layering, it seems you can just use any class you'd like and re-implement anything.
• Q: how easy is it going to be to follow changes?
• The Content API doesn't provide the abstraction on an integration level but on a windowing system level (in terms of rendering)

Qt issues:

• The main issue as far as I can see right now with the code base is that the rendering is completely unsuitable for Qt (out of the box at least)
• The way the sources are organized no patches are required at all since all classes are equal in terms of "export"
• Qt are convincend that Qt integration can be done completely out of tree
• An out of tree QT integration AFAICS right now would use very little of the Content API layer, because all it provides in terms of graphics is a GtkWidget* on X11 and the android webview is inside the content layer AFAICS (I mean, render_host_widget_view_android.cc is next to the other ones, not on top)