Agree that icon font could be good approach.

However, loading font in the system level risk of creating another
platform-specific Wingdings <http://en.wikipedia.org/wiki/Wingdings> font.
If we are not planning to ship a font to the general web, I will strongly
against doing so. At least, platform font available to general web should
not contain PUA code points, but instead the Emoji code points, if possible.

We need to figure out how to share assets between apps without repackaging
it in every application.zip. It's harder to figure out but it's the right
approach.

<http://en.wikipedia.org/wiki/Wingdings>


On Tue, Mar 19, 2013 at 9:15 AM, Kevin Grandon <[email protected]> wrote:

> Hi All,
>
> I'm currently working with UX on a prototype of utilizing an icon font.
> Using an icon font would have the following advantages:
>
> 1 - Better performance. I profiled and noticed that on average an icon
> font would save roughly 6 ms per icon replaced.
> 2 - Better scalability. As they are vectors, they could scale to any
> device size/dimension seamlessly. No need for @2x images.
>
> Implementation wise, it would look like this:
>
> 1 - A new font file is generated from SVGs, and packaged with the other
> MozTT fonts.
> 2 - The font would be loaded from the system level, and we would map icon
> CSS to the private use unicode range.
> 3 - There should be a transparent migration for apps, as we can simply
> update the building blocks. Or potentially we could force apps to include a
> new small CSS file.
>
> If this looks good, next steps would be to build out the prototype more
> and file bugs for components/apps which should take advantage of the icon
> font. I'd love to hear what you guys think of this approach.
>
> Thanks,
> Kevin Grandon
> _______________________________________________
> dev-b2g mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-b2g
>



-- 
Tim Guan-tin Chien, Senior Front-end Dev., Mozilla Corp. (Taiwan)
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to