⏪ ⏩ are two examples, while these ► are pretty plain. Not that I don't like the specific designs, but the customization destroys any chance of their use if you want to keep consistent looks. In chrome they are on a blue background. I think other browsers might display them differently. Would be cool to have a neutral design that could be adjusted by font color.
But anyway, thank you for your work!
FYI, Unicode has two symbols, xFE0E and xFE0F, which explicitly requests the previous character to display as either a "text" (i.e. a solid vector) or "emoji" representation, respectively. These are well supported in browsers.
Test:
⏩⏫⏪⏬◀▶⤵↩↔↙↘↖↗⬆⬇⬅↕↪ℹ⤴🆒🈳🈶🈚🈵🆓🆗🆖🈴🈲🉐🈹🈁🆕🆙🈺🆔🆘🆑㊗㊙🈂Ⓜ🉑🈸🈷🅰🅱🆎🅾©®™‼⁉⭕〰◼◻◾◽▪⬜⬛▫〽
Course HN does just fine without Emojis. I can only imagine the amount of downvoting that would ensue. I could see maybe some being useful like the arrows.
Edit:
By the looks of it the emojis that are meant to be signs work. The ones that are actual faces do not.
∫ x² dx
∑ φᵢ yᵢ = 1
z ∈ ℝᵐ
https://evil-icons.io/ https://css.gg/ https://ikonate.com/ https://boxicons.com/
Not saying there's anything wrong here, for all I know it might be the same author on both projects. Taking a closer look, it might even be the case that tabler-icons is just a rebranding of FeatherIcons.
What does "quality" mean for SVG icons though? I could choose the resolution to be whatever I want.
For instance, I could mangle some SVG icons and while you could scale them to an infinite size.. you wouldn't want to use them ;)
These look great BTW!
That said, some of the icons reminded me of this article:
The GitHub account links to this site:
Which looks like a typical sales page. But it also says "free" everywhere. No info on pricing or business model.
The icons page tays to install the icons like this:
npm install tabler-icons --save
Does this make you vurnurable to code coming downstream from this repo in the future?- paid support
- paid premium components
- etc
I also see they are already selling email tenplates here: https://gumroad.com/l/tabler-email?utm_source=demo
I'm also very actively looking for a catch whenever I see something like this but this seems entirely benign as far as I can see.
Edit: there's also a pay-what-you-want page when you click download. Still totally ok with me.
The command is a standard way to install a module and save that specific version in package.json. By default I believe it's "^x.x.x", which allows patch versions that increment the last number when explicitly updating - otherwise re/install will always get that specific version.
It's no less (or more) secure than any other dependency. The last vulnerability that I heard about was the ability for modules for run arbitrary commands, for example from the pre/post-install step. If I recall correctly, they added an optional way to disable this, but many modules make use of it for compiling native code, etc.
So - I'd say yes, installing any dependency will make you vulnerable to code coming downstream. However, an SVG icon library with little to no executable code can probably be considered low risk.
can probably be considered low risk
How so? I would think it puts its files in a publicly accessible path. That means if it puts executable code there (python,php,js whatever)
in a future release it allows for a server-takeover.I like that I can select only a few icons and generate a custom true type font straight from the web application.
The toolkit is Dear ImGui and I load the TTF font with the simple API AddFontFromMemoryCompressedBase85TTF.
Then when I need a button with an Icon I just use it like this: if (ImGui::Button(ICON_FIRST, button_sz)) { }
The trick in C++ was to define the ICON_FIST in this way:
#define ICON_FIRST u8"\uea21"
I can then rescale my interface by simply changing the font size and the icons keep all nice and clean.
And if you in-line the SVG then you don’t get caching benefits.
Plus you can actually style the individual strokes with icomoon icons - it’s just not as trivial.
Disclaimer: I’ve been a happy icomoon customer for years (I just wish they had an API).
"MIT License" is not the same thing as "MIT Licensed". MIT did not license these.
*eyeroll*