View Single Post
Posts: 4 | Thanked: 4 times | Joined on Feb 2010
#29
Originally Posted by tomasj View Post
Our compositor is really small (both code and feature wise) and intently focuses on filling the niche of a high-performance OpenGL compositor for handhelds or slightly larger devices. It's not really something you would want to use even on your laptop at this time. It does some quite innovative things like seamlessly un-redirecting the rendering for windows that fill the device screen, which is perfect for a handheld but doesn't make sense in other type of setups.
I understand the reason doing so. What is this "seamlessly un-redirecting rendering"?

Originally Posted by tomasj View Post
That said, the Harmattan UI framework can, and has been, run with other window managers and compositors. The apps don't really make any assumptions in this regard. Still, while the apps can technically be run in software by switching the graphics system, we see it as critical to the user experience that we can depend on OpenGL acceleration being available to us. So we are setting the minimum hardware baseline at the N900 level for the entire framework, and not making any compromises in order to also scale downwards.
As I assume (somewhat confirmed) that Harmattan UI framework will be the base of MeeGo, I think it was targeting much more devices. So I have these ideas because I view it as a more generic compositor and technically it is easy to achieve with Qt. Probably MeeGo will do another window manager/compositor, though it might not as HW OpenGL is also assumed, at least to what I heard.
I really like the graphic system/backend thing of Qt, which makes it possible to use OpenGL or not and it is transparent to application and can be changed at runtime. And this is impossible in clutter based system.
 

The Following 2 Users Say Thank You to ezjd For This Useful Post: