On Wednesday 02 March 2011 17:54:53 ext Clark, Joel wrote: > On Wednesday, March 02, 2011 4:53 AM Gabriel M. Beddingfield wrote > > > However, the MTF includes things like mcompositor, > > mdecorator, duicontrolpanel, etc... These are fundamental > > parts of the Handset UX, the IVI UX, and the Tablet UX. So, > > if the MTF is scheduled for termination... then I missed a > > memo somewhere. > > > > -gabriel > > Small correction. The current IVI images don't include mcompositor and the > current IVI home screen uses QT and matchbox2. > > Also can't mcompositor be separated from MTF and run on other frameworks?
Yes, the core mcompositor framework does not depend on MTF. Though currently, the decorator implementation is linked to MTF to draw the a MTF-looking border around 3rd party application, but even that can be replaced. The decorator library is abstracted so one can easily create their own decorations based on another toolkit. I understand that MCompositor currently is quite underdocumented and probably not very understood very well in MeeGo. Should spend some time creating arch docs for it - too little too late though :) Cool stuff you can do for it is for example easily writing GLSL shader effects (see MCompositeWindowShaderEffect class for example) for windows and has an extremely flexible animation system based on Qt's animation framework that can easily be extended using plugins. -abdiel > > regards > Joel > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
