Closed amkuchta closed 4 years ago
@punker76 if you agree with this, I can create a PR to clean it up.
/cc @Evangelink WDYT?
Yeah :D I was having the same feeling when working on adding MUI styles.
Should I go ahead and create a PR, @punker76 & @Evangelink? And if so, would you like me to break out the namespace a bit more to make room for MUI, perhaps like so:
MahApps.Font.Family.Header.Default
MahApps.Font.Family.Header.MUI
That's ok on my side @amkuchta! Regarding the .Default
suffix, it's up to you, I was a bit out of time lately to make progress on MUI.
I just think it would be nice to have all of the names go to the same depth, and Default
tells users what the normal value would be for MA.M vs MA.M's implementation of MUI (or any other style that may be included in the future)
Is your feature request related to a problem? Please describe.
Looking through the new naming conventions,
Fonts
are structured as follows:MahApps.Fonts.[Family]
(e.g.MahApps.Fonts.Header
)MahApps.Sizes.Font.[Size]
(e.g.MahApps.Sizes.Font.Header
)I think that this is namespacing is inconsistent, and that a small update could make things easier for other users to follow.
Describe the solution you'd like
I suggest updating to the following naming convention for consistency:
MahApps.Font.Family.[Family]
(e.g.MahApps.Font.Family.Header
)MahApps.Font.Size.[Size]
(e.g.MahApps.Font.Size.Header
)This creates a more consistent (and therefore easier to use) namespacing.
Additional context
N/A
Closed Issues
N/A