Proposal: Unseal all the things
## Summary  <!-- Include 1-2 sentences summarizing your feature or API proposal --> ## Rationale <!-- Create a list that describes WHY the feature should be added to WinUI for all developers and users. Proposals often have multiple motives for why we should do the work, so list each one as a separate bullet. If applicable you can also describe how the proposal aligns to the current WinUI roadmap and priorities in a separate paragraph: https://github.com/Microsoft/microsoft-ui-xaml/blob/master/docs/roadmap.md --> * Enable developers to subclass a wider range of our classes/controls (longstanding request from our community) <!---------------------- The below sections are optional when submitting an idea or proposal. All sections are required before we'll accept a PR to master, but aren't necessary to start the discussion. ------------------------> ## Scope <!-- Please include a list of what the feature should and shouldn't do by filling in the table below. 'Must' implies that the feature should not ship without this capability. 'Should' is something we should push hard for, but is not absolutely required to ship. 'Could' is a nice-to-have; a good stretch goal that isn't painful if we don't achieve it. 'Won't' is a clear statement that the proposal/feature will intentionally not have that capability. This list will evolve and grow as the proposal becom
Posted by ryandemopoulos on May 30, 2019, 5:40 PM
Tags
Related issues
- This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
- I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
- the new VSCode UI, looks cute, i don't like it.
- I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
- The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
- Add PR-style review comments in Git Diff UI that feed into the active agent thread
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
ux (Software)
This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
the new VSCode UI, looks cute, i don't like it.
I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
Add PR-style review comments in Git Diff UI that feed into the active agent thread
Thanks for indulging me so far, by the way, I really appreciate this discussion, it's very stimulating.
Migrate GDScript to the GDExtension mechanism and overhaul the implementation
Proposal: Unseal all the things
## Summary  <!-- Include 1-2 sentences summarizing your feature or API proposal --> ## Rationale <!-- Create a list that describes WHY the feature should be added to WinUI for all developers and users. Proposals often have multiple motives for why we should do the work, so list each one as a separate bullet. If applicable you can also describe how the proposal aligns to the current WinUI roadmap and priorities in a separate paragraph: https://github.com/Microsoft/microsoft-ui-xaml/blob/master/docs/roadmap.md --> * Enable developers to subclass a wider range of our classes/controls (longstanding request from our community) <!---------------------- The below sections are optional when submitting an idea or proposal. All sections are required before we'll accept a PR to master, but aren't necessary to start the discussion. ------------------------> ## Scope <!-- Please include a list of what the feature should and shouldn't do by filling in the table below. 'Must' implies that the feature should not ship without this capability. 'Should' is something we should push hard for, but is not absolutely required to ship. 'Could' is a nice-to-have; a good stretch goal that isn't painful if we don't achieve it. 'Won't' is a clear statement that the proposal/feature will intentionally not have that capability. This list will evolve and grow as the proposal becom
Comments (0)
No comments yet. Start the discussion.