I agree. IMHO it’s much better to have a Custom FA code system instead of, or in addition to the dropdown system. All those lists will all need updating everytime new FA icons are added.
1 Like
That makes the user go to a third-party site to look up a code snippet, essentially, which is something I wish to avoid. I would rather do the work myself and save the user the trouble.
1 Like
Adam: I understand what you’re saying. But I’ve found in practice I typically go to the FontAwesome website anyways as the short text description provided from stacks (yours and several others) don’t really tell me what the icon looks like. Simpler for me to go to FontAwesome, look at things visually (rather than a text list). Adding the FA code is not difficult. But whether I add FA code or simply choose something in a dropdown list is less important to me. The main point is I’m often visiting FA website anyways. (Until, of course, I know a particular icon and name well enough that it’s not needed.)
2 Likes
RW Edit view http://d.pr/i/fYBNm
Also, v4.7 icons are not visible in Edit Mode when used. This bug has also been reported to Isaiah.
I also don’t like list selection for visual things such as icons. I end up spending too much time selecting a few by trial and error, and then visiting the FA site to find the icon I like the look of, remember the name of it, and then going back to the dropdown list to find the matching name.
Roll on the day when Stacks and RW will use a graphical interface.
So true Gary… I complete agree.