HandyOrg / HandyOrg/HandyControl
不能够独立的引入用户认为需要的部分
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
每个公司都是有自己基本的主题的。我们只需要使用你们中我们很认可或优秀的地方而不是全部，我观察源码，你们把Theme.xaml，以及三个默认样式xaml生成操作都是页。而其他所有控件生成操作都是无。这导致我只能引入Theme.xaml，这会引入所有样式，而无法单独使用你的某个控件或者样式。我也观察了其余ui框架。比如MaterialDesignThemes及其他，他们的每个xaml生成操作都是页，都支持单独引入某个控件。下图1，2分别是你们的图片。3是其余框架的截图。或者说你们这样做有其他意义，请解答。或者有其他方式？
Steps to reproduce the bug
1 打开源码。
2 打开theme.xml 点击属性，发现生成操作为页
3 打开TextBox.xaml 点击属性，发现生成操作为无
4 打开其余ui框架的源码，点击任意xaml,点击属性，生成操作为页
Expected behavior
我认为，每个框架应该是支持别人使用它被认为需要部分，而非全部
Screenshots
No response
NuGet package version
None
IDE
No response
Framework type
No response
Windows version
No response
Additional context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the resource and build settings for Theme.xaml and TextBox.xaml, as described in the issue, and inspect how the default styles are packaged. Determine whether individual control styles can be consumed without importing the full theme, then verify the result with a minimal WPF usage example. Done means the requested parts can be included independently or the supported limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100