.palette Modifier Cannot be Applied to WindowGroup

[MatiMax]

Issue

The .palette modifier cannot be applied to WindowGroup as demonstrated in the README.md.

Tested Environment

The test has been conducted on

• Ubuntu Server 24.04 LTS with Swift toolchain version 6.3.2
• macOS Sequoia 15.7.7 with Swift toolchain version 6.2.4.1.4

and TUIKit main branch version.

How to Reproduce

@main
struct MyApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
       }
        .palette(SystemPalette(.green))  // Classic green terminal 
    }
}

Observed Behaviour

Compiling the code will result in the following error:

App.swift:9:5: error: value of type 'WindowGroup<ContentView>' has no member 'palette'
 7 |             ContentView()
 8 |         }
 9 | 			.palette(SystemPalette(.amber))
   |     `- error: value of type 'WindowGroup<ContentView>' has no member 'palette'
10 |     }
11 | }

Expected Behaviour

Compiling the code should be successful regarding to TUIkit's own documentation.

Work-around

Moving the .palette modifier to the ContentView() results in successful compilation, and the application works visually as expected.

[wadetregaskis]

I'm not sure if this repo is still active - there's been no commits for a couple of months, and pull requests are disabled.

This bug (and your other one, #1) are fixed in my fork, https://github.com/wadetregaskis/TUIkit (as are hundreds of other issues).

[MatiMax]

Hi Wade, thanks for pointing this out. Glad to see, that this repository gets love from other fork maintainers. 😇 I've been in direct messaging contact with Phranck (he happens to live nearby me), but I cannot tell if and when he spends time on TUIkit. It seems he's got some nice projects on the way that eat up time.

Yes, I noticed that the repository has pull requests disabled which certainly limits the possibility of getting things fixed in this repo. Also, as Stewart Lynch recently posted two videos about TUIkit I think it would be a good move to think over the strategy of letting the community help fixing things—that's my humble opinion, for what it's worth … 😉

Thanks for referring to your repo. I really want to get a TUI app on its way with TUIkit, but I was hesitant because of some glitches that might block me on the way. So, I'll be glad to try out your fork.

Thanks for your comment and your fantastic work on your fork.

P.S. By the way, the scripts in TUIkit/project-template in your fork have not been updated to point to your repository, hence when creating a new app using tuikit init it will reference still Phranck's repo. So, that's a heads up for those working with your fork.

[wadetregaskis]

My original intent was to just fix a few personal showstoppers and upstream those, but then (a) I realised I couldn't do pull requests and (b) I kinda got carried away. 😆

I'm also excited to have a TUI framework for Swift that's relatively easy to use. There's a few other packages that have dabbled in this area previously, but in a much more rudimentary way.

P.S. By the way, the scripts in TUIkit/project-template in your fork have not been updated to point to your repository

Ooh, thanks for noting that! Whoops. 😅

I'll fix that momentarily.

[phranck]

I'm not sure if this repo is still active - there's been no commits for a couple of months, and pull requests are disabled.

This bug (and your other one, #1) are fixed in my fork, https://github.com/wadetregaskis/TUIkit (as are hundreds of other issues).

Howdy! It IS still active. However, I've got very little time at the moment. But things are looking up... 😄

Btw: I opened PRs for my repo. So, I had a look over your fixes and additions in your fork. I would like to invite you to open pull requests.

[phranck]

@wadetregaskis If it's okay I would like to add you as a collaborator to this project. Please let me know.