Move Breeze to Framework

[Carl Schwan]

On Wed, Jan 8, 2025, at 6:24 PM, Nate Graham wrote:
> On 1/3/25 8:17 AM, Nicolas Fella wrote:
> > Am 30.12.24 um 18:51 schrieb Nate Graham:
> >> A long term concern I have is that it's messy and unpleasant to have
> >> default styling data scattered across so many places. Ideally we'd be
> >> able to centralize *all* data about a particular style in a single
> >> repo, so that making changes is easy and that repo can be swapped out
> >> for another one in the future.
> >>
> >> I see an opportunity to move closer to that here. So my preference
> >> would be to implement the proposal, but also:
> >> - the default window decorations remain in Breeze
> > 
> > That part is problematic. The window decoration needs KDecoration, which
> > is not in Frameworks, and given that it's closely tied to KWin I'd argue
> > it shouldn't be.
> 
> That's reasonable, but on the other hand having Breeze retain a close 
> tie to KWin muddies the story about our apps being designed to work well 
> outside of a Plasma environment. From that perspective, it may be worth 
> thinking about how to break the strong link.

Which is why the breeze decoration should go to the kdecoration framework.
It's only used on Plasma, not anywhere else where our apps with Breeze are
used and it's the only part of Breeze which actually depends on some plasma
stuff.

> 
> Nate
>