Is your feature request related to a problem? Please describe.

I am new to Swift and am having trouble understanding the use of ColibriComponents.

Describe the solution you'd like

If the screenshots/images in the markdown files were accompanied by the code for them, that'd be a great solution.

Describe alternatives you've considered

Improve the documentation with more examples of actual usage instead of template code.

Additional context

That's all, thanks!

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

Hi @david-swift ,

thank you very much for creating such a great package.

I'm looking for a library which can help me to create a native setting screen for my macOS app and I have just found this repo.

I find that it'd be helpful for us if we can have a sample app demonstrating some common usages for this package.

Wdyt?

Describe alternatives you've considered

N/A

Additional context

N/A

Overview

I wanted to render a TabView within the SettingContent but it doesn't seem to work. Any idea why?

Here is my code:

// App.swift
...
.settings {
  SettingsTab(.init("Inline" as String, systemSymbol: .textBelowPhoto), id: "shortcut") {
        SettingsSubtab(.noSelection, id: "no-selection") {
            InlineSettingsView()
        }
    }
  }

//  InlineSettingsView.swift

struct InlineSettingsView: View {
    var body: some View {
        TabView {
            Text("A")
                .tabItem {
                    Label("A", systemSymbol: .person2)
                }
            
            Text("B")
                .tabItem {
                    Label("B", systemSymbol: .person2)
                }
        }
    }
}

I wanted to achieve something like this:

Overview

The design of the sidebar buttons is not great yet. Any chance we can make it minimal like the rest of the macOS apps?

Example XCode app:

Is your feature request related to a problem? Please describe.

This feature doesn't make sense when the user always need to edit something on the sidebar. A misclick might render the "No selection" screen which is just a text "No row selected" etc. Which is kinda annoying.

Describe the solution you'd like

Allow developers to specify the behavior. Maybe show "No selection" screen only if there is no rows in the sidebar. Otherwise, always select one row.

Describe alternatives you've considered

Not sure.

Additional context

This is for SettingsSubtab

Is your feature request related to a problem? Please describe.

Basically the title. Is it possible to trigger the Setting window to select a tab after showing up

Describe the solution you'd like

A method or some other way to set which tab to focus on. Maybe a Binding when creating the Setting View?

Describe alternatives you've considered

Not sure.

Additional context

Not sure.

Overview

This is more of a question than a feature request though. The actions is working great, however, it's common to show a dropdown menu when clicking on the Plus button, or when clicking on the options

Like this:

How can I achieve this with SettingsKit?

I can see that the ToolbarAction body is a Button. Maybe we should allow developers to specify the body or to create a custom ToolbarAction (make it a protocol maybe)?

@david-swift

Is your feature request related to a problem? Please describe.

After a new SettingsSubtab is created, SettingsKit does not select that tab automatically. Not a good UX

Describe the solution you'd like

After a new SettingsSubtab is created, automatically select that tab.

Describe alternatives you've considered

Another solution is allowing developer to specify the $selection.

Additional context

Reference:

One of my apps still need to support macOS 12.

Is it possible to use SettingsKit on macOS 12?

If yes, how can I do it?

Thanks for your great work!

Problem

The SettingTab always have a fixed height. Is it possible to have it automatically adjust based on the inside content?

SettingsKit:

Preview app:

Thanks for the good work.

Problem Statement

The current implementation of . standardActions {} uses index instead of id for the remove action. This is quite problematic when the order of the list changes, or when there is a mix of static items and dynamic items.

Let me explain. Given this code:

SettingsTab(.init("Models" as String, systemSymbol: .cpu), id: "model") {
  SettingsSubtab(.init("Static Item 1" as String, systemSymbol: .cpu), id: "model-static-1") {
    StaticItem1()
  }

  SettingsSubtab(.init("Static Item 2" as String, systemSymbol: .cpu), id: "model-static-2") {
    StaticItem2()
  }

  for item in dynamicItemList {
    SettingsSubtab(.init(item.name, systemSymbol: .cpu), id: "model-\(recordId)") {
        DynamicItem(item: item)
    }
  }
}
.standardActions {
    // 
} remove: { index in
    // handling index here can be annoying, for example when I add more Static item in the front
    // will need to increase the check for index each time to find the correct item to be removed
}

When removing an item, I always have to check if the index >= 2 (dynamic) or static. When I add new static item to the settings sub-tabs, it's prone to error.

Suggestion

Maybe support both index and id in the callback parameters? Something like this

.standardActions {
    // 
} remove: { id, index in
    // handling index here can be annoying, for example when I add more Static item in the front
    // will need to increase the check for index each time to find the correct item to be removed
}

IMO, id should be the source of truth, not index.