profile
viewpoint

draft-js-plugins/draft-js-plugins 3618

React Plugin Architecture for Draft.js including Slack-Like Emojis, FB-Like Mentions and Stickers

ianstormtaylor/awesome-heroku 224

A curated list of helpful Heroku resources.

ianstormtaylor/bump 65

Easily bump the version of all the different package.json equivalents.

ianstormtaylor/animate.sass 53

A fork of animate.css written in SASS with a few modifications.

ianstormtaylor/browser-logger 44

A dead simple logger, designed to be perfect for the browser.

ianstormtaylor/backbone-inheritance 12

(I no longer use Backbone, but feel free to check this plugin out. The code is pretty straightforward.) A Backbone.js mixin that lets Views inherit properties from their parents.

ianstormtaylor/animate 10

Easily apply animate.css animations to elements via Javascript.

ianstormtaylor/backbone-state 9

(I no longer use Backbone, but feel free to check this plugin out. The code is pretty straightforward.) A Backbone.js mixin that adds states to Views.

brighthas/textarea-indent 8

html textarea auto indentation.

ianstormtaylor/assert-dir-equal 6

Assert that the contents of two directories are equal.

issue commentseiyria/gameicons-font

Use ligatures?

@seiyria awesome! I dig a little digging, and it looks like the SVG transformer technically support ligatures, but that something in the TTF transformation doesn't? I'm not exactly sure, but I opened an issue upstream: https://github.com/nfroidure/svgicons2svgfont/issues/114

ianstormtaylor

comment created time in 2 months

issue openednfroidure/svgicons2svgfont

Human-readable ligatures?

Feature request

I'd like to be able to use a word as a ligature in a font, but for some reason it doesn't seem to work. For example, unicode: ['heart'] would ideally only render a heart icon when the user types 'heart'.

created time in 2 months

startednvm-sh/nvm

started time in 2 months

issue commentseiyria/gameicons-font

Use ligatures?

Fair enough, if you haven't touched it in 5 years I doubt it makes sense then. FWIW though, the ligatures approach is a better approach in almost all cases since it means the font can easily be used in places other than CSS.

how this would work with angular bindings (does <i class="gameicons">{{ name}}</i> work?)

Yup, that would work.

what changes need to be made for this to work? are they any packages that can be dropped into the build process to do this?

I'm not sure how ligatures in fonts are described, so I don't know.

can a separate output for this be created so both options are available?

Yup! Both approaches can exist in the same font.

what are the drawbacks and benefits for both approaches?

The current approach only works for CSS. If you wanted to use the font in mobile apps, printed materials, digital images, etc. then you have to go through a really tedious process to use the glyphs. The only real drawback to the ligatures approach was compatibility, but all modern browsers and operating systems support them these days.

ianstormtaylor

comment created time in 2 months

issue openedseiyria/gameicons-font

Use ligatures?

This font is awesome! It works for CSS-based use cases, but I was hoping to use it in a graphics program like Figma or Photoshop. Right now this is really hard to do. (You have to copy the unicode string directly from the CSS files, convert it to an actual glyph which renders as just a black box, then paste this glyph into your text somewhere.)

Ideally it would work how the Material Icons (docs explanation) font does with ligatures, where you can just type bloody-sword in the font and it will become the "bloody-sword" icon automatically. This makes it really easy to use everywhere.

If the font build process could support this it would be amazing!


Side benefit: this would make CSS use easy still too, because you can just add a single class like:

<i class="gameicons">bloody-sword</i>

created time in 2 months

more