Move Breeze to Framework

[Nate Graham]

On 12/30/24 12:31 PM, christoph at cullmann.io wrote:
> On 2024-12-30 18:51, Nate Graham wrote:
>> 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
>> - the default colors remain in Breeze, and are removed from KColorScheme
> 
> I think that is no good idea, that makes then Breeze even mandatory if 
> an application just wants to have dark mode.

Breeze is already increasingly being made mandatory in our apps, right? 
Our apps need to have *some* theme available.


>> - breeze-icons is merged into Breeze
> 
> Like above, not sure about that. Even if one can just build and install 
> parts that seems to me like we will have some 'super framework'.
> 
> I think colors and icons are decoupled enough, users are even allowed to 
> change them and I fail to see the large issue in having them in 
> different repos.

It's not a huge deal, but I think it's nice to have a complete theme in 
one git repo so it's clear where to make changes and what needs to be 
replaced once we change the default theme.

Put another way, if Breeze and Breeze Icons are both frameworks, and 
both mandatory, and both full of Breeze assets, I don't see a compelling 
reason *not* to merge them.


Nate