salesforce-ux/design-system-android

design-system-android's Issues

Manifest file declares application label

The library manifest file contains a label attribute for the application element. This will conflict with consuming apps.

There is an easy workaround to ignore the label, but it shouldn't be necessary. The manifest file should just be an empty element.

Integrated SalesforceDesignSystemIcons and SalesforceSans?

@jandolina We really like the slick look of the new Salesforce UX icons and the SalesforceSans fonts, thank you!

Here's a feature request :

We would like to get the SalesforceSans-*.ttf font(s) embedded in new version(s) of SalesforceDesignSystemIcons.ttf so that we can render both icon glyphs and "regular" text using a single integrated UI component.

For example we would like to be able to specify a single button/label with the text "\uEBA4 Add", which would be the UtilityAdd icon glyph integrated with the " Add" text). Currently attemping this, and specifying SalesforceDesignSystemIcons.ttf will correctly show the icon glyph, but the text will be rendered in the system default font (tested on Android and Windows); and alternatively specifying SalesforceSans-*.ttf will result in the icon glyph not rendering but the text rendering properly in SalesforceSans.

So currently to achieve this integrated icon/text effect, we need to use two different buttons/labels specifying SalesforceDesignSystemIcons.ttf font family for the icon glyph and SalesforceSans-*.ttf for the regular text. This makes for unnecessarily verbose code when managing the composite UI.

This new feature would be nice to have for the SalesforceSans-*.ttf and SalesforceDesignSystemIcons.ttf fonts across all supported platforms (iOS, Android, Windows, etc).

Kind regards!