Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spec: Restructure the Toolkit #1

Open
Lamparter opened this issue Dec 7, 2024 · 0 comments
Open

Spec: Restructure the Toolkit #1

Lamparter opened this issue Dec 7, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@Lamparter
Copy link
Member

📄 Description

This is an incredibly big task and project, and will require a lot of help.
This issue represents and tracks the progress of the brand new Toolkit (new name required!) including the merge of:

  • GlowUI
  • CrimsonUI
  • Crimson.Toolkit
  • CubeKit

⚡ API Changes

This will require significant changes to the way that the Toolkit API is built. Unlike CommunityToolkit and others, this will have both UWP and WindowsAppSDK versions inside the same package (using the Alloy application model documented here)

👥 Usage scenarios

A rudimentary list of the most famous new Toolkit APIs: (see sub-issues or comments for more)

UnifiedApp

public partial class UnifiedApp : Microsoft.UI.Xaml.Application

ThemeHelper

public bool IsThemeEnabled(Guid themeId)

🔙 Backward Compatibility

This will break everything that previously used GlowUI, CubeKit, CrimsonUI and Riverside.Toolkit.
They will need to be adapted and namespace references must be updated.

🤔 Difficulty

High

@Lamparter Lamparter added the enhancement New feature or request label Dec 7, 2024
@Lamparter Lamparter added this to the New Toolkit milestone Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants