Font awesome icons : how should we store the collection server side, for an optimal ease of maintenance ?

[ghost]

The question is : what is the most convenient format to use for the icon list ?
The solution should take into account the ease of initial creation and maintenance of such a list.

In an ideal world, the best solution would be to use a raw css file downloded from fontawesome.com, which would be parsed by a smart php ajax callback to produce a js parsable json sent to the customizer.

@eri-trabiccolo let's discuss that tomorrow.

[ghost]

@eri-trabiccolo, the icon list is now generated by a specific method ( see a461849 and 77de31e )

[ghost]

see #55

[eri-trabiccolo]

Hi Nico,
actually I was thinking about something slightly different;

1. we should refer to our own font-awesome version not the remote one (our set might be not in sync)
2. we actually don't need raw css file to parse, icons can be retrieved by svg files (they're basically xml):
   https://raw.githubusercontent.com/presscustomizr/customizr/dev/assets/shared/fonts/fa/webfonts/fa-brands-400.svg
   See glyph-name attribute of the glyph tag

So basically what we should do is:

1. parse the 3 svg files convert them into json
2. create the merged icon list A-Z ASC ordered

The whole thing could have been done in js only but since the PHP template (with the caching mechanism) is already there now, we can do 1) (and potentially 2)) in PHP (libxml is usually included in PHP installs - users don't having it won't be able to use the icon module: we really should not care about poor hostings IMHO)
Then we just have to send the whole thing in json, and build the select in JS.

What do you think?

[eri-trabiccolo]

Do you want me to look for a way to automatically download and put into nimble the whole font-awesome assets too?

[EDIT]
In a skype call we decided to not do this for the moment.

[eri-trabiccolo]

fixed in #58
the code to generate the file can be found in #57

#58 doesn't include the code above, hence you need to manually run (add) it.