On Monday 21 February 2011 22:11:23 Aaron J. Seigo wrote: > On Sunday, February 20, 2011, Martin Gräßlin wrote: > > What do you think about this idea? > > first, thumbs up for daring to ask the Big Questions. it's something i > appreciate in you as a developer :) > > so ...personally, i'm ok with re-thinking the options in the kcm GUI, but i > feel that it is a very bad time to try and make it depend on opengl with no > way for the user to turn it off because: yes I think the majority was for not changing ;-) > <snip> > what might make for an interesting "could it be done?", and i don't know if > it could be in kwin, is taking all the non-composited code and moving it > out of kwin core as a compile time option. this would at least allow > devices using kwin to avoid whatever code overhead would be incurred. i'd > even go so far as to remove the auto-disable functionality in those cases, > since the harware is 100% known. Part of it is done, part of it can be done, most of it cannot be done. * OpenGL 1 code is ifdefed if compiled against GLES * XRender Code could be disabled and is disabled if XRender is not found * Core is mostly too strongly coupled to disable functionality. At the moment I think only Tabbox could be disabled at compile time.
As mentioned some time ago I would like to have core more modularized which would allow to cherry-pick the features wanted at compile time. Cheers Martin
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
