I'd like to try and help out on WxWidgets wrapper. It's mostly GUI I guess, but does have OpenGL calls, networkign, pretty much anything. But Reaction part is of course GUI. I guess I'm asking these questions because we are seeing traditional GUI windows making more use of graphics hardware. Going beyond 2d line and shape functions to using 3d for what we use as a 2d window to scale it easier than an overlay, etc. So for all things that we could have accelerated using more recent 3d methods than old 2d methods, I want to take advantage of this as much as I can for WxWidgets GUIs, be they GL or 2d things. But for discussions I've seen about our current hardware compositing, it seems Cairo is what gets named, not Reaction, so I began to wonder if Cairo got some special treatment early on that Reaction was still waiting for. And when Mesa comes, will Cairo or Reaction or whatever be the first to benefit from any additional hardware accleration due to that. Reaction I think is the obvious target for a GUI API wrapper on OS4, regardless of accelerators. In time, if Reaction doesn't support something but it gets added later, anything using Reaction will magically get faster on that feature. I guess I'm curious, at what level does this hardware compositing or other acceleration fit in for our graphics stuff? Do Cairo and Reaction and anything else each have to support it themselves somehow, or is it now a fundamental way of doing things at our lowest levels of graphics support in teh OS, and thus any grapics related thing uses hardware compositing/acceleration without needing to know about it? Such as, I know P96 drivers can have 2d hardware accelerated things, but P96 does not do 3d. How do P96 applications benefit from modern 2d methods using 3d hardware features or whatever it is that we call compositing? Things like that.