There are several reasons why we have chosen our font instead of a third-party font such as Font Awesome
- they do not provide all the icons we need for our controls and we cannot make quick requests for any missing or urgently needed ones;
- we have this font in development and it is used in several other Progress
products as well;
- it is an internal project, which means there would not be any unexpected changes orbroken scenarios, since we are in direct contact with the team that develops and supports it;
- Font Awesome
have stated in their WPF
toolkit that they face the same problem with the glyphs in design-time for VS
, the same we have reported to Microsoft;
is made by us for us
Third-party font glyphs can still be used in user project of course, but our decision was not to rely so much on a third-party library, as we seek to provide as long-during support for our products as possible with the smallest possible amount of braking changes, which tips the scales significantly in favor of an internal product being used in the default styles of our controls.
We sincerely hope that this slight inconvenience would be resolved soon enough in VS
, as we have tried numerous approaches to display them in design time before reporting a bug to MS
, but so far the scenario with a resource in an assembly is not working properly still.
Telerik by Progress
Telerik UI for WPF is ready for Visual Studio 2017 RC! Learn more.